Bug#374986: xserver-xorg-video-ati: [2.6.17/radeon] Xserver and console dead, rt_sigaction looping, not killable

2007-06-20 Thread Robert Millan
On Tue, Jun 19, 2007 at 11:15:56PM +0200, Brice Goglin wrote:
 
 Hi,
 
 About a year ago, you reported (or replied to) a bug to the Debian BTS
 regarding the X server and console dying on a Radeon X800GTO board. Did
 you reproduce this problem recently? With Xorg/Etch? With latest
 xserver-xorg-core and drivers? If not, I will close this bug in the next
 weeks.

My card is an X300, but it seems to hit the same bug.  I haven't tried lately,
but will try again tomorrow after my exams.

Thank you

-- 
Robert Millan

My spam trap is [EMAIL PROTECTED]  Note: this address is only intended
for spam harvesters.  Writing to it will get you added to my black list.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#374986: xserver-xorg-video-ati: [2.6.17/radeon] Xserver and console dead, rt_sigaction looping, not killable

2007-06-19 Thread Eduard Bloch
#include hallo.h
* Brice Goglin [Tue, Jun 19 2007, 10:32:18PM]:
 Hi,
 
 About a year ago, you reported (or replied to) a bug to the Debian BTS
 regarding the X server and console dying on a Radeon X800GTO board. Did
 you reproduce this problem recently? With Xorg/Etch? With latest
 xserver-xorg-core and drivers? If not, I will close this bug in the next
 weeks.

The particular card has been replaced few weeks ago (because it sucked
and I got fed up with this ATI piece of crap), but with kernel
2.6.21rc... or so, the problem was still there.

Feel free to close if nobody else can reproduce it.

Regards,
Eduard.

-- 
XTaran .oO( Wer grummelt so spät durch Nacht und IRC... )
towo Es ist der Ganneff mit seiner HURD?
towo HURD, oh HURD, was birgst Du so bang Dein Gesicht?
Siehst, mein Ganneff, Du den madduck nicht?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#374986: xserver-xorg-video-ati: [2.6.17/radeon] Xserver and console dead, rt_sigaction looping, not killable

2007-06-19 Thread Brice Goglin
Hi,

About a year ago, you reported (or replied to) a bug to the Debian BTS
regarding the X server and console dying on a Radeon X800GTO board. Did
you reproduce this problem recently? With Xorg/Etch? With latest
xserver-xorg-core and drivers? If not, I will close this bug in the next
weeks.

Thanks,
Brice



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#374986: xserver-xorg-video-ati: [2.6.17/radeon] Xserver and console dead, rt_sigaction looping, not killable

2006-06-30 Thread Michel Dänzer
On Wed, 2006-06-28 at 10:26 +0200, Eduard Bloch wrote: 
 
 Without loading the DRI module, it works.

So the problem was avoided previously because the DRI wasn't supported
with your card yet. As you may have noticed in the log file, r300 DRI is
still considered experimental, but you can try the attached patch which
was recently merged in xf86-video-ati git upstream.


-- 
Earthling Michel Dänzer   |  http://tungstengraphics.com
Libre software enthusiast |  Debian, X and DRI developer

diff --git a/src/radeon_driver.c b/src/radeon_driver.c
index 2381831..149cb2e 100644
--- a/src/radeon_driver.c
+++ b/src/radeon_driver.c
@@ -133,6 +133,7 @@ static void RADEONInitDispBandwidth(Scrn
 static void RADEONGetMergedFBOptions(ScrnInfoPtr pScrn);
 static int RADEONValidateMergeModes(ScrnInfoPtr pScrn);
 static void RADEONSetDynamicClock(ScrnInfoPtr pScrn, int mode);
+static void RADEONForceSomeClocks(ScrnInfoPtr pScrn);
 static void RADEONUpdatePanelSize(ScrnInfoPtr pScrn);
 static void RADEONSaveMemMapRegisters(ScrnInfoPtr pScrn, RADEONSavePtr save);
 
@@ -5738,6 +5739,9 @@ #endif
 }
 }
 
