ATI Radeon HD 4650 randomly crashes with fglrx driver (in U 10.10 even more often - about each 15 minutes)

Bug #665863 reported by Jakub 'Livio' Rusinek
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
fglrx-installer (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I installed Kubuntu 10.10 in place of Ubuntu 10.04.

In 10.04 I experienced a lot of crashes while trying to play movies using XvBA through mplayer.
In 10.10 KDE desktop effects have been bringing it to crash even faster. Things started to get better after I had disabled them completely.

But absolutely calm my PC is when I use vesa driver. (opensource radeon is way too slow; I can't accept it).

fglrx I'm using is so-called 10.10. I remember using 10.4 or so on openSUSE 11.2 and then, or on 10.6 I started to see random crashes.

I'll show you a screenshot. (colours of vertical (always only vertical!) lines are random. sometimes instead of striped picture I get some "coloured tv-noise", which I haven't captured yet.)

freezes sometimes answer to Linux SysRq combinations and sometimes not.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: fglrx 2:8.780-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
NonfreeKernelModules: fglrx
Architecture: i386
Date: Sun Oct 24 13:24:39 2010
DkmsStatus: fglrx, 8.780, 2.6.35-22-generic, i686: installed
GdmLog:
 Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log'] failed with exit code 1: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
 QFileSystemWatcher: failed to add paths: /home/jakub/.config/ibus/bus
 Bus::open: Can not get ibus-daemon's address.
 IBusInputContext::createInputContext: no connection to ibus-daemon
 cat: /var/log/gdm/:0.log: No such file or directory
GdmLog1: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory
GdmLog2: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory
InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
Lsusb:
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=b18e69df-4e52-4953-927b-9fc28d38fc05 ro quiet splash
ProcEnviron:
 LANGUAGE=
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
SourcePackage: fglrx-installer
dmi.bios.date: 08/07/2006
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.80
dmi.board.name: K7VT4APro
dmi.board.version: 1.0x
dmi.chassis.asset.tag: 00000000
dmi.chassis.type: 3
dmi.chassis.version: X.XX
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd08/07/2006:svn:pnK7VT4APro:pvr1.0x:rvn:rnK7VT4APro:rvr1.0x:cvn:ct3:cvrX.XX:
dmi.product.name: K7VT4APro
dmi.product.version: 1.0x
glxinfo: Error: [Errno 2] No such file or directory
peripherals: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.35-22-generic

Revision history for this message
Jakub 'Livio' Rusinek (liviopl-pl) wrote :
Revision history for this message
Jakub 'Livio' Rusinek (liviopl-pl) wrote :

Oh, well. Screenshot doesn't show striped vertical screen I was talking about but the latter. My bad.

Revision history for this message
dazza5000 (darran-kelinske) wrote :

Possibly related to:

https://bugs.kde.org/show_bug.cgi?id=232213

Doing some more research.

Revision history for this message
Jakub 'Livio' Rusinek (liviopl-pl) wrote :

I see no relation. My bug is purely related to fglrx driver, and not even desktop effects of KWin. Not talking of Compiz, by the way ;) .

Bryce Harrington (bryce)
tags: added: kubuntu
Revision history for this message
Jakub 'Livio' Rusinek (liviopl-pl) wrote :

I tried everything I could and... Surprisingly changing CPU back to slower Duron helped. Not software issue, so closed as invalid.

Changed in fglrx-installer (Ubuntu):
status: New → Invalid
Revision history for this message
sam (sdoyle-2) wrote :

This is definitely a valid bug. I is happening to me as well. Using 2 ati radeon 4870 3 display (happens with 2 as well) opening up applications randomly causes crash and restart so I'm back at login

happens with xinerama enabled and disabled

applications that work: browser (firefox, chrome) nautilus, terminal windows update manager etc
applications that don't work: youtube, video, keeypassx (huh normal app) some other applications I have run work sometimes and don't others. The current state of the fglrx driver for 10.10 is extremely unstable.

Changed in fglrx-installer (Ubuntu):
status: Invalid → New
Revision history for this message
Jakub 'Livio' Rusinek (liviopl-pl) wrote :

When it comes to me, I could say "works for me". So the bug you want to file is not about the problem I describe. I don't really know what should I do here, so I simply unsubscribed.

Good luck resolving!

Revision history for this message
bugbot (bugbot) wrote :

Hey Jakub,

Hi, have you had a chance to test if this bug is still present in natty?

If it does (and if you're the original reporter), please boot into natty
and run the command:

  apport-collect <bug-number>

which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run this right after reproducing the problem.)

Changed in fglrx-installer (Ubuntu):
status: New → Incomplete
Revision history for this message
madbiologist (me-again) wrote :

Official support for Ubuntu 10.10 "Maverick Meerkat" has ended. If this problem is still occurring on Ubuntu 12.04.1 "Precise Pangolin" please open a new bug. (The good news is that the open source driver is a lot faster these days).

Changed in fglrx-installer (Ubuntu):
status: Incomplete → 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.