Comment 124 for bug 160413

(In reply to comment #72)
> Success! I managed to get it working for both S5 and S3 some hours ago. :)
>
> My "fix" was to comment out the following four lines in rtl8169_suspend():
>
> spin_lock_irq(&tp->lock);
>
> rtl8169_asic_down(ioaddr);
>
> rtl8169_rx_missed(dev, ioaddr);
>
> spin_unlock_irq(&tp->lock);
>
> Also, I commented out setting a shutdown handler.

I think that you could keep the shutdown handler with the above lines commented out...
What you basically do is disable what stops the network operation (I assume you would lose a few packets this way and eventually disturb the suspend process in case you are still receiving lots of traffic)
For details HW doc is needed, e.g. what does ChipCmd 0x0 exactly mean

> Bruno, with this information, do you still believe it to be related to the
> MAC
> address not being properly configured??
To be checked what NICs were affected (or maybe still partially are), François should know best. But your results don't rule it out.

> Shutting down the box and then pulling and re-attaching the power cord leaves
> it unresponsive to WOL magic packets I'm afraid.
For me the acpitool did the task on this point, you may want to check your BIOS settings as well (how much of WoL it allows).