Bug 453298 - Freeze crash with Network Manager following kernel update
Summary: Freeze crash with Network Manager following kernel update
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 9
Hardware: athlon
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-06-29 09:00 UTC by jamesarbrown
Modified: 2009-07-14 15:52 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-07-14 15:52:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description jamesarbrown 2008-06-29 09:00:13 UTC
Description of problem:

Network Manager when connecting to wireless network causes a total freeze (inc
mouse pointer) and requires power off reboot.

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

[jamesarbrown@localhost ~]$ uname -r    <<< Working with Network Manager
2.6.25-14.fc9.x86_64
[jamesarbrown@localhost ~]$ rpm -qa |grep kernel
kernel-2.6.25.6-55.fc9.x86_64
kernel-headers-2.6.25.6-55.fc9.x86_64
kernel-2.6.25-14.fc9.x86_64
kerneloops-0.10-11.fc9.x86_64
[jamesarbrown@localhost ~]$ rpm -qa |grep Network
NetworkManager-glib-0.7.0-0.9.4.svn3675.fc9.x86_64
NetworkManager-gnome-0.7.0-0.9.4.svn3675.fc9.x86_64
NetworkManager-0.7.0-0.9.4.svn3675.fc9.x86_64
[jamesarbrown@localhost ~]$ 


How reproducible:

Install ISO DVD spin of fedora.
yum install b43-fwcutter
export FIRMWARE_INSTALL_DIR="/lib/firmware"
wget http://downloads.openwrt.org/sources/broadcom-wl-4.80.53.0.tar.bz2
tar xjf broadcom-wl-4.80.53.0.tar.bz2
cd broadcom-wl-4.80.53.0/kmod
sudo b43-fwcutter-011/b43-fwcutter -w "$FIRMWARE_INSTALL_DIR" wl_apsta.o

Laptop works on wireless ok and hotplugging eth0

Now yum update -y and on login the machine freezes. 

To get access again Login as root. Erase /home/useracc/.gnome* (to remove
wireless connection info)

Login to useracc can be accessed now. But fire up Network Manager and total freeze.

Only way to work: grub into original kernel from DVD spin.

Additional Info 

lspci = 30:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan
mini-PCI (rev 01)

Machine Hp/Compaq NX6325

Comment 1 Bug Zapper 2009-06-10 01:49:55 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Bug Zapper 2009-07-14 15:52:04 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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