Date: Wed, 9 Aug 2017 16:05:15 +0100 From: Rafal Lukawiecki <raf@rafal.net> To: freebsd-stable@freebsd.org Subject: Re: Is it worth waiting for AMD Opteron X3000 support in FreeBSD? Bug [221350] Message-ID: <7B1C3028-EBD7-4671-AB6E-CD7EB72F99DF@rafal.net> In-Reply-To: <20170809130804.GG81427@home.opsec.eu> References: <CE97377F-06B4-43E9-A242-3B59A7BD0733@rafal.net> <20170809130804.GG81427@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
Many thanks, Kurt, for pointing out those other 3 bug reports. On the face o= f it, they look different to mine. In my case, and in the case of another us= er who has reported this on the FreeNAS forum (affecting FreeBSD 11.0), the b= oot progresses past the point shown in the 3 reports that you have suggested= , by perhaps another 5-10 seconds. Kindly have a look at the screenshots I h= ave submitted within the bug report here: https://bugs.freebsd.org/bugzilla/= show_bug.cgi?id=3D221350 ...and you may notice that the boot process hangs just after it has displaye= d messages about pci0 acpi. The verbose boot (screenshot also above) shows t= hat the boot process seems to have just identified memory modules on pcib0. T= he remaining screenshots show kernel panics when I tried to disable ACPI. I will test the boot with the other releases of FreeBSD as suggested by Miro= slav Lachman, later today, and I will report back here, then I suppose I can= make a decision if to move this discussion to freebsd-current, as recommend= ed by @wishmaster. I apologise for confusing which list to keep reporting to= . Many thanks, Rafal Lukawiecki=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7B1C3028-EBD7-4671-AB6E-CD7EB72F99DF>