LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Alistair John Strachan <alistair@devzero.co.uk>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Jiri Slaby <jirislaby@gmail.com>,
Simon Arlott <simon@fire.lp0.eu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
Edward Hsu <edward_hsu@realtek.com.tw>,
Ivan Vecera <ivecera@redhat.com>
Subject: Re: r8169 MAC addresses broken
Date: Sun, 26 Oct 2008 00:55:59 +0100 [thread overview]
Message-ID: <200810260055.59783.alistair@devzero.co.uk> (raw)
In-Reply-To: <20081025223443.GA30913@electric-eye.fr.zoreil.com>
On Saturday 25 October 2008 23:34:43 Francois Romieu wrote:
> Jiri Slaby <jirislaby@gmail.com> :
> [...]
>
> > Ah, I thought I have broken hardware. I have similar problem, my mac is
> > initially all zeroes. When I set it up, it works until suspend. After
> > that I need to unbind the driver, bind it again, and it works then (mac
> > is still the set one).
> >
> > I'm out of the notebook right now, but it is 10ec:8168:
> > 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> > RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
> > Subsystem: ASUSTeK Computer Inc. Unknown device 11f5
> >
> > I used it perfectly far later than 2.6.24 (maybe 2.6.26?), 2.6.27 is yet
> > defunct.
>
> 2.6.27 proper ? That's bad news.
Just thought I'd chime in to report the same thing. I don't use the NICs very
frequently, so I didn't notice until I read the report.
On this machine, the NICs are never put through a suspend/resume cycle, so
that doesn't seem to be anything to do with it.
The NICs should have incremental MAC addresses, since they're mainboard
devices. Put it this way, they used to.
Now when they're detected, one has the correct MAC, and the second has the
first 32bits of its MAC corrupted.
eth0: RTL8169sc/8110sc at 0xffffc2000001e000, 00:50:8d:b3:5f:de, XID 18000000 IRQ 23
eth1: RTL8169sc/8110sc at 0xffffc20000070000, d8:81:ec:10:5f:df, XID 18000000 IRQ 22
d8:81:ec:10 is corruption; 00:50:8d:b3 is correct.
I can bisect pretty easily if this is helpful.
--
Cheers,
Alistair.
next prev parent reply other threads:[~2008-10-25 23:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-25 20:25 Simon Arlott
2008-10-25 21:49 ` Jiri Slaby
2008-10-25 22:34 ` Francois Romieu
2008-10-25 23:55 ` Alistair John Strachan [this message]
2008-10-26 10:38 ` Jiri Slaby
2008-10-26 12:52 ` Krzysztof Halasa
2008-10-26 15:01 ` Francois Romieu
2008-10-27 19:50 ` Simon Arlott
2008-10-28 9:12 ` Ivan Vecera
2008-10-26 20:42 ` Krzysztof Halasa
2008-10-26 17:24 ` Jiri Slaby
2008-10-26 17:34 ` Arjan van de Ven
2008-10-26 17:46 ` Francois Romieu
2008-10-28 10:09 ` Jiri Slaby
2008-10-28 13:45 ` Krzysztof Halasa
2008-10-28 13:51 ` Jiri Slaby
2008-10-28 20:37 ` Krzysztof Halasa
2008-11-03 9:04 ` Ivan Vecera
2008-11-03 14:50 ` Jiri Slaby
2008-11-04 18:49 ` Ivan Vecera
2008-11-04 21:10 ` Jiri Slaby
2008-11-05 9:51 ` Ivan Vecera
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=200810260055.59783.alistair@devzero.co.uk \
--to=alistair@devzero.co.uk \
--cc=edward_hsu@realtek.com.tw \
--cc=ivecera@redhat.com \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
--cc=simon@fire.lp0.eu \
--subject='Re: r8169 MAC addresses broken' \
/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
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).