netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: 570268@bugs.debian.org, Dale Schroeder <dale@texasbb.com>,
	netdev@vger.kernel.org
Subject: Re: sky2 fails when memory exceeds 2GB on amd64 kernel
Date: Sun, 21 Feb 2010 02:06:06 +0000	[thread overview]
Message-ID: <1266717966.24602.14.camel@localhost> (raw)
In-Reply-To: <4B7F52E0.2010303@texasbb.com>

[-- Attachment #1: Type: text/plain, Size: 1882 bytes --]

Stephen,

Debian received this bug report on sky2:

Dale Schroeder wrote:
> No matter what brand, size, or speed of ddr2 RAM I try, I cannot 
> successfully boot when the installed memory is greater than 2GB.
> The system is an Acer Aspire M1100 with the most recent BIOS.  I have 
> tried with kernels 2.6.32-5 and 2.6.30-8squeeze1.
> 
> During the boot sequence, sky2 fails with a 0x2010 pci error; then 
> several programs slowly load until dmsg appears, at which time the 
> screen fills with hexadecimal errors similar to those in this debian bug 
> thread:
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=457967
> 
> Disabling the network interface in the BIOS allows bootup to finish, 
> although some programs fail to load due to the missing network connection.
> Decreasing the RAM to 2GB returns booting to normal.
> 
> I've seen numerous references to bugs with this network hardware and the 
> amd64 kernel, but none related to adding extra memory.  I am unaware as 
> to how I can capture the errors, since I cannot finish the boot process 
> when the errors happen.

Further information:

> I tested another network card, a Netgear GA311 which uses the r8169 driver.
> With this card, all 4GB of memory is recognized and the system 
> successfully boots.
> This would seem to rule out the BIOS and points to sky2 on the Marvell 
> m/b chip
> being my problem.
> 
> Obviously, the new card doesn't resolve the bug, but it does solve my 
> problem.

Does this sound like a plausible symptom of the bugs fixed by:

f6815077e75c5b7f55b56fc3788e328514d4e72a sky2: fix transmit DMA map leakage
3fbd9187d004149fb8a98c9cb51ef9f4a4f66aca sky2: hand receive DMA mapping failures

In any case, are the above suitable for 2.6.32-stable (once merged by
Linus)?

Ben.

-- 
Ben Hutchings
73.46% of all statistics are made up.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

           reply	other threads:[~2010-02-21  2:06 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <4B7F52E0.2010303@texasbb.com>]

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=1266717966.24602.14.camel@localhost \
    --to=ben@decadent.org.uk \
    --cc=570268@bugs.debian.org \
    --cc=dale@texasbb.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.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).