Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262474AbVAEQJB (ORCPT ); Wed, 5 Jan 2005 11:09:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262498AbVAEQGO (ORCPT ); Wed, 5 Jan 2005 11:06:14 -0500 Received: from fsmlabs.com ([168.103.115.128]:39646 "EHLO fsmlabs.com") by vger.kernel.org with ESMTP id S262510AbVAEQEy (ORCPT ); Wed, 5 Jan 2005 11:04:54 -0500 Date: Wed, 5 Jan 2005 09:05:11 -0700 (MST) From: Zwane Mwaikambo To: Martin Drab cc: Linux Kernel Mailing List Subject: Re: APIC/LAPIC hanging problems on nForce2 system. In-Reply-To: Message-ID: References: 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: 1452 Lines: 31 On Wed, 5 Jan 2005, Martin Drab wrote: > I'm witnessing a total freeze on my system when the APIC and LAPIC are > enabled in kernel 2.6.10-bk7. > > The feeze seems to occur whenever there is some heavy interrupt occurance, > usually high network communication load, or high HDD activity. The freeze > does not occur after constant time during the heavy interrupt load, but it > ALLWAYS occurs, and allways after quite a short time. The freeze is total, > I mean nothing reacts, then, even the cursor on the HW text console stops > blinking. Only cold reset helps. > > The problem disappears when I turn off APIC and LAPIC (by the "noapic > nolapic" commands at the kernel boot command line). I tried to turn off > only APIC (i.e., only "noapic"), at first it seemd to be working, but it > frozen anyway, only a bit later. I also tried to turn off only the LAPIC > (i.e., only "nolapic"), but then my HDD was loosing interrupts, so the > system didn't even boot. > > I also tried the native kernel from MDK 10.1 i586, i.e. 2.6.8.1-12mdk and > it works without any problem with both APIC and LAPIC enabled. > > Does anybody have a clue what could be wrong? I'm assuming that 2.6.10 is ok? - 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/