Date: Mon, 15 Jul 2002 17:43:28 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Peter Wemm <peter@wemm.org> Cc: freebsd-current@freebsd.org Subject: Re: panic: absolutely cannot call smp_ipi_shootdown with interrupts already disabled Message-ID: <15667.16896.808227.270806@grasshopper.cs.duke.edu> In-Reply-To: <20020715211406.451A43811@overcee.wemm.org> References: <15667.13541.978257.347017@grasshopper.cs.duke.edu> <20020715211406.451A43811@overcee.wemm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Wemm writes: > Eww! Care to confirm that the following works? I was going to just commit > it since it is pretty obvious, but a brief sanity check would probably > be an idea. (beware, xterm cut/paste whitespace damage). > > ddb runs with interrupts disabled and the other cpus halted. We could not > get the 'ack' from the IPI. The panic was real - you'd have locked up hard > if it had not triggered. > > db_write_bytes temporarily changes a local cpu mapping and changes it back > while everything else is frozen. We do not need to do a coherent invalidate. That seems to work. Thanks! Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15667.16896.808227.270806>