netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Martin Michlmayr <tbm@cyrius.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	341801@bugs.debian.org, asd@suespammers.org,
	kevin@sysexperts.com
Subject: Re: skge error; hangs w/ hardware memory hole
Date: Fri, 7 Jul 2006 23:28:51 +0200	[thread overview]
Message-ID: <200607072328.51282.ak@suse.de> (raw)
In-Reply-To: <20060707141843.73fc6188@dxpl.pdx.osdl.net>

On Friday 07 July 2006 23:18, Stephen Hemminger wrote:
> On Mon, 3 Jul 2006 22:52:38 +0200
> Martin Michlmayr <tbm@cyrius.com> wrote:
> 
> > We received the following bug report at http://bugs.debian.org/341801
> > 
> > | I have a Asus A8V with 4GB of RAM. When I turn on the hardware memory
> > | hole in the BIOS, the skge driver prints out this message:
> > |       skge hardware error detected (status 0xc00)
> > | and then does not work. Setting debug=16 doesn't really show anything.


Is that a board with VIA chipset?

VIA doesn't seem to support PCI accesses with addresses >4GB and they also
don't have a working GART IOMMU.

It will likely work with iommu=force

I've been pondering to force this, but was still waiting for more reports.

-Andi


  reply	other threads:[~2006-07-07 21:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-03 20:52 skge error; hangs w/ hardware memory hole Martin Michlmayr
2006-07-07 21:18 ` Stephen Hemminger
2006-07-07 21:28   ` Andi Kleen [this message]
2006-07-08  8:50     ` Martin Michlmayr
2006-07-09 15:24     ` Anthony DeRobertis
2006-07-12  2:46     ` Anthony DeRobertis
2006-07-12  2:54       ` Andreas Kleen
2006-07-12  4:09         ` Kevin Brown
2006-07-12 13:37           ` Andi Kleen
2006-07-23  6:32         ` Anthony DeRobertis
2006-07-24  2:12           ` Stephen Hemminger
2006-07-25  2:35           ` Andi Kleen

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=200607072328.51282.ak@suse.de \
    --to=ak@suse.de \
    --cc=341801@bugs.debian.org \
    --cc=asd@suespammers.org \
    --cc=kevin@sysexperts.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@osdl.org \
    --cc=tbm@cyrius.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).