Unfortunately I've still experienced this bug twice with the 3.0.0-1-amd64
kernel, so the problem's still there.

I presume it's a resume bug that needs to be filed against the e1000e module
upstream?

Reply via email to