I got one of these on each of my laptop and build machine; details beelow are from the build machine (which has a serial console and runs a vanilla GENERC kernel). Previous (successful) builld was r329197 (for both machines), yesterday. Copy/paste from serial console: ... da1: Serial Number 20100818841300000 da1: 40.000MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present da1: quirks=0x2<NO_6_BYTE> ugen0.3: <Dell Dell USB Entry Keyboard> at usbus0 da1: Delete methods: <NONE(*),ZERO> ukbd0 on uhub1 ukbd0: <Dell Dell USB Entry Keyboard, class 0/0, rev 1.10/1.78, addr 2> on usbus0 pass8 at umass-sim0 bus 0 scbus6 target 0 lun 2 kbd2 at ukbd0 kbd2: ukbd0, generic (0), config:0x0, flags:0x3d0000pass8: <Generic- SD/MMC 1.00> Removable Direct Access SCSI device pass8: Serial Number 20100818841300000 pass8: 40.000MB/s transfersrandom: harvesting attach, 8 bytes (4 bits) from ukbd0 da2 at umass-sim0 bus 0 scbus6 target 0 lun 2 da2: <Generic- SD/MMC 1.00> Removable Direct Access SCSI device da2: Serial Number 20100818841300000 da2: 40.000MB/s transfers da2: Attempt to query device size failed: NOT READY, Medium not present da2: quirks=0x2<NO_6_BYTE> da2: Delete methods: <NONE(*),ZERO> (probe0:umass-sim0:0:0:3): Down reving Protocol Version from 2 to 0? Fatal trap 12: page fault while in kernel mode pass9 at umass-sim0 bus 0 scbus6 target 0 lun 3 cpuid = 4; apic id = 04 fault virtual address = 0x78 pass9: <Generic- M.S./M.S.Pro/HG 1.00> Removable Direct Access SCSI device fault code = supervisor write data, page not present pass9: Serial Number 20100818841300000 ugen0.4: <Broadcom Corp BCM43142A0> at usbus0 pass9: 40.000MB/s transfersinstruction pointer = 0x20:0xffffffff80a20c87 stack pointer = 0x28:0xfffffe0000428a10 da3 at umass-sim0 bus 0 scbus6 target 0 lun 3 da3: <Generic- M.S./M.S.Pro/HG 1.00> Removable Direct Access SCSI device da3: Serial Number 20100818841300000 da3: 40.000MB/s transfers da3: Attempt to query device size failed: NOT READY, Medium not present da3: quirks=0x2<NO_6_BYTE> frame pointer = 0x28:0xfffffe0000428a30 da3: Delete methods: <NONE(*),ZERO> code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 13 (g_event) [ thread pid 13 tid 100044 ] Stopped at g_part_wither+0x37: movq $0,offset+0x40(%rdi) db> bt Tracing pid 13 tid 100044 td 0xfffff800039d2000 g_part_wither() at g_part_wither+0x37/frame 0xfffffe0000428a30 g_run_events() at g_run_events+0x344/frame 0xfffffe0000428a70 fork_exit() at fork_exit+0x84/frame 0xfffffe0000428ab0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0000428ab0 --- trap 0, rip = 0, rsp = 0, rbp = 0 --- db> (This is still using the Forth loader, FWIW.) On the laptop, I tried issuing the "panic" command (within ddb), and got a core file, but the result appears to be a 'panic: from debugger', and the stack trace doesn't reflect the above, so it's not clear to me that that was a useful thing for me to have done. Is there some poking I can do to this to shed more light? Peace, david -- David H. Wolfskill david_at_catwhisker.org The circus around that memo helps confirm that Mr. Trump is unfit for office. 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:41:14 UTC