Bug 6108 - Failure of r8169 ethernet i/f after resume from S3 sleep
Summary: Failure of r8169 ethernet i/f after resume from S3 sleep
Status: REJECTED INSUFFICIENT_DATA
Alias: None
Product: Drivers
Classification: Unclassified
Component: Network (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Francois Romieu
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-20 02:38 UTC by David Giddy
Modified: 2008-09-24 13:44 UTC (History)
8 users (show)

See Also:
Kernel Version: 2.6.15.3
Subsystem:
Regression: ---
Bisected commit-id:


Attachments
r8169 resume tryfix (6.66 KB, patch)
2006-02-20 15:45 UTC, Francois Romieu
Details | Diff
r8169: fix broken ring index handling in suspend/resume (3.69 KB, patch)
2006-02-22 15:58 UTC, Francois Romieu
Details | Diff
r8169: enable wake on lan (4.07 KB, patch)
2006-02-22 15:59 UTC, Francois Romieu
Details | Diff
.rej file for the seperate wol enable patch (1.71 KB, patch)
2006-02-22 22:44 UTC, Patrick Thomson
Details | Diff

Description David Giddy 2006-02-20 02:38:32 UTC
Most recent kernel where this bug did not occur: Unknown

Distribution: Debian unstable

Hardware Environment: Gigabyte GA-8IPE1000-G motherboard with RTL8169 GigE on 
board. Realtek 8139 100baseT ethernet PCI card activiated as well (but no 
cable connected).

Software Environment: 2.6.15.3 kernel with ACPI patch 20050902-2.6.15.diff, 
DSDT repaired to compile cleanly with iasl. nvidia and USB modules removed 
before testing. Shutdown to single user mode before testing. R8169_DEBUG 
defined in r8169.c to print debugging info.

Problem Description: 
On resume from S3 sleep state, r8169 ethernet interface will not respond.


Steps to reproduce:
telinit 1
rmmod nvidia ehci_hcd
echo -n mem >/sys/power/state
Push power button to resume
Network will no longer work

Relevant files (I hope!):

dmesg output:
kernel code, 12076k reserved, 653k data, 160k init, 131008k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 3033.57 BogoMIPS (lpj=6067144)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 3febfbff 00000000 00000000 00000000 
00000000 00000000 00000000
CPU: After vendor identify, caps: 3febfbff 00000000 00000000 00000000 00000000 
00000000 00000000
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 256K
CPU: After all inits, caps: 3febfbff 00000000 00000000 00000080 00000000 
00000000 00000000
mtrr: v2.0 (20020519)
CPU: Intel(R) Pentium(R) 4 CPU 1.50GHz stepping 02
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
   tbget-0284: *** Info: Table [DSDT] replaced by host OS
 tbxface-0109 [02] load_tables           : ACPI Tables successfully acquired
Parsing all Control 
Methods:.......................................................................
............................................................................
Table [DSDT](id 0005) - 561 Objects with 54 Devices 147 Methods 25 Regions
ACPI Namespace successfully loaded at root c03dc5dc
ACPI: setting ELCR to 0200 (from 0eb8)
evxfevnt-0091 [03] enable                : Transition to ACPI mode successful
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfb040, last bus=2
PCI: Using configuration type 1
ACPI: Subsystem revision 20050902
evgpeblk-0988 [06] ev_create_gpe_block   : GPE 00 to 1F [_GPE] 4 regs on int 
0x9
evgpeblk-0996 [06] ev_create_gpe_block   : Found 6 Wake, Enabled 0 Runtime 
GPEs in this block
Completing Region/Field/Buffer/Package 
initialization:................................................................
Initialized 24/25 Regions 9/9 Fields 21/21 Buffers 10/10 Packages (570 nodes)
Executing all Device _STA and_INI 
methods:...........................................................
59 Devices found containing: 59 _STA, 2 _INI methods
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
PCI quirk: region 1000-107f claimed by ICH4 ACPI/GPIO/TCO
PCI quirk: region 1080-10bf claimed by ICH4 GPIO
PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
Boot video device is 0000:01:00.0
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs *3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 *7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 *4 5 6 7 9 10 11 12 14 15)
SCSI subsystem initialized
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
PCI: Bridge: 0000:00:01.0
  IO window: disabled.
  MEM window: f8000000-f9ffffff
  PREFETCH window: f0000000-f7ffffff
