System Hangs With Kernel Migration Processes Consuming 100% CPU

Bug #1223055 reported by Andrew Piziali
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Once or twice a week, the system becomes non-responsive, with the mouse cursor tracking mouse movement but no keyboard response. Until today I would resort to using the kernel magic keys to reboot the system (R-E-I-S-U-B). Today I remotely logged in from another machine on the LAN and discovered that not only was the kernel alive and all processes running, but that the "migration/0" and "migration/1" processes were consuming 50% of the CPU each, as reported by top(1). I suspect this is why the system becomes non-responsive.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-generic 3.2.0.53.63
ProcVersionSignature: Ubuntu 3.2.0-53.81-generic 3.2.50
Uname: Linux 3.2.0-53-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: andy 2195 F.... pulseaudio
 /dev/snd/controlC0: andy 2195 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xee400000 irq 47'
   Mixer name : 'Analog Devices AD1981'
   Components : 'HDA:11d41981,17aa2025,00100200'
   Controls : 21
   Simple ctrls : 12
Card1.Amixer.info:
 Card hw:1 'U0x46d0x804'/'USB Device 0x46d:0x804 at usb-0000:00:1d.7-6.2.2, high speed'
   Mixer name : 'USB Mixer'
   Components : 'USB046d:0804'
   Controls : 2
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'Mic',0
   Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
   Capture channels: Mono
   Limits: Capture 0 - 6144
   Mono: Capture 4608 [75%] [24.00dB] [on]
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 79HT50WW-1.07'
   Mixer name : 'ThinkPad EC 79HT50WW-1.07'
   Components : ''
   Controls : 2
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
   Playback channels: Mono
   Limits: Playback 0 - 14
   Mono: Playback 7 [50%] [on]
Date: Mon Sep 9 16:56:22 2013
HibernationDevice: RESUME=UUID=5301c707-e227-46f3-8b49-a319582091a4
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: LENOVO 8743CTO
MarkForUpload: True
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-53-generic root=UUID=a9ba509e-76a3-4c03-b898-0409f24233eb ro quiet splash nomodeset vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-53-generic N/A
 linux-backports-modules-3.2.0-53-generic N/A
 linux-firmware 1.79.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/05/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 7IET32WW (1.13 )
dmi.board.name: 8743CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7IET32WW(1.13):bd02/05/2008:svnLENOVO:pn8743CTO:pvrThinkPadT60:rvnLENOVO:rn8743CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 8743CTO
dmi.product.version: ThinkPad T60
dmi.sys.vendor: LENOVO

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of the introduction of a regression, and when this regression was introduced. If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem.

Changed in linux (Ubuntu):
importance: Undecided → High
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.11 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-saucy/

tags: added: kernel-da-key
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

Joseph, to answer your question regarding when the issue appeared, it has been something I have tolerated for a long time (> 6 mo) so it probably appeared after an Ubuntu update, but I cannot pinpoint which one.

Regarding testing the latest upstream kernel, yes, I believe I can test v3.11 but we'll need to allow one or two weeks of daily system use to see if the migration/[01] process issue is resolved. I'll keep you posted.

Thanks.

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

Okay, I am running v3.11 so I'll report any subsequent hangs between now and September 23, 2013.

       $ uname -a
       Linux elijah 3.11.0-031100-generic #201309021735 SMP Mon Sep 2 21:44:40 UTC 2013 i686 i686 i386 GNU/Linux
       $

Thanks.

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

Today (September 15 ,2013, 1830 CDT) this Ubuntu 12.10 system running the 3.11 kernel hung as described above. Adding tag "kernel-bug-exists-upstream."

tags: added: kernel-bug-exists-upstream
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

The 3.12-rc1 kernel was just released. Can you also test this kernel to see if it also exhibits the bug:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc1-saucy/

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

Joseph, I am a bit leery of running an RC kernel. Any chance of filesytsem corruption?

Thanks.

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

Joseph, I installed the three 3.12-rc1 kernel packages:

linux-headers-3.12.0-031200rc1_3.12.0-031200rc1.201309161735_all.deb
linux-image-3.12.0-031200rc1-generic_3.12.0-031200rc1.201309161735_i386.deb
linux-headers-3.12.0-031200rc1-generic_3.12.0-031200rc1.201309161735_i386.deb

but the installation failed with both an error ("kernel package linux-headers-3.12.0-031200rc1-generic is not supported") and missing firmware messages for the radeon module. Please see the attached log "Linux Kernel 3.12 Install Log" for the details.

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

You shouldn't have to install the linux-headers package, just the linux-image package.

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

What about the Radeon module missing firmware messages?

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

Joseph, I'd like to test the 3.12 kernel but need an answer to my question about the missing Radeon firmware messages (see 9/18/13 note above). Thanks!

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

I am following up on my 9/18/13 and 9/22/13 question. It is safe to run the 3.12rc kernel even though the installation reported many missing firmware warnings? The first few warnings from the installation log I posted above are:

W: Possible missing firmware /lib/firmware/radeon/CYPRESS_smc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/JUNIPER_smc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/REDWOOD_smc.bin for module radeon
...

Thank you.

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

I booted the 3.12rc kernel but discovered that All Settings -> Sound no longer recognizes my two attached USB headsets. It only reports the motherboard sound card (Thinkpad T60). These are the /var/log/syslog messages from attaching one of the headsets:

======================
Sep 26 15:41:32 elijah kernel: [ 247.272108] usb 2-1: new full-speed USB device number 5 using uhci_hcd
Sep 26 15:41:32 elijah kernel: [ 247.426322] usb 2-1: New USB device found, idVendor=0d8c, idProduct=0008
Sep 26 15:41:32 elijah kernel: [ 247.426329] usb 2-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
Sep 26 15:41:32 elijah kernel: [ 247.426333] usb 2-1: Product: C-Media USB Audio Device
Sep 26 15:41:32 elijah kernel: [ 247.435597] input: C-Media USB Audio Device as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.3/input/input16
Sep 26 15:41:32 elijah kernel: [ 247.436449] hid-generic 0003:0D8C:0008.0007: input,hidraw0: USB HID v1.00 Device [C-Media USB Audio Device ] on usb-0000:00:1d.0-1/input3
Sep 26 15:41:32 elijah mtp-probe: checking bus 2, device 5: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1"
Sep 26 15:41:32 elijah mtp-probe: bus: 2, device: 5 was not an MTP device
Sep 26 15:41:32 elijah kernel: [ 247.493985] snd_usb_audio: `-2' invalid for parameter `index'
======================

Perhaps the "`-2' invalid for parameter" is the cause. Therefore, in order to use my headsets, I rebooted back to the stock 3.2.0-52 kernel.

Next?

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

Joseph, I am now running the 3.2.0-54 kernel that was pushed out today:

$ uname -a
Linux elijah 3.2.0-54-generic #82-Ubuntu SMP Tue Sep 10 20:09:12 UTC 2013 i686 i686 i386 GNU/Linux

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

I had to reboot my system this morning for the same reason as described in the bug description: System became non-responsive as though the CPU was running at 100% or it was fielding thousands of interrupts. I am currently running the 3.2.0-54 kernel.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

It would be good to know if this is a regression. If it is, we could bisect to identify the commit that introduced this.

Can you test the 3.2 final kernel to see if it exhibits this bug:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-precise/

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

Will do. I will report results within two weeks, by October 14, 2013.

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

Kernel 3.2.0-030200-generic appears to hang just as frequently as the latest Ubuntu 12.10 kernel (3.2.0-54-generic). Hence, I suspect that, if this is a kernel bug, it was introduced before 3.2.0-030200-generic.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

The 3.12-rc5 kernel is now the current mainline kernel. Can you see if this kernel also exhibits the bug:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc5-saucy/

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

