On Tue, 26 Feb 2008 10:35:31 +0100 (CET) Nikola Ciprich <extmaillist@xxxxxxxxxxx> wrote:
Hi
On Sun, 24 Feb 2008, Andrew Morton wrote:
Hi Andrew,
thanks a lot for reply, I'm attaching requested information.
please let me know if You need more information/testing, whatever.
I'll be glad to help.
BR
nik
Areca support doesn't seem to be very interested in the problem :-(
(cc's added)
Please get the machine into this state of memory exhaustion then take
copies of the output of the following, and send them via reply-to-all to
this email:
- cat /proc/meminfo
- cat /proc/slabinfo
- dmesg -c > /dev/null ; echo m > /proc/sysrq-trigger ; dmesg -c
Thanks.
Alas, that all looks OK to me.
You never get any out-of-memory messages, and no oom-killing messages?
Possibly what is happening here is that in this low-memory condition, some
of the driver's internal memory-allocation attempts are failing, and the
driver isn't correctly handling this. This is a rare situation which may
well not have been hit in anyone else's testing.
I expect that the Areca engineers will be able to reproduce this with a
suitably small "mem=" kernel boot option. If not, they could perhaps
investigate the kernel's fault-injection framework, which permits
simulation of page allocation failures.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/