• 6.9.0-beta22 again unexpected GSO type

    NewDisplayName

    By NewDisplayName

      • Minor

    Hi,

    ive posted this issue around 6.5 unraid and it got "fixed"? by 6.8.3, now its back... it seems to happen when i start the Windows 10 VM. I already tried to edit the template and click update, but didnt changed anything.

     

    While its spamming the log with



    Jul 7 20:16:18 Unraid-Server kernel: tun: unexpected GSO type: 0x0, gso_size 1384, hdr_len 1450
    Jul 7 20:16:18 Unraid-Server kernel: tun: c0 7a f0 21 a5 fd 21 2a 72 d6 16 97 13 5f df 47 .z.!..!*r...._.G
    Jul 7 20:16:18 Unraid-Server kernel: tun: 24 44 8b 16 37 ef 25 74 da 6f f6 3b 4a ba 2e 19 $D..7.%t.o.;J...
    Jul 7 20:16:18 Unraid-Server kernel: tun: 8f e8 8f 9c 27 25 c4 e0 ad 39 61 70 15 c3 34 7a ....'%...9ap..4z
    Jul 7 20:16:18 Unraid-Server kernel: tun: 8d c5 6b 9b ac cf 45 bc e2 28 2e 75 56 58 00 00 ..k...E..(.uVX..

    the server is kinda unresponsive.

     

    Is this supposed to work or what i am doing wrong?


    Or is this bug still unresolved?

     

    Go to reports Prereleases

    User Feedback

    Recommended Comments



    NewDisplayName

    I can confirm 5.0 and OVM makes it useable and you only get some time a day these GSO errors, but, just to be safe, i reverted back today, currentlyi can live with low speed.

     

    But this should be fixed.

    Link to comment
    Marshalleq

    Just chipping in after installing latest beta I'm also getting my logs fill up (like they're actually 100% filled up the tmps drive) as per the below:

     

    Aug  6 16:11:44 OBI-WAN kernel: tun: unexpected GSO type: 0x0, gso_size 1402, hdr_len 1468

    Aug  6 16:11:44 OBI-WAN kernel: tun: unexpected GSO type: 0x0, gso_size 1402, hdr_len 1468

    Aug  6 16:11:44 OBI-WAN kernel: tun: 24 49 92 24 96 b5 95 ad aa aa aa aa b3 b3 49 92  $I.$..........I.

    Aug  6 16:11:44 OBI-WAN kernel: tun: 8f 5c 2c 5d 4e 99 30 e3 1d 15 ee 66 4a fc 79 09  .\,]N.0....fJ.y.

    Aug  6 16:11:44 OBI-WAN kernel: tun: e6 17 43 84 7a 39 48 1c e9 f4 c4 35 77 26 6e fa  ..C.z9H....5w&n.

    Aug  6 16:11:44 OBI-WAN kernel: tun: fe 53 61 0d 59 e5 6d 03 39 2b 47 51 0e f0 42 ab  .Sa.Y.m.9+GQ..B.

    Aug  6 16:11:44 OBI-WAN kernel: tun: 24 49 92 24 96 b5 95 ad aa aa aa aa b3 b3 49 92  $I.$..........I.

    Aug  6 16:11:44 OBI-WAN kernel: tun: 24 49 92 24 96 b5 95 ad aa aa aa aa a9 a9 49 92  $I.$..........I.

    Aug  6 16:11:44 OBI-WAN kernel: tun: 3a 1c 4f f1 93 59 f7 ec 24 5c 8a 63 f9 8d 34 a9  :.O..Y..$\.c..4.

    Aug  6 16:11:44 OBI-WAN kernel: tun: 24 49 92 24 00 00 00 00 aa aa aa aa a9 a9 49 92  $I.$..........I.

    Aug  6 16:11:44 OBI-WAN kernel: tun: unexpected GSO type: 0x0, gso_size 1402, hdr_len 1468

    Aug  6 16:11:44 OBI-WAN kernel: tun: 74 51 07 64 ba 4e 12 d9 33 53 1b ac c4 a3 af 38  tQ.d.N..3S.....8

    Aug  6 16:11:44 OBI-WAN kernel: tun: d1 a7 a6 a5 52 de 50 9b 9d 42 7d fc 2a 07 c8 c1  ....R.P..B}.*...

    Aug  6 16:11:44 OBI-WAN kernel: tun: unexpected GSO type: 0x0, gso_size 1402, hdr_len 1468

    Aug  6 16:11:44 OBI-WAN kernel: tun: 5a 65 d4 d1 f7 3a f0 9c 09 44 7e d6 2e b9 b4 df  Ze...:...D~.....

    Aug  6 16:11:44 OBI-WAN kernel: tun: 7a b8 67 bb 3c db 50 6a c0 24 12 5f 6e 8c 56 19  z.g.<.Pj.$._n.V.

    Aug  6 16:11:44 OBI-WAN kernel: tun: 94 63 43 2d 3d fb 29 af 83 32 95 21 f0 6f 87 16  .cC-=.)..2.!.o..

     

    Commonalities to the above, I also have 10G Intel Nic, multi internal networks, some windows VM's.  I'll go through the above steps (haven't changed to Q35-5.0 yet - just wanted to register a 'me too'.

     

    Edit - As it turns out, I did have Q35-5.0 already due to having to recreate the template - (something that I constantly have to do with unraid for some reason) and that defaulted to 5.0 and virtio-net.

     

    In this configuration, my logs are flooded with these messages.  It starts when I start a Windows 10 machine and doesn't stop after I've stopped the VM - have to restart the whole server.  Perhaps I can restart the virtual machine manager - haven't gotten that far yet.

     

    Edit 2: One more reboot and they're down to 500 or so an hour.  So that's survivable compared to before at about 1-2 per second.  Will continue to try and pin it down over the next few days.

     

    Logs now attached.

     

     

    obi-wan-diagnostics-20200807-1106.zip

    Edited by Marshalleq
    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×

  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.

    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.