All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "Preston A. Elder" <prez@goth.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AGPGart / AMD K7
Date: Fri, 20 Apr 2007 11:55:37 -0400	[thread overview]
Message-ID: <20070420155537.GA20118@redhat.com> (raw)
In-Reply-To: <46286775.5000507@goth.net>

On Fri, Apr 20, 2007 at 03:10:45AM -0400, Preston A. Elder wrote:
 
 > I have a Tyan Thunder K7x Pro (S2469) and the amd-k7-agp module does not
 > seem to be probing my AGP device.  I have even tried putting debugging
 > code into the amd-k7-agp module, and sure enough I can see it being
 > loaded, but the probe function is never called.  This is with kernel 2.6.19.

This is the second report of this I've heard, and I really have no good
explanation for it.

 > As you can see, the first device is indeed showing up as AGP capable and
 > such, its just never probed (at least the probe function in amd-k7-agp
 > is never called once the module is loaded).
 > 
 > To simplefy things, here is a pcitweak -l of the top two devices above:
 > PCI: 00:00:0: chip 1022,700c card 0000,0000 rev 20 class 06,00,00 hdr 00
 > PCI: 00:01:0: chip 1022,700d card 0000,0000 rev 00 class 06,04,00 hdr 01
 > 
 > In the amd-k7-agp code, this is in the device list:
 >     {
 >     .class      = (PCI_CLASS_BRIDGE_HOST << 8),
 >     .class_mask = ~0,
 >     .vendor     = PCI_VENDOR_ID_AMD,
 >     .device     = PCI_DEVICE_ID_AMD_FE_GATE_700C,
 >     .subvendor  = PCI_ANY_ID,
 >     .subdevice  = PCI_ANY_ID,
 >     },
 > 
 > Which matches the first device.  So I'm completely unsure as to why this
 > device is never probed or how to fix it.

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

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2007-04-20 15:56 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 [this message]
2007-04-20 16:53   ` Preston A. Elder
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=20070420155537.GA20118@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prez@goth.net \
    /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.