All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@sw.ru>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: tg3 broken after "PCI: Fix bus resource assignment on 32 bits with 64b resources"
Date: Wed, 6 Feb 2008 13:05:10 +0300	[thread overview]
Message-ID: <20080206100510.GA29127@localhost.sw.ru> (raw)
In-Reply-To: <1202244592.7079.68.camel@pasglop>

On Wed, Feb 06, 2008 at 07:49:52AM +1100, Benjamin Herrenschmidt wrote:
> 
> > so x86_64 will work well?
> > 
> > the problem is that BIOS does not assign one resource for you tg3. and
> > kernel pcibios_assign_to_unassign (?) try
> > to assign resource to your card.
> 
> But the kernel shouldn't try to assign a resource in the 64 bits space
> to a card behind a bridge... at least not a non-prefetchable resource
> since those can't be forwarded (P2P bridges only define a 32 bits window
> for non-prefetchable resources).
> 
> So it does look to me like the kernel may be doing something wrong. I
> haven't had a chance to look at the logs in details yet (just woke up).
> 
> > revert the patch happen to work, you only have 2g less RAM (?), so
> > 0x8000000 still can be used.
> > 
> > sometime you could get hang if your MB have two HT chains. ...because
> > BIOS already allocate two io range for the two chain.
> > and kernel may assign resource from the range1 belong to HT1 to device
> > under HT0.
> > solution: need pci root bios to provide _CRS to replace...
> > and i have one patch but it only take care of 64 bit kernel for this case.
> > 
> > 
> > easy solution for you: try to get one updated BIOS.

BTW, "[PATCH] x86_32: fix regression caused by trim ram according to mtrr on system with 4G more RAM"
http://marc.info/?l=linux-kernel&m=120229095121673&w=2
fixes this box too and I have back all 4G of RAM as a bonus. :-)


  reply	other threads:[~2008-02-06 10:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-04 15:12 tg3 broken after "PCI: Fix bus resource assignment on 32 bits with 64b resources" Alexey Dobriyan
2008-02-04 21:54 ` Benjamin Herrenschmidt
2008-02-05  9:17   ` Alexey Dobriyan
2008-02-05 10:07     ` Yinghai Lu
2008-02-05 20:49       ` Benjamin Herrenschmidt
2008-02-06 10:05         ` Alexey Dobriyan [this message]
2008-02-06 10:40           ` Yinghai Lu
2008-02-06 21:15           ` Benjamin Herrenschmidt
2008-02-07 10:07             ` Alexey Dobriyan
2008-02-06  1:05     ` Benjamin Herrenschmidt
2008-02-04 21:57 ` Benjamin Herrenschmidt
2008-02-04 21:59 ` Benjamin Herrenschmidt
2008-02-13 22:52 ` Rafael J. Wysocki
2008-02-13 23:01   ` Benjamin Herrenschmidt
2008-02-13 23:03   ` Alexey Dobriyan
2008-02-13 23:06     ` Rafael J. Wysocki

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=20080206100510.GA29127@localhost.sw.ru \
    --to=adobriyan@sw.ru \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yhlu.kernel@gmail.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.