Re: scheduler panic

From: Larry Rosenman <ler_at_lerctr.org>
Date: Fri, 23 Dec 2011 10:42:04 -0600
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/23/2011 8:54 AM, John Baldwin wrote:
> The sloppiest fix might be to do this:
> 
> Index: sched_ule.c 
> ===================================================================
>
> 
- --- sched_ule.c	(revision 228777)
> +++ sched_ule.c	(working copy) _at__at_ -1434,7 +1434,8 _at__at_
> sched_priority(struct thread *td) } else { pri = SCHED_PRI_MIN; if
> (td->td_sched->ts_ticks) -			pri += SCHED_PRI_TICKS(td->td_sched); 
> +			pri += min(SCHED_PRI_TICKS(td->td_sched), +
> SCHED_PRI_RANGE); pri += SCHED_PRI_NICE(td->td_proc->p_nice); 
> KASSERT(pri >= PRI_MIN_BATCH && pri <= PRI_MAX_BATCH, 
> ("sched_priority: invalid priority %d: nice %d, "
> 

I've applied this to both the host and the guest, and am recompiling
the guest kernel (hopefully it'll stay up long enough...).

I'll report back.

Do y'all (FreeBSD Devs) want a PR?


- -- 
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 512-248-2683                 E-Mail: ler_at_lerctr.org
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJO9K9cAAoJENC8dtAvA1zmruAIAL0udaYatGWp5E/Th9YYD8Hh
FHVri/G/Va8YsivqfZLFYUZd8SyqO/0vxEIoG73iKJJmjW/CpYIjgOvCRvsCrefm
ABOYmRX0dvC8GLHDgN9XFt4J9GmNTDcneNV7rOvWKisygkHw0GlK5DxKtSo3PsE8
6MQSnUuVmUMggsVQfBUiPTyTmJigcJ9KuEdfbHQ2o7+sCWx+gAKCyfVFcwkNIrYv
M7j21dJ8hjHUteHZ3YttVjYku0/YISSmtvGVCMlm2xBGD+tTu5g2ZcqZsxzlRFst
HyLGDP3mKSQJRMHcvl+OXMmwnFO7m31fLhj04LIWardV93S3CYF0c54LNEHYEN4=
=/imM
-----END PGP SIGNATURE-----
Received on Fri Dec 23 2011 - 15:42:29 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:22 UTC