[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: glibc; introducing slashpackage-foreign (was: GNU Mach panic)

At Wed, 9 Mar 2005 12:50:55 +0100, Thomas Schwinge <[EMAIL PROTECTED]> wrote: > > [ Cc'ed to the slashpackage-foreign list > mailto:[EMAIL PROTECTED]>. ] > > [ Replied publically with Alfred's permission. ] This is all very well, but could you give us some context why you posted this here in t

Re: IRC (was: GNU Mach panic)

Was I just too stupid to find such archives or do they really not exist? They do, http://web.walfield.org/~deride/ I suppose it would be rather trivial to have interesting channels logged on a few machines, have the logs compared and merged, so that nothing is missed and have the w

Re: glibc; introducing slashpackage-foreign (was: GNU Mach panic)

the nptl and linuxthreads add-ons should be disabled for GNU/Hurd. They are disabled for the Hurd; don't use --enable-add-ons the way you are using it. I have to use './configure [...] --prefix=[...] --with-headers=[...]' because I have every package installed into its own hierarchy

IRC (was: GNU Mach panic)

[ Replied publically with Alfred's permission. ] On Sun, Mar 06, 2005 at 09:35:17AM +0100, Alfred M. Szmidt wrote: > If you are familiar with IRC then you can pop by irc.gnu.org, ##hurd. I've never used IRC before, but installed the Emacs IRC Client ERC http://www.emacswiki.org/cgi-bin/wiki/Emacs

glibc; introducing slashpackage-foreign (was: GNU Mach panic)

[ Cc'ed to the slashpackage-foreign list mailto:[EMAIL PROTECTED]>. ] [ Replied publically with Alfred's permission. ] On Sun, Mar 06, 2005 at 09:28:43AM +0100, Alfred M. Szmidt wrote: >rm {nptl,linuxthreads}/configure > > Why? When using 'configure [...] --enable-add-ons' to tell glibc's

Re: GNU Mach panic

Yes, kdb is documented in GNU Mach Reference. But I'm not aware of documented precise instructions how to make good report for GNU Mach panic, e.g. where to set breakpoints and what kdb commands to be run for the report. That depends on a case by case basis, like all debu

Re: GNU Mach panic

On Sun, Mar 06, 2005 at 01:42:27AM +0100, Alfred M. Szmidt wrote: > Always tell us what function the EIP really is. Probably not that helpful... #v+ $ addr2line -fe gnumach 0x11a07e Debugger ./kern/debug.c:102 #v- #v+ cat -n kern/debug.c | grep -C 10 ^\ \ \ 102 92 asm("ta 0x81");

Re: GNU Mach panic

t for GNU Mach panic, e.g. where to set breakpoints and what kdb commands to be run for the report. Regards, ogi ___ Bug-hurd mailing list Bug-hurd@gnu.org http://lists.gnu.org/mailman/listinfo/bug-hurd

Re: GNU Mach panic

It is already documented in the --help output for configure, and in the GNU Mach documentation, so there is no need to mention this on the wiki. It would be nice if someone could take the information stored on the wiki, and incoperate it into the Hurd or GNU Mach manuals. The wiki is not a substi

Re: GNU Mach panic

Thomas Schwinge wrote: Another GNU Mach panic: #v+ panic: zalloc: zonethreads exhausted Kernel Breakpoint trap, eip 0x11a07e Stopped at 0x11a07d: int $3 db> continue panic: zalloc: zone kalloc.256 exhausted Kernel Breakpoint trap, eip 0x11a07e Stopped at 0x11a07d: int $3 db> reset #v- How ha

Re: GNU Mach panic

Always tell us what function the EIP really is. You haven't told use what arguments for glibc you used to compile it. ___ Bug-hurd mailing list Bug-hurd@gnu.org http://lists.gnu.org/mailman/listinfo/bug-hurd

GNU Mach panic

Hello! Another GNU Mach panic: #v+ panic: zalloc: zonethreads exhausted Kernel Breakpoint trap, eip 0x11a07e Stopped at 0x11a07d: int $3 db> continue panic: zalloc: zone kalloc.256 exhausted Kernel Breakpoint trap, eip 0x11a07e Stopped at 0x11a07d: int $3 db> reset #v- The system was