Date: Tue, 10 Aug 2004 20:36:19 +0000 (UTC) From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: Colin Percival <colin.percival@wadham.ox.ac.uk> Cc: freebsd-current@freebsd.org Subject: Re: Lock order reversal in 5.2-CURRENT Message-ID: <Pine.BSF.4.53.0408102034520.1709@e0-0.zab2.int.zabbadoz.net> In-Reply-To: <6.1.0.6.1.20040810114002.03ef96c8@popserver.sfu.ca> References: <20040810203073.SM01804@manrikigusari> <6.1.0.6.1.20040810114002.03ef96c8@popserver.sfu.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 10 Aug 2004, Colin Percival wrote: > At 11:29 10/08/2004, Terrence Koeman wrote: > >lock order reversal > > 1st 0xc0645aa0 sched lock (sched lock) @ /usr/src/sys/vm/vm_zeroidle.c:156 > > 2nd 0xc06748c0 sio (sio) @ /usr/src/sys/dev/sio/sio.c:3039 > > > >This LOR is not on http://sources.zabbadoz.net/freebsd/lor.html, so I'm > >guessing this one locked up my system. > > This is LOR #013 on bzeeb's list. There isn't any solution yet, but there is > a simple workaround: unplug the serial console. is it fully the same ? At least it happens in two places then or did functions get moved ? If so then I will merge 020 into 013 ? -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.53.0408102034520.1709>