Fred Flinnstone, thank you for reporting this and helping make Ubuntu better. 
Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If
so, could you please test for this with the latest development release
of Ubuntu? ISO CD images are available from
http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications->Accessories->Terminal), as it will automatically gather
and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following 
https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional 
upstream developers to examine the issue. Please do not test the kernel in the 
daily folder, but the one all the way at the bottom. Once you've tested the 
upstream kernel, please comment on which kernel version specifically you tested 
and remove the tag:
needs-upstream-testing

This can be done by clicking on the yellow pencil icon next to the tag located 
at the bottom of the bug description and deleting the text:
needs-upstream-testing

If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why 
specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Tips:
https://help.ubuntu.com/community/ReportingBugs

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

-- 
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/766408

Title:
  [sandybridge-gt2] GPU lockup using xvmc (Render IPEHR: 0x02000004)

Status in X.org xf86-video-intel:
  Unknown
Status in “linux” package in Ubuntu:
  Incomplete
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-video-intel

  I've started vdr-sxfe with video driver xvmc. After first start the
  screen gone on and off a couple of times, after half a minute crash.
  After second start the pc locked up, only hard reset helped.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: xserver-xorg-video-intel 2:2.14.0-4ubuntu7
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  Architecture: amd64
  Chipset: sandybridge-gt2
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  DRM.card0.DP.1:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.DP.2:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.DP.3:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.HDMI.A.1:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.HDMI.A.2:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.HDMI.A.3:
   status: connected
   enabled: enabled
   dpms: On
   modes: 1920x1080 1280x1024 1280x720 1024x768 800x600 640x480
   edid-base64: 
AP///////wBN2QFcAQEBAQESAQOAoFp4Cg3JoFdHmCcSSEwhCACBgAEBAQEBAQEBAQEBAQEBAjqAGHE4LUBYLEUAQIRjAAAeAR0AclHQHiBuKFUAQIRjAAAeAAAA/ABTT05ZIFRWIFhWCiAgAAAA/QAwPg5GDwAKICAgICAgAeQCAytwUB8QFAUTBBIRFhUDAgcGASAjCQcHgwEAAGYDDAAwAIDjBQMB4gA5AjqA0HI4LUAQLEWAQIRjAAAeAR0AvFLQHiC4KFVAQIRjAAAeAR2AGHEcFiBYLCUAQIRjAACeAR2A0HIcFiAQLCWAQIRjAACeAAAAAAAAAAAAAAAAqg==
  DRM.card0.VGA.1:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  Date: Tue Apr 19 19:35:47 2011
  DistUpgraded: Log time: 2011-04-16 16:36:13.524659
  DistroCodename: natty
  DistroVariant: ubuntu
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0112] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Giga-byte Technology Device [1458:d000]
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
  IntelGpuDump: Error: command ['intel_gpu_dump'] failed with exit code 1: 
Couldn't map MMIO region: No such file or directory
  InterpreterPath: /usr/bin/python2.7
  MachineType: Gigabyte Technology Co., Ltd. H67A-UD3H-B3
  ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic 
root=UUID=c7658c2a-257e-4c97-888e-d8e869de86e8 ro quiet splash vt.handoff=7
  ProcKernelCmdLine_: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic 
root=UUID=c7658c2a-257e-4c97-888e-d8e869de86e8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg             1:7.6+4ubuntu3
   libdrm2                  2.4.23-1ubuntu6
   xserver-xorg-video-intel 2:2.14.0-4ubuntu7
  Renderer: Unknown
  SourcePackage: xserver-xorg-video-intel
  Title: [sandybridge-gt2] GPU lockup
  UpgradeStatus: Upgraded to natty on 2011-04-16 (3 days ago)
  UserGroups:
   
  dmi.bios.date: 02/11/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: H67A-UD3H-B3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd02/11/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67A-UD3H-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67A-UD3H-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H67A-UD3H-B3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu12
  version.libdrm2: libdrm2 2.4.23-1ubuntu6
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu1
  version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110107+b795ca6e-0ubuntu7

  [lspci]
  00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor 
Family DRAM Controller [8086:0100] (rev 09)
        Capabilities: [88] Subsystem: Giga-byte Technology Device [1458:5000]
  00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation 
Core Processor Family Integrated Graphics Controller [8086:0112] (rev 09) 
(prog-if 00 [VGA controller])
        Subsystem: Giga-byte Technology Device [1458:d000]

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/766408/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to