Greg Steuck <[email protected]> writes: > I tried to unplug the USB hub before machine finished zzz'ing. Then I > hit the power button to wake up and: >> it was very strange. the system came up. I plugged in USB hub. Keyboard >> became operational. >> I hit enter, shell on the console responded with # >> I switched to X, then the system hung. So no backtrace.
I waited longer and didn't go to X, tried ls(1) instead, this worked. Tried top(1) and it crashed similar to the original I reported. Except unlike the other "clean" crash at address 0 this bombed out at c05e3cf3b68. OCR'd screen (https://photos.app.goo.gl/5muWRCAH1hs3d7Yd7): wskbd2 at ucc0 mux 1 wskbd2: connecting to wsdisplay uhide at uhidev4 reportid 2: input-1, output=0, feature=0 home# ls .Xdefaults.cache .cshrc . forward .Login .profile .ssh file home# top attempt to execute user address 0xc05e3cf3b68 in supervisor mode kernel: page fault trap, code=0 Stopped at 0xc05e3cf3b68: uvm_fault (0xffffffff822bc878, 0xc05e3cf3b68, 0, 1) -> e kernel: page fault trap, code=0 at db_read_bytes+0x70: movzbl 0(%rdi, %rcx, 1), %eax Stopped TID PID UID PRFLAGS PFLAGS CPU COMMAND db_read_bytes(c05e3cf3b68,1, ffff8000231531c8) at db_read_bytes+0x70 db_get_value(c05e3cf3b68,1,0) at db_get_value+0x3f db_disasm(c05e3cf3b68,0) at db_disasm+0x8b db_trap(6,0) at db_trap+xa5 db_ktrap(6,0, ffff800023153420) at db_ktrap+0x112 kerntrap(ffff800023153420) at kerntrap+0xa2 alltraps_kern_meltdown() at alltraps_kern_meltdown+0x7b c85e3cf3b68(fffffd88274af570, fffffd88274af570, ffff800000217000,4504, ffffffff81e20c64,c05e3cf3b68) at 0xc05e3cf3b68 nvme_q_complete(ffff8000000d3000, ffff80000102c000) at nvme_q_complete+8x118 nvme_intr(ffff8000000d3000) at nvme_intr+0x27 intr_handler(ffff800023153620, ffff800000211300) at intr_handler+0x6e Xintr_ioapic_edge26_untramp() at Xintr_ioapic_edge26_untramp+0x18f acpicpu_idle() at acpicpu_idle+0x11f sched_idle(ffffffff8226bff0) at sched_idle+0x280 end trace frame: 0x0, count: 1 ddb{0}>
