IRQ handling issues on sandy bridge board

[Michael Atkinson]

I7-2600 on sandy bridge board goes in to slow mode due to interrupt (handling?) problems. (Ubuntu 2.6.38-11.48-generic 2.6.38.8)

(FYI: there are a few instances on this kernel problem published on the web. Depending on what hardware is affected symptoms do change)

Two to three times a day this occurs:

Sep 3 02:32:30 atkinson1 kernel: [52442.380243] irq 16: nobody cared (try booting with the "irqpoll" option)
Sep 3 02:32:30 atkinson1 kernel: [52442.380246] Pid: 2060, comm: vmware-vmx Tainted: P 2.6.38-11-generic #48-Ubuntu
Sep 3 02:32:30 atkinson1 kernel: [52442.380248] Call Trace:
Sep 3 02:32:30 atkinson1 kernel: [52442.380248] <IRQ> [<ffffffff810d515b>] ? __report_bad_irq.clone.2+0x2b/0xa0
Sep 3 02:32:30 atkinson1 kernel: [52442.380256] [<ffffffff810d555a>] ? note_interrupt+0x19a/0x1e0
Sep 3 02:32:30 atkinson1 kernel: [52442.380258] [<ffffffff8106d559>] ? __do_softirq+0xf9/0x1c0
Sep 3 02:32:30 atkinson1 kernel: [52442.380260] [<ffffffff810d644d>] ? handle_fasteoi_irq+0xdd/0x110
Sep 3 02:32:30 atkinson1 kernel: [52442.380263] [<ffffffff8100e9c2>] ? handle_irq+0x22/0x40
Sep 3 02:32:30 atkinson1 kernel: [52442.380266] [<ffffffff815cb57d>] ? do_IRQ+0x5d/0xe0
Sep 3 02:32:30 atkinson1 kernel: [52442.380268] [<ffffffff815c38d3>] ? ret_from_intr+0x0/0x15
Sep 3 02:32:30 atkinson1 kernel: [52442.380269] <EOI> [<ffffffffa0c66347>] ? Task_Switch+0x1307/0x1690 [vmmon]
Sep 3 02:32:30 atkinson1 kernel: [52442.380276] [<ffffffffa0c60010>] ? Warning+0x40/0x50 [vmmon]
Sep 3 02:32:30 atkinson1 kernel: [52442.380279] [<ffffffffa0c68fcf>] ? Vmx86_RunVM+0xbf/0x360 [vmmon]
Sep 3 02:32:30 atkinson1 kernel: [52442.380282] [<ffffffff81178558>] ? do_sys_poll+0x1d8/0x240
Sep 3 02:32:30 atkinson1 kernel: [52442.380284] [<ffffffff81177080>] ? __pollwait+0x0/0xf0
Sep 3 02:32:30 atkinson1 kernel: [52442.380287] [<ffffffffa0c5f6db>] ? LinuxDriver_Ioctl.clone.3+0xdcb/0x10b0 [vmmon]
Sep 3 02:32:30 atkinson1 kernel: [52442.380289] [<ffffffff81177170>] ? pollwake+0x0/0x60
Sep 3 02:32:30 atkinson1 kernel: [52442.380290] [<ffffffff81177170>] ? pollwake+0x0/0x60
Sep 3 02:32:30 atkinson1 kernel: [52442.380292] [<ffffffff81177170>] ? pollwake+0x0/0x60
Sep 3 02:32:30 atkinson1 kernel: [52442.380294] [<ffffffff81177170>] ? pollwake+0x0/0x60
Sep 3 02:32:30 atkinson1 kernel: [52442.380296] [<ffffffff81177170>] ? pollwake+0x0/0x60
Sep 3 02:32:30 atkinson1 kernel: [52442.380298] [<ffffffff81177170>] ? pollwake+0x0/0x60
Sep 3 02:32:30 atkinson1 kernel: [52442.380300] [<ffffffff8105f464>] ? try_to_wake_up+0x244/0x3e0
Sep 3 02:32:30 atkinson1 kernel: [52442.380301] [<ffffffff8105f612>] ? default_wake_function+0x12/0x20
Sep 3 02:32:30 atkinson1 kernel: [52442.380304] [<ffffffff8127aab6>] ? security_task_kill+0x16/0x20
Sep 3 02:32:30 atkinson1 kernel: [52442.380306] [<ffffffff81077e50>] ? check_kill_permission+0x120/0x180
Sep 3 02:32:30 atkinson1 kernel: [52442.380308] [<ffffffff8107a0d6>] ? group_send_sig_info+0x26/0x70
Sep 3 02:32:30 atkinson1 kernel: [52442.380310] [<ffffffff8107a22f>] ? kill_pid_info+0x3f/0x60
Sep 3 02:32:30 atkinson1 kernel: [52442.380311] [<ffffffff8107a290>] ? kill_something_info+0x40/0x160
Sep 3 02:32:30 atkinson1 kernel: [52442.380313] [<ffffffff8105f600>] ? default_wake_function+0x0/0x20
Sep 3 02:32:30 atkinson1 kernel: [52442.380315] [<ffffffffa0c5f9d5>] ? LinuxDriver_UnlockedIoctl+0x15/0x20 [vmmon]
Sep 3 02:32:30 atkinson1 kernel: [52442.380317] [<ffffffff811764ff>] ? do_vfs_ioctl+0x8f/0x360
Sep 3 02:32:30 atkinson1 kernel: [52442.380319] [<ffffffff81165020>] ? vfs_read+0x120/0x180
Sep 3 02:32:30 atkinson1 kernel: [52442.380321] [<ffffffff81176861>] ? sys_ioctl+0x91/0xa0
Sep 3 02:32:30 atkinson1 kernel: [52442.380323] [<ffffffff8100c002>] ? system_call_fastpath+0x16/0x1b
Sep 3 02:32:30 atkinson1 kernel: [52442.380324] handlers:
Sep 3 02:32:30 atkinson1 kernel: [52442.380325] [<ffffffff814376f0>] (usb_hcd_irq+0x0/0x70)
Sep 3 02:32:30 atkinson1 kernel: [52442.380329] [<ffffffffa007e4a0>] (rhine_interrupt+0x0/0x2d0 [via_rhine])
Sep 3 02:32:30 atkinson1 kernel: [52442.380334] [<ffffffffa06cbe90>] (nv_kern_isr+0x0/0x80 [nvidia])
Sep 3 02:32:30 atkinson1 kernel: [52442.380460] Disabling IRQ #16

