All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 40542] New: overflow/panic on KVM hipervizor
Date: Thu, 4 Aug 2011 17:22:48 GMT	[thread overview]
Message-ID: <bug-40542-28872@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=40542

           Summary: overflow/panic on KVM hipervizor
           Product: Virtualization
           Version: unspecified
    Kernel Version: 3.0.0
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: kvm
        AssignedTo: virtualization_kvm@kernel-bugs.osdl.org
        ReportedBy: slawek@rozbicki.eu
        Regression: No


Created an attachment (id=67522)
 --> (https://bugzilla.kernel.org/attachment.cgi?id=67522)
some debug info like /proc/cpuinfo and .config from kernel

I have 2 machines virtualized with KVM on Gentoo host. There is a gentoo and
win2k8r2 guests (there is apache2 on gentoo which connects with php to mssql
server on the second guest). 

During the apache benchmark (ab -c 50 -n 100000 http://address/), hipervisor
TCP stack crashes (not entirely, but random anomalies are noticed for example
iptables -Lnv makes ssh session crashed). Here is kern.log snap:

---
 Aug  4 18:54:46 flu kernel: general protection fault: 0000 [#1] SMP
Aug  4 18:54:46 flu kernel: CPU 0
Aug  4 18:54:46 flu kernel: Modules linked in: bridge stp llc kvm_intel kvm
Aug  4 18:54:46 flu kernel:
Aug  4 18:54:46 flu kernel: Pid: 4327, comm: bash Not tainted
3.0.0-xxxx-std-ipv4-64 #7 Supermicro X8STi/X8STi
Aug  4 18:54:46 flu kernel: RIP: 0010:[<ffffffff810f8aaa>] 
[<ffffffff810f8aaa>] fget_light+0x6a/0xc0
Aug  4 18:54:46 flu kernel: RSP: 0018:ffff880579015f38  EFLAGS: 00010202
Aug  4 18:54:46 flu kernel: RAX: ffff8806196fa180 RBX: 00007fffdade98f0 RCX:
0000000000000008
Aug  4 18:54:46 flu kernel: RDX: 0000880618ffac80 RSI: ffff880579015f54 RDI:
ffff880618fc77f8
Aug  4 18:54:46 flu kernel: RBP: ffff880579015f38 R08: 0000000000000000 R09:
0000000000000000
Aug  4 18:54:46 flu kernel: R10: 0000000000000008 R11: 0000000000000246 R12:
00000000000000ff
Aug  4 18:54:46 flu kernel: R13: 0000000000005410 R14: 00007fffdade985c R15:
00000000007b6ae0
Aug  4 18:54:46 flu kernel: FS:  00007f495700d700(0000)
GS:ffff88063fc00000(0000) knlGS:0000000000000000
Aug  4 18:54:46 flu kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug  4 18:54:46 flu kernel: CR2: 00000000004620d0 CR3: 000000057927b000 CR4:
00000000000026e0
Aug  4 18:54:46 flu kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
Aug  4 18:54:46 flu kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
0000000000000400
Aug  4 18:54:46 flu kernel: Process bash (pid: 4327, threadinfo
ffff880579014000, task ffff88061aacc750)
Aug  4 18:54:46 flu kernel: Stack:
Aug  4 18:54:46 flu kernel: ffff880579015f78 ffffffff8110786a 0000000000010000
0000000000000000
Aug  4 18:54:46 flu kernel: 00007fffdade98f0 0000000000000082 00007fffdade9990
0000000000000000
Aug  4 18:54:46 flu kernel: 00000000000010e7 ffffffff818fe2fb 0000000000000246
0000000000000008
Aug  4 18:54:46 flu kernel: Call Trace:
Aug  4 18:54:46 flu kernel: [<ffffffff8110786a>] sys_ioctl+0x2a/0x80
Aug  4 18:54:46 flu kernel: [<ffffffff818fe2fb>] system_call_fastpath+0x16/0x1b
Aug  4 18:54:46 flu kernel: Code: 74 37 31 d2 48 89 d0 c9 c3 0f 1f 84 00 00 00
00 00 48 8b 40 08 3b 38 73 e9 89 ff 48 c1 e7 03 48 03 78 08 48 8b 17 48 85 d2
74 d9 <f6> 42 3d 40 75 d1 48 89 d0 c9 c3 0f 1f 00 48 8b 7a 30 4c 8d 42
Aug  4 18:54:46 flu kernel: RIP  [<ffffffff810f8aaa>] fget_light+0x6a/0xc0
Aug  4 18:54:46 flu kernel: RSP <ffff880579015f38>
Aug  4 18:54:46 flu kernel: ---[ end trace 9de898b3d5b9d4c6 ]---
Aug  4 18:54:46 flu kernel: general protection fault: 0000 [#2] SMP
Aug  4 18:54:46 flu kernel: CPU 0
Aug  4 18:54:46 flu kernel: Modules linked in: bridge stp llc kvm_intel kvm
Aug  4 18:54:46 flu kernel:
Aug  4 18:54:46 flu kernel: Pid: 4327, comm: bash Tainted: G      D    
3.0.0-xxxx-std-ipv4-64 #7 Supermicro X8STi/X8STi
Aug  4 18:54:46 flu kernel: RIP: 0010:[<ffffffff810f5567>] 
[<ffffffff810f5567>] filp_close+0x17/0x90
Aug  4 18:54:46 flu kernel: RSP: 0018:ffff880579015cc8  EFLAGS: 00010282
Aug  4 18:54:46 flu kernel: RAX: ffff880618fc77f8 RBX: 0000880618ffac80 RCX:
ffff8806196fa240
Aug  4 18:54:46 flu kernel: RDX: 0000000000000000 RSI: ffff880619648140 RDI:
0000880618ffac80
Aug  4 18:54:46 flu kernel: RBP: ffff880579015ce8 R08: 0000000000000000 R09:
0000000000000000
Aug  4 18:54:46 flu kernel: R10: ffff88061875c090 R11: 0000000000000446 R12:
0000000000000001
Aug  4 18:54:46 flu kernel: R13: ffff8806196fa180 R14: ffff880619648140 R15:
00000000000000ff
Aug  4 18:54:46 flu kernel: FS:  0000000000000000(0000)
GS:ffff88063fc00000(0000) knlGS:0000000000000000
Aug  4 18:54:46 flu kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug  4 18:54:46 flu kernel: CR2: 00000000004620d0 CR3: 0000000001b93000 CR4:
00000000000026e0
Aug  4 18:54:46 flu kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
Aug  4 18:54:46 flu kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
0000000000000400
Aug  4 18:54:46 flu kernel: Process bash (pid: 4327, threadinfo
ffff880579014000, task ffff88061aacc750)
Aug  4 18:54:46 flu kernel: Stack:
Aug  4 18:54:46 flu kernel: ffff880617983840 0000000000000003 0000000000000001
ffff8806196fa180
Aug  4 18:54:46 flu kernel: ffff880579015d38 ffffffff8104feb0 ffff8806179838a0
0000000000000000
Aug  4 18:54:46 flu kernel: ffff880579015d58 ffff88061aacc750 ffff880619648140
ffff880617983840
Aug  4 18:54:46 flu kernel: Call Trace:
Aug  4 18:54:46 flu kernel: [<ffffffff8104feb0>] put_files_struct+0xd0/0xf0
Aug  4 18:54:46 flu kernel: [<ffffffff8104ff15>] exit_files+0x45/0x50
Aug  4 18:54:46 flu kernel: [<ffffffff81051da8>] do_exit+0x718/0x830
Aug  4 18:54:46 flu kernel: [<ffffffff81005bfc>] oops_end+0x9c/0xe0
Aug  4 18:54:46 flu kernel: [<ffffffff81005d36>] die+0x56/0x90
Aug  4 18:54:46 flu kernel: [<ffffffff81003942>]
do_general_protection+0x152/0x160
Aug  4 18:54:46 flu kernel: [<ffffffff818fdeaf>] general_protection+0x1f/0x30
Aug  4 18:54:46 flu kernel: [<ffffffff810f8aaa>] ? fget_light+0x6a/0xc0
Aug  4 18:54:46 flu kernel: [<ffffffff8105c4d1>] ? sys_rt_sigprocmask+0x71/0xc0
Aug  4 18:54:46 flu kernel: [<ffffffff8110786a>] sys_ioctl+0x2a/0x80
Aug  4 18:54:46 flu kernel: [<ffffffff818fe2fb>] system_call_fastpath+0x16/0x1b
Aug  4 18:54:46 flu kernel: Code: 24 4c 8b 64 24 08 c9 c3 66 66 66 2e 0f 1f 84
00 00 00 00 00 55 48 89 e5 48 83 ec 20 48 89 5d e8 4c 89 65 f0 4c 89 6d f8 48
89 fb
Aug  4 18:54:46 flu kernel: RIP  [<ffffffff810f5567>] filp_close+0x17/0x90
Aug  4 18:54:46 flu kernel: RSP <ffff880579015cc8>
Aug  4 18:54:46 flu kernel: ---[ end trace 9de898b3d5b9d4c7 ]---
Aug  4 18:54:46 flu kernel: Fixing recursive fault but reboot is needed!
---

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

             reply	other threads:[~2011-08-04 17:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-04 17:22 bugzilla-daemon [this message]
2011-08-04 17:24 ` [Bug 40542] overflow/panic on KVM hipervizor bugzilla-daemon
2011-08-04 17:33 ` bugzilla-daemon
2011-08-07 13:39   ` Brad Campbell
2011-08-07 15:08     ` Avi Kivity
2011-08-08  1:40       ` Brad Campbell
2011-08-04 17:58 ` bugzilla-daemon
2011-08-05 17:17 ` bugzilla-daemon
2011-08-06 13:09 ` bugzilla-daemon
2011-08-06 16:21 ` bugzilla-daemon
2011-08-06 16:31 ` bugzilla-daemon
2011-08-06 16:33 ` bugzilla-daemon
2011-08-07 14:55 ` bugzilla-daemon
2011-08-07 15:10 ` bugzilla-daemon
2011-08-07 16:01 ` bugzilla-daemon
2011-08-08  1:41 ` bugzilla-daemon
2011-08-19 10:37 ` bugzilla-daemon
2014-06-25 16:08 ` bugzilla-daemon

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=bug-40542-28872@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@vger.kernel.org \
    /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.