All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Chris Wright <chrisw@osdl.org>, xen-devel@lists.xensource.com
Subject: Re: dma_alloc_coherent issue with tg3 in x86_64 build
Date: Thu, 28 Jul 2005 14:07:32 -0700	[thread overview]
Message-ID: <20050728210732.GD19052@shell0.pdx.osdl.net> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D282822@liverpoolst.ad.cl.cam.ac.uk>

* Ian Pratt (m+Ian.Pratt@cl.cam.ac.uk) wrote:
> 
> > During boot of dom0, I get the following.  Box is remote, so 
> > I'm now waiting for proxy power button pusher ;-)  tg3 init 
> > fails doing dma_alloc_coherent (I assume this is from 
> > tg3_init_one -> tg3_test_dma -> pci_alloc_consistent -> 
> > dma_alloc_coherent).  Looks like an issue with the amount of 
> > memory in dom0.  Is this known?
> 
> Is this with a debug=y build of Xen? I can see how that might provoke
> the situation more than other builds.

Yes, it is.

> Do you know how large a contiguous chunk the tg3 needs? 

I believe that one was just 2 pages.

> I guess we could hold onto a few large chunks before making the dom0
> memory allocation.
> 
> Alternatively, if we get a failure, we should round up to the next power
> of two and then balloon out that much memory. Repeat until success...

I guess that'd be quick that early in boot.

thanks,
-chris

  parent reply	other threads:[~2005-07-28 21:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-28 20:59 dma_alloc_coherent issue with tg3 in x86_64 build Ian Pratt
2005-07-28 20:03 ` Scott Parish
2005-07-29  8:33   ` Gerd Knorr
2005-07-28 21:07 ` Chris Wright [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-07-28 21:25 Ian Pratt
2005-07-29 10:07 ` Keir Fraser
2005-07-28 19:36 Chris Wright
2005-07-28 19:44 ` Jerone Young
2005-07-28 19:52   ` Chris Wright
2005-07-28 20:59     ` Jerone Young
2005-07-29 10:03 ` Keir Fraser

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=20050728210732.GD19052@shell0.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --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.