PCI: Bridge: 0000:00:1e.0
  IO window: 9000-afff
  MEM window: fa000000-fbffffff
  PREFETCH window: 50000000-500fffff
PCI: Setting latency timer of device 0000:00:1e.0 to 64
highmem bounce pool size: 64 pages
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
ACPI: Power Button (FF) [PWRF]
ACPI: Power Button (CM) [PWRB]
ACPI: Fan [FAN] (on)
acpi_processor-0507 [06] processor_get_info    : Error getting cpuindex for 
acpiid 0x1
ACPI: Thermal Zone [THRM] (22 C)
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH5: IDE controller at PCI slot 0000:00:1f.1
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:00:1f.1[A] -> Link [LNKC] -> GSI 11 (level, low) -> 
IRQ 11
ICH5: chipset revision 2
ICH5: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide0...
hda: Maxtor 6Y080L0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: Maxtor 6Y080L0, ATA DISK drive
hdd: LTN526D, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
SiI680: IDE controller at PCI slot 0000:02:01.0
ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt 0000:02:01.0[A] -> Link [LNKF] -> GSI 10 (level, low) -> 
IRQ 10
SiI680: chipset revision 2
SiI680: BASE CLOCK == 133
SiI680: 100% native mode on irq 10
    ide2: MMIO-DMA , BIOS settings: hde:pio, hdf:pio
    ide3: MMIO-DMA , BIOS settings: hdg:pio, hdh:pio
Probing IDE interface ide2...
Probing IDE interface ide3...
hdg: Maxtor 6Y120L0, ATA DISK drive
ide3 at 0xf88100c0-0xf88100c7,0xf88100ca on irq 10
Probing IDE interface ide2...
hda: max request size: 128KiB
hda: Host Protected Area detected.
	current capacity is 160084415 sectors (81963 MB)
	native  capacity is 160086528 sectors (81964 MB)
