From owner-freebsd-i386@FreeBSD.ORG Tue Mar 9 08:28:07 2004 Return-Path: Delivered-To: freebsd-i386@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 72FC716A4CE for ; Tue, 9 Mar 2004 08:28:07 -0800 (PST) Received: from mail.gmx.net (pop.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 9362B43D45 for ; Tue, 9 Mar 2004 08:28:06 -0800 (PST) (envelope-from DanielFFM@gmx.net) Received: (qmail 12343 invoked by uid 0); 9 Mar 2004 16:28:05 -0000 Received: from 213.83.45.141 by www38.gmx.net with HTTP; Tue, 9 Mar 2004 17:28:05 +0100 (MET) Date: Tue, 9 Mar 2004 17:28:05 +0100 (MET) From: DanielFFM@gmx.net To: des@des.no (=?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?=), freebsd-i386@FreeBSD.org MIME-Version: 1.0 References: X-Priority: 3 (Normal) X-Authenticated: #211067 Message-ID: <20044.1078849685@www38.gmx.net> X-Mailer: WWW-Mail 1.6 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Subject: Re: My Problem Report i386/63871: Kernel Panic after 1h0m15s X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Mar 2004 16:28:07 -0000 Hi Dag, > Its absence has absolutely no consequences for servers and desktop > machines. It is a problem for laptops, however, which is why it was > added to GENERIC three years ago (2000-11-15). thanks for your feed-back. However, the dates make me wondering :-) This is how I came to the idea it may be new: The option was missing in my kernel-config, as I was using a modified GENERIC from a 5.0.whatever version. It came in to my focus, while comparing a 5.2.1 GENERIC to my "modified GENERIC" which was happily panic'ing. The two machines, which behave identicially, are a P266-MMX board with Intel chipset, and an AMD 1700+ with SiS chipset. Both definitely no laptops, but ordinary energy-hungry and heavy home boxes :-) I took a non-modified very original GENERIC (from CVS-tag RELENG_5_2_1_RELEASE), just commented out the "device pmtimer" -> Kernel panic after 1h0m15s. Next removed the comment so the statement became back active -> The kernel survived the magical border. So, I'm no kernel-hacker, but clearly shows, that this device at least "influences" the behaviour. Maybe someone else is able to reproduce this behavior on another piece of hardware... Regards, Daniel Zuck -- +++ NEU bei GMX und erstmalig in Deutschland: TÜV-geprüfter Virenschutz +++ 100% Virenerkennung nach Wildlist. Infos: http://www.gmx.net/virenschutz