NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/54023: assertion panic during shutdown
The following reply was made to PR kern/54023; it has been noted by GNATS.
From: Hauke Fath <hf%spg.tu-darmstadt.de@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
matthew green <mrg%eterna.com.au@localhost>
Subject: Re: kern/54023: assertion panic during shutdown
Date: Wed, 6 Mar 2019 17:31:56 +0100
On 3/1/19 10:30 PM, matthew green wrote:
> can you turn on USB_DEBUG and UHID_DEBUG, make sure that usb_debug
> is set in sysctl, make sure ddb will be entered (ddb.onpanic=1),
This is the log from msgbuf after 'reboot 0x04':
[ 266.812560] panic: kernel diagnostic assertion "xfer->ux_status !=
USBD_CANCELLED" failed: file
"/public/netbsd-developer/sys/dev/usb/ehci.c", line 3264
[ 266.832561] cpu3: Begin traceback...
[ 266.832561] trace fp ffffffc044d87820
[ 266.842567] fp ffffffc044d87840 vpanic() at ffffffc000439570
netbsd:vpanic+0x198
[ 266.852563] fp ffffffc044d878a0 kern_assert() at ffffffc000569ae4
netbsd:kern_assert+0x5c
[ 266.862565] fp ffffffc044d87930 ehci_abort_xfer() at
ffffffc000178ac4 netbsd:ehci_abort_xfer+0x2c4
[ 266.872565] fp ffffffc044d87990 usbd_ar_pipe() at ffffffc0000c1000
netbsd:usbd_ar_pipe+0x1c8
[ 266.882566] fp ffffffc044d879e0 usbd_abort_pipe() at
ffffffc0000c1390 netbsd:usbd_abort_pipe+0x28
[ 266.892566] fp ffffffc044d87a00 uhidev_stop() at ffffffc0000de8e8
netbsd:uhidev_stop+0x30
[ 266.902568] fp ffffffc044d87a20 uhidclose() at ffffffc0000df374
netbsd:uhidclose+0x64
[ 266.912568] fp ffffffc044d87a50 cdev_close() at ffffffc000425d88
netbsd:cdev_close+0xb8
[ 266.922570] fp ffffffc044d87a90 spec_close() at ffffffc0004ae8c0
netbsd:spec_close+0x1a0
[ 266.932570] fp ffffffc044d87ae0 VOP_CLOSE() at ffffffc0004a1fb4
netbsd:VOP_CLOSE+0x3c
[ 266.942571] fp ffffffc044d87b20 vn_close() at ffffffc00049a5ac
netbsd:vn_close+0x34
[ 266.952571] fp ffffffc044d87b50 closef() at ffffffc0003d7dd8
netbsd:closef+0x50
[ 266.962573] fp ffffffc044d87b90 fd_free() at ffffffc0003db2e4
netbsd:fd_free+0x1ac
[ 266.972573] fp ffffffc044d87c00 exit1() at ffffffc0003e2c48
netbsd:exit1+0xe8
[ 266.982574] fp ffffffc044d87cc0 sigexit() at ffffffc000407da8
netbsd:sigexit+0x1d8
[ 266.992575] fp ffffffc044d87d10 postsig() at ffffffc00040815c
netbsd:postsig+0x26c
[ 267.002576] fp ffffffc044d87db0 lwp_userret() at ffffffc0003ecc20
netbsd:lwp_userret+0x1a0
[ 267.012577] fp ffffffc044d87e00 userret() at ffffffc00007063c
netbsd:userret+0x6c
[ 267.022578] fp ffffffc044d87e20 syscall() at ffffffc0000703cc
netbsd:syscall+0x104
[ 267.042580] tf ffffffc044d87ed0 el0_trap() at ffffffc00006ea10
netbsd:el0_trap
[ 267.042580] ---- trapframe 0xffffffc044d87ed0 (304 bytes) ----
[ 267.052581] pc=0000f707d44a3e90, spsr=0000000080000000
[ 267.052581] esr=0000000056000003, far=ffffffc0440d9000
[ 267.062581] x0=0000000000000003, x1=0000ffffffe93ba8
[ 267.072582] x2=0000000000000001, x3=0000f707d4586c98
[ 267.072582] x4=0000ffffffe928b9, x5=0000000000000000
[ 267.082583] x6=0000ffffffe9318c, x7=0000000000000000
[ 267.082583] x8=0000ffffffe928b9, x9=0000000000000011
[ 267.092584] x10=0000000000000004, x11=0000000000000001
[ 267.092584] x12=000003ffffffa4c0, x13=000003ffffffa4c4
[ 267.102585] x14=0000f707d433c254, x15=0000ffffffe93110
[ 267.112585] x16=0000000200112b38, x17=0000f707d44a3e90
[ 267.112585] x18=0000000000004040, x19=0000ffffffe94faf
[ 267.122587] x20=0000ffffffe94fe8, x21=0000000000000008
[ 267.122587] x22=0000000200112000, x23=0000f707d433c140
[ 267.132587] x24=0000ffffffe93ba8, x25=0000ffffffe955a5
[ 267.132587] x26=0000ffffffe955b3, x27=0000000000000000
[ 267.142588] x28=0000000000000001, fp=x29=0000000000000000
[ 267.142588] lr=x30=00000002001020fc, sp=0000ffffffe93af0
[ 267.152589] ------------------------------------------------
[ 267.162590] cpu3: End traceback...
rebooting...
> and since the keyboard probably won't work (it is either the kbd
> or mouse that is triggering this fault),
The kbd actually worked, but ...
> also set ddb.commandonenter
> to something like "show kernhist usbhist", then we may even get a
> useful usb log of what it was doing before the crash. it may
> scroll a lot -- but the really useful stuff is likely in the last
> part, so hopefully a picture not video will suffice.
'show kernhist' told me putput would exceed 50000 characters, and 'show
usbhist" said it didn't exist.
I will rebuild with larger DDB_HISTORY_SIZE and retry.
> ps: it occurs to me another test case that isn't reboot would be
> to (remotely) use drvctl -d to detach the ukbd/ums devices and
> see if either or both trigger this problem directly there, or if
> something else is the trigger..
I tried that, it paniced anyway.
Cheerio,
hauke
Home |
Main Index |
Thread Index |
Old Index