xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad@kernel.org>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: xen-devel@lists.xensource.com, konrad <konrad.wilk@oracle.com>
Subject: Re: Kernel 3.7.0-pre-rc1 kernel BUG at drivers/net/xen-netback/netback.c:405 RIP: e030:[<ffffffff814714f9>] [<ffffffff814714f9>] netbk_gop_frag_copy+0x379/0x380
Date: Sun, 7 Oct 2012 19:34:45 -0400	[thread overview]
Message-ID: <20121007233444.GA26929@localhost.localdomain> (raw)
In-Reply-To: <729626082.20121006002054@eikelenboom.it>

On Sat, Oct 06, 2012 at 12:20:54AM +0200, Sander Eikelenboom wrote:
> 
> Friday, October 5, 2012, 9:26:31 PM, you wrote:
> 
> > Sorry for top posting - on mobile.
> 
> > I saw it too yesterday but only on a specific hardware - AMD FX8. What type of CPU do you have?  Does xsave=off on Xen line help?
> 
> Nope the xsave=off doesn't help
> 
> > Sander Eikelenboom <linux@eikelenboom.it> wrote:
> 
> >>Hi Konrad,
> >>
> >>Just tested kernel 3.7.0-pre-rc1 but ran into a oops in netback on boot after starting some guests:
> >>
> >>[  402.723915] ------------[ cut here ]------------
> >>[  402.734629] kernel BUG at drivers/net/xen-netback/netback.c:405!

Looking at the code, this is what we get:

        /* Data must not cross a page boundary. */
        BUG_ON(size + offset > PAGE_SIZE);

Looking at the commits, the one recently added was:
commit c571898ffc24a1768e1b2dabeac0fc7dd4c14601
Author: Andres Lagar-Cavilla <andres@lagarcavilla.org>
Date:   Fri Sep 14 14:26:59 2012 +0000

    xen/gndev: Xen backend support for paged out grant targets V4.
    

But after reverting it and trying the kernel I still got the crash.

So .. the weirdness is that this seems to be only happening on
certain AMD machines - for example on my AMD A8 box I did not see this.

I fear that the next step is to do a bit off git bisection to
get an idea of which merge it might be. I am going to be AFK
on Monday so I won't get to this until Tuesday/Wednesay :-(

.. Thought to help speed this process, this looks like a
candidate:

commit 229993001282e128a49a59ec43d255614775703a
Merge: 7687b80 fd0f586
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Oct 1 11:13:33 2012 -0700

    Merge branch 'x86-mm-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull x86/mm changes from Ingo Molnar:
     "The biggest change is new TLB partial flushing code for AMD CPUs.
      (The v3.6 kernel had the Intel CPU side code, see commits
      e0ba94f14f74..effee4b9b3b.)

  reply	other threads:[~2012-10-07 23:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-05 19:26 Kernel 3.7.0-pre-rc1 kernel BUG at drivers/net/xen-netback/netback.c:405 RIP: e030:[<ffffffff814714f9>] [<ffffffff814714f9>] netbk_gop_frag_copy+0x379/0x380 konrad
2012-10-05 19:31 ` Sander Eikelenboom
2012-10-05 22:20 ` Sander Eikelenboom
2012-10-07 23:34   ` Konrad Rzeszutek Wilk [this message]
2012-10-08  8:54     ` Ian Campbell
2012-10-08  8:58       ` Sander Eikelenboom
2012-10-08 12:43       ` Sander Eikelenboom
2012-10-09  2:24       ` Sander Eikelenboom
2012-10-09  9:23         ` Ian Campbell
2012-10-09 11:07           ` Sander Eikelenboom
2012-10-09 13:16             ` Ian Campbell
  -- strict thread matches above, loose matches on Subject: below --
2012-10-05 17:22 Sander Eikelenboom

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=20121007233444.GA26929@localhost.localdomain \
    --to=konrad@kernel.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux@eikelenboom.it \
    --cc=xen-devel@lists.xensource.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).