Date: Fri, 5 Apr 2019 15:02:15 +1100 (EST) From: Bruce Evans <brde@optusnet.com.au> To: longwitz@incore.de Cc: bugs@freebsd.org Subject: Re: [Bug 236838] Commit r340224 prevents loading the kernel for some Intel Xeon hardware Message-ID: <20190405145411.L959@besplex.bde.org> In-Reply-To: <bug-236838-227-kSsyaP8nGZ@https.bugs.freebsd.org/bugzilla/> References: <bug-236838-227@https.bugs.freebsd.org/bugzilla/> <bug-236838-227-kSsyaP8nGZ@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
On Thu, 4 Apr 2019 a bug that dpesnt want replies@freebsd.org wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236838 > > --- Comment #5 from longwitz@incore.de --- > Created attachment 203384 > --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=203384&action=edit > Output serial console of full verbose boot > > I use amd64, the commit r340224 (r339979) does only affect amd64. Removing the > line with 'case 0x3590' helps, kernel now boots fine. With the patch > > --- pci_cfgreg.c.orig 2018-11-26 16:43:04.706033000 +0100 > +++ pci_cfgreg.c 2019-04-04 11:30:51.847357000 +0200 > @@ -90,13 +90,15 @@ > * This also implies that it can do PCIe extended config cycles. > */ > > + printf("pci_cfgregopen called\n"); > ... > together with a 'printf(Calling pci_early_quirks())' in machdep.c and setting > "debug.late_console=0" in loader.conf I got the attached output on the serial > console. I checked that vt still crashes with debug.late_console=0. So configuring vt breaks early console use even for console drivers that work early. Brucehelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190405145411.L959>