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() > The fact that we're not calling the ->probe function is quite bizarre. > > It could be this in __driver_attach > > if (!dev->driver) > driver_probe_device(drv, dev); > > Though that'd be odd. > > Putting a #define DEBUG 1 in drivers/base/dd.c may also yield some clues. > > Dave > > OK, I found it!
Here is more trace: Linux agpgart interface v0.101 (c) Dave Jones agp_amdk7_init: In function agp_amdk7_init: Before pci_register_driver __pci_register_driver: In Function (driver = agpgart-amdk7, multithread = 0) __pci_register_driver: Before Spinlock __pci_register_driver: Before Init List Head __pci_register_driver: Before driver_register bus_add_driver: In Function (c0492920) bus_add_driver: Before kobject_set_name bus_add_driver: error = 0 bus_add_driver: Before kobject_register bus_add_driver: error = 0 bus_add_driver: Before driver_attach __driver_attach (0000:00:00.0,1): Before Down (parent) (c21c8600) __driver_attach (0000:00:00.0, 1): Before Down __driver_attach (0000:00:00.0, 1): Before Probe Device (c049fe54) __driver_attach (0000:00:00.0, 1): alreay registered with driver amd76x_edac __driver_attach (0000:00:00.0, 1): Before Up __driver_attach (0000:00:00.0, 1): Before Up (parent) (c21c8600) __driver_attach (0000:00:00.0, 1): Returning 0 bus_add_driver: error = 0 bus_add_driver: Before klist_add_tail bus_add_driver: Before module_add_driver bus_add_driver: Before driver_add_attrs bus_add_driver: error = 0 bus_add_driver: Before add_bind_files bus_add_driver: error = 0 bus_add_driver: Returning 0 __pci_register_driver: error = 0 __pci_register_driver: Before pci_create_newid_file __pci_register_driver: error = 0 __pci_register_driver: Returning 0 I snipped some since __driver_attach is called many times. But the long and short is that 00:00:00 is already associated with the 'amd76x_edac' driver, and as such will not call the agp probe call. What is this edac, btw? PreZ :) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/