Date: Thu, 14 Sep 2000 14:54:50 +0200 From: Mitja Horvat <mitja.horvat@hermes.si> To: freebsd-stable@freebsd.org Subject: panic: kmem_malloc(-1077936128): kmem_map too small Message-ID: <20000914145450.A337@lamu.hermes.si>
next in thread | raw e-mail | index | archive | help
Hi, I recently upgraded to 4.1-STABLE, and I had problems booting the kernel since then. The problem occurs exactly when mountd is started and begins to export filesystems. These are the information I can get from the crash dump: IdlePTD 3375104 initial pcb at 2bf7a0 panicstr: kmem_malloc(-1077936128): kmem_map too small: 6619136 total allocated panic messages: --- panic: kmem_malloc(-1077936128): kmem_map too small: 6619136 total allocated syncing disks... 67 67 67 67 67 67 67 67 67 67 67 67 67 67 67 67 67 67 67 67 giving up on 64 buffers Uptime: 25s dumping to dev #ad/0x20001, offset 24 dump ata0: resetting devices .. done 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 3 0 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 And this is the gdd -k backtrace : (kgdb) where #0 0xc013c7d4 in boot () #1 0xc013cb58 in poweroff_wait () #2 0xc01e88bc in kmem_malloc () #3 0xc01385d4 in malloc () #4 0xc0168747 in vfs_hang_addrlist () #5 0xc0168977 in vfs_export () #6 0xc01dc077 in ffs_mount () #7 0xc01697f2 in mount () #8 0xc023085a in syscall2 () #9 0xc0225115 in Xint0x80_syscall () #10 0x8049956 in ?? () #11 0x8048364 in ?? () #12 0x8048139 in ?? () It seems to me like there's something wrong with exporting a filesystem. In my case, I'm trying to export the / filesystem as shown in this /etc/exports file: /home -maproot=nobody -network 10.17 -mask 255.255.0.0 # /cdrom -maproot=root -ro -network 10.17 -mask 255.255.0.0 (Note, that I commented out /cdrom just in case, but it's the same with or without it) Anybody had similar experiences? I would really appreciate a patch or that it gets fixed in the cvs tree as soon as possible. (If this problem has been reported before I apologize, I subscribed to freebsd-stable only today) Thank your for your answers, Mitja To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000914145450.A337>