[Bug 17928] New: Network: problems establishing connection after upgrade (hoary->breezy)
bugzilla-daemon at bugzilla.ubuntu.com
bugzilla-daemon at bugzilla.ubuntu.com
Sun Oct 16 20:33:02 UTC 2005
Please do not reply to this email. You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=17928
Ubuntu | linux
Summary: Network: problems establishing connection after upgrade
(hoary->breezy)
Product: Ubuntu
Version: unspecified
Platform: i386
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: linux
AssignedTo: ben.collins at ubuntu.com
ReportedBy: ilja.sidoroff at iki.fi
QAContact: kernel-bugs at lists.ubuntu.com
After upgrading to breezy I have had problems with network. Establishing
connections to internet hosts fails. The problem is most visible when using
Firefox. About half of the time connections time out. When this happens any
subsequent connection attempts fail also for a short period of time (maybe for a
couple of minutes). The problem is not limited to Firefox, but any other network
connections show similiar behaviour. Nestat shows that connections get stuct
into SYN_SENT state so it seems that for some reason network adapter drops
incoming packets. I'm using onboard network adapter (ASUS A7N8X-VM/400 mobo,
realtek 8201BL LAN). I've tried to pass acpi=off and pci=routeirq parameters to
kernel, but this doesn't help. I suspect forcedeth module has something to do
with this, but I don't know how to debug this further. Any tips would be great.
Here is cat /proc/interrupts:
CPU0
0: 25367545 IO-APIC-edge timer
1: 7277 IO-APIC-edge i8042
8: 1 IO-APIC-edge rtc
9: 0 IO-APIC-level acpi
14: 98523 IO-APIC-edge ide0
15: 226823 IO-APIC-edge ide1
18: 4941522 IO-APIC-level EMU10K1, nvidia
19: 3 IO-APIC-level ohci1394
20: 3 IO-APIC-level ehci_hcd:usb3
21: 114317 IO-APIC-level ohci_hcd:usb2
22: 2606567 IO-APIC-level ohci_hcd:usb1, eth0
NMI: 0
LOC: 25205317
ERR: 0
MIS: 0
and attached dmesg & lsmod outputs
--
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
More information about the kernel-bugs
mailing list