Bug#755138: [xorg] impossible execute startx

2014-07-17 Thread Marco Righi
Package: xorg
Version: 1:7.7+7
Severity: critical

--- Please enter the report below this line. ---
Similar bug opened: 755...@bugs.debian.org

Description file attached. I have the same problem on two different
computers with the following nvidia card:

(this one refers to log file attached)
GPU #0:
  Name  : GeForce GT 520
  UUID  : GPU-dc95c099-9b26-3273-d3b0-2e66bee1522a
  PCI BusID : PCI:1:0:0

  Number of Display Devices: 2

  Display Device 0 (CRT-1):
  EDID Name : Samsung SyncMaster
  Minimum HorizSync : 30.000 kHz
  Maximum HorizSync : 81.000 kHz
  Minimum VertRefresh   : 56 Hz
  Maximum VertRefresh   : 75 Hz
  Maximum PixelClock: 140.000 MHz
  Maximum Width : 1280 pixels
  Maximum Height: 1024 pixels
  Preferred Width   : 1280 pixels
  Preferred Height  : 1024 pixels
  Preferred VertRefresh : 60 Hz
  Physical Width: 380 mm
  Physical Height   : 300 mm

  Display Device 1 (DFP-0):
  EDID Name : Ancor Communications Inc VE247
  Minimum HorizSync : 30.000 kHz
  Maximum HorizSync : 83.000 kHz
  Minimum VertRefresh   : 50 Hz
  Maximum VertRefresh   : 76 Hz
  Maximum PixelClock: 170.000 MHz
  Maximum Width : 1920 pixels
  Maximum Height: 1080 pixels
  Preferred Width   : 1920 pixels
  Preferred Height  : 1080 pixels
  Preferred VertRefresh : 60 Hz
  Physical Width: 530 mm
  Physical Height   : 300 mm


This is the other computer message

Command 502 of 3 #nvidia-xconfig --query-gpu-info
Number of GPUs: 1

GPU #0:
  Name  : GeForce 8500 GT
  UUID  : GPU-8b451ec2-ef7d-fe26-5c81-16ae92dfda2d
  PCI BusID : PCI:1:0:0

  Number of Display Devices: 2

  Display Device 0 (CRT-0):
  EDID Name : Ancor Communications Inc ASUS VH222
  Minimum HorizSync : 30.000 kHz
  Maximum HorizSync : 85.000 kHz
  Minimum VertRefresh   : 55 Hz
  Maximum VertRefresh   : 75 Hz
  Maximum PixelClock: 160.000 MHz
  Maximum Width : 1920 pixels
  Maximum Height: 1080 pixels
  Preferred Width   : 1920 pixels
  Preferred Height  : 1080 pixels
  Preferred VertRefresh : 60 Hz
  Physical Width: 470 mm
  Physical Height   : 260 mm

  Display Device 1 (CRT-1):
  EDID Name : Ancor Communications Inc ASUS VH222
  Minimum HorizSync : 30.000 kHz
  Maximum HorizSync : 85.000 kHz
  Minimum VertRefresh   : 55 Hz
  Maximum VertRefresh   : 75 Hz
  Maximum PixelClock: 160.000 MHz
  Maximum Width : 1920 pixels
  Maximum Height: 1080 pixels
  Preferred Width   : 1920 pixels
  Preferred Height  : 1080 pixels
  Preferred VertRefresh : 60 Hz
  Physical Width: 470 mm
  Physical Height   : 260 mm



Please contact me. I am glad to help you.

thanks
Marco Righi

--- System information. ---
Architecture: amd64
Kernel:   Linux 3.14-1-amd64

Debian Release: jessie/sid
  500 testing-updates ftp.it.debian.org
  500 testing www.deb-multimedia.org
  500 testing security.debian.org
  500 testing ftp.it.debian.org
  500 testing apt.jenslody.de
  500 stable  repo.wuala.com
  500 stable  apt.spideroak.com
  500 sid linux.dropbox.com
  500 debian  packages.linuxmint.com
  100 jessie-backports ftp.it.debian.org

--- Package information. ---
Depends  (Version) | Installed
==-+-==
xserver-xorg  (= 1:7.7+7) | 1:7.7+7
libgl1-mesa-glx|
 OR libgl1 |
