the machine is still not properly setup and I didn't want to "pollute" bugs@ without a proper sendbug(1), sorry about that.
that being said just tested booting the machine without the hdmi cable to stop inteldrm from attaching, but after everything is booted then attaching the cable makes inteldrm attach cleanly and the machine doesn't panic. I intend to use this as an headless router anyway so if it works this way I'm fine with it. [...] vscsi0 at root scsibus2 at vscsi0: 256 targets softraid0 at root scsibus3 at softraid0: 256 targets root on sd0a (6d2c4982bb37fa0d.a) swap on sd0b dump on sd0b inteldrm0: 1024x768, 32bpp wsdisplay0 at inteldrm0 mux 1 wskbd0: connecting to wsdisplay0 wsdisplay0: screen 0-5 added (std, vt100 emulation) > reports like this should go to bugs@ not tech > > Most of the pool use in drm is quite mechanical conversions of > kmem_cache*. The only suspect thing I can spot is in a detach path, > which isn't involved if a wsdisplay is being attached. > > I can't reproduce this here on a braswell system with the same > kernel from snapshots or a locally built kernel. >
