kernel bug in linux-image-3.2.0-0.bpo.4-amd64
Hi!
I have a VIA VB8001-16 motherboard running xen and when using
linux-image-3.2.0-0.bpo.4-amd64 I can trigger a kernel oops in domU.
I suspect that this is caused by the bug
corrected in commit a349e23d1cf746f8bdc603dcc61fae9ee4a695f6 upstream.
But that is just my unqualified guess.
And for debian testing:
linux (3.2.35-1) unstable; urgency=low
.
* New upstream stable update:
...
- [x86] xen: don't corrupt %eip when returning from a signal
handler
Sorry for the poor formatting, below:
[ 854.826235] alignment check: 0000 [#1] SMP
[ 854.826265] CPU 0
[ 854.826273] Modules linked in: xenfs ext3 jbd evdev snd_pcm snd_timer
snd soundcore snd_page_alloc via_cputemp hwmon_vid pcspkr ext4 mbcache
jbd2 crc16 dm_mod xen_netfront xen_blkfront
[ 854.826354]
[ 854.826365] Pid: 2348, comm: asterisk Not tainted 3.2.0-0.bpo.4-amd64 #1 Debian 3.2.32-1~bpo60+1
[ 854.826391] RIP: e030:[<ffffffff8100e19f>] [<ffffffff8100e19f>] do_signal+0x28c/0x635
[ 854.826425] RSP: e02b:ffff880014d3be38 EFLAGS: 00250246
[ 854.826439] RAX: ffff880014d3bfd8 RBX: ffff880014d3bf58 RCX: 0000000000000000
[ 854.826456] RDX: 0000000000000000 RSI: 0000000000000001 RDI: 000000008005023b
[ 854.826473] RBP: 0000000000000017 R08: 0000000000000000 R09: 0000000000000008
[ 854.826490] R10: 0000000000007ff0 R11: 0000000000000000 R12: ffff880014d37380
[ 854.826508] R13: 00007f9e832b1b78 R14: ffff880014d36ee0 R15: 00007f9e832b1d40
[ 854.826531] FS: 00007f9e832b2700(0000) GS:ffff88003fc00000(0000) knlGS:0000000000000000
[ 854.826551] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b [ 854.826566] CR2: 00007f9e832b1ff8 CR3: 000000001e1bf000 CR4: 0000000000000620
[ 854.826584] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 854.826602] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 854.826620] Process asterisk (pid: 2348, threadinfo ffff880014d3a000, task ffff880014d36ee0)
[ 854.826639] Stack:
[ 854.826647] 0000000000000000 ffffffff81007555 0000000000000017 00007f9efffffffa
[ 854.826674] 0000006b00000541 ffff8800187a1d98 0000000000000000 0000000000000000
[ 854.826701] 00007f9e83238000 00007f9e83237000 00007f9e832b2700 0000000000000000
[ 854.826727] Call Trace:
[ 854.826747] [<ffffffff81007555>] ? get_phys_to_machine+0x16/0x58
[ 854.826768] [<ffffffff8136d4b3>] ? stub_clone+0x13/0x20
[ 854.826790] [<ffffffff8136d192>] ? system_call_fastpath+0x16/0x1b
[ 854.826808] [<ffffffff8100d722>] ? __switch_to+0x23b/0x2b1
[ 854.826826] [<ffffffff8100e56d>] ? do_notify_resume+0x25/0x67
[ 854.827041] [<ffffffff810470f2>] ? schedule_tail+0x24/0x56
[ 854.827060] [<ffffffff8136d460>] ? int_signal+0x12/0x17
[ 854.827075] Code: bd 38 01 00 00 e8 78 a7 04 00 85 c0 0f 85 70 02 00
00 65 48 8b 04 25 88 c6 00 00 8b 90 88 e0 ff ff c7 80 88 e0 ff ff 00 00
00 00 <48> 8b 05 fe e2 67 00 a9 00 00 00 04 74 0a 49 c7 45 08 01 00 00
[ 854.827253] RIP [<ffffffff8100e19f>] do_signal+0x28c/0x635
[ 854.827272] RSP <ffff880014d3be38>
[ 854.827299] ---[ end trace e5411f91d54565e6 ]---
Does anyone know more about this, or have any advice how to debug this?
I'm fairly capable (I think) of debugging code using gdb in userspace, never
tried kernel gdb though.
Thanks!
Kindly
// Mattias
Reply to: