Hi Matt,
Thanks for the patch. It didn't help with resume - but below is the
output after patching, let me know if you need more details.
( Looks like 0xffffffff is invalid/corrupted device id /vendor id? )
[ 163.856001] tg3 0000:0e:00.0: restoring config space at offset 0xc (was 0x0, writing 0x20040000)
[ 163.856001] tg3 0000:0e:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
[ 163.856001] tg3 0000:0e:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100006)
[snip]
[ 164.450277] pcieport-driver 0000:1e:00.0: setting latency timer to 64
[ 164.450415] pcieport-driver 0000:1e:01.0: setting latency timer to 64
[ 164.450493] tg3 0000:0e:00.0: restoring config space at offset 0xc (was 0x0, writing 0x20040000)
[ 164.451110] serial 00:08: activated
[snip]
[ 168.913863] Restarting tasks ... done.
[ 170.332953] tg3 0000:0e:00.0: wake-up capability disabled by ACPI
[ 170.332960] tg3 0000:0e:00.0: PME# disabled
[ 170.333047] tg3 0000:0e:00.0: irq 54 for MSI/MSI-X
[ 170.333250] eth0: Reg value at offset 0x0 is 0xffffffff
[ 170.394281] [drm] Loading R500 Microcode
[ 170.394330] [drm] Num pipes: 1
[ 171.726650] tg3: eth0: No firmware running.
[ 183.119745] ADDRCONF(NETDEV_UP): eth0: link is not ready
Parag
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html