On Sun, Oct 03, 2010 at 01:35:06PM -0500, eagir...@cox.net wrote: > I installed the 2 October snapshot yesterday, and after the reboot got a > panic.
You "installed"? Not "updated"? > > I booted again from the RAMdisk kernel, point to the 3 October snaphot and > ignored the hash mismatch, and panicked again. Trace and ps for each below. > -- > Ed Ahlsen-Girard > Ft. Walton Beach FL > > trace for 2 October snapshot:: > panic kernel diagnostic assertion "flags & (M_WAITOK | M_NOWAIT)" failed: \ > file "../../../../kern/kern_malloc.c" line 194 > stopped at Debugger+0x4: popl %ebp > Debugger(d08c4d72.dc17ac28,d08a370c,dc17ac28,0) at Debugger+0x4 > panic(d08a370c,d082b68e,d08ac09,d08a0fe4,c2) at panic+0x5d > __assert(d082bb8e,d08a0fe4,c2,d08ac0c09,d6d5216a) at __assrt+0x2e > malloc(1000,7f,0,0,11) at malloc+0x5e0 > end(1000,d09a93d0,30,1,1ff86) at 0xdc1928a6 > end(d1ec1180,1,2,d082a55e,ca81f) at 0xdc190e56 > lkmioctl(1c00,80044b03,dc17ae8c,3,d6d698a8,d6d52014,ca7e0,0) at \ > lkmioctl+0x48a ^ something related to loadable kernel modules > spec_ioctl(dc17ada0,d6d52014,dc17adbc,d09a4b7f000) at \ > spec_ioctl+0x8c > VOP_IOCTL(d6bdf174,80044b03,dc17ae8c,3,d667f000) at \ > VOP_IOCTL+0x42 > vn_ioctl(d6d5c948,80044b03,dc17ae8c,d6d698a8,4) at vn_ioctl+0x61 > sys_ioctl(d6d698a8,dc17af64,dc17af84,dc17afa8,d6d698a8) at \ > sys_ioctl+0x1b8 > syscall() at syscall+0x2f0 > syscall (number 0) > 0x2: > > ps for 2 October snapshot: > PID PPID PGRP UID S FLAGS WAIT COMMAND > *19708 31790 31790 0 7 0x4000 modload And there it is, you're loading a kernel module. You just voided your warranty :) > 1768 1358 1358 74 3 0x180 bpf pflogd > 1358 1 1358 0 3 0x80 netio pflogd > 14407 18189 18189 73 3 0x180 poll syslogd > 18189 1 19198 0 3 0x88 netio syslogd > 31790 1 31790 0 3 0x4080 pause sh > 13 0 0 0 3 100200 aiodoned aiodoned > 12 0 0 0 3 100200 syncer update > 11 0 0 0 3 100200 cleaner cleaner > 10 0 0 0 3 100200 reaper reaper > 9 0 0 0 3 100200 pgdaemon pagedaemon > 8 0 0 0 3 100200 bored crypto > 7 0 0 0 3 100200 pftm pfpurge > 6 0 0 0 3 100200 usbtsk usbtask > 5 0 0 0 3 100200 acpi0 acpi0 > 4 0 0 0 3 100200 bored syswq > 3 0 0 0 3 40100200 idle0 > 2 0 0 0 3 100200 kmalloc kmthread > 1 0 1 0 3 4080 wait init > 0 -1 0 0 3 80200 scheduler swapper > > trace for 3 October snapshot:: > panic kernel diagnostic assertion "flags & (M_WAITOK | M_NOWAIT)" failed: \ > file "../../../../kern/kern_malloc.c" line 194 > stopped at Debugger+0x4: popl %ebp > Debugger(d08c4c1c.dc180c28,d08a35ac,dc180c28,60) at Debugger+0x4 > panic(d08a35ac,d082b56e,d08a0aa9,d08a0e84,c2) at panic+0x5d > __assert(d082b56e,d08a0e84,c2,d08a0aa9,d6d6c8bc) at __assrt+0x2e > malloc(1000,7f,0,0,11) at malloc+0x5e0 > end(1000,d09a93d0,30,1,1ff86) at 0xdc18e8a6 > end(d1e9d180,1,2,d082a43e,ca81f) at 0xdc18ae56 > lkmioctl(1c00,80044b03,dc180e8c,3,d6d698a8,d6d5f4b8,ca7e0,0) at \ > lkmioctl+0x48a > spec_ioctl(dc180da0,d6d5f4b8,dc180dbc,d09a4b70,d6c20d04) at \ > spec_ioctl+0x8c > VOP_IOCTL(d6c20d04,80044b03,dc180e8c,3,d6d7f000) at \ > VOP_IOCTL+0x42 > vn_ioctl(d6d5c9a0,80044b03,dc180e8c,d6d698a8,4) at vn_ioctl+0x61 > sys_ioctl(d6d698a8,dc180f66,dc180f84,d1da30e8,d6d79060) at \ > sys_ioctl+0x1b8 > syscall() at syscall+0x2f0 > syscall (number 0) > 0x2: > > > PID PPID PGRP UID S FLAGS WAIT COMMAND > *13623 1270 1270 0 7 0x4000 modload > 24528 31806 31806 74 3 0x180 bpf pflogd > 31806 1 31806 0 3 0x80 netio pflogd > 12417 9937 9937 73 3 0x180 poll syslogd > 9937 1 9937 0 3 0x88 netio syslogd > 1270 1 1270 0 3 0x4080 pause sh > 13 0 0 0 3 100200 aiodoned aiodoned > 12 0 0 0 3 100200 syncer update > 11 0 0 0 3 100200 cleaner cleaner > 10 0 0 0 3 100200 reaper reaper > 9 0 0 0 3 100200 pgdaemon pagedaemon > 8 0 0 0 3 100200 bored crypto > 7 0 0 0 3 100200 pftm pfpurge > 6 0 0 0 3 100200 usbtsk usbtask > 5 0 0 0 3 100200 acpi0 acpi0 > 4 0 0 0 3 100200 bored syswq > 3 0 0 0 3 40100200 idle0 > 2 0 0 0 3 100200 kmalloc kmthread > 1 0 1 0 3 4080 wait init > 0 -1 0 0 3 80200 scheduler swapper
