* Re: RTC causes hard lockups in 2.5.70-mm8
@ 2003-06-13 8:40 Florian Schirmer
0 siblings, 0 replies; 6+ messages in thread
From: Florian Schirmer @ 2003-06-13 8:40 UTC (permalink / raw)
To: linux-kernel; +Cc: alan, duvall
Hi,
> Alan asked whether it was a specific in or out instruction in the
> driver, but I don't know how to find out.
rtc_read never returns. It is busy waiting for a rtc interrupt to arrive.
Which will never do... I blaim ACPI, as it works fine with acpi=off.
Regards,
Florian
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: RTC causes hard lockups in 2.5.70-mm8
2003-06-17 19:34 ` Eric Altendorf
@ 2003-06-19 7:31 ` Eric Altendorf
0 siblings, 0 replies; 6+ messages in thread
From: Eric Altendorf @ 2003-06-19 7:31 UTC (permalink / raw)
To: Linux Kernel Mailing List, swsusp-devel
Oops. Incorrect swsusp maillist address in previous email...sorry if
people get bounces when they reply to that msg.
--eric
On Tuesday 17 June 2003 12:34, Eric Altendorf wrote:
> 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
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: RTC causes hard lockups in 2.5.70-mm8
2003-06-13 8:25 ` Alan Cox
@ 2003-06-17 19:34 ` Eric Altendorf
2003-06-19 7:31 ` Eric Altendorf
0 siblings, 1 reply; 6+ messages in thread
From: Eric Altendorf @ 2003-06-17 19:34 UTC (permalink / raw)
To: Linux Kernel Mailing List, Alan Cox, Nathaniel W. Filardo,
swsusp-devel-request
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: RTC causes hard lockups in 2.5.70-mm8
2003-06-13 2:12 Nathaniel W. Filardo
2003-06-13 2:24 ` Danek Duvall
@ 2003-06-13 8:25 ` Alan Cox
2003-06-17 19:34 ` Eric Altendorf
1 sibling, 1 reply; 6+ messages in thread
From: Alan Cox @ 2003-06-13 8:25 UTC (permalink / raw)
To: Nathaniel W. Filardo; +Cc: Linux Kernel Mailing List
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: RTC causes hard lockups in 2.5.70-mm8
2003-06-13 2:12 Nathaniel W. Filardo
@ 2003-06-13 2:24 ` Danek Duvall
2003-06-13 8:25 ` Alan Cox
1 sibling, 0 replies; 6+ messages in thread
From: Danek Duvall @ 2003-06-13 2:24 UTC (permalink / raw)
To: Nathaniel W. Filardo; +Cc: linux-kernel
On Thu, Jun 12, 2003 at 10:12:06PM -0400, Nathaniel W. Filardo wrote:
> 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.
>
> Hardware is a Fujitsu P2120 with Transmeta TM8500 with ALi chipset:
I saw this on the same hardware on 2.4.21-rc7-ac1, and I've seen a
report of the same on -rc1-ac3, but not on module loading, on accessing
the driver. The problem doesn't seem to be present when running the non
-acX kernels.
Alan asked whether it was a specific in or out instruction in the
driver, but I don't know how to find out.
Danek
^ permalink raw reply [flat|nested] 6+ messages in thread
* RTC causes hard lockups in 2.5.70-mm8
@ 2003-06-13 2:12 Nathaniel W. Filardo
2003-06-13 2:24 ` Danek Duvall
2003-06-13 8:25 ` Alan Cox
0 siblings, 2 replies; 6+ messages in thread
From: Nathaniel W. Filardo @ 2003-06-13 2:12 UTC (permalink / raw)
To: linux-kernel
-----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.
Hardware is a Fujitsu P2120 with Transmeta TM8500 with ALi chipset:
00:00.0 Host bridge: Transmeta Corporation LongRun Northbridge (rev 03)
00:00.1 RAM memory: Transmeta Corporation SDRAM controller
00:00.2 RAM memory: Transmeta Corporation BIOS scratchpad
00:02.0 USB Controller: ALi Corporation. [ALi] USB 1.1 Controller (rev 03)
00:04.0 Multimedia audio controller: ALi Corporation. [ALi] M5451 PCI
AC-Link Controller Audio Device (rev 01)
00:06.0 Bridge: ALi Corporation. [ALi] M7101 PMU
00:07.0 ISA bridge: ALi Corporation. [ALi] M1533 PCI to ISA Bridge
[Aladdin IV]
00:09.0 USB Controller: NEC Corporation USB (rev 41)
00:09.1 USB Controller: NEC Corporation USB (rev 41)
00:09.2 USB Controller: NEC Corporation USB 2.0 (rev 02)
00:0c.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus
Controller (rev 01)
00:0f.0 IDE interface: ALi Corporation. [ALi] M5229 IDE (rev c3)
00:10.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
00:12.0 Network controller: Harris Semiconductor Prism 2.5 Wavelan chipset
(rev 01)
00:13.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000
Controller (PHY/Link)
00:14.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6
LY
Any additional information needed I'll be happy to provide.
- --nwf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE+6TLZR4WVIgmDWjIRAsSNAJ0UZUq/4A4MmQ4DHcl6qnncWcIFDwCfSUYD
mE9xrtTweq57eM95dbs9Tbo=
=iUCG
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2003-06-19 7:16 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-06-13 8:40 RTC causes hard lockups in 2.5.70-mm8 Florian Schirmer
-- strict thread matches above, loose matches on Subject: below --
2003-06-13 2:12 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
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 NNTP newsgroup(s).