From: "Sven Köhler" <sven.koehler@gmail.com>
To: xen-devel@lists.xensource.com
Subject: 2.6.28.7 domU crashes
Date: Wed, 11 Mar 2009 23:47:52 +0100 [thread overview]
Message-ID: <gp9f31$g98$1@ger.gmane.org> (raw)
Hi,
below is the output of the kernel just before it goes down and crashes.
I have to use "xm destroy" to kill it.
I have tried the enable/disable the "Optimize for Size" setting in the
kernel. I hopes that it's some kind of compiler bug because of the
"invalid opcode" thing. But actually I don't a clue what this might be
caused by.
Do you have any idea?
The crash is very reproducable.
Regards,
Sven
-Os
------------[ cut here ]------------
kernel BUG at /usr/src/linux-2.6.28/drivers/block/xen-blkfront.c:243!
invalid opcode: 0000 [#1]
last sysfs file: /sys/kernel/uevent_seqnum
CPU 0
Pid: 4841, comm: ebuild Not tainted 2.6.28.7 #5
RIP: e030:[<ffffffff803f22ef>] [<ffffffff803f22ef>]
do_blkif_request+0x156/0x312
RSP: e02b:ffffffff806fee08 EFLAGS: 00010046
RAX: 0000000000000000 RBX: 0000000000000002 RCX: 0000000000000000
RDX: 0000000000000001 RSI: 000000000000000a RDI: 0000000000002fe0
RBP: ffff88001a96ba50 R08: ffffffff806337f0 R09: ffff88001a96d540
R10: 000000000000003e R11: ffffffff8024d9eb R12: ffff88001a8c66f0
R13: ffff88001a914000 R14: ffff88000ef2d7c0 R15: ffff88001664b788
FS: 00007f712f92a6d0(0000) GS:ffffffff80707000(0000) knlGS:0000000000000000
CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f712e085024 CR3: 000000001a3de000 CR4: 0000000000000660
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process ebuild (pid: 4841, threadinfo ffff8800166aa000, task
ffff8800167a4050)
Stack:
0000000000000019 ffff88001a968800 ffff88001a914000 000005fc00000000
000000000000000f 0000000000000002 0000000000000001 ffff88001a968820
ffffffff00000001 ffff88001a968800 0000000000000000 ffff88001a96ba50
Call Trace:
<IRQ> <0> [<ffffffff803a8d0a>] ? blk_invoke_request_fn+0x1e/0x3f
[<ffffffff803f24c3>] ? kick_pending_request_queues+0x18/0x24
[<ffffffff803f2f7a>] ? blkif_interrupt+0x1a0/0x1c2
[<ffffffff80248d4b>] ? handle_IRQ_event+0x2c/0x61
[<ffffffff8024a538>] ? handle_level_irq+0x5c/0xa0
[<ffffffff802114d4>] ? do_IRQ+0x57/0xb3
[<ffffffff803d2c68>] ? xen_evtchn_do_upcall+0x89/0xeb
[<ffffffff8049f22e>] ? xen_do_hypervisor_callback+0x1e/0x30
<EOI> <0>Code: 00 00 66 41 8b 46 2a 44 0f b7 e0 66 89 44 24 32 49 c1
e4 04 4d 03 66 48 c7 44 24 34 00 00 00 00 e9 f4 00 00 00 80 7d 01 0b 75
04 <0f> 0b eb fe 48 bf 00 00 00 00 00 1e 00 00 49 03 3c 24 48 b8 b7
RIP [<ffffffff803f22ef>] do_blkif_request+0x156/0x312
RSP <ffffffff806fee08>
Kernel panic - not syncing: Fatal exception in interrupt
-O2
------------[ cut here ]------------
kernel BUG at /usr/src/linux-2.6.28/drivers/block/xen-blkfront.c:243!
invalid opcode: 0000 [#1]
last sysfs file: /sys/kernel/uevent_seqnum
CPU 0
Pid: 4723, comm: ebuild Not tainted 2.6.28.7 #6
RIP: e030:[<ffffffff80449200>] [<ffffffff80449200>]
do_blkif_request+0x2f0/0x380
RSP: e02b:ffffffff80783df8 EFLAGS: 00010046
RAX: 0000000000000000 RBX: ffff88000505da40 RCX: ffff88000505da40
RDX: ffff88001a8c65a0 RSI: 000000000000000a RDI: 0000000000000520
RBP: ffff88001a96b3c0 R08: 0000000000002900 R09: 0000000000000000
R10: 0000000000000000 R11: 000000000000001a R12: 0000000000000520
R13: 0000000000000002 R14: ffff88001a8c65b0 R15: 0000000000000000
FS: 00007fd37d7596d0(0000) GS:ffffffff8078c000(0000) knlGS:0000000000000000
CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00000000006c4900 CR3: 00000000162c9000 CR4: 0000000000000660
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process ebuild (pid: 4723, threadinfo ffff88001638c000, task
ffff880016382450)
Stack:
000000000000004c ffff88001a966800 ffff88001a914000 ffff88000501fd48
000000008027c3d2 0000000000000015 ffff88001a914000 00000000803f0804
ffff88000505da40 ffff88001a966820 ffffffff00000001 ffff88001a966800
Call Trace:
<IRQ> <0> [<ffffffff803f0c73>] ? blk_invoke_request_fn+0x33/0x40
[<ffffffff804492a8>] ? kick_pending_request_queues+0x18/0x30
[<ffffffff80449ef3>] ? blkif_interrupt+0x1a3/0x1e0
[<ffffffff80255639>] ? handle_IRQ_event+0x39/0x80
[<ffffffff80257532>] ? handle_level_irq+0x52/0xc0
[<ffffffff80212a3c>] ? do_IRQ+0x5c/0xd0
[<ffffffff80423295>] ? xen_evtchn_do_upcall+0xa5/0xe0
[<ffffffff802379db>] ? __do_softirq+0xab/0x140
[<ffffffff805172ce>] ? xen_do_hypervisor_callback+0x1e/0x30
<EOI> <0>Code: fa d0 00 00 00 48 8d bc 07 88 00 00 00 e8 89 c2 fb ff
8b 7c 24 54 e8 20 93 fd ff ff 44 24 24 e9 3b fd ff ff 0f 0b eb fe 0f 1f
00 <0f> 0b eb fe 48 8b 7c 24 30 48 8b 54 24 30 b9 0b 00 00 00 48 c7
RIP [<ffffffff80449200>] do_blkif_request+0x2f0/0x380
RSP <ffffffff80783df8>
Kernel panic - not syncing: Fatal exception in interrupt
next reply other threads:[~2009-03-11 22:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 22:47 Sven Köhler [this message]
2009-03-12 0:29 ` 2.6.28.7 domU crashes Jeremy Fitzhardinge
2009-03-12 10:56 ` Sven Köhler
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='gp9f31$g98$1@ger.gmane.org' \
--to=sven.koehler@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.