From: Shannon Wynter <kernel.org.alias@fremnet.net>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] skge: 32bit DMA for ASUS A8N-SLI Premium
Date: Sat, 27 Nov 2010 05:05:19 +1000 [thread overview]
Message-ID: <4CF004EF.90107@fremnet.net> (raw)
In-Reply-To: <20101126105233.091f818d@nehalam>
Stephen Hemminger wrote:
> On Fri, 26 Nov 2010 23:51:46 +1000
> Shannon Wynter <kernel.org.alias@fremnet.net> wrote:
>
>
>> Add ASUS A8N-SLI Premium to the list of boards that require the quirk to
>> limit DMA to 32bit in the skge.c module.
>>
>> Signed-off-by: Shannon Wynter <kernel.org.alias@fremnet.net>
>> ---
>> --- a/drivers/net/skge.c 2010-11-26 08:35:21.000000000 +1000
>> +++ b/drivers/net/skge.c 2010-11-26 08:58:52.000000000 +1000
>> @@ -4158,6 +4158,13 @@
>> DMI_MATCH(DMI_BOARD_NAME, "nForce"),
>> },
>> },
>> + {
>> + .ident = "ASUSTeK A8N-SLI Premium",
>> + .matches = {
>> + DMI_MATCH(DMI_BOARD_VENDOR, "ASUSTeK Computer INC."),
>> + DMI_MATCH(DMI_BOARD_NAME, "A8N-SLI Premium"),
>> + },
>> + },
>> {}
>> };
>>
>>
>>
>
> Ok. Maybe I have to buy one of these beasts to find the root
> cause of this.
>
>
It's quite an old board, I'd let you on mine and say go for your life
but it's actually kind of mission critical (in so much as a home server
can be).
Is there anything I can provide/do/run for you to give you a head start
in the right direction?
The problem showed up when I upgraded from 1gb to 4gb of memory (the
maximum the board can handle)
next prev parent reply other threads:[~2010-11-26 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-26 13:51 [PATCH] skge: 32bit DMA for ASUS A8N-SLI Premium Shannon Wynter
2010-11-26 18:52 ` Stephen Hemminger
2010-11-26 19:05 ` Shannon Wynter [this message]
2011-01-05 5:55 ` Shannon Wynter
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=4CF004EF.90107@fremnet.net \
--to=kernel.org.alias@fremnet.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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).