On Mon, 27 Sep 2010, John Baldwin wrote: > On Saturday, September 25, 2010 3:53:34 pm Anton Shterenlikht wrote: >> On amd64 r213168 I've a ral(4) CardBus >> wireless device of obscure origin. >> It is identified as >> >> db> bt >> Tracing pid 0 tid 100068 td 0xffffff0001b59440 >> kbd_enter() at kbd_enter+0x3d >> panic() at panic+0x17b >> witness_unlock() at witness_unlock+0x297 >> _mtx_unlock_flags() at _mtx_unlock_flags+0x7e >> rt2560_ioctl() at rt2560_ioctl+0xbf >> taskqueue_run() at taskqueue_run+0x63 >> taskqueue_thread_loop() at taskqueue_thread_loop+0x54 >> fork_exit() at fork_exit+0x12a >> fork_trampoline() at fork_trampoline+0xe >> --- trap 0, rip 0, rsp=0xffffff80b2d41cf0, rbp = 0 --- > > This will likely fix your panic, but I think the card is likely to still not > work: > > Index: rt2560.c > =================================================================== > --- rt2560.c (revision 212900) > +++ rt2560.c (working copy) > _at__at_ -2667,8 +2667,7 _at__at_ > RAL_WRITE(sc, RT2560_CSR1, RT2560_HOST_READY); > > if (rt2560_bbp_init(sc) != 0) { > - rt2560_stop(sc); > - RAL_UNLOCK(sc); > + rt2560_stop_locked(sc); > return; > } > John, You are right, the panic has got away, but the card doesn't seem to work. After issuing "ifconfig wlan0 up scan" I just get lots of ral0: could not read from BBP ral0: timeout waiting for BBP messages on the console. Shall I give up on this particular device? many thanks antonReceived on Wed Sep 29 2010 - 08:34:12 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:07 UTC