Re: OOPS REPORT: Will someone _please_ look at this? (was Re: BUG & OOPS REPORT: /proc/scsi/ entries not properly cleaned up)

2000-10-10 Thread Douglas Gilbert
Matthew Dharm wrote: > > Yet more followup with myself I can reproduce this problem on > 2.4.0-test10-pre1 every time. I'm using the ide-scsi and usb-storage > modules to trigger the bug -- loading and then unloading either one causes > /proc/scsi to not be cleaned up properly. > > As yet,

OOPS REPORT: Will someone _please_ look at this? (was Re: BUG & OOPS REPORT: /proc/scsi/ entries not properly cleaned up)

2000-10-10 Thread Matthew Dharm
Yet more followup with myself I can reproduce this problem on 2.4.0-test10-pre1 every time. I'm using the ide-scsi and usb-storage modules to trigger the bug -- loading and then unloading either one causes /proc/scsi to not be cleaned up properly. As yet, nobody has indicated to me that they

Re: BUG & OOPS REPORT: /proc/scsi/ entries not properly cleaned up

2000-10-02 Thread Matthew Dharm
Following up yet some more with myself... is anyone actually looking at this stuff? I can provide even more information if desired, but I'd really like to know that at least one person who understands this code is looking at it Anyway, I managed to get a better OOPS trace. Here it is: ksym

Re: BUG & OOPS REPORT: /proc/scsi/ entries not properly cleaned up

2000-10-01 Thread Matthew Dharm
Just to follow-up to my own post, I have some more datapoints... The bug definatley seems to be in either the SCSI layer or the procfs layer. The behavior is the same if I use either ide-scsi or usb-storage, which are the only two SCSI modules I can test. Matt On Fri, Sep 29, 2000 at 03:19:23P