Wireless NICs on 7.2

[Paul B. Mahol]

On 7/2/09, Robert Hall <rjhjr0 at gmail.com> wrote:
>> And what about TX/RX signal?
>
> I don't know where to look for that. :)

It is part of scan output.

>> Could you put backtrace somewhere?
>> http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html
>
> Backtrace from crashing with a Belkin ndis:
> (kgdb) backtrace
> #0  doadump () at pcpu.h:196
> #1  0xc055bcc3 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
> #2  0xc055bece in panic (fmt=Variable "fmt" is not available.
> ) at /usr/src/sys/kern/kern_shutdown.c:574
> #3  0xc079041c in trap_fatal (frame=0xd5f9571c, eva=0) at
> /usr/src/sys/i386/i386/trap.c:939
> #4  0xc0790680 in trap_pfault (frame=0xd5f9571c, usermode=0, eva=0) at
> /usr/src/sys/i386/i386/trap.c:852
> #5  0xc0790fd9 in trap (frame=0xd5f9571c) at
> /usr/src/sys/i386/i386/trap.c:530
> #6  0xc077dbbb in calltrap () at /usr/src/sys/i386/i386/exception.s:159
> #7  0xc32b5239 in BLKWGDv7_sys_drv_data_start () from
> /boot/modules/BLKWGDv7_sys.ko
> Previous frame inner to this frame (corrupt stack?)
>
> And from a Linksys crash
> (kgdb) backtrace
> #0  doadump () at pcpu.h:196
> #1  0xc055bcc3 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
> #2  0xc055bece in panic (fmt=Variable "fmt" is not available.
> ) at /usr/src/sys/kern/kern_shutdown.c:574
> #3  0xc079041c in trap_fatal (frame=0xd600cb98, eva=382216) at
> /usr/src/sys/i386/i386/trap.c:939
> #4  0xc0790680 in trap_pfault (frame=0xd600cb98, usermode=0,
> eva=382216) at /usr/src/sys/i386/i386/trap.c:852
> #5  0xc0790fd9 in trap (frame=0xd600cb98) at
> /usr/src/sys/i386/i386/trap.c:530
> #6  0xc077dbbb in calltrap () at /usr/src/sys/i386/i386/exception.s:159
> #7  0xc329dde6 in rt61_sys_drv_data_start () from
> /boot/modules/./rt61_sys.ko
> Previous frame inner to this frame (corrupt stack?)
>
> I hope this is what you were asking for. :)
>

Does crash happens if you load them after boot?

-- 
Paul