Description of problem:
BUG: warning at drivers/scsi/sata_mv.c:1919/__msleep() (Not tainted)
<f8876660> __mv_phy_reset+0xeb/0x3a7 [sata_mv] <c04c9784>
<f8877cce> mv_interrupt+0x209/0x310 [sata_mv] <c043db72>
<c043dc17> __do_IRQ+0x7c/0xd1 <c0405035> do_IRQ+0x63/0x80
<c04036f2> common_interrupt+0x1a/0x20 <c0417db3> kmap_atomic+0x75/0x7a
<c043f67e> file_read_actor+0x59/0xe0 <c043fec6>
<c044098d> __generic_file_aio_read+0x167/0x1ac <c043f625> file_read_actor+0x0/0xe0
<c0440a12> generic_file_aio_read+0x40/0x47 <c045bd3a> do_sync_read+0xc3/0xfd
<c042c17c> autoremove_wake_function+0x0/0x35 <c045bc77> do_sync_read+0x0/0xfd
<c045c671> vfs_read+0xa6/0x14e <c045c9f0> sys_read+0x41/0x67
Version-Release number of selected component (if applicable):
Linux version 2.6.17-1.2174_FC5 (firstname.lastname@example.org) (gcc
version 4.1.1 20060525 (Red Hat 4.1.1-1))
Boot with Supermicro SAT2-MV8 card installed.
Created attachment 135847 [details]
dmesg output of kernel.
There's a patch here that might make it go away:
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.
With the FC5 kernel 2.6.18-1.2200.fc5 I no longer see the BUG output. I have no
way to verify that the same conditions still exist, but it seems likely so I
guess this report can be closed...