netdev - Re: Realtek 8111C transmit timed out

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <25625.84.245.32.19.1218051465.squirrel@secure.greenhost.nl>
Date:	Wed, 6 Aug 2008 21:37:45 +0200 (CEST)
From:	"Indan Zupancic" <indan@....nu>
To:	"Francois Romieu" <romieu@...zoreil.com>
Cc:	netdev@...r.kernel.org
Subject: Re: Realtek 8111C transmit timed out

Hello,

On Wed, August 6, 2008 20:12, Francois Romieu wrote:
> Indan Zupancic <indan@....nu> :
> [...]
>> I'm running a git version just before 2.6.27-rc2 and while the card
>> worked fine in 2.6.26, after a resume from suspend to ram I now get:
>
> You cab try to revert the four (4) r8169.c related patches that went
> in between 2.6.26 and 2.6.27-rc1. I doubt it will make a difference
> though.

"git log drivers/net/r8169.c" shows only two commits since May 11:

r8169: avoid thrashing PCI conf space above RTL_GIGA_MAC_VER_06

r8169: multicast register update

Then at May 11 comes:

r8169: remove non-napi code

But I think that was in 2.6.26 already.

Reverting the first two didn't help, so I guess it's messed up
somewhere else.

Are two patches missing or didn't they touch r8169.c?

I tried manually reverting patch

0004-r8169-new-phy-init-parameters-for-the-8168b.patch

(misread your mail), and it didn't seem applied yet.

> Is a git bisect an option ?

Yes, but it takes quite a lot of time and I'm busy at the moment,
so I'll wait till rc2 to see if it's fixed then. If it isn't I'll
start digging.

Greetings,

Indan


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html