All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerone Young <jyoung5@us.ibm.com>
To: Chris Wright <chrisw@osdl.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: dma_alloc_coherent issue with tg3 in x86_64 build
Date: Thu, 28 Jul 2005 15:59:15 -0500	[thread overview]
Message-ID: <1122584355.3564.7.camel@thinkpad> (raw)
In-Reply-To: <20050728195205.GY9157@shell0.pdx.osdl.net>

So when I remove "dom0_mem"  from the xen boot parmater & let dom0
allocate all memory I hit the same problem.

But also with todays HG build I can nolonger fully boot Dom0. Stops just
after printing "io scheduler cfq registered".

I'll talk a look at both to see what is going on.


On Thu, 2005-07-28 at 12:52 -0700, Chris Wright wrote:
> * Jerone Young (jyoung5@us.ibm.com) wrote:
> > What build are you using? I have a dual opteron with the same card &
> > driver (tg3) ... and works fine. I'll try today's build. But the build
> > I'm using is only a few days old and has no problems with x86-64. I'll
> > try todays and see what happens.
> 
> Both current hg, as well as a  pull from yesterday.  The box is remote,
> so a reboot is a very slow operation.  I just confirmed that reducing
> the amount of dom0 memory fixes the issue.  Machine has 2G, and I was
> giving all of it to dom0.
> 
> thanks,
> -chris
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
-- 
Jerone Young
IBM Linux Technology Center
jyoung5@us.ibm.com
512-838-1157 (T/L: 678-1157)

  reply	other threads:[~2005-07-28 20:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-28 19:36 dma_alloc_coherent issue with tg3 in x86_64 build Chris Wright
2005-07-28 19:44 ` Jerone Young
2005-07-28 19:52   ` Chris Wright
2005-07-28 20:59     ` Jerone Young [this message]
2005-07-29 10:03 ` Keir Fraser
  -- strict thread matches above, loose matches on Subject: below --
2005-07-28 20:59 Ian Pratt
2005-07-28 20:03 ` Scott Parish
2005-07-29  8:33   ` Gerd Knorr
2005-07-28 21:07 ` Chris Wright
2005-07-28 21:25 Ian Pratt
2005-07-29 10:07 ` 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=1122584355.3564.7.camel@thinkpad \
    --to=jyoung5@us.ibm.com \
    --cc=chrisw@osdl.org \
    --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.