From: George Dunlap <George.Dunlap@eu.citrix.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: Sander Eikelenboom <linux@eikelenboom.it>, xen-devel@lists.xensource.com
Subject: Re: Crash during boot in Debian lenny default dom0 kernel (2.6.26-2-xen-686)
Date: Wed, 24 Feb 2010 23:57:38 +0000 [thread overview]
Message-ID: <de76405a1002241557y4449110v37b811fd36c60c4d@mail.gmail.com> (raw)
In-Reply-To: <20100224202009.GE2761@reaktio.net>
pci=nomsi in the guest command line?
I realize dom0 is a privileged guest, but it still seems like we
should try not to crash Xen as a result on guest input. :-)
Thanks for the work-around,
-George
On Wed, Feb 24, 2010 at 8:20 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> On Wed, Feb 24, 2010 at 08:08:10PM +0100, Sander Eikelenboom wrote:
>>
>> Wasn't pci=nomsi required for those kernels ?
>>
>
> Yeah, pci=nomsi has been the workaround for this bug..
> Many people have seen (and reported) this bug in the lenny kernel.
>
> Would be good to hunt down the actual reason..
>
> -- Pasi
>
>>
>> Wednesday, February 24, 2010, 7:47:09 PM, you wrote:
>>
>> > I recenty tried to boot my Debian lenny distro on a newer Intel
>> > Nehalem box using Debian Lenny's default xen kernel
>> > (2.6.26-2-xen-686), and it crashed during boot. Full log attached,
>> > but the key info is here:
>>
>> > I tried doing a "binary search" to see where this was introduced, but
>> > it fails the same way all the way back to c/s 20000.
>>
>> > The same kernel/hypervisor combination boots fine on a different box I have.
>>
>> > -George
>>
>> > (XEN) ----[ Xen-4.0.0-rc4 x86_64 debug=n Tainted: C ]----
>> > (XEN) CPU: 15
>> > (XEN) RIP: e008:[<ffff82c4801535a9>] pci_enable_msi+0x4c9/0x580
>> > (XEN) RFLAGS: 0000000000010282 CONTEXT: hypervisor
>> > (XEN) rax: ffff82c3ffeb6141 rbx: 0000000000000000 rcx: ffff830828b0e690
>> > (XEN) rdx: ffff830828b0e718 rsi: ffff8300bf6975b0 rdi: ffff830828b0e6e0
>> > (XEN) rbp: ffff83082cd7fec8 rsp: ffff83082cd7fd88 r8: 0000000000000005
>> > (XEN) r9: ffff830828b0e700 r10: 00000000000000a8 r11: 0000000000000040
>> > (XEN) r12: ffff830828b0e710 r13: ffff830828b0e670 r14: ffff83082cd7fe38
>> > (XEN) r15: 0000000000000000 cr0: 000000008005003b cr4: 00000000000026f0
>> > (XEN) cr3: 000000043fdcf000 cr2: ffff82c3ffeb614d
>> > (XEN) ds: 007b es: 007b fs: 00d8 gs: 0000 ss: 0000 cs: e008
>> > (XEN) Xen stack trace from rsp=ffff83082cd7fd88:
>> > (XEN) 0000000000000246 ffff830828b0e6e0 0000000080000000 0000000100000000
>> > (XEN) 3408000000000000 0000000200000000 000f5861e4a00100 0000000000000141
>> > (XEN) ffff83082cd71ec8 ffff83082cd7fec8 0000000000000136 ffff83082cd60000
>> > (XEN) 0000000000000038 00000000ffffffed 0000000000000000 ffff82c480154832
>> > (XEN) 00000000000004d8 0000000000000038 00000000000000e0 ffff83083fd81c80
>> > (XEN) ffff830828b0e670 00000000f5861e0c 0000000000000000 ffff83082cd60000
>> > (XEN) ffff83082cd400f0 00000000f5861e0c 0000000000000136 0000000000000038
>> > (XEN) ffff83082cd7fec8 ffff82c4801ede5f 7265646e776f206f ffff82c48024c080
>> > (XEN) ffff83082cd60180 ffff83082cd7fe98 0000000000007ff0 ffffffffffffffff
>> > (XEN) 0000000800000000 0000000100000000 ffff8308f5861e4a ffff82c4802eaa80
>> > (XEN) 0000000800000000 0000000000000038 f5861e4a00000001 000000000000000f
>> > (XEN) ffffffffffffffff ffff8300bf2e8000 0000000000000035 0000000000000000
>> > (XEN) 0000000000000000 0000000000000000 0000000000000000 ffff82c4801ef863
>> > (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
>> > (XEN) 0000000000000035 000000000000000d 0000000000000000 0000000000000000
>> > (XEN) 0000000000000000 0000000000000000 0000000000000021 00000000f5861e0c
>> > (XEN) 00000000c033741f 00000000ffffffff 0000000000000000 0000010000000000
>> > (XEN) 00000000c0101427 0000000000000061 0000000000000286 00000000f5861e08
>> > (XEN) 0000000000000069 0000000000000000 0000000000000000 0000000000000000
>> > (XEN) 0000000000000000 000000000000000f ffff8300bf2e8000
>> > (XEN) Xen call trace:
>> > (XEN) [<ffff82c4801535a9>] pci_enable_msi+0x4c9/0x580
>> > (XEN) [<ffff82c480154832>] map_domain_pirq+0x242/0x2f0
>> > (XEN) [<ffff82c4801ede5f>] compat_physdev_op+0xc8f/0x1010
>> > (XEN) [<ffff82c4801ef863>] compat_hypercall+0x83/0x90
>> > (XEN)
>> > (XEN) Pagetable walk from ffff82c3ffeb614d:
>> > (XEN) L4[0x105] = 00000000bf4e2027 5555555555555555
>> > (XEN) L3[0x10f] = 00000000bf698063 5555555555555555
>> > (XEN) L2[0x1ff] = 00000000bf697063 5555555555555555
>> > (XEN) L1[0x0b6] = f5861e4a00100173 ffffffffffffffff
>> > (XEN)
>> > (XEN) ****************************************
>> > (XEN) Panic on CPU 15:
>> > (XEN) FATAL PAGE FAULT
>> > (XEN) [error_code=000b]
>> > (XEN) Faulting linear address: ffff82c3ffeb614d
>> > (XEN) ****************************************
>>
>>
>>
>> --
>> Best regards,
>> Sander mailto:linux@eikelenboom.it
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2010-02-24 23:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 18:47 Crash during boot in Debian lenny default dom0 kernel (2.6.26-2-xen-686) George Dunlap
2010-02-24 19:08 ` Sander Eikelenboom
2010-02-24 20:20 ` Pasi Kärkkäinen
2010-02-24 23:57 ` George Dunlap [this message]
2010-02-25 6:50 ` Jiang, Yunhong
2010-02-25 10:48 ` George Dunlap
2010-02-25 10:56 ` Jan Beulich
2010-02-25 11:46 ` George Dunlap
2010-02-25 12:13 ` George Dunlap
2010-02-25 13:07 ` Jan Beulich
2010-02-25 13:19 ` Sander Eikelenboom
2010-02-25 13:24 ` Pasi Kärkkäinen
2010-02-25 13:43 ` Jan Beulich
2010-02-25 14:05 ` Pasi Kärkkäinen
2010-02-25 13:28 ` George Dunlap
2010-02-26 11:05 ` George Dunlap
2010-02-26 11:14 ` Sander Eikelenboom
2010-02-26 11:21 ` George Dunlap
2010-02-26 12:04 ` Pasi Kärkkäinen
2010-02-26 12:26 ` Sander Eikelenboom
2010-02-26 1:42 ` Jiang, Yunhong
2010-02-26 10:55 ` George Dunlap
2010-02-26 10:56 ` George Dunlap
2010-02-25 13:10 ` Jan Beulich
2010-02-25 9:16 ` Jan Beulich
2010-02-25 9:28 ` Jiang, Yunhong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=de76405a1002241557y4449110v37b811fd36c60c4d@mail.gmail.com \
--to=george.dunlap@eu.citrix.com \
--cc=linux@eikelenboom.it \
--cc=pasik@iki.fi \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).