panic on rpi3b: usbconfig reset
Ronald Klop <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.arm,gmane.os.freebsd.devel.usb |
|---|---|
| Message-ID | <254722283.8424.1720796671190@localhost> |
Hi, Performing "usbconfig reset" on my RPI3B running 14.1-RELEASE-p2/aarch64 results in a panic. Here is the output on the serial console: login: Jul 12 13:18:35 rpi3 su[14837]: ronald to root on /dev/pts/0 uhub0: at usbus1, port 1, addr 1 (disconnected) ugen1.2: <vendor 0x0424 product 0x2514> at usbus1 (disconnected) uhub1: at uhub0, port 1, addr 2 (disconnected) ugen1.3: <vendor 0x0424 product 0x2514> at usbus1 (disconnected) uhub2: at uhub1, port 1, addr 3 (disconnected) ugen1.4: <vendor 0x0424 product 0x7800> at usbus1 (disconnected) muge0: at uhub2, port 1, addr 4 (disconnected) muge0: warning: Failed to read register 0x120 muge0: warning: MII is busy muge0: warning: Failed to read register 0x120 muge0: warning: MII is busy muge0: warning: Failed to read register 0x120 muge0: warning: MII is busy muge0: warning: Failed to read register 0x120 muge0: warning: MII is busy muge0: warning: Failed to read register 0x120 muge0: warning: MII is busy muge0: warning: Failed to read register 0x120 muge0: warning: MII is busy muge0: warning: Failed to read register 0x120 muge0: warning: MII is busy muge0: warning: Failed to read register 0x120 muge0: warning: MII is busy muge0: warning: Failed to read register 0x120 muge0: warning: MII is busy muge0: warning: Failed to read register 0x120 ukphy0: detached muge0: warning: MII is busy Fatal data abort: miibus0: detached x0: 0x0000000000000000 x1: 0xffff0000403f44d4 x2: 0x0000000000000000 x3: 0xffff00000032e24c x4: 0xffff00000088eef8 x5: 0x0000000000000041 x6: 0xffff00000052cee8 x7: 0xffff0000403f43b0 x8: 0x0000000000000053 x9: 0xaf460225cde9dab0 x10: 0x0000000000000001 x11: 0x0000000000000001 x12: 0x0000000000000001 x13: 0x0000000000000001 x14: 0x0000000000000000 x15: 0x0000000000000002 x16: 0x0000000000000000 x17: 0xffff0000403f42b5 x18: 0xffff0000403f45d0 x19: 0xffffa00001980380 x20: 0x0000000000000000 x21: 0x0000000000000000 x22: 0x0000000000000001 x23: 0xffffa00001a70200 x24: 0xffffa00001980800 x25: 0xffff000000c5d410 x26: 0xffffa000018045c0 x27: 0xffff000000ca5000 x28: 0x0000000000000000 x29: 0xffff0000403f45d0 sp: 0xffff0000403f45d0 lr: 0xffff0000001dec34 elr: 0xffff0000001dec44 spsr: 0x0000000060000045 far: 0x0000000000000000 esr: 0x0000000096000004 panic: vm_fault failed: 0xffff0000001dec44 error 1 cpuid = 2 time = 1720783402 KDB: stack backtrace: #0 0xffff000000525d3c at kdb_backtrace+0x58 #1 0xffff0000004d0d40 at vpanic+0x198 #2 0xffff0000004d0ba4 at panic+0x44 #3 0xffff0000008b795c at data_abort+0x2cc #4 0xffff000000893814 at handle_el1h_sync+0x14 Uptime: 7m10s Dumping 134 out of 926 MB:..3%..12%..21%..33%..42%..51%..63%..72%..81%..93% Dump complete Resetting system ... I have a core dump and can gather more information. The panic is repeatable. Regards, Ronald.