Re: kern/49831: kernel panic on close of ucom tty

[Iain Hibbert <plunky%ogmig.net@localhost>]

The following reply was made to PR kern/49831; it has been noted by GNATS.

From: Iain Hibbert <plunky%ogmig.net@localhost>
To: Nick Hudson <skrll%netbsd.org@localhost>, gnats-bugs%NetBSD.org@localhost, 
    gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/49831: kernel panic on close of ucom tty
Date: Tue, 28 Jun 2016 21:16:14 +0100 (BST)

 On Tue, 28 Jun 2016, Nick Hudson wrote:
 
 > Please try
 > 
 > http://www.netbsd.org/~skrll/nhusb.amd64.2.netbsd
 
 Hmm.. boot single user with nouveau disabled .. then plug the device in, 
 and immediate panic in ucom_attach()
 
 umct0 at uhub1 port 1
 umct0: Targus Group Intl Targus Group Intl, rev 1.10/1.03, addr 2
 ucom0 at umct0
 panic: kernel diagnostic assertion "ucaa->ucaa_bulkin != -1 || (ucaa->ucaa_ipipe && ucaa->ucaa_ixfer)" failed: file "/wrk/nhusb/src/sys/dev/usb/ucom.c", line 271 
 fatal breakpoint trap in supervisor mode
 trap type 1 code 0 rip ffffffff80114c15 cs 8 rflags 246 cr2 706682946000 ilevel 0 rsp fffffe8040defa00
 curlwp 0xfffffe81077e6160 pid 0.53 lowest kstack 0xfffffe8040dec2c0
 Stopped in pid 0.53 (system) at	netbsd:breakpoint+0x5:	leave	
 db{1}>
 breakpoint() at netbsd:breakpoint+0x5
 vpanic() at netbsd:vpanic+0x140
 cd_play_msf() at netbsd:cd_play_msf
 ucom_attach() at netbsd:ucom_attach+0x85a
 config_attach_loc() at netbsd:config_attach_loc+0x17a
 config_found_sm_loc() at netbsd:config_found_sm_loc+0x48
 umct_attach() at netbsd:umct_attach+0x23a
 config_attach_loc() at netbsd:config_attach_loc+0x17a
 config_found_sm_loc() at netbsd:config_found_sm_loc+0x48
 usbd_attachwholedevice() at netbsd:usbd_attachwholedevice+0x8e
 usbd_probe_and_attach() at netbsd:usbd_probe_and_attach+0x46
 usbd_new_device() at netbsd:usbd_new_device+0xf0d
 uhub_explore() at netbsd:uhub_explore+0x2f4
 usb_discover() at netbsd:usb_discover+0x6f
 usb_event_thread() at netbsd:usb_event_thread+0x238
 db{1}> 
 
 I got a backtrace this time, though no core .. and also I tried with 
 hw.ucom.debug=1 but no additional information was shown
 
 iain