Re: zfs panic with yesterday -current

From: Pawel Jakub Dawidek <pjd@xxxxxxxxxxx>
Date: Tue, 31 Jul 2007 13:41:01 +0200

On Tue, Jul 31, 2007 at 10:47:25AM +0200, Cedric Tabary wrote:

finally I managed to reproduce it :
panic: kmem_malloc(16384): kmem_map too small: 343056384 total allocated
cpuid = 1
KDB: enter: panic
[thread pid 1206 tid 100154 ]
Stopped at kdb_enter+0x31: popq %rbp

Are you sure this is amd64?

--
Pawel Jakub Dawidek http://www.wheel.pl
pjd@xxxxxxxxxxx http://www.FreeBSD.org
FreeBSD committer Am I Evil? Yes, I Am!

Attachment: pgpFRVTgLkz4B.pgp
Description: PGP signature

Follow-Ups:
- Re: zfs panic with yesterday -current
  - From: Cedric Tabary

References:
- zfs panic with yesterday -current
  - From: Cedric Tabary
- Re: zfs panic with yesterday -current
  - From: Pawel Jakub Dawidek
- Re: zfs panic with yesterday -current
  - From: Cedric Tabary
- Re: zfs panic with yesterday -current
  - From: Cedric Tabary

Prev by Date: Re: zfs panic with yesterday -current
Next by Date: High interrupt count on irq12
Previous by thread: Re: zfs panic with yesterday -current
Next by thread: Re: zfs panic with yesterday -current
Index(es):
- Date
- Thread

Relevant Pages

malloc fallout and linprocfs
... If I fire up a linux version of OpenOffice on amd64, ... several messages of the following form on the console. ... KDB: stack backtrace: ...
(freebsd-current)
Re: panic: kmem_malloc(131072): kmem_map too small (AMD64)
... KDB: enter: panic ... This was with these settings in loader.conf: ... How much ram do you have? ... Is this amd64 or i386? ...
(freebsd-current)
Re: ZFS leaking vnodes (sort of)
... Thu Jul 12 02:28:52 UTC 2007 ... KDB: enter: panic ...
(freebsd-current)
HEADSUP [amd64]: New KDB framework untested.
... Since I don't have an amd64 box myself, I could not test the new KDB ... framework. ... But obviously when it's not tested there's a big chance it ...
(freebsd-current)