From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 11:12:08 2009 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 2AB06106566C for ; Tue, 20 Jan 2009 11:12:08 +0000 (UTC) (envelope-from markir@paradise.net.nz) Received: from smtp5.clear.net.nz (smtp5.clear.net.nz [203.97.33.68]) by mx1.freebsd.org (Postfix) with ESMTP id EA40E8FC0C for ; Tue, 20 Jan 2009 11:12:07 +0000 (UTC) (envelope-from markir@paradise.net.nz) Received: from zmori.markir.net (121-73-164-72.dsl.telstraclear.net [121.73.164.72]) by smtp5.clear.net.nz (CLEAR Net Mail) with ESMTP id <0KDR00JGKNQSTH00@smtp5.clear.net.nz> for FreeBSD-stable@FreeBSD.org; Tue, 20 Jan 2009 23:56:53 +1300 (NZDT) Date: Tue, 20 Jan 2009 23:56:52 +1300 From: Mark Kirkwood In-reply-to: <20090109171857.GA49752@marvin.eastcentral.edu> To: Reuben Message-id: <4975ADF4.1070103@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit References: <20090109171857.GA49752@marvin.eastcentral.edu> User-Agent: Thunderbird 2.0.0.19 (X11/20090117) Cc: FreeBSD-stable@FreeBSD.org Subject: Re: Broken loader on 7.1-STABLE? 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, 20 Jan 2009 11:12:08 -0000 Reuben wrote: > > I was wondering if anyone else was seeing loader (v1.02) break after updating from 7.1-RELEASE to 7.1-STABLE. After performing the prescribed updating procedure (via the handbook), the system will go through the normal steps and after the boot menu will present the following error: > > Can't work out which disk we are booting from. > Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0 > > According to the bugbusting page on the FreeBSD wiki there's two issues at work that cause this behavior; patches were committed to HEAD/RELENG earlier last year in Mar and Aug. Up until now I've never come across this problem in 6.x or 7.0. In doing a little research I've come across a few older threads via google where it was believed that the problem was caused by improper CFLAGS in make.conf. I've commented mine out and rebuilt things.. with the same end result. In fact, if it's any help, my CFLAGS declaration in make.conf is taken verbatim from the /usr/share/examples/etc/make.conf. Furthermore, on selecting option 6 from the boot menu (escape to loader prompt), the system [I'm assuming] crashes displaying a blinking ASCII pattern from which only a hard reboot will work. > > FWIW, this is a fairly plain system.. nothing special in sysctl.conf or loader.conf, and the kernel is pretty stock as well (more or less GENERIC with my sound device and pf). > > A temporary fix for me was to copy over loader.old to loader in /boot. > > > I am getting this too - update from RELENG_7 @12 Jan src to 20 Jan and I have: panic: free: guard1 fail @ 0x511d from /usr/src/sys/boot/i386/loader/../../common/module.c:959 Can't work out which disk we are booting from. Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0 Copying loader.old to loader did not work around this for me - I had to empty loader.conf too. Here is what *was* in there: ---> begin loader.conf # Sound sound_load="YES" snd_hda_load="YES" # IPC kern.ipc.semmni=500 kern.ipc.semmns=500 # CD/DVD DMA atapicam_load="YES" hw.ata.atapi_dma=0 --> end loader.conf At this point I am not sure which if are the bad guys... The machine is an Asus a8vx. regards Mark