Crash with recent kernel on wireless

[John Baldwin]

On Friday 25 April 2008 08:25:14 am Vladimir Grebenschikov wrote:
> Hi
>
> Recently I've upgraded 7-STABLE: Mar 11 -> Apr 24
>
> Everything was fine until I've tried to configure wireless (ath driver,
> WPA)
> It crashes every time after interface becomes UP,
> (I've seen associated in ifconfig output before crash), but before dhcp
> finished to get IP.
>
> % cat /var/crash/info.43
> Dump header from device /dev/ad0s2b
>   Architecture: i386
>   Architecture Version: 2
>   Dump Length: 162320384B (154 MB)
>   Blocksize: 512
>   Dumptime: Fri Mar 28 17:24:32 2008
>   Hostname: vbook.fbsd.ru
>   Magic: FreeBSD Kernel Dump
>   Version String: FreeBSD 7.0-STABLE #3: Tue Mar 11 19:35:53 MSK 2008
>     root at vbook:/usr/obj/usr/src/sys/VBOOK
>   Panic String: non-maskable interrupt trap
>   Dump Parity: 3087556879
>   Bounds: 43
>   Dump Status: good
>
> kgdb does not shows match (why ?):
>
> % kgdb  /boot/kernel.bad/kernel /var/crash/vmcore.43
> [GDB will not be able to debug user-mode
> threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"]
> GNU gdb 6.1.1 [FreeBSD]
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
> are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for
> details.
> This GDB was configured as "i386-marcel-freebsd".
> (no debugging symbols found)...No struct type named linker_file.
> No struct type named linker_file.
> No struct type named linker_file.
> No struct type named linker_file.
> Attempt to extract a component of a value that is not a structure
> pointer.
> Attempt to extract a component of a value that is not a structure
> pointer.
> Attempt to extract a component of a value that is not a structure
> pointer.
> Attempt to extract a component of a value that is not a structure
> pointer.
> #0  0x00000000 in ?? ()
> (kgdb)
>
> Any ideas what to do ? Or probably some hints.

Build a kernel with debug symbols and then reproduce the crash.

-- 
John Baldwin