LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Ivan Vecera <ivecera@redhat.com> To: Simon Arlott <simon@fire.lp0.eu> Cc: Krzysztof Halasa <khc@pm.waw.pl>, Jiri Slaby <jirislaby@gmail.com>, Francois Romieu <romieu@fr.zoreil.com>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, netdev <netdev@vger.kernel.org>, Edward Hsu <edward_hsu@realtek.com.tw> Subject: Re: r8169 MAC addresses broken Date: Tue, 28 Oct 2008 10:12:51 +0100 [thread overview] Message-ID: <4906D793.8020109@redhat.com> (raw) In-Reply-To: <49061B7E.6050409@simon.arlott.org.uk> Simon Arlott napsal(a): > On 26/10/08 12:52, Krzysztof Halasa wrote: >> Jiri Slaby <jirislaby@gmail.com> writes: >> >>> However I may have a hw failure or some bug overwrote my eeprom, I see this >>> in current mmotm: >>> r8169 0000:06:00.0: PCI INT A disabled >>> r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded >>> r8169 0000:06:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 >>> r8169 0000:06:00.0: setting latency timer to 64 >>> r8169: mac_version = 0x0c >>> r8169 0000:06:00.0: irq 43 for MSI/MSI-X >>> r8169: MAC address found in EEPROM: 00:00:00:00:00:00 >>> eth0: RTL8168b/8111b at 0xffffc200042b0000, 00:00:00:00:00:00, XID 38000000 >> I think we need drivers or maybe some tool to save contents of those >> little EEPROM / flash NVM configuration chips before it's too late. >> First the ICH* e1000e corruption and now GbE RTL. > > With the reverted patch my MAC addresses are still broken: Try full power-off (disconnect power supply/remove battery). > > [ 1.527660] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded > [ 1.533421] r8169 0000:00:09.0: PCI INT A -> Link[LNKC] -> GSI 10 (level, low) -> IRQ 10 > [ 1.541743] r8169 0000:00:09.0: PCI: Disallowing DAC for device > [ 1.547799] r8169 0000:00:09.0: no PCI Express capability > [ 1.554519] eth0: RTL8169sc/8110sc at 0xbf6f8000, 00:00:00:00:25:c2, XID 18000000 IRQ 10 > > [ 1.563480] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded > [ 1.570525] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11 > [ 1.576363] r8169 0000:00:0b.0: PCI INT A -> Link[LNKD] -> GSI 11 (level, low) -> IRQ 11 > [ 1.584597] r8169 0000:00:0b.0: PCI: Disallowing DAC for device > [ 1.590651] r8169 0000:00:0b.0: no PCI Express capability > [ 1.596659] eth1: RTL8169sc/8110sc at 0xbf6fc000, 00:00:00:00:25:c3, XID 18000000 IRQ 11 >
next prev parent reply other threads:[~2008-10-28 14:23 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-10-25 20:25 r8169 MAC addresses broken Simon Arlott 2008-10-25 21:49 ` Jiri Slaby 2008-10-25 22:34 ` Francois Romieu 2008-10-25 23:55 ` Alistair John Strachan 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 [this message] 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=4906D793.8020109@redhat.com \ --to=ivecera@redhat.com \ --cc=edward_hsu@realtek.com.tw \ --cc=jirislaby@gmail.com \ --cc=khc@pm.waw.pl \ --cc=linux-kernel@vger.kernel.org \ --cc=netdev@vger.kernel.org \ --cc=romieu@fr.zoreil.com \ --cc=simon@fire.lp0.eu \ /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: linkBe 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).