Bug 442773 - kernel: 2.6.24.4-64 System stops at "Bringing up Interface wlan0" during boot.
Summary: kernel: 2.6.24.4-64 System stops at "Bringing up Interface wlan0" during boot.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 8
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-16 18:21 UTC by Jeffrey R. Evans
Modified: 2008-04-16 18:58 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-04-16 18:58:50 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jeffrey R. Evans 2008-04-16 18:21:50 UTC
Description of problem:
kernel: 2.6.24.4-64   System stops at "Bringing up Interface wlan0" during boot.
kernel 2.6.24.3-50 did not exhibit this issue using the same system with the
exact same configuration. 
kernel 2.6.23.1-42 does not exhibit this issue using the same system with the
exact same configuration.

Version-Release number of selected component (if applicable):
kernel: 2.6.24.4-64

How reproducible:
10 of 10 for 100% repro.

Steps to Reproduce:
1.Install Fedora 8 normally.
2.Update all packages EXCEPT the kernel 2.6.24.4-64
3.Verify system is operational after updates.
4. Reboot system and verify it is still operational.
5. Install the kernel 2.6.24.4-64 package.
6. Reboot as suggested.

Actual RESULTs:
System stops making progress during boot at the "Bringing up Interface wlan0" 
step.  The "spinner" keeps spinning.  There is no further progress on the boot.
  



Expected results:
Expect system to continue to boot as in previous kernel updates.

Additional info:
wlan0 is an Airlink 101 IEEE 802.11g PCI device of the rt61 pci variety.

Comment 1 Jeffrey R. Evans 2008-04-16 18:58:50 UTC
Installing kernel 2.6.24-4.82 from Koji resolved this issue for my system. 
Thanks John, sorry for the extra bug.


Note You need to log in before you can comment on or make changes to this bug.