At Thu, 19 Feb 2004 19:24:22 +0100,
marco_g wrote:
>
> Marcus Brinkmann <[EMAIL PROTECTED]> writes:
>
> > At Mon, 16 Feb 2004 18:06:59 +0100 (MET),
> > ams wrote:
> >>
> >>panic: zalloc: zone kalloc.8192 exhausted
> >
> >> Silly question maybe, but, how much RAM and swap do you have? zalloc
Marcus Brinkmann <[EMAIL PROTECTED]> writes:
> At Mon, 16 Feb 2004 18:06:59 +0100 (MET),
> ams wrote:
>>
>>panic: zalloc: zone kalloc.8192 exhausted
>
>> Silly question maybe, but, how much RAM and swap do you have? zalloc
>> messages tend to pop up when you have to little swap or RAM.
>
> C
At Mon, 16 Feb 2004 18:06:59 +0100 (MET),
ams wrote:
>
>panic: zalloc: zone kalloc.8192 exhausted
> Silly question maybe, but, how much RAM and swap do you have? zalloc
> messages tend to pop up when you have to little swap or RAM.
Could also be a resource leak. For example a port leak. I
>> If you have a serial console then you could check what is
>> happening in Mach (and maybe crash). Do you have a serial
>> console?
>
>Yes, I do. You mean the kernel debugger? How to use this?
>
> No, I mean a real serial console, the kernel debugger sucks.
"Alfred M. Szmidt" <[EMAIL PROTECTED]> writes:
>> If you have a serial console then you could check what is
>> happening in Mach (and maybe crash). Do you have a serial
>> console?
>
>Yes, I do. You mean the kernel debugger? How to use this?
>
> No, I mean a real serial console,
390MB RAM. And this was after a fresh boot with nothing started
yet. And I do not remember how much swap I have, but I assume that
is not really relevant.
vmstat will show you how much swap you have.
>Does someone have any idea what the problem might be and how I
>can deb
"Alfred M. Szmidt" <[EMAIL PROTECTED]> writes:
>panic: zalloc: zone kalloc.8192 exhausted
>(There is a small pause here and a bit of disk activity/ flashing IDE LEDs)
>hd1: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
>hd0: disabled DMA
>hd1: disabled DMA
>
panic: zalloc: zone kalloc.8192 exhausted
(There is a small pause here and a bit of disk activity/ flashing IDE LEDs)
hd1: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hd0: disabled DMA
hd1: disabled DMA
ide0: reset: success
(And here my box reboots after so
Marco Gerards <[EMAIL PROTECTED]> writes:
> James Morrison <[EMAIL PROTECTED]> writes:
>
> > What is your crash server setup to do? Have you tried attached gdb to
> > the crash server?
>
> It is set to --suspend. I have not yet tried to debug the crash
> server, that is a good idea.
Does t
James Morrison <[EMAIL PROTECTED]> writes:
> What is your crash server setup to do? Have you tried attached gdb to
> the crash server?
It is set to --suspend. I have not yet tried to debug the crash
server, that is a good idea.
Still, it is stupid that Mach crashes. :)
Thanks,
Marco
_
Marco Gerards <[EMAIL PROTECTED]> writes:
> Hi,
>
> While I tried to generate a segfault it crashed GNUMach (1.x, I have
> tested both CVS and 1.2) with this error:
>
> panic: zalloc: zone kalloc.8192 exhausted
> (There is a small pause here and a bit of disk activity/ flashing IDE LEDs)
> hd1
11 matches
Mail list logo
