Re: [BUGREPORT] 2.2.10-ac10: oops+panic when interrupting cdrecord

Bert Lindner (bert@box.balpol.tudelft.nl)
Fri, 16 Jul 1999 02:10:00 +0200 (CEST)


> Slab poisoning catches another victim.
>
> > >>EIP: c0110338 <__wake_up+1c/48>
> > Trace: c485f178 <cleanup_module+135ac/180f4>
> > Trace: c485ef5c <cleanup_module+13390/180f4>
> > Trace: c48107d3 <scsi_old_done+57b/588>
> > Trace: c4820d6d <sym53c8xx_intr+69/78>
> > Trace: c0109f69 <handle_IRQ_event+31/68>
>
> And that would seem to be in the sym53c8xx driver when unloaded. Gerard?
> I think that you will not have any trouble if you compile the driver
> into your kernel instead of as a module.

I just tried that, and the problem remained. Putting the sym53c8xx driver
into the kernel but keeping SCSI disk/CD/generic support as modules led to
weird things: disk not recognized, two versions of 'scsi' (identical
file entries) in /proc/scsi.

This might be my mistake, however, because I hadn't removed the old
modules before installing the new ones.

In the end I put the whole SCSI subsystem IN the kernel. This time I
did remove the old modules. I only thought of the old modules after having
build an all static SCSI sub system, otherwise I wouldn't have changed
both factors at once, sorry. Now the same happened: oops after
interrupting a cdrecord dummy recording session.

You want me to write down another oops? Only I probably won't have time
for that before Sunday...

Regards,

-Bert.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/