Date: Sat, 20 Nov 2010 16:17:24 +0800 From: Adrian Chadd <adrian@freebsd.org> To: Colin Percival <cperciva@freebsd.org> Cc: "freebsd-xen@freebsd.org" <freebsd-xen@freebsd.org> Subject: Re: system stalls when wallclock/TOD nudged Message-ID: <AANLkTi=yrY8W7BYTopY12Etyuzb=QR89mj69RpTnf74z@mail.gmail.com> In-Reply-To: <4CE7837E.3030901@freebsd.org> References: <4CE68CD7.10804@freebsd.org> <1290191413.1758.16.camel@localhost> <4CE77AE7.3010106@freebsd.org> <AANLkTikoFuUDcwF8AojoWCXdwnobbkyrj7343phmt2ap@mail.gmail.com> <4CE7837E.3030901@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 20 November 2010 16:14, Colin Percival <cperciva@freebsd.org> wrote: > On 11/19/10 23:40, Adrian Chadd wrote: >> I bet if you did some slicing of -head versions, you'll find an >> earlier version that doesn't do that. :-) > > Sure, all I need to do is go back a couple of days, and I find a FreeBSD > Xen kernel which doesn't do this... because it panics before the clock > gets nudged. :-) > Well, try a -head kernel from 6 months ago but patch with your recent changes? :-) Adrian >> On 20 November 2010 15:38, Colin Percival <cperciva@freebsd.org> wrote: >>> It seems that this bug is related somehow to the idle thread sleeping -= - when >>> I comment out the call to idle_block from cpu_idle_hlt in i386/machdep.= c the >>> stalling goes away. >>> >>>> On Fri, 2010-11-19 at 06:42 -0800, Colin Percival wrote: >>>>> During the boot process, in the middle of running rc.d scripts, my Fr= eeBSD/Xen >>>>> instance stalls. =A0It does nothing until I send a shutdown signal, a= t which point >>>>>> [XEN] hypervisor wallclock nudged; nudging TOD. >>>>> and a couple buffered lines of rc.d script output are printed. =A0Fro= m there the >>>>> rc.shutdown script starts running, but it too stalls after a short ti= me; then I >>>>> see >>>>>> [XEN] hypervisor wallclock nudged; nudging TOD. >>>>>> Nov 19 14:08:33 init: timeout expired for /bin/sh on /etc/rc.shutdow= n: Interrupted system call; going to single user mode >>>>> printed, suggesting that the shutdown watchdog timer at least managed= to not get >>>>> stuck even though everything else did. > > -- > Colin Percival > Security Officer, FreeBSD | freebsd.org | The power to serve > Founder / author, Tarsnap | tarsnap.com | Online backups for the truly pa= ranoid >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=yrY8W7BYTopY12Etyuzb=QR89mj69RpTnf74z>