Bug 80890 - [panic] kmem_malloc(73728): kmem_map too small running mysql
Summary: [panic] kmem_malloc(73728): kmem_map too small running mysql
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: sparc64 (show other bugs)
Version: 5.4-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-sparc64 (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-11 13:10 UTC by Carlos Sola
Modified: 2011-12-12 19:57 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Carlos Sola 2005-05-11 13:10:07 UTC 
The machine is a SUN E450 with
cpu0: Sun Microsystems UltraSparc-II Processor (400.00 MHz CPU)
cpu1: Sun Microsystems UltraSparc-II Processor (400.00 MHz CPU)
real memory  = 1073741824 (1024 MB)
avail memory = 1039368192 (991 MB)

Runing mysql-server-4.1.10a (package install)
When I run my application in other server that connects to this sparc mysql, after a while it's dump a panic and reboot.
The message is:

panic: kmem_malloc(73728): kmem_map too small: 348577792 total allocated
cpuid = 1
boot() called on cpu#0
Uptime: 5m37s
Cannot dump. No dump device defined.
Automatic reboot in 15 seconds - press a key on the console to abort
Rebooting...
Resetting ...

How-To-Repeat: Just make 300 mysql connections and simple selects. I suppose its a memory allocation problem and not mysql issue.
Comment 1 Marius Strobl freebsd_committer freebsd_triage 2011-12-12 19:10:17 UTC 
State Changed
From-To: open->feedback

Is this still an issue with a current version of FreeBSD, i.e. 8 or 9?
Comment 2 Marius Strobl freebsd_committer freebsd_triage 2011-12-12 19:55:55 UTC 
State Changed
From-To: feedback->closed

Close; submitter email address bounces.