Help understanding crash logs

BaronBS · Feb 7, 2025

Hello forum,

I had a unique crash today (never happened before).

The OS just froze and rebooted a few min latter. I was browsing with firefox open and a few others desktop apps running, nothing fancy.

Code:

doas cat /var/log/all.log
......
Feb  6 15:40:00 BattleStar-Lat5420 /usr/sbin/cron[17237]: (root) CMD (/usr/libexec/atrun)
Feb  6 15:44:00 BattleStar-Lat5420 /usr/sbin/cron[69307]: (operator) CMD (/usr/libexec/save-entropy)
Feb  6 15:45:00 BattleStar-Lat5420 /usr/sbin/cron[83532]: (root) CMD (/usr/libexec/atrun)
Feb  6 15:50:00 BattleStar-Lat5420 /usr/sbin/cron[50141]: (root) CMD (/usr/libexec/atrun)
Feb  6 15:55:00 BattleStar-Lat5420 /usr/sbin/cron[16853]: (root) CMD (/usr/libexec/atrun)
Feb  6 15:56:07 BattleStar-Lat5420 kernel: ugen0.2: <Microchip USB5806 Smart Hub> at usbus0 (disconnected)
Feb  6 15:56:07 BattleStar-Lat5420 kernel: uhub2: at uhub1, port 2, addr 1 (disconnected)
Feb  6 15:56:07 BattleStar-Lat5420 kernel: ugen0.3: <Realtek USB 10/100/1000 LAN> at usbus0 (disconnected)
Feb  6 15:56:07 BattleStar-Lat5420 kernel: ure0: at uhub2, port 3, addr 2 (disconnected)
Feb  6 15:56:07 BattleStar-Lat5420 kernel: rgephy0: detached
Feb  6 15:56:07 BattleStar-Lat5420 kernel: miibus0: detached
Feb  6 15:56:07 BattleStar-Lat5420 kernel: ure0: detached
Feb  6 15:59:15 BattleStar-Lat5420 syslogd: restart
Feb  6 15:59:15 BattleStar-Lat5420 syslogd: kernel boot file is /boot/kernel/kernel
Feb  6 15:59:15 BattleStar-Lat5420 kernel:
Feb  6 15:59:15 BattleStar-Lat5420 syslogd: last message repeated 1 times
Feb  6 15:59:15 BattleStar-Lat5420 kernel: Fatal trap 12: page fault while in kernel mode
Feb  6 15:59:15 BattleStar-Lat5420 kernel: cpuid = 4; apic id = 04
Feb  6 15:59:15 BattleStar-Lat5420 kernel: fault virtual address        = 0x458
Feb  6 15:59:15 BattleStar-Lat5420 kernel: fault code           = supervisor read data, page not present
Feb  6 15:59:15 BattleStar-Lat5420 kernel: instruction pointer  = 0x20:0xffffffff80b1ac29
Feb  6 15:59:15 BattleStar-Lat5420 kernel: stack pointer                = 0x28:0xfffffe0170f03760
Feb  6 15:59:15 BattleStar-Lat5420 kernel: frame pointer                = 0x28:0xfffffe0170f037e0
Feb  6 15:59:15 BattleStar-Lat5420 kernel: code segment         = base 0x0, limit 0xfffff, type 0x1b
Feb  6 15:59:15 BattleStar-Lat5420 kernel:                      = DPL 0, pres 1, long 1, def32 0, gran 1
Feb  6 15:59:15 BattleStar-Lat5420 kernel: processor eflags     = interrupt enabled, resume, IOPL = 0
Feb  6 15:59:15 BattleStar-Lat5420 kernel: current process              = 0 (netlink_socket (PID)
Feb  6 15:59:15 BattleStar-Lat5420 kernel: rdi: fffff8000b6882e0 rsi: 0000000000000004 rdx: 0000000000000000
Feb  6 15:59:15 BattleStar-Lat5420 kernel: rcx: 0000000000000001  r8: fffff803865ac520  r9: fffffe0170f04000
Feb  6 15:59:15 BattleStar-Lat5420 kernel: rax: 0000000000000000 rbx: 0000000000000012 rbp: fffffe0170f037e0
Feb  6 15:59:15 BattleStar-Lat5420 kernel: r10: 0000000000001388 r11: 0000000082d39ec6 r12: 0000000000000000
Feb  6 15:59:15 BattleStar-Lat5420 kernel: r13: fffff803865ac000 r14: fffffe0170f03788 r15: fffff8000b6882e0
Feb  6 15:59:15 BattleStar-Lat5420 kernel: trap number          = 12
Feb  6 15:59:15 BattleStar-Lat5420 kernel: panic: page fault
Feb  6 15:59:15 BattleStar-Lat5420 kernel: cpuid = 4
Feb  6 15:59:15 BattleStar-Lat5420 kernel: time = 1738853767
Feb  6 15:59:15 BattleStar-Lat5420 kernel: KDB: stack backtrace:
Feb  6 15:59:15 BattleStar-Lat5420 kernel: #0 0xffffffff80b8d13d at kdb_backtrace+0x5d
Feb  6 15:59:15 BattleStar-Lat5420 kernel: #1 0xffffffff80b3ef01 at vpanic+0x161
Feb  6 15:59:15 BattleStar-Lat5420 kernel: #2 0xffffffff80b3ed93 at panic+0x43
Feb  6 15:59:15 BattleStar-Lat5420 kernel: #3 0xffffffff8102cb1f at trap_pfault+0x3af
Feb  6 15:59:15 BattleStar-Lat5420 kernel: #4 0xffffffff81003748 at calltrap+0x8
Feb  6 15:59:15 BattleStar-Lat5420 kernel: #5 0xffffffff8094e778 at usbd_do_request_flags+0x8a8
Feb  6 15:59:15 BattleStar-Lat5420 kernel: #6 0xffffffff8094e85e at usbd_do_request_proc+0x5e
Feb  6 15:59:15 BattleStar-Lat5420 kernel: #7 0xffffffff849cf4b5 at ure_miibus_readreg+0xb5
Feb  6 15:59:15 BattleStar-Lat5420 kernel: #8 0xffffffff806e8cd3 at rgephy_linkup+0xc3
Feb  6 15:59:15 BattleStar-Lat5420 kernel: #9 0xffffffff806e8248 at rgephy_status+0x28
Feb  6 15:59:15 BattleStar-Lat5420 kernel: #10 0xffffffff806e81d3 at rgephy_service+0x323
Feb  6 15:59:15 BattleStar-Lat5420 kernel: #11 0xffffffff806e4177 at mii_pollstat+0x57
Feb  6 15:59:15 BattleStar-Lat5420 kernel: #12 0xffffffff849d4924 at ure_ifmedia_sts+0x184
Feb  6 15:59:15 BattleStar-Lat5420 kernel: #13 0xffffffff80c6e406 at ifmedia_ioctl+0x176
Feb  6 15:59:15 BattleStar-Lat5420 kernel: #14 0xffffffff80d8c735 at dump_iface+0x145
Feb  6 15:59:15 BattleStar-Lat5420 kernel: #15 0xffffffff80d8ed1c at dump_cb+0x1c
Feb  6 15:59:15 BattleStar-Lat5420 kernel: #16 0xffffffff80c65077 at if_foreach_sleep+0x227
Feb  6 15:59:15 BattleStar-Lat5420 kernel: #17 0xffffffff80d8dc0d at rtnl_handle_getlink+0x24d
Feb  6 15:59:15 BattleStar-Lat5420 kernel: Uptime: 13h20m34s
Feb  6 15:59:15 BattleStar-Lat5420 kernel: Dumping 4888 out of 32272 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%
Feb  6 15:59:15 BattleStar-Lat5420 kernel: Dump complete
Feb  6 15:59:15 BattleStar-Lat5420 kernel: Automatic reboot in 15 seconds - press a key on the console to abort
Feb  6 15:59:15 BattleStar-Lat5420 kernel: ---<<BOOT>>---
Feb  6 15:59:15 BattleStar-Lat5420 kernel: Copyright (c) 1992-2023 The FreeBSD Project.
Feb  6 15:59:15 BattleStar-Lat5420 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Feb  6 15:59:15 BattleStar-Lat5420 kernel:      The Regents of the University of California. All rights reserved.
Feb  6 15:59:15 BattleStar-Lat5420 kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
Feb  6 15:59:15 BattleStar-Lat5420 kernel: FreeBSD 14.2-STABLE stable/14-n270273-3d30774f0056 GENERIC amd64
Feb  6 15:59:15 BattleStar-Lat5420 kernel: FreeBSD clang version 19.1.7 (https://github.com/llvm/llvm-project.git llvmorg-19.1.7-0-gcd708029e0b2)
.......

What do I need to look for here?

atax1a · Feb 7, 2025

walking the stack trace backwards, it panicked when frame 5, usbd_do_request_flags took a page fault in kernel mode. going further up, frame 8 says rgephy_linkup and frame 12 says ure_ifmedia_sts, implicating the ure(4) driver. Ergo, you likely have a problem with your USB ethernet device. We'd start looking there, and also check memory, just to be sure.

BaronBS · Feb 7, 2025

atax1a said:
walking the stack trace backwards, it panicked when frame 5, usbd_do_request_flags took a page fault in kernel mode. going further up, frame 8 says rgephy_linkup and frame 12 says ure_ifmedia_sts, implicating the ure(4) driver.

Can you elaborate on how did you arrived on that conclusion?

atax1a said:
Ergo, you likely have a problem with your USB ethernet device. We'd start looking there,

Like a usb dongle? If so, I don't have one.

atax1a said:
and also check memory, just to be sure.

How?

atax1a · Feb 7, 2025

BaronBS said:
Can you elaborate on how did you arrived on that conclusion?

Reading the stack trace from the logs you posted, which forms a record of function calls that lead to the panic. the function names mention ure twice. here's the logs with running commentary.

Code:

kernel: #0 0xffffffff80b8d13d at kdb_backtrace+0x5d            We are here, printing the backtrace.
kernel: #1 0xffffffff80b3ef01 at vpanic+0x161                  Internals of panic
kernel: #2 0xffffffff80b3ed93 at panic+0x43                    panic!  the next call is what decided to panic
kernel: #3 0xffffffff8102cb1f at trap_pfault+0x3af             This is the page fault handler.
kernel: #4 0xffffffff81003748 at calltrap+0x8                  This is some kind of internal handler.
kernel: #5 0xffffffff8094e778 at usbd_do_request_flags+0x8a8   Here, we are processing a USB request
kernel: #6 0xffffffff8094e85e at usbd_do_request_proc+0x5e     Same here
kernel: #7 0xffffffff849cf4b5 at ure_miibus_readreg+0xb5       Trying to read from a `ure`
kernel: #8 0xffffffff806e8cd3 at rgephy_linkup+0xc3            while taking a link up, probably.
kernel: #9 0xffffffff806e8248 at rgephy_status+0x28            ...
kernel: #10 0xffffffff806e81d3 at rgephy_service+0x323         ...
kernel: #11 0xffffffff806e4177 at mii_pollstat+0x57            ...
kernel: #12 0xffffffff849d4924 at ure_ifmedia_sts+0x184        here's `ure` again, this time involved in a media query
kernel: #13 0xffffffff80c6e406 at ifmedia_ioctl+0x176          as called via ioctl()
kernel: #14 0xffffffff80d8c735 at dump_iface+0x145             and the rest of this just looks like a story of how we got here
kernel: #15 0xffffffff80d8ed1c at dump_cb+0x1c
kernel: #16 0xffffffff80c65077 at if_foreach_sleep+0x227
kernel: #17 0xffffffff80d8dc0d at rtnl_handle_getlink+0x24d

dunno what to say about not having a ure device, because that stack trace is visibly in the middle of trying to talk to some kind of USB device. the immediate prior logs also say that a USB hub and a ure device just detached.

As far as doing memory tests, we'd download the "Linux iso" from https://memtest.org and dd it onto a flash drive, reboot to it, and let it run at least one pass.

BaronBS · Feb 7, 2025

atax1a said:
dunno what to say about not having a ure device, because that stack trace is visibly in the middle of trying to talk to some kind of USB device. the immediate prior logs also say that a USB hub and a ure device just detached.

Can USB mean something internal? because the only thing connected via usb is a nvme external storage device, it is a laptop, I don't need a usb ethernet dongle. wtf

atax1a said:
As far as doing memory tests, we'd download the "Linux iso" from https://memtest.org and dd it onto a flash drive, reboot to it, and let it run at least one pass.

Will do it.

And thank you very much for the commented log, it really helped me.

ralphbsz · Feb 7, 2025

BaronBS said:
Can USB mean something internal?

Absolutely could. Run some commands to diagnose what USB hardware you have, for example usbconfig.

On "big" computers, USB-connected built in Ethernet ports seem unusual, but on small ones (like Raspberry Pi class) they are common. In between, for example NUCs, I don't know.

atax1a · Feb 7, 2025

yeah, if you haven't plugged one in, it's likely that your motherboard ethernet device is the ure.

BaronBS said:
kernel: ugen0.2: <Microchip USB5806 Smart Hub> at usbus0 (disconnected)
kernel: uhub2: at uhub1, port 2, addr 1 (disconnected)
kernel: ugen0.3: <Realtek USB 10/100/1000 LAN> at usbus0 (disconnected)
kernel: ure0: at uhub2, port 3, addr 2 (disconnected)
kernel: rgephy0: detached
kernel: miibus0: detached
kernel: ure0: detached

on the one hand, your hub and ethernet device shouldn't be falling off the bus, but their reattachment also shouldn't panic the system.

ralphbsz · Feb 7, 2025

atax1a said:
... but their reattachment also shouldn't panic the system.

I think this bears repeating: A kernel panic is always either a hardware fault (typically a memory problem), or a bug in the kernel. If both hardware and OS were perfect, a user would not be able to cause a panic. Alas ...

fmc000 · Feb 7, 2025

Feb 6 15:59:15 BattleStar-Lat5420 kernel: #17 0xffffffff80d8dc0d at rtnl_handle_getlink+0x24d

Did you have a link flap or something?

BaronBS · Feb 7, 2025

ralphbsz said:
Absolutely could. Run some commands to diagnose what USB hardware you have, for example usbconfig.

On "big" computers, USB-connected built in Ethernet ports seem unusual, but on small ones (like Raspberry Pi class) they are common. In between, for example NUCs, I don't know.

atax1a said:
yeah, if you haven't plugged one in, it's likely that your motherboard ethernet device is the ure.

on the one hand, your hub and ethernet device shouldn't be falling off the bus, but their reattachment also shouldn't panic the system.

More context:

Code:

beastie@BattleStar-Lat5420 --> ~
Ψ doas lsusb                                                                                                                                                                                                                                 < 5:37 >  < 11,725-02-07 >  < 0 > 
Bus /dev/usb Device /dev/ugen1.6: ID 8087:0026 Intel Corp. AX201 Bluetooth
Bus /dev/usb Device /dev/ugen1.5: ID 1bcf:28c4 Sunplus Innovation Technology Inc. 
Bus /dev/usb Device /dev/ugen1.4: ID 0bda:9210 Realtek Semiconductor Corp. RTL9210 M.2 NVME Adapter
Bus /dev/usb Device /dev/ugen1.3: ID 0424:284c Microchip Technology, Inc. (formerly SMSC) 
Bus /dev/usb Device /dev/ugen0.3: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter
Bus /dev/usb Device /dev/ugen1.2: ID 0424:2806 Microchip Technology, Inc. (formerly SMSC) 
Bus /dev/usb Device /dev/ugen0.2: ID 0424:5806 Microchip Technology, Inc. (formerly SMSC) 
Bus /dev/usb Device /dev/ugen0.1: ID 0000:0000  
Bus /dev/usb Device /dev/ugen1.1: ID 0000:0000

I didn't now that realtek also make disk adapters.
According ure(4), it handles 0.3 but not 1.4. I don't know how that help, but there it is.

ure – RealTek RTL8152/RTL8153/RTL8153B/RTL8156/RTL8156B USB to Ethernet
controller driver

cracauer@ · Feb 7, 2025

A M.2 NVMe connected via USB built into a laptop?

ralphbsz · Feb 7, 2025

Interesting design, putting both ethernet and NVME on the USB bus. I guess the power and space savings justify it.

tingo · Feb 7, 2025

cracauer@ said:
A M.2 NVMe connected via USB built into a laptop?

Yes. Usually cheap ones.

Phishfry · Feb 8, 2025

ralphbsz said:
putting both ethernet and NVME on the USB bus.

Does this laptop have an ARM processor?

BaronBS · Feb 8, 2025

cracauer@ said:
A M.2 NVMe connected via USB built into a laptop?

IDK if I'm reading this correctly. But I do have a external case with a internal nvme inside connected to the note via usb as a external drive.

Also, it happened again:

Code:

doas cat /var/log/all.log
........
Feb  8 14:10:00 BattleStar-Lat5420 /usr/sbin/cron[6626]: (root) CMD (/usr/libexec/atrun)
Feb  8 14:11:00 BattleStar-Lat5420 /usr/sbin/cron[26922]: (operator) CMD (/usr/libexec/save-entropy)
Feb  8 14:15:00 BattleStar-Lat5420 /usr/sbin/cron[95889]: (root) CMD (/usr/libexec/atrun)
Feb  8 14:20:00 BattleStar-Lat5420 /usr/sbin/cron[84357]: (root) CMD (/usr/libexec/atrun)
Feb  8 14:20:13 BattleStar-Lat5420 kernel: ugen0.2: <Microchip USB5806 Smart Hub> at usbus0 (disconnected)
Feb  8 14:20:13 BattleStar-Lat5420 kernel: uhub2: at uhub1, port 2, addr 1 (disconnected)
Feb  8 14:20:13 BattleStar-Lat5420 kernel: ugen0.3: <Realtek USB 10/100/1000 LAN> at usbus0 (disconnected)
Feb  8 14:20:13 BattleStar-Lat5420 kernel: ure0: at uhub2, port 3, addr 2 (disconnected)
Feb  8 14:20:13 BattleStar-Lat5420 kernel: rgephy0: detached
Feb  8 14:20:13 BattleStar-Lat5420 kernel: miibus0: detached
Feb  8 14:20:13 BattleStar-Lat5420 kernel: ure0: detached
Feb  8 14:20:13 BattleStar-Lat5420 kernel: uhub2: detached
Feb  8 14:23:34 BattleStar-Lat5420 syslogd: restart
Feb  8 14:23:34 BattleStar-Lat5420 syslogd: kernel boot file is /boot/kernel/kernel
Feb  8 14:23:34 BattleStar-Lat5420 kernel:
Feb  8 14:23:34 BattleStar-Lat5420 syslogd: last message repeated 1 times
Feb  8 14:23:34 BattleStar-Lat5420 kernel: Fatal trap 12: page fault while in kernel mode
Feb  8 14:23:34 BattleStar-Lat5420 kernel: cpuid = 0; apic id = 00
Feb  8 14:23:34 BattleStar-Lat5420 kernel: fault virtual address        = 0x458
Feb  8 14:23:34 BattleStar-Lat5420 kernel: fault code           = supervisor read data, page not present
Feb  8 14:23:34 BattleStar-Lat5420 kernel: instruction pointer  = 0x20:0xffffffff80b1ac29
Feb  8 14:23:34 BattleStar-Lat5420 kernel: stack pointer                = 0x28:0xfffffe01cca6d760
Feb  8 14:23:34 BattleStar-Lat5420 kernel: frame pointer                = 0x28:0xfffffe01cca6d7e0
Feb  8 14:23:34 BattleStar-Lat5420 kernel: code segment         = base 0x0, limit 0xfffff, type 0x1b
Feb  8 14:23:34 BattleStar-Lat5420 kernel:                      = DPL 0, pres 1, long 1, def32 0, gran 1
Feb  8 14:23:34 BattleStar-Lat5420 kernel: processor eflags     = interrupt enabled, resume, IOPL = 0
Feb  8 14:23:34 BattleStar-Lat5420 kernel: current process              = 0 (netlink_socket (PID)
Feb  8 14:23:34 BattleStar-Lat5420 kernel: rdi: fffff8003541e6e0 rsi: 0000000000000004 rdx: 0000000000000000
Feb  8 14:23:34 BattleStar-Lat5420 kernel: rcx: 0000000000000001  r8: fffff80227ff2c60  r9: fffffe01cca6e000
Feb  8 14:23:34 BattleStar-Lat5420 kernel: rax: 0000000000000000 rbx: 0000000000000012 rbp: fffffe01cca6d7e0
Feb  8 14:23:34 BattleStar-Lat5420 kernel: r10: 0000000000001388 r11: 0000000089e934a7 r12: 0000000000000000
Feb  8 14:23:34 BattleStar-Lat5420 kernel: r13: fffff80227ff2740 r14: fffffe01cca6d788 r15: fffff8003541e6e0
Feb  8 14:23:34 BattleStar-Lat5420 kernel: trap number          = 12
Feb  8 14:23:34 BattleStar-Lat5420 kernel: panic: page fault
Feb  8 14:23:34 BattleStar-Lat5420 kernel: cpuid = 0
Feb  8 14:23:34 BattleStar-Lat5420 kernel: time = 1739020813
Feb  8 14:23:34 BattleStar-Lat5420 kernel: KDB: stack backtrace:
Feb  8 14:23:34 BattleStar-Lat5420 kernel: #0 0xffffffff80b8d13d at kdb_backtrace+0x5d
Feb  8 14:23:34 BattleStar-Lat5420 kernel: #1 0xffffffff80b3ef01 at vpanic+0x161
Feb  8 14:23:34 BattleStar-Lat5420 kernel: #2 0xffffffff80b3ed93 at panic+0x43
Feb  8 14:23:34 BattleStar-Lat5420 kernel: #3 0xffffffff8102cb1f at trap_pfault+0x3af
Feb  8 14:23:34 BattleStar-Lat5420 kernel: #4 0xffffffff81003748 at calltrap+0x8
Feb  8 14:23:34 BattleStar-Lat5420 kernel: #5 0xffffffff8094e778 at usbd_do_request_flags+0x8a8
Feb  8 14:23:34 BattleStar-Lat5420 kernel: #6 0xffffffff8094e85e at usbd_do_request_proc+0x5e
Feb  8 14:23:34 BattleStar-Lat5420 kernel: #7 0xffffffff849cf4b5 at ure_miibus_readreg+0xb5
Feb  8 14:23:34 BattleStar-Lat5420 kernel: #8 0xffffffff806e8cd3 at rgephy_linkup+0xc3
Feb  8 14:23:34 BattleStar-Lat5420 kernel: #9 0xffffffff806e8248 at rgephy_status+0x28
Feb  8 14:23:34 BattleStar-Lat5420 kernel: #10 0xffffffff806e81d3 at rgephy_service+0x323
Feb  8 14:23:34 BattleStar-Lat5420 kernel: #11 0xffffffff806e4177 at mii_pollstat+0x57
Feb  8 14:23:34 BattleStar-Lat5420 kernel: #12 0xffffffff849d4924 at ure_ifmedia_sts+0x184
Feb  8 14:23:34 BattleStar-Lat5420 kernel: #13 0xffffffff80c6e406 at ifmedia_ioctl+0x176
Feb  8 14:23:34 BattleStar-Lat5420 kernel: #14 0xffffffff80d8c735 at dump_iface+0x145
Feb  8 14:23:34 BattleStar-Lat5420 kernel: #15 0xffffffff80d8ed1c at dump_cb+0x1c
Feb  8 14:23:34 BattleStar-Lat5420 kernel: #16 0xffffffff80c65077 at if_foreach_sleep+0x227
Feb  8 14:23:34 BattleStar-Lat5420 kernel: #17 0xffffffff80d8dc0d at rtnl_handle_getlink+0x24d
Feb  8 14:23:34 BattleStar-Lat5420 kernel: Uptime: 1d22h21m29s
Feb  8 14:23:34 BattleStar-Lat5420 kernel: Dumping 5436 out of 32272 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%
Feb  8 14:23:34 BattleStar-Lat5420 kernel: Dump complete
Feb  8 14:23:34 BattleStar-Lat5420 kernel: Automatic reboot in 15 seconds - press a key on the console to abort
Feb  8 14:23:34 BattleStar-Lat5420 kernel: ---<<BOOT>>---
Feb  8 14:23:34 BattleStar-Lat5420 kernel: Copyright (c) 1992-2023 The FreeBSD Project.
Feb  8 14:23:34 BattleStar-Lat5420 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Feb  8 14:23:34 BattleStar-Lat5420 kernel:      The Regents of the University of California. All rights reserved.
.....

It wasn't happening last week before I upgrade my system, gonna upgrade again to see if changes anything.

Code:

beastie@BattleStar-Lat5420 --> ~
Ψ uname -a                                                                                                                                                                                                                                < 14:31 >  < 11,725-02-08 >  < 130 >
FreeBSD BattleStar-Lat5420.chaos.org 14.2-STABLE FreeBSD 14.2-STABLE stable/14-n270273-3d30774f0056 GENERIC amd64

Edit: More context, the notebook is a Dell Latitude 5420:

Code:

beastie@BattleStar-Lat5420 --> ~
Ψ fastfetch                                                                                                                                                                                                                                 < 14:33 >  < 11,725-02-08 >  < 0 >
```                        `        beastie@BattleStar-Lat5420
  ` `.....---.......--.```   -/     --------------------------
  +o   .--`         /y:`      +.    Host: Latitude 5420
   yo`:.            :o      `+-     Kernel: FreeBSD 14.2-STABLE
    y/               -/`   -o/      Uptime: 10 mins
   .-                  ::/sy+:.     Packages: 1241 (pkg)
   /                     `--  /     Shell: zsh 5.9
  `:                          :`    Display (LGD068F): 1920x1080 @ 60 Hz in 14" [Built-in] *
  `:                          :`    Display (DELL P2422HE): 1920x1080 @ 60 Hz in 24" [External]
   /                          /     DE: LXQt 2.1.0
   .-                        -.     WM: Openbox (X11)
    --                      -.      Theme: KvRoughDarkGlassRed [Qt], Flat-Remix-GTK-Red-Darkest [GTK2/3]
     `:`                  `:`       Icons: Acid [Qt], Acid [GTK2/3]
       .--             `--.         Font: Hack Nerd Font (11pt) [Qt], Hack Nerd Font (11pt) [GTK2/3]
          .---.....----.            Cursor: redglass (32px)
                                    Terminal: qterminal 2.1.0
                                    Terminal Font: Hack Nerd Font (11pt)
                                    CPU: 11th Gen Intel(R) Core(TM) i7-1185G7 (8) @ 4.80 GHz
                                    GPU: Intel Iris Xe Graphics [Integrated]
                                    Memory: 6.28 GiB / 31.52 GiB (20%)
                                    Swap: 0 B / 35.00 GiB (0%)
                                    Disk (/): 40.64 GiB / 769.03 GiB (5%) - zfs
                                    Disk (/EXM2): 96.00 KiB / 167.60 GiB (0%) - zfs
                                    Disk (/boot/efi): 1.33 MiB / 259.91 MiB (1%) - msdosfs
                                    Disk (/media/exm2): 63.03 GiB / 230.62 GiB (27%) - zfs
                                    Disk (/zroot): 96.00 KiB / 728.39 GiB (0%) - zfs
                                    Local IP (wlan0): 192.168.1.149/24
                                    Battery (DELL R89GC13): 100% [AC Connected]
                                    Locale: C.UTF-8

                                                          
                                                          
beastie@BattleStar-Lat5420 --> ~
Ψ

Edit2: I disconnected the external "internal nvme" and now it is gone from the usb list, but IDK how this is relevant, bc the drive in question is not supposed to handle this hardware.

Code:

beastie@BattleStar-Lat5420 --> ~
Ψ doas lsusb                                                                                                                                                                                                                                < 14:40 >  < 11,725-02-08 >  < 0 >
Bus /dev/usb Device /dev/ugen1.6: ID 8087:0026 Intel Corp. AX201 Bluetooth
Bus /dev/usb Device /dev/ugen1.5: ID 1bcf:28c4 Sunplus Innovation Technology Inc.
Bus /dev/usb Device /dev/ugen1.3: ID 0424:284c Microchip Technology, Inc. (formerly SMSC)
Bus /dev/usb Device /dev/ugen0.3: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter
Bus /dev/usb Device /dev/ugen1.2: ID 0424:2806 Microchip Technology, Inc. (formerly SMSC)
Bus /dev/usb Device /dev/ugen0.2: ID 0424:5806 Microchip Technology, Inc. (formerly SMSC)
Bus /dev/usb Device /dev/ugen0.1: ID 0000:0000 
Bus /dev/usb Device /dev/ugen1.1: ID 0000:0000

tingo · Feb 8, 2025

Be sure you have updated all the relevant kernel modules (you know, the ones in kld_list= in /etc/rc.conf). If you are on pkg's quarterly branch, this might involve compiling from source.

BaronBS · Feb 17, 2025

Upgrade didn't help, It happened again today:

Code:

beastie@BattleStar-Lat5420 --> ~
Ψ doas cat /var/log/all.log
...
Feb 17 14:50:00 BattleStar-Lat5420 /usr/sbin/cron[53141]: (root) CMD (/usr/libexec/atrun)
Feb 17 14:55:00 BattleStar-Lat5420 /usr/sbin/cron[16347]: (root) CMD (/usr/libexec/atrun)
Feb 17 14:55:00 BattleStar-Lat5420 /usr/sbin/cron[15823]: (operator) CMD (/usr/libexec/save-entropy)
Feb 17 15:00:00 BattleStar-Lat5420 /usr/sbin/cron[77061]: (root) CMD (newsyslog)
Feb 17 15:00:00 BattleStar-Lat5420 /usr/sbin/cron[77070]: (operator) CMD (/usr/libexec/save-entropy)
Feb 17 15:00:23 BattleStar-Lat5420 kernel: ugen0.2: <Microchip USB5806 Smart Hub> at usbus0 (disconnected)
Feb 17 15:00:23 BattleStar-Lat5420 kernel: uhub2: at uhub1, port 2, addr 1 (disconnected)
Feb 17 15:00:23 BattleStar-Lat5420 kernel: ugen0.3: <Realtek USB 10/100/1000 LAN> at usbus0 (disconnected)
Feb 17 15:00:23 BattleStar-Lat5420 kernel: ure0: at uhub2, port 3, addr 2 (disconnected)
Feb 17 15:00:23 BattleStar-Lat5420 kernel: rgephy0: detached
Feb 17 15:00:23 BattleStar-Lat5420 kernel: miibus0: detached
Feb 17 15:00:23 BattleStar-Lat5420 kernel: ure0: detached
Feb 17 15:00:23 BattleStar-Lat5420 kernel: uhub2: detached
Feb 17 15:04:14 BattleStar-Lat5420 syslogd: restart
Feb 17 15:04:14 BattleStar-Lat5420 syslogd: kernel boot file is /boot/kernel/kernel
Feb 17 15:04:14 BattleStar-Lat5420 kernel: 
Feb 17 15:04:14 BattleStar-Lat5420 syslogd: last message repeated 1 times
Feb 17 15:04:14 BattleStar-Lat5420 kernel: Fatal trap 12: page fault while in kernel mode
Feb 17 15:04:14 BattleStar-Lat5420 kernel: cpuid = 6; apic id = 06
Feb 17 15:04:14 BattleStar-Lat5420 kernel: fault virtual address        = 0x458
Feb 17 15:04:14 BattleStar-Lat5420 kernel: fault code           = supervisor read data, page not present
Feb 17 15:04:14 BattleStar-Lat5420 kernel: instruction pointer  = 0x20:0xffffffff80b1ad59
Feb 17 15:04:14 BattleStar-Lat5420 kernel: stack pointer                = 0x28:0xfffffe016dea1760
Feb 17 15:04:14 BattleStar-Lat5420 kernel: frame pointer                = 0x28:0xfffffe016dea17e0
Feb 17 15:04:14 BattleStar-Lat5420 kernel: code segment         = base 0x0, limit 0xfffff, type 0x1b
Feb 17 15:04:14 BattleStar-Lat5420 kernel:                      = DPL 0, pres 1, long 1, def32 0, gran 1
Feb 17 15:04:14 BattleStar-Lat5420 kernel: processor eflags     = interrupt enabled, resume, IOPL = 0
Feb 17 15:04:14 BattleStar-Lat5420 kernel: current process              = 0 (netlink_socket (PID)
Feb 17 15:04:14 BattleStar-Lat5420 kernel: rdi: fffff80001b8cee0 rsi: 0000000000000004 rdx: 0000000000000000
Feb 17 15:04:14 BattleStar-Lat5420 kernel: rcx: 0000000000000001  r8: fffff807a87cb520  r9: fffffe016dea2000
Feb 17 15:04:14 BattleStar-Lat5420 kernel: rax: 0000000000000000 rbx: 0000000000000012 rbp: fffffe016dea17e0
Feb 17 15:04:14 BattleStar-Lat5420 kernel: r10: 0000000000001388 r11: 000000008a63189c r12: 0000000000000000
Feb 17 15:04:14 BattleStar-Lat5420 kernel: r13: fffff807a87cb000 r14: fffffe016dea1788 r15: fffff80001b8cee0
Feb 17 15:04:14 BattleStar-Lat5420 kernel: trap number          = 12
Feb 17 15:04:14 BattleStar-Lat5420 kernel: panic: page fault
Feb 17 15:04:14 BattleStar-Lat5420 kernel: cpuid = 6
Feb 17 15:04:14 BattleStar-Lat5420 kernel: time = 1739800823
Feb 17 15:04:14 BattleStar-Lat5420 kernel: KDB: stack backtrace:
Feb 17 15:04:14 BattleStar-Lat5420 kernel: #0 0xffffffff80b8d2ad at kdb_backtrace+0x5d
Feb 17 15:04:14 BattleStar-Lat5420 kernel: #1 0xffffffff80b3f031 at vpanic+0x161
Feb 17 15:04:14 BattleStar-Lat5420 kernel: #2 0xffffffff80b3eec3 at panic+0x43
Feb 17 15:04:14 BattleStar-Lat5420 kernel: #3 0xffffffff8102db1f at trap_pfault+0x3af
Feb 17 15:04:14 BattleStar-Lat5420 kernel: #4 0xffffffff81003de8 at calltrap+0x8
Feb 17 15:04:14 BattleStar-Lat5420 kernel: #5 0xffffffff8094e798 at usbd_do_request_flags+0x8a8
Feb 17 15:04:14 BattleStar-Lat5420 kernel: #6 0xffffffff8094e87e at usbd_do_request_proc+0x5e
Feb 17 15:04:14 BattleStar-Lat5420 kernel: #7 0xffffffff847ee4b5 at ure_miibus_readreg+0xb5
Feb 17 15:04:14 BattleStar-Lat5420 kernel: #8 0xffffffff806e8cf3 at rgephy_linkup+0xc3
Feb 17 15:04:14 BattleStar-Lat5420 kernel: #9 0xffffffff806e8268 at rgephy_status+0x28
Feb 17 15:04:14 BattleStar-Lat5420 kernel: #10 0xffffffff806e81f3 at rgephy_service+0x323
Feb 17 15:04:14 BattleStar-Lat5420 kernel: #11 0xffffffff806e4197 at mii_pollstat+0x57
Feb 17 15:04:14 BattleStar-Lat5420 kernel: #12 0xffffffff847f3924 at ure_ifmedia_sts+0x184
Feb 17 15:04:14 BattleStar-Lat5420 kernel: #13 0xffffffff80c6e6b6 at ifmedia_ioctl+0x176
Feb 17 15:04:14 BattleStar-Lat5420 kernel: #14 0xffffffff80d8ccb5 at dump_iface+0x145
Feb 17 15:04:14 BattleStar-Lat5420 kernel: #15 0xffffffff80d8f29c at dump_cb+0x1c
Feb 17 15:04:14 BattleStar-Lat5420 kernel: #16 0xffffffff80c65317 at if_foreach_sleep+0x227
Feb 17 15:04:14 BattleStar-Lat5420 kernel: #17 0xffffffff80d8e18d at rtnl_handle_getlink+0x24d
Feb 17 15:04:14 BattleStar-Lat5420 kernel: Uptime: 2d0h34m38s
Feb 17 15:04:14 BattleStar-Lat5420 kernel: Dumping 5412 out of 32274 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%
Feb 17 15:04:14 BattleStar-Lat5420 kernel: Dump complete
Feb 17 15:04:14 BattleStar-Lat5420 kernel: Automatic reboot in 15 seconds - press a key on the console to abort
Feb 17 15:04:14 BattleStar-Lat5420 kernel: ---<<BOOT>>---
Feb 17 15:04:14 BattleStar-Lat5420 kernel: Copyright (c) 1992-2023 The FreeBSD Project.
Feb 17 15:04:14 BattleStar-Lat5420 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Feb 17 15:04:14 BattleStar-Lat5420 kernel:      The Regents of the University of California. All rights reserved.
Feb 17 15:04:14 BattleStar-Lat5420 kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
Feb 17 15:04:14 BattleStar-Lat5420 kernel: FreeBSD 14.2-STABLE stable/14-n270424-31af1ba0a87c GENERIC amd64
Feb 17 15:04:14 BattleStar-Lat5420 kernel: FreeBSD clang version 19.1.7 (https://github.com/llvm/llvm-project.git llvmorg-19.1.7-0-gcd708029e0b2)
Feb 17 15:04:14 BattleStar-Lat5420 kernel: VT(efifb): resolution 1920x1080
...

tingo said:
Be sure you have updated all the relevant kernel modules (you know, the ones in kld_list= in /etc/rc.conf). If you are on pkg's quarterly branch, this might involve compiling from source.

I use latest with kmod repo:

Code:

beastie@BattleStar-Lat5420 --> ~
Ψ pkg -vv
....
Repositories:
  FreeBSD: { 
    url             : "pkg+https://pkg.FreeBSD.org/FreeBSD:14:amd64/latest",
    enabled         : yes,
    priority        : 0,
    mirror_type     : "SRV",
    signature_type  : "FINGERPRINTS",
    fingerprints    : "/usr/share/keys/pkg"
  }
  FreeBSD_Base: { 
    url             : "pkg+https://pkg.FreeBSD.org/FreeBSD:14:amd64/base_weekly",
    enabled         : no,
    priority        : 0,
    mirror_type     : "SRV",
    signature_type  : "FINGERPRINTS",
    fingerprints    : "/usr/share/keys/pkg"
  }
  FreeBSD_Kmods: { 
    url             : "pkg+https://pkg.freebsd.org/FreeBSD:14:amd64/kmods_latest_2",
    enabled         : yes,
    priority        : 0,
    mirror_type     : "SRV",
    signature_type  : "FINGERPRINTS",
    fingerprints    : "/usr/share/keys/pkg"
  }
  14STABLE-amd64: { 
    url             : "http://100.118.169.120/packages/14STABLE-amd64-latest-all/",
    enabled         : no,
    priority        : 100,
    mirror_type     : "HTTP",
    signature_type  : "PUBKEY",
    pubkey          : "/usr/local/etc/ssl/certs/poudriere.cert"
  }

cracauer@ · Feb 17, 2025

Did you try a different USB Ethernet interface? I have one here that never gave me trouble in FreeBSD.

BaronBS · Feb 17, 2025

cracauer@ said:
Did you try a different USB Ethernet interface? I have one here that never gave me trouble in FreeBSD.

If you mean a usb Ethernet dongle, I don't have one. If you mean a internal card, I will need to buy one.

Edit: And the nvme that was connect last time, it is not this time.

ralphbsz · Feb 17, 2025

Since it happened again, exactly the same way, after an upgrade, it's not a transient hardware problem (the infamous alpha particle into memory), it's a bug. You should open a PR and upload the stack trace, and a dump if you have it.

A separate question is how to work around it, and there the idea of a different USB-Ethernet dongle seems like the best short-term plan. Just one word of warning: the cheap Chinese clones you find on Amazon and such places often are bizarrely incompatible with the real ones. I used to have a handful in my parts bin, and on my most recent cleanup I tossed them all in the trash, keeping only one name-brand one after verifying that it works both on Linux and FreeBSD.