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

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

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, nobody