+if ((!info-IsSecondary)  (IS_R300_VARIANT || IS_RV100_VARIANT))
+  RADEONForceSomeClocks(pScrn);
+
 if (info-allowColorTiling  (pScrn-virtualX  info-MaxSurfaceWidth)) {
 	xf86DrvMsg(pScrn-scrnIndex, X_INFO,
 		   Color tiling not supported with virtual x resolutions larger than %d, disabling\n,
@@ -9751,6 +9757,16 @@ RADEONGetMergedFBOptions(ScrnInfoPtr pSc
 }
 }
 
+static void RADEONForceSomeClocks(ScrnInfoPtr pScrn)
+{
+/* It appears from r300 and rv100 may need some clocks forced-on */
+ CARD32 tmp;
+
+ tmp = INPLL(pScrn, RADEON_SCLK_CNTL);
+ tmp |= RADEON_SCLK_FORCE_CP | RADEON_SCLK_FORCE_VIP;
+ OUTPLL(pScrn, RADEON_SCLK_CNTL, tmp);
+}
+
 static void RADEONSetDynamicClock(ScrnInfoPtr pScrn, int mode)
 {
 RADEONInfoPtr  info   = RADEONPTR(pScrn);


Bug#374986: xserver-xorg-video-ati: [2.6.17/radeon] Xserver and console dead, rt_sigaction looping, not killable

2006-06-28 Thread Eduard Bloch
#include hallo.h
* Michel Dänzer [Sat, Jun 24 2006, 02:14:13PM]:

  moment where it usualy changes the resolution the monitor goes off and
  the console seems to be dead. Keyboard does not react, not even magic
  sys-rq does work. I can login from remote but I cannot kill X any more.
  It hangs and eats 99% CPU power (displayed by top).
 
 If this is with the DRI enabled, does it also happen with it disabled?
 
 Please attach full X config and log files corresponding to the problem.

Without loading the DRI module, it works. I attach the Xorg and kernel
logs, this time with 2.6.17-mm1 kernel. The good thing, it does respond
to SysRQ, somehow. I can reset the keyboard mode and reboot cleanly.

The only thing I note by looking at the X log is that previosly it was
running over lots of /dev/dri/card* files and stoped at:

drmOpenDevice: node name is /dev/dri/card13
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card14
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
(EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM
[dri] Disabling DRI.

Yeah. And this time, we get:

drmOpenByBusid: Searching for BusID pci::02:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: drmOpenMinor returns 7
drmOpenByBusid: drmGetBusid reports pci::02:00.0
(II) RADEON(0): [dri] Found DRI library version 1.2.0 and kernel module version 
1.24.0

And the screen is black and strace log shows this looping over
unsuccessfull syscalls.

Eduard.

Eduard.


Xorg.0.log.old
Description: application/trash


Bug#374986: xserver-xorg-video-ati: [2.6.17/radeon] Xserver and console dead, rt_sigaction looping, not killable

2006-06-24 Thread Michel Dänzer
On Thu, 2006-06-22 at 15:44 +0200, Eduard Bloch wrote: 
 Package: xserver-xorg-video-ati
 Version: 1:6.5.8.0-1
 Severity: important
 
 Hello,
 
 my Radeon X800GTO,PCIe card does not work with kernel 2.6.17 anymore.
 With 2.6.16 there was no such problem. Now the driver gets up and in the
 moment where it usualy changes the resolution the monitor goes off and
 the console seems to be dead. Keyboard does not react, not even magic
 sys-rq does work. I can login from remote but I cannot kill X any more.
 It hangs and eats 99% CPU power (displayed by top).

If this is with the DRI enabled, does it also happen with it disabled?

Please attach full X config and log files corresponding to the problem.


 Unfortunately the VESA driver shows similar symptoms (it has failed
 already with 2.6.16), however I have not straced it yet. I believe that
 VESA has been working with Xorg 6.8 or 6.9 and kernel versions from
 those days.

That would be a separate bug then.


-- 
Earthling Michel Dänzer   |  http://tungstengraphics.com
Libre software enthusiast |  Debian, X and DRI developer




Bug#374986: xserver-xorg-video-ati: [2.6.17/radeon] Xserver and console dead, rt_sigaction looping, not killable

2006-06-22 Thread Eduard Bloch
Package: xserver-xorg-video-ati
Version: 1:6.5.8.0-1
Severity: important

Hello,

my Radeon X800GTO,PCIe card does not work with kernel 2.6.17 anymore.
With 2.6.16 there was no such problem. Now the driver gets up and in the
moment where it usualy changes the resolution the monitor goes off and
the console seems to be dead. Keyboard does not react, not even magic
sys-rq does work. I can login from remote but I cannot kill X any more.
It hangs and eats 99% CPU power (displayed by top).

Unfortunately the VESA driver shows similar symptoms (it has failed
already with 2.6.16), however I have not straced it yet. I believe that
VESA has been working with Xorg 6.8 or 6.9 and kernel versions from
those days.

Do you have any suggestions? Should I forward the issue to LKML?

Relevant strace log parts attached.

Eduard.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-amd64-k8
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages xserver-xorg-video-ati depends on:
ii  libc6 2.3.6-15   GNU C Library: Shared libraries
ii  xserver-xorg-core 1:1.0.2-8  X.Org X server -- core server

xserver-xorg-video-ati recommends no packages.

-- no debconf information

-- 


log_cut.bz2
Description: Binary data