On Wed, 28 Nov 2001 14:58, Deryk Barker wrote: > I'm running Mdk 7.2 (I'm waiting for a quiet few days to upgrade) on a > dual Celeron 400 w 256MB RAM. > > Until recently it has been very stable, but in the last week or so it > keeps freezing up (or so I initially thought) every night. I'd come in > in the morning and find a motionless screensaver and nmo repsonse to > any stimulus. > > However, taking a closer look at the logs, I find this happening > regularly: > > Nov 26 04:00:00 jupiter CROND[12179]: (root) CMD > (/usr/share/msec/security.sh) Nov 26 04:00:00 jupiter CROND[12180]: (root) > CMD ( /sbin/rmmod -as) Nov 26 04:00:02 jupiter kernel: Kernel panic: > SUPERMOUNT panic (device 0/3): supermount_put_write_access: filesystem not > write accessed > > Now, rmmod seems to run regularly without bringing the system down, so > I'm assuming the problem stems from the running of security.sh > > The only think I can think is that we did have a power outage here > before this started happening (although whether immediately before I > don't recall) and there's a small possiblity that some file has become > corrupt - although an rpm -V msec doesn't seem to show anything > significant. > > If anyone has any suggestions as to where to look next, I'd be happy > to hear them.
Try running the security.sh script by itself to determine if that is what causes the crash. Then have a look in the script itself, and add an exit to it at various stages to weed out exactly where it's crashing. My feeling is that as rmmod and security.sh are running at the same time, rmmod might be removing a module that alllows access to some partition that security.sh is trying to access - security.sh causes the kernel to try and load that module, while rmmod is removing it, causing a panic .. ? Just a guess. t -- PGP key : http://n12turbo.com/tarragon/public.key
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
