Created attachment 489747 [details]
'crash_startup.txt' (inside the tarball) is the startup summary produced by crash tool and 'crash_log.txt' is the output of its log subcommand.

Description of problem:

  Fedora 14 (64 bit) freezes on Dell Studio 1558 when it's 
  connected to an ad-hoc wireless network. The freezes were 
  generally found during light to moderate network usage, 
  and were somewhat random. The wireless card is that of Broadcom.


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

  Kernel: 2.6.35.11-83.fc14.x86_64
  Wireless driver: kmod-wl-5.100.82.38-1.fc14.1.x86_64


How reproducible:

  There were only two situations where a consistent pattern 
  was found and I have described in step 1 below. All other 
  occurrences were somewhat random and happened when the 
  wireless network was under use.


Steps to Reproduce:
  1. (a) Have kmod-wl installed
     (b) Connect to an existing ad-hoc wireless network using 
         gnome network manager. The system was connected to the 
         Ethernet as well.
         ( The wireless network under use was operating in 802.11b/g
           channel 11, with a 10-character WEP key and had five other 
           nodes. 
         )
     (c) Open Wireshark and tell it to sniff the eth1 interface (the 
         wireless interface shows up as eth1 rather than wlan0). The
         system would immediately freeze.

     * Note: This procedure worked only twice. Upon seeing the above
             two crashes, I removed the kmod-wl module and 
             reinstalled it, after which I could not get the machine 
             to freeze this way.
             
  2. Connect to a wireless network as mentioned in the previous 
     step and run `tcpdump -i eth1 ...` on the interface and have 
     some outgoing traffic on that machine. The system might 
     possibly freeze after sometime.

  
Actual results:
  
  The system completely freezes, with no response to keyboard or 
  mouse and no reply to ping/ssh, leaving the power button as the 
  only option. 
  
  * Upon configuring kdump, however, the system was able to 
    initiate an auto reboot after about a minute.


Expected results:
  
  The system normally would not freeze if it is not connected to 
  a wireless network.


Additional info:

  Processor: Intel(R) Core(TM) i5 M 430 @ 2.27GHz, Stepping 02
  RAM: 3.9GB
  Desktop environment: Gnome
  
  Other noteworthy software/drivers present:
    ATI Catalyst for Mobility Radeon 5470 v.012.020.000.032
    VirtualBox 4.0.4 (launches a kernel module on start-up)