Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 452934 - System freezes when connected to wireless network
Summary: System freezes when connected to wireless network
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 9
Hardware: i386
OS: Linux
low
high
Target Milestone: ---
Assignee: John W. Linville
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-06-26 01:47 UTC by Azwan b. Amit
Modified: 2008-08-12 15:32 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-08-12 15:32:15 UTC


Attachments (Terms of Use)

Description Azwan b. Amit 2008-06-26 01:47:09 UTC
Description of problem:
System freezes when I successfully connected to wireless network. I need to do
force reboot and select previous kernel to solve this problem. My laptop is NEC
Versa S5500, Fedora 9, 
$ /sbin/lspci | grep Network
03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN
Network Connection (rev 61)

Version-Release number of selected component (if applicable):
kernel-2.6.25.6-55.fc9.i686.
iwl4965-firmware-4.44.1.20-1.noarch
NetworkManager-0.7.0-0.9.4.svn3675.fc9.i386

How reproducible:
Everytime I use the mentioned kernel version and try to connect to wireless network

Steps to Reproduce:
1. Boot up computer
2. Select a wireless network (Using Network-Manager)
3. When Network-Manager successfully connected, system goes to freeze
  
Actual results:
System freezes

Expected results:


Additional info:

Comment 1 John W. Linville 2008-06-26 13:20:36 UTC
Please try -57.fc9 or later:

   http://koji.fedoraproject.org/koji/buildinfo?buildID=52456


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