Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267360AbUJWLm4 (ORCPT ); Sat, 23 Oct 2004 07:42:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267365AbUJWLmz (ORCPT ); Sat, 23 Oct 2004 07:42:55 -0400 Received: from ipx20189.ipxserver.de ([80.190.249.56]:58758 "EHLO ipx20189.ipxserver.de") by vger.kernel.org with ESMTP id S267360AbUJWLmu (ORCPT ); Sat, 23 Oct 2004 07:42:50 -0400 Date: Sat, 23 Oct 2004 14:41:18 +0300 (EAT) From: Zwane Mwaikambo To: Andrew Morton Cc: "Rafael J. Wysocki" , Linux Kernel Subject: Re: 2.6.9-mm1: NForce3 problem (IRQ sharing issue?) In-Reply-To: Message-ID: References: <200410222354.44563.rjw@sisk.pl> <20041022162656.2f9ca653.akpm@osdl.org> 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: 1830 Lines: 47 Cc for LKML, (damned NNTP client) On Sat, 23 Oct 2004, Zwane Mwaikambo wrote: > On Sat, 23 Oct 2004, Andrew Morton wrote: > > > "Rafael J. Wysocki" wrote: > > > > > > Hi, > > > > > > I have a problem with 2.6.9-mm1 on an AMD64 NForce3-based box. Namely, after > > > some time in X, USB suddenly stops working and sound goes off simultaneously > > > (it's quite annoying, as I use a USB mouse ;-)). It is 100% reproducible and > > > it may be related to the sharing of IRQ 5: > > > > > > rafael@albercik:~> cat /proc/interrupts > > > CPU0 > > > 0: 3499292 XT-PIC timer > > > 1: 7135 XT-PIC i8042 > > > 2: 0 XT-PIC cascade > > > 5: 6945 XT-PIC NVidia nForce3, ohci_hcd > > > 8: 0 XT-PIC rtc > > > 9: 1416 XT-PIC acpi, yenta > > > 10: 2 XT-PIC ehci_hcd > > > 11: 37266 XT-PIC SysKonnect SK-98xx, yenta, ohci1394, ohci_hcd > > > 12: 13781 XT-PIC i8042 > > > 14: 16 XT-PIC ide0 > > > 15: 23601 XT-PIC ide1 > > > NMI: 0 > > > LOC: 3498657 > > > ERR: 1 > > > MIS: 0 > > > > > > (NVidia nForce3 is a sound chip, snd_intel8x0). After it happens I can't > > > reboot the box cleanly (the ohci-hcd driver cannot be reloaded) and it does > > > not leave any traces in the log. > > > > > > > Beats me. Does the interrupt count stop increasing? > > Could we also get a dmesg and lspci? Boot with the 'debug' kernel > parameter. - 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/