Hello Denis, On 27/01/18(Sat) 12:38, Denis wrote: > Hello Martin, > > Thank you for your attention to the problem with run driver. > > Here is DDB output.
Sorry but can you give more context? How does this happen, why do you need to do? What is the output of 'ps', what is your dmesg? What is your hostname.runX ? See https://www.openbsd.org/report.html for more informations about how to report a problem. > .. dmesg > starting network > panic: attempt to execute user address 0x0 in supervisor mode > Stopped at db_enter+0x5 popq %rbp > TID PID UID PRFLAGS PFLAGS CPU COMMAND > *374840 4608 0 0x14000 0x20 1 usbtask > db_enter() at db_enter+0x5 > panic() at panic+0x128 > trap() at trap+0x6ac > --- trap (number 6) --- > (null) (0,0,ffff80000025c508,5,ffffffff814c8e8d,ffff800032dc1180) at 0 > usb_task_thread(0) at usb_task_thread+0xd8 > end trace frame: 0x0, count: 10 > > ddb{1} trace > db_enter() at db_enter+0x5 > panic() at panic+0x128 > trap() at trap+0x6ac > --- trap (number 6) --- > (null) (0,0,ffff80000025c508,5,ffffffff814c8e8d,ffff800032dc1180) at 0 > usb_task_thread(0) at usb_task_thread+0xd8 > end trace frame: 0x0, count: -5 > > Denis > > > On 1/25/2018 5:34 PM, Martin Pieuchot wrote: > > Hello Denis, > > > > On 25/01/18(Thu) 17:16, Denis wrote: > >> Finally catch kernel panic in the middle of run adapter work. > > Could you please set ddb.panic to 1? > > > > It's hard to figure out what's wrong in your reports because as soon as > > your machine tries to reboot it panics, panics and panics again. So we > > can't tell what is the first (real) problem. > > > > And please stop cross posting. bugs@ is enough for such problems :) > > > > Thanks, > > Martin > > >
