I'll go along with that. I was about to submit a report about this but then saw this thread. I have noticed the system will degrade in the same way if my parprt Zip drive is attached after the system has booted. When installing 8.2 / Cooker I had the Zip drive attached. Having never done this before I wanted to see what difference it actually makes. Any modprobing and super mounting therefore was put in place by the stock install procedure and it does use Supermount.
Owen On Friday 12 Apr 2002 6:59 pm, you wrote: > On Friday 12 April 2002 10:50 am, Borsenkow Andrej wrote: > > χ πΤΞ, 12.04.2002, Χ 21:30, Alan ΞΑΠΙΣΑΜ: > > > This is pretty nasty. > > > > > > This is using the stock kernel from Mandrake 8.2. I expect that > > > similar problems exist in the cooker version. > > > > > > What happens is that after some indeterminate time period, the system > > > does not allow you to start new processes. Already existing processes > > > run, but new processes will not start and you cannot restart new > > > processes. Shutting down cannot happen because you can't start the > > > shutdown script! > > > > > > After looking through the logs, I think I have found the cause of the > > > problem. It appears that devfs is dying. It kills enough of the kernel > > > to not work correctly, but not enough of the kernel to choke all > > > together. (Enough to be frustrating.) It looks like the lethal > > > combination is a remountable ide-scsi device, but that is only a guess > > > at this point. > > > > What device? Is it supermounted read-write? > > I believe it is the zip drive that it is choking in. The oops happens in > scan_dir_for_removable(). (The only removable devices are two scsi cd-rom > drives and an ide Zip drive. The zip drive is the only one that gets > classed as "removable" to my knowledge.) > > I assume it is supermounted as read/write. It is a fresh install of 8.2 > with no real changes to devices. (I have been too busy coding to modify > the system too much.)
