Re: usb panic

[maya%netbsd.org@localhost]

On Sat, Sep 01, 2018 at 05:45:48PM +0100, Patrick Welche wrote:
> On Sat, Sep 01, 2018 at 04:47:32PM +0100, Patrick Welche wrote:
> > Just tried today's source on the usual -current/amd64 laptop, and:
> > 
> > fatal breakpoint trap in supervisor mode
> > trap type 1 code 0 rip 0xffffffff8021cd05 cs 0x0 rflags 0x202 cr2 0 ilevel 0 rsp 0xfffff2b68fa981c0 pid 0.46 lowest kstack 0xffffab00adc0b2c0
> > ...
> > vpanic() at netbsd:breakpint+0x5
> > ch_voltag_convert_in()
> > usb_insert_transfer() +0xe6
> > roothub_ctrl_transfer() +0x2c
> > usbd_transfer() +0xa7
> > usbd_do_request_flags() +0xba
> > usbd_get_initial_ddesc() +0x55
> > usbd_new_device() +0x1d2
> > usb_doattach() +0xa1
> > config_interrupts_thread() +0x35
> > 
> > (no external usb devices connected... back to netbsd.old...)
> 
> Bad computer day... added a load of DEBUG options, I don't get as far as
> the USB:
> 
> Stopped in pid 0.80 (system)  == configroot
> 
> breakpoint
> vpanic
> snprintf
> lockdebug_more
> lockdebug_alloc
> _mutex_init
> intel_dp_init_connector
> intel_dp_init
> intel_modeset_init
> i915_driver_load
> drm_dev_register
> drm_pci_attach
> i915drmkms_attach_real
> config_mountroot_thread

You'd have better luck with 'userconf disable i915drmkms' if you want
LOCKDEBUG or turning off LOCKDEBUG. yeah, new drmkms isn't quite
perfect.

The backtrace bug is fixed but at least I still get LOCKDEBUG issues.