hda: Host Protected Area disabled.
hda: 160086528 sectors (81964 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
hda: cache flushes supported
 hda: hda1 hda2 hda3
hdc: max request size: 128KiB
hdc: 160086528 sectors (81964 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
hdc: cache flushes supported
 hdc: hdc1 hdc2 hdc3
hdg: max request size: 64KiB
hdg: 240121728 sectors (122942 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(133)
hdg: cache flushes supported
 hdg: hdg1 hdg2 hdg3 < hdg5 hdg6 hdg7 >
libata version 1.20 loaded.
ata_piix 0000:00:1f.2: version 1.05
ACPI: PCI Interrupt 0000:00:1f.2[A] -> Link [LNKC] -> GSI 11 (level, low) -> 
IRQ 11
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ata1: SATA max UDMA/133 cmd 0xC000 ctl 0xC402 bmdma 0xD000 irq 11
ata2: SATA max UDMA/133 cmd 0xC800 ctl 0xCC02 bmdma 0xD008 irq 11
ata1: dev 0 cfg 49:2f00 82:346b 83:5b01 84:4003 85:3468 86:1801 87:4003 88:207f
ata1: dev 0 ATA-6, max UDMA/133, 58631231 sectors: LBA
ata1(0): applying bridge limits
ata1: dev 0 configured for UDMA/100
scsi0 : ata_piix
ata2: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3468 86:3c01 87:4003 88:207f
ata2: dev 0 ATA-6, max UDMA/133, 156301488 sectors: LBA48
ata2: dev 0 configured for UDMA/133
scsi1 : ata_piix
  Vendor: ATA       Model: ST330013AS        Rev: 3.01
  Type:   Direct-Access                      ANSI SCSI revision: 05
  Vendor: ATA       Model: ST380817AS        Rev: 3.42
  Type:   Direct-Access                      ANSI SCSI revision: 05
SCSI device sda: 58631231 512-byte hdwr sectors (30019 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 58631231 512-byte hdwr sectors (30019 MB)
SCSI device sda: drive cache: write back
 sda: sda1 sda2
sd 0:0:0:0: Attached scsi disk sda
SCSI device sdb: 156301488 512-byte hdwr sectors (80026 MB)
SCSI device sdb: drive cache: write back
SCSI device sdb: 156301488 512-byte hdwr sectors (80026 MB)
SCSI device sdb: drive cache: write back
 sdb: sdb1 sdb2
sd 1:0:0:0: Attached scsi disk sdb
md: raid0 personality registered as nr 2
md: raid5 personality registered as nr 4
raid5: automatically using best checksumming function: pIII_sse
   pIII_sse  :  1983.000 MB/sec
raid5: using function: pIII_sse (1983.000 MB/sec)
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
NET: Registered protocol family 2
input: AT Translated Set 2 keyboard as /class/input/input0
IP route cache hash table entries: 65536 (order: 6, 262144 bytes)
TCP established hash table entries: 262144 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
TCP bic registered
Using IPI Shortcut mode
ACPI wakeup devices: 
PCI0 HUB0 USB0 USB1 USB2 USB3 USBE 
ACPI: (supports S0 S3 S4 S5)
md: Autodetecting RAID arrays.
md: autorun ...
md: considering sdb2 ...
md:  adding sdb2 ...
md:  adding hdg5 ...
md: hdg1 has different UUID to sdb2
md:  adding hdc3 ...
md: hdc1 has different UUID to sdb2
md:  adding hda3 ...
md: hda1 has different UUID to sdb2
md: created md1
md: bind<hda3>
md: bind<hdc3>
md: bind<hdg5>
md: bind<sdb2>
md: running: <sdb2><hdg5><hdc3><hda3>
raid5: device sdb2 operational as raid disk 3
raid5: device hdg5 operational as raid disk 2
raid5: device hdc3 operational as raid disk 1
raid5: device hda3 operational as raid disk 0
raid5: allocated 4195kB for md1
raid5: raid level 5 set md1 active with 4 out of 4 devices, algorithm 2
RAID5 conf printout:
 --- rd:4 wd:4 fd:0
 disk 0, o:1, dev:hda3
 disk 1, o:1, dev:hdc3
 disk 2, o:1, dev:hdg5
 disk 3, o:1, dev:sdb2
md: considering hdg1 ...
md:  adding hdg1 ...
md:  adding hdc1 ...
md:  adding hda1 ...
md: created md0
md: bind<hda1>
md: bind<hdc1>
md: bind<hdg1>
md: running: <hdg1><hdc1><hda1>
md0: setting max_sectors to 128, segment boundary to 32767
raid0: looking at hdg1
raid0:   comparing hdg1(1951744) with hdg1(1951744)
raid0:   END
raid0:   ==> UNIQUE
raid0: 1 zones
raid0: looking at hdc1
raid0:   comparing hdc1(1951744) with hdg1(1951744)
raid0:   EQUAL
raid0: looking at hda1
raid0:   comparing hda1(1951744) with hdg1(1951744)
raid0:   EQUAL
raid0: FINAL 1 zones
raid0: done.
raid0 : md_size is 5855232 blocks.
raid0 : conf->hash_spacing is 5855232 blocks.
raid0 : nb_zone is 1.
raid0 : Allocating 4 bytes for hash.
md: ... autorun DONE.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 160k freed
NET: Registered protocol family 1
usbcore: registered new driver usbfs
usbcore: registered new driver hub
hdd: ATAPI 52X CD-ROM drive, 120kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
USB Universal Host Controller Interface driver v2.3
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 5
PCI: setting IRQ 5 as level-triggered
ACPI: PCI Interrupt 0000:00:1d.0[A] -> Link [LNKA] -> GSI 5 (level, low) -> 
IRQ 5
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1d.0: irq 5, io base 0x0000bc00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 9
PCI: setting IRQ 9 as level-triggered
ACPI: PCI Interrupt 0000:00:1d.1[B] -> Link [LNKD] -> GSI 9 (level, low) -> 
IRQ 9
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.1: irq 9, io base 0x0000b000
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.2[C] -> Link [LNKC] -> GSI 11 (level, low) -> 
IRQ 11
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.2: irq 11, io base 0x0000b400
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.3[A] -> Link [LNKA] -> GSI 5 (level, low) -> 
IRQ 5
PCI: Setting latency timer of device 0000:00:1d.3 to 64
uhci_hcd 0000:00:1d.3: UHCI Host Controller
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.3: irq 5, io base 0x0000b800
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
acpi_bus-0201 [01] bus_set_power         : Device is not power manageable
ACPI: PCI Interrupt Link [LNK1] enabled at IRQ 4
PCI: setting IRQ 4 as level-triggered
ACPI: PCI Interrupt 0000:00:1d.7[D] -> Link [LNK1] -> GSI 4 (level, low) -> 
IRQ 4
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
PCI: cache line size of 128 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 5
ehci_hcd 0000:00:1d.7: irq 4, io mem 0xfc000000
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 8 ports detected
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 3
PCI: setting IRQ 3 as level-triggered
ACPI: PCI Interrupt 0000:00:1f.5[B] -> Link [LNKB] -> GSI 3 (level, low) -> 
IRQ 3
PCI: Setting latency timer of device 0000:00:1f.5 to 64
mice: PS/2 mouse device common for all mice
intel8x0_measure_ac97_clock: measured 54181 usecs
intel8x0: clocking to 48000
r8169 Gigabit Ethernet driver 2.2LK-NAPI loaded
ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 7
PCI: setting IRQ 7 as level-triggered
ACPI: PCI Interrupt 0000:02:09.0[A] -> Link [LNKE] -> GSI 7 (level, low) -> 
IRQ 7
r8169: mac_version == RTL_GIGA_MAC_VER_E (0002)
r8169: phy_version == RTL_GIGA_PHY_VER_E (0000)
eth0: Identified chip type is 'RTL8169s/8110s'.
eth0: RTL8169 at 0xf887a000, 00:0f:ea:e4:ea:3d, IRQ 7
r8169: mac_version == RTL_GIGA_MAC_VER_E (0002)
r8169: phy_version == RTL_GIGA_PHY_VER_E (0000)
r8169: MAC version != 0 && PHY version == 0 or 1
r8169: Do final_reg2.cfg
r8169: Set MAC Reg C+CR Offset 0x82h = 0x01h
input: GenPS/2 Genius <NULL> as /class/input/input1
8139too Fast Ethernet driver 0.9.27
ACPI: PCI Interrupt 0000:02:03.0[A] -> Link [LNKA] -> GSI 5 (level, low) -> 
IRQ 5
eth1: RealTek RTL8139 at 0xf88c4000, 00:50:ba:60:39:89, IRQ 5
eth1:  Identified 8139 chip type 'RTL-8139C'
Adding 489972k swap on /dev/hda2.  Priority:-1 extents:1 across:489972k
Adding 489972k swap on /dev/hdc2.  Priority:-2 extents:1 across:489972k
Adding 489972k swap on /dev/hdg2.  Priority:-3 extents:1 across:489972k
Adding 498004k swap on /dev/sda1.  Priority:-4 extents:1 across:498004k
Adding 489940k swap on /dev/sdb1.  Priority:-5 extents:1 across:489940k
EXT3 FS on sda2, internal journal
nvidia: module license 'NVIDIA' taints kernel.
ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 5 (level, low) -> 
IRQ 5
NVRM: loading NVIDIA Linux x86 NVIDIA Kernel Module  1.0-8178  Wed Dec 14 
16:22:51 PST 2005
kjournald starting.  Commit interval 5 seconds
EXT3 FS on md1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hdg6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on md0, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hdg7, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
eth1: link down
NET: Registered protocol family 17
r8169: <6>r8169: Set MAC Reg C+CR Offset 0xE0. Bit-3 and bit-14 MUST be 1
r8169: eth0: link up




lspci output:

0000:00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-
Hub Interface (rev 02)
0000:00:01.0 PCI bridge: Intel Corporation 82865G/PE/P PCI to AGP Controller 
(rev 02)
0000:00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB 
UHCI Controller #1 (rev 02)
0000:00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB 
UHCI Controller #2 (rev 02)
0000:00:1d.2 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB 
UHCI Controller #3 (rev 02)
0000:00:1d.3 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB 
UHCI Controller #4 (rev 02)
0000:00:1d.7 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 
EHCI Controller (rev 02)
0000:00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2)
0000:00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC 
Interface Bridge (rev 02)
0000:00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE 
Controller (rev 02)
0000:00:1f.2 IDE interface: Intel Corporation 82801EB (ICH5) SATA Controller 
(rev 02)
0000:00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus Controller 
(rev 02)
0000:00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER 
(ICH5/ICH5R) AC'97 Audio Controller (rev 02)
0000:01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 
5200] (rev a1)
0000:02:01.0 Mass storage controller: Silicon Image, Inc. PCI0680 Ultra ATA-
133 Host Controller (rev 02)
0000:02:03.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10)
0000:02:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 
Gigabit Ethernet (rev 10)



lsmod output (after modules removed):
Module                  Size  Used by
af_packet              16136  0 
evdev                   7680  0 
8139too                21248  0 
r8169                  25736  0 
snd_intel8x0           28700  0 
snd_ac97_codec         90016  1 snd_intel8x0
snd_ac97_bus            1920  1 snd_ac97_codec
snd_pcm                75272  2 snd_intel8x0,snd_ac97_codec
snd_timer              19460  1 snd_pcm
snd                    43876  4 snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
soundcore               7264  1 snd
snd_page_alloc          8328  2 snd_intel8x0,snd_pcm
usbcore               110212  1 
unix                   21808  0 


/proc/interrupts:
           CPU0       
  0:      82397          XT-PIC  timer
  1:        297          XT-PIC  i8042
  2:          0          XT-PIC  cascade
  3:          0          XT-PIC  Intel ICH5
  4:          0          XT-PIC  ehci_hcd:usb5
  5:      19061          XT-PIC  uhci_hcd:usb1, uhci_hcd:usb4, eth1, nvidia
  7:        439          XT-PIC  eth0
  9:          0          XT-PIC  acpi, uhci_hcd:usb2
 10:       1828          XT-PIC  ide3
 11:       5766          XT-PIC  libata, uhci_hcd:usb3
 12:      10135          XT-PIC  i8042
 14:        428          XT-PIC  ide0
 15:        420          XT-PIC  ide1
NMI:          0 
LOC:      82354 
ERR:          0


ifconfig output (after resume when eth0 is not working):
eth0      Link encap:Ethernet  HWaddr 00:0F:EA:E4:EA:3D  
          inet addr:192.168.0.3  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3806 errors:0 dropped:4294967292 overruns:0 frame:0
          TX packets:2459 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1888685 (1.8 MiB)  TX bytes:671499 (655.7 KiB)
          Interrupt:7 Base address:0x4000 

eth1      Link encap:Ethernet  HWaddr 00:50:BA:60:39:89  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:5 Base address:0x6000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:144 errors:0 dropped:0 overruns:0 frame:0
          TX packets:144 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:9648 (9.4 KiB)  TX bytes:9648 (9.4 KiB)
Comment 1 Francois Romieu 2006-02-20 15:45:24 UTC
Created attachment 7426 [details]
r8169 resume tryfix

The way rtl8169_resume() handles the ring indexes is completely broken.
Comment 2 David Giddy 2006-02-21 03:48:57 UTC
The patch seems to have fixed the problem. Machine will now suspend and resume 
and the ethernet interface seems to function normally - Thanks!

Now I need to get Wake-on-LAN working - I presume the driver should support 
that ? Any config gotchas to be aware of ?

Many thanks,

David.
Comment 3 Francois Romieu 2006-02-21 04:05:08 UTC
David Giddy:
[...]
> Now I need to get Wake-on-LAN working - I presume the driver should support
that ? 

'g' mode has just been reported to work.

> Any config gotchas to be aware of ?

The same report said that 'pumbg' did not produce the expected result but I have
not understood what it did exactly. Feel free to describe it. :o)

