https://bugzilla.novell.com/show_bug.cgi?id=342148#c4 --- Comment #4 from Harald Koenig <koenig@linux.de> 2007-11-20 12:58:53 MST --- (In reply to comment #2 from Brandon Philips)
Could you attach the output from `dmesg` while you are seeing the issue?
done (without/before the test suspend cycles below).
Is there any pattern to the times it works and the times it doesn't? Have you tried other wired networks?
not that I'd realize. right now I have the impression that once "it happens" the driver/stack is stuck until I rmmod/modprobe e1000 driver... any idea how to query some driver (tcp stack?) data before/after rmmod/modprobe such that a comparision might give some hints ? I just did a rmmod/modprobe e1000 and then did a few suspend/resume from/to ram cycles with unplug/replug ethernet etc (typical very day duty cycle) but I haven't been successfull trying to trigger problme -- right now ping works fine without tcpdump...
Perhaps you could try testing the latest kernel-default from this repository? http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_Factory/
can't promise it but I'll try to... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.