> > On 1/14/09, Yuriy Tsibizov <Yuriy.Tsibizov_at_gfk.com> wrote: > >> > >>> On 1/14/09, Yuriy Tsibizov <Yuriy.Tsibizov_at_gfk.com> wrote: > >>> > Kip, > >>> > > >>> > this happens on fresh -CURRENT, with configuration > similar to one > >>> > described in > >>> > > >>> http://docs.freebsd.org/cgi/mid.cgi?3a142e750812080658r645dc1c > >>> 4sdd612585 > >>> > fe9ad7d6 (wpa_supplicant is main suspect in triggering this > >>> panic). No > >>> > crashdump / backtrace available. > >>> > > >>> > Somehow needlock!=0, and rnh is already locked. > >>> > > >>> > HW is Intel Atom D945GCLF2 (2core + HT enabled) + D-Link > >>> Atheros-based > >>> > card with WPA and static ip. > >> > >>> And bt is completly the same as was mine? > >> > >> I don't have backtrace -- swap was tooo small. > > > I need a full backtrace in order to fix. I have a textdumps enabled now (with default script that calls bt), will it be enough or full memory dump (for kgdb analysis) is a must? Yuriy.Received on Fri Jan 16 2009 - 09:51:11 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:40 UTC