Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 Jul 2007 00:57:40 +0200
From:      Attilio Rao <attilio@FreeBSD.org>
To:        Rene Ladan <r.c.ladan@gmail.com>
Cc:        Jeff Roberson <jroberson@chesapeake.net>, current@freebsd.org
Subject:   Re: ULE/SCHED_SMP diff for 7.0
Message-ID:  <469E9AE4.6050007@FreeBSD.org>
In-Reply-To: <469E897B.7080100@gmail.com>
References:  <20070716233030.D92541@10.0.0.1> <469E83F8.3090103@gmail.com>	<20070718142649.Y561@10.0.0.1> <469E897B.7080100@gmail.com>

index | next in thread | previous in thread | raw e-mail

Rene Ladan wrote:
> Jeff Roberson schreef:
>> On Wed, 18 Jul 2007, Rene Ladan wrote:
>>
>>> Jeff Roberson schreef:
>>>> http://people.freebsd.org/~jeff/ule.diff
>>>>
>>>> This patch is scheduled for inclusion in 7.0.  I would like anyone who
>>>> cares to run it to validate that it does not create any stability or
>>>> performance regression over the existing ULE.  This patch replaces ULE
>>>> with SCHED_SMP, which will now no longer exist as a seperate fork of
>>>> ULE.
>>> [..]
>>>
>>> I cvsupped this evening at 19:34 UTC.  The new ULE scheduler works fine
>>> in single-user mode (it survives "make kernel"), but when I go to
>>> multi-user mode I get a "sched_add: trying to run inhibited thread"
>>> panic (2 vmcores lost due to fsck :( )
>> Can you get me a backtrace?  You can enable KDB and DDB in your kernel
>> along with INVARIANTS.  Just type 'tr' and record the function names
>>
> 
> I found a file #165060 in /var/lost+found .  kgdb didn't eat it, but strings
> could still extract the attached backtrace.  In case you want to recompile
> the kernel, it is compiled with -O1 -pipe -march=prescott
> -fno-strict-aliasing

Are you using libkse?
I think this problem is linked to other KSE locking issue we are 
currently experiencing and that I'm trying to fix (a little bit time 
constrained now).

Attilio



home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?469E9AE4.6050007>