From: Francois Romieu <romieu@fr.zoreil.com>
To: Thanasis <thanasis@asyr.hopto.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Hayes Wang <hayeswang@realtek.com>
Subject: Re: RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
Date: Fri, 21 Sep 2012 17:28:28 +0200 [thread overview]
Message-ID: <20120921152828.GA24364@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <505BF437.4090506@asyr.hopto.org>
Thanasis <thanasis@asyr.hopto.org> :
> on 09/21/2012 02:20 AM Francois Romieu wrote the following:
[...]
> > Thanasis, can you narrow down a bit the failing revision ?
>
> Sure, let me know how to do it please.
A rough kernel estimate had been enough. Nevermind.
You will find a hopefully not too quick 2.6.38 backport at :
git://violet.fr.zoreil.com/romieu/r8169
It does not reach the current in-kernel r8169.c state - call me lazy - but
stops somewhere between 3.2 and 3.3. While only 76 commits long, it should
be enough to spot a r8169 regression.
Assuming you run a 2.6.38-something kernel whose build tree lays at the
usual place, the included makefile will build a out-of-kernel r8169 driver.
You can use it as:
git clone git://violet.fr.zoreil.com/romieu/r8169
cd r8169
git rev-list --all | tac | while read c; do
git reset --hard $c
make
rmmod r8169
sync
insmod ./r8169.ko
<insert your ip addr add ... / link up and test sequence here>
done > /tmp/lets-go-shopping.log
^C when things go wrong.
You could do a git bisect but there may be several stupidly broken
commits and I have not checked that the top of the tree works.
Of course you are suggested to check that the code won't try to abuse
your system.
--
Ueimor
next prev parent reply other threads:[~2012-09-21 15:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 17:28 RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02) Thanasis
2012-09-20 17:47 ` Bjorn Helgaas
2012-09-20 18:10 ` Thanasis
2012-09-20 19:02 ` Bjorn Helgaas
2012-09-20 23:20 ` Francois Romieu
2012-09-21 4:59 ` Thanasis
2012-09-21 15:28 ` Francois Romieu [this message]
2012-09-21 16:30 ` Thanasis
2012-09-21 17:31 ` Thanasis
2012-09-21 16:41 ` Thanasis
2012-09-21 17:54 ` Francois Romieu
2012-09-21 19:20 ` Thanasis
2012-09-21 20:29 ` Francois Romieu
2012-09-21 21:17 ` Thanasis
2012-09-21 22:53 ` Francois Romieu
2012-09-22 6:20 ` Thanasis
2012-09-22 8:28 ` Thanasis
2012-09-22 8:44 ` Thanasis
2012-09-21 19:56 ` Thanasis
2012-09-24 23:12 ` Francois Romieu
2012-09-25 8:55 ` Thanasis
2012-09-25 9:54 ` Francois Romieu
2012-09-25 13:05 ` Thanasis
2012-09-25 20:53 ` Francois Romieu
2012-09-26 5:41 ` Thanasis
2012-09-30 8:03 ` Thanasis
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=20120921152828.GA24364@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=bhelgaas@google.com \
--cc=hayeswang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thanasis@asyr.hopto.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