https://bugzilla.novell.com/show_bug.cgi?id=342148#c1 Summary: after kernel upadate: e1000 ethernet only works while in promiscuous mode Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: koenig@linux.de QAContact: qa@suse.de Found By: --- last weekend I got a new kernel via online update to harald > uname -a Linux harald 2.6.22.12-0.1-default #1 SMP 2007/11/06 23:05:18 UTC x86_64 x86_64 x86_64 GNU/Linux on an IBM T60 notebook with e1000. now since monday I have major problems with dhcp and network setup in our company, before none of these problems showed up regularly (not with 10.3 before last update and not with 10.1/10.2 before). 1) the weirdest effect to me is that now a ping to the default gateway only works while eth1 (e1000) is in promiscuous mode by running tcpdump. as soon as I stop tcpdump, I can't reach the gateway anymore :-( completely stopping firewall doesn't make any difference. finally I did a "rmmod e1000 ; modprobe e1000" and "ping gateway" works again without running tcpdump. other observations: 2) on monday (day 1 after update;) the same "can't ping gateway" happend. at that time I finally stoppted testing and did reboot the notebook (usually I only do suspend2ram for weeks -- typically until kernel update;). 3) dhcp takes very long (many minutes and/or multiple unplug/plug of RJ45). today our net admin checked the dhcp server logs and noticed that the first dhcp answer from the dhcp server seemed to be ignored from the notebook. it took 15 minutes until the notebook got it's (static/reserved) ip-adress via dhcpcd. tough ping to gateway didn't work then (see above). are there known/similar problems with the current kernel 2.6.22.12-0.1 ? any suggestion for testing in case the same problems show up again tomorrow morning ? before I found out that running tcpdump fixes the "can't ping gateway" problem, I planned for next morning to run tcpdump on eth1 before I connect the RJ45 and capture all packets, so that later I can check and compare the dhcp server log with the tcpdump log of the received dhcp packets. but now it might happen that running tcpdump might influence just the problem which I try to test -- can this be a heisenbug ? any thoughts about good tests -- or any suggestion about new kernel/setttings ? one scenario for next week is to step back to last kernel version. comments on that ? -- 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.