[Touch-packages] [Bug 1290775] Re: X freeze, garbled output, "*ERROR* Failed to schedule IB" on RV635/M86 (Radeon HD3650) and RV620

2015-11-23 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1290775

Title:
  X freeze, garbled output, "*ERROR* Failed to schedule IB" on RV635/M86
  (Radeon HD3650) and RV620

Status in xorg package in Ubuntu:
  Expired

Bug description:
  On two different computers stragnge display errors are encountered.

  Machine A is a laptop:
  uname: Linux x 3.11.0-18-generic #32-Ubuntu SMP Tue Feb 18 21:11:14 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux
  /proc/cmdline: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic root=UUID=... ro 
quiet splash vt.handoff=7

  Machine B is desktop PC:
  uname: Linux x 3.11.0-18-generic #32-Ubuntu SMP Tue Feb 18 21:11:14 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux
  /proc/cmdline: root=/dev/mapper/somelv ro quiet splash

  Both machines are running Ubuntu 13.10, with frequent updates (say, at least 
or more than once a week).
  Both are running xserver-xorg-video-ati 1:7.2.0-0ubuntu10, neither has 
installed anything with fglrx nor catalyst in package name.

  On B (desktop PC), display was occasionaly garbled with small artefacts (like 
few pixel lines of random dots), and occasionally screen freezes, than goes 
blank for a second, then works normaly again for some time - but after 3-4 such 
cycles, display permanently freezes. Restarting lightdm through one of VT 
consoles helped. Some applications, like firefox, caused these problems to be 
more frequent.  
  Then, as machine was frequently updated in hope of a fix, this changed, but 
to worse. Screen went completely garbled, mouse pointer turned to large square 
full of random noise, but underlying applications were probably running. VT 
consoles also went garbled and hard to use. Both DVI outputs were affected.

  On A machine display is mostly blank (though BIOS and GRUP screens are 
presented OK), sometimes graphical greeter (logon screen) is displayed, 
sometimes not. Bu in either case machine freezes and no logon is possible.
  Sometimes SysRq keys are working to reboot can be done, sometimes not.
  As this machine is equiped with swithchable graphics, when other GPU (Intel, 
integrated) is used display is presented ok.

  Machine A lshw extract:
  description: Notebook
  product: 20553AG ()
  vendor: LENOVO
  version: ThinkPad T500
  ...
 *-display
  description: VGA compatible controller
  product: RV635/M86 [Mobility Radeon HD 3650]
  vendor: Advanced Micro Devices, Inc. [AMD/ATI]
  physical id: 0
  bus info: pci@:01:00.0
  version: 00
  width: 32 bits
  clock: 33MHz
  capabilities: pm pciexpress msi vga_controller bus_master 
cap_list rom
  configuration: driver=radeon latency=0
  resources: irq:48 memory:d000-dfff 
ioport:2000(size=256) memory:cfff-cfff memory:cff0-cff1

  Machine A dmesg extract:
  ...
  [0.881667] [drm] radeon kernel modesetting enabled.
  [0.881891] [drm] initializing kernel modesetting (RV635 0x1002:0x9591 
0x17AA:0x2117).
  [0.881913] [drm] register mmio base: 0xCFFF
  [0.881914] [drm] register mmio size: 65536
  [0.882003] ATOM BIOS: M86M
  [0.882021] radeon :01:00.0: VRAM: 256M 0x - 
0x0FFF (256M used)
  [0.882023] radeon :01:00.0: GTT: 512M 0x1000 - 
0x2FFF
  [0.882025] [drm] Detected VRAM RAM=256M, BAR=256M
  [0.882026] [drm] RAM width 128bits DDR
  [0.882059] [TTM] Zone  kernel: Available graphics memory: 1988596 kiB
  [0.882061] [TTM] Initializing pool allocator
  [0.882064] [TTM] Initializing DMA pool allocator
  [0.882081] [drm] radeon: 256M of VRAM memory ready
  [0.882082] [drm] radeon: 512M of GTT memory ready.
  [0.882093] [drm] GART: num cpu pages 131072, num gpu pages 131072
  [0.887931] [drm] Loading RV635 Microcode
  [0.888799] [drm] PCIE GART of 512M enabled (table at 0x0004).
  [0.48] radeon :01:00.0: WB enabled
  [0.50] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x1c00 and cpu addr 0x880150118c00
  [0.52] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x1c0c and cpu addr 0x880150118c0c
  [0.54] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
  [0.56] [drm] Driver supports precise vblank timestamp query.
  [0.79] radeon :01:00.0: irq 48 for MSI/MSI-X
  [0.89] radeon :01:00.0: radeon: using MSI.
  [0.888912] [drm] radeon: irq initialized.
  [0.920625] [drm] ring test on 0 succeeded in 1 usecs
  [0.920683] [drm] ring test on 

