Bug#413463: xserver-xorg-video-ati: Crash on start with radeon driver

2007-03-28 Thread Sven Arvidsson
[ Follow up for bug 413463 ]

I have reproduced the crash with version 6.6.191-1, but I also figured
out what setting caused the crash:

Option MergedFB false

The above option seems to be the culprit, as removing it from xorg.conf
lets me start X as usual. 

The reason I added this option in the first place is because otherwise I
have no working Xv for video. (Only a black area where the video should
be).

I'm using a card with both VGA and DVI using a TFT monitor connected to
the VGA port. It seems like X fails to detect that I'm only using one
monitor, and thus gives me no Xv for the VGA port. I tried to fix this
by specifically setting MonitorLayout NONE, TDMS but it also seems
like my TFT monitor is detected as a CRT, as I needed to specify NONE,
CRT, otherwise I only get a black screen.

Should I file a separate bug about this?

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 760BDD22


signature.asc
Description: This is a digitally signed message part


Bug#413463: xserver-xorg-video-ati: Crash on start with radeon driver

2007-03-28 Thread Brice Goglin
forwarded 413463 https://bugs.freedesktop.org/show_bug.cgi?id=10442
thank you



Sven Arvidsson wrote:
 I have reproduced the crash with version 6.6.191-1, but I also figured
 out what setting caused the crash:
 Option MergedFB false
 The above option seems to be the culprit, as removing it from xorg.conf
 lets me start X as usual.

Looks like https://bugs.freedesktop.org/show_bug.cgi?id=10442
Option MergedFB off leads to segfault
It has been reported this morning.

 The reason I added this option in the first place is because otherwise I
 have no working Xv for video. (Only a black area where the video should
 be).

 I'm using a card with both VGA and DVI using a TFT monitor connected to
 the VGA port. It seems like X fails to detect that I'm only using one
 monitor, and thus gives me no Xv for the VGA port. I tried to fix this
 by specifically setting MonitorLayout NONE, TDMS but it also seems
 like my TFT monitor is detected as a CRT, as I needed to specify NONE,
 CRT, otherwise I only get a black screen.

 Should I file a separate bug about this?

Let's see what happens in this upstream bug first. We are close to the
6.7 release of the ATI driver, it's a good time to get such bugs fixed.
If you basically copy-paste all what you said above in the upstream bug,
they might tell you to file another bug, we'll see. Of course, feel free
to provide even more details, and to tell them to fix this bug before
releasing 6.7 :)

Brice



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



Processed: Re: Bug#413463: xserver-xorg-video-ati: Crash on start with radeon driver

2007-03-28 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 forwarded 413463 https://bugs.freedesktop.org/show_bug.cgi?id=10442
Bug#413463: xserver-xorg-video-ati: Crash on start with radeon driver
Forwarded-to-address changed from 
https://bugs.freedesktop.org/show_bug.cgi?id=10405 to 
https://bugs.freedesktop.org/show_bug.cgi?id=10442.

 thank you
Stopping processing here.

Please contact me if you need assistance.

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


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



Bug#413463: xserver-xorg-video-ati: Crash on start with radeon driver

2007-03-25 Thread Sven Arvidsson
Hi,

Any news on this yet? Should I report it directly to upstream instead?

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 760BDD22


signature.asc
Description: This is a digitally signed message part


Bug#413463: xserver-xorg-video-ati: Crash on start with radeon driver

2007-03-25 Thread Julien Cristau
On Sun, Mar 25, 2007 at 16:55:31 +0200, Sven Arvidsson wrote:

 Hi,
 
Hi Sven,

 Any news on this yet? Should I report it directly to upstream instead?
 
It would be best if you could do that, yes.

Thanks a lot,
Julien


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



Bug#413463: xserver-xorg-video-ati: Crash on start with radeon driver

2007-03-05 Thread Sven Arvidsson
Package: xserver-xorg-video-ati
Version: 1:6.6.3-5
Severity: normal

X crashes on start with the radeon driver:

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x84) [0x80c02f4]
1: [0xb7ef0420]
2: /usr/lib/xorg/modules/drivers//radeon_drv.so [0xb7b3d56f]
3: /usr/lib/xorg/modules/drivers//radeon_drv.so(RADEONPreInit+0xb99) 
[0xb7b405c9]
4: /usr/bin/X(InitOutput+0x9c4) [0x809ff54]
5: /usr/bin/X(main+0x27b) [0x806e35b]
6: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0xb7d08ea8]
7: /usr/bin/X(FontFileCompleteXLFD+0xa5) [0x806d8a1]

Fortunately, the vesa driver still works. I tried falling back to
xserver-xorg-core 1.2.0-5 and xserver-xorg-video-ati 6.6.3-4 but with
the same results.

