Re: OOPS 2.6.0-test4 repeatable

Russell King
2003-08-25T10:55:43Z

On Mon, Aug 25, 2003 at 12:25:04PM +0200, Mario Mikocevic wrote:
> On 2003.08.25 11:40, Russell King wrote:
> > On Mon, Aug 25, 2003 at 11:18:46AM +0200, Mario Mikocevic wrote:
> > > IBM Thinkpad R40 with 2.6.0-test4, alsa compiled as module.
> > > If I plug in D-link DWL-650+ (_just_ a plug in a slot) and _then_
> > > modprobe snd-intel8x0 within seconds this oops barfs on me.
> >
> > After asking akpm what an "invalid operand" on x86 means, he says its
> > a BUG() statement. So, can you please supply both the ksymoops'd
> > *and* the raw undecoded kernel messages. Apparantly ksymoops cuts off
> > the lines which indicate that it was a bug and where the BUG() statement
> > was.

Ok so it isn't a BUG(). The next thing I'd consider is whether it was
a corrupted pci driver list, but it doesn't look like it.

Ok, lets try to get some extra info from your kernel - please apply
the patch below. This is likely to produce a fair amount of extra
messages at boot. It should also produce another raft of messages
when you insert the cardbus card but before the module, and another
raft afterwards.

I'm only interested in the ones around the time when you insert the
cardbus card and the module.

--- linux/drivers/pci/pci-driver.c.old Mon Aug 25 11:51:03 2003
+++ linux/drivers/pci/pci-driver.c Mon Aug 25 11:52:59 2003
@@ -66,7 +66,8 @@
{
int error = -ENODEV;
const struct pci_device_id *id;
-
+printk("pci_dev: %s driver: %p ", pci_name(pci_dev), drv);
+printk("name: %s table: %p probe: %p\n", drv->name, drv->id_table, drv->probe);
if (!drv->id_table)
return error;
id = pci_match_device(drv->id_table, pci_dev);