Ubuntu
xserver-xorg-driver-ati package

  1. Bug #30447
  2. Comment #129

Comment 129 for bug 30447

Revision history for this message
emil_p8 (emile-visual) wrote : Re: Lockup problems with both the free xorg ATI driver and the proprietary fglrx driver, using various ATI cards

Well i tried to monitor via ssh. This is the output of sudo cat /proc/kmsg
:

succesful shutdown:

elena@deepthought:~$ sudo cat /proc/kmsg
Password:
<6>[17179708.412000] [fglrx] total GART = 67108864
<6>[17179708.412000] [fglrx] free GART = 51118080
<6>[17179708.412000] [fglrx] max single GART = 51118080
<6>[17179708.412000] [fglrx] total LFB = 128905216
<6>[17179708.412000] [fglrx] free LFB = 122613760
<6>[17179708.412000] [fglrx] max single LFB = 122613760
<6>[17179708.412000] [fglrx] total Inv = 0
<6>[17179708.412000] [fglrx] free Inv = 0
<6>[17179708.412000] [fglrx] max single Inv = 0
<6>[17179708.412000] [fglrx] total TIM = 0

Broadcast message from root@deepthought (Mon Nov 27 19:04:05 2006):

The system is going down for reboot NOW!
<5>[17179714.820000] apm: disabled on user request.
Connection to 10.0.0.7 closed by remote host.
Connection to 10.0.0.7 closed.

shutdown when it locks:

elena@deepthought:~$ sudo cat /proc/kmsg
Password:
<6>[17179644.604000] [fglrx] total GART = 67108864
<6>[17179644.604000] [fglrx] free GART = 51118080
<6>[17179644.604000] [fglrx] max single GART = 51118080
<6>[17179644.604000] [fglrx] total LFB = 128905216
<6>[17179644.604000] [fglrx] free LFB = 122613760
<6>[17179644.604000] [fglrx] max single LFB = 122613760
<6>[17179644.604000] [fglrx] total Inv = 0
<6>[17179644.604000] [fglrx] free Inv = 0
<6>[17179644.604000] [fglrx] max single Inv = 0
<6>[17179644.604000] [fglrx] total TIM = 0

And then ssh locks. Output seems the same.
BTW, the above is on dapper because I reverted to it (clean install) on this machine, but the problem remained.
Otherwise, i forgot to mention that on edgy, when in X i have no access to a virtual tty (ctrl+alt+Fx), it appears completely garbled, but accepts "blind" input. No such problem in dapper.
It seems to me that this problem appeared after this famous hi-panic xorg dapper upgrade which broke many ubuntus, but now i forgot to test this before patching my new dapper install.
Last thing, in dapper swithching to a console and rebooting from there never caused any problems