Bug 205076
Summary: | kernel oops at make_class_name during udev initialization | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Christian Nolte <ch.nolte> | ||||
Component: | kernel | Assignee: | Dave Jones <davej> | ||||
Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 5 | CC: | pfrields, wtogami | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2006-10-21 05:52:37 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: | |||||||
Attachments: |
|
Description
Christian Nolte
2006-09-03 20:54:24 UTC
Changing to proper owner, kernel-maint. I have diffed the changelog of the current development kernel-2.6.17-1.2611.fc6 with kernel-2.6.17-1.2174_FC5 and stumbled upon the libata-device_add patch (see http://www.redhat.com/archives/fedora-cvs-commits/2006-August/msg00076.html) which I have tried today against 2.6.17-1.2174_FC5 with no success and the same oops. I will try the other PATA/SATA patches from the current development kernel. Created attachment 135920 [details]
patch against libata (2174)
I managed to get a patch together which gets kernel-2.6.17-1.2174_FC5 up running again (but don't trust on what I have done here, this is ugly!). I made a diff between libata from 2611 and 2174 and every dependent scsi-drivers. The only thing I left untouched was the irq-handling macros IRQF_SHARED and IRQF_DISABLED defined in include/linux/interrupt.h (2611). The oops during udev initialization is gone now and no strange messages can be found with dmesg, but some side effects have occured: Playing back sounds via ESD (gnome) or players using the xine backend result in a looping playback of the first second of the sound until the process is killed (mplayer has no such issues). Furthermore it is not possible to start the bluetooth service (it hangs). These problems could be related to what I have reported in bug #205479 for 2611. Referring to the original posting: putting some printk's in make_class_name() shows that kobject_name(&class_dev->kobj) returns null for the class_device which shall be removed via class_device_del(). I suppose that the problem lies somewhere in the sata_nv-driver code, but I don't know where to begin here. Some help would be appreciated. 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. This BUG has been fixed with kernel 2.6.18-1.2200.fc5 |