Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751051AbVIMDiQ (ORCPT ); Mon, 12 Sep 2005 23:38:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751049AbVIMDiP (ORCPT ); Mon, 12 Sep 2005 23:38:15 -0400 Received: from [204.13.84.100] ([204.13.84.100]:46394 "EHLO stargazer.tbdnetworks.com") by vger.kernel.org with ESMTP id S1750774AbVIMDiP (ORCPT ); Mon, 12 Sep 2005 23:38:15 -0400 Date: Mon, 12 Sep 2005 20:38:14 -0700 To: Linus Torvalds Cc: linux-kernel@vger.kernel.org Subject: Re: 2.6.13.1 locks machine after some time, 2.6.12.5 work fine Message-ID: <20050913033814.GA879@tbdnetworks.com> References: <1126569577.25875.25.camel@defiant> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="nFreZHaLTZJo0R7j" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i From: Norbert Kiesel Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 13676 Lines: 254 --nFreZHaLTZJo0R7j Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, diff is appended. Regarding the -rc3 and friends, currently I can't as I jumped directly from 12.5 to 13. This is my desktop at work, so I try to keep it somewhat stable. However, if you have a guess which versions to try, I can give it a spin. It takes some time though to test, as the lockup normally only happens after 1 hour or so (although I could propably speed this up by doing lots of disk IO). Best, Norbert On Mon, Sep 12, 2005 at 08:00:24PM -0700, Linus Torvalds wrote: > > > On Mon, 12 Sep 2005, Norbert Kiesel wrote: > > > > I append the lspci -vvv from both 2.6.12.5 and 2.6.13.1 The diff > > between these two is: > > Can you do "lspci -vvx" instead (the numbers are actually meaningful: > they say what the hardware has been told, while the symbolic info contains > some stuff that lspci actually gathered through other means by querying > the kernel). > > Also, "diff -U 50 working broken" is a really nice way to show not only > the differences - it gives enough context that you can see all the > relevant info from the diff, and you don't even need to show the two > different versions separately (ie the diff itself ends up containing > pretty much all relevant info). > > Finally - if you can try to pinpoint it somewhat more (eg "2.6.13-rc3 is > ok, -rc4 is not"), that would be very helpful.. > > Linus > --nFreZHaLTZJo0R7j Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=diff-U50 --- 2.6.12.5/lspci-vvx 2005-09-12 20:26:21.000000000 -0700 +++ 2.6.13.1/lspci-vvx 2005-09-12 20:29:05.000000000 -0700 @@ -1,62 +1,62 @@ 0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 02) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- - Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- -00: 06 11 05 03 06 00 10 a2 02 00 00 06 00 00 00 00 +00: 06 11 05 03 06 00 10 22 02 00 00 06 00 00 00 00 10: 08 00 00 e0 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Reset- FastB2B- Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00: 06 11 05 83 07 00 30 22 00 00 04 06 00 00 01 00 10: 00 00 00 00 00 00 00 00 00 01 01 00 90 90 00 00 20: 00 e4 f0 e5 00 d0 f0 df 00 00 00 00 00 00 00 00 30: 00 00 00 00 80 00 00 00 00 00 00 00 00 00 0c 00 0000:00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 22) Subsystem: VIA Technologies, Inc. VT82C686/A PCI to ISA Bridge 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- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00: 02 10 60 59 07 00 b0 02 01 00 00 03 08 20 80 00 10: 08 00 00 d0 01 90 00 00 00 00 00 e5 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 87 17 60 59 30: 00 00 00 00 58 00 00 00 00 00 00 00 05 01 08 00 0000:01:00.1 Display controller: ATI Technologies Inc: Unknown device 5940 (rev 01) Subsystem: Hightech Information System Ltd.: Unknown device 5961 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR-