linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Michlmayr <tbm@cyrius.com>
To: Stephen Hemminger <shemminger@osdl.org>, netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, 341801@bugs.debian.org,
	asd@suespammers.org, kevin@sysexperts.com
Subject: skge error; hangs w/ hardware memory hole
Date: Mon, 3 Jul 2006 22:52:38 +0200	[thread overview]
Message-ID: <20060703205238.GA10851@deprecation.cyrius.com> (raw)

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.

Another users confirms this bug, saying:

| I'm running kernel 2.6.15-1-amd64-generic version 2.6.15-6, and see
| the very same thing.
| So I have to turn off the memory remapping feature that allows the
| system to see all 4 gig of memory, and thus lose the use of about 200
| megabytes of memory.
| Hardware: ASUS A8V Deluxe, 4G RAM, Athlon 64 3200+ CPU.

This problem has probably been there forever and also happens with the
sk98lin driver:

| With sk98lin under both 2.6.12 and 2.6.17 I get the following message,
| repeated countless times, and finally a hang: [this is copied from
| screen on to a sheet a paper and re-typed, beware typos]:

| eth0: Adapter failed
| eth0: -- ERROR --
| class: Hardware failure
| Nr: 0x264
| Msg: unexpected IRQ Status error

The bug is still present in 2.6.17 -mm6:

| -mm6 does not work with skge and the hardware memory hole. It gave
| these messages:

| skge eth0: enabling interface
| skge 0000:00:0a.0: PCI error cmd=0x117 status=0x22b0
| skge unable to clear error (so ignoring them)
| skge eth0: Link is up at 1000 Mbps, full duplex, flow control tx and rx

| DHCP never managed to get an IP address.

Any idea what to do about this?
-- 
Martin Michlmayr
http://www.cyrius.com/

             reply	other threads:[~2006-07-03 20:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-03 20:52 Martin Michlmayr [this message]
2006-07-07 21:18 ` skge error; hangs w/ hardware memory hole Stephen Hemminger
2006-07-07 21:28   ` Andi Kleen
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
2006-07-19 14:05 Andy Chittenden
     [not found] <6uDGH-7Nj-57@gated-at.bofh.it>
     [not found] ` <200609200901.39460.ak@suse.de>
     [not found]   ` <45118F00.2030303@highlandsun.com>
     [not found]     ` <200609202121.14156.ak@suse.de>
     [not found]       ` <4511A101.2070707@highlandsun.com>
     [not found]         ` <5624739.1158784754480.SLOX.WebMail.wwwrun@imap-dhs.suse.de>
2006-09-24 19:50           ` Howard Chu

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=20060703205238.GA10851@deprecation.cyrius.com \
    --to=tbm@cyrius.com \
    --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 \
    /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).