From: "Preston A. Elder" <prez@goth.net>
To: Dave Jones <davej@redhat.com>, "Preston A. Elder" <prez@goth.net>,
linux-kernel@vger.kernel.org
Subject: Re: AGPGart / AMD K7
Date: Fri, 20 Apr 2007 12:53:31 -0400 [thread overview]
Message-ID: <4628F00B.3010304@goth.net> (raw)
In-Reply-To: <20070420155537.GA20118@redhat.com>
Dave Jones wrote:
> try adding some instrumentation to __pci_register_driver and the functions
> it calls.
>
> oh, one thought.. do you have CONFIG_PCI_MULTITHREAD_PROBE set?
> I'm wondering if the probing is racing with another driver which is claiming
> the same PCI ID. (Edac, or watchdog for example)
>
Dave,
Multithread is not set.
Here is the output of my instrumentation:
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: DEBUG 0
agpgart: DEBUG 1
__pci_register_driver: In function
__pci_register_driver: driver = agpgart-amdk7, multithread = 0
__pci_register_driver: Before Spinlock
__pci_register_driver: Before List Init
__pci_register_driver: Before Driver Register
__pci_register_driver: Error = 0
__pci_register_driver: Returning 0
The DEBUG 0 and 1 are coming from agp_amdk7_init()
There is a DEBUG 2 at the top of agp_amdk7_probe(), even before
pci_find_capability, but the function never gets called.
I assume an error of 0 means no conflict. Any further steps to take for
this? I would really like my AGP working :S
Especially since lspci obviously detects it, even tells me it supports
1x, 2x and 4x.
PreZ :S
next prev parent reply other threads:[~2007-04-20 16:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 7:10 AGPGart / AMD K7 Preston A. Elder
2007-04-20 15:55 ` Dave Jones
2007-04-20 16:53 ` Preston A. Elder [this message]
2007-04-20 17:33 ` Dave Jones
2007-04-20 18:04 ` Preston A. Elder
2007-04-20 18:20 ` Dave Jones
2007-04-20 18:29 ` Greg KH
2007-04-20 19:00 ` Dave Jones
2007-04-20 23:26 ` Greg KH
2007-04-21 0:33 ` Dave Jones
2007-04-20 18:31 ` Preston A. Elder
2007-04-20 18:49 ` Dave Jones
2007-04-20 20:22 ` Preston A. Elder
2007-04-20 20:33 ` Dave Jones
2007-04-20 22:00 ` Preston A. Elder
2007-04-20 23:42 ` Preston A. Elder
2007-04-21 0:15 ` Greg KH
2007-04-20 23:25 ` Greg KH
[not found] <fa.asou3h2GKTshe+XpxGJ/K4Wjf2s@ifi.uio.no>
[not found] ` <fa.YcM0QJJYQHgI9i0mZF4z2OtPhr8@ifi.uio.no>
[not found] ` <fa.8rayS7oJHYA3XGzEX9anUebRoMM@ifi.uio.no>
[not found] ` <fa.2SB7j6GjGOW6vvgLY7nbvSnuM6I@ifi.uio.no>
[not found] ` <fa.v7TywLl5PsPHzpOETJp8xq50Gno@ifi.uio.no>
[not found] ` <fa.S5WSCyOavqOFWClpzzJKcKpj03M@ifi.uio.no>
2007-05-03 9:35 ` John Sigler
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=4628F00B.3010304@goth.net \
--to=prez@goth.net \
--cc=davej@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.