From: Bernard Blackham <bernard@blackham.com.au>
To: Florian-Daniel Otel <otel@ce.chalmers.se>
Cc: EricAltendorf@orst.edu,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Swsusp-devel] Re: RTC causes hard lockups in 2.5.70-mm8
Date: Thu, 19 Jun 2003 17:17:43 +0800 [thread overview]
Message-ID: <20030619091743.GA765@amidala> (raw)
In-Reply-To: <16113.30505.519963.233275@solen.ce.chalmers.se>
On Thu, Jun 19, 2003 at 10:41:13AM +0200, Florian-Daniel Otel wrote:
> I can confirm the RTC problems on a Fujitsu LifeBook P2120 (Crusoe
> TM5800, ALi, ACPI). In my case I was even more fortunate (??) since
> using RTC (either compiled-in in the kernel and/or as a module), any
> call to "hwclock" locks the machine rock solid
Ditto. Also an ALi here. I traced it through (printk debugging) and
it appears to lock up in the call to schedule() in rtc_read().
(2.4.21)
Has happened since about 2.4.21-pre3'ish. Haven't had time yet to
establish exactly which release (or ACPI release) started it.
A quirkier but similar bug - this laptop would freeze when writing
to the hardware clock *IF* there was a CD-ROM in the drive (IDE).
This freeze also seemed to occur at midnight most nights. Ejecting
the CD-ROM before saving the hwclock and also at 11:59pm disabled
the problem. This problem existed even without ACPI.
Bernard.
--
Bernard Blackham
bernard at blackham dot com dot au
next prev parent reply other threads:[~2003-06-19 9:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 2:12 RTC causes hard lockups in 2.5.70-mm8 Nathaniel W. Filardo
2003-06-13 2:24 ` Danek Duvall
2003-06-13 8:25 ` Alan Cox
2003-06-17 19:34 ` Eric Altendorf
2003-06-19 7:31 ` Eric Altendorf
2003-06-19 8:41 ` [Swsusp-devel] " Florian-Daniel Otel
2003-06-19 8:46 ` Florian-Daniel Otel
2003-06-19 9:17 ` Bernard Blackham [this message]
2003-06-20 21:25 ` Pavel Machek
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=20030619091743.GA765@amidala \
--to=bernard@blackham.com.au \
--cc=EricAltendorf@orst.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=otel@ce.chalmers.se \
/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