Your message dated Thu, 10 Jun 2010 14:23:13 +0100 with message-id <1276176193.14011.119.camel@localhost> and subject line Re: Bug#585420: r8169 shows broken MAC address (and possibly r8169 is broken at all) has caused the Debian Bug report #585420, regarding r8169 shows broken MAC address (and possibly r8169 is broken at all) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 585420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585420 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---Package: linux-image-2.6.32-3-686
- To: submit@bugs.debian.org
- Subject: r8169 shows broken MAC address (and possibly r8169 is broken at all)
- From: Dmitry Baryshev <ksquirrel.iv@gmail.com>
- Date: Thu, 10 Jun 2010 15:55:19 +0300
- Message-id: <AANLkTimjR3kzBT6X14-MKUWQ3y683IwLAQ_hoKokOcFt@mail.gmail.com>
Version: 2.6.32-9Severity: importantI have Realtek ethernet controller on VIA system:02:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8110SC/8169SC Gigabit Ethernet (rev 10)With 2.6.32 it had problems with IRQ:[ 19.000671] r8169: eth0: link up
[ 19.000718] r8169: eth0: link up
[ 19.300868] irq 16: nobody cared (try booting with the "irqpoll" option)
[ 19.300882] Pid: 0, comm: swapper Tainted: G C 2.6.32-3-686 #1
[ 19.300888] Call Trace:
[ 19.300902] [<c106d4e1>] ? __report_bad_irq+0x24/0x69
[ 19.300910] [<c106d4e8>] ? __report_bad_irq+0x2b/0x69
[ 19.300920] [<c106d60d>] ? note_interrupt+0xe7/0x13e
[ 19.300929] [<c106db3b>] ? handle_fasteoi_irq+0x7a/0x97
[ 19.300941] [<c10053cf>] ? handle_irq+0x17/0x1b
[ 19.300949] [<c1004c51>] ? do_IRQ+0x38/0x89
[ 19.300958] [<c10037f0>] ? common_interrupt+0x30/0x38
[ 19.300973] [<c101b074>] ? native_safe_halt+0x2/0x3
[ 19.300982] [<c1008ebb>] ? default_idle+0x3c/0x5a
[ 19.300990] [<c1002388>] ? cpu_idle+0x89/0xa5
[ 19.301004] [<c13a3800>] ? start_kernel+0x30c/0x311
[ 19.301009] handlers:
[ 19.301013] [<f839b848>] (rtl8169_interrupt+0x0/0x283 [r8169])I added "irqpoll" option to the kernel command line. IRQ problem seems to be gone, but know controller doesn't work. I can see it in ifconfig, but it's MAC address is "00:00:00:00:00:0f" (should be "00-21-11-00-00-0f"). My router assignes DHCP addresses according to client's MAC, and after upgrading to 2.6.32 I cannot get DHCP address. I can add rules for "00:00:00:00:00:0f" on my router, but nevertheless, ethernet controller cannot get DHCP address again. It seems to be a r8169 bug in 2.6.32. I've backported some changes from 2.6.34, and now my controller works fine. Backports are in attached patch. It will be great to backport all bugfixes from .34 (AFAIU, it must be done in upstream, since .32 is an LTS).Thanks!
--
Regards, Krasu
Attachment: linux-2.6.32-r8169.diff
Description: Binary data
--- End Message ---
--- Begin Message ---
- To: 585420-done@bugs.debian.org
- Subject: Re: Bug#585420: r8169 shows broken MAC address (and possibly r8169 is broken at all)
- From: Ben Hutchings <ben@decadent.org.uk>
- Date: Thu, 10 Jun 2010 14:23:13 +0100
- Message-id: <1276176193.14011.119.camel@localhost>
- In-reply-to: <AANLkTimjR3kzBT6X14-MKUWQ3y683IwLAQ_hoKokOcFt@mail.gmail.com>
- References: <AANLkTimjR3kzBT6X14-MKUWQ3y683IwLAQ_hoKokOcFt@mail.gmail.com>
Version: 2.6.32-13 On Thu, 2010-06-10 at 15:55 +0300, Dmitry Baryshev wrote: [...] > I've backported some changes from 2.6.34, and now my controller works > fine. Backports are in attached patch. It will be great to backport > all bugfixes from .34 (AFAIU, it must be done in upstream, since .32 > is an LTS). [...] We already have those bug fixes (currently only in unstable, but soon to move into testing). Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.Attachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---