Ubuntu
fglrx-installer package

  1. Bug #118605
  2. Comment #72

Comment 72 for bug 118605

Revision history for this message
Andreas Modinos (blueturtl) wrote :

I can confirm this bug on a Compaq nx6125 laptop (AMD Turion64, generic kernel, Ati Xpress200M with fglrx driver).
OS: Ubuntu 8.04.1

I log in as user #1, then switch to user #2. If after this I log out user #2, the system will hang with a black screen. I am able to move the cursor, but otherwise the system is completely unresponsive. Switching to another terminal will not work, nor will trying to restart X (Ctrl+Alt+Backspace). I have to hold down the power button to restart.

I can provide the following information from my kernel log, it appears the fglrx driver is in trouble right before the lockup occurs:

Jul 3 10:19:19 creature kernel: [ 523.982813] [fglrx:firegl_lock] *ERROR* Process 7578 is using illegal context 0x00000005
Jul 3 10:20:30 creature kernel: [ 560.363705] [fglrx:fireglAsyncioIntEnableMsgHandler] *ERROR* IRQMGR returned error 1 when trying to enable interrupt source 20008000
Jul 3 10:20:30 creature kernel: [ 560.363714] [fglrx] Receive enable interrupt message with irqEnableMask: 20008000
Jul 3 10:24:13 creature kernel: [ 683.510810] [fglrx:fireglAsyncioIntEnableMsgHandler] *ERROR* IRQMGR returned error 1 when trying to enable interrupt source 20008000
Jul 3 10:24:13 creature kernel: [ 683.510819] [fglrx] Receive enable interrupt message with irqEnableMask: 20008000
Jul 3 10:27:39 creature kernel: [ 814.770094] [fglrx] interrupt source 20008000 successfully disabled!
Jul 3 10:27:39 creature kernel: [ 814.770100] [fglrx] enable ID = 0x00000001
Jul 3 10:27:39 creature kernel: [ 814.770103] [fglrx] Receive disable interrupt message with irqEnableMask: 20008000; dwIRQEnableId: 00000001
Jul 3 10:27:41 creature kernel: [ 816.871867] [fglrx:firegl_lock_free] *ERROR* lock was not held by 5! (*lock=0x80000001)
Jul 3 10:27:41 creature kernel: [ 816.871877] [fglrx:firegl_unlock] *ERROR* firegl_lock_free failed!

I checked to comments for a fix, but apparently they are already applied in the latest Hardy updates?
At least my /etc/ati/authatieventsd.sh seems to match the spesified changes a few posts back.