Date: Mon, 14 Mar 2011 19:48:22 +0100 From: =?ISO-8859-1?Q?Olivier_Cochard=2DLabb=E9?= <olivier@cochard.me> To: Mike Scott <mike@scottsonline.org.uk> Cc: freebsd-stable@freebsd.org Subject: Re: problems booting 8.x kernel Message-ID: <AANLkTik%2BshOH_1u03NCKZWTcZzwF6CwDveiMQdTuxAYZ@mail.gmail.com> In-Reply-To: <4D7DE88C.9070405@scottsonline.org.uk> References: <4D7DE88C.9070405@scottsonline.org.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 14, 2011 at 11:06 AM, Mike Scott <mike@scottsonline.org.uk> wro= te: > > Basically, I'm finding that the 8.1 and 8.2 kernels hang on certain machi= nes > during bootup, specifically during device discover and module load. I've > tried 8.2 off the current release CD, and also 8.1 off the Debian kfreebs= d > 6.0.0 distribution - both have the same issue. > I've got the same problem with one motherboard (Asus K8N7-E deluxe): Since FreeBSD 8.0, there is an ACPI bug (pr 142263) in the FreeBSD kernel that detect wrong address for all devices. As example, here is an extract of the dmesg on FreeBSD 7.2: nfe0: <NVIDIA nForce4 CK804 MCP8 Networking Adapter> port 0xb000-0xb007 mem 0xd3000000-0xd3000fff irq 21 at device 10.0 on pci0 nfe0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xd3000000 But, since FreeBSD 8.0, the dmesg report this (note the reserved mem diff): nfe0: <NVIDIA nForce4 CK804 MCP8 Networking Adapter> irq 21 at device 10.0 on pci0 nfe0: Lazy allocation of 0x1000000 bytes rid 0x10 type 3 at 0x81000000 nfe0: Reserved 0x1000000 bytes for rid 0x10 type 3 at 0x81000000! Try to boot by disabling ACPI into the FreeBSD boot screen=85 This solve the problem on my motherboard. Regards, Olivier
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTik%2BshOH_1u03NCKZWTcZzwF6CwDveiMQdTuxAYZ>