Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #183059 > unrolled thread

Kernel Panic in VMXNET3 Driver

Started byMini Trader <miniflowtrader@gmail.com>
First post2017-07-03 23:40 +0200
Last post2017-07-04 08:30 +0200
Articles 7 — 2 participants

Back to article view | Back to linux.debian.user

Contents

  Kernel Panic in VMXNET3 Driver Mini Trader <miniflowtrader@gmail.com> - 2017-07-03 23:40 +0200
    Re: Kernel Panic in VMXNET3 Driver deloptes <deloptes@gmail.com> - 2017-07-03 23:50 +0200
      Re: Kernel Panic in VMXNET3 Driver Mini Trader <miniflowtrader@gmail.com> - 2017-07-04 00:10 +0200
        Re: Kernel Panic in VMXNET3 Driver Mini Trader <miniflowtrader@gmail.com> - 2017-07-04 00:20 +0200
          Re: Kernel Panic in VMXNET3 Driver deloptes <deloptes@gmail.com> - 2017-07-04 00:50 +0200
            Re: Kernel Panic in VMXNET3 Driver Mini Trader <miniflowtrader@gmail.com> - 2017-07-04 01:00 +0200
              Re: Kernel Panic in VMXNET3 Driver deloptes <deloptes@gmail.com> - 2017-07-04 08:30 +0200

#183059 — Kernel Panic in VMXNET3 Driver

FromMini Trader <miniflowtrader@gmail.com>
Date2017-07-03 23:40 +0200
SubjectKernel Panic in VMXNET3 Driver
Message-ID<tZhey-7h6-19@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

I had posted earlier that I was having issues with a java program but after
doing some quick digging I've been able to identity the error.  I enabled
logging kernel messages over the network and was able to capture this.
Would appreciate some guidance on where to go from here.

