Red Hat Bugzilla – Bug 249383
Kernel 188.8.131.52-27.fc7 can't see sata drive
Last modified: 2007-11-30 17:12:11 EST
Description of problem:
Looks like the kernel fails to initialize SATA driver at boot.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Happens when booting system.
See screen shots.
See dmesg and lspci output from working system.
Created attachment 159838 [details]
dmesg output from working system
Created attachment 159839 [details]
lspci output from working system
Created attachment 159840 [details]
Photo #1 of SATA init fail at boot
Created attachment 159841 [details]
Photo #2 of SATA init fail at boot
This is not to clear but I was in a hurry as it
disappears fairly quickly. Hopefully you will be
able to make sense from the two photos.
This bug seems to be the same as #232897 but with different chipset.
(In reply to comment #5)
> This bug seems to be the same as #232897 but with different chipset.
And probably the same as in bug 249469.
Adding the options given in comment #9 seems to have resolved the
problem for me but that doesn't change the fact that something
isn't quite right.
We probably need to go back to disabling MSI by default.
Just for curiosity. Are these problems due to the wrong MSI implementation in
kernel or due to its implementation in various devices?
(In reply to comment #8)
> Just for curiosity. Are these problems due to the wrong MSI implementation in
> kernel or due to its implementation in various devices?
MSI was broken in previous kernels but should be fixed now. There are devices
that don't work right and there are also motherboards that are broken (BIOS
updates sometimes fix those.)
I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the fedora kernel.
I am CC'ing myself to this bug and will try and assist you in resolving it if I can.
There hasn't been much activity on this bug for a while. Could you tell me if
you are still having problems with the latest kernel?
If the problem no longer exists then please close this bug or I'll do so in a
few days if there is no additional information lodged.
(In reply to comment #10)
> There hasn't been much activity on this bug for a while. Could you tell me if
> you are still having problems with the latest kernel?
It has been fixed in a later kernel.
I'm running 184.108.40.206-41.fc7 at the moment.
Thanks for the update Ian. I'm adjusting the resolution to let folks know what
worked for them.