On Wed, Jan 19, 2022 at 11:04:26PM -0800, guent...@openbsd.org wrote: > On Wed, 19 Jan 2022, Thomas Frohwein wrote: > > >Synopsis: crash on booting GENERIC.MP since upgrade to Jan 18 snapshot > > >Category: kernel amd64 > > >Environment: > > System : OpenBSD 7.0 > > Details : OpenBSD 7.0-current (GENERIC) #265: Wed Jan 19 11:41:29 > > MST 2022 > > > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC > > > > Architecture: OpenBSD.amd64 > > Machine : amd64 > > >Description: > > Since I upgraded to from a Jan 5 snapshot to Jan 18, I am > > unable to boot GENERIC.MP anymore. I am still able to boot > > bsd.rd and bsd.sp - I am sending this bug report from this > > computer running bsd.sp. > > > > When I boot the MP kernel, it fails after the lines: > > > > wsdisplay0: screen 1-5 added (std, vt100 emulation) > > iwm0: hw rev 0x200, rw ver 36.ca7b901d.0, address a4:34:d9:9f:c7:e3 > ... > > The backtrace is kinda nonsensical, showing a copyout() call with no > predecessor, but maybe that's just from copy*() not setting up a proper > frame? However, that's not a change. Neither has there been any change > in the pmap layer in multiple months. The areas of concern IMO are DRM > and (because it was the last thing mentioned) iwm, but the former seems > _much_ more likely.
Booting bsd.mp with inteldrm disabled works? boot -c disable inteldrm* q > > > Philip Guenther > > ... > > sd2 at scsibus4 targ 1 lun 0: <OPENBSD, SR CRYPTO, 006> > > sd2: 1953513MB, 512 bytes/sector, 4000795775 sectors > > root on sd2a (66c54421b07c8a9f.a) swap on sd2b dump on sd2b > > inteldrm0: 1920x1080, 32bpp > > wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation), using wskbd0 > > wskbd1: connecting to wsdisplay0 > > wskbd2: connecting to wsdisplay0 > > wskbd3: connecting to wsdisplay0 > > wsdisplay0: screen 1-5 added (std, vt100 emulation) > > iwm0: hw rev 0x200, fw ver 36.ca7b901d.0, address a4:34:d9:9f:c7:e3