-- 
Ueimor
Comment 4 David Giddy 2006-02-21 04:24:37 UTC
I tried using ethtool to set each mode and in all cases, it appears to remain
disabled, yet it claims to support all modes. When I put machine into S3, LAN
LEDs are off, which I suspect means the I/F has been completely powered off. The
BIOS setting for wake-on-Ring (LAN) is enabled as are "Wake on PME". 

simba:/home/david# ethtool -s eth0 wol g
simba:/home/david# ethtool eth0
Settings for eth0:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: pumbg
        Wake-on: d
        Current message level: 0x00000033 (51)
        Link detected: yes
simba:/home/david#

Let me know any tests you would like run.
Comment 5 Patrick Thomson 2006-02-21 12:57:42 UTC
The patch provided by Francois has also fixed my issue - namely, a netgear
DGE-528T that uses the 8169 chip, but has wake-on-lan that was not previously
supported properly by the kernel (much to my frustration).

Report: mode g works as expected with a magic packet.

mode p works as expected (poweron when ethernet cable plugged in) (this will
cause the strange bouncing-back after a powerdown when the card is placed in
mode pumbg - since there is already PHY activity by the fact I never unplugged
the cable in the first place)

Further tests pending.

(personally, this is entirely a feature request, since the machine I use this
card in has a really inacessible power switch)

