13 Sep
2005
13 Sep
'05
7:23 p.m.
Ah, I didn't know that was highly experimental. I was given this choice:
Clock & Timer Selection
1. Legacy Timer Support (LEGACY_TIMER)
2. HPET
Timer Support (HPET_TIMER)
3. High Resolution Timer Support (HIGH_RES_TIMERS) (NEW)
choice[1-3?]:
I didn't know what HPET was, legacy sounds slow, so I picked high res. I'll
give the kernel without high res a try tonight. Thanks!
On Tue, 13 Sep 2005 at 17:07 -0400, Lee Revell wrote:
On Tue, 2005-09-13 at 14:53 -0600, Hans Fugal wrote:
--
Hans Fugal | If more of us valued food and cheer and
http://hans.fugal.net/ | song above hoarded gold, it would be a
http://gdmxml.fugal.net/ | merrier world.
| -- J.R.R. Tolkien
---------------------------------------------------------------------
GnuPG Fingerprint: 6940 87C5 6610 567F 1E95 CB5E FC98 E8CD E0AA D460
On Tue, 13 Sep 2005 at 16:49 -0400, Lee Revell
wrote:
LKML archives or a Google search.
Lee
On Tue, 2005-09-13 at 14:36 -0600, Hans Fugal
wrote:
Hmm, no I think it was enabled. I take it it should be disabled? Is that
documented somewhere?
On Tue, 13 Sep 2005 at 22:26 +0200, Peter
Mogensen wrote:
> Hans Fugal wrote:
> > I have tried the 2.6.13-rt kernel and it boots fine but will lock up
> > after a few minutes. (2.6.12-rt had the same problem for me IIRC)
>
> For what it's worth:
> Do you have any other "experimental" kernel features? My 2.6.13-rt also
> freezes (or spontaniously reboots) after a while, but it seems to only
> happen when my ipw2100 WLAN module is used. That module is otherwise
None that come to mind. I will send in my .config per Lee's suggestion.
I'm not usually doing anything interesting either, just locks up out of
the blue.
You disabled CONFIG_HIGH_RES_TIMERS right?