[Touch-packages] [Bug 1290775] Re: X freeze, garbled output, "*ERROR* Failed to schedule IB" on RV635/M86 (Radeon HD3650) and RV620

2015-09-24 Thread Christopher M. Penalver
Darko S, thank you for taking the time to report this bug and helping to make 
Ubuntu better. Please execute the following command, as it will automatically 
gather debugging information, in a terminal:
apport-collect 1290775

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

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Package changed: xserver-xorg-video-ati (Ubuntu) => xorg (Ubuntu)

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1290775

Title:
  X freeze, garbled output, "*ERROR* Failed to schedule IB" on RV635/M86
  (Radeon HD3650) and RV620

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  On two different computers stragnge display errors are encountered.

  Machine A is a laptop:
  uname: Linux x 3.11.0-18-generic #32-Ubuntu SMP Tue Feb 18 21:11:14 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux
  /proc/cmdline: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic root=UUID=... ro 
quiet splash vt.handoff=7

  Machine B is desktop PC:
  uname: Linux x 3.11.0-18-generic #32-Ubuntu SMP Tue Feb 18 21:11:14 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux
  /proc/cmdline: root=/dev/mapper/somelv ro quiet splash

  Both machines are running Ubuntu 13.10, with frequent updates (say, at least 
or more than once a week).
  Both are running xserver-xorg-video-ati 1:7.2.0-0ubuntu10, neither has 
installed anything with fglrx nor catalyst in package name.

  On B (desktop PC), display was occasionaly garbled with small artefacts (like 
few pixel lines of random dots), and occasionally screen freezes, than goes 
blank for a second, then works normaly again for some time - but after 3-4 such 
cycles, display permanently freezes. Restarting lightdm through one of VT 
consoles helped. Some applications, like firefox, caused these problems to be 
more frequent.  
  Then, as machine was frequently updated in hope of a fix, this changed, but 
to worse. Screen went completely garbled, mouse pointer turned to large square 
full of random noise, but underlying applications were probably running. VT 
consoles also went garbled and hard to use. Both DVI outputs were affected.

  On A machine display is mostly blank (though BIOS and GRUP screens are 
presented OK), sometimes graphical greeter (logon screen) is displayed, 
sometimes not. Bu in either case machine freezes and no logon is possible.
  Sometimes SysRq keys are working to reboot can be done, sometimes not.
  As this machine is equiped with swithchable graphics, when other GPU (Intel, 
integrated) is used display is presented ok.

  Machine A lshw extract:
  description: Notebook
  product: 20553AG ()
  vendor: LENOVO
  version: ThinkPad T500
  ...
 *-display
  description: VGA compatible controller
  product: RV635/M86 [Mobility Radeon HD 3650]
  vendor: Advanced Micro Devices, Inc. [AMD/ATI]
  physical id: 0
  bus info: pci@:01:00.0
  version: 00
  width: 32 bits
  clock: 33MHz
  capabilities: pm pciexpress msi vga_controller bus_master 
cap_list rom
  configuration: driver=radeon latency=0
  resources: irq:48 memory:d000-dfff 
ioport:2000(size=256) memory:cfff-cfff memory:cff0-cff1

  Machine A dmesg extract:
  ...
  [0.881667] [drm] radeon kernel modesetting enabled.
  [0.881891] [drm] initializing kernel modesetting (RV635 0x1002:0x9591 
0x17AA:0x2117).
  [0.881913] [drm] register mmio base: 0xCFFF
  [0.881914] [drm] register mmio size: 65536
  [0.882003] ATOM BIOS: M86M
  [0.882021] radeon :01:00.0: VRAM: 256M 0x - 
0x0FFF (256M used)
  [0.882023] radeon :01:00.0: GTT: 512M 0x1000 - 
0x2FFF
  [0.882025] [drm] Detected VRAM RAM=256M, BAR=256M
  [0.882026] [drm] RAM width 128bits DDR
  [0.882059] [TTM] Zone  kernel: Available graphics memory: 1988596 kiB
  [0.882061] [TTM] Initializing pool allocator
  [0.882064] [TTM] Initializing DMA pool allocator
  [0.882081] [drm] radeon: 256M of VRAM memory ready
  [0.882082] [drm] radeon: 512M of GTT memory ready.
  [0.882093] [drm] GART: num cpu pages 131072, num gpu pages 131072
  [0.887931] [drm] Loading RV635 Microcode
  [0.888799] [drm] PCIE GART of 512M enabled (table at 0x0004).
  [0.48] radeon :01:00.0: WB enabled
  [0.50] radeon :01:00.0: fence d