From owner-freebsd-hardware@FreeBSD.ORG Wed May 7 06:35:48 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8C1A37B401 for ; Wed, 7 May 2003 06:35:48 -0700 (PDT) Received: from pl122.evertek.net (pl122.evertek.net [216.51.178.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0705843FBF for ; Wed, 7 May 2003 06:35:46 -0700 (PDT) (envelope-from klaatu@evertek.net) Received: from pl122.evertek.net (localhost [127.0.0.1]) by pl122.evertek.net (8.12.9/8.12.9) with ESMTP id h47DXqjn017522; Wed, 7 May 2003 08:33:52 -0500 (CDT) (envelope-from klaatu@evertek.net) Received: (from klaatu@localhost) by pl122.evertek.net (8.12.9/8.12.9/Submit) id h47DXpWC017521; Wed, 7 May 2003 08:33:51 -0500 (CDT) X-Authentication-Warning: aristotle.pl122.evertek.net: klaatu set sender to klaatu@evertek.net using -f Date: Wed, 7 May 2003 08:33:51 -0500 From: Mike Dean To: Sourabh Ladha Message-ID: <20030507133351.GB17350@evertek.net> References: <20030506204948.GA10809@evertek.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Organization: Engedi Technology X-Preferred-Format: text/plain X-Operating-System: FreeBSD 5.0-CURRENT X-Mail-System: fetchmail, procmail, mutt, vim, abook cc: freebsd-hardware@freebsd.org Subject: Re: Gateway and FreeBSD X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 May 2003 13:35:48 -0000 * Sourabh Ladha [2003-06-05 18:26]: > Thanks for the email Mike. I tried doing what you had suggested but didn't > have any luck. I get stuck at the same place and the machine freezes. I can't say that I've experienced that problem. The symptoms I had were a page fault, kernel panic, and abrupt shutdown. So it could be a different problem. > SOS: What else could I do? I don't really have any further ideas, except one. Is this a new Centrino-based machine? I don't know much about Centrino, but it's possible there are issues with FreeBSD support for that architecture. Either that, or, in cheapening up the 400x (IIRC, it's a lower-end machine than the 450), they put in some chips that FreeBSD doesn't like. Unfortunately, it sounds like you probably can't very easily get a copy of your kernel messages to send. Unless one of the other list readers tell you how to capture that with a non-functional system. -Mike