2.5.70 freezes when running hwclock

2.5.70 freezes when running hwclock

[Éric Brunet]

I have tried 2.5.70 on an intel chipset based pc, and I got a
reproductible complete freeze during the boot process when hwclock is
run. Even Caps Lock wouldn't lit the little led.

Removing the offending line, 2.5.70 seemed to work... I haven't fully
tried it yet.

Is this problem known/identified/fixed yet, or do you want a more
complete bug report ?

Regards,

	Éric Brunet	

Re: 2.5.70 freezes when running hwclock

[Michael Frank]

On Saturday 31 May 2003 16:05, Éric Brunet wrote:
> I have tried 2.5.70 on an intel chipset based pc, and I
> got a reproductible complete freeze during the boot
> process when hwclock is run. Even Caps Lock wouldn't lit
> the little led.
>
> Removing the offending line, 2.5.70 seemed to work... I
> haven't fully tried it yet.
>
> Is this problem known/identified/fixed yet, or do you
> want a more complete bug report ?

This seems to be an ACPI related problem on ALI 1533/1535 
compatible implementations frequently seen on Toshiba's.

As a workaround, Boot with ACPI=off and add --directisa to 
hwclock lines in rc.sysinit and halt (or their equivalents)

If this is really an Intel chipset it would be a first 

Please post your problem, solution and system info and lspci 
to ACPI list.

Regards
Michael

Re: 2.5.70 freezes when running hwclock

[Éric Brunet]

On Sat, May 31, 2003 at 06:41:47PM +0800, Michael Frank wrote:
> > I have tried 2.5.70 on an intel chipset based pc, and I
> > got a reproductible complete freeze during the boot
> > process when hwclock is run. Even Caps Lock wouldn't lit
> > the little led.
> This seems to be an ACPI related problem on ALI 1533/1535 
> compatible implementations frequently seen on Toshiba's.
> 
> As a workaround, Boot with ACPI=off and add --directisa to 
> hwclock lines in rc.sysinit and halt (or their equivalents)
> 
> If this is really an Intel chipset it would be a first 
> 
> Please post your problem, solution and system info and lspci 
> to ACPI list.

hwclock --directisa works indeed. ACPI is indeed configured in, and 
I haven't tried to boot with ACPI=off.

Computer is a shuttle SB51G with an intel 845G/845GL chipset.

-------------------- lspci ----------------------------------
00:00.0 Host bridge: Intel Corp. 82845G/GL [Brookdale-G] Chipset Host Bridge (rev 03)
00:02.0 VGA compatible controller: Intel Corp. 82845G/GL [Brookdale-G] Chipset Integrated Graphics Device (rev 03)
00:1d.0 USB Controller: Intel Corp. 82801DB USB (Hub #1) (rev 02)
00:1d.1 USB Controller: Intel Corp. 82801DB USB (Hub #2) (rev 02)
00:1d.2 USB Controller: Intel Corp. 82801DB USB (Hub #3) (rev 02)
00:1d.7 USB Controller: Intel Corp. 82801DB USB EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB PCI Bridge (rev 82)
00:1f.0 ISA bridge: Intel Corp. 82801DB ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corp. 82801DB ICH4 IDE (rev 02)
00:1f.3 SMBus: Intel Corp. 82801DB SMBus (rev 02)
00:1f.5 Multimedia audio controller: Intel Corp. 82801DB AC'97 Audio (rev 02)
01:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
01:07.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46)
01:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS)
------------------------------------------------------------------------------

I am not sure what is relevant about the RTC. Let's try this:

------------------ lspci -vvv -s 00:1f.0 -----------------------------
00:1f.0 ISA bridge: Intel Corp. 82801DB ISA Bridge (LPC) (rev 02)
        Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
------------------------------------------------------------------------

------------------- lspci -vvv -s 00:1f.3---------------------------
00:1f.3 SMBus: Intel Corp. 82801DB SMBus (rev 02)
        Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer: Unknown device fb50
        Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Interrupt: pin B routed to IRQ 5
        Region 4: I/O ports at 0500 [size=32]
--------------------------------------------------------------------

2.5.67 was working fine, with the same configuration.

Regards,

	Éric Brunet