libgl1-mesa-dri|
libglu1-mesa   |
xfonts-base (= 1:1.0.0-1) |
xfonts-100dpi   (= 1:1.0.0-1) |
xfonts-75dpi(= 1:1.0.0-1) |
xfonts-scalable (= 1:1.0.0-1) |
x11-apps   |
x11-session-utils  |
x11-utils  |
x11-xkb-utils  |
x11-xserver-utils  |
xauth  |
xinit  |
xfonts-utils   |
xkb-data   |
xorg-docs-core |
xterm  |
 OR x-terminal-emulator|
xserver-xorg-core(= 2:1.15.0.901) |
xserver-xorg-video-all |
 OR xorg-driver-video  |
xserver-xorg-input-all |
 OR xorg-driver-input  |
xserver-xorg-input-evdev

Bug#592588: [scorched3d] Crash and reset of X graphics interfaces on ACER Traelmate 6292

2010-08-19 Thread Marco Righi
User:root Computer:europa Base:X11 Current:/etc/X11
Command 508 of 9 #ls
app-defaults ko_KR.eucKR  xorg.conf
  Xsession.d
cursors  openbox  xorg.conf~
  Xsession.options
default-display-manager  rgb.txt
xorg.conf.1239897374-16.aprile.2009-17.56.root.tgz  XvMCConfig
fontstwm  Xreset
  Xwrapper.config
fvwm XXreset.d
ja_JP.eucJP  xinitXresources
ja_JP.UTF-8  xkb  Xsession
===


Perhaps I can help you because on the shell of the notebook appears this
error (that reports the point[er] that causes the error)

===
[...]
Please also check the log file at /var/log/Xorg.0.log for additional
information.
X: ../../src/i830_batchbuffer.h:79: intel_batch_emit_dword: Assertion
'pI830-batch_ptr != ((void *)0' failed.
xinit: connection to X server lost.
===

Sorry I send only to you this e-mail, I kow this is incomplete. If you
think that it is really useful, please forward it as you prefer.

Contact me if you think I help the team in debug process.

Thanks
Marco


Il 19/08/2010 14:23, Julien Cristau ha scritto:
 On Thu, Aug 12, 2010 at 11:12:48 +0200, Marco Righi wrote:
 
 The chipset should be an intel 810.

 It's not i810, it's a 965GM.  Reassigning this bug to mesa.
 
 It would be useful if you could get a backtrace from the X server.
 Install xserver-xorg-core-dbg and libgl1-mesa-dri-dbg, and follow the
 instructions at http://wiki.debian.org/XStrikeForce/XserverDebugging
 
 Cheers,
 Julien




-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c6d33ae.9030...@gmail.com



Bug#592588: [scorched3d] Crash and reset of X graphics interfaces on ACER Traelmate 6292

2010-08-19 Thread Marco Righi
I work with this machine, I prefer do not upgrgade to an experimental
version of the driver.

Sorry, I can not risk a stop of the machine.

Marco

Il 19/08/2010 15:58, Julien Cristau ha scritto:
 On Thu, Aug 19, 2010 at 15:37:50 +0200, Marco Righi wrote:
 
 0xb78db424 in __kernel_vsyscall ()
 (gdb) set logging overwrite on
 (gdb) set logging on
 Copying output to gdb.txt.
 
 You need to type 'continue' here at the gdb prompt.  That will unblock
 X, and let you run the program that crashes it.  Then gdb will stop it
 again, and at that point you can get a backtrace.
 
 (gdb) bt full
 #0  0xb78db424 in __kernel_vsyscall ()
 No symbol table info available.
 [...]

 Perhaps I can help you because on the shell of the notebook appears this
 error (that reports the point[er] that causes the error)

 ===
 [...]
 Please also check the log file at /var/log/Xorg.0.log for additional
 information.
 X: ../../src/i830_batchbuffer.h:79: intel_batch_emit_dword: Assertion
 'pI830-batch_ptr != ((void *)0' failed.
 xinit: connection to X server lost.
 ===

 OK, this bit is useful, thanks.  Can you upgrade
 xserver-xorg-video-intel to the version in experimental (2.12), and try
 again?
 
 Cheers,
 Julien




-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c6d3943.7070...@gmail.com