Error log for Tue, 22 Oct 2002 23:12:03 +0000, segfault in module "Joe
Potter": dump details are as follows...
>> Error log for Tue, 22 Oct 2002 21:13:47 +0000, segfault in module "Joe
>> Potter": dump details are as follows...
>>> Hello All,
>>> I have a little problem.
>>> We are a small private school that has moved from a pure M$ house to
>>> almost pure linux. We run linux on the server and it does Samba (for
>>> the few winnderrrs boxen), NAT, NIS, NFS, firewall, and fileserving.
>>> It is Redhat 7.3. It is as stable as any box I have ever seen.
>>> In the lab, we have 20 boxen which are mostly K6 AMD boxes with a few
>>> Dells. We have run SuSE and also RedHat. We have used GDM and KDM.
>>> The problem is that the boxes will freeze at the login screen every
>>> once in a while. The box goes unused for a while and the screen blanks
>>> --- and most of the time moving the mouse or hitting a key brings back
>>> the screen. But, every once in a while the box must be re-booted to
>>> regain controll.
>>> Hell fire, this is heaven compared to last year with 18 win98 boxes
>>> (same machines). But, I would like to fix this little irritation.
>>> Oh, it seems only the K6 AMD home built boxes with freeze.
>>> Any ideas?
>> I would bet that there is some sort sort of conflict between the power
>> saving features of the BIOS and apmd.
>> I would try either disabling the Power Saving from the BIOS -XOR-
>> disable the apmd. That's an exclusive or, btw.
> OK, a little more detail please. :-)
Most modern BIOS have power saving features which control the state of
various components after a period of system inactivity. These include
putting the system in a power saving "suspend" state by spinning down
drives, turning off the monitor, and sometimes even putting the CPU in a
sort of "hibernation" mode.
The Advanced Power Management functions of Linux (as controlled by the
apmd daemon), also do this from a software stance.
There is a chance that the two may be conflicting when one is kicking in,
and also the other, putting the system in a sort of "coma" from which no
input device event will trigger a wakeup.
Disabling one or the other should resolve this for you if it is the case.
At my last job, we had a similar problem when putting Win95 on newer T21
laptops. Since Win95 didn't recognize the hardware suspend state, it got
sort of confused and misinterpreted it as a power down condition, shutting
off the laptop in mid-session. I believe IBM eventually issued a patch
fix for it, but the short term fix was to just disable power saving from
rapskat - 6:48am up 25 days, 7:33, 1 user, load average: 0.67, 0.87, 0.75
103 processes: 99 sleeping, 4 running, 0 zombie, 0 stopped
CPU states: 0.0% user, 0.1% system, 0.1% nice, 0.0% idle
To err is human, to forgive, beyond the scope of the Operating System.
-----------== Posted via Newsfeed.Com - Uncensored Usenet News ==----------
http://www.newsfeed.com The #1 Newsgroup Service in the World!
-----= Over 100,000 Newsgroups - Unlimited Fast Downloads - 19 Servers =-----