On Sun, 3 Mar 2002, Andrew Morton wrote:
> The loop driver does really naughty things which defeat the kernel's
> management of dirty data. It's quite easy to livelock machines with
> it, especially if you increase the dirty buffer thresholds.
I'd appreciate it if you could go in to more detail off list, out of
a general interest I have here.
> I expect the problem will go away if you drop the dirty buffer
> thresholds:
>
> echo 10 0 0 0 500 3000 25 0 0 > /proc/sys/vm/bdflush
>
> Could you please try that?
Unfortunately not today or probably earlier this week as I'm about to be
150 miles away from the office back in the land of cs.nott.ac.uk and am
planning to avoid late night sysrq fun over a serial console this week :-)
> Also, if/when it locks up again, the SYSRQ-P information will be
> interesting. Use the key sequence several times, record the EIP values,
> look them up after reboot. Probably, they point at shrink_cache().
Well, at least this kernel should have kernel debugging enabled so if/when
it happens again or I get chance to look at it over this week I'll lookup
where it's happening - for now all I need to know is that loopback still
isn't kosher on 2.4 and I need to avoid it by using a 2.2 box or whatever.
Jon.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Mar 07 2002 - 21:00:31 EST