#182: panic: ath0=ap + ath1=sta ==> soggy cornflakes
-----------------------------------------+----------------------------------
Reporter: John Denker <[EMAIL PROTECTED]> | Owner:
Type: defect | Status: new
Priority: major | Milestone: version 1.0.0 - first
stable release
Component: madwifi: driver | Version: trunk
Resolution: | Keywords:
-----------------------------------------+----------------------------------
Comment (by [EMAIL PROTECTED]):
1a) I copied down the stack-trace from a couple of different crashes. See
newly attached file '''crash.log''' Also, I attached upgraded versions of
the '''crashme''' script and the '''wifi-up''' script. In all cases, the
latest and greatest versions of these items can be found at
[http://www.av8n.com/computer/wifi-bugs/]
1b) I had to hand-type the stack trace. Setting up a serial console was a
complete waste of time; no crash info appeared on the serial console.
1c) Note that in the two crashes in the log there is a block of 6 lines
(beginning and ending with scan_next) that is identical in both cases.
That's probably a big hint as to the nature of the problem.
2) I observe it to crash the same with *or* without WEP turned on.
MRenzmann's previous comment mentioned bug #160, which mentions WEP, but
evidence suggests the WEP issue is a red herring.
3) I observe it to crash the same with same *or* different essids given to
the ap and sta.
4) I have reproduced the crash on another machine. One is a 300 MHz
desktop with a Proxim 8482-WD on the PCI bus, while the other is a 1800
MHz laptop with built-in 802.11 a/b/g.
6) Question: has anybody tried to reproduce this bug? It is 100%
reproducible chez moi. Am I the only person who has ever tried to
instantiate an ap and a sta on the same card? This is a documented
feature according to the wlanconfig manpage; indeed it is a prominently-
featured feature. I was hoping a few gazillion people would contact me,
either with sympathy or with success stories and workaround info.
7) If I may make a process suggestion: On a project of this size, it
helps to have a suite of regression tests. The tests get run on the
"current version" each night. This keeps down the number of new bugs, and
is particularly effective at keeping old bugs from creeping back in.
'''The examples given on the manpage would be a good place to start. They
should either work, or be documented to not work.'''
--
Ticket URL: <http://madwifi.org/ticket/182>
Madwifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
