All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Daniel Schmitt <daniel.schmitt@udo.edu>
Cc: xen-devel@lists.xensource.com
Subject: Re: crash e100 amd64 >=4GB RAM
Date: Thu, 27 May 2010 11:29:00 -0400	[thread overview]
Message-ID: <20100527152900.GB4342@phenom.dumpdata.com> (raw)
In-Reply-To: <178a7c8c6f1dbc6bc3dc1dd17f63a8fc.squirrel@webmail.tu-dortmund.de>

On Wed, May 26, 2010 at 10:28:05PM +0200, Daniel Schmitt wrote:
> Hello list,
> 
> I'm using gentoo Linux with xen 3.4.1 and linux kernel 2.6.30 fine till
> now where I need more RAM. I used 2GB and now I want to use 4GB.
> But upping eth0 (4-port e100 Quad Port Device by Compaq) crashed the kernel.
> I tried xen 4.0.0 with linux kernel 2.6.32, same error.
> Using swiotlb=force or swiotlb=128,force or iommu=off did not succeed even.
> The board has a tg3 gigabit NIC, too. Upping this device does not crash
> the kernel.
> It must have something to do with e100 driver.
> 
> Can anyone help?

Yes. Please follow these steps:
http://wiki.xensource.com/xenwiki/XenParavirtOpsHelp

> 
> Here is some crash information:
> ------------------------
> kernel BUG at lib/swiotlb-xen.c:454!
> [<ffffffff80481120>] e100_rx_alloc_skb+0x190/0x230
> ...
> RIP [<ffffffff803c56a6>] swiotlb_sync_single_for_device+0x96/0xe0
> Segmentation fault
> ------------------------
> 
> Thanks for your help,
> Daniel
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

      reply	other threads:[~2010-05-27 15:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-26 20:28 crash e100 amd64 >=4GB RAM Daniel Schmitt
2010-05-27 15:29 ` Konrad Rzeszutek Wilk [this message]

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=20100527152900.GB4342@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=daniel.schmitt@udo.edu \
    --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 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.