> From: Dale Ghent <da...@elemental.org> > Date: Wed, 30 Dec 2015 15:35:42 -0500 > > > On Dec 30, 2015, at 3:21 PM, Mark Kettenis <mark.kette...@xs4all.nl> = > wrote: > >=20 > >> From: Dale Ghent <da...@elemental.org> > >> Date: Wed, 30 Dec 2015 14:49:58 -0500 > >>=20 > >> Has anyone used or otherwise been able to boot 5.8 on a Xeon-D 1540 =3D= > > >> system? We're experimenting with a SuperMicro Xeon-D 1540 system =3D > >> = > (http://www.supermicro.com/products/system/1U/5018/SYS-5018D-FN4T.cfm) =3D= > > >> and are, surprisingly, not getting terribly far into the kernel boot = > =3D > >> process, with a plethora of "... not configured" messages on console = > =3D > >> preceding a complete free-up after probing the xHCI root hub. > >>=20 > >> The "not configured" messages also apply to each of the 8 cores ("cpu = > at =3D > >> mainbus0: not configured"). The same thing happens with the latest =3D > >> snapshot (dated Dec. 27) > >>=20 > >> Here's a screenshot of the console showing how far the kernel gets =3D > >> before things grind to a halt: http://imgur.com/zETFs7j > >>=20 > >> Might anyone be able to drop a hint or some background info? > >=20 > > You could try disabing devices in UKC. Boot your kernel with "boot > > -c" at the boot> prompt, and at the UKC> prompt enter "disable > > xhci"and "quit". If that doesn't help, try disabling other devices as > > well. > > We've tried that route, but unfortunately there's not a whole lot in the = > BIOS options to turn off, including the USB controllers. I just replied = > to my original post with a transcription of the kernel messages when it = > tries to initially probe and set up the busses and cpus... clearly it = > isn't happy with something.
Read my message again. I'm suggesting to turn xhci off in the kernel, not the BIOS. Also, using a serial console could help catching afull dmesg. Looks like there is no physical serial port, but you can use the IPMI SOL(serial-over-LAN). Assuming console redirection to COM1 is enabled in the bios. Enter "stty com1 115200" and "set tty com1" at the OpenBSD bootloader boot> prompt to let the kernel use the serial port as the console. Cheers, Mark
