From: Ben Stuyts <ben@stuyts.nl> To: Alfred Perlstein <alfred@FreeBSD.ORG> Cc: Jeff Roberson <jroberson@chesapeake.net>, Terry Lambert <tlambert2@mindspring.com>, Robert Watson <rwatson@freebsd.org>, current@freebsd.org, jeff@freebsd.org Subject: Re: [Ugly PATCH] Again: panic kmem_malloc() Message-ID: <20021017124351.A37274@terminus.stuyts.nl> In-Reply-To: <20021016212619.GR95327@elvis.mu.org>; from alfred@FreeBSD.ORG on Wed, Oct 16, 2002 at 02:26:19PM -0700 References: <4.3.2.7.2.20021016213322.01c6d348@terminus> <4.3.2.7.2.20021016225907.00b8b8b0@terminus> <20021016212619.GR95327@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Alfred, On Wed, Oct 16, 2002 at 02:26:19PM -0700, Alfred Perlstein wrote: > * Ben Stuyts <ben@stuyts.nl> [021016 14:05] wrote: > > > > No need to wait for tomorrow. :-) Just 1.5 hours later, vmstat -m says: > > > > < sem167344 2622K 2622K 167344 16,1024,4096 > > --- > > > sem235512 3687K 3687K 235512 16,1024,4096 > > > > So it looks indeed like sem is the problem, > > what does > sysctl -a | grep ^p10 > say? p1003_1b.asynchronous_io: 0 p1003_1b.mapped_files: 1 p1003_1b.memlock: 0 p1003_1b.memlock_range: 0 p1003_1b.memory_protection: 0 p1003_1b.message_passing: 0 p1003_1b.prioritized_io: 0 p1003_1b.priority_scheduling: 1 p1003_1b.realtime_signals: 0 p1003_1b.semaphores: 0 p1003_1b.fsync: 0 p1003_1b.shared_memory_objects: 1 p1003_1b.synchronized_io: 0 p1003_1b.timers: 0 p1003_1b.aio_listio_max: 0 p1003_1b.aio_max: 0 p1003_1b.aio_prio_delta_max: 0 p1003_1b.delaytimer_max: 0 p1003_1b.mq_open_max: 0 p1003_1b.pagesize: 4096 p1003_1b.rtsig_max: 0 p1003_1b.sem_nsems_max: 0 p1003_1b.sem_value_max: 0 p1003_1b.sigqueue_max: 0 p1003_1b.timer_max: 0 > My guess is that you don't have the module in question loaded. > > If you do, then why? (it's marked experimental) The only modules loaded are: [terminus.stuyts.nl boot/kernel]21: kldstat Id Refs Address Size Name 1 3 0xc0100000 3daa00 kernel 2 1 0xc12fd000 2000 green_saver.ko > And why aren't these bug reports a lot more detailed? (meaing why > aren't you actually giving an hypothesys as to why the code is > broken?) I think it was Jeff Roberson hinting at that. I am only reporting a problem and I hope I can help fixing it. I have however no knowledge of the kernel internals, so forgive me for being too vague and let me know what more information you need. > *grumble* Sorry... Kind regards, Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021017124351.A37274>