[arch-general] e1000e 2.6.30.1 kernel massive packet loss
in addition to my resolv.conf issues. I notice a severe packet loss 20-30% between me an my local router. downgrading to the 2.6.30.0-5 kernel seems to fix it. anyone aware of driver problems with the e1000e driver in that kernel? -- Caleb Cushing http://xenoterracide.blogspot.com
Caleb Cushing schrieb:
in addition to my resolv.conf issues. I notice a severe packet loss 20-30% between me an my local router. downgrading to the 2.6.30.0-5 kernel seems to fix it. anyone aware of driver problems with the e1000e driver in that kernel?
The only upstream change between 2.6.30 and 2.6.30.1 I could see are: Andy Gospodarek (1): e1000e: stop unnecessary polling when using msi-x You can try booting with the nomsi kernel option. If that helps (and if it doesn't), can you please open an upstream bug report?
On Fri, Jul 10, 2009 at 5:09 PM, Thomas Bächler<thomas@archlinux.org> wrote:
Caleb Cushing schrieb:
in addition to my resolv.conf issues. I notice a severe packet loss 20-30% between me an my local router. downgrading to the 2.6.30.0-5 kernel seems to fix it. anyone aware of driver problems with the e1000e driver in that kernel?
The only upstream change between 2.6.30 and 2.6.30.1 I could see are:
Andy Gospodarek (1): e1000e: stop unnecessary polling when using msi-x
You can try booting with the nomsi kernel option. If that helps (and if it doesn't), can you please open an upstream bug report?
Are you sure this is related to this machine? With this issue and the resolv.conf issue (it being empty) you reported, my gut says something is whacked with your router.
On Fri, Jul 10, 2009 at 6:15 PM, Aaron Griffin<aaronmgriffin@gmail.com> wrote:
Are you sure this is related to this machine? With this issue and the resolv.conf issue (it being empty) you reported, my gut says something is whacked with your router.
my router doesn't provide my dns I have a dns server running locally (which is why dhcpcd isn't supposed to overwrite resolv.conf). the fact that the packet loss immediately went away when I downgraded and I didn't have a problem until I actually loaded the new kernel. (my router is an linksys wrt54gl running openwrt 8.09.1) -- Caleb Cushing http://xenoterracide.blogspot.com
Caleb Cushing schrieb:
my router doesn't provide my dns I have a dns server running locally (which is why dhcpcd isn't supposed to overwrite resolv.conf). the fact that the packet loss immediately went away when I downgraded and I didn't have a problem until I actually loaded the new kernel. (my router is an linksys wrt54gl running openwrt 8.09.1)
You have to break that thing pretty hard to not provide DNS. Actually, I couldn't get dnsmasq to not transmit DNS via DHCP even when I wanted to.
On Fri, Jul 10, 2009 at 6:53 PM, Thomas Bächler<thomas@archlinux.org> wrote:
You have to break that thing pretty hard to not provide DNS. Actually, I couldn't get dnsmasq to not transmit DNS via DHCP even when I wanted to.
well... 8.09.1 has an option to disable. but my as I've said in the other thread I've configured dhcpcd.conf not to get dns. sot it's behaving appropriately that way. but inappropriately by still overwriting resolv.conf. -- Caleb Cushing http://xenoterracide.blogspot.com
On Fri, Jul 10, 2009 at 6:09 PM, Thomas Bächler<thomas@archlinux.org> wrote:
You can try booting with the nomsi kernel option. If that helps (and if it doesn't), can you please open an upstream bug report?
out of curiousity since I downgraded using pacman -U ... would my fallback kernel be 2.6.30.1 or? I'm not sure how fallback creation works. also since MSI is normally enabled, isn't disabling it kind of off for telling if those changes are the cause of the problem? -- Caleb Cushing http://xenoterracide.blogspot.com
On Fri, Jul 10, 2009 at 6:39 PM, Caleb Cushing<xenoterracide@gmail.com> wrote:
On Fri, Jul 10, 2009 at 6:09 PM, Thomas Bächler<thomas@archlinux.org> wrote:
You can try booting with the nomsi kernel option. If that helps (and if it doesn't), can you please open an upstream bug report?
out of curiousity since I downgraded using pacman -U ... would my fallback kernel be 2.6.30.1 or? I'm not sure how fallback creation works. also since MSI is normally enabled, isn't disabling it kind of off for telling if those changes are the cause of the problem?
Arch doesn't have a fallback kernel. It only has a fallback initrd which doesn't attempt to keep things out that shouldn't be needed in a normal startup. -Dan
participants (4)
-
Aaron Griffin
-
Caleb Cushing
-
Dan McGee
-
Thomas Bächler