[  118.656721] ------------[ cut here ]------------
[  118.657261] kernel BUG at
/build/linux-9uDFZV/linux-4.9.30/drivers/net/vmxnet3/vmxnet3_drv.c:1413!
[  118.658106] invalid opcode: 0000 [#1] SMP
[  118.658628] Modules linked in: netconsole configfs sb_edac edac_core
coretemp crct10dif_pclmul ppdev crc32_pclmul vmw_balloon
ghash_clmulni_intel intel_rapl_perf joydev serio_raw pcspkr sg shpchp
vmwgfx vmw_vmci ttm drm_kms_helper drm nfit libnvdimm battery evdev
parport_pc parport ac acpi_cpufreq button ip_tables x_tables autofs4 ext4
crc16 jbd2 crc32c_generic fscrypto ecb mbcache dm_mod sr_mod cdrom sd_mod
ata_generic crc32c_intel aesni_intel aes_x86_64 glue_helper lrw gf128mul
ablk_helper cryptd psmouse ata_piix vmxnet3 vmw_pvscsi i2c_piix4 libata
scsi_mod
[  118.661572] CPU: 0 PID: 891 Comm: java Not tainted 4.9.0-3-amd64 #1
Debian 4.9.30-2+deb9u2
[  118.662153] Hardware name: VMware, Inc. VMware Virtual Platform/440BX
Desktop Reference Platform, BIOS 6.00 04/05/2016
[  118.663136] task: ffff8dd87882a0c0 task.stack: ffffa99981470000
[  118.663695] RIP: 0010:[<ffffffffc0217725>]  [<ffffffffc0217725>]
vmxnet3_rq_rx_complete+0x905/0xf10 [vmxnet3]
[  118.664735] RSP: 0000:ffff8dd87fc03e38  EFLAGS: 00010297
[  118.665279] RAX: 0000000000000000 RBX: 0000000000000000 RCX:
ffff8dd878ad5a00
[  118.665857] RDX: 0000000000000040 RSI: 0000000000000001 RDI:
0000000000000040
[  118.666426] RBP: 0000000000000001 R08: 0000000000000000 R09:
0000000000000028
[  118.666984] R10: 0000000000000000 R11: ffff8dd8369688c0 R12:
ffff8dd8369690c0
[  118.667613] R13: ffff8dd835ea8330 R14: ffff8dd87c192010 R15:
ffff8dd835ed8018
[  118.668172] FS:  00007f1b1974e700(0000) GS:ffff8dd87fc00000(0000)
knlGS:0000000000000000
[  118.668723] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  118.669310] CR2: 00007f1ad63e2fd8 CR3: 000000007bcac000 CR4:
00000000003406f0
[  118.669892] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[  118.670520] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
0000000000000400
[  118.671099] Stack:
[  118.671677]  ffff8dd836969190 0000004000000007 0000000000000002
ffff8dd8369690e0
[  118.672313]  ffffffffb22b002d ffff8dd8369688c0 0000000000000000
ffff8dd8369688c0
[  118.672950]  0000000000000000 ffff8dd8369688c0 ffff8dd8369690e0
0000000000000040
[  118.673603] Call Trace:
[  118.674166]  <IRQ> [  118.674180]  [<ffffffffb22b002d>] ?
task_numa_fault+0x6ed/0xd20
[  118.674876]  [<ffffffffc0217e75>] ? vmxnet3_poll_rx_only+0x35/0xa0
[vmxnet3]
[  118.675479]  [<ffffffffb2700b80>] ? net_rx_action+0x240/0x370
[  118.676099]  [<ffffffffb2808d95>] ? __do_softirq+0x105/0x290
[  118.676681]  [<ffffffffb227cf6e>] ? irq_exit+0xae/0xb0
[  118.677294]  [<ffffffffb2808aef>] ? do_IRQ+0x4f/0xd0
[  118.677971]  [<ffffffffb2806c02>] ? common_interrupt+0x82/0x82
[  118.678522]  <EOI> [  118.678532] Code:
89 54 24 28 e8 9d 72 4e f2 0f b6 44 24 30 4c 8b 5c 24 38 4c 8b 54 24 28 49
c7 84 24 48 01 00 00 00 00 00 00 89 c6 e9 59 f8 ff ff <0f> 0b 0f 0b 49 83
84 24 a0 01 00 00 01 49 c7 84 24 48 01 00 00
[  118.680438] RIP  [<ffffffffc0217725>] vmxnet3_rq_rx_complete+0x905/0xf10
[vmxnet3]
[  118.681063]  RSP <ffff8dd87fc03e38>
[  118.681676] ---[ end trace 5927dc1afdb8f3dd ]---
[  118.682244] Kernel panic - not syncing: Fatal exception in interrupt
[  118.682880] Kernel Offset: 0x31200000 from 0xffffffff81000000
(relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[  118.683993] ---[ end Kernel panic - not syncing: Fatal exception in
interrupt

[toc] | [next] | [standalone]

#183060

Fromdeloptes <deloptes@gmail.com>
Date2017-07-03 23:50 +0200
Message-ID<tZhod-7kC-9@gated-at.bofh.it>
In reply to#183059
Mini Trader wrote:

> task_numa_fault+0x6ed/0xd20

what happens if you boot the vm with numa=off

[toc] | [prev] | [next] | [standalone]

#183063

FromMini Trader <miniflowtrader@gmail.com>
Date2017-07-04 00:10 +0200
Message-ID<tZhHA-7Go-7@gated-at.bofh.it>
In reply to#183060

[Multipart message — attachments visible in raw view] — view raw

Looks to be the same.

On Mon, Jul 3, 2017 at 5:48 PM, deloptes <deloptes@gmail.com> wrote:

> Mini Trader wrote:
>
> > task_numa_fault+0x6ed/0xd20
>
> what happens if you boot the vm with numa=off
>
>
>
>

[toc] | [prev] | [next] | [standalone]

#183065

FromMini Trader <miniflowtrader@gmail.com>
Date2017-07-04 00:20 +0200
Message-ID<tZhRf-7JE-9@gated-at.bofh.it>
In reply to#183063

[Multipart message — attachments visible in raw view] — view raw

More information.  I found a post here:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650635

They mention LRO so I disabled it.  I cannot reproduce if LRO is disabled.

On Mon, Jul 3, 2017 at 5:59 PM, Mini Trader <miniflowtrader@gmail.com>
wrote:

> Looks to be the same.
>
> On Mon, Jul 3, 2017 at 5:48 PM, deloptes <deloptes@gmail.com> wrote:
>
>> Mini Trader wrote:
>>
>> > task_numa_fault+0x6ed/0xd20
>>
>> what happens if you boot the vm with numa=off
>>
>>
>>
>>
>

[toc] | [prev] | [next] | [standalone]

#183069

Fromdeloptes <deloptes@gmail.com>
Date2017-07-04 00:50 +0200
Message-ID<tZikh-7UA-3@gated-at.bofh.it>
In reply to#183065
Mini Trader wrote:

> More information.  I found a post here:
> 
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650635
> 
> They mention LRO so I disabled it.  I cannot reproduce if LRO is disabled.
> 
> On Mon, Jul 3, 2017 at 5:59 PM, Mini Trader <miniflowtrader@gmail.com>
> wrote:
> 
>> Looks to be the same.
>>
>> On Mon, Jul 3, 2017 at 5:48 PM, deloptes <deloptes@gmail.com> wrote:
>>
>>> Mini Trader wrote:
>>>
>>> > task_numa_fault+0x6ed/0xd20
>>>
>>> what happens if you boot the vm with numa=off
>>>
>>>
>>>
>>>
>>

the change mentioned in the article is in the kernel - at least 4.11.2 - I
don't know about your version. The article is about 4.4.

perhaps solved by chance - you have to report back to kernel maintainer I
guess

4.11.2 and 4.10.14

line nr 1395 to 1415
                        if (VMXNET3_VERSION_GE_2(adapter) &&
                            rcd->type == VMXNET3_CDTYPE_RXCOMP_LRO) {
                                struct Vmxnet3_RxCompDescExt *rcdlro;
                                rcdlro = (struct Vmxnet3_RxCompDescExt
*)rcd;

                                segCnt = rcdlro->segCnt;
                                WARN_ON_ONCE(segCnt == 0);
                                mss = rcdlro->mss;
                                if (unlikely(segCnt <= 1))
                                        segCnt = 0;
                        } else {
                                segCnt = 0;
                        }
                } else {
                        BUG_ON(ctx->skb == NULL && !skip_page_frags);

                        /* non SOP buffer must be type 1 in most cases */
                        BUG_ON(rbi->buf_type != VMXNET3_RX_BUF_PAGE);
                        BUG_ON(rxd->btype != VMXNET3_RXD_BTYPE_BODY);

[toc] | [prev] | [next] | [standalone]

#183070

FromMini Trader <miniflowtrader@gmail.com>
Date2017-07-04 01:00 +0200
Message-ID<tZitY-7Ys-1@gated-at.bofh.it>
In reply to#183069

[Multipart message — attachments visible in raw view] — view raw

I am on stretch  Debian 4.9.30-2+deb9u2.  Is there a link to submit this
bug too?

On Ubuntu's 4.4.0-83-generic this is not reproducible.


On Mon, Jul 3, 2017 at 6:45 PM, deloptes <deloptes@gmail.com> wrote:

> Mini Trader wrote:
>
> > More information.  I found a post here:
> >
> > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650635
> >
> > They mention LRO so I disabled it.  I cannot reproduce if LRO is
> disabled.
> >
> > On Mon, Jul 3, 2017 at 5:59 PM, Mini Trader <miniflowtrader@gmail.com>
> > wrote:
> >
> >> Looks to be the same.
> >>
> >> On Mon, Jul 3, 2017 at 5:48 PM, deloptes <deloptes@gmail.com> wrote:
> >>
> >>> Mini Trader wrote:
> >>>
> >>> > task_numa_fault+0x6ed/0xd20
> >>>
> >>> what happens if you boot the vm with numa=off
> >>>
> >>>
> >>>
> >>>
> >>
>
> the change mentioned in the article is in the kernel - at least 4.11.2 - I
> don't know about your version. The article is about 4.4.
>
> perhaps solved by chance - you have to report back to kernel maintainer I
> guess
>
> 4.11.2 and 4.10.14
>
> line nr 1395 to 1415
>                         if (VMXNET3_VERSION_GE_2(adapter) &&
>                             rcd->type == VMXNET3_CDTYPE_RXCOMP_LRO) {
>                                 struct Vmxnet3_RxCompDescExt *rcdlro;
>                                 rcdlro = (struct Vmxnet3_RxCompDescExt
> *)rcd;
>
>                                 segCnt = rcdlro->segCnt;
>                                 WARN_ON_ONCE(segCnt == 0);
>                                 mss = rcdlro->mss;
>                                 if (unlikely(segCnt <= 1))
>                                         segCnt = 0;
>                         } else {
>                                 segCnt = 0;
>                         }
>                 } else {
>                         BUG_ON(ctx->skb == NULL && !skip_page_frags);
>
>                         /* non SOP buffer must be type 1 in most cases */
>                         BUG_ON(rbi->buf_type != VMXNET3_RX_BUF_PAGE);
>                         BUG_ON(rxd->btype != VMXNET3_RXD_BTYPE_BODY);
>
>
>
>

[toc] | [prev] | [next] | [standalone]

#183083

Fromdeloptes <deloptes@gmail.com>
Date2017-07-04 08:30 +0200
Message-ID<tZpvs-4v6-7@gated-at.bofh.it>
In reply to#183070
Mini Trader wrote:

> I am on stretch  Debian 4.9.30-2+deb9u2.  Is there a link to submit this
> bug too?
> 
> On Ubuntu's 4.4.0-83-generic this is not reproducible.

usually reportbug is used to do this, however  IMO you are hitting some
other bug, but this is just a guess

regards

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web