linux-kernel - Re: Cannot boot xen DomU

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4790E13D.5040603@goop.org>
Date:	Fri, 18 Jan 2008 09:26:21 -0800
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	xming <xmingske@...il.com>
CC:	linux-kernel@...r.kernel.org,
	Xen-devel <xen-devel@...ts.xensource.com>
Subject: Re: Cannot boot xen DomU > 2.6.23.1

xming wrote:
>> Would it be possible to map the eip and some top parts of the stack back
>> to kernel symbols?  Seems to be the same place in both traces, which is
>> interesting.
>>     
>
> Can you tell me how, or show me some pointers?
>   

Do "nm -n vmlinux" on the kernel to set an address sorted list of 
symbols, and then look to see what's near the eip (c037c0c7) and near 
the top of the stack (c0100add, c0378980, c0101962, ...).  Some of these 
may be in data, or other strange places, but the ones which correspond 
to code are interesting.

>>> Scenario 2 (have_vcpu_info_placement = 0)
>>> --------------------------------------------------------------
>>>
>>> test1: no crash
>>> test2: no crash, but occationally I still get funny output like this
>>>
>>> 00AAAAAAAAAAAAAAAAAAAAAAAAAAZZ
>>> 00AAAAAAAAAAAAAAAAAAAAAAAAAAZZ00AAAAAAAAAAAAAAAAAAAAAAAAAAZZ
>>> 00AAAAAAAAAAAAAAAAAAAAAAAAAAZZ
>>> 00AAAAAAAAAAAAAAAAAAAAAAAAAAZZ
>>> 0000AAAAAAAAAAAAAAAAAAAAAAAAAAZZ
>>> 00AAAAAAAAAAAAAAAAAAAAAAAAAAZZ
>>> 00AAAAAAAAAAAAAAAAAAAAAAAAAAZZ
>>> 000AAAAAAAAAAAAAAAAAAAAAAAAAAZZ
>>> 000AAAAAAAAAAAAAAAAAAAAAAAAAAZZ
>>> 00AAAAAAAAAAAAAAAAAAAAAAAAAAZZ
>>>
>>>       
>> Hm, I guess some of the output is getting dropped.  Does this happen
>> with 2.6.18-xen?
>>     
>
> yes it does
>   

OK, good.  I Didn't Break It (tm) ;)

    J
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/