The system is then slow until i disable and re-enable networkingIE. Probably due to Ethernet being on IRQ16.

By slow i mean extremely slow graphics, slow keyboard response, jerky mouse movement.

~$ cat /proc/interrupts
           CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7
  0: 307 0 0 0 0 0 0 0 IR-IO-APIC-edge timer
  1: 2 0 0 0 0 0 0 0 IR-IO-APIC-edge i8042
  4: 4 0 0 0 0 0 0 0 IR-IO-APIC-edge
  8: 1 0 0 0 0 0 0 0 IR-IO-APIC-edge rtc0
  9: 0 0 0 0 0 0 0 0 IR-IO-APIC-fasteoi acpi
 12: 4 0 0 0 0 0 0 0 IR-IO-APIC-edge i8042
 16: 3581288 0 0 0 0 0 0 0 IR-IO-APIC-fasteoi ehci_hcd:usb1, nvidia, eth2
 17: 212 0 0 0 0 0 0 0 IR-IO-APIC-fasteoi hda_intel
 23: 63 127495 0 0 0 0 0 0 IR-IO-APIC-fasteoi ehci_hcd:usb2
 40: 0 0 0 0 0 0 0 0 DMAR_MSI-edge dmar0
 42: 6055887 0 0 0 0 0 0 0 IR-PCI-MSI-edge eth1
 43: 96186 688875 0 0 0 0 0 0 IR-PCI-MSI-edge ahci
 44: 1 0 0 0 0 0 0 0 IR-PCI-MSI-edge xhci_hcd
 45: 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge xhci_hcd
 46: 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge xhci_hcd
 47: 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge xhci_hcd
 48: 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge xhci_hcd
 49: 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge xhci_hcd
 50: 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge xhci_hcd
 51: 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge xhci_hcd
 52: 3371 0 80292 0 0 0 0 0 IR-PCI-MSI-edge hda_intel
NMI: 0 0 0 0 0 0 0 0 Non-maskable interrupts
LOC: 36042344 13862118 9086861 4722130 35157018 11887098 24667071 5105328 Local timer interrupts
SPU: 0 0 0 0 0 0 0 0 Spurious interrupts
PMI: 0 0 0 0 0 0 0 0 Performance monitoring interrupts
IWI: 0 0 0 0 0 0 0 0 IRQ work interrupts
RES: 47641 16087 3136 1403 50228 9355 3178 1422 Rescheduling interrupts
CAL: 7674 11013 12902 15967 13619 15382 17726 15201 Function call interrupts
TLB: 24375 47217 5488 1474 18702 8560 3888 1383 TLB shootdowns
TRM: 0 0 0 0 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 0 0 0 0 Threshold APIC interrupts
MCE: 0 0 0 0 0 0 0 0 Machine check exceptions
MCP: 283 283 283 283 283 283 283 283 Machine check polls
ERR: 0
MIS: 0

I agree that primarily one would expect vmware to be (part of) the cause, but there are many others indicating similar issues without vmware
example: http://blog.adamsbros.org/2011/07/21/ubuntu-sluggish-or-slow/
Most informative: https://bugzilla.redhat.com/show_bug.cgi?id=474624
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: michael 1511 F.... pulseaudio
 /dev/snd/pcmC0D0p: michael 1511 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xfb300000 irq 52'
   Mixer name : 'Realtek ALC892'
   Components : 'HDA:10ec0892,14627673,00100302'
   Controls : 32
   Simple ctrls : 18
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xfb080000 irq 17'
   Mixer name : 'Nvidia GPU 1c HDMI/DP'
   Components : 'HDA:10de001c,14622630,00100100'
   Controls : 4
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
DistroRelease: Ubuntu 11.04
HibernationDevice: RESUME=UUID=06ab5e32-68a5-4c2b-ae46-e2a04305d074
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
IwConfig:
 lo no wireless extensions.

 eth1 no wireless extensions.

 eth2 no wireless extensions.
MachineType: MSI MS-7673
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic root=UUID=0eafddd4-988e-41d8-8a24-3e1b86d35132 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-11-generic N/A
 linux-backports-modules-2.6.38-11-generic N/A
 linux-firmware 1.52
RfKill:

Tags: natty
Uname: Linux 2.6.38-11-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 03/02/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.9
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P67A-C43 (MS-7673)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd03/02/2011:svnMSI:pnMS-7673:pvr1.0:rvnMSI:rnP67A-C43(MS-7673):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7673
dmi.product.version: 1.0
dmi.sys.vendor: MSI

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 843709

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Michael Atkinson (mongoose-m)]

Additional info

[Michael Atkinson (mongoose-m)]

apport information

[Michael Atkinson (mongoose-m)]

apport information

[Michael Atkinson (mongoose-m)]

apport information

[Michael Atkinson (mongoose-m)]

apport information

[Michael Atkinson (mongoose-m)]

apport information

[Michael Atkinson (mongoose-m)]

apport information

[Michael Atkinson (mongoose-m)]

apport information

[Michael Atkinson (mongoose-m)]

apport information

[Michael Atkinson (mongoose-m)]

apport information

[Michael Atkinson (mongoose-m)]

apport information

[Michael Atkinson (mongoose-m)]

apport information

[Michael Atkinson (mongoose-m)]

apport information

[Michael Atkinson (mongoose-m)]

apport information

[Michael Atkinson (mongoose-m)]

apport information

[Michael Atkinson (mongoose-m)]

apport information

[Michael Atkinson (mongoose-m)]

apport information

[Michael Atkinson (mongoose-m)]

apport information

[Michael Atkinson (mongoose-m)]

apport information

[Michael Atkinson (mongoose-m)]

Update:

The original configuration had 2 x 4 GB DDR-3 modules. After upgrading to 4 x 4 GB DDR-3 modules, the problem has disappeared.

Suspect there is a memory issue involved in the interrupt handling process.

[Raymond Johnson (johnson-downclimb)]

I'm pretty sure that this bug is causing my network to fail on me every 5 minutes to 5+hours. I can restart it by disabling and re-enabling networking with the network manager, but the entry in dmesg is always the same:

[ 4163.037770] irq 18: nobody cared (try booting with the "irqpoll" option)
[ 4163.037777] Pid: 0, comm: swapper Tainted: P C 3.0.0-12-generic #20-Ubuntu
[ 4163.037779] Call Trace:
[ 4163.037781] <IRQ> [<ffffffff810cf8ad>] __report_bad_irq+0x3d/0xe0
[ 4163.037793] [<ffffffff810cfcd5>] note_interrupt+0x135/0x180
[ 4163.037797] [<ffffffff810cdcc9>] handle_irq_event_percpu+0xa9/0x220
[ 4163.037807] [<ffffffff810cde8e>] handle_irq_event+0x4e/0x80
[ 4163.037808] [<ffffffff810d0604>] handle_fasteoi_irq+0x64/0xf0
[ 4163.037811] [<ffffffff8100c252>] handle_irq+0x22/0x40
[ 4163.037813] [<ffffffff815f3d2a>] do_IRQ+0x5a/0xe0
[ 4163.037815] [<ffffffff815ea413>] common_interrupt+0x13/0x13
[ 4163.037816] <EOI> [<ffffffff813496cb>] ? intel_idle+0xcb/0x120
[ 4163.037820] [<ffffffff813496ad>] ? intel_idle+0xad/0x120
[ 4163.037823] [<ffffffff814ab062>] cpuidle_idle_call+0xa2/0x1d0
[ 4163.037826] [<ffffffff8100920b>] cpu_idle+0xab/0x100
[ 4163.037829] [<ffffffff815b803e>] rest_init+0x72/0x74
[ 4163.037831] [<ffffffff81ad0c2b>] start_kernel+0x3d4/0x3df
[ 4163.037834] [<ffffffff81ad0388>] x86_64_start_reservations+0x132/0x136
[ 4163.037836] [<ffffffff81ad0140>] ? early_idt_handlers+0x140/0x140
[ 4163.037838] [<ffffffff81ad0459>] x86_64_start_kernel+0xcd/0xdc
[ 4163.037839] handlers:
[ 4163.037847] [<ffffffffa0040aa0>] rtl8169_interrupt
[ 4163.037848] Disabling IRQ #18

