[Ubuntu-x-swat] [Bug 1046326] Re: Ubuntu Slow, crash, sluggish from version 10.04 upwards on i3/i5/i7 machines
It is mindblowing how nobody reacts to these things. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1046326 Title: Ubuntu Slow, crash, sluggish from version 10.04 upwards on i3/i5/i7 machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1046326/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1046326] [NEW] Ubuntu Slow, crash, sluggish from version 10.04 upwards on i3/i5/i7 machines
Public bug reported: This is an attempt to get proper attention to the massive amounts of people stuggling with ubuntu freezing at random, or becoming very slow or sluggish. ( https://bugs.launchpad.net/ubuntu/+source/xserver-xorg- video-intel/+bug/993187 ) Developers won't work on it because the problem is not given enough detail. This is however a severe issue. Here's my info gathered so far: Ubuntu will at random points suddenly become very slow and sluggish. graphics run far behind, keyboard strokes take multiple seconds to show, graphics are updated in super slowmo mode, or if you're unlucky; the system dies completely. This is related to a problem with the interrupt handling. On my own machine (MSI i7, nvidia card, 16 Gb, 5 sata HDD's) I have had this problem from 10.04 (when I bough the hware) up to 12.04. I have since upgraded up to kernel 3.5.3 with varying results. Some suggestions in posts make the periods between crashes shorter, some days it works fine, some days it happens every five minutes, but it NEVER goes away. If you consider this is interrupt related, that makes perfect sense. Every single 'crash' is marked by an unanswered interrupt. See below syslog: Sep 5 15:13:14 Server kernel: [112195.631364] irq 16: nobody cared (try booting with the irqpoll option) Sep 5 15:13:14 Server kernel: [112195.631368] Pid: 17901, comm: firefox Tainted: P O 3.5.3-030503-generic #201208252335 Sep 5 15:13:14 Server kernel: [112195.631369] Call Trace: Sep 5 15:13:14 Server kernel: [112195.631370] IRQ [810e5a5d] __report_bad_irq+0x3d/0xe0 Sep 5 15:13:14 Server kernel: [112195.631378] [810e5ce5] note_interrupt+0x135/0x190 Sep 5 15:13:14 Server kernel: [112195.631380] [810e3559] handle_irq_event_percpu+0xa9/0x210 Sep 5 15:13:14 Server kernel: [112195.631382] [810e370e] handle_irq_event+0x4e/0x80 Sep 5 15:13:14 Server kernel: [112195.631384] [810e6874] handle_fasteoi_irq+0x64/0x120 Sep 5 15:13:14 Server kernel: [112195.631388] [81016632] handle_irq+0x22/0x40 Sep 5 15:13:14 Server kernel: [112195.631391] [816a49ea] do_IRQ+0x5a/0xe0 Sep 5 15:13:14 Server kernel: [112195.631394] [8169a86a] common_interrupt+0x6a/0x6a Sep 5 15:13:14 Server kernel: [112195.631395] EOI [816a2c2d] ? system_call_fastpath+0x1a/0x1f Sep 5 15:13:14 Server kernel: [112195.631398] handlers: Sep 5 15:13:14 Server kernel: [112195.631401] [814bc670] usb_hcd_irq Sep 5 15:13:14 Server kernel: [112195.631462] [a0d65cb0] nv_kern_isr [nvidia] Sep 5 15:13:14 Server kernel: [112195.631470] [a00640f0] rhine_interrupt [via_rhine] Sep 5 15:13:14 Server kernel: [112195.631471] Disabling IRQ #16 The problem is massively compounded by the fact that irqpoll and irqfixup options NO LONGER WORK AT ALL ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/855199https://bugs.launchpad.net/ubuntu/+source/linux/+bug/855199 ). No matter if you switch to Nouveau, diff kernel, or other drivers, the problem remains is varying severity. Again; logical if there is a problem with the kernel interrupt handling itself. So here's the kicker. It is easy to resolve! By forcing a restart of the interrupt handlers the system INSTANTLY comes back to 100% functional life: root@Server:~# service network-manager restart My theory (for what it's worth; I have programmed assembly for 40 years) is that there is a multi-threading fault somewhere, which causes the kernel to miss an interrupt, or to miss allocating it. There is truly no point in uploading hardware specs and/or software config to this bug. There are litteraly thousands of different configs experiencing the same issue. The one thing they have in common though: Shared interrupts (usually 16) and LOAD on that interrupt (USB (KB+MS), VGA, ETH) on high speed machines. I strongly urge the kernel people to accept responsibility for this one. The problem is getting very much out of hand because it seems to get worse as CPU power increases. And more and more people are increasing to I7 etc Hence the massive flood of problems. I have created a keyboard shortcut that does the service restart and this works perfectly 100% of the time. If any dev needs more info, contact me. I hope this gets some very VERY high level attentions VERY soon. This is extremely damaging to Linux in general. Michael ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-bug -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1046326 Title: Ubuntu Slow, crash, sluggish from version 10.04 upwards on i3/i5/i7 machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1046326/+subscriptions ___ Mailing
[Ubuntu-x-swat] [Bug 1046326] Re: Ubuntu Slow, crash, sluggish from version 10.04 upwards on i3/i5/i7 machines
** Description changed: This is an attempt to get proper attention to the massive amounts of people stuggling with ubuntu freezing at random, or becoming very slow or sluggish. ( https://bugs.launchpad.net/ubuntu/+source/xserver-xorg- video-intel/+bug/993187 ) Developers won't work on it because the problem is not given enough detail. This is however a severe issue. Here's my info gathered so far: Ubuntu will at random points suddenly become very slow and sluggish. graphics run far behind, keyboard strokes take multiple seconds to show, graphics are updated in super slowmo mode, or if you're unlucky; the system dies completely. This is related to a problem with the interrupt handling. On my own machine (MSI i7, nvidia card, 16 Gb, 5 sata HDD's) I have had this problem from 10.04 (when I bough the hware) up to 12.04. I have since - upgraded up to kernel 3.5.3 with varying results. Some suggestions in - posts make the periods between crashes shorter, some days it works fine, - some days it happens every five minutes, but it NEVER goes away. + upgraded up to various kernels up to 3.5.3 with varying results. Some of + the suggestions in posts make the periods between crashes shorter, some + days it works fine, some days it happens every five minutes, but it + NEVER goes away. If you consider this is interrupt related, that makes perfect sense. Every single 'crash' is marked by an unanswered interrupt. See below syslog: Sep 5 15:13:14 Server kernel: [112195.631364] irq 16: nobody cared (try booting with the irqpoll option) Sep 5 15:13:14 Server kernel: [112195.631368] Pid: 17901, comm: firefox Tainted: P O 3.5.3-030503-generic #201208252335 Sep 5 15:13:14 Server kernel: [112195.631369] Call Trace: Sep 5 15:13:14 Server kernel: [112195.631370] IRQ [810e5a5d] __report_bad_irq+0x3d/0xe0 Sep 5 15:13:14 Server kernel: [112195.631378] [810e5ce5] note_interrupt+0x135/0x190 Sep 5 15:13:14 Server kernel: [112195.631380] [810e3559] handle_irq_event_percpu+0xa9/0x210 Sep 5 15:13:14 Server kernel: [112195.631382] [810e370e] handle_irq_event+0x4e/0x80 Sep 5 15:13:14 Server kernel: [112195.631384] [810e6874] handle_fasteoi_irq+0x64/0x120 Sep 5 15:13:14 Server kernel: [112195.631388] [81016632] handle_irq+0x22/0x40 Sep 5 15:13:14 Server kernel: [112195.631391] [816a49ea] do_IRQ+0x5a/0xe0 Sep 5 15:13:14 Server kernel: [112195.631394] [8169a86a] common_interrupt+0x6a/0x6a Sep 5 15:13:14 Server kernel: [112195.631395] EOI [816a2c2d] ? system_call_fastpath+0x1a/0x1f Sep 5 15:13:14 Server kernel: [112195.631398] handlers: Sep 5 15:13:14 Server kernel: [112195.631401] [814bc670] usb_hcd_irq Sep 5 15:13:14 Server kernel: [112195.631462] [a0d65cb0] nv_kern_isr [nvidia] Sep 5 15:13:14 Server kernel: [112195.631470] [a00640f0] rhine_interrupt [via_rhine] Sep 5 15:13:14 Server kernel: [112195.631471] Disabling IRQ #16 - - The problem is massively compounded by the fact that irqpoll and irqfixup options NO LONGER WORK AT ALL ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/855199https://bugs.launchpad.net/ubuntu/+source/linux/+bug/855199 ). + The problem is massively compounded by the fact that irqpoll and + irqfixup options NO LONGER WORK AT ALL ( + https://bugs.launchpad.net/ubuntu/+source/linux/+bug/855199 ). No matter if you switch to Nouveau, diff kernel, or other drivers, the problem remains is varying severity. Again; logical if there is a problem with the kernel interrupt handling itself. So here's the kicker. It is easy to resolve! By forcing a restart of the interrupt handlers the system INSTANTLY comes back to 100% functional life: root@Server:~# service network-manager restart My theory (for what it's worth; I have programmed assembly for 40 years) is that there is a multi-threading fault somewhere, which causes the kernel to miss an interrupt, or to miss allocating it. There is truly no point in uploading hardware specs and/or software config to this bug. There are litteraly thousands of different configs experiencing the same issue. The one thing they have in common though: Shared interrupts (usually 16) and LOAD on that interrupt (USB (KB+MS), VGA, ETH) on high speed machines. I strongly urge the kernel people to accept responsibility for this one. The problem is getting very much out of hand because it seems to get worse as CPU power increases. And more and more people are increasing to I7 etc Hence the massive flood of problems. I have created a keyboard shortcut that does the service restart and this works perfectly 100% of the time. If any dev needs more info, contact me. I hope this gets some very VERY high level attentions VERY soon. This is extremely damaging to Linux in general. Michael **
