Package: gnumach
Version: 1:20020421-1 (not installed)
Severity: normal

I was running an highly resource consumption process when Mach paniced. The
reason is probably related to bug #82600

But the problem i'm reporting is that Mach unexpectedly rebooted the machine
after panicing. The error message i could read was something similar to:

  panic: kalloc: memory exhausted in zalloc

(it's not exact, as i didn't have time to write it down. there was a number
i ommited and maybe the "zalloc/kalloc" order was reversed)

Mach should realy stop after a panic and let the user read the message,
instead of rebooting.

just in case it helps, my system has 128 MB of RAM and 512 MB of swap.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux aragorn 2.2.22 #1 dl nov 25 21:59:43 CET 2002 i586
Locale: LANG=ca_ES.ISO-8859-1, [EMAIL PROTECTED] (ignored: LC_ALL set)




_______________________________________________
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd

Reply via email to