Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264261AbUD0S1z (ORCPT ); Tue, 27 Apr 2004 14:27:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264260AbUD0SZa (ORCPT ); Tue, 27 Apr 2004 14:25:30 -0400 Received: from mailhst2.its.tudelft.nl ([130.161.34.250]:51185 "EHLO mailhst2.its.tudelft.nl") by vger.kernel.org with ESMTP id S264296AbUD0SYi (ORCPT ); Tue, 27 Apr 2004 14:24:38 -0400 Date: Tue, 27 Apr 2004 20:24:25 +0200 (METDST) From: Arjen Verweij Reply-To: a.verweij@student.tudelft.nl To: Len Brown cc: Ross Dickson , Jesse Allen , "Prakash K. Cheemplavam" , Craig Bradney , , , "Maciej W. Rozycki" , Jamie Lokier , Daniel Drake , Ian Kumlien , Allen Martin Subject: Re: IO-APIC on nforce2 [PATCH] + [PATCH] for nmi_debug=1 + [PATCH] for idle=C1halt, 2.6.5 In-Reply-To: <1083088854.2322.38.camel@dhcppc4> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2562 Lines: 71 Len, I don't think that the CPU model has much to do with anything, it is pretty much chipset related. My last remark about buying you a mobo for debugging purposes was a vain attempt at humor. I'm just surprised of the lack of support the vendors and NVIDIA/AMD are giving. I realise that Linux may be only a marginal part of the market for those companies so it is not commercially justifiable to invest a lot of time in this. We all appreciate whatever input you may have, because a solution without indepth knowledge of how ACPI/APIC code handles stuff is probably needed to tackle this issue. All I can do is gather info, and I'm currently thinking of a plan to get the info we need. Regards, Arjen On 27 Apr 2004, Len Brown wrote: > On Tue, 2004-04-27 at 13:02, Arjen Verweij wrote: > > > After having his box run with cat /dev/hda > /dev/null for a night > > straight no lockup has occured. The brand of his motherboard is Shuttle. > > My shuttle is a FN41 board in a SN41G2 system. > > I found "rev 1.0" BIOS (FN41S00X of 12/18/2002) on Shuttle's ftp site > and downgraded to that, but still no hang. > > It may be this board never hangs no matter what, > or perhaps C1 disconnect was simply disabled in that BIOS > b/c there was no option for it in Advanced Chipset Features > like there is for the most recent BIOS. > > Other things about my board. > I run "optimized defaults", I don't overclock anything. > Processor is an AMD XP 2200+ > Does anybody else see the hang with this processor model? > I wonder if the hang is processor model or speed dependent? > > > Does anyone have some input on how to tackle this problem? > > Unfortunately I don't have tools for debugging nvidia + amd hardware. > I would expect that those companies do, however. So encouraging them > to reproduce the hang internally may be the best way to go. > > > buy Len the cheapest broken nforce2 board I can find at pricewatch.com and > > have it shipped to his house :) > > I got tangled in this b/c this board (actually, the reference BIOS for > this chipset) had some unusual ACPI related failures. If the failures > turn out to be related to ACPI, I'll do what I can to help. But I > expect that hardware debugging tools may be necessary before the > hang issue is completely explained and solved. > > -Len > > > - 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/