[Prev][Next][Index][Thread]
Re: oops....
On Thu, 31 Oct 1996, Jonathan Ben-Avraham wrote:
> > Oct 31 11:53:44 bit kernel: Cannot read proc file system.
> > Oct 31 11:54:14 bit last message repeated 90021 times
> > Oct 31 11:55:15 bit last message repeated 175841 times
> > Oct 31 11:56:16 bit last message repeated 173583 times
> > Oct 31 11:57:18 bit last message repeated 180054 times
> > Oct 31 11:57:29 bit last message repeated 34685 times
> >
> >
> > ahem... ls /proc looks just fine, anyone?! before my messages blows beyond
> > proportions?!
> >
> I have never seen this one before. What do you have /proc mounted on?
> Does it have enough space? If you don't have a real /proc partition,
> what does your df look like? Is there enough space? Did you recently
> add RAM? Try rebooting, else reformat /proc partition. Is /proc mounted
> correctly during the boot sequence? Is your /etc/fstab corrupted? Did
> you change the number of SCSI drives so that /proc that was mounted on
> /dev/sdb1 should now really be mounted on /dev/sda1?
>
> If any of the above are the reason then you owe me a lollypop.
I tryed rebooting, and it never came back, but not knowing the cause is
only HALF a solution... so no lolly for you! I forgot to mention... all
that time klogd took 50-60% of the CPU according to TOP, could it be that
by some weird "magic circle" the busy CPU made accesses to /proc slower
thus making klogd timeout all the time and retry, and so add more weight
on the poor CPU etc.? humm...
-------------------------------------------------------------
Ira Abramov <ira@scso.com> Scalable Solutions
SITE Web Presence ("webspace for rent") http://www.site.co.il
Beeper 91826 at 058-212121 FAX (972)2-643-0471
POBox 3600, Jerusalem 91035, Israel Tel (972)2-642-6822
http://www.scso.com/~ira Check out: http://www.linux.org.il
References: