Port-xen archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: kernel: supervisor trap asynchronous system trap, code=0

To: bouyer%antioche.eu.org@localhost
Subject: Re: kernel: supervisor trap asynchronous system trap, code=0
From: yamt%mwd.biglobe.ne.jp@localhost (YAMAMOTO Takashi)
Date: Tue, 4 Sep 2007 21:57:49 +0900 (JST)

> > anyway, please don't call ras_lookup with interrupt disabled.
> 
> OK. I just wanted to make sure the new context was fully installed before
> re-taking interrupts. I didn't notice a C function was being called.

can you fix it?

i'm still not sure why taking interrupts here is a bad thing.
have you investigated it since then?

YAMAMOTO Takashi

Follow-Ups:
- Re: kernel: supervisor trap asynchronous system trap, code=0
  - From: Manuel Bouyer

References:
- Re: kernel: supervisor trap asynchronous system trap, code=0
  - From: Manuel Bouyer

Prev by Date: Re: Xen2 bailout: "Aieee! CPU0 is toast..."
Next by Date: Re: Xen booting problem
Previous by Thread: Re: kernel: supervisor trap asynchronous system trap, code=0
Next by Thread: Re: kernel: supervisor trap asynchronous system trap, code=0
Indexes:

Home | Main Index | Thread Index | Old Index