#2042: ieee80211_unref_node: NULL ieee80211_node *
----------------------------------------+-----------------------------------
      Reporter:  [EMAIL PROTECTED]      |       Owner:  georg                
          Type:  defect                 |      Status:  assigned             
      Priority:  minor                  |   Milestone:                       
     Component:  madwifi: 802.11 stack  |     Version:  trunk                
    Resolution:                         |    Keywords:  NULL ieee80211_node *
Patch_attached:  1                      |     Pending:  0                    
----------------------------------------+-----------------------------------
Comment (by [EMAIL PROTECTED]):

 I can reproduce this problem.

 It happened to me, running Kismet.  It generated 160MB of system log
 messages, filling up my partition and eventually causing a crash.  The
 system log messages were identical to those posted above.

 I'm running the madwifi driver on an Asus EeePC 701, first generation.

 The Atheros WiFi device is PCI ID 168c:001c (rev 01), subsystem ID
 1a3b:1026

 Version of madwifi driver used: madwifi-hal-0.10.5.6-r3835-20080801

 I tried the latest SVN.  The HAL didn't like this particular Atheros chip.
 So, only this snapshot will work!  Since this is a regression, should I
 file an additional bug on this?

 During normal operation (associated with an AP), this bug does not happen.

 However, during "offline" operation (monitor mode, or otherwise), this bug
 happens all the time.  It repeats every second or so, maybe even for each
 incoming packet, I am not sure yet.

 Based on the helpful stack trace and error message printed, it was easy to
 find where they were happening in the source.  I don't understand the
 driver well enough to find the root cause of the bug.

 Here is a very rude patch.  It simply comments out the stack trace and
 error message!  It doesn't fix the underlying cause of the bug, in any
 way.

 It does work for me, though, and I was able to capture over 500K packets
 in Kismet without a hitch.  This is much better than previous versions,
 which locked up after just 1K packets or so (this was symptomatic of bug
 1904).

-- 
Ticket URL: <http://madwifi.org/ticket/2042#comment:6>
madwifi.org <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets

Reply via email to