Re: Debugging kernel panic on boot.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Somebody in the thread at some point said:

> ata1: port is slow to respond, please be patient (Status 0x80)
> ATA: abnormal status 0x3F on port 0x000101f7

> Trying to resume from /dev/sda3
> Unable to access resume device (/dev/sda3)

> Any suggestions as to what I can do to try to figure out exactly what is
> causing this failure?

That "Unable to access resume device (/dev/sda3)" isn't normal, it
usually says something different IIRC.

Therefore I would guess it can't talk to your drive properly.

Recent kernels couldn't bring up a network device on one machine here,
staring at it further /proc/interrupts showed 0 interrupts associated
with that device.  Adding pci=biosirq to the kernel commandline got that
working again, so give it a try.  Press 'A' at the grub prompt and addit
on the end of the bad kernel's commandline.

-Andy


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux