Bug 138352

Summary: Trying to asociate to an essid causes a panic
Product: [Fedora] Fedora Reporter: Bill Peck <bpeck>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3   
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: 2005-01-29 21:55:35 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 Flags
lspci, lsmod and panic. none

Description Bill Peck 2004-11-08 15:19:18 UTC 
Description of problem:
I'm filing this here first even though its a kernel panic.  You can
move it dcbw.  I just wanted to make sure you saw it. :-)

Version-Release number of selected component (if applicable):
NetworkManager-0.3.1-3
kernel-2.6.9-1.667

How reproducible:
Everytime

Steps to Reproduce:
1. Install FC3 with a wireless card 
2. run NetworkManagerInfo
3. click on the radar sweep
4. enter in other wireless network
5. I entered in our essid at redhat
6. either the system will panic now or after you select that essid in 
   drop down menu.

I've attached lspci, lsmod, and the kernel panic.
Comment 1 Bill Peck 2004-11-08 15:20:29 UTC 
Created attachment 106285 [details]
lspci, lsmod and panic.
Comment 2 Dan Williams 2005-01-29 21:55:35 UTC 
I take it the panic doesn't happen any more with prism54?  I see it
was with the orinoco driver too, I'm kind of ignoring Orinoco bug
reports for now :)
Comment 3 Bill Peck 2005-01-31 14:51:31 UTC 
it doesn't happen with either now.  :-)