public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kevin O'Shea" <mastergoon@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: nvidia oops 2.6.8-rc3-mm2
Date: Sun, 8 Aug 2004 21:07:52 -0700	[thread overview]
Message-ID: <bec878da04080821071647a846@mail.gmail.com> (raw)
In-Reply-To: <cone.1092022093.780511.26660.502@pc.kolivas.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)
[<c0232bdb>] kobject_register+0x5b/0x60
[<c028dd00>] bus_add_driver+0x50/0xd0
[<c028e31f>] driver_register+0x2f/0x40
[<c023daec>] pci_register_driver+0x5c/0x90
[<e10bb00f>] svia_init+0xf/0x1d [sata_via]
[<c013157e>] sys_init_module+0x12e/0x280
[<c0104135>] 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 <kernel@kolivas.org> 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:
> >  [<c0114375>] 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
> 
>

      reply	other threads:[~2004-08-09  4:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-09  2:36 [BUG?] nvidia oops 2.6.8-rc3-mm2 Kevin O'Shea
2004-08-09  2:48 ` Jesse Stockall
2004-08-09  3:28 ` Con Kolivas
2004-08-09  4:07   ` Kevin O'Shea [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bec878da04080821071647a846@mail.gmail.com \
    --to=mastergoon@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox