7

I updated Ubuntu 22.04.4 to 6.5.0-21 kernel update, since then I am unable to boot up into Ubuntu. While boot up, there is the error iwlwifi WRT: Invalid buffer destination I tried to boot into recovery mode, but without success (loop in "Starting Network Time Synchronization").

I got a black screen with the following messages.

[   0.004260] __common_interrupt: 1.55 No irq handler for vector
[   0.004260] __common_interrupt: 2.55 No irq handler for vector
[   0.004260] __common_interrupt: 3.55 No irq handler for vector
[   0.004260] __common_interrupt: 4.55 No irq handler for vector
[   0.004260] __common_interrupt: 5.55 No irq handler for vector
[   0.004260] __common_interrupt: 6.55 No irq handler for vector
[   0.004260] __common_interrupt: 7.55 No irq handler for vector
[   0.004260] __common_interrupt: 8.55 No irq handler for vector
[   0.004260] __common_interrupt: 9.55 No irq handler for vector
[   0.004260] __common_interrupt: 10.55 No irq handler for vector
[   5.301695] 
[  12.505302] iwlwifi 0000:06:00.0: WRT: Invalid buffer destination
_

What can I do now?

karel
  • 122,292
  • 133
  • 301
  • 332
LeMoussel
  • 171

4 Answers4

1

Just solved a similar problem. Some how in the power settings my Automatic Suspend settings was changed to plugged- in and should be When on Battery. Apparently the program I am running is not able to let my os know it running. Check your Power settings!

propolis
  • 11
1

I had the same issue, it seems that's related to disk space . I solved this issue by booting into recovery mode, selecting the "clean" option ( that likely initiated a process to remove unnecessary files from the disk) and confirming "Yes" then i was able to reboot my system normally.

Soukaina
  • 11
1

I had the same issue. It was due to disk space. I ran "df -h" and I saw that my root filesystem is 100% full. So I ran "du -h --max-depth=1" to list the largest directories in my current directory and it was my Document. So I moved some of the contents to another location.

Stephen_esu
  • 21
1

I had changed etc/fstab manually to start a partition automatically on startup, but then I removed that partition and separated it in 2. It all looked fine until I restarted the computer and this error showed up. I went back to etc/fstab, removed the line I had added, restarted the computer and it was all good again!

jpenna
  • 180
  • 1
  • 8