Bug 578590

Summary: /sbin/modprobe exits with status 0x0009, hangs boot on b44 with 2.6.32.10
Product: [Fedora] Fedora Reporter: Daniel Sweet <djsweet33484>
Component: kernelAssignee: John W. Linville <linville>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: anton, benjavalero, dougsland, gansalmon, itamar, jonathan, jsaavedra.uy, kernel-maint, linville, sergio
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: kernel-2.6.32.10-94.fc12 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-04-05 14:34:40 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:

Description Daniel Sweet 2010-03-31 18:17:55 UTC
Description of problem: udev crashes when rc.sysinit loads the b44 module, and /sbin/modprobe exits with status 0x0009 on modprobe -b pci:<address of offending NIC>. Boot halts entirely when rc.sysinit reaches the "Sync waiting for storage" stage.

Version-Release number of selected component (if applicable):
2.6.32.10-90.fc12.x86_64 through 2.6.32.10-90.fc12.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install kernel-2.6.32.10-90.fc12.x86_64 with a default initramfs
2. Boot to new kernel
3.
  
Actual results:
udevd prints debugging information and boot halts after "Setting Hostname" message. More messages are printed if a udev event is triggered (for example, the RF kill switch is toggled.)

Expected results:
Continued booting.

Additional info:
The hang occurs early enough that /var/log/messages isn't opened for writing. Blacklisting the b44 module in /etc/modprobe.d/blacklist.conf and running dracut -f /boot/initramfs-2.6.32.10-90.fc12.x86_64.img 2.6.32.10-90.fc12.x86_64 from an unaffected kernel or chroot from a rescue disk will allow the system to boot normally.

Comment 1 Daniel Sweet 2010-03-31 18:45:49 UTC
It appears something similar happened to the 2.6.33 series with Bug 577463. It's still valid for 2.6.32.10.

Comment 2 Juan Saavedra 2010-04-02 13:54:30 UTC
I have the same problem after tomorrow's update.
Booting with the new 2.6.32.10-90.fc12.i686 produces the same error.
Right now I'm using the previous 2.6.32.9-70.fc12.i686 and everything is ok.

Comment 3 Sergio Basto 2010-04-02 15:10:23 UTC
(In reply to comment #2)
> I have the same problem after tomorrow's update.
> Booting with the new 2.6.32.10-90.fc12.i686 produces the same error.
> Right now I'm using the previous 2.6.32.9-70.fc12.i686 and everything is ok.    

Exactly the same here, I got a, 4 year old, b44. 
Hopefully 2.6.32.10-94.fc12.i686.PAE from koji has the fix mention on Bug 577463, which I tested and fix the bug here.

Best regards,

Comment 4 John W. Linville 2010-04-05 14:34:40 UTC

*** This bug has been marked as a duplicate of bug 578217 ***