From: Jens Stroebel <drifter@bcsoft.de>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev list <netdev@vger.kernel.org>
Subject: Re: 2.6.21.5+1small patch: not blocking
Date: Fri, 29 Jun 2007 17:44:56 +0200 [thread overview]
Message-ID: <468528F8.8050806@bcsoft.de> (raw)
In-Reply-To: <4684F898.80204@bcsoft.de>
Jens Stroebel wrote:
> Francois Romieu wrote:
>> [...]
>> It may help and/or accelerate things if you can narrow the fix(es) in
>> the current r8169 serie.
> Instead, I built 2.6.21.5+[a patch I snatched from a mail communication
> you had on 2007-06-20
> (Msg-ID: <20070620211530.GA10042@electric-eye.fr.zoreil.com> )].
> I will attach it with this mail, as it is really small and you don't
> have to dig around to know what I'm talking about.
>
> As I am no kernel-developer, I am not sure there are no undesired side
> effects by applying this patch to this kernel; if you think there are
> (could/should be), it would be nice if you could state that, so I'd
> refrain from testing with this combination.
Following up to myself:
It seems like the patch is able to change things in a way which makes
the machine lock up hard. Pity that, looked so promising at first...
greets,
jens
--
drifter@bcsoft.de
23.....56.......drifting
By caffeine alone I set my mind in motion, By the beans of Java
do thoughts acquire speed, hands acquire shaking, the shaking
becomes a warning, By caffeine alone do I set my mind in motion
next prev parent reply other threads:[~2007-06-29 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 18:08 r8169: 2.6.22rc6+patches works, but 2.6.21.5 and 2.6.22rc6 without patches->network transfer blocking Jens Stroebel
2007-06-28 21:30 ` Francois Romieu
2007-06-29 12:18 ` 2.6.21.5+1small patch: not blocking [was: Re: r8169: 2.6.22rc6+patches works, but 2.6.21.5 and 2.6.22rc6 without patches->network transfer blocking] Jens Stroebel
2007-06-29 15:44 ` Jens Stroebel [this message]
2007-06-29 19:22 ` 2.6.21.5+1small patch: not blocking 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=468528F8.8050806@bcsoft.de \
--to=drifter@bcsoft.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).