From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265249AbUHIEIB (ORCPT ); Mon, 9 Aug 2004 00:08:01 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265211AbUHIEIB (ORCPT ); Mon, 9 Aug 2004 00:08:01 -0400 Received: from rproxy.gmail.com ([64.233.170.195]:56168 "EHLO mproxy.gmail.com") by vger.kernel.org with ESMTP id S265249AbUHIEH4 (ORCPT ); Mon, 9 Aug 2004 00:07:56 -0400 Message-ID: Date: Sun, 8 Aug 2004 21:07:52 -0700 From: "Kevin O'Shea" To: LKML Subject: Re: nvidia oops 2.6.8-rc3-mm2 In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org That fixed it. I now have a new error in my dmesg however (thought I'd add it here incase its related): kobject_register failed for sata_via (-17) [] kobject_register+0x5b/0x60 [] bus_add_driver+0x50/0xd0 [] driver_register+0x2f/0x40 [] pci_register_driver+0x5c/0x90 [] svia_init+0xf/0x1d [sata_via] [] sys_init_module+0x12e/0x280 [] sysenter_past_esp+0x52/0x71 Thanks for the help so far! Kevin O'Shea MyUID.com On Mon, 09 Aug 2004 13:28:13 +1000, Con Kolivas wrote: > Kevin O'Shea writes: > > > I hope its ok to post about this here, but I thought it might be a > > kernel bug not nvidia. > > > > This is the oops with the new 6111 driver (it worked fine on mm1). > > > > Thanks, > > Kevin > > > Call Trace: > > [] io_apic_set_pci_routing+0x1e5/0x210 > > I quote from akpm's announcement: > > - If some devices mysteriously stop working, try booting with pci=routeirq. > If that fixes it, please send a report, Cc'ing bjorn.helgaas@hp.com. See > remove-unconditional-pci-acpi-irq-routing.patch > > That looks like it might help your issue too since the oops talks about pci > routing. > > Cheers, > Con > >