On Monday 02 October 2006 12:48, Hendrik Sattler wrote: > Am Montag 02 Oktober 2006 11:33 schrieb Michael Buesch: > > On Monday 02 October 2006 11:20, Hendrik Sattler wrote: > > > Am Montag 02 Oktober 2006 10:43 schrieb Michael Buesch: > > > > On Sunday 01 October 2006 14:11, Hendrik Sattler wrote: > > > > > Am Dienstag 26 September 2006 16:46 schrieb Larry Finger: > > > > > > To fix as much as we can at the moment, please get the > > > > > > "patch_2.6.18_to_wireless-2.6.bz2" file from > > > > > > ftp://lwfinger.dynalias.org/patches and apply that to your kernel. > > > > > > > > > > Anything else that could be applied? I built 2.6.18 with wireless2.6 > > > > > patch yesterday and tonight, I got: > > > > > NETDEV WATCHDOG: wlan0: transmit timed out > > > > > bcm43xx: Controller RESET (TX timeout) ... > > > > > bcm43xx: Controller restarted > > > > > > > > > > I have a BCM4306. > > > > > > > > Complete logs, please. > > > > > > That's what you got, I didn't build with debug output enabled. > > > > Ah, you want us to debug the problem, but compiled > > without debug support. You see the problem? ;) > > The problem is that bcm43xx does not differ much between severity of debug > messages. > Examples: > When compiling without _debug_ messages, I do not even get information about > the detected chipset. Only: > bcm43xx driver > is pretty thin output (please replace that line with useful information). > OTOH, _compiling_ with debug messages gives me _lots_ of output all the time, > making dmesg rather useless for normal use. > How about triggering this on/off at runtime (e.g. module parameter debug or > sysfs file) with default to off? For distribution kernels, this would be > _a_lot_ better. Until the driver is sufficiently stable, just compile them in > by default. If same goes for softmac, that would be even greater. > Usually, those errors happen more than once (one-time bugs are rather hard to > fix). > Just don't assume that the user does not need dmesg output for other > purposes, > too. And having endless pages with softmac+bcm43xx lines is just that.
Hendrik, what are you trying to gain? If you want help, provide debug info. Fullstop. How do you define "sufficiently stable"? For me the driver is sufficiently stable on all of my devices. It's really simple. If you run into a bug, provide debug info. There is no need to think about "sufficiently stable" or something. -- Greetings Michael. _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
