I saw this first on my laptop; backtrace mentioned something about iwn(4), so after I saved the crash dump, I flippe dthe wireless switch off and tried again... and got a different (but undoubtedly related) panic, which I also saved. Then, after my build machine finished, that also got a panic (using a GENERIC kernel), so I saved that away, as well. Gory details are available at http://www.catwhisker.org/~david/FreeBSD/panic_09Apr2013/. Here's what's in there: freebeast: total 126476 -rw-r--r-- 1 david staff 44616 Apr 9 08:49:54 2013 core.txt.3 -rw-r--r-- 1 david staff 7881 Apr 7 08:04:47 2013 dmesg.boot.10.0-CURRENT -rw-r--r-- 1 david staff 491 Apr 9 08:41:09 2013 info.3 -rw-r--r-- 1 david staff 129323008 Apr 9 08:41:16 2013 vmcore.3 laptop: total 627248 -rw-r--r-- 1 david staff 45055 Apr 9 06:35:36 2013 core.txt.5 -rw-r--r-- 1 david staff 48156 Apr 9 06:35:46 2013 core.txt.6 -rw-r--r-- 1 david staff 13606 Apr 7 05:53:33 2013 dmesg.boot.10.0-CURRENT -rw-r--r-- 1 david staff 465 Oct 24 07:36:27 2012 info.5 -rw-r--r-- 1 david staff 469 Apr 9 06:31:39 2013 info.6 -rw-r--r-- 1 david staff 430333952 Oct 24 07:36:46 2012 vmcore.5 -rw-r--r-- 1 david staff 211210240 Apr 9 06:31:49 2013 vmcore.6 (I'm not too concerned about passwords being in there, since I never had a chance to even try to type one in. :-} Unfortunately, it appears that my invocation of "crashinfo" was less than useflu, even though I pointed it at the kernel(s) that had been running when the crash(es) occurred: the backtrace shown is useless. I can try to boot the build machine under the previous "head" kernel (vs. stable/9), and try that again...? AFK for a bit -- need to have laptop display replaced (unrelated). Peace, david -- David H. Wolfskill david_at_catwhisker.org Taliban: Evil men with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key.
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:36 UTC