From: Terence Ripperda <tripperda@nvidia.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
Michael Geithe <warpy@gmx.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.8.1-mm2 (nvidia breakage)
Date: Thu, 19 Aug 2004 16:51:25 -0500 [thread overview]
Message-ID: <20040819215124.GA6114@hygelac> (raw)
In-Reply-To: <1092938035.28370.13.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]
the original bug report was during module load time, when we're
probing our devices via the pci_driver's probe callback. this is well
before we hook up interrupts or do anything in our closed source code.
I'm attaching a trimmed down version of our driver that pretty much
only does this probe (complete source is included). I don't know if
this will reproduce the original bug or not.
Let me know if I can help anymore.
Thanks,
Terence
On Thu, Aug 19, 2004 at 06:53:56PM +0100, alan@lxorguk.ukuu.org.uk wrote:
> On Iau, 2004-08-19 at 17:51, Bjorn Helgaas wrote:
> > I assume this problem is with the Nvidia binary-only driver? My guess
> > is that the driver doesn't call pci_enable_device() before using
> > pci_dev->irq. I don't have source for that driver, so I can't verify
> > this.
>
> An obvious test would be for someone with an Nvidia to write a little
> module that does nothing but pci_enable_device it. Load and unload that
> then see what happens
>
> -
> 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/
>
[-- Attachment #2: nv_mini.tar.gz --]
[-- Type: application/octet-stream, Size: 7676 bytes --]
next prev parent reply other threads:[~2004-08-19 21:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040819092654.27bb9adf.akpm@osdl.org>
2004-08-19 16:51 ` 2.6.8.1-mm2 (nvidia breakage) Bjorn Helgaas
2004-08-19 17:53 ` Alan Cox
2004-08-19 21:51 ` Terence Ripperda [this message]
2004-08-19 22:03 ` Bjorn Helgaas
2004-08-19 22:22 ` Alan Cox
2004-08-19 22:58 ` Terence Ripperda
2004-08-20 15:53 ` Bjorn Helgaas
2004-08-20 16:24 ` Michael Geithe
2004-08-20 19:04 ` Terence Ripperda
2004-08-23 15:30 ` Bjorn Helgaas
2004-08-23 19:01 ` Terence Ripperda
2004-08-24 15:26 ` Bjorn Helgaas
2004-08-24 17:22 ` Terence Ripperda
2004-08-24 17:36 ` Roland Dreier
2004-08-24 22:03 ` Terence Ripperda
2004-08-24 22:35 ` 2.6.8.1-mm2 (nvidia breakage) [u] Martin Schlemmer [c]
2004-08-24 5:17 2.6.8.1-mm2 (nvidia breakage) Michael Geithe
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=20040819215124.GA6114@hygelac \
--to=tripperda@nvidia.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bjorn.helgaas@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=warpy@gmx.de \
/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