Using fglrx my computer is brought to a full stop if I log into an account, switch to an other and log out

Bug #160658 reported by Jon Ramvi on 2007-11-07
2
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.22 (Ubuntu)
Medium
Unassigned

Bug Description

Using fglrx my computer is brought to a full stop if I log into an account, switch to an other and log out

Jon Ramvi (ramvi) wrote :

Ubuntu 7.10 and fglrx 8.42 that is

Jon Ramvi (ramvi) wrote :

But I don't know for a fact that fglrx is the problem, maybe I should try reproducing the bug using the vesa driver...

Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux-restricted-modules-2.6.22 which provides the fglrx driver.

Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. What exactly do you mean by a full stop? Is there anything in '/var/log/syslog*' or '/var/log/Xorg.0.log*' pertaining to this crash? Thanks in advance.

Changed in linux-restricted-modules-2.6.22:
assignee: nobody → brian-murray
status: New → Incomplete
Jon Ramvi (ramvi) wrote :

Seems to be an fglrx bug:

Dec 8 06:50:29 ramvi -- MARK --
Dec 8 07:09:01 ramvi /USR/SBIN/CRON[12364]: (root) CMD ( [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -r -0 rm)
Dec 8 07:17:01 ramvi /USR/SBIN/CRON[12434]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Dec 8 07:30:01 ramvi /USR/SBIN/CRON[13115]: (root) CMD (test -x /etc/init.d/anacron && /usr/sbin/invoke-rc.d anacron start >/dev/null)
Dec 8 07:30:02 ramvi anacron[13140]: Anacron 2.3 started on 2007-12-08
Dec 8 07:30:02 ramvi anacron[13140]: Normal exit (0 jobs run)
Dec 8 07:39:01 ramvi /USR/SBIN/CRON[13925]: (root) CMD ( [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -r -0 rm)
Dec 8 07:50:29 ramvi -- MARK --
Dec 8 07:53:34 ramvi gnome-power-manager: (ramvi) Interaktiv utlogging for GNOME fordi av/på-knappen ble trykket på
Dec 8 07:53:50 ramvi gdmgreeter[17544]: WARNING: Theme broken: must have pam-message label!
Dec 8 07:54:04 ramvi gnome-power-manager: (marie) Strømstyring is already running in this session.
Dec 8 07:54:26 ramvi gnome-power-manager: (marie) Interaktiv utlogging for GNOME fordi av/på-knappen ble trykket på
Dec 8 07:54:48 ramvi gnome-power-manager: (marie) Interaktiv utlogging for GNOME fordi av/på-knappen ble trykket på
Dec 8 07:54:52 ramvi kernel: [ 9879.272000] [fglrx:firegl_lock_free] *ERROR* lock was not held by 4! (*lock=0x80000001)
Dec 8 07:54:52 ramvi kernel: [ 9879.272000] [fglrx:firegl_unlock] *ERROR* firegl_lock_free failed!
Dec 8 07:57:04 ramvi syslogd 1.4.1#21ubuntu3: restart.

Changed in linux-restricted-modules-2.6.22:
assignee: brian-murray → ubuntu-kernel-team
importance: Undecided → Medium
status: Incomplete → Confirmed
Bryce Harrington (bryce) wrote :

[This is an automated message]

As of Intrepid (8.10), we have a dedicated package 'fglrx-installer' for fglrx bugs, which now includes a process for upstreaming bugs to AMD.

  http://bugs.launchpad.net/ubuntu/+source/fglrx-installer

To transition your bug into the new fglrx-package, we need your help. Please do the following:

 a. Verify the bug occurs in Intrepid.
     (Intrepid ISOs: http://cdimage.ubuntu.com)
 b. If you haven't already, please include in the bug:
     * Your /var/log/Xorg.0.log
     * The output of `lspci -vvnn`
     * Steps to reproduce the issue
 c. Click 'Also affects distribution'
 d. Set 'Source Package Name' to 'fglrx-installer'
 e. Click Continue

Thank you. This will assist us in reviewing and upstreaming your fglrx bug, as appropriate.

[We'll expire the fglrx bugs in l-r-m-* in a month or so.]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux-restricted-modules-2.6.22 (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers