[bug #19426] GNU Mach: panic: zalloc: zone kalloc.8192 exhausted

Update of bug #19426 (project hurd): Status:None => Fixed Open/Closed:Open => Closed ___ Follow-up Comment #3: agreed!

[bug #19426] GNU Mach: panic: zalloc: zone kalloc.8192 exhausted

Follow-up Comment #2, bug #19426 (project hurd): Probably, as mach uses new allocator now, this bug could be closed? ___ Reply to this item at: ___ Mess

[bug #19426] GNU Mach: panic: zalloc: zone kalloc.8192 exhausted

Follow-up Comment #1, bug #19426 (project hurd): That's a general issue with leaks of port & such. In the debian gnumach package I've extended the zone map to 64MB. On buildds, I've actually even made it 200MB. ___ Reply to this item at:

[bug #19426] GNU Mach: panic: zalloc: zone kalloc.8192 exhausted

Additional Item Attachment, bug #19426 (project hurd): File name: feed_rss10_80x15_2.png Size:3 KB ___ Reply to this item at: ___ Message sent

[bug #19426] GNU Mach: panic: zalloc: zone kalloc.8192 exhausted

URL: <http://savannah.gnu.org/bugs/?19426> Summary: GNU Mach: panic: zalloc: zone kalloc.8192 exhausted Project: The GNU Hurd Submitted by: mbanck Submitted on: Tuesday 03/27/07 at 14:44 Category: GN

Re: Panic: zalloc!

Jon Arney <[EMAIL PROTECTED]> writes: >> When we use oskit-mach we can get better data with gdb over serial >> line. > > If you will be switching uKernels, does this mean that the zalloc > problem is not worth investigating since it will probably go away > with gnumach, or am I missing something.

Re: Panic: zalloc!

get better data with gdb over serial line. If you will be switching uKernels, does this mean that the zalloc problem is not worth investigating since it will probably go away with gnumach, or am I missing something. Sorry if I'm being thick-headed. > > > Going to the physical c

Re: Panic: zalloc!

Marcus Brinkmann <[EMAIL PROTECTED]> writes: > We might make it a command line option at some time, but this also requires > planning ahead ;) Another option is to have some reserved disk blocks for > the kernel to write a memory dump (core file) to. Why not have a timeout, during which somebod

Re: Panic: zalloc!

r even some other bug). We are currently lacking data to give a good interpretation for the zalloc problems. When we use oskit-mach we can get better data with gdb over serial line. > Going to the physical console, I noticed a message 'panic: zalloc' > and before I could copy it

Panic: zalloc!

elf, this is not good". Going to the physical console, I noticed a message 'panic: zalloc' and before I could copy it down, the box re-booted on me. This brings me finally to the point! Around line 171 of gnumach/kern/debug.c I found the following fragment from the 'panic