From: Eric Altendorf <EricAltendorf@orst.edu>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
"Nathaniel W. Filardo" <nwf@andrew.cmu.edu>,
swsusp-devel-request@lists.sourceforge.net
Subject: Re: RTC causes hard lockups in 2.5.70-mm8
Date: Tue, 17 Jun 2003 12:34:00 -0700 [thread overview]
Message-ID: <200306171232.27887.EricAltendorf@orst.edu> (raw)
In-Reply-To: <1055492730.5162.0.camel@dhcp22.swansea.linux.org.uk>
On Friday 13 June 2003 01:25, Alan Cox wrote:
> On Gwe, 2003-06-13 at 03:12, Nathaniel W. Filardo wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > If I set CONFIG_RTC=m and rebuild, when the kernel autoloads
> > rtc.ko the system immediately locks hard, not responding even to
> > magic SysRq series. Backing out either of the rtc-* patches from
> > -mm8 does not seem to fix the problem.
>
> It seems to be ALI + ACPI related but I dont yet understand what is
> going on
>
I'm running a Toshiba Libretto L2 (Crusoe, ACPI, ALI). I don't have
any troubles with 2.5.63 (which happens to be my current stable
kernel). However, I've been playing with 2.4.21 with just the swsusp
patches (not -ac) and with most builds I've tried there, invoking
hwclock always hangs the machine (which I assume is rtc related).
Let me know if I can provide any more information...
Eric
next prev parent reply other threads:[~2003-06-19 6:11 UTC|newest]
Thread overview: 10+ 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 [this message]
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
2003-06-20 21:25 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2003-06-13 8:40 Florian Schirmer
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=200306171232.27887.EricAltendorf@orst.edu \
--to=ericaltendorf@orst.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nwf@andrew.cmu.edu \
--cc=swsusp-devel-request@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.