Patrick
Comment 6 Francois Romieu 2006-02-22 15:58:25 UTC
Created attachment 7446 [details]
r8169: fix broken ring index handling in suspend/resume
Comment 7 Francois Romieu 2006-02-22 15:59:52 UTC
Created attachment 7447 [details]
r8169: enable wake on lan
Comment 8 Francois Romieu 2006-02-22 16:09:31 UTC
David, Patrick, could you try the two patch that I have just attached in that
order on top of 2.6.16-rc4, namely:
- r8169: fix broken ring index handling in suspend/resume
- r8169: enable wake on lan

The first one should fix the suspend/resume issue. No WOL.
The second one should add the WOL feature.

Separating the bugfix from the wol feature should ease the merge
process (I'll try both for 2.6.16 but there is no guarantee) and there
are a few little differences from the previous, aggregated, version.

-- 
Ueimor
Comment 9 Patrick Thomson 2006-02-22 22:44:07 UTC
Created attachment 7453 [details]
.rej file for the seperate wol enable patch

It seems that the wol enable patch no longer applies cleanly - It could still
be that I am making a silly mistake, but I tried everything I could think of to
get this to apply cleanly and failed. Vanilla 2.6.15.4 having previously
reverted the existing patch.
Comment 10 Patrick Thomson 2006-02-22 22:48:19 UTC
Yes, I can't read instructions. That would be what happens when I forget to
apply the broken ring index handling patch first. Apologies, but I tend to work
on this early in the morning, perhaps not the best time to patch a kernel.
Comment 11 Patrick Thomson 2006-02-22 23:04:45 UTC
I can confirm that the compound patch still enables wake on lan with the same
functionality I managed to test last time. I also feel rather stupid about the
triple post, but this is offset by the warm fuzzy feeling of contributing in
some small way to the community that supported my needs for so long. Great job,
guys!
Comment 12 David Giddy 2006-02-23 04:05:29 UTC
I tried the two patches against 2.6.16-rc4 and found the following:
- resume still works, however the interface seems to drop back from 1000Mb/s to
100 Mb/s after resume and stay there. I tried ethtool -r eth0, but apparently
triggering re-negotiation is not currently supported.
- setting the wol bits now is correctly reflected in the output of ethtool:

simba# ethtool eth0
Settings for eth0:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 100Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: pumbg
        Wake-on: pumbg
        Current message level: 0x00000033 (51)
        Link detected: yes

However, when I put the computer into S3 sleep, the ethernet LEDs go dark and
there is no response to either a directed packet or a magic packet.
Comment 13 David Giddy 2006-03-02 14:21:10 UTC
Francois,

Any further suggestions on getting WOL working (see my last response)? Any 
recommendations on how to test further ?

Thanks,

David.
Comment 14 Michael Goth 2006-03-11 14:55:00 UTC
Hi!

just wanted to add that wake-on-lan modes p and g work for me on 2.6.15.4 (I
didn't test any other), but only on the first of the three RTL8169 chips of my
board. I don't know if that's a driver bug or a hardware thing. I only need one
port to wake the machine up, so for me, everything works perfectly. Many thanks
to Francois for the patch!

   Michael
Comment 15 David Giddy 2006-04-17 00:21:44 UTC
Francois,

Any further progress on this bug ? See my last comments on the problems I am 
still seeing.

Thanks,

David.
Comment 16 Len Brown 2006-08-09 21:01:22 UTC
this issues appears to be driver specific, rather than ACPI related.
moving to drivers/network
Comment 17 Pavel Machek 2006-09-29 04:11:43 UTC
Is the problem still there with 2.6.18?
Comment 18 Rafael J. Wysocki 2006-10-26 09:48:23 UTC
I think this entry should be closed due to the lack of response from the reporter.
Comment 19 Francois Romieu 2006-10-26 13:34:37 UTC
bugme-daemon@bugzilla.kernel.org <bugme-daemon@bugzilla.kernel.org> :
[...]
> I think this entry should be closed due to the lack of response from the reporter.

I prefer to keep it open:
- some of my r8169 queue from 05/2006 will only be in 2.6.19 ;
- there is a flood of new 8169-like (8168) since mid-2006 ;
- I am not convinced that the issue has gone/is negligible.

Comment 20 David Giddy 2006-10-26 18:00:42 UTC
Sorry, I've been flat out. I haven't had time to followup this bug as
I ditched the offending card and have been using an e1000 based card
(successfully) since. It was still a problem when I last looked some
months back and I haven't seen any updates to the driver since.


On 10/27/06, bugme-daemon@bugzilla.kernel.org
<bugme-daemon@bugzilla.kernel.org> wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=6108
>
>
>
>
>
> ------- Additional Comments From rjwysocki@sisk.pl  2006-10-26 09:48 -------
> I think this entry should be closed due to the lack of response from the reporter.
>
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
> You are on the CC list for the bug, or are watching someone who is.
>

Comment 21 Francois Romieu 2007-04-02 14:46:45 UTC
This one should be fixed by the patch available at:

http://www.fr.zoreil.com/people/francois/misc/20070402-2.6.21-rc5-r8169-test.patch

If nobody complains, I will close the bug as soon as the relevant bits
hits the main trunk.

-- 
Ueimor
Comment 22 Francois Romieu 2007-07-11 14:25:42 UTC
Note to myself: the failure of autonegotation after resume needs to be fixed.
This is the same bug that Peter Missel <peter.missel@onlinehome.de> reported
on netdev (16/04/2007+).

-- 
Ueimor
Comment 23 Natalie Protasevich 2007-07-18 20:19:08 UTC
It looks like the patch mentioned in #21 is in, should David test it? 
Ueimor, I suppose you would still like to keep this bug open until you get the problem in #22?
Thanks.
Comment 24 Francois Romieu 2007-07-19 15:34:59 UTC
Natalie Protasevich:
[...]
> I suppose you would still like to keep this bug open until you get the
> problem in #22?

Yes.

-- 
Ueimor
Comment 25 Alan 2008-09-23 10:30:08 UTC
Still relevant ?
Comment 26 Francois Romieu 2008-09-24 13:44:21 UTC
Alan :
> Still relevant ?

No. It can be closed without a significant loss of information.

I guess that it either calls for more PHY tweaks or it will be fixed with
some (not too) different WOL problem.

-- 
Ueimor

Note You need to log in before you can comment on or make changes to this bug.