Will do!

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

The 3.12 kernel hung this morning, as in earlier instances. These are a few observations from a remote login (ssh) from another system on the LAN:

* No process was consuming an inordinate amount of CPU, unlike previous migration/0 and migration/1 processes
* No process or thread was doing any significant I/O
* When Alt-SysReq-K was pressed on the hung system, no response was observed. I expected all processes on the X server's virtual console to be killed.
* After a "shutdown -r -t10 now" was executed from the remote login, ps(1) revealed that the X server was in WCHAN "exit" and its STATUS was "Ds." The system did not reboot.
* Alt-SysReq-R, I, E, S, U, B rebooted the system

I am now running 3.2.0-55-generic until I receive further diagnosis instructions.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

To perform a bisect and identify the commit that introduced this, we need to find the last good kernel and first bad kernel. We now know 3.2 final has the bug. Can you also test the 3.1 final kernel to see if it has the bug:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.1-oneiric/

If it does, please test the 3.0 final kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.0-oneiric/

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

Joseph, I mailed "Benjamin Herrenschmidt <email address hidden>" an upstream bug report.

Regarding bisecting, I will run the 3.1 kernel for two weeks or until I observe the same failure. Thanks.

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

I have not received a reply from Benjamin Herrenschmidt so I opened kernel upstream bug report 63801 (https://bugzilla.kernel.org/show_bug.cgi?id=63801).

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

The system hung running the 3.1 final kernel so I reverted back to running the current stock Ubuntu kernel, 3.2.0-55-generic.

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

Whoops! I just realized that you wanted me to also test the 3.0 final kernel so I will boot that shortly.

Thanks.

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

Booted and running 3.0 final kernel. Will report success or failure during the next two weeks.

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

Running kernel 3.0.0-0300-generic this morning, the system hung like before: kworker/0 and kworker/1 processes each consuming about 15%, Xorg 35%. The Xorg process would not respond to signals 1, 15 or 9. I resorted to the magic key sequence R-E-I-S-U-B to reboot, running the current stock kernel, 3.2.0-55-generic.

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :
Download full text (3.6 KiB)

Running 3.2.0-55-generic, my system again hung this morning but the evidence is increasingly pointing to either the X server (Xorg) or the video device driver as the culprit.

As earlier, the keyboard became non-responsive (except the kernel magic keys) and the mouse nearly non-responsive, the mouse cursor moving in hesitant steps as the mouse was moved. I logged into the system from another machine on the LAN to examine the running processes. avconv was converting a video file (68% CPU), kworker/1:0 was consuming 62%, and Xorg 52% on this Intel Core2 T5500 dual core mobile CPU. Suspecting the X server from earlier observations, I examined its log file (/var/log/Xorg.0.log):

...
[ 41368.758] [mi] EQ overflowing. Additional events will be discarded until existing events are processed.
[ 41368.772]
Backtrace:
[ 41369.118] 0: /usr/bin/X (xorg_backtrace+0x37) [0xe3e837]
[ 41369.118] 1: /usr/bin/X (mieqEnqueue+0x223) [0xe1cb83]
[ 41369.118] 2: /usr/bin/X (0xcb6000+0x4ccd5) [0xd02cd5]
[ 41369.118] 3: /usr/bin/X (xf86PostMotionEventM+0xf9) [0xd43d99]
[ 41369.118] 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x40e000+0x3c3d) [0x411c3d]
[ 41369.118] 5: /usr/lib/xorg/modules/input/evdev_drv.so (0x40e000+0x524f) [0x41324f]
[ 41369.118] 6: /usr/bin/X (0xcb6000+0x78381) [0xd2e381]
[ 41369.118] 7: /usr/bin/X (0xcb6000+0x9fce8) [0xd55ce8]
[ 41369.118] 8: (vdso) (__kernel_sigreturn+0x0) [0x1cf400]
[ 41369.118] 9: /usr/bin/X (0xcb6000+0x18cad0) [0xe42ad0]
[ 41369.118] 10: (vdso) (__kernel_sigreturn+0x0) [0x1cf400]
[ 41369.118] 11: (vdso) (__kernel_vsyscall+0x2) [0x1cf416]
[ 41369.118] 12: /lib/i386-linux-gnu/libc.so.6 (ioctl+0x19) [0x85a949]
[ 41369.118] 13: /usr/lib/i386-linux-gnu/libdrm.so.2 (drmIoctl+0x34) [0x2b79a4]
[ 41369.118] 14: /usr/lib/i386-linux-gnu/libdrm.so.2 (drmCommandNone+0x31) [0x2ba431]
[ 41369.119] 15: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x47e000+0xa705e) [0x52505e]
[ 41369.119] 16: /usr/lib/xorg/modules/libexa.so (0x3f5000+0x51b8) [0x3fa1b8]
[ 41369.119] 17: /usr/lib/xorg/modules/libexa.so (0x3f5000+0x5614) [0x3fa614]
[ 41369.119] 18: /usr/lib/xorg/modules/libexa.so (0x3f5000+0x56c8) [0x3fa6c8]
[ 41369.119] 19: /usr/lib/xorg/modules/libexa.so (exaMoveOutPixmap+0x4c) [0x3f8e2c]
[ 41369.119] 20: /usr/lib/xorg/modules/libexa.so (0x3f5000+0x5511) [0x3fa511]
[ 41369.119] 21: /usr/lib/xorg/modules/libexa.so (0x3f5000+0xca1e) [0x401a1e]
[ 41369.119] 22: /usr/lib/xorg/modules/libexa.so (exaOffscreenAlloc+0x20c) [0x401c4c]
[ 41369.119] 23: /usr/lib/xorg/modules/libexa.so (0x3f5000+0x5a23) [0x3faa23]
[ 41369.119] 24: /usr/lib/xorg/modules/libexa.so (0x3f5000+0x61b2) [0x3fb1b2]
[ 41369.119] 25: /usr/lib/xorg/modules/libexa.so (0x3f5000+0x3d1f) [0x3f8d1f]
[ 41369.119] 26: /usr/lib/xorg/modules/libexa.so (0x3f5000+0xe4a1) [0x4034a1]
[ 41369.119] 27: /usr/lib/xorg/modules/libexa.so (0x3f5000+0xf092) [0x404092]
[ 41369.119] 28: /usr/bin/X (0xcb6000+0x10d40b) [0xdc340b]
[ 41369.119] 29: /usr/bin/X (CompositePicture+0x21e) [0xdb5efe]
[ 41369.119] 30: /usr/bin/X (0xcb6000+0x10538c) [0xdbb38c]
[ 41369.119] 31: /usr/bin/X (0xcb6000+0x1007f1) [0xdb67f1]
[ 41369.119] 32: /usr/bin/X (0xcb6000+0x3791d) [0xced91d]
[ 41369.119] 33: /usr/bin/X (0xcb6000+...

Read more...

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

Booted the current Ubuntu 12.10 kernel, 3.2.0-56-generic.

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

System hung again today but I was able to kill the X server (Xorg) with signal 3 (QUIT) by ssh-ing in from another machine on the LAN, running top(1) as root, and using the "k" command.

To recap the current status: running kernels 3.0.0 though the current Ubuntu 12.10 kernel, 3.2.0-56-generic, an undetermined condition causes the X server to cease responding to the keyboard and only respond to mouse movement in a hesitant fashion. Xorg may be killed by sending it a QUIT signal as root. The kernel magic keys may also be used to reboot the system (R-E-I-S-U-B).

There are repeatable video artifacts that may be demonstrated using a Thunderbird message composition window that may be related to this hang issue.

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

When the system hung this afternoon, I was able to recover control by killing the X server with a QUIT signal (3). However, when I logged back in from the display manager (LightDM), the color palette was messed up. Logging out and back did not resolve the problem. I finally power cycled the machine and all was well again.

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

I recovered from a system hang this morning with a "kill -SIGQUIT <X process ID>". The color palette is still fine.

How may I move this bug report to either Xorg or to the Radeon video driver?

Thanks.

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

When the system hung this afternoon, I was able to recover control by killing the X server with a QUIT signal (3). However, when I logged back in from the display manager (LightDM), the color palette was messed up. Logging out and back did not resolve the problem. I finally power cycled the machine and all was well again.

Joseph, I am still waiting to learn how to transfer this bug report to either the X server (Xorg) or to the Radeon video device driver.

Thanks!

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

This bug report ought to be transferred from "Linux Package" to either the X server or the Radeon video driver. The X server still hangs in a livelock-like fashion every three or four days, requiring a kill -QUIT to kill the server.

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

I am still having to kill the X server (kill -QUIT) ever other day or so because the GUI hangs, while awaiting instructions on how to move this bug report to the Xorg X server or the Radeon video device driver. Thank you.

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

I am still having to kill the X server (kill -QUIT) ever other day or so because the GUI hangs, while awaiting instructions on how to move this bug report to the Xorg X server or the Radeon video device driver. Thank you.

Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

I am still having to kill the X server (kill -QUIT) ever other day or so because the GUI hangs, while awaiting instructions on how to move this bug report to the Xorg X server or the Radeon video device driver. Thank you.

affects: linux (Ubuntu) → xorg (Ubuntu)
Changed in xorg (Ubuntu):
status: Incomplete → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xorg (Ubuntu):
status: New → Confirmed
Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

I have not seen this hang since I stopped using the direct rendering (DRI) of the ATI Mobility Radeon X1400 in this ThinkPad T60. I switched video drivers (now using the X.Org "radeon" driver) because the new external monitor I am using (ViewSonic VG2439m) would glitch, loose sync and scamble text) with the ATI driver I was using.

