[Kernel-packages] [Bug 1188647] Re: Please change intel_pstate default to disable
I'm posting here because pstate is giving me problems as well, but in the opposite direction. Upon bootup and for several hours thereafter, scaling works correctly. But after a period of time something happens (which is of course not mentioned in any log) and scaling_max_freq is set to scaling_min_freq and cannot be changed at all. root@ossy:/etc# cd /sys/devices/system/cpu/cpu0/cpufreq root@ossy:/sys/devices/system/cpu/cpu0/cpufreq# ls affected_cpus cpuinfo_transition_latency scaling_driver scaling_setspeed cpuinfo_cur_freq related_cpus scaling_governor cpuinfo_max_freq scaling_available_governors scaling_max_freq cpuinfo_min_freq scaling_cur_freq scaling_min_freq root@ossy:/sys/devices/system/cpu/cpu0/cpufreq# cat scaling_max_freq 160 root@ossy:/sys/devices/system/cpu/cpu0/cpufreq# cat cpuinfo_max_freq 370 root@ossy:/sys/devices/system/cpu/cpu0/cpufreq# cat cpuinfo_max_freq > scaling_max_freq root@ossy:/sys/devices/system/cpu/cpu0/cpufreq# cat scaling_max_freq 160 root@ossy:/sys/devices/system/cpu/cpu0/cpufreq# echo performance > scaling_governor root@ossy:/sys/devices/system/cpu/cpu0/cpufreq# cat scaling_governor performance root@ossy:/sys/devices/system/cpu/cpu0/cpufreq# cat cpuinfo_max_freq > scaling_max_freq root@ossy:/sys/devices/system/cpu/cpu0/cpufreq# cat scaling_max_freq 160 This happens whether or not I have Enhanced SpeedStep enabled in my BIOS. (This is also not a BIOS limit problem.) Disabling pstate entirely allows me to run at 3.3GHz all the time. Since powerclamp is loaded and thermald is running I'm still protected from overheating situations. Since this is a desktop I don't really care about the power usage but I can see where this would be a bigger problem for laptops. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1188647 Title: Please change intel_pstate default to disable Status in linux package in Ubuntu: Fix Released Bug description: 3.9 introduced a new default governor on SandyBridge CPUs called INTEL_PSTATE which, when built in and enabled (the default), removes all other governors (like our usual default, ondemand). 3.10 extended this to Ivybridge generation CPUs. In theory, this isn't an awful thing, as the new Intel pstate governor should be higher performance and give better power savings. In theory. In practice, it drives my CPUs to max frequency nearly constantly, spins my fans like mad and, somehow, does all of this while also eating enough CPU time in kernel threads to make my machine choppy, unresponsive, and unable to do simple things like play videos when I get off work. Therefore, I propose that we, for now, toggle intel_pstate to disable by default (I am using intel_pstate=disable on my command line right now, with great success), so it's still built in, and people can play with it, but it's off by default. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.9.0-4-generic 3.9.0-4.9 ProcVersionSignature: Ubuntu 3.9.0-4.9-generic 3.9.4 Uname: Linux 3.9.0-4-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adconrad 2574 F pulseaudio CurrentDmesg: [ 30.633035] init: plymouth-stop pre-start process (2079) terminated with status 1 [ 36.086916] br0: port 1(eth0) entered forwarding state Date: Fri Jun 7 08:48:56 2013 HibernationDevice: RESUME=UUID=73040efa-baec-458a-8307-3bca07b26c3c InstallationDate: Installed on 2012-12-09 (179 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121209) MachineType: LENOVO 4173LPB MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-4-generic root=UUID=aad5-ef31-4428-973f-71740fc7cb6a ro intel_pstate=disable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.9.0-4-generic N/A linux-backports-modules-3.9.0-4-generic N/A linux-firmware 1.109 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 8CET55WW (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 4173LPB 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:bvr8CET55WW(1.35):bd09/13/2012:svnLENOVO:pn4173LPB:pvrThinkPadT420s:rvnLENOVO:rn4173LPB:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4173LPB dmi.product.version: ThinkPad T420s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1188
[Kernel-packages] [Bug 1188647] Re: Please change intel_pstate default to disable
I had looked at other relevant threads on askubuntu but I figured it was a kernel issue. I'll certainly work within the context of this bug to try to fix if possible. I'm on 4.9.0-15-generic but I just installed 4.10.0-041000rc6.201701291830 and will reply with results (after removing the line from /etc/default/grub to disable pstate). Relevant info from cpuinfo: vendor_id : GenuineIntel cpu family : 6 model : 42 model name : Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz stepping: 7 microcode : 0x29 cpu MHz : 3311.061 Threads (among many) that I saw on askubuntu http://askubuntu.com/questions/296653/ubuntu-13-04-cpu-frequency-scaling-stuck-on-lowest-frequency http://askubuntu.com/questions/353383/cpu-frequency-scaling-issue-scaling-max-freq-wrong -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1188647 Title: Please change intel_pstate default to disable Status in linux package in Ubuntu: Fix Released Bug description: 3.9 introduced a new default governor on SandyBridge CPUs called INTEL_PSTATE which, when built in and enabled (the default), removes all other governors (like our usual default, ondemand). 3.10 extended this to Ivybridge generation CPUs. In theory, this isn't an awful thing, as the new Intel pstate governor should be higher performance and give better power savings. In theory. In practice, it drives my CPUs to max frequency nearly constantly, spins my fans like mad and, somehow, does all of this while also eating enough CPU time in kernel threads to make my machine choppy, unresponsive, and unable to do simple things like play videos when I get off work. Therefore, I propose that we, for now, toggle intel_pstate to disable by default (I am using intel_pstate=disable on my command line right now, with great success), so it's still built in, and people can play with it, but it's off by default. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.9.0-4-generic 3.9.0-4.9 ProcVersionSignature: Ubuntu 3.9.0-4.9-generic 3.9.4 Uname: Linux 3.9.0-4-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adconrad 2574 F pulseaudio CurrentDmesg: [ 30.633035] init: plymouth-stop pre-start process (2079) terminated with status 1 [ 36.086916] br0: port 1(eth0) entered forwarding state Date: Fri Jun 7 08:48:56 2013 HibernationDevice: RESUME=UUID=73040efa-baec-458a-8307-3bca07b26c3c InstallationDate: Installed on 2012-12-09 (179 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121209) MachineType: LENOVO 4173LPB MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-4-generic root=UUID=aad5-ef31-4428-973f-71740fc7cb6a ro intel_pstate=disable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.9.0-4-generic N/A linux-backports-modules-3.9.0-4-generic N/A linux-firmware 1.109 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 8CET55WW (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 4173LPB 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:bvr8CET55WW(1.35):bd09/13/2012:svnLENOVO:pn4173LPB:pvrThinkPadT420s:rvnLENOVO:rn4173LPB:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4173LPB dmi.product.version: ThinkPad T420s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1188647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1188647] Re: Please change intel_pstate default to disable
Wow. I've never seen this before. My scaling_min_freq and scaling_max_freq are now set to... 0! root@ossy:/sys/devices/system/cpu/cpu0/cpufreq# ls -1 * affected_cpus cpuinfo_cur_freq cpuinfo_max_freq cpuinfo_min_freq cpuinfo_transition_latency related_cpus scaling_available_governors scaling_cur_freq scaling_driver scaling_governor scaling_max_freq scaling_min_freq scaling_setspeed root@ossy:/sys/devices/system/cpu/cpu0/cpufreq# cat * 0 1737414 370 160 4294967295 0 performance powersave 1737414 intel_pstate performance 0 0 root@ossy:/sys/devices/system/cpu/cpu0/cpufreq# uname -a Linux ossy 4.10.0-041000rc6-generic #201701291830 SMP Sun Jan 29 23:32:29 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux And now scaling_max_freq is stuck: root@ossy:/sys/devices/system/cpu/cpu0/cpufreq# cat cpuinfo_max_freq > scaling_max_freq root@ossy:/sys/devices/system/cpu/cpu0/cpufreq# cat scaling_max_freq 0 Inside of the intel_pstate folder, I can move max_perf_pct up to 44 max, and turn on turbo: root@ossy:/sys/devices/system/cpu/intel_pstate# ls -1 max_perf_pct min_perf_pct no_turbo num_pstates turbo_pct root@ossy:/sys/devices/system/cpu/intel_pstate# cat * 0 0 1 22 19 root@ossy:/sys/devices/system/cpu/intel_pstate# echo 40 > min_perf_pct root@ossy:/sys/devices/system/cpu/intel_pstate# cat min_perf_pct 0 root@ossy:/sys/devices/system/cpu/intel_pstate# echo 100 > max_perf_pct root@ossy:/sys/devices/system/cpu/intel_pstate# cat max_perf_pct 44 root@ossy:/sys/devices/system/cpu/intel_pstate# echo 0 > no_turbo root@ossy:/sys/devices/system/cpu/intel_pstate# cat no_turbo 0 root@ossy:/sys/devices/system/cpu/intel_pstate# echo 100 > max_perf_pct root@ossy:/sys/devices/system/cpu/intel_pstate# cat max_perf_pct 44 But I'm sure at some point later it will go down again and not go back up until I change things manually (or reboot). Not entirely sure when this happened. I had it running for over 12 hours (including a lot of load with BOINC projects overnight). It wasn't stuck like this in the morning, but at some point today it got into this state. Nothing strange I can see in my system log, except for maybe [13347.141990] powercap intel-rapl:0: package locked by BIOS, monitoring only But I don't think my BIOS is limiting anything because when I echo 1 > /sys/module/processor/parameters/ignore_ppc it doesn't make a difference, I still can't change any of the values (scaling_max_freq or max_perf_pct) that I want to get my original speed back, only rebooting helps. Anyway, if you don't think this is the right bug I can open another one or something, but unless you can suggest a patch to try or a setting to change I am probably just going to disable pstate on the GRUB command line and be done with it (and of course ensure thermald and powerclamp are running and my fans are in good shape and as dust-free as can be). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1188647 Title: Please change intel_pstate default to disable Status in linux package in Ubuntu: Fix Released Bug description: 3.9 introduced a new default governor on SandyBridge CPUs called INTEL_PSTATE which, when built in and enabled (the default), removes all other governors (like our usual default, ondemand). 3.10 extended this to Ivybridge generation CPUs. In theory, this isn't an awful thing, as the new Intel pstate governor should be higher performance and give better power savings. In theory. In practice, it drives my CPUs to max frequency nearly constantly, spins my fans like mad and, somehow, does all of this while also eating enough CPU time in kernel threads to make my machine choppy, unresponsive, and unable to do simple things like play videos when I get off work. Therefore, I propose that we, for now, toggle intel_pstate to disable by default (I am using intel_pstate=disable on my command line right now, with great success), so it's still built in, and people can play with it, but it's off by default. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.9.0-4-generic 3.9.0-4.9 ProcVersionSignature: Ubuntu 3.9.0-4.9-generic 3.9.4 Uname: Linux 3.9.0-4-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adconrad 2574 F pulseaudio CurrentDmesg: [ 30.633035] init: plymouth-stop pre-start process (2079) terminated with status 1 [ 36.086916] br0: port 1(eth0) entered forwarding state Date: Fri Jun 7 08:48:56 2013 HibernationDevice: RESUME=UUID=73040efa-baec-458a-8307-3bca07b26c3c InstallationDate: Installed on 2012-12-09 (179 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121209) MachineType: LENOVO 4173LPB MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-4-
[Kernel-packages] [Bug 1188647] Re: Please change intel_pstate default to disable
Ooh thanks for the grep trick I knew there was a better way. thermald may have something to do with it but I'm not getting the syslog spamming like that bug report, though I do have a couple of those entries listed. I will stop posting to this bug though. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1188647 Title: Please change intel_pstate default to disable Status in linux package in Ubuntu: Fix Released Bug description: 3.9 introduced a new default governor on SandyBridge CPUs called INTEL_PSTATE which, when built in and enabled (the default), removes all other governors (like our usual default, ondemand). 3.10 extended this to Ivybridge generation CPUs. In theory, this isn't an awful thing, as the new Intel pstate governor should be higher performance and give better power savings. In theory. In practice, it drives my CPUs to max frequency nearly constantly, spins my fans like mad and, somehow, does all of this while also eating enough CPU time in kernel threads to make my machine choppy, unresponsive, and unable to do simple things like play videos when I get off work. Therefore, I propose that we, for now, toggle intel_pstate to disable by default (I am using intel_pstate=disable on my command line right now, with great success), so it's still built in, and people can play with it, but it's off by default. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.9.0-4-generic 3.9.0-4.9 ProcVersionSignature: Ubuntu 3.9.0-4.9-generic 3.9.4 Uname: Linux 3.9.0-4-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adconrad 2574 F pulseaudio CurrentDmesg: [ 30.633035] init: plymouth-stop pre-start process (2079) terminated with status 1 [ 36.086916] br0: port 1(eth0) entered forwarding state Date: Fri Jun 7 08:48:56 2013 HibernationDevice: RESUME=UUID=73040efa-baec-458a-8307-3bca07b26c3c InstallationDate: Installed on 2012-12-09 (179 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121209) MachineType: LENOVO 4173LPB MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-4-generic root=UUID=aad5-ef31-4428-973f-71740fc7cb6a ro intel_pstate=disable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.9.0-4-generic N/A linux-backports-modules-3.9.0-4-generic N/A linux-firmware 1.109 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 8CET55WW (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 4173LPB 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:bvr8CET55WW(1.35):bd09/13/2012:svnLENOVO:pn4173LPB:pvrThinkPadT420s:rvnLENOVO:rn4173LPB:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4173LPB dmi.product.version: ThinkPad T420s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1188647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1293569] Re: iwlwifi-7260-8.ucode causes network disconnections problems
Is this patch in the most recent -30 kernel? If not when might it make it in? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1293569 Title: iwlwifi-7260-8.ucode causes network disconnections problems Status in “linux-firmware” package in Ubuntu: Confirmed Status in “linux-firmware” source package in Precise: Fix Released Status in “linux-firmware” source package in Trusty: Fix Released Bug description: Running 14.04 (beta) with Kernel 3.13.0-17-generic I've encountered a strange and reproducible error with the iwlwifi-7260-8.ucode firmware. This laptop is a Dell XPS 12 (haswell). With the -8 firmware, it will connect fine to wifi for 30 or 40 mins at a time, then will start dropping connections repeatedly. Even modprobe -r unloading and reloading doesn't fix the issue, only a reboot will temporarily solve it for 40 mins at a time. Moreover, here is what's strange, is during these episodes of disconnection it seems to affect the actual router (2Wire), as the other devices in the house will also start to have issues (very slow connections, limited range,etc). Once I reboot this laptop everything and all devices will return to normal. This issue has been fixed by me manually removing the -8 firware from /lib/firmware and letting the -7 firmware load instead. Since that has been done there has not been a single issue of this happening (now going on 4 days). let me know if there is any other information you would like me to provide. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-firmware 1.126 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 17 08:13:25 2014 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2014-03-07 (9 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140307) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1293569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1041790] Re: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0
I can also reproduce the bug using the new Google Maps (easiest way to do so seems to be zooming in/out). However it occurs for me even after I disable semaphores: root@hawty:~# cat /sys/module/i915/parameters/semaphores 0 (after that): [614445.590357] [drm:i915_hangcheck_elapsed] *ERROR* stuck on render ring [614445.590468] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x5268000 ctx 10) at 0x5268210 this is ubuntu 13.04 with 2.21.6-0ubuntu4 intel driver, but kernel 3.11.1. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1041790 Title: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 Status in X.org xf86-video-intel: Confirmed Status in “linux” package in Ubuntu: Confirmed Status in “sandybridge-meta” package in Ubuntu: Confirmed Status in “xserver-xorg-video-intel” package in Ubuntu: Triaged Bug description: X locks up periodically for a 2 to ten seconds at a time and this crash log gets generated. It's significantly more than several times a day but not quite continuous. Temporarily disabiling semaphores seems to eliminate the problem. E.g.: $ sudo -s # echo 0 > /sys/modules/i915/parameters/semaphores [Workaround] 1. Edit your /etc/default/grub file. 2. Change this line: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.semaphores=0" 3. Then run sudo update-grub 4. And reboot If you indeed have this bug, that should stop the lockups from happening. If it doesn't, then file a new bug report. Side Effects: Rendering throughput is dropped by 10% with SNA, or as much as 3x with UXA. OpenGL performance is likely to be reduced by about 30%. More CPU time is spent waiting for the GPU with rc6 disabled, so increased power consumption. [Original Report] ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 Uname: Linux 3.6.0-rc3-git-20120826.1015 x86_64 ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 Chipset: sandybridge-m-gt2 Date: Sun Aug 26 16:06:32 2012 DistroCodename: quantal DistroVariant: ubuntu DuplicateSignature: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 Ubuntu 12.10 EcryptfsInUse: Yes ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GpuHangFrequency: Continuously InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2) InterpreterPath: /usr/bin/python3.2mu MachineType: Dell Inc. Dell System XPS L502X ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.0-rc3-git-20120826.1015 root=UUID=135c8090-427c-460a-909d-eff262cd44b6 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu3 libdrm2 2.4.38-0ubuntu2 xserver-xorg-video-intel 2:2.20.3-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 UdevDb: Error: [Errno 2] No such file or directory: 'udevadm' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1041790] Re: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0
Sorry. :) Unfortunately/fortunately I can no longer reproduce it after doing a BIOS update on my ASUS motherboard (was about 18 months behind). Based on your description of the bug as possibly related to the BIOS I decided to do that update, and even though it's only been about 10 minutes of usage, I can't reproduce this in Google Maps at all, where it was sure to cause the bug. I'd certainly recommend that anyone having this issue investigate a BIOS upgrade. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1041790 Title: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 Status in X.org xf86-video-intel: Confirmed Status in “linux” package in Ubuntu: Confirmed Status in “sandybridge-meta” package in Ubuntu: Confirmed Status in “xserver-xorg-video-intel” package in Ubuntu: Triaged Bug description: X locks up periodically for a 2 to ten seconds at a time and this crash log gets generated. It's significantly more than several times a day but not quite continuous. Temporarily disabiling semaphores seems to eliminate the problem. E.g.: $ sudo -s # echo 0 > /sys/modules/i915/parameters/semaphores [Workaround] 1. Edit your /etc/default/grub file. 2. Change this line: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.semaphores=0" 3. Then run sudo update-grub 4. And reboot If you indeed have this bug, that should stop the lockups from happening. If it doesn't, then file a new bug report. Side Effects: Rendering throughput is dropped by 10% with SNA, or as much as 3x with UXA. OpenGL performance is likely to be reduced by about 30%. More CPU time is spent waiting for the GPU with rc6 disabled, so increased power consumption. [Original Report] ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 Uname: Linux 3.6.0-rc3-git-20120826.1015 x86_64 ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 Chipset: sandybridge-m-gt2 Date: Sun Aug 26 16:06:32 2012 DistroCodename: quantal DistroVariant: ubuntu DuplicateSignature: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 Ubuntu 12.10 EcryptfsInUse: Yes ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GpuHangFrequency: Continuously InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2) InterpreterPath: /usr/bin/python3.2mu MachineType: Dell Inc. Dell System XPS L502X ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.0-rc3-git-20120826.1015 root=UUID=135c8090-427c-460a-909d-eff262cd44b6 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu3 libdrm2 2.4.38-0ubuntu2 xserver-xorg-video-intel 2:2.20.3-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 UdevDb: Error: [Errno 2] No such file or directory: 'udevadm' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