I'm attaching the old log file where X crash, as the one picked up by
reportbug is with vesa.

-- Package-specific info:
Contents of /var/lib/x11/X.roster:
xserver-xorg

/etc/X11/X target unchanged from checksum in /var/lib/x11/X.md5sum.

X server symlink status:
lrwxrwxrwx 1 root root 13 2006-03-24 17:10 /etc/X11/X - /usr/bin/Xorg
-rwxr-xr-x 1 root root 1597708 2007-03-02 20:12 /usr/bin/Xorg

Contents of /var/lib/x11/xorg.conf.roster:
xserver-xorg

VGA-compatible devices on PCI bus:
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R200 QM [Radeon 
9100]

/etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum.

Xorg X server configuration file status:
-rw-r--r-- 1 root root 3526 2007-03-05 09:05 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type man /etc/X11/xorg.conf at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section Files
FontPath/usr/share/fonts/X11/misc
FontPath/usr/X11R6/lib/X11/fonts/misc
FontPath/usr/share/fonts/X11/cyrillic
FontPath/usr/X11R6/lib/X11/fonts/cyrillic
FontPath/usr/share/fonts/X11/100dpi/:unscaled
FontPath/usr/X11R6/lib/X11/fonts/100dpi/:unscaled
FontPath/usr/share/fonts/X11/75dpi/:unscaled
FontPath/usr/X11R6/lib/X11/fonts/75dpi/:unscaled
FontPath/usr/share/fonts/X11/Type1
FontPath/usr/X11R6/lib/X11/fonts/Type1
FontPath/usr/share/fonts/X11/100dpi
FontPath/usr/X11R6/lib/X11/fonts/100dpi
FontPath/usr/share/fonts/X11/75dpi
FontPath/usr/X11R6/lib/X11/fonts/75dpi
# path to defoma fonts
FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType
EndSection

Section Module
Loadbitmap
Loaddbe
Loadddc
#Load   dri
Loadextmod
Loadfreetype
Loadglx
Loadint10
Loadrecord
Loadtype1
Loadvbe
EndSection

Section Extensions
Option Composite Enable
EndSection

Section InputDevice
Identifier  Generic Keyboard
Driver  kbd
Option  CoreKeyboard
Option  XkbRules  xorg
Option  XkbModel  pc105
Option  XkbLayout se
Option  XkbOptionsctrl:nocaps
EndSection

Section InputDevice
Identifier  Configured Mouse
Driver  mouse
Option  CorePointer
Option  Device/dev/input/mice
Option  Protocol  ExplorerPS/2
Option  Emulate3Buttons   true
EndSection

Section Device
Identifier  ATI Technologies, Inc. Radeon R200 QM [Radeon 9100]
Driver  ati
BusID   PCI:1:0:0
Option  UseFBDev  false
Option  AGPMode 4
#Option AGPFastWrite  on
Option  MergedFB false
#Option MonitorLayout TMDS, NONE
#Option EnablePageFliptrue
Option  XAANoOffscreenPixmaps true
EndSection

Section Monitor
Identifier  CMC 17
Option  DPMS
HorizSync   30-82
VertRefresh 56-76
EndSection

Section Screen
Identifier  Default Screen
Device  ATI Technologies, Inc. Radeon R200 QM [Radeon 9100]
Monitor CMC 17
DefaultDepth24
SubSection Display
Depth   1
Modes   1280x1024 1152x864 1024x768 800x600 
640x480
EndSubSection
SubSection 

Bug#413463: xserver-xorg-video-ati: Crash on start with radeon driver

2007-03-05 Thread Sven Arvidsson
 I tried falling back to
 xserver-xorg-core 1.2.0-5 and xserver-xorg-video-ati 6.6.3-4 but with
 the same results.

Falling back further, to xserver-xorg-video-ati version 6.6.3-2, I can't
reproduce this and everything seem to work fine.

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 760BDD22


signature.asc
Description: This is a digitally signed message part


Bug#413463: xserver-xorg-video-ati: Crash on start with radeon driver

2007-03-05 Thread Brice Goglin
Sven Arvidsson wrote:
 Package: xserver-xorg-video-ati
 Version: 1:6.6.3-5
 Severity: normal

 X crashes on start with the radeon driver:

 Backtrace:
 0: /usr/bin/X(xf86SigHandler+0x84) [0x80c02f4]
 1: [0xb7ef0420]
 2: /usr/lib/xorg/modules/drivers//radeon_drv.so [0xb7b3d56f]
 3: /usr/lib/xorg/modules/drivers//radeon_drv.so(RADEONPreInit+0xb99) 
 [0xb7b405c9]
 4: /usr/bin/X(InitOutput+0x9c4) [0x809ff54]
 5: /usr/bin/X(main+0x27b) [0x806e35b]
 6: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0xb7d08ea8]
 7: /usr/bin/X(FontFileCompleteXLFD+0xa5) [0x806d8a1]
   

