Re: Debugging kernel panic on boot.

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

 



Andy Green wrote:

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

Yes, it seems that for some reason the ATA driver isn't able to access the drive on these later kernels.

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.

Thanks for the suggestion. I tried that but still no dice. Exact same failure as before. I've also tried disabling the onboard SCSI controller (which isn't being used) in case that was interfering, but that made no difference either.

Simon.


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

  Powered by Linux