From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263258AbTJUSKN (ORCPT ); Tue, 21 Oct 2003 14:10:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263259AbTJUSKN (ORCPT ); Tue, 21 Oct 2003 14:10:13 -0400 Received: from azgamers.com ([68.98.208.145]:31891 "HELO azgamers.com") by vger.kernel.org with SMTP id S263258AbTJUSKG (ORCPT ); Tue, 21 Oct 2003 14:10:06 -0400 From: "Matt H." To: linux-kernel@vger.kernel.org Subject: Re: nforce2 random lockups - still no solution ? Date: Tue, 21 Oct 2003 11:13:00 -0700 User-Agent: KMail/1.5.9 References: <3F95748E.8020202@tuwien.ac.at> In-Reply-To: <3F95748E.8020202@tuwien.ac.at> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200310211113.00326.lkml@lpbproductions.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Turn off apic in the bios.. it should then work well .. On Tuesday 21 October 2003 11:01 am, Samuel Kvasnica wrote: > Hello, > > Last few weeks I spent quite much time trying to get working two nforce2 > chipset based motherboards with latest linux 2.4.22 - ASUS A7N8 Deluxe > 2.0 and > MSI K7N2 Delta. Althought the latest kernel version already detects > correctly all the nforce2 stuff and APIC seems to run work as well, > some random lockups still remain. At the very beginning I believed I > could get rid of lockups by setting lower udma mode on IDE (hdparm -X > udma3). > In the fact this only reduced very much the probability of lockups - > with udma5 I could freeze the system within few minutes e.g. during > kernel compilation. > with udma3 system is usually stable for several days, but sometimes it > locks. When it happens, it happens mostly during first 30 mins after boot. > I'm booting with noapic, nolapic and acpi=off, but it doesn't seem to > have really any effect on lockups. > Unfortunatelly, I can't get any debug info. I've redirected syslog to > flash-card but didn't get even a bit more of info, it seems to blow-up > the chipset completelly and immediatelly. > > Now, in the system with MSI K7N2 motherboard I have a framegrabber > (Hauppauge PVR-250) installed, using ivtv driver. > I'm able to lock-up the system when streaming uncompressed video (e.g. > cat /dev/yuv0 >/dev/null) and the lockups are also hard, w/o debug info. > The ivtv driver is using DMA very heavily but seems to work on other > chipsets. So these lock-up problems might be rather DMA then APIC related. > Interesting is that I've never had such a lock-up when running WinXP on > same computer ( :-) seems impossible), even under load and with the > framegrabber. > I've run memtest on both machines for 24 hours, it shouldn't be bad > memory. On both machines I'm using just onboard hardware, except for the > AGP graphic card > (matrox and nvidia) and the framegrabber. Hard disk is on parallel IDE, > SATA controller is disabled. > > So my conclusion is that the nforce2 lock-ups are still unsolved at the > moment. Any nforce experts around ? > > Please, reply directly using cc:, I'm not on the list. > > thanks, > > Sam > > > > - > 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/