Messages in this thread | | | Date | Mon, 28 Jul 2003 23:18:12 -0600 | From | "S. Anderson" <> | Subject | Re: OOPS 2.6.0-test2, modprobe i810fb |
| |
On Mon, Jul 28, 2003 at 08:26:00PM -0700, Andrew Morton wrote: > "S. Anderson" <sa@xmission.com> wrote: > > > > On Mon, Jul 28, 2003 at 06:18:07PM +0100, Pavel Rabel wrote: > > > Got this OOPS when trying "modprobe i810fb", > > > kernel 2.6.0-test2 > > > > > > > I am also getting this oops, or somthing very simmillar. > > yay! I finally fixed a bug! (sheesh, bad day). > > The device table is not null-terminated so we run off the end during > matching and go oops. >
Thanks, that fixes the oops Pavel reported!
But I now realize the oops I am getting is different...
It happens only if any of these "i810fb, i810_audio or intel-agp" are compiled in the kernel or insterted as modules.
i810fb, i810_audio or intel-agp load up fine and seem to all work properly. I only get the oops when I put a card into my cardbus slot.
this is what i think happens, when I put the card in, it sets off some functions that will try to get a driver for the card I just inserted. when it gets to the pci_bus_match function, my cards vendor and device numbers are tested against a drivers id_table. when that driver is "i810fb, i810_audio or intel-agp" (and i810fb, i810_audio or intel-agp is allready loaded) the id_table is at an address that cant be handled, thus cauing the oops. I am having trouble figuring out why pci_drv->id_table isnt valid in this case.
Any ideas?
Thanks, Shawn Anderson - 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/
| |