From: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
To: Samuel Thibault <samuel.thibault@fnac.net>,
Samuel Thibault <Samuel.Thibault@ens-lyon.fr>,
linux-laptop@vger.kernel.org
Subject: Re: Time freezing on Armada E500 Laptop
Date: Mon, 23 Jun 2003 10:57:07 +0300 [thread overview]
Message-ID: <200306230753.h5N7r0u09635@Port.imtp.ilyichevsk.odessa.ua> (raw)
In-Reply-To: <20030621025104.GA4906@bouh.unh.edu>
On 21 June 2003 05:51, Samuel Thibault wrote:
> Hi,
>
> This has been happening for months since I bougth my laptop: it
> sometimes seems to be frozen, and merely pressing a key unfreezes it.
> Sending chars on serial port does as well, but the USB mouse does not.
> I had a closer look and realized that the only matter was the IRQ0 not
> being generated by the pit any more... So that jiffies wouldn't
> increase, hence any program based on time would indeed freeze while
> cpu burners would still run for instance. Fancy things being the window
> manager still working, but freezing on raising a window. The system
> clock goes round within ~5s. Remote shells still work of course, since
> network generates IRQs, but sshd is frozen :/.
>
> I tried 2.4 & 2.5, enabling / disabling APM, ACPI, speedstep, without
> any change. Flashing my bios to the latest version didn't add any option
> to the setup, it still only has a dozen, the only one related to power
> management being speedstep, which I tried to enable / disable as well.
> The Power Management program shipped by compaq for win95 won't run ("you
> need administrator rights", uh? on w95?)
>
> Just to be sure, Linux wouldn't ever disable IRQ0, would it? Could it
> on the other hand use other timers such as the rtc for detecting this
> trouble, and even use them as fallbacks?
CMOS clock can bee used to detect this I suppose.
There is also the NMI watchdog.
--
vda
prev parent reply other threads:[~2003-06-23 7:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-21 2:51 Time freezing on Armada E500 Laptop Samuel Thibault
2003-06-23 7:57 ` Denis Vlasenko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200306230753.h5N7r0u09635@Port.imtp.ilyichevsk.odessa.ua \
--to=vda@port.imtp.ilyichevsk.odessa.ua \
--cc=Samuel.Thibault@ens-lyon.fr \
--cc=linux-laptop@vger.kernel.org \
--cc=samuel.thibault@fnac.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).