Bug#528682: xserver-xorg-video-radeon: Combination of X11/testing and kernel 2.6.26 freezes (at least) screen and input

2009-05-14 Thread Julien Cristau
retitle 528682 Combination of X11/testing and kernel 2.6.29 freezes (at least) 
screen and input
kthxbye

Hi,

does installing the firmware-linux package make this go away?

Cheers,
Julien



-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Processed: Re: Bug#528682: xserver-xorg-video-radeon: Combination of X11/testing and kernel 2.6.26 freezes (at least) screen and input

2009-05-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> retitle 528682 Combination of X11/testing and kernel 2.6.29 freezes (at 
> least) screen and input
Bug#528682: xserver-xorg-video-radeon: Combination of X11/testing and kernel 
2.6.26 freezes (at least) screen and input
Changed Bug title to `Combination of X11/testing and kernel 2.6.29 freezes (at 
least) screen and input' from `xserver-xorg-video-radeon: Combination of 
X11/testing and kernel 2.6.26 freezes (at least) screen and input'.

> kthxbye
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#528682: xserver-xorg-video-radeon: Combination of X11/testing and kernel 2.6.26 freezes (at least) screen and input

2009-05-14 Thread stefan schwarzer
Package: xserver-xorg-video-radeon
Version: 1:6.9.0-1+lenny4
Severity: important


Hi there,
I am following testing on a Fujitsu/Siemens Lifebook E8010 with Radeon graphics 
(Radeon 9600 M10).
A recent package upgrade (must have been the last 2-3 days, May 12 or later) 
causes 
at least the graphics/input of my system to freeze with linux kernels 2.6.29-1 
and 2.6.29-2. 
I cannot easily test login/ping via network, so I cannot tell whether the 
kernel is still 
alive; however there is nothing in the messages file that would point to a 
crash (stack trace, e.g.). The freeze does not occur when running kernel 
2.6.26 (where I'm typing this message). 

The freeze happens systematically about 1-2 seconds after kdm comes up (could 
thus also be caused
by kde/qt4.2??). My xorg.conf is really quite basic apart from one line 
specifiying 
AGPMode 1 which has worked fine so far

The server log looks unsuspicious on first sight, but it seems that something
concerning dri is different for the two kernels (I can't tell if it is 
important or not). 
Below is a diff between a log from the freeze with kernel 2.6.26-2 against the 
current log.

I'd be interested in pointers to resolve the problem, because I'd like to use 
the later kernel. 
My notebook will not hibernate with 2.6.26 ...

Thanks a lot - 


nbkms11-l:/home/sts# diff /var/log/Xorg.0.log /var/log/Xorg.0.log.old
6c6
< Current Operating System: Linux nbkms11-l 2.6.26-1-686 #1 SMP Fri Mar 13 
18:08:45 UTC 2009 i686
---
> Current Operating System: Linux nbkms11-l 2.6.29-2-686 #1 SMP Sun May 3 
> 12:46:00 UTC 2009 i686
15c15
< (==) Log file: "/var/log/Xorg.0.log", Time: Thu May 14 18:22:41 2009
---
> (==) Log file: "/var/log/Xorg.0.log", Time: Thu May 14 18:20:26 2009
116a117,118
> (II) Bus 2 prefetchable memory range:
>   [0] -1  0   0x8800 - 0x93ff (0xc00) MX[B]
123a126,127
> (II) Bus 3 prefetchable memory range:
>   [0] -1  0   0x8800 - 0x8bff (0x400) MX[B]
128a133,134
> (II) Bus 4 prefetchable memory range:
>   [0] -1  0   0x8c00 - 0x8fff (0x400) MX[B]
133a140,141
> (II) Bus 8 prefetchable memory range:
>   [0] -1  0   0x9000 - 0x93ff (0x400) MX[B]
154c162
<   [7] -1  0   0x8800 - 0x880003ff (0x400) MX[B]
---
>   [7] -1  0   0x9400 - 0x940003ff (0x400) MX[B]
181c189
<   [7] -1  0   0x8800 - 0x880003ff (0x400) MX[B]
---
>   [7] -1  0   0x9400 - 0x940003ff (0x400) MX[B]
219c227
<   [11] -1 0   0x8800 - 0x880003ff (0x400) MX[B]
---
>   [11] -1 0   0x9400 - 0x940003ff (0x400) MX[B]
482c490
<   [11] -1 0   0x8800 - 0x880003ff (0x400) MX[B]
---
>   [11] -1 0   0x9400 - 0x940003ff (0x400) MX[B]
515c523
<   [11] -1 0   0x8800 - 0x880003ff (0x400) MX[B]
---
>   [11] -1 0   0x9400 - 0x940003ff (0x400) MX[B]
726c734
<   [13] -1 0   0x8800 - 0x880003ff (0x400) MX[B]
---
>   [13] -1 0   0x9400 - 0x940003ff (0x400) MX[B]
798c806
< (II) RADEON(0): [agp] Ring mapped at 0xb7763000
---
> (II) RADEON(0): [agp] Ring mapped at 0xb77f4000
800c808
< (II) RADEON(0): [agp] Ring read ptr mapped at 0xb7762000
---
> (II) RADEON(0): [agp] Ring read ptr mapped at 0xb77f3000
802c810
< (II) RADEON(0): [agp] Vertex/indirect buffers mapped at 0xb349b000
---
> (II) RADEON(0): [agp] Vertex/indirect buffers mapped at 0xb352c000
804,805c812,813
< (II) RADEON(0): [agp] GART Texture map mapped at 0xb2fbb000
< (II) RADEON(0): [drm] register handle = 0xc010
---
> (II) RADEON(0): [agp] GART Texture map mapped at 0xb304c000
> (II) RADEON(0): [drm] register handle = 0x2802
821,831c829,832
< (II) RADEON(0): [drm] Added 32 65536 byte vertex/indirect buffers
< (II) RADEON(0): [drm] Mapped 32 vertex/indirect buffers
< (II) RADEON(0): [drm] dma control initialized, using IRQ 11
< (II) RADEON(0): [drm] Initialized kernel GART heap manager, 5111808
< (WW) RADEON(0): DRI init changed memory map, adjusting ...
< (WW) RADEON(0):   MC_FB_LOCATION  was: 0xcbffc800 is: 0xcbffc800
< (WW) RADEON(0):   MC_AGP_LOCATION was: 0xffc0 is: 0xd07fd000
< (II) RADEON(0): RADEONRestoreMemMapRegisters() :
< (II) RADEON(0):   MC_FB_LOCATION   : 0xcbffc800 0xcbffc800
< (II) RADEON(0):   MC_AGP_LOCATION  : 0xd07fd000
< (II) RADEON(0): Direct rendering enabled
---
> (II) RADEON(0): [drm] removed 1 reserved context for kernel
> (II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xf8124000 at 0xb78f5000
> (II) RADEON(0): [drm] Closed DRM master.
> (WW) RADEON(0): Direct rendering disabled
879,903c880,887
< drmOpenDevice: node name is /dev/dri/card0
< drmOpenDevice: open result is 9, (OK)
< drmOpenByBusid: Searching for BusID pci::01:00.0
< drmOpenDevice: node name is /dev/dri/card0
< drmOpenDevice: open result is 9, (OK)
< drmOpenByBusid: drmOpenMinor returns 9
< drmOpenByBusid: drmGetBusid reports pci::01:00.0
< (WW) AIGLX: 3D driver claims to not support visual 0x23
< (WW) AIGLX: 3D driver clai