Could you rebuild the server (xserver-xorg-core) and ATI driver with
debugging information and capture a backtrace with gdb? FYI, there are
details on all this at http://wiki.debian.org/HowToGetABacktrace
(replace hello with the packages above).

Thank you
Brice



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



Bug#413463: xserver-xorg-video-ati: Crash on start with radeon driver

2007-03-05 Thread Sven Arvidsson
On Mon, 2007-03-05 at 20:01 +0100, Brice Goglin wrote:
 Could you rebuild the server (xserver-xorg-core) and ATI driver with
 debugging information and capture a backtrace with gdb? FYI, there are
 details on all this at http://wiki.debian.org/HowToGetABacktrace
 (replace hello with the packages above).

Hi,

Sure, I'm attaching the backtrace. 

BTW, that page doesn't have any tips on getting a backtrace from X.
Maybe one of the examples from this page could be adapted?
http://wiki.x.org/wiki/DebuggingTheXserver . I ended up using Debugging
with one machine, version 1.

Also, thanks for following up on this bug so fast! :)

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 760BDD22
(gdb) Reading symbols from /usr/bin/Xorg.orig...done.
Using host libthread_db library /lib/tls/i686/cmov/libthread_db.so.1.
(gdb) (gdb) SignalStop  Print   Pass to program Description
SIGUSR1   NoYes Yes User defined signal 1
(gdb) SignalStopPrint   Pass to program Description
SIGUSR2   NoYes Yes User defined signal 2
(gdb) SignalStopPrint   Pass to program Description
SIGPIPE   NoYes Yes Broken pipe
(gdb) Starting program: /usr/bin/Xorg.orig :0 -dpi 96 -audit 0 -auth 
/var/lib/gdm/:0.Xauth -nolisten tcp vt7
Failed to read a valid object file image from memory.

X Window System Version 7.2.0
Release Date: 22 January 2007
X Protocol Version 11, Revision 0, Release 7.2
Build Operating System: Linux Debian
Current Operating System: Linux zoe 2.6.18-4-686 #1 SMP Wed Feb 21 16:06:54 UTC 
2007 i686
Build Date: 05 March 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /var/log/Xorg.0.log, Time: Mon Mar  5 22:01:06 2007
(==) Using config file: /etc/X11/xorg.conf
[Thread debugging using libthread_db enabled]
[New Thread -1210890560 (LWP 7460)]
(**) RADEON(0): RADEONPreInit

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1210890560 (LWP 7460)]
0xb7c0aabe in RADEONValidateMergeModes (pScrn1=0x81ef390)
at ../../src/radeon_modes.c:648
648 if (pScrn-monitor-DDC) {
(gdb) #0  0xb7c0aabe in RADEONValidateMergeModes (pScrn1=0x81ef390)
at ../../src/radeon_modes.c:648
#1  0xb7bf756f in RADEONPreInitModes (pScrn=0x81ef390, 
pInt10=value optimized out) at ../../src/radeon_driver.c:2252
#2  0xb7bfa5c9 in RADEONPreInit (pScrn=0x81ef390, flags=value optimized out)
at ../../src/radeon_driver.c:3187
#3  0x0809ff54 in InitOutput (pScreenInfo=0x81dc540, argc=11, argv=0xbfd3b294)
at ../../../../hw/xfree86/common/xf86Init.c:601
#4  0x0806e35b in main (argc=11, argv=0xbfd3b294, envp=0xbfd3b2c4)
at ../../dix/main.c:370
(gdb) Continuing.

Backtrace:
0: /usr/bin/Xorg.orig(xf86SigHandler+0x84) [0x80cc2a4]
1: [0xb7fc2420]
2: /usr/lib/xorg/modules/drivers//radeon_drv.so [0xb7bf756f]
3: /usr/lib/xorg/modules/drivers//radeon_drv.so(RADEONPreInit+0xb99) 
[0xb7bfa5c9]
4: /usr/bin/Xorg.orig(InitOutput+0x9c4) [0x809ff54]
5: /usr/bin/Xorg.orig(main+0x27b) [0x806e35b]
6: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0xb7ddaea8]
7: /usr/bin/Xorg.orig(FontFileCompleteXLFD+0xa5) [0x806d8a1]

Fatal server error:
Caught signal 11.  Server aborting


Program received signal SIGABRT, Aborted.
0xb7fc2410 in ?? ()
(gdb) The program is running.  Exit anyway? (y or n) [answered Y; input not 
from terminal]


signature.asc
Description: This is a digitally signed message part