I'm running an i5-2500k with a Z68 chipset. If more logs or troubleshooting will help, I'm happy to provide what I can.

[lynix (lynix47)]

Same problem here on an ASUS P8P67 EVO Rev 3, i5-2500k:

irq 16: nobody cared (try booting with the "irqpoll" option)
Pid: 0, comm: swapper Tainted: P C 3.1.6-1-ck #1
Call Trace:
 <IRQ> [<ffffffff810bbcf6>] __report_bad_irq+0x36/0xe0
 [<ffffffff810bbfac>] note_interrupt+0x15c/0x210
 [<ffffffff810b9e89>] handle_irq_event_percpu+0xc9/0x2a0
 [<ffffffff810848e6>] ? do_timer+0x2d6/0x500
 [<ffffffff810ba0a8>] handle_irq_event+0x48/0x70
 [<ffffffff810bc8da>] handle_fasteoi_irq+0x5a/0xe0
 [<ffffffff81016992>] handle_irq+0x22/0x40
 [<ffffffff814095da>] do_IRQ+0x5a/0xe0
 [<ffffffff8140622e>] common_interrupt+0x6e/0x6e
 <EOI> [<ffffffff81275f3b>] ? intel_idle+0xcb/0x120
 [<ffffffff81275f1d>] ? intel_idle+0xad/0x120
 [<ffffffff81319916>] cpuidle_idle_call+0xc6/0x350
 [<ffffffff81013229>] cpu_idle+0xc9/0x120
 [<ffffffff813e2d62>] rest_init+0x96/0xa4
 [<ffffffff8194ec15>] start_kernel+0x3bf/0x3cc
 [<ffffffff8194e347>] x86_64_start_reservations+0x132/0x136
 [<ffffffff8194e140>] ? early_idt_handlers+0x140/0x140
 [<ffffffff8194e44d>] x86_64_start_kernel+0x102/0x111
handlers:
[<ffffffffa03d37a0>] rtl8169_interrupt
[<ffffffffa0b895d0>] nv_kern_isr
Disabling IRQ #16

Running kernel-3.1.6-1 on x86_64. The problem also slows down my eth0 to about 600k/s - quite annoying.

[mbabcock (babcockm)]

I am running 2 systems using the i7 2600 CPU with the Z68 chip set. Specifically the P8Z68-V Pro mother board. I had been running 6G of memory in each system but changed the configuration after reading this bug report to 8G on 1 and 4G on the other. I am running Ubuntu 10.04.3 LTS 64bit on both systems. Both are behaving the same as the others listed above. They have extremely high latency and very slow file transfers. I am running Intel Pro/1000 GT network cards.

dmesg output:

[ 163.595546] irq 18: nobody cared (try booting with the "irqpoll" option)
[ 163.595552] Pid: 0, comm: swapper Not tainted 2.6.32-37-generic #81-Ubuntu
[ 163.595554] Call Trace:
[ 163.595556] <IRQ> [<ffffffff810c6c1b>] __report_bad_irq+0x2b/0xa0
[ 163.595567] [<ffffffff810c6e1c>] note_interrupt+0x18c/0x1d0
[ 163.595571] [<ffffffff810c751d>] handle_fasteoi_irq+0xdd/0x100
[ 163.595575] [<ffffffff81014d12>] handle_irq+0x22/0x30
[ 163.595580] [<ffffffff8154804c>] do_IRQ+0x6c/0xf0
[ 163.595583] [<ffffffff81012b13>] ret_from_intr+0x0/0x11
[ 163.595585] <EOI> [<ffffffff81311055>] ? acpi_idle_enter_bm+0x294/0x2c8
[ 163.595594] [<ffffffff8131104e>] ? acpi_idle_enter_bm+0x28d/0x2c8
[ 163.595599] [<ffffffff8143c207>] ? cpuidle_idle_call+0xa7/0x140
[ 163.595604] [<ffffffff81010e53>] ? cpu_idle+0xb3/0x110
[ 163.595608] [<ffffffff8153cbf8>] ? start_secondary+0xa8/0xaa
[ 163.595610] handlers:
[ 163.595612] [<ffffffffa00389d0>] (e1000_intr+0x0/0x120 [e1000])
[ 163.595624] Disabling IRQ #18

