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

Re: [Xen-devel] Xen 4.7.0 boot PANIC on kernel 4.7.0-4 + UEFI ?



>>> On 02.08.16 at 15:54, <lists@xxxxxxxxxxxx> wrote:

> 
> On Tue, Aug 2, 2016, at 06:38 AM, Jan Beulich wrote:
>> Well, without going through the _full_ thread again, what I could
>> easily find is
>> 
>> "So full console output from boot -> crash now doesn't look any different 
>> than 
> 
>> 
>>      https://lists.xen.org/archives/html/xen-devel/2016-07/msg02814.html 
>> "
>> 
>> which doesn't tell me at all which combination of /mapbs and/or
>> /noexitboot was used. Certainly in that run "efi=attr=uc" wasn't
>> used. It in particular seems highly questionable to me that the
>> reboot crash would look _exactly_ the same with /mapbs.
> 
> You keep stating what you don't see.

Because you keep being vague...

> Afaict, there are four options that seem to have been talked about 
> 
> /mapbs & /noexitboot on the EFI cmd line
> 
> and
> 
> efi=attr=uc and ef=no-rs on the xen cmd line
> 
> I really don't want to keep guessing and reposting unnecessary information, 
> and am TRYING to provide the right information.
> 
> Can you simply say what output you want?  What combination of options of efi 
> cmd line, xen cmd line, and log options?
> 
> I will provide THAT.

Unless /mapbs really produces an _exactly_ identical crash, I'd like to
see that boot's output at maximum log level. I don't recall "efi=no-rs"
having been mentioned before on this thread, but yes, I'd expect
that one to help as much as the suggested "reboot=..." option, so
if either doesn't, logs thereof would also be of interest.

Jan

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.