* kernel BUG at drivers/net/xen-netfront.c:305
[not found] <20130227193752.GA641@isprime.com>
@ 2013-02-28 12:23 ` Wei Liu
2013-02-28 13:20 ` annie li
0 siblings, 1 reply; 3+ messages in thread
From: Wei Liu @ 2013-02-28 12:23 UTC (permalink / raw)
To: David Olsen, xen-devel@lists.xen.org
Cc: annie li, wei.liu2, Ian Campbell, konrad.wilk@oracle.com
Drop Xen-user, add Xen-devel
Annie, this is the bug report I talked about. Have you encountered this
before?
Wei.
On Wed, 2013-02-27 at 19:37 +0000, David Olsen wrote:
> Hello,
>
> I've been having an issue with a particular DomU on a server. The Dom0 runs
> other instances just fine, this particular instance will run just fine for a
> few hours to a few days, then it will just die out with the following error:
>
> ---
> kernel BUG at drivers/net/xen-netfront.c:305!
> invalid opcode: 0000 [#1] SMP
> Modules linked in:
> CPU 0
> Pid: 0, comm: swapper/0 Not tainted 3.6.6-gentoo #1
> RIP: e030:[<ffffffff812c14ad>] [<ffffffff812c14ad>] xennet_alloc_rx_buffers+0x1d7/0x2fe
> RSP: e02b:ffff88006da03d80 EFLAGS: 00010286
> RAX: 00000000000001ff RBX: ffff880066f88000 RCX: 0000000000000001
> RDX: 0000000000000057 RSI: 0000000000000000 RDI: 0000000000004fc0
> RBP: 000000000cc1323f R08: 0000000000000000 R09: 00000000000038df
> R10: 00000000000004f1 R11: 0000000000003431 R12: 000000000cc13257
> R13: ffff8800669c0600 R14: 00000000000004fc R15: 0000000000000057
> FS: 00007fcb35820740(0000) GS:ffff88006da00000(0000) knlGS:0000000000000000
> CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: 00007fcb3052e260 CR3: 000000005aa3a000 CR4: 0000000000042660
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Process swapper/0 (pid: 0, threadinfo ffffffff81586000, task ffffffff81599410)
> Stack:
> 0000000000000056 0000001864b24900 ffff880066f89430 ffff880066f89c80
> ffff880066f88000 0000000000000001 ffff880066f88758 ffff88006da18d30
> ffff880066f88000 0000000000000000 ffff88006da03e28 ffffffff812c2a61
> Call Trace:
> <IRQ>
> [<ffffffff812c2a61>] ? xennet_poll+0xa0a/0xa98
> [<ffffffff8104e45d>] ? hrtimer_interrupt+0x112/0x1c9
> [<ffffffff81326920>] ? net_rx_action+0x6e/0x139
> [<ffffffff8103a91a>] ? __do_softirq+0x9c/0x145
> [<ffffffff81281e9d>] ? __xen_evtchn_do_upcall+0x1b0/0x1ed
> [<ffffffff8141973c>] ? call_softirq+0x1c/0x30
> [<ffffffff8100be36>] ? do_softirq+0x3c/0x7a
> [<ffffffff8103ab82>] ? irq_exit+0x42/0x9a
> [<ffffffff812838cb>] ? xen_evtchn_do_upcall+0x27/0x32
> [<ffffffff8141978e>] ? xen_do_hypervisor_callback+0x1e/0x30
> <EOI>
> [<ffffffff810013aa>] ? hypercall_page+0x3aa/0x1000
> [<ffffffff810013aa>] ? hypercall_page+0x3aa/0x1000
> [<ffffffff81006836>] ? xen_safe_halt+0xc/0x13
> [<ffffffff81011003>] ? default_idle+0x23/0x3f
> [<ffffffff8101182c>] ? cpu_idle+0x60/0xa2
> [<ffffffff8161baca>] ? start_kernel+0x32e/0x339
> [<ffffffff8161b5b5>] ? repair_env_string+0x54/0x54
> [<ffffffff8161e2b2>] ? xen_start_kernel+0x465/0x46b
> Code: 45 08 49 c7 45 08 00 00 00 00 48 89 42 08 48 89 10 41 0f b6 d7 49 89 5d 20 48 8d 82 a8 01 00 00 48 83 bc c3 40 07 00 00 00 74 02 <0f> 0b 48 8b 7c 24 18 4c 89 ac c3 40 07 00 00 48 89 14 24 e8 e2
> RIP [<ffffffff812c14ad>] xennet_alloc_rx_buffers+0x1d7/0x2fe
> RSP <ffff88006da03d80>
> ---[ end trace 77f364e88037c131 ]---
> Kernel panic - not syncing: Fatal exception in interrupt
> ---
>
> Here's the config for that instance:
> kernel = "/xen/kernels/kernel-linux-3.6.11-domU"
> memory = 6144
> maxmem = 16384
> maxvcpus = 24
> vcpus = 2
> name = "REDACTED"
> disk = ['phy:/dev/vg/REDACTED-root,sda1,w','phy:/dev/swap/REDACTED-swap,sdb1,w']
> root = "/dev/xvda1 ro"
> extra = "console=hvc0 xencons=tty"
> vif = [ 'bridge=eth0,mac=00:16:3e:52:ca:47', 'bridge=eth1,mac=00:16:3e:d4:b7:d8' ]
>
> It's just a basic LAMP setup, with the MySQL being external to the instance.
>
> Running xen version 4.2.0 on a Gentoo Linux box.
>
> Let me know if the error looks familiar to anyone, or if there is any more
> information I can provide.
>
> -d
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: kernel BUG at drivers/net/xen-netfront.c:305
2013-02-28 12:23 ` kernel BUG at drivers/net/xen-netfront.c:305 Wei Liu
@ 2013-02-28 13:20 ` annie li
2013-02-28 13:57 ` Wei Liu
0 siblings, 1 reply; 3+ messages in thread
From: annie li @ 2013-02-28 13:20 UTC (permalink / raw)
To: Wei Liu
Cc: David Olsen, konrad.wilk@oracle.com, Ian Campbell,
xen-devel@lists.xen.org
On 2013-2-28 20:23, Wei Liu wrote:
> Drop Xen-user, add Xen-devel
>
> Annie, this is the bug report I talked about. Have you encountered this
> before?
No, I didn't.
Probably it is what Konrad hit when he run netperf test with bunch of
your patches? I did not check the issue you fixed in Konrad's tree at
that time.
Thanks
Annie
>
>
> Wei.
>
> On Wed, 2013-02-27 at 19:37 +0000, David Olsen wrote:
>> Hello,
>>
>> I've been having an issue with a particular DomU on a server. The Dom0 runs
>> other instances just fine, this particular instance will run just fine for a
>> few hours to a few days, then it will just die out with the following error:
>>
>> ---
>> kernel BUG at drivers/net/xen-netfront.c:305!
>> invalid opcode: 0000 [#1] SMP
>> Modules linked in:
>> CPU 0
>> Pid: 0, comm: swapper/0 Not tainted 3.6.6-gentoo #1
>> RIP: e030:[<ffffffff812c14ad>] [<ffffffff812c14ad>] xennet_alloc_rx_buffers+0x1d7/0x2fe
>> RSP: e02b:ffff88006da03d80 EFLAGS: 00010286
>> RAX: 00000000000001ff RBX: ffff880066f88000 RCX: 0000000000000001
>> RDX: 0000000000000057 RSI: 0000000000000000 RDI: 0000000000004fc0
>> RBP: 000000000cc1323f R08: 0000000000000000 R09: 00000000000038df
>> R10: 00000000000004f1 R11: 0000000000003431 R12: 000000000cc13257
>> R13: ffff8800669c0600 R14: 00000000000004fc R15: 0000000000000057
>> FS: 00007fcb35820740(0000) GS:ffff88006da00000(0000) knlGS:0000000000000000
>> CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
>> CR2: 00007fcb3052e260 CR3: 000000005aa3a000 CR4: 0000000000042660
>> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
>> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
>> Process swapper/0 (pid: 0, threadinfo ffffffff81586000, task ffffffff81599410)
>> Stack:
>> 0000000000000056 0000001864b24900 ffff880066f89430 ffff880066f89c80
>> ffff880066f88000 0000000000000001 ffff880066f88758 ffff88006da18d30
>> ffff880066f88000 0000000000000000 ffff88006da03e28 ffffffff812c2a61
>> Call Trace:
>> <IRQ>
>> [<ffffffff812c2a61>] ? xennet_poll+0xa0a/0xa98
>> [<ffffffff8104e45d>] ? hrtimer_interrupt+0x112/0x1c9
>> [<ffffffff81326920>] ? net_rx_action+0x6e/0x139
>> [<ffffffff8103a91a>] ? __do_softirq+0x9c/0x145
>> [<ffffffff81281e9d>] ? __xen_evtchn_do_upcall+0x1b0/0x1ed
>> [<ffffffff8141973c>] ? call_softirq+0x1c/0x30
>> [<ffffffff8100be36>] ? do_softirq+0x3c/0x7a
>> [<ffffffff8103ab82>] ? irq_exit+0x42/0x9a
>> [<ffffffff812838cb>] ? xen_evtchn_do_upcall+0x27/0x32
>> [<ffffffff8141978e>] ? xen_do_hypervisor_callback+0x1e/0x30
>> <EOI>
>> [<ffffffff810013aa>] ? hypercall_page+0x3aa/0x1000
>> [<ffffffff810013aa>] ? hypercall_page+0x3aa/0x1000
>> [<ffffffff81006836>] ? xen_safe_halt+0xc/0x13
>> [<ffffffff81011003>] ? default_idle+0x23/0x3f
>> [<ffffffff8101182c>] ? cpu_idle+0x60/0xa2
>> [<ffffffff8161baca>] ? start_kernel+0x32e/0x339
>> [<ffffffff8161b5b5>] ? repair_env_string+0x54/0x54
>> [<ffffffff8161e2b2>] ? xen_start_kernel+0x465/0x46b
>> Code: 45 08 49 c7 45 08 00 00 00 00 48 89 42 08 48 89 10 41 0f b6 d7 49 89 5d 20 48 8d 82 a8 01 00 00 48 83 bc c3 40 07 00 00 00 74 02 <0f> 0b 48 8b 7c 24 18 4c 89 ac c3 40 07 00 00 48 89 14 24 e8 e2
>> RIP [<ffffffff812c14ad>] xennet_alloc_rx_buffers+0x1d7/0x2fe
>> RSP <ffff88006da03d80>
>> ---[ end trace 77f364e88037c131 ]---
>> Kernel panic - not syncing: Fatal exception in interrupt
>> ---
>>
>> Here's the config for that instance:
>> kernel = "/xen/kernels/kernel-linux-3.6.11-domU"
>> memory = 6144
>> maxmem = 16384
>> maxvcpus = 24
>> vcpus = 2
>> name = "REDACTED"
>> disk = ['phy:/dev/vg/REDACTED-root,sda1,w','phy:/dev/swap/REDACTED-swap,sdb1,w']
>> root = "/dev/xvda1 ro"
>> extra = "console=hvc0 xencons=tty"
>> vif = [ 'bridge=eth0,mac=00:16:3e:52:ca:47', 'bridge=eth1,mac=00:16:3e:d4:b7:d8' ]
>>
>> It's just a basic LAMP setup, with the MySQL being external to the instance.
>>
>> Running xen version 4.2.0 on a Gentoo Linux box.
>>
>> Let me know if the error looks familiar to anyone, or if there is any more
>> information I can provide.
>>
>> -d
>>
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xen.org
>> http://lists.xen.org/xen-users
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: kernel BUG at drivers/net/xen-netfront.c:305
2013-02-28 13:20 ` annie li
@ 2013-02-28 13:57 ` Wei Liu
0 siblings, 0 replies; 3+ messages in thread
From: Wei Liu @ 2013-02-28 13:57 UTC (permalink / raw)
To: annie li
Cc: David Olsen, konrad.wilk@oracle.com, wei.liu2, Ian Campbell,
xen-devel@lists.xen.org
On Thu, 2013-02-28 at 13:20 +0000, annie li wrote:
> On 2013-2-28 20:23, Wei Liu wrote:
> > Drop Xen-user, add Xen-devel
> >
> > Annie, this is the bug report I talked about. Have you encountered this
> > before?
>
> No, I didn't.
> Probably it is what Konrad hit when he run netperf test with bunch of
> your patches? I did not check the issue you fixed in Konrad's tree at
> that time.
>
Could be. But this is a kernel without my patches, so I'm suspecting it
is a vanilla bug.
Wei.
> Thanks
> Annie
> >
> >
> > Wei.
> >
> > On Wed, 2013-02-27 at 19:37 +0000, David Olsen wrote:
> >> Hello,
> >>
> >> I've been having an issue with a particular DomU on a server. The Dom0 runs
> >> other instances just fine, this particular instance will run just fine for a
> >> few hours to a few days, then it will just die out with the following error:
> >>
> >> ---
> >> kernel BUG at drivers/net/xen-netfront.c:305!
> >> invalid opcode: 0000 [#1] SMP
> >> Modules linked in:
> >> CPU 0
> >> Pid: 0, comm: swapper/0 Not tainted 3.6.6-gentoo #1
> >> RIP: e030:[<ffffffff812c14ad>] [<ffffffff812c14ad>] xennet_alloc_rx_buffers+0x1d7/0x2fe
> >> RSP: e02b:ffff88006da03d80 EFLAGS: 00010286
> >> RAX: 00000000000001ff RBX: ffff880066f88000 RCX: 0000000000000001
> >> RDX: 0000000000000057 RSI: 0000000000000000 RDI: 0000000000004fc0
> >> RBP: 000000000cc1323f R08: 0000000000000000 R09: 00000000000038df
> >> R10: 00000000000004f1 R11: 0000000000003431 R12: 000000000cc13257
> >> R13: ffff8800669c0600 R14: 00000000000004fc R15: 0000000000000057
> >> FS: 00007fcb35820740(0000) GS:ffff88006da00000(0000) knlGS:0000000000000000
> >> CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
> >> CR2: 00007fcb3052e260 CR3: 000000005aa3a000 CR4: 0000000000042660
> >> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> >> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> >> Process swapper/0 (pid: 0, threadinfo ffffffff81586000, task ffffffff81599410)
> >> Stack:
> >> 0000000000000056 0000001864b24900 ffff880066f89430 ffff880066f89c80
> >> ffff880066f88000 0000000000000001 ffff880066f88758 ffff88006da18d30
> >> ffff880066f88000 0000000000000000 ffff88006da03e28 ffffffff812c2a61
> >> Call Trace:
> >> <IRQ>
> >> [<ffffffff812c2a61>] ? xennet_poll+0xa0a/0xa98
> >> [<ffffffff8104e45d>] ? hrtimer_interrupt+0x112/0x1c9
> >> [<ffffffff81326920>] ? net_rx_action+0x6e/0x139
> >> [<ffffffff8103a91a>] ? __do_softirq+0x9c/0x145
> >> [<ffffffff81281e9d>] ? __xen_evtchn_do_upcall+0x1b0/0x1ed
> >> [<ffffffff8141973c>] ? call_softirq+0x1c/0x30
> >> [<ffffffff8100be36>] ? do_softirq+0x3c/0x7a
> >> [<ffffffff8103ab82>] ? irq_exit+0x42/0x9a
> >> [<ffffffff812838cb>] ? xen_evtchn_do_upcall+0x27/0x32
> >> [<ffffffff8141978e>] ? xen_do_hypervisor_callback+0x1e/0x30
> >> <EOI>
> >> [<ffffffff810013aa>] ? hypercall_page+0x3aa/0x1000
> >> [<ffffffff810013aa>] ? hypercall_page+0x3aa/0x1000
> >> [<ffffffff81006836>] ? xen_safe_halt+0xc/0x13
> >> [<ffffffff81011003>] ? default_idle+0x23/0x3f
> >> [<ffffffff8101182c>] ? cpu_idle+0x60/0xa2
> >> [<ffffffff8161baca>] ? start_kernel+0x32e/0x339
> >> [<ffffffff8161b5b5>] ? repair_env_string+0x54/0x54
> >> [<ffffffff8161e2b2>] ? xen_start_kernel+0x465/0x46b
> >> Code: 45 08 49 c7 45 08 00 00 00 00 48 89 42 08 48 89 10 41 0f b6 d7 49 89 5d 20 48 8d 82 a8 01 00 00 48 83 bc c3 40 07 00 00 00 74 02 <0f> 0b 48 8b 7c 24 18 4c 89 ac c3 40 07 00 00 48 89 14 24 e8 e2
> >> RIP [<ffffffff812c14ad>] xennet_alloc_rx_buffers+0x1d7/0x2fe
> >> RSP <ffff88006da03d80>
> >> ---[ end trace 77f364e88037c131 ]---
> >> Kernel panic - not syncing: Fatal exception in interrupt
> >> ---
> >>
> >> Here's the config for that instance:
> >> kernel = "/xen/kernels/kernel-linux-3.6.11-domU"
> >> memory = 6144
> >> maxmem = 16384
> >> maxvcpus = 24
> >> vcpus = 2
> >> name = "REDACTED"
> >> disk = ['phy:/dev/vg/REDACTED-root,sda1,w','phy:/dev/swap/REDACTED-swap,sdb1,w']
> >> root = "/dev/xvda1 ro"
> >> extra = "console=hvc0 xencons=tty"
> >> vif = [ 'bridge=eth0,mac=00:16:3e:52:ca:47', 'bridge=eth1,mac=00:16:3e:d4:b7:d8' ]
> >>
> >> It's just a basic LAMP setup, with the MySQL being external to the instance.
> >>
> >> Running xen version 4.2.0 on a Gentoo Linux box.
> >>
> >> Let me know if the error looks familiar to anyone, or if there is any more
> >> information I can provide.
> >>
> >> -d
> >>
> >>
> >> _______________________________________________
> >> Xen-users mailing list
> >> Xen-users@lists.xen.org
> >> http://lists.xen.org/xen-users
> >
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-02-28 13:57 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20130227193752.GA641@isprime.com>
2013-02-28 12:23 ` kernel BUG at drivers/net/xen-netfront.c:305 Wei Liu
2013-02-28 13:20 ` annie li
2013-02-28 13:57 ` Wei Liu
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.