On Fri, 13 Jun 2003, John Hay wrote:
> On a 5.1-RELEASE machine I have been able to cause a panic like this:
>
> panic: kmem_malloc(4096): kmem_map too small: 28610560 total allocated
>
> The machine is an old 300MHz Celeron with 64M Ram. I get the panic by
> un-taring a "huge" .tgz file onto a vi
Hello,
At 09:06 06/10/2002, Mikhail Teterin wrote:
>... 218222592 total allocated
>
>this machine has a total of 512Mb of RAM, and no swap.
>No X was running. Just ``cvs update''-ing.
I got this also a couple of times over the last week. It would panic every
few days with this same message. I c
On Mon, 7 Oct 2002, Mikhail Teterin wrote:
> No... With today's kernel, machine has already _frozen_ after swappager
> complained about lack of swap. Rather sad -- a not so uncommon installation
> with 128Mb of memory plus twice that much of swap would still have less
> virtual memory than this b
îÅĦÌÑ 06 öÏ×ÔÅÎØ 2002 03:13 am, n0g0013 ÷É ÎÁÐÉÓÁÌÉ:
> On 06.10-03:06, Mikhail Teterin wrote:
> > this machine has a total of 512Mb of RAM, and no swap.
> > No X was running. Just ``cvs update''-ing.
>
> running vinum ? i am getting this consistently with vinum (but am
> taking an age to rebuild
On 06.10-03:06, Mikhail Teterin wrote:
> this machine has a total of 512Mb of RAM, and no swap.
> No X was running. Just ``cvs update''-ing.
running vinum ? i am getting this consistently with vinum (but am
taking an age to rebuild.
did you get a backtrace ? . . . to vfs allocations
. . . and
