Bug 182005
Summary: | problems and kernel oops when accessing IEEE1394 drive thru soundblaster audigy 4 pro | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ronny Bremer <rbremer> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | pfrields, stefan-r-rhbz, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-10-18 06:29:41 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 175429 |
Description
Ronny Bremer
2006-02-18 21:43:52 UTC
2.6.15-1.1826.2.10_FC5smp is quite old now, and a lot of change has happened in the scsi layer recently. Can you retry with the latest kernel? (people.redhat.com/davej/kernels/Fedora/devel has the latest one -- rawhide is currently frozen until after test3 is released) (In reply to comment #1) Yes, did that. I upgraded to the kernel 2.6.15-1.1955_FC5smp (it might not be the one you referred me to, but I will check that one out later) The kernel oops still happens, but the sbp2 module now gets loaded automatically during boot, which is an improvement :-) I will check the other kernel and post the results. Thanks! downloaded latest kernel (1969) still the same issue. anything I can get you to narrow it down? See my comments in http://marc.theaimsgroup.com/?l=linux-scsi&m=114038995826749 Stefan, your assumption was absolutely right, passing the parameters to scsi_mod will fix the kernel dump. Thank you! Please close this and I will open up a new bug report, because the hotplug system (hal) will not detect the IEEE drive being plugged in, I have to load SBP2 manually. Ron Ronny, thanks for testing and confirming that the workaround helps. We wrapped it into a patch which is now in the -mm patchset. Thereby the necessary blacklist flag is set automatically for these Initio bridges without extra scsi_mod parameters. The patch should go to Linus soon, hopefully before 2.6.16 is released. Linus' kernel has its own bug entry now: http://bugzilla.kernel.org/show_bug.cgi?id=6114 However the Fedora Core bug should of course _not_ be closed until the patch made it also downstream into Fedora Core's kernel. BTW, the Hal issue was already posted in bug 174723 . Similar bug reports were made for udev which suffers the same regression since Linux 2.6.14. Stefan, I agree. Please leave this bug open. I will constantly update to the latest kernel from Dave see when it disappears. Ron Stefan, rawhide kernels are usually running Linus' -git of the day, so as soon as it gets upstream, we should pick it up within a day. Thanks for your input on this. Linus now has a patch which lets sbp2 suppress the problematic SCSI command if an Initio bridge was detected. This should cover most Initio based devices. Al Viro suggested an actual fix for sd_mod to get rid of the corruption independently of device detection; this is not yet merged. Ok, gonna give the KOTD a try. Guys, great work, this is why I love open source :-) Thank you all. Ron Complete fix for all Initio bridges and similarly broken bridges arrived in Linus' tree now: http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=489708007785389941a89fa06aedc5ec53303c96 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. Thank you. I tested it with the latest kernel from FC5 and it works fine now. Thank you!!! |