From owner-freebsd-stable@FreeBSD.ORG Tue Mar 15 09:54:27 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 430CD106564A for ; Tue, 15 Mar 2011 09:54:27 +0000 (UTC) (envelope-from mike@scottsonline.org.uk) Received: from honeysuckle.london.02.net (honeysuckle.london.02.net [87.194.255.144]) by mx1.freebsd.org (Postfix) with ESMTP id CD4FC8FC13 for ; Tue, 15 Mar 2011 09:54:26 +0000 (UTC) Received: from scottsonline.org.uk (78.105.254.41) by honeysuckle.london.02.net (8.5.133) id 4D4A076A014B734F for freebsd-stable@freebsd.org; Tue, 15 Mar 2011 09:54:25 +0000 Received: from [192.168.0.2] (picard.scotts [192.168.0.2]) by scottsonline.org.uk (8.13.8/8.13.8) with ESMTP id p2F9sNn5042622 for ; Tue, 15 Mar 2011 09:54:23 GMT (envelope-from mike@scottsonline.org.uk) Message-ID: <4D7F374F.3060404@scottsonline.org.uk> Date: Tue, 15 Mar 2011 09:54:23 +0000 From: Mike Scott User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4D7DE88C.9070405@scottsonline.org.uk> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (scottsonline.org.uk [192.168.0.1]); Tue, 15 Mar 2011 09:54:23 +0000 (GMT) X-Scanned-By: MIMEDefang 2.67 on 192.168.0.1 Subject: Re: problems booting 8.x kernel X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2011 09:54:27 -0000 On 14/03/11 18:48, Olivier Cochard-Labbé wrote: > On Mon, Mar 14, 2011 at 11:06 AM, Mike Scott wrote: >> >> Basically, I'm finding that the 8.1 and 8.2 kernels hang on certain machines >> 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 kfreebsd >> 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: 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: 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… This solve > the problem on my motherboard. Thanks for the note. I've tried disabling everything - floppy, usb and acpi - in the BIOS. Still no joy; it just hangs. I don't get the 'lazy allocation' message you do; nfe0 looks reasonable here. I'm using boot -v. Depending on whether I use -p (single step) as well, the hang point changes from just after "flowtable cleaner started" or the message about a firewire bus reset I quoted earlier. I've found the occasional similar comment on the web, such as http://forums.freebsd.org/showthread.php?p=117767 hanging on amd64 smp hardware after 'ata pseudoraid loaded' (which is a message I sometimes see just before the 'flowtable' message); maybe related, maybe not. But no answers :-{ I think I'll have to give up because I'm out of ideas, settle for a linux kernel on this particular target h/w, and just hope this issue doesn't affect another machine I have which is due for imminent upgrade from 6.2 to 8.x. -- Mike Scott Harlow, Essex, England