Date: Tue, 7 Jun 2005 06:56:09 +0900 (JST) From: Norikatsu Shigemura <nork@FreeBSD.org> To: Jeff Roberson <jroberson@chesapeake.net> Cc: nork@FreeBSD.org, current@FreeBSD.org Subject: Re: ULE Status. Message-ID: <200506062156.j56Lu9ix008106@sakura.ninth-nine.com> In-Reply-To: <20050606151209.E16943@mail.chesapeake.net> References: <20050604052429.T8209@mail.chesapeake.net> <200506051336.j55DacJJ070482@sakura.ninth-nine.com> <200506051547.j55FluRV073876@sakura.ninth-nine.com> <20050606151209.E16943@mail.chesapeake.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 6 Jun 2005 15:12:59 -0400 (EDT) Jeff Roberson <jroberson@chesapeake.net> wrote: > > > > I just fixed what should be the last ULE+KSE+PREEMPTION bug. Please let > > > > me know if you run into any problems with it, preferably with a seperate > > > > mail to me as I'm more likely to see this than one which is cc'd to > > > > current@. > > > Wow! that's cool! > > > I tried to 'nice -20 make -j1024 buildworld' with > > > SCHED_ULE and PREEMPTION kernel options. I contacted a > > > panic like following, and sorry, I cannot get a crash dump. > Is this on CURRENT or 5.x? What is your sched_ule.c version? I'm doing > this on CURRENT while playing a movie with mplayer without issue. Off course, I'm using latest CURRENT in this time, and sched_ule.c,v 1.151. FreeBSD nadesico.ninth-nine.com 6.0-CURRENT FreeBSD 6.0-CURRENT #4: Mon Jun 6 01:02:49 JST 2005 nork@nadesico.ninth-nine.com:/usr/obj/usr/src/sys/NADESICO i386 $FreeBSD: src/sys/kern/sched_ule.c,v 1.151 2005/06/04 09:24:15 jeff Exp $ > > #22 0xc04b3ebc in sched_add (td=0x0, flags=0) > > at /usr/src/sys/kern/sched_ule.c:1745 > > #23 0xc04b4988 in setrunqueue (td=0xc3a3f4b0, flags=0) at kern_switch.c:564 > > #24 0xc04b46a1 in adjustrunqueue (td=0xc3a3f4b0, newpri=16) > > at kern_switch.c:325 > > #25 0xc04b3354 in sched_thread_priority (td=0xc3a3f4b0, prio=16 '\020') > > at /usr/src/sys/kern/sched_ule.c:1235 > > #26 0xc04b339d in sched_lend_prio (td=0x0, prio=16 '\020') > > at /usr/src/sys/kern/sched_ule.c:1250 > > #27 0xc04c7f9e in propagate_priority (td=0xc3a3f4b0) > > at /usr/src/sys/kern/subr_turnstile.c:204 > > #28 0xc04c8a7d in turnstile_wait (lock=0xc06d0b60, owner=0x0) > > at /usr/src/sys/kern/subr_turnstile.c:629 > > #29 0xc0490351 in _mtx_lock_sleep (m=0xc06d0b60, td=0xc2c58320, opts=0, > > file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:550 > > #30 0xc0480dec in ithread_loop (arg=0xc2c59c00) > > at /usr/src/sys/kern/kern_intr.c:545 > > #31 0xc047fa60 in fork_exit (callout=0xc0480c50 <ithread_loop>, arg=0x0, > > frame=0x0) at /usr/src/sys/kern/kern_fork.c:789 > > #32 0xc061053c in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:208 I think that fork and ithread with sched_ule issue has a issue.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200506062156.j56Lu9ix008106>