Re: Panic on dom0 shutdown

[Johan Ihrén <johani%johani.org@localhost>]

Hi Manuel,

On Jan 7, 2013, at 11:39 , Manuel Bouyer wrote:

> On Thu, Jan 03, 2013 at 10:54:41AM +0100, Johan Ihrén wrote:
>>> points to; and this is where the faulty bus_space_read_4() is happening ...
>> 
>> Hmm. So using "-fno-optimize-sibling-calls" is not sufficient to avoid all 
>> tail-calls? Is there any other way of forcing no tail-calls? Otherwise it 
>> would seem that while tail-calls obviously improve performace they also make 
>> debugging... close to impossible.
> 
> Did you make a build from scratch ? maybe not all files got rebuilt with
> -fno-optimize-sibling-calls ?

Yes, this is with the kernel rebuilt from scratch. Still the same trace.

Johan

PS. FWIW, probably not really relevant, but if I turn off ddb.onpanic so that 
the box just reboots then the trace is slighty different. That trace looks like 
this:

printf_nolog()
startlwp()
alltraps()
pirq_interrupt()
Xresume_xenev6()
-- interrupt --
...