From owner-freebsd-stable@FreeBSD.ORG Sat Nov 14 02:44:40 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 D5425106568F for ; Sat, 14 Nov 2009 02:44:40 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by mx1.freebsd.org (Postfix) with ESMTP id 81B758FC19 for ; Sat, 14 Nov 2009 02:44:39 +0000 (UTC) Received: from OMTA20.westchester.pa.mail.comcast.net ([76.96.62.71]) by QMTA05.westchester.pa.mail.comcast.net with comcast id 4qLq1d0011YDfWL55qkgMZ; Sat, 14 Nov 2009 02:44:40 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by OMTA20.westchester.pa.mail.comcast.net with comcast id 4qqa1d0053S48mS3gqqbLm; Sat, 14 Nov 2009 02:50:35 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 62A421E3035; Fri, 13 Nov 2009 18:44:38 -0800 (PST) Date: Fri, 13 Nov 2009 18:44:38 -0800 From: Jeremy Chadwick To: freebsd-stable@freebsd.org Message-ID: <20091114024438.GA93630@icarus.home.lan> References: <5f67a8c40911121246m144ba07w707a1c268fb2102c@mail.gmail.com> <4AFD6D69.7090109@thekeelecentre.com> <5f67a8c40911131757s48a57d9by11c74a417324e48c@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5f67a8c40911131757s48a57d9by11c74a417324e48c@mail.gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: FreeBSD 7.x hang-on-boot on Dell 1950 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: Sat, 14 Nov 2009 02:44:40 -0000 On Fri, Nov 13, 2009 at 08:57:56PM -0500, Zaphod Beeblebrox wrote: > On Fri, Nov 13, 2009 at 9:30 AM, Richard Tector < > richardtector@thekeelecentre.com> wrote: > > > Can you try with 7.0 (should be available on ftp-archive)? > > I can confirm that 7.0 exhibits the same behaviour (and is incidentally very > chatty about probing the raid controller) > > > > I have a 1950 from Sept '07 that's now running 7.2-STABLE i386 with the fd > > devices removed. It started out as 7.0-RELEASE, so maybe its a problem > > introduced since then? > > > > Also, you didn't mention if you were running i386 or amd64. > > This 1950 may predate that a bit, but I'm not sure how to nail it down > exactly, other than by it's hardware components. Anyways, 7.0 does the same > thing --- still wedged. I haven't seen anyone recommend this as a test method yet -- disabling fdc prior to the kernel booting via the loader prompt: - Press 6 at the menu, - At the loader prompt, type: set hint.fdc.0.disabled="1" boot -v (or without -v; your choice) You shouldn't need to set hint.fd.0.disabled="1", since fd0 would normally bind to fdc0; disable the latter and you disable the lesser. The intention here is to rule out the device attachment failures from fdc as the source of the deadlock. For sake of comparison, on our systems (non-Dell), this is what we see during fdc/fd probe and shortly after: fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 cpu0: on acpi0 I'd have recommended disabling ACPI but you tried it already with the same results. :-) -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |