From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sander Eikelenboom Subject: Re: Xen-unstable Linux 3.14-rc3 and 3.13 Network troubles Date: Wed, 19 Feb 2014 12:33:59 +0100 Message-ID: <14710449418.20140219123359@eikelenboom.it> References: <1772884781.20140218222513@eikelenboom.it> <20140219112858.GN18398@zion.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20140219112858.GN18398@zion.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Wei Liu Cc: ANNIE LI , Paul Durrant , Zoltan Kiss , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org Wednesday, February 19, 2014, 12:28:58 PM, you wrote: > On Tue, Feb 18, 2014 at 10:25:13PM +0100, Sander Eikelenboom wrote: >> Hi All, >> >> I'm currently having some network troubles with Xen and recent linux kernels. >> >> - When running with a 3.14-rc3 kernel in dom0 and a 3.13 kernel in domU >> I get what seems to be described in this thread: http://www.spinics.net/lists/netdev/msg242953.html >> > I *think* that issue should've been fixed -- not with that patch but with > a different one. *sigh* >> In the guest: >> [57539.859584] net eth0: rx->offset: 0, size: 4294967295 >> [57539.859599] net eth0: rx->offset: 0, size: 4294967295 >> [57539.859605] net eth0: rx->offset: 0, size: 4294967295 >> [57539.859610] net eth0: Need more slots >> [58157.675939] net eth0: Need more slots >> [58725.344712] net eth0: Need more slots >> [61815.849180] net eth0: rx->offset: 0, size: 4294967295 >> [61815.849205] net eth0: rx->offset: 0, size: 4294967295 >> [61815.849216] net eth0: rx->offset: 0, size: 4294967295 >> [61815.849225] net eth0: Need more slots >> >> Xen reports: >> (XEN) [2014-02-18 03:22:47] grant_table.c:1857:d0 Bad grant reference 19791875 >> (XEN) [2014-02-18 03:42:33] grant_table.c:1857:d0 Bad grant reference 268435460 >> (XEN) [2014-02-18 04:15:23] grant_table.c:289:d0 Increased maptrack size to 14 frames >> (XEN) [2014-02-18 04:15:27] grant_table.c:289:d0 Increased maptrack size to 15 frames >> (XEN) [2014-02-18 04:15:48] grant_table.c:289:d0 Increased maptrack size to 16 frames >> (XEN) [2014-02-18 04:15:50] grant_table.c:289:d0 Increased maptrack size to 17 frames >> (XEN) [2014-02-18 04:15:55] grant_table.c:289:d0 Increased maptrack size to 18 frames >> (XEN) [2014-02-18 04:15:55] grant_table.c:289:d0 Increased maptrack size to 19 frames >> (XEN) [2014-02-18 04:15:56] grant_table.c:289:d0 Increased maptrack size to 20 frames >> (XEN) [2014-02-18 04:15:56] grant_table.c:289:d0 Increased maptrack size to 21 frames >> (XEN) [2014-02-18 04:15:59] grant_table.c:289:d0 Increased maptrack size to 22 frames >> (XEN) [2014-02-18 04:15:59] grant_table.c:289:d0 Increased maptrack size to 23 frames >> (XEN) [2014-02-18 04:16:00] grant_table.c:289:d0 Increased maptrack size to 24 frames >> (XEN) [2014-02-18 04:16:05] grant_table.c:289:d0 Increased maptrack size to 25 frames >> (XEN) [2014-02-18 04:16:05] grant_table.c:289:d0 Increased maptrack size to 26 frames >> (XEN) [2014-02-18 04:16:06] grant_table.c:289:d0 Increased maptrack size to 27 frames >> (XEN) [2014-02-18 04:16:12] grant_table.c:289:d0 Increased maptrack size to 28 frames >> (XEN) [2014-02-18 04:16:18] grant_table.c:289:d0 Increased maptrack size to 29 frames >> (XEN) [2014-02-18 04:17:00] grant_table.c:1857:d0 Bad grant reference 268435460 >> (XEN) [2014-02-18 04:17:00] grant_table.c:1857:d0 Bad grant reference 268435460 >> (XEN) [2014-02-18 04:34:03] grant_table.c:1857:d0 Bad grant reference 4325377 >> > Judging from the log above I presume it happens after DomU has been > running for quite a while? Could you elaborate on the exact steps to > reproduce? > Does it happen when you use 3.13 as backend? yes i happens when it runs for a while (could be due to the fragment packet problems that seems to be a nasty problem that reoccurs from time to time. But i just noticed in the specific VM that caused this i had TSO switched off (to see if it would effect the case below which it didn't) so it could be due to that. I will see if i can figure that out and report back. >> >> >> Another issue with networking is when running both dom0 and domU's with a 3.14-rc3 kernel: >> - i can ping the guests from dom0 >> - i can ping dom0 from the guests >> - But i can't ssh or access things by http >> - I don't see any relevant error messages ... >> - This is with the same system and kernel config as with the 3.14 and 3.13 combination above >> (that previously worked fine) > I think I am able to reproduce this. I'm looking into it now. Luckily > there isn't that many changesets between 3.13 and 3.14. >>From what i can remember it's somehwere from early in the merge window, but i didn't get to report it due quite some other bugs in different subsystems this mergewindow. > Wei. >> >> -- >> >> Sander