On Wed, 20 Jun 2001, Justin Guyett wrote:
> the offending process is memeat (allocates 192*1024*1024 bytes, then
> memsets it to 0, then sleeps forever, though apparently it never gets to
> that part). It has to be in memset(ptr, 0, 192*1024*1024).
> ksymoops from sysrq-m attached,
hmm, well h
On Wed, 20 Jun 2001, Marcelo Tosatti wrote:
> > happened again (vt1 and 2 echo but shells are unresponsive, vt3+ don't
> > echo) only active process was the program allocating 192mb and writing to
> > it, no find this time.
>
> Can you get the backtrace of this process?
the offending process is
On Wed, 20 Jun 2001, Justin Guyett wrote:
> On Wed, 20 Jun 2001, Justin Guyett wrote:
>
> > I got it to freeze in console (two generic find / -type f / type d), one
> > process allocating and writing 0 to 192mb
> >
> > machine responds to pings, switching VTs works
> >
> > (256 physical, 512 s
On Wed, 20 Jun 2001, Justin Guyett wrote:
> I got it to freeze in console (two generic find / -type f / type d), one
> process allocating and writing 0 to 192mb
>
> machine responds to pings, switching VTs works
>
> (256 physical, 512 swap)
happened again (vt1 and 2 echo but shells are unrespons
I got it to freeze in console (two generic find / -type f / type d), one
process allocating and writing 0 to 192mb
machine responds to pings, switching VTs works
(256 physical, 512 swap)
Mem-info
Free pages: 1524kB (0kB High)
( Active: 39586, inactive_dirty: 18590, inactive_clean: 0, free: 381
5 matches
Mail list logo