Revision history for this message
Kenneth Loafman (kenneth-loafman) wrote :

root@stealth:~# uname -a
Linux stealth 3.13.0-44-generic #73-Ubuntu SMP Tue Dec 16 00:22:43 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

The bug appears to be related directly to the number of processes. I have 4 processors and 16GB of memory and normally only hit this problem when I have greater than 1024 processes running (Chrome, Eclipse, VMware w/3 VMs). I can recover from the problem if I am patient and shutdown the 3 VMs, Chrome, and Eclipse, all heavy thread users. migration/x goes away and the system returns to normal.

Is there a way to turn off migration in Ubuntu?

Revision history for this message
penalvch (penalvch) wrote :

Andrew Piziali, is this still an issue for you?

no longer affects: linux-kernel-64 (Ubuntu)
tags: added: bios-outdated-1.19
Changed in xorg (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Andrew Piziali (bj7u6139zdy-andy) wrote :

No. I have not seen this failure during the last eight weeks where, as mentioned earlier, I am no longer using the direct rendering function of my video card.

Revision history for this message
Kenneth Loafman (kenneth-loafman) wrote :

I do not believe that this bug is isolatable to zorg. I have seen this bug at least weekly and I'm keeping my 12.04 system up-to-date. I can sometimes get around the problem by killing off tasks, starting with Chrome and Eclipse, that use a lot of threads, but that takes a lot of patience. I'd like some help finding the cause if that is possible. This is very annoying!

Again I ask, is there a way to turn off migrations? It seems to do no good.

Changed in xorg (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Andrew Piziali, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1223055/comments/55 regarding this is no longer an issue for you. 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.

Kenneth Loafman, please file a new report via a terminal:
ubuntu-bug xorg

Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

Also, please feel free to subscribe me to it.

Changed in xorg (Ubuntu):
importance: High → Undecided
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.