Don't know what I was doing but...
rrs at cisco.com
Sun Jun 10 15:59:39 UTC 2007
Attilio Rao wrote:
> Attilio Rao wrote:
>> Randall Stewart wrote:
>>> Hi all:
>>> I have a fairly recent current.. like yesterday I think.. and
>>> I just saw this tumble out (I usually run with witness and invariants
>>> on in my laptop now :-D)
>>> lock order reversal:
>>> 1st 0xc0b79f70 sched lock (sched lock) @ kern/sched_4bsd.c:846
>>> 2nd 0xc0bec658 descriptor tables (descriptor tables) @
>> Mm, since dt_lock is a leaf mutex, the opposite case seems quite
>> impossible, so I expect this would be the result of some other bug...
>> if next cvsup doesn't fix it, just let me know and I will look into
> More precisely, I'd like to better study effects recent thread_lock
> introduction had on witness rules.
I did a sup this AM... I will re-do that then cvs update and
NSSTG - Cisco Systems Inc.
803-345-0369 <or> 803-317-4952 (cell)
More information about the freebsd-current