Possibly a device should be able to have more than one driver
associated with it - so the AGP driver and EDAC could both use the
device in question here (though this would probably be a sizable change).
Either way, at least I found the culprit :)
PreZ :)
Preston A. Elder wrote:
> Dave Jones w
Dave Jones wrote:
> On Fri, Apr 20, 2007 at 04:22:06PM -0400, Preston A. Elder wrote:
> > Dave, Greg,
> >
> > Here is the trace with 2.6.20.6
> >
> > I added back in my trace code, as you see. As you can also see,
> > agp_amdk7_probe is
.
Everything looks successful, too :(
I will try with 2.6.21rc7, but I don't hold out too much hope.
PreZ
Dave Jones wrote:
> On Fri, Apr 20, 2007 at 02:31:01PM -0400, Preston A. Elder wrote:
>
> > Here is the code for __pci_register_driver:
> > ...
> >
> > So in
Dave Jones wrote:
> On Fri, Apr 20, 2007 at 02:04:45PM -0400, Preston A. Elder wrote:
> > Dave Jones wrote:
> > > On Fri, Apr 20, 2007 at 12:53:31PM -0400, Preston A. Elder wrote:
> > >
> > > > Linux agpgart interface v0.101 (c) Dave Jones
> > >
Dave Jones wrote:
> On Fri, Apr 20, 2007 at 12:53:31PM -0400, Preston A. Elder wrote:
>
> > Linux agpgart interface v0.101 (c) Dave Jones
> > agpgart: DEBUG 0
> > agpgart: DEBUG 1
> > __pci_register_driver: In function
> > __pci_register_driver: dri
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
Hi,
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.
Hi,
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.
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 Jones wrote:
On Fri, Apr 20, 2007 at 12:53:31PM -0400, Preston A. Elder wrote:
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
Dave Jones wrote:
On Fri, Apr 20, 2007 at 02:04:45PM -0400, Preston A. Elder wrote:
Dave Jones wrote:
On Fri, Apr 20, 2007 at 12:53:31PM -0400, Preston A. Elder wrote:
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: DEBUG 0
agpgart: DEBUG 1
.
Everything looks successful, too :(
I will try with 2.6.21rc7, but I don't hold out too much hope.
PreZ
Dave Jones wrote:
On Fri, Apr 20, 2007 at 02:31:01PM -0400, Preston A. Elder wrote:
Here is the code for __pci_register_driver:
...
So in the above case, we ARE saying
Dave Jones wrote:
On Fri, Apr 20, 2007 at 04:22:06PM -0400, Preston A. Elder wrote:
Dave, Greg,
Here is the trace with 2.6.20.6
I added back in my trace code, as you see. As you can also see,
agp_amdk7_probe is still not called.
Try looking down in __driver_attach
to have more than one driver
associated with it - so the AGP driver and EDAC could both use the
device in question here (though this would probably be a sizable change).
Either way, at least I found the culprit :)
PreZ :)
Preston A. Elder wrote:
Dave Jones wrote:
On Fri, Apr 20, 2007 at 04:22
14 matches
Mail list logo