If you require more information, log outputs, anything I can provide please ask.

[mbabcock (babcockm)]

I tried booting with the "irqpoll" option on 1 of the 2 systems. It's been almost 24 hours and the latency issues have not returned.

[Christian Vincenot (bigdugong)]

Same bug here in 12.10. Tried different kernels up to 3.7.0 but doesn't help. Also tested different nvidia driver series (304,310,313, and 319) and makes no difference. Kernel switches don't work either (irqpoll, acpi=off, pci=routeirq, etc). Used to work a bit better with Nouveau (i.e. the idle load was much lower and this IRQ handling error did not appear, but the system was still slow when working), but not anymore with the latest version (1:1.0.6+git20130315.a80785f7-0ubuntu0sarvatt~quantal), which produces exactly the same behavior as with the Nvidia driver.

It would be great if something could check this out since this bug has been around for 1.5 years now.

------------
[ 5.461204] Call Trace:
[ 5.461208] <IRQ> [<ffffffff810e975d>] __report_bad_irq+0x3d/0xe0
[ 5.461233] [<ffffffff810e9a64>] note_interrupt+0x1b4/0x200
[ 5.461243] [<ffffffff810e7237>] handle_irq_event_percpu+0xa7/0x1f0
[ 5.461250] [<ffffffff810e73ce>] handle_irq_event+0x4e/0x80
[ 5.461258] [<ffffffff810ea5da>] handle_fasteoi_irq+0x5a/0x100
[ 5.461268] [<ffffffff81016712>] handle_irq+0x22/0x40
[ 5.461278] [<ffffffff816bad1a>] do_IRQ+0x5a/0xe0
[ 5.461286] [<ffffffff816b0cad>] common_interrupt+0x6d/0x6d
[ 5.461289] <EOI> [<ffffffff810a84f2>] ? ktime_get+0x52/0xe0
[ 5.461309] [<ffffffff813a425d>] ? intel_idle+0xed/0x150
[ 5.461316] [<ffffffff813a423e>] ? intel_idle+0xce/0x150
[ 5.461324] [<ffffffff8154bbf9>] cpuidle_enter+0x19/0x20
[ 5.461330] [<ffffffff8154c2c7>] cpuidle_idle_call+0xa7/0x260
[ 5.461338] [<ffffffff810efa05>] ? rcu_eqs_enter+0x65/0xa0
[ 5.461346] [<ffffffff8101d8cf>] cpu_idle+0xaf/0x120
[ 5.461356] [<ffffffff8167a372>] rest_init+0x72/0x80
[ 5.461365] [<ffffffff81cfebef>] start_kernel+0x3c7/0x3d4
[ 5.461372] [<ffffffff81cfe677>] ? do_early_param+0x91/0x91
[ 5.461379] [<ffffffff81cfe356>] x86_64_start_reservations+0x131/0x135
[ 5.461386] [<ffffffff81cfe45a>] x86_64_start_kernel+0x100/0x10f
[ 5.461389] handlers:
[ 5.461409] [<ffffffffa030c6f0>] ath_isr [ath9k]
[ 5.461554] [<ffffffffa095c9f0>] nv_kern_isr [nvidia]
[ 5.461559] Disabling IRQ #16

[thw24 (thw24)]

Face it: there will be no bug fix, really.
I had exactly the same problem for a long time (system slow, NIC fails/slow throughput after a few minutes).

SOLUTION:

1. change the PCI NIC to another slot so that it's not on the same interrupt with the nvidia (check with "cat /proc/interrupts")
--> system not slow anymore

2. change the PCI NIC with a PCIe NIC (no IRQ handling failures anymore)
--> stable network connection

That's it!
Have a beautiful day! :)

[Christian Vincenot (bigdugong)]

@thw24: Thanks for the suggestions. However, the system is running on a laptop, so these solutions are sadly not applicable here :)

[penalvch (penalvch)]

Michael Atkinson, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/843709/comments/22 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.