[Desktop-packages] [Bug 1041790]

2013-09-08 Thread Dan Doel
I have, I think, a reliable way to trigger this behavior, if that helps.
It requires a non-trivial setup, though.

I have gnome-shell running on dual monitors. The first is 1920x1200, the
second is 1920x1080 (not sure if the resolution difference matters). If
I run a full-screen game on The 1920x1200 monitor, I get freezes, and
notes in the dmesg about hangcheck timers and kickrings (stuck wait on
blitter ring).

I believe OpenGL acceleration of the desktop is important, because the
freezes are not triggered in fluxbox, for instance. I'm not sure if the
game itself needs to be using OpenGL, or if the full-screen window is
the triggering factor, or something else entirely. It is important that
the game keep the monitors distinct, and only go full screen on one. I
just tried it on Battle for Wesnoth, and full screen there sets the
monitors to mirror, which doesn't trigger the problem.

This is on an i7 4770, if that matters.

I realize this is may be difficult to put together for a test setup, but
I thought I'd mention it.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1115308] [NEW] Chromium webapps block functionality of other Chromium windows

2013-02-04 Thread Dan Doel
Public bug reported:

The chromium webapp plugin seems to cause some odd locked down behavior
of other chromium windows. Steps to reproduce are as follows:

  1) Launch a webapp in chromium. GMail or Google+ cause this, at least, for 
reference.
  2) Open a normal chromium window

The second chromium window will now not function properly. Typing
anything into the omnibox and pressing enter will just clear the
omnibox, not navigate anywhere. And keyboard shortcuts to open new tabs
and jump to the omnibox (ctrl-t, ctrl-l) will not do anything.

Presumably this is due to the webapp plugin locking down chromium to act
like a stand-alone application, but it affects _all_ chromium windows
opened after a chromium webapp (at least), not just the webapp window.
The ill effects go away by closing all chromium windows.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: chromium-browser 24.0.1312.56-0ubuntu0.12.10.3
ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2
Uname: Linux 3.5.0-23-generic x86_64
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
Date: Mon Feb  4 09:55:18 2013
Desktop-Session:
 DESKTOP_SESSION = ubuntu
 XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg
 XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
InstallationDate: Installed on 2013-01-19 (15 days ago)
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
MarkForUpload: True
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
chromium-default: CHROMIUM_FLAGS=
gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'ubuntu-mono-dark\n'/desktop/gnome/interface/gtk_theme = b'Ambiance\n'

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug quantal running-unity

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1115308

Title:
  Chromium webapps block functionality of other Chromium windows

Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  The chromium webapp plugin seems to cause some odd locked down
  behavior of other chromium windows. Steps to reproduce are as follows:

1) Launch a webapp in chromium. GMail or Google+ cause this, at least, for 
reference.
2) Open a normal chromium window

  The second chromium window will now not function properly. Typing
  anything into the omnibox and pressing enter will just clear the
  omnibox, not navigate anywhere. And keyboard shortcuts to open new
  tabs and jump to the omnibox (ctrl-t, ctrl-l) will not do anything.

  Presumably this is due to the webapp plugin locking down chromium to
  act like a stand-alone application, but it affects _all_ chromium
  windows opened after a chromium webapp (at least), not just the webapp
  window. The ill effects go away by closing all chromium windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: chromium-browser 24.0.1312.56-0ubuntu0.12.10.3
  ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic x86_64
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  Date: Mon Feb  4 09:55:18 2013
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2013-01-19 (15 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme =