From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@vger.kernel.org
Subject: Re: r8169: hard freezes on TX
Date: Wed, 23 May 2007 08:21:02 +0200 [thread overview]
Message-ID: <200705230821.13479.eike-kernel@sf-tec.de> (raw)
In-Reply-To: <20070522202934.GA21991@electric-eye.fr.zoreil.com>
[-- Attachment #1: Type: text/plain, Size: 2797 bytes --]
You wrote:
> Rolf Eike Beer <eike-kernel@sf-tec.de> :
> [...]
>
> > I often see freezes when I do much outgoing transfer. I have never seen
> > this happening on incoming transfers. When this happens the system locks
> > up hard, I don't see anything in the log. Since this is my laptop I have
> > trouble debugging it: there is no serial console and debugging this via
> > netconsole doesn't look like a good idea.
>
> Keyboard leds are dead afterwards I guess, right ?
I'm not absolutely sure but I can do a test later today.
> If you are experiencing bugs related to networking, I suggest to stay
> away from netconsole. It is not funny to analyze several bugs at the same
> time.
I did not expect anything coming through there, last time I tested even pings
were unanswered. Because of this I didn't even try netconsole.
> > When I say "much outgoing transfer" this means "several megabytes". If I
> > copy out 30 MB I almost everytime get this. I usually copy that much only
> > at home when I feed my gentoo server. That host only has a 10 MBit
> > connection. Nevertheless I've also seen that on different hosts using
> > different files on different protocols (ftp, scp, smb).
> >
> :o/
>
> So it can be reproduced with a simple ftp put of several megabytes of
> data completely cached in memory (no disk access) ?
I can put it into RAM before next test to be absolutely sure.
> > This is the output of lspci for my NIC:
> >
> > 05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E PCI
> > Express Fast Ethernet controller (rev 01)
>
> I have not seen a lot of reports for this one. Either it is perfect or
> it is barely used.
>
> [...]
>
> > Hm, is there a reason why we don't use MSI here?
>
> A request for testers was posted (netdev + lk) on 16/03/2007 which
> contained MSI code for the 8168. I did not enable it for the 8101 because
> it had only received (positive) reports from 8168 users.
>
> Afair, the RFT got no feedback.
I'll dig for it.
> > Ah, one thing is missing: I've not tested it with current kernel, latest
> > I tested was 2.6.21-rc7. But I've seen this on many previous version,
> > although I thought it became better some versions ago. I wont bet on it,
> > it might just have been luck.
>
> You can/should try:
> http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.22-rc2 (patch-kit)
> or:
> http://www.fr.zoreil.com/people/francois/misc/20070522-2.6.22-rc2-r8169.pat
>ch
>
> If you are fluent with git and you do not mind rebasing, you can try
> git://electric-eye.fr.zoreil.com/home/romieu/linux/linux-2.6-out r8169
>
> (don't do the initial clone from here, thanks)
>
> As an option, akpm includes the git branch for you in -mm.
I'll take a look, thanks.
Eike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-05-23 6:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-20 13:20 r8169: hard freezes on TX Rolf Eike Beer
2007-05-22 20:29 ` Francois Romieu
2007-05-23 6:21 ` Rolf Eike Beer [this message]
2007-05-23 6:48 ` Rolf Eike Beer
2007-06-04 13:06 ` Rolf Eike Beer
2007-06-04 21:46 ` Francois Romieu
2007-06-05 7:33 ` Rolf Eike Beer
2007-06-07 14:13 ` Rolf Eike Beer
2007-06-07 22:23 ` Francois Romieu
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=200705230821.13479.eike-kernel@sf-tec.de \
--to=eike-kernel@sf-tec.de \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.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).