Arch Linux

Nameless One

Member

Registered: 2007-08-05

Posts: 11

Epic packet loss/inconsistent intarweb. Ugh.

I should have asked MUCH earlier since I've had this problem since the introduction of the 2.6.23 series kernel.
But alas, I was too lazy and instead wallowed around in Windows.

WELL, the problem is this.
1.) On boot, the 'Starting Network' takes longer than it should.
2.) Pinging anywhere results in a huge delay before it shows the first line eg.

PING google.com (74.125.19.103) 56(84) bytes of data.

And then there is an even larger delay till the first response comes in. Usually from there I only receieve every second or third packet, with loss sometimes reaching 80-100%. Each response takes AGES!
3.) Can't download anything (I don't have a browser to test web browsing, just the base install), Pacman is fudged.
4.) After a few minutes the entire net will cut off.

This is on a base install from the 2007.08-2 Core ISO that's been fully updated. When I reboot into the updated environment, I get the above.

This only started occuring after moving to the 2.6.23 series kernel (at least I think it did O.o).
If I install using the 2007.08-2 Core ISO with the 2.6.22 kernel the net works fine up till I do a pacman -Syu and get all the latest packages + reboot.
If I install using the 2007.11-0.4 Core ISO with the 2.6.23 kernel, I get the problems above.

So some package update in between 2007.08-2 and 2007.11-0.4 has broken my net.

I have a wired ASDL connection using a Realtek RTL8110SC network chip on my AMD 690G chipset motherboard. It uses the 'r8169' module.
rc.conf is configured just with eth0="dhcp".

HELP ME!

Last edited by Nameless One (2008-01-12 01:35:40)

jacko

Member

Registered: 2007-11-23

Posts: 840

Re: Epic packet loss/inconsistent intarweb. Ugh.

eth0='dhcp'

maybe that's just a typo on your part.

post your rc.conf and resolv.conf

Last edited by jacko (2008-01-12 01:08:19)

Nameless One

Member

Registered: 2007-08-05

Posts: 11

Re: Epic packet loss/inconsistent intarweb. Ugh.

Yah, sorry, was a typo.

Here is my rc.conf:

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

#
# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_NZ.utf8"
HARDWARECLOCK="localtime"
TIMEZONE="Pacific/Auckland"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

#
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="yes"
# Module Blacklist - modules in this list will never be loaded by udev
MOD_BLACKLIST=()
#
# Modules to load at boot-up (in this order)
#   - prefix a module with a ! to blacklist it
#
MODULES=(r8169 slhc snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

#
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
HOSTNAME="The-Nexus"
#
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available
# interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
#
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
# Don't use this for wireless interfaces, see network profiles below
#
eth0="dhcp"
INTERFACES=(eth0)
#
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
#
# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network-profiles
#
#NET_PROFILES=(main)

#
# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng network netfs crond)


# End of file

...and my pretty much empty resolv.conf

# Generated by dhcpcd for interface eth0
nameserver 10.1.1.1

peets

Member

From: Montreal

Registered: 2007-01-11

Posts: 936

Website

Re: Epic packet loss/inconsistent intarweb. Ugh.

You could try adding a line somewhat like this to your /etc/pacman.conf

HoldPkg = kernel26

and then upgrade everything (pacman -Syu). Your kernel won't get upgraded, and you'll be able to see if it's really the culprit.

Or, simpler yet, upgrade just the kernel and see if the net still works!

Nameless One

Member

Registered: 2007-08-05

Posts: 11

Re: Epic packet loss/inconsistent intarweb. Ugh.

Well I did just what you said peets.
I did a fresh install from the 2007.08-2 ISO. Net is working.
I then only updated the 'kernel26' package. Reboot.
Net isn't working.

Well, seems like the problem is isolated to the 2.6.23 kernel and whatever else is in its package.

EDIT: It isn't such a huge deal. I've now got a fully working desktop but I've avoided updating the kernel, it's still at 2.6.22.9, but everything else is up to date and I compiled Catalyst 7.12 for 2.6.22.
But it would be nice to know what is causing the problem so that I might get a nice new and shiny kernel

Last edited by Nameless One (2008-01-12 06:27:15)

jacko

Member

Registered: 2007-11-23

Posts: 840

Re: Epic packet loss/inconsistent intarweb. Ugh.

this seems like a huge problem though, from the looks of it I'd say whatever is happening, it's happening when dhcpcd is generating a nameserver. Everything else looks just fine. But, I am not the one to ask about why resolve.conf isn't getting generated right.

do u have another linux install with the net working? U could upgrade to the newest kernel and then manually update the resolve.conf with a working nameserver list and see if you still have the problem. That would help narrow the problem down even further. May help point someone in the right direction to solve the issue.

edit: I think once u upgrade to new kernel u just manually edit resolve.conf with working nameserver list and should be well for you. My nameservers haven't changed since the day I ordered my internet.

Last edited by jacko (2008-01-12 14:58:44)

Nameless One

Member

Registered: 2007-08-05

Posts: 11

Re: Epic packet loss/inconsistent intarweb. Ugh.

I've got Windows Vista and Arch installed, and the net works fine on both right now.
The Arch install was a fresh one I did yesterday, it's fully updated EXCEPT the kernel. So it's at 2.6.22.9 BUT the internet works fine on it.
The funny thing is my resolv.conf on this working 2.6.22.9 installation is identical O.o

# Generated by dhcpcd for interface eth0
nameserver 10.1.1.1

It might be the resolv.conf but the fact the same one works on 2.6.22.9 means the problem may possibly lay elsewhere.
Could it possibly be a fudged kernel module? I'm stumped.