From owner-freebsd-mobile Fri Jan 31 08:41:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA29927 for mobile-outgoing; Fri, 31 Jan 1997 08:41:58 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA29922 for ; Fri, 31 Jan 1997 08:41:54 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA09683; Fri, 31 Jan 1997 09:41:43 -0700 (MST) Date: Fri, 31 Jan 1997 09:41:43 -0700 (MST) Message-Id: <199701311641.JAA09683@rocky.mt.sri.com> From: Nate Williams To: hm@hcs.de Cc: mobile@freebsd.org Subject: Re: 2.1.6.1 + PAO: occasional panic at boot In-Reply-To: References: Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > i've just installed 2.1.6.1 and the PAO package from the PAO www site for > 2.1.5 - and i'm very pleased! > > The only problem i'm experiencing so far is that i get panics from time > to time at boot time, after the message for the apm0 driver: "cannot mount > root". Then i get into ddb and when pressing a key i get the message > "Card 0 inserted" (there is an 3com 3c589c in slot 0 using the ep driver). Weird. But, the apm0 driver doesn't print that out, but the kernel itself does. Can you do a backtrace to see whose calling panic()? > The machine is a digital Hinote 433, 12Mb Ram, 512Mb disk (Toshiba > MK1924FCV). How old is the BIOS on this thing? Nate