ARM64 Panic

[R0me0 ***]

Hello guys,
After Installed a snapshot from one week ago.
I just kept pi3 on "login" and day by day I went to console and tried
login/logout

Randomly it crashes and seems it is the same error I was facing before 6.1
release
I already tried to install on different usb's flash drives and is the same
error;


Any directions are really appreciated.
Thank you

Sorry the lack of dmesg

ddb> trace
db_enter() at panic+0x154
panic() at pool_get+0x54
pool_get() at dwc2_hcd_urb_enqueue+0x94
dwc2_hcd_urb_enqueue() at dwc2_device_start+0x3c4
dwc2_device_start() at usb_transfer_complete+0x2ec
usb_transfer_complete() at dwc2_softintr+0x74
dwc2_softintr() at softintr_dispatch+0xa0
softintr_dispatch() at arm_do_pending_intr+0x9c
arm_do_pending_intr() at bcm_intc_irq_handler+0xa8
bcm_intc_irq_handler() at handle_el1h_irq+0x6c
handle_el1h_irq() at sched_idle+0x198
sched_idle() at proc_trampoline+0xc

ddb> continue
syncing disks... panic: mtx 0xffffff800435cab8: locking against myself
Stopped at panic+0x158: db_enter() at panic+0x154
panic() at dwc2_device_start+0x34c
dwc2_device_start() at usbd_transfer+0x140
usbd_transfer() at umass_setup_transfer+0x90
umass_setup_transfer() at umass_bbb_transfer+0x1ac
umass_bbb_transfer() at umass_scsi_cmd+0xd4
umass_scsi_cmd() at sdstart+0x2a0

[Stuart Henderson]

Post by R0me0 ***
Hello guys,
After Installed a snapshot from one week ago.

A problem with the dwctwo(4) driver which could result in this
was fixed on 2017/06/20. I'm unsure whether this made it into a
snapshot yet, but if you're not already running "OpenBSD
6.1-current (GENERIC) #0: Wed Jun 21 17:47:53 AEST 2017" you
should update to at least that version, if it still occurs then
you could build a new kernel or wait for a newer snap to be
built.

[R0me0 ***]

Hello, Stuart! :) Thank you for the reply, I will try a fresh install
:)

[] 's guys

Post by Stuart Henderson

Post by R0me0 ***
Hello guys,
After Installed a snapshot from one week ago.

A problem with the dwctwo(4) driver which could result in this
was fixed on 2017/06/20. I'm unsure whether this made it into a
snapshot yet, but if you're not already running "OpenBSD
6.1-current (GENERIC) #0: Wed Jun 21 17:47:53 AEST 2017" you
should update to at least that version, if it still occurs then
you could build a new kernel or wait for a newer snap to be
built.

[Jonathan Gray]

Post by Stuart Henderson

Post by R0me0 ***
Hello guys,
After Installed a snapshot from one week ago.

A problem with the dwctwo(4) driver which could result in this
was fixed on 2017/06/20. I'm unsure whether this made it into a
snapshot yet, but if you're not already running "OpenBSD
6.1-current (GENERIC) #0: Wed Jun 21 17:47:53 AEST 2017" you
should update to at least that version, if it still occurs then
you could build a new kernel or wait for a newer snap to be
built.

It does include it. There will be no new snapshots until someone has
time to look into making lld handle the linker script the kernel now
requires. This also means you can't build your own kernel till then.