Re: kvm segfaults and bad page state in 3.4.0

2012-07-02 Thread Fengguang Wu 
Hi Guangrong,

On Tue, Jul 03, 2012 at 02:41:02PM +0800, Xiao Guangrong wrote:
> Hi Fengguang,
> 
> I can reproduce this bug in my test case, and have posted
> a patch to fix it which can found at:
> http://marc.info/?l=linux-mm&m=134129723504527&w=2
> 
> Could you please try it?

Thank you very much! I'm glad to try it out in my compile servers.
Note that I've not encountered the bug since then (seems not very
reproducible). So the feedback would be kind of "the patch works well"
rather than confirming that it fixed the bug for me. Sorry for that.

Thanks,
Fengguang

> On 06/04/2012 07:46 PM, Fengguang Wu wrote:
> > Hi,
> > 
> > I'm running lots of kvm instances for doing kernel boot tests.
> > Unfortunately the test system itself is not stable enough, I got scary
> > errors in both kvm and the host kernel. Like this. 
> > 
> > [294025.795382] kvm used greatest stack depth: 2896 bytes left
> > [310388.622083] kvm[1864]: segfault at c ip 7f498e9f6a81 sp 
> > 7f4994b9fca0 error 4 in kvm[7f498e96+33b000]
> > [310692.050589] kvm[4332]: segfault at 10 ip 7fca662620b9 sp 
> > 7fca70472af0 error 6 in kvm[7fca661cc000+33b000]
> > [312608.950120] kvm[18931]: segfault at 8 ip 7f95962a10a5 sp 
> > 7f959d777170 error 4 in kvm[7f959620b000+33b000]
> > [312622.941640] kvm[19123]: segfault at 10 ip 7f406f5580b9 sp 
> > 7f4077d8b350 error 6 in kvm[7f406f4c2000+33b000]
> > [313917.860951] kvm[28789]: segfault at c ip 7f718f4dfa81 sp 
> > 7f7198459520 error 4 in kvm[7f718f449000+33b000]
> > [313919.177192] kvm used greatest stack depth: 2864 bytes left
> > [314061.390945] kvm used greatest stack depth: 2208 bytes left
> > [327479.676068] BUG: Bad page state in process kvm  pfn:59ac9
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: kvm segfaults and bad page state in 3.4.0

2012-07-02 Thread Xiao Guangrong 
Hi Fengguang,

I can reproduce this bug in my test case, and have posted
a patch to fix it which can found at:
http://marc.info/?l=linux-mm&m=134129723504527&w=2

Could you please try it?

On 06/04/2012 07:46 PM, Fengguang Wu wrote:
> Hi,
> 
> I'm running lots of kvm instances for doing kernel boot tests.
> Unfortunately the test system itself is not stable enough, I got scary
> errors in both kvm and the host kernel. Like this. 
> 
> [294025.795382] kvm used greatest stack depth: 2896 bytes left
> [310388.622083] kvm[1864]: segfault at c ip 7f498e9f6a81 sp 
> 7f4994b9fca0 error 4 in kvm[7f498e96+33b000]
> [310692.050589] kvm[4332]: segfault at 10 ip 7fca662620b9 sp 
> 7fca70472af0 error 6 in kvm[7fca661cc000+33b000]
> [312608.950120] kvm[18931]: segfault at 8 ip 7f95962a10a5 sp 
> 7f959d777170 error 4 in kvm[7f959620b000+33b000]
> [312622.941640] kvm[19123]: segfault at 10 ip 7f406f5580b9 sp 
> 7f4077d8b350 error 6 in kvm[7f406f4c2000+33b000]
> [313917.860951] kvm[28789]: segfault at c ip 7f718f4dfa81 sp 
> 7f7198459520 error 4 in kvm[7f718f449000+33b000]
> [313919.177192] kvm used greatest stack depth: 2864 bytes left
> [314061.390945] kvm used greatest stack depth: 2208 bytes left
> [327479.676068] BUG: Bad page state in process kvm  pfn:59ac9

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: kvm segfaults and bad page state in 3.4.0

2012-06-04 Thread Fengguang Wu 
On Mon, Jun 04, 2012 at 08:35:30PM +0800, Fengguang Wu wrote:
> Hi Gleb,
> 
> On Mon, Jun 04, 2012 at 02:56:50PM +0300, Gleb Natapov wrote:
> > On Mon, Jun 04, 2012 at 07:46:03PM +0800, Fengguang Wu wrote:
> > > Hi,
> > > 
> > > I'm running lots of kvm instances for doing kernel boot tests.
> > > Unfortunately the test system itself is not stable enough, I got scary
> > > errors in both kvm and the host kernel. Like this. 
> > > 
> > What do you mean by "in both kvm and the host kernel". Do you have
> 
> I mean the host side's kvm user space process and kernel seem to have 
> problems.
> 
> > similar Oopses inside your guests? If yes can you post one?
> 
> There are all kinds of problems in the guest kernel, too. Probably I
> built in too many modules (take a debian config and s/=m/=y/) and
> enabled too many debug options. Many of the bugs I ran into have
> already been reported by others in LKML. Here are more weird things.

Two more boot errors..

storvsc device driver (from Microsoft..) bug:

[  108.445777] hv_vmbus: registering driver storvsc
[  108.498750] [ cut here ]
[  108.502649] kernel BUG at /c/kernel-tests/intel/drivers/base/driver.c:227!
[  108.502649] invalid opcode:  [#1] SMP DEBUG_PAGEALLOC
[  108.502649] CPU 0 
[  108.502649] Modules linked in:
[  108.502649] 
[  108.502649] Pid: 1, comm: swapper/0 Not tainted 3.2.0-rt13+ #1 Bochs Bochs
[  108.502649] RIP: 0010:[]  [] 
driver_register+0x24/0x116
[  108.502649] RSP: 0018:8800162c5e60  EFLAGS: 00010246
[  108.502649] RAX: 84131c40 RBX: 8411e580 RCX: 25232522
[  108.502649] RDX:  RSI: 82dac59f RDI: 8411e580
[  108.502649] RBP: 8800162c5ea0 R08: 0002 R09: 84f32270
[  108.502649] R10:  R11:  R12: 
[  108.502649] R13: 83aeeeff R14:  R15: 
[  108.502649] FS:  () GS:88001740() 
knlGS:
[  108.502649] CS:  0010 DS:  ES:  CR0: 8005003b
[  108.502649] CR2:  CR3: 03e12000 CR4: 06f0
[  108.502649] DR0:  DR1:  DR2: 
[  108.502649] DR3:  DR6: 0ff0 DR7: 0400
[  108.502649] Process swapper/0 (pid: 1, threadinfo 8800162c4000, task 
8800162c0040)
[  108.502649] Stack:
[  108.502649]  8800162c5eb0 8800162c5e70 8800162c5e80 
8411e560
[  108.502649]   83aeeeff  

[  108.502649]  8800162c5ed0 827e3b18 83e6eda8 
845d6460
[  108.502649] Call Trace:
[  108.502649]  [] __vmbus_driver_register+0x4a/0x5c
[  108.502649]  [] ? rtsx_init+0x29/0x29
[  108.502649]  [] storvsc_drv_init+0x35/0x3f
[  108.502649]  [] do_one_initcall+0x7f/0x13a
[  108.502649]  [] kernel_init+0xce/0x148
[  108.502649]  [] kernel_thread_helper+0x4/0x10
[  108.502649]  [] ? retint_restore_args+0x13/0x13
[  108.502649]  [] ? start_kernel+0x412/0x412
[  108.502649]  [] ? gs_change+0x13/0x13
[  108.502649] Code: 5c 41 5d 41 5e 5d c3 55 48 89 e5 41 57 41 56 41 55 41 54 
53 48 83 ec 18 66 66 66 66 90 48 8b 47 08 48 89 fb 48 83 78 68 00 75 02 <0f> 0b 
48 83 78 30 00 74 07 48 83 7f 30 00 75 1c 48 83 78 38 00 
[  108.502649] RIP  [] driver_register+0x24/0x116
[  108.502649]  RSP 
[  110.913751] ---[ end trace 184c66c6768bd651 ]---
[  110.967270] swapper/0 used greatest stack depth: 3688 bytes left
[  111.021415] Kernel panic - not syncing: Attempted to kill init!
[  111.075053] Pid: 1, comm: swapper/0 Tainted: G  D  3.2.0-rt13+ #1
[  111.130699] Call Trace:
[  111.185972]  [] panic+0xa0/0x1b3
[  111.241642]  [] ? _raw_write_unlock_irq+0x2e/0x47
[  111.294939]  [] do_exit+0x9b/0x7b7
[  111.349523]  [] ? kmsg_dump+0x82/0x135
[  111.402315]  [] oops_end+0xaf/0xb8
[  111.454034]  [] die+0x5a/0x66
[  111.505217]  [] do_trap+0x11a/0x129
[  111.555117]  [] do_invalid_op+0x98/0xa1
[  111.603546]  [] ? driver_register+0x24/0x116
[  111.651247]  [] ? trace_hardirqs_off_caller+0x3f/0x9e
[  111.700511]  [] ? trace_hardirqs_off_thunk+0x3a/0x3c
[  111.748561]  [] ? restore_args+0x30/0x30
[  111.796413]  [] invalid_op+0x1b/0x20
[  111.844369]  [] ? _raw_spin_unlock_irqrestore+0x3e/0x61
[  111.893537]  [] ? driver_register+0x24/0x116
[  111.943061]  [] __vmbus_driver_register+0x4a/0x5c
[  111.993386]  [] ? rtsx_init+0x29/0x29
[  112.043646]  [] storvsc_drv_init+0x35/0x3f
[  112.093912]  [] do_one_initcall+0x7f/0x13a
[  112.144693]  [] kernel_init+0xce/0x148
[  112.194717]  [] kernel_thread_helper+0x4/0x10
[  112.243875]  [] ? retint_restore_args+0x13/0x13
[  112.290508]  [] ? start_kernel+0x412/0x412
[  112.336927]  [] ? gs_change+0x13/0x13
[  112.382371] Rebooting in 10 seconds..


OOM when running udev net.agent (I suspect it's related to the new
kernel, since I didn't upgrade udev etc. recently):

[  319.628759] VFS: Mo

Re: kvm segfaults and bad page state in 3.4.0

2012-06-04 Thread Gleb Natapov 
On Mon, Jun 04, 2012 at 07:46:03PM +0800, Fengguang Wu wrote:
> Hi,
> 
> I'm running lots of kvm instances for doing kernel boot tests.
> Unfortunately the test system itself is not stable enough, I got scary
> errors in both kvm and the host kernel. Like this. 
> 
What do you mean by "in both kvm and the host kernel". Do you have
similar Oopses inside your guests? If yes can you post one?

--
Gleb.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html