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

Re: [Xen-devel] BUG: unable to handle kernel paging request at 0000000000003360 RIP: e030:[<ffffffff817bf0f6>] [<ffffffff817bf0f6>] xenvif_free+0x76/0x130

Friday, June 6, 2014, 12:28:02 PM, you wrote:

> On Fri, Jun 06, 2014 at 11:57:14AM +0200, Sander Eikelenboom wrote:
>> Friday, June 6, 2014, 11:33:56 AM, you wrote:
>> > Hi,
>> > Can you please do an "addr2line -e [your vmlinuz] ffffffff817bf0f6" to 
>> > figure out which line is causing the issue?
>> > Thanks,
>> > Zoli
>> addr2line doesn't work on vmlinuz (only on a uncompressed vmlinux), and 
>> unfortunately i don't have the build tree of that build anymore AND 
>> ./scripts/extract-vmlinux also doesn't seem to work for some reason 
>> :S *sigh*

> Can you obtain .config and rebuild?

> If you don't have .config anymore, another method is to boot into your
> Dom0 and check if there's /proc/config.gz. If so, zcat /proc/config.gz
> will give you back the .config file used to build this kernel.

> Wei.

Well it's not the .config i'm worried about .. it's the tree it self :)
 .. it was not a pristine upstream tree .. but a concoction of
linuses tree + bluetooth fixes + xen-devel + xen-multi-queue etc.

So i consider it impossible to recreate that at this point.

And unfortunately due to some space limitations, it's build without also 
the source .debs

I have now something out of vmlinuz that readelf recognizes but addr2line still 
doesn't give any lines back on any address from that stacktrace :-(

Xen-devel mailing list



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