From: Nick Warne <nick@linicks.net>
To: linux-kernel@vger.kernel.org
Subject: Re: RTL8139, the final patch ?
Date: Sat, 20 Aug 2005 23:17:46 +0100 [thread overview]
Message-ID: <200508202317.46937.nick@linicks.net> (raw)
In-Reply-To: <200508202153.17837.nick@linicks.net>
On Saturday 20 August 2005 21:53, you wrote:
> I have a problem with it:
> It's about patching, reverting, patching, reverting,...
> I got lost. That's why I asked for a... "straighter" one :-)
>> But I looked at what he said and found the real problem on my system (after
>> all that):
>> http://www.ussg.iu.edu/hypermail/linux/kernel/0403.1/1537.html
> It's about a configuration option in the kernel?
> The patch is about adding the option, if i'm right.
No, what happened was on 2.6.2 all was well. When 2.6.3 came out I got these
timeout errors on the NIC's - but using the 2.6.2 8139too.c file in 2.6.3
worked. Mr Hirofumi then took up the challenge and sent me patches. Slowly
he resolved the issue, but the conclusion was it wasn't the code causing it.
It was an option in my BIOS PCI level/edge settings as I posted. People on
laptops get this error, like you, but there is no BIOS option as such... :-/
Nick
--
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."
next prev parent reply other threads:[~2005-08-20 22:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-20 20:53 RTL8139, the final patch ? Nick Warne
2005-08-20 22:04 ` Rakotomandimby Mihamina
2005-08-20 22:17 ` Nick Warne [this message]
2005-08-21 0:24 ` OGAWA Hirofumi
2005-09-14 17:16 ` Rakotomandimby Mihamina
2005-09-15 15:21 ` OGAWA Hirofumi
-- strict thread matches above, loose matches on Subject: below --
2005-08-20 18:38 Rakotomandimby Mihamina
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=200508202317.46937.nick@linicks.net \
--to=nick@linicks.net \
--cc=linux-kernel@vger.kernel.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