From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jacob Gorm Hansen Subject: Re: netif_suspend / resume Date: Mon, 23 May 2005 15:27:13 -0700 Message-ID: <429258C1.4040003@diku.dk> References: <428E650E.3070409@diku.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Kip Macy , xen-devel List-Id: xen-devel@lists.xenproject.org Kip Macy wrote: > If you're not averse to GDB you can use the gdbserver to look at the > state. If it is calling domain_crash you can enable coredump. > Evidently some interface has changed that has broken gdbserver for the > moment, but once I finish with -testing this weekend I'll probably get > to submitting a patch. Thanks, I would like to play with gdb and xen at some point. Actually, I should probably rephrase my question: xenlinux in unstable crashes after executing the following code, and I don't think it should. Am I wrong? __cli(); netif_suspend(); time_suspend(); ctrl_if_suspend(); irq_suspend(); irq_resume(); ctrl_if_resume(); time_resume(); netif_resume(); __sti(); /Jacob