Bug#573007: NIC r8169 doesn t start at restart on kernel linux-image-2.6.32-trunk-686 (workaround)
- To: 573007@bugs.debian.org
- Subject: Bug#573007: NIC r8169 doesn t start at restart on kernel linux-image-2.6.32-trunk-686 (workaround)
- From: Florent Rougon <f.rougon@free.fr>
- Date: Sun, 28 Mar 2010 19:06:17 +0200
- Message-id: <87wrww8jg6.fsf@zita.maison>
- Reply-to: Florent Rougon <f.rougon@free.fr>, 573007@bugs.debian.org
- In-reply-to: <1269795046.8653.166.camel@localhost> (Ben Hutchings's message of "Sun, 28 Mar 2010 17:50:46 +0100")
- References: <87d3yo9ziv.fsf@zita.maison> <1269795046.8653.166.camel@localhost>
Ben Hutchings <ben@decadent.org.uk> wrote:
> This is now being handled upstream and there is a proposed fix. We will
> apply that once it has been tested across a range of RTL8169-family
> chips.
Thank you. If it can be of some help, I may test something. I am
currently using upstream 2.6.32 compiled with make-kpkg on lenny. My
Ethernet chip is RTL8111D according to the motherboard manual, and the
MB itself is Gigabyte GA-P55-UD5.
'lspci -v' says:
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
Subsystem: Giga-byte Technology Device e000
Flags: bus master, fast devsel, latency 0, IRQ 35
I/O ports at ae00 [size=256]
Memory at fb6ff000 (64-bit, prefetchable) [size=4K]
Memory at fb6f8000 (64-bit, prefetchable) [size=16K]
[virtual] Expansion ROM at fb600000 [disabled] [size=128K]
Capabilities: [40] Power Management version 3
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
Capabilities: [70] Express Endpoint, MSI 01
Capabilities: [ac] MSI-X: Enable- Mask- TabSize=4
Capabilities: [cc] Vital Product Data <?>
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [140] Virtual Channel <?>
Capabilities: [160] Device Serial Number 00-e0-4c-68-00-00-00-03
Kernel driver in use: r8169
Kernel modules: r8169
[ About the script I posted, if anyone wants to use it in the meantime:
I noticed one can be more specific by replacing the "ifup/ifdown -a"
calls with "ifup/ifdown $interfaces". ]
Regards,
--
Florent
Reply to: