My Problem Report i386/63871: Kernel Panic after 1h0m15s

DanielFFM at gmx.net DanielFFM at gmx.net
Tue Mar 9 08:28:07 PST 2004


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



More information about the freebsd-i386 mailing list