The following reply was made to PR kern/181100; it has been noted by GNATS.
From: Julio Merino
To: bug-follo...@freebsd.org, julio+host-mastodon-j...@meroh.net
Cc:
Subject: Re: kern/181100: [bwi] Turning up bwi0 crashes / deadlocks the kernel
Date: Sun, 11 Aug 2013 12:40:56 -0400
I rebuilt a
I don't think so, but Wikipedia claims that work on 11n
started in 2002...
> On 11 August 2013 09:50, Julio Merino wrote:
>
>> bwi0: firmware rev 0x0127, patch level 0x000e
>> panic: rate 130 is basic/mcs?
>
> See, that's just odd. If it's a non-11n (MCS)
On Sun, Aug 11, 2013 at 11:03 PM, Adrian Chadd wrote:
> Try "call doadump" and see what it does.
No luck. That said "Dumping 0 MB" and didn't record anything...
--
Julio Merino / @jmmv
___
freebsd-wireless@f
On 2013-08-11 23:19 , Adrian Chadd wrote:
> Try this patch in sys/dev/bwi/ :
This is what I got:
bwi_mac_set_ackrates: i=0 (of 12); rs->rs_rates = 130
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wirele
ert_panic
_bwi_txeof
bwi_txeof_status32
bwi_intr
intr_event_execute_handlers
ithread_loop
fork_exit
fork_trampoline
(blindly typed while reading from kdb)
--
Julio Merino / @jmmv
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman
SSERT within _bwi_txeof() mentioning "ring_idx",
and that's the line triggering the panic.
(And yes, I've verified this... not with a core dump, because I cannot
get one, but by putting printfs() around the various KASSERTS that
yield this message.)
On Sat, Aug 17, 2013 at 7:03 PM, Adrian Chadd wrote:
> yes, print out ring_idx
That information is already in the panic message:
panic: ring_idx 0
Also, init_tx_ring gets called with ring_idx set from 0 to 5.
--
Julio Merino / @jmmv
___
free
