Hi,

Can you please work with Justin to figure out the IP of that panic inside
_bwi_txeof(), and then map it back to a line number?

I've no idea where the panic is actually triggering.

Thanks,


-adrian


On 13 August 2013 19:45, Julio Merino <ju...@meroh.net> wrote:

> On Tue, Aug 13, 2013 at 5:58 AM, Adrian Chadd <adr...@freebsd.org> wrote:
> > Hi!
> >
> > Please update to the latest -HEAD and try again.
>
> No luck. It gets a bit further now (ifconfig wlan0 up returns to the
> shell) but then panics:
>
> panic: ring_idx 0
> cpuid = 1
> KDB: stack backtrace:
> kdb_backtrace
> vpanic
> kassert_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/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Reply via email to