From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 2 Aug 2001 23:38:03 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 2 Aug 2001 23:37:54 -0400 Received: from wb1-a.mail.utexas.edu ([128.83.126.134]:30737 "HELO mail.utexas.edu") by vger.kernel.org with SMTP id ; Thu, 2 Aug 2001 23:37:43 -0400 Message-ID: <3B697310.EF44BCDB@mail.utexas.edu> Date: Thu, 02 Aug 2001 21:34:40 +0600 From: "Bobby D. Bryant" Organization: (I do not speak for) The University of Texas at Austin (nor they for me). X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-ac2 i686) X-Accept-Language: en,fr,de MIME-Version: 1.0 To: linux-kernel@vger.kernel.org CC: Mike Frisch Subject: Re: "clock timer configuration lost" on ASUS A7A266 In-Reply-To: <20010802152921.A6242@saturn.tlug.org> Content-Type: multipart/mixed; boundary="------------94D54FB41D37AF03B7DAFD90" Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org This is a multi-part message in MIME format. --------------94D54FB41D37AF03B7DAFD90 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mike Frisch wrote: > Hardware: ASUS A7A266 (ALiMAGiK chipset), AMD T-Bird 1.2 GHz > Kernel: 2.4.7-ac2 > > 'dmesg' frequently reports: > > probable hardware bug: clock timer configuration lost - probably a VIA686a motherboard. > probable hardware bug: restoring chip configuration. Just FYI, I see the same thing on the same board. My lspci -vv is also attached. Ask if you need more. Bobby Bryant Austin, Texas --------------94D54FB41D37AF03B7DAFD90 Content-Type: text/plain; charset=us-ascii; name="temp.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="temp.txt" 00:00.0 Host bridge: Acer Laboratories Inc. [ALi]: Unknown device 1647 (rev 04) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Capabilities: [a4] Power Management version 1 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:01.0 PCI bridge: Acer Laboratories Inc. [ALi] M5247 (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- SERR- Reset- FastB2B- 00:04.0 IDE interface: Acer Laboratories Inc. [ALi] M5229 IDE (rev c4) (prog-if fa) Subsystem: Asustek Computer, Inc.: Unknown device 8053 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- [disabled] [size=64K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:0b.0 Unknown mass storage controller: Promise Technology, Inc. 20267 (rev 02) Subsystem: Promise Technology, Inc.: Unknown device 4d33 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- [disabled] [size=64K] Capabilities: [58] Power Management version 1 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:0d.0 Serial controller: US Robotics/3Com 56K FaxModem Model 5610 (rev 01) (prog-if 02 [16550]) Subsystem: US Robotics/3Com: Unknown device 00d7 Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR-