Re: 2.1.51 Still Freezing

Ben Clifford (benc@dass.prestel.co.uk)
Tue, 19 Aug 1997 08:27:14 +0000 (GMT)


I have a similar problem - the differences seem to be that I am getting a
lot of failed network buffer allocs, according to Shift-Scrolllock or
SysRq-M. I also only have one task in the Run state at the time. It seems
to occur when my news server sends big stuff like the newsgroups list, or
the index for a large newsgroup.

After a while, an error message "tcp_write_wakeup: fragment failed"
appears, if I have the message level set low enough.

I made a patch to give SysRq-N which terminates the current process. This
allows me to recover the system when the above happens, instead of just
pressing Reset.

I won't post the patch again; I expect it is available on linux-hq.

On Tue, 19 Aug 1997, Jeff DeFouw wrote:

> * Happens at any time, uptime doesn't seem to matter.
> * Usually happens during low or no activity (this time with X was my only
> exception)
> * Hard disk activity stops except for maybe a few clicks.
> * Kernel VT switching, SysRq, and debug output still works.
> * Can continue to type on last used VT if input is not handled by
> a process, all other VT's will not accept input at all.
> * Scheduling: Control-ScrollLock output displayed about 6 tasks in Run
> state, "current" doesn't change.
> * Plenty of free cache, buffers, memory, and swap during freeze,
> according to Shift-ScrollLock.
> * No Oops

--
PGP 0xD4C9C0B1 http://www.geocities.com/SiliconValley/Lakes/7456/
1264kb of spam & junk filtered; Linux 2.1.50 on dass up for 21 hours