[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100328221924.GG30031@ZenIV.linux.org.uk>
Date: Sun, 28 Mar 2010 23:19:24 +0100
From: Al Viro <viro@...IV.linux.org.uk>
To: Fran?ois Romieu <romieu@...zoreil.com>
Cc: Ben Hutchings <ben@...adent.org.uk>,
David Miller <davem@...emloft.net>, timo.teras@....fi,
ivecera@...hat.com, netdev@...r.kernel.org
Subject: Re: [PATCH] r8169: fix broken register writes
On Sun, Mar 28, 2010 at 11:28:58PM +0200, Fran?ois Romieu wrote:
> Ben Hutchings <ben@...adent.org.uk> :
> [...]
> > Thanks Fran?ois. Which hardware have you tested this on so far ?
>
> 10ec:8169 (rev 10) / RTL8169sb/8110sb / XID 10000000
>
> Timo's is a 10ec:8167 / RTL8169sc/8110sc / XID 18000000. He only tested
> the MAC[04] part.
FWIW, XID18000000 here (J7F4) loses MAC4 on shutdown; hadn't tested the patch
yet. 2.6.26 (on that box) and 2.6.31 (on identical mb) work, 2.6.33 doesn't.
I suspect that bisect would lead to commit cc098dc70 (i.e. the place where we
started to set address on shutdown). One more data point: ifconfig hw ether
done under 2.6.26 did restore the address. And that's the same function,
isn't it?
Another interesting bit: unlike the older kernel, grep for eth0 in .33 dmesg
eth0: RTL8169sc/8110sc at 0xf87fc000, 00:30:18:a4:65:89, XID 18000000 IRQ 18
r8169: eth0: link down
ADDRCONF(NETDEV_UP): eth0: link is not ready
r8169: eth0: link up
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
where with .26 (with the same userland) had
eth0: RTL8169sc/8110sc at 0xf87fc000, 00:30:18:a4:65:89, XID 18000000 IRQ 18
r8169: eth0: link up
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Same for .31 on another box, modulo different address there...
--
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
Powered by blists - more mailing lists