Bug#699472: xserver-xorg-core: Caught signal 11 (Segmentation fault). Server aborting
I don't know if it's related, but got another reproducible
segmentation fault while trying another game (FTL).
In Xorg.0.log:
[1305277.651] Backtrace:
[1305277.660] 0: /usr/bin/Xorg (xorg_backtrace+0x36) [0x7fbe5f917cd6]
[1305277.660] 1: /usr/bin/Xorg (0x7fbe5f799000+0x182829) [0x7fbe5f91b829]
[1305277.660] 2: /lib/x86_64-linux-gnu/libpthread.so.0
(0x7fbe5eac1000+0xf030) [0x7fbe5ead0030]
[1305277.661] 3: /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
(0x7fbe59d4a000+0x285ae3) [0x7fbe59fcfae3]
[1305277.661] 4: /usr/lib/xorg/modules/extensions/libglx.so
(0x7fbe5c23+0xddb1) [0x7fbe5c23ddb1]
[1305277.661] 5: /usr/lib/xorg/modules/extensions/libglx.so
(0x7fbe5c23+0x3c223) [0x7fbe5c26c223]
[1305277.661] 6: /usr/bin/Xorg (0x7fbe5f799000+0x52e61) [0x7fbe5f7ebe61]
[1305277.661] 7: /usr/bin/Xorg (0x7fbe5f799000+0x41ec5) [0x7fbe5f7daec5]
[1305277.661] 8: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xfd) [0x7fbe5d7e8ead]
[1305277.661] 9: /usr/bin/Xorg (0x7fbe5f799000+0x4219d) [0x7fbe5f7db19d]
[1305277.661]
[1305277.661] Segmentation fault at address 0x637f4870
[1305277.661]
Fatal server error:
[1305277.661] Caught signal 11 (Segmentation fault). Server aborting
A backtrace is also attached.
Thank you!
Best regards,
Nelson
Continuing.
[New Thread 0x7fbe586c8700 (LWP 26833)]
Program received signal SIGSEGV, Segmentation fault.
_mesa_GenTextures (n=256, textures=) at main/texobj.c:876
876 main/texobj.c: Arquivo ou diretório não encontrado.
#0 _mesa_GenTextures (n=256, textures=) at main/texobj.c:876
texObj =
name = 1871
target = 0
ctx = 0x7fbe6261f030
first =
i =
#1 0x7fbe5c23ddb1 in __glXDisp_GenTextures (cl=0x7fbe62b4b058,
pc=) at ../../glx/indirect_dispatch.c:2851
n = 256
answerBuffer = {2201748512, 32767, 1602384045, 32702, 2201748528,
32767, 2202004137, 32767, 0 , 2201748624, 32767,
2202004137, 32767, 2201748688, 32767, 0, 0, 0, 1, 1, 0, 1606004352,
32702, 1605976304, 32702, 2201748688, 32767, 1572175494, 32702,
2201748688, 32767, 1, 0, 1606004352, 32702, 1603393436, 32702, 0, 0,
2, 0, 0, 0, 2, 0, 1606004224, 32702, 1603360858, 32702, 32,
0, 1637120688, 32702, 1650585648, 32702, 2201748752, 32767, 112, 0,
891963, 0 , 58, 0, 1602787880, 32702, 1635264896,
32702, 48, 32702, 2201749064, 32767, 2201748992, 32767, 32, 0,
25165825, 58, 1572142792, 32702, 0, 32702, 24, 0, 16, 48,
2201749216, 32767, 2201749008, 32767, 1572142792, 32702, 1, 0, 27,
0, 1669243184, 32702, 4112, 0, 1, 0 , 2201749216,
32767, 2202004137, 32767, 2201749280, 32767, 0, 0, 1635451600,
32702, 1635454272, 32702, 1605960840, 32702, 1602160052, 32702,
1661456160, 32702, 1605960832, 32702, 1548310592, 32702, 0, 0}
textures = 0x637f4870
req =
error = 32702
cx =
#2 0x7fbe5c26c223 in __glXDispatch (client=)
at ../../glx/glxext.c:568
rendering = 0 '\000'
stuff = 0x7fbe637ea130
opcode = 145 '\221'
proc =
cl = 0x7fbe62b4b058
retval =
#3 0x7fbe5f7ebe61 in Dispatch () at ../../dix/dispatch.c:428
clientReady = 0x7fbe61947ab0
result =
client = 0x7fbe62b4af10
nready = 0
icheck = 0x7fbe5fb940f0
start_tick = 14020
#4 0x7fbe5f7daec5 in main (argc=10, argv=0x7fff833c0918,
envp=) at ../../dix/main.c:288
i =
alwaysCheckForInput = {0, 1}
Bug#699472: xserver-xorg-core: Caught signal 11 (Segmentation fault). Server aborting
Hi!
On Fri, Feb 1, 2013 at 9:22 AM, Michel Dänzer wrote:
> BTW, I presume you're not intentionally running the game with indirect
> rendering, are you? If you installed the 32 bit version of the demo,
> installing the libgl1-mesa-{glx,dri}:i386 packages might help.
Hum... I had libgl1-mesa-glx:i386 installed but not libgl1-mesa-dri:i386.
Now it's working without any issues.
But even with the missing library, X shouldn't crash, right?
Thank you!
Best regards,
Nelson
--
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/CAARFvTW3z4GRPt0i-vThWukKDCqfgmBn=e-8q0dhdwv0n+g...@mail.gmail.com
Bug#699472: xserver-xorg-core: Caught signal 11 (Segmentation fault). Server aborting
Hi!
On Thu, Jan 31, 2013 at 5:28 PM, Julien Cristau wrote:
> That attachment doesn't show an error.
The right log was sent on another email.
> Also please get a backtrace from gdb if the bug is reproducible (with
> xserver-xorg-core-dbg and libgl1-mesa-dri-dbg installed).
gdb bt full is attached.
Thank you!
Best regards,
Nelson
Continuing.
[New Thread 0x7f326171c700 (LWP 4239)]
[New Thread 0x7f3260227700 (LWP 4248)]
Program received signal SIGSEGV, Segmentation fault.
convert_sampler (st=st@entry=0x7f326a92da80,
sampler=sampler@entry=0x7f326a92db70, texUnit=1)
at state_tracker/st_atom_sampler.c:141
141 state_tracker/st_atom_sampler.c: Arquivo ou diretório não encontrado.
#0 convert_sampler (st=st@entry=0x7f326a92da80,
sampler=sampler@entry=0x7f326a92db70, texUnit=1)
at state_tracker/st_atom_sampler.c:141
texobj = 0x7f326aa096f0
ctx = 0x7f326a8fdf80
msamp = 0x34
#1 0x7f3263138dd9 in update_fragment_samplers (st=0x7f326a92da80)
at state_tracker/st_atom_sampler.c:247
texUnit =
sampler = 0x7f326a92db70
ctx = 0x7f326a8fdf80
fprog = 0x7f326a68c290
su =
#2 update_samplers (st=0x7f326a92da80) at state_tracker/st_atom_sampler.c:267
No locals.
#3 0x7f3263136a8f in st_validate_state (st=st@entry=0x7f326a92da80)
at state_tracker/st_atom.c:197
state = 0x7f326a92e2e0
#4 0x7f326313ca7b in st_Clear (ctx=0x7f326a8fdf80, mask=50)
at state_tracker/st_cb_clear.c:508
st = 0x7f326a92da80
depthRb = 0x7f326a7680d0
stencilRb = 0x7f326a7680d0
quad_buffers = 0
clear_buffers = 0
i =
#5 0x7f32652de7c4 in __glXDisp_Render (cl=,
pc=) at ../../glx/glxcmds.c:2011
entry = {bytes = 8, varsize = 0}
extra =
proc =
err = 0
req =
client = 0x7f326a24c430
left =
cmdlen = 8
error =
commandsDone =
hdr =
glxc = 0x7f326a4760a0
sw =
#6 0x7f32652e1223 in __glXDispatch (client=)
at ../../glx/glxext.c:568
rendering = 1 '\001'
stuff = 0x7f326a3e8960
opcode = 1 '\001'
proc =
cl = 0x7f326a24c578
retval =
#7 0x7f3268884e61 in Dispatch () at ../../dix/dispatch.c:428
clientReady = 0x7f326a17dd80
result =
client = 0x7f326a24c430
nready = 0
icheck = 0x7f3268c2d0f0
start_tick = 2340
#8 0x7f3268873ec5 in main (argc=10, argv=0x7fffb8b71ee8,
envp=) at ../../dix/main.c:288
i =
alwaysCheckForInput = {0, 1}
Bug#624548: More info for #624548
I have created a xorg.conf file (via Xorg -configure) and included in Section Screen: Option "Accel" "no" Things are really slow (as expected) but crashes are gone too. >From http://nouveau.freedesktop.org/wiki/EXA it says that nouveau doesn't support XAA, so there is no sense in testing the "XaaNo*" options, right? Is there something else that I can test to try to narrow this, please? Thank you again! Best regards, Nelson -- 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/CAARFvTVaiAbKk6Ca+LoCJaE8gEr=UZG=-vvj8cuvuvirxw-...@mail.gmail.com
Bug#624548: More info for #624548
On Wed, Jul 13, 2011 at 9:05 AM, Nelson A. de Oliveira wrote: > Any terminal + Gnome works nicely. Stupid me. Actually it crashes with Gnome too; works nicely with Gnome Terminal and not urxvt. Sorry for the lack of coffee. Nelson -- 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/CAARFvTXHSUWFdQ8=Xi48reQV6c9OP8=1hmVu4PXh=fvsta4...@mail.gmail.com
Bug#624548: More info for #624548
Hi again! On Tue, Jul 12, 2011 at 5:01 PM, Nelson A. de Oliveira wrote: > I don't know if it adds something useful, but adding a new Nvidia > graphics card (and using xserver-xorg-video-nouveau), unholding the > packages and updating them to their latest versions it also crashes > hard when opening an urxvt terminal. Sorry to annoy again, but with basically any terminal + awesome window manager it crashes, unfortunately. Any terminal + Gnome works nicely. Thank you! Best regards, Nelson -- 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/CAARFvTVdqfq6kf07TwXNas0z412ztVfgk=ecs+juannz28+...@mail.gmail.com
Bug#624548: xserver-xorg: Segmentation fault while opening rxvt
Hi again! :-) On Fri, Apr 29, 2011 at 3:15 PM, Cyril Brulebois wrote: >> I've got /var/lib/gdm3/core (and not /etc/X11/core; is there something >> wrong about this?). > > (noted; to check and investigate before updating the page.) Maybe one more thing: on both wikis we have "gdb -p $(pidof X)" but actually it should be "gdb -p $(pidof Xorg)", right? > (and sorry again for not noticing the “two gdb backtraces” part.) No problems :-) Looking at even older logs here I saw these updates: xserver-xorg 1:7.5+8 -> 1:7.6+6 xserver-xorg-core 2:1.7.7-13 -> 2:1.9.5-1 xserver-xorg-input-all 1:7.5+8 -> 1:7.6+6 xserver-xorg-input-evdev 1:2.3.2-6 -> 1:2.6.0-2 xserver-xorg-input-synaptics 1.2.2-2 -> 1.4.0-1 xserver-xorg-input-wacom 0.10.5+20100416-1 -> 0.10.10+20110203-1 xserver-xorg-video-ati 1:6.13.1-2+squeeze1 -> 1:6.14.0-1 xserver-xorg-video-mach64 6.8.2-3 -> 6.8.2-5 xserver-xorg-video-r128 6.8.1-3 -> 6.8.1-5 xserver-xorg-video-radeon 1:6.13.1-2+squeeze1 -> 1:6.14.0-1 Downgrading them back to the older versions and everything is fine now. This machine stayed a long time without rebooting or restarting X, thus that is why I didn't see any kind of problems before. Thank you! Best regards, Nelson -- 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/banlktin_un-cipcxxpvzlfdhfpihaup...@mail.gmail.com
Bug#624548: xserver-xorg: Segmentation fault while opening rxvt
Hi!
On Fri, Apr 29, 2011 at 11:35 AM, Cyril Brulebois wrote:
> it's always good to provide full backtraces, see:
> http://pkg-xorg.alioth.debian.org/howto/report-bugs.html
> http://pkg-xorg.alioth.debian.org/howto/use-gdb.html
I have followed http://wiki.debian.org/XStrikeForce/XserverDebugging
to get both backtraces before.
By including this in /etc/gdm3/daemon.conf:
[daemon]
LocalXserverCommand=/usr/bin/Xorg -br -verbose -audit 0 -novtswitch -core
I've got /var/lib/gdm3/core (and not /etc/X11/core; is there something
wrong about this?).
The backtraced gdb output of the core is attached.
Just in case it's important, it has been backtraced by:
set logging on
handle SIGPIPE nostop
bt full
> (Anyway, trying without the FontPath should be easy enough to check,
> if you want to make sure about #615975.)
I didn't have any FontPath "unix/:port" in xorg.conf (actually I don't
have a xorg.conf; just created one via "Xorg -configure", to include
Option "NoTrapSignals" in it).
But even after commenting all the FontPath in this generated
xorg.conf, the problem still persists.
Is it another way to get a better backtrace or something else that I
can do, please?
Thank you!
Best regards,
Nelson
Continuing.
Program received signal SIGABRT, Aborted.
0x7fa6a4ec4165 in raise (sig=) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
64 ../nptl/sysdeps/unix/sysv/linux/raise.c: Arquivo ou diretório não
encontrado.
in ../nptl/sysdeps/unix/sysv/linux/raise.c
#0 0x7fa6a4ec4165 in raise (sig=) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
pid =
selftid =
#1 0x7fa6a4ec6f70 in abort () at abort.c:92
act = {__sigaction_handler = {sa_handler = 0x7fffacbd4968, sa_sigaction
= 0x7fffacbd4968}, sa_mask = {__val = {
140736091474256, 140736091483695, 13, 140353709248667, 3,
140736091474266, 6, 140353709248671, 2,
140736091474254, 2, 140353709239759, 1, 140353709248667, 3,
140736091474260}}, sa_flags = 12,
sa_restorer = 0x7fa6a4fb909f}
sigs = {__val = {32, 0 }}
#2 0x7fa6a4efa27b in __libc_message (do_abort=,
fmt=)
at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
ap = {{gp_offset = 40, fp_offset = 48, overflow_arg_area =
0x7fffacbd52d0, reg_save_area = 0x7fffacbd51e0}}
ap_copy = {{gp_offset = 16, fp_offset = 48, overflow_arg_area =
0x7fffacbd52d0, reg_save_area = 0x7fffacbd51e0}}
fd = 26
on_2 =
list =
nlist = 0
cp =
written = false
#3 0x7fa6a4f03ad6 in malloc_printerr (action=3, str=0x7fa6a4fb7bd0
"malloc(): memory corruption",
ptr=) at malloc.c:6267
buf = "019cbd00"
cp = 0x7fa6a4fb0e40 "0123456789abcdefghijklmnopqrstuvwxyz"
#4 0x7fa6a4f06b6d in _int_malloc (av=0x7fa6a51eee40, bytes=) at malloc.c:4396
iters = 0
nb = 640
idx =
bin = 0x0
victim = 0x19cbcf0
size =
victim_index =
remainder =
remainder_size =
block =
bit =
map =
fwd =
bck = 0xff00ff00
errstr =
__func__ = "_int_malloc"
#5 0x7fa6a4f08930 in __libc_malloc (bytes=632) at malloc.c:3661
ar_ptr = 0x7fa6a51eee40
victim = 0x4f
__func__ = "__libc_malloc"
#6 0x004dccb9 in damageText (pDrawable=,
pGC=0x540, x=6, y=-1, count=140353709215296,
chars=0x407d88 "", fontEncoding=TwoD16Bit, textType=3) at
../../../miext/damage/damage.c:1513
info =
i =
n =
w =
imageblt =
#7 0x004e134a in damageImageText16 (pDrawable=0x13fc660,
pGC=0x13fdd30, x=6, y=10, count=-1527050688,
chars=) at ../../../miext/damage/damage.c:1610
oldFuncs = 0x7d0180
#8 0x00428a03 in doImageText (client=0x13fb750, c=0x7fffacbd54e0) at
../../dix/dixfonts.c:1565
err =
lgerr = 0
fpe =
#9 0x00428acf in ImageText (client=0x540, pDraw=,
pGC=0x6, nChars=,
data=0x7fa6a4fb0e40 "0123456789abcdefghijklmnopqrstuvwxyz", xorg=4226440,
yorg=-1, reqType=77, did=16777225)
at ../../dix/dixfonts.c:1616
local_closure = {client = 0x13fb750, pDraw = 0x13fc660, pGC =
0x13fdd30, nChars = 79 'O', data = 0x144227c "",
xorg = 6, yorg = 10, reqType = 77 'M', imageText = 0x4e1260
, itemSize = 2, did = 16777225}
#10 0x0044647b in ProcImageText16 (client=0x13fb750) at
../../dix/dispatch.c:2330
pDraw = 0x13fc660
pGC = 0x13fdd30
#11 0x00448909 in Dispatch () at ../../dix/dispatch.c:432
result =
client = 0x13fb750
nready = 0
start_tick = 1300
#12 0x004257ab in main (argc=12, argv=0x7fffacbd5758, envp=) at ../../dix/main.c:291
i = 1
alwaysCheckForInput = {0, 1}
SignalStop Print Pass to program Description
SIGPIPE NoYes Yes Broken pipe
The program is not being run.
#0 _int_ma
Bug#493641: xserver-xorg: X server dying with error in I830WaitLpRing()
Hi! On Sat, Jun 13, 2009 at 3:34 AM, Brice Goglin wrote: > Does this still happen with latest intel driver in unstable or > experimental? It is very stable with the latest version from sid. Sorry that I did not send a message about this. Thank you very much! Best regards, Nelson -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#497523: NEWS?
Hi! On Sun, Apr 12, 2009 at 9:42 AM, David Nusinow wrote: > Brice Goglin wrote: >> David actually wrote a NEWS entry about this yesterday: >> >> http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-input-synaptics.git;a=commitdiff;h=598ae3fe8592f80e97f58a1c54822754dcd5378e >> >> If anybody knows how to enable tapping at runtime with hal or xinput, we >> can add it as well. > > Additionally, if people who actually have and use synaptics could check > the example in that entry and confirm that it works, I'd very much > appreciate it. Using Option "TouchpadOff" "2" didn't work here. I had to use this however: Option "TapButton1""1" Option "TapButton2""2" Option "TapButton3""3" If there is something that I can do to help (sending logs, etc), please, just ask. Thank you! Best regards, Nelson -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
"Dead" keyboard after upgrade of xserver (experimental)
(CC me, please) Hi! Today I have updated some packages from experimental: xserver-common 2:1.5.2-1 -> 2:1.5.3-1 xserver-xephyr 2:1.5.2-1 -> 2:1.5.3-1 xserver-xorg-core 2:1.5.2-1 -> 2:1.5.3-1 But after turning on the machine later, I got a "dead" keyboard: nothing could be written, numlock nor caps lock were working, couldn't kill the server (ctrl+alt+backspace) nor change to console (ctrl+alt+f1). Then booted a live CD and downgraded those packages: [REMOVE, NOT USED] libpciaccess0 [REMOVE, DEPENDENCIES] xserver-common [REMOVE, DEPENDENCIES] xserver-xephyr [REMOVE, DEPENDENCIES] xserver-xorg-input-synaptics [DOWNGRADE] x11-common 1:7.4~4 -> 1:7.3+18 [DOWNGRADE] xserver-xorg 1:7.4~4 -> 1:7.3+18 [DOWNGRADE] xserver-xorg-core 2:1.5.3-1 -> 2:1.4.2-8 [DOWNGRADE] xserver-xorg-input-kbd 1:1.3.1-2 -> 1:1.3.1-1 [DOWNGRADE] xserver-xorg-input-mouse 1:1.3.0-2 -> 1:1.3.0-1 [DOWNGRADE] xserver-xorg-video-intel 2:2.4.2-1 -> 2:2.3.2-2+lenny5 And now it works again. With version 1.5.2 (from experimental) everything was working normally, but with 1.5.3 I just can't get my keyboard to work. Do you know something that has changed from 1.5.2 to 1.5.3, please? Can I do something to help in debugging this problem? Thank you! Best regards, Nelson signature.asc Description: PGP signature
Bug#495139: cleanlinks: warning in "find" usage
Package: xutils-dev Version: 1:7.4+3 Severity: minor Hi! Running "cleanlinks" I get this message (that I think that it's inoffensive): $ cleanlinks Removing empty directories ... find: warning: you have specified the -depth option after a non-option argument -type, but options are not positional (-depth affects tests specified before it as well as those specified after it). Please specify options before other arguments. (...) Thank you! Best regards, Nelson -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26.2-naoliv1 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xutils-dev depends on: ii cpp 4:4.3.1-2 The GNU C preprocessor (cpp) ii libc6 2.7-13 GNU C Library: Shared libraries ii x11-common1:7.4~1X Window System (X.Org) infrastruc xutils-dev recommends no packages. xutils-dev suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#493641: xserver-xorg: X server dying with error in I830WaitLpRing()
Package: xserver-xorg Version: 1:7.3+15 Severity: important Hi! This is the second time that my X server dies here, closing togheter everything that I was working on :-/ Well, X dies and I can't get it back; trying to start it I get: === Fatal server error: lockup === The error message that I get on Xorg.0.log, after the crash is: === Error in I830WaitLpRing(), timeout for 2 seconds pgetbl_ctl: 0x7ffc0001 getbl_err: 0x ipeir: 0x iphdr: 0x66014140 LP ring tail: 0x00010d50 head: 0x00010d74 len: 0x0001f001 start 0x eir: 0x esr: 0x emr: 0x instdone: 0xfa41 instpm: 0x memmode: 0x0306 instps: 0x800f04c4 hwstam: 0xfffe ier: 0x0002 imr: 0x iir: 0x0070 Ring at virtual 0xa7935000 head 0x10d74 tail 0x10d50 count 32759 00010cf4: 03cc2000 00010cf8: 00200184 00010cfc: 00240188 00010d00: 0100 00010d04: 00010d08: 0010 00010d0c: 0200 00010d10: 54f6 00010d14: 03cc2000 00010d18: 00200188 00010d1c: 0024018c 00010d20: 0100 00010d24: 00010d28: 0010 00010d2c: 0200 00010d30: 54f6 00010d34: 03cc2000 00010d38: 0020018c 00010d3c: 00240190 00010d40: 0100 00010d44: 00010d48: 0010 00010d4c: 0200 00010d50: 0c73 00010d54: 0014 00010d58: 0c74 00010d5c: 00010d60: 0c2e 00010d64: ff90 00010d68: 0c32 00010d6c: a00d 00010d70: 0c2e 00010d74: 08a1 Ring end space: 28 wanted 32 (II) intel(0): [drm] removed 1 reserved context for kernel (II) intel(0): [drm] unmapping 8192 bytes of SAREA 0xf8957000 at 0xb7c63000 (II) intel(0): [drm] Closed DRM master. Fatal server error: lockup === The full log is available here: http://people.debian.org/~naoliv/misc/Xorg.0.log.txt Can I do something else to help on this, please? Thank you very much! Best regards, Nelson -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 Ago 25 2006 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1719604 Ago 2 18:43 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: lrwxrwxrwx 1 root root 16 Jun 22 2007 /etc/X11/xorg.conf -> xorg.conf.single 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" Load"i2c" Load"bitmap" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"type1" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "latitude" Option "XkbLayout" "us_intl" EndSection Section "InputDevice" Identifier "Con
Bug#468278: Still present in latest git
Hi! With the latest git code (git describe gives xf86-video-intel-2.2.0-73-g02a3b80) from git://git.freedesktop.org/git/xorg/driver/xf86-video-intel (is it the right place to get the code?), I am still getting the same behavior. Just to inform you. Best regards, Nelson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#467388: xserver-xorg: X is crashing with "Fatal server error: Caught signal 11. Server aborting"
Package: xserver-xorg Version: 1:7.3+10 Severity: important Hi! There is already some time that X is crashing here, with no apparent motive. I can reproduce it by opening OpenOffice and clicking on the "File" menu. It crashs X instantly, then it restarts X and GDM. If I press CTRL+ALT+F1 then it crashs X hard (I can't get back to GDM nor can use console; the system keeps functional). It also crashes with Wine and StarCraft. And also crashs if I press my laptop power button, to turn off the computer. Well, "normal" Xorg.0.log is available at http://people.debian.org/~naoliv/misc/xorg/before-crash.txt After the crash, you can see http://people.debian.org/~naoliv/misc/xorg/after-crash.txt This is what is show at the end of the log file: Backtrace: 0: /usr/bin/X(xf86SigHandler+0x7e) [0x80c675e] 1: [0xa7f23420] 2: /usr/bin/X(XkbWriteXKBKeymapForNames+0x582) [0x819f6d2] 3: /usr/bin/X(XkbDDXLoadKeymapByNames+0x1aa) [0x81a9e2a] 4: /usr/bin/X(ProcXkbGetKbdByName+0x301) [0x8181351] 5: /usr/bin/X [0x818939a] 6: /usr/bin/X [0x814d86e] 7: /usr/bin/X(Dispatch+0x2bf) [0x808d1ef] 8: /usr/bin/X(main+0x48b) [0x807470b] 9: /lib/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xa7cb4450] 10: /usr/bin/X(FontFileCompleteXLFD+0x205) [0x8073a81] Fatal server error: Caught signal 11. Server aborting And there is also another line that appears on the log: (WW) intel(0): Existing errors found in hardware state. My xorg.conf is available at http://people.debian.org/~naoliv/misc/xorg/xorg.conf Is something else that I can do to help, please? Thank you very much! Best regards, Nelson -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24-naoliv1 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xserver-xorg depends on: ii debconf [debconf-2 1.5.19Debian configuration management sy ii x11-common 1:7.3+10 X Window System (X.Org) infrastruc ii x11-xkb-utils 7.3+1 X11 XKB utilities ii xkb-data 1.1~cvs.20080104.1-1 X Keyboard Extension (XKB) configu ii xserver-xorg-core 2:1.4.1~git20080131-1 Xorg X server - core server ii xserver-xorg-input 1:1.2.2-3 X.Org X server -- keyboard input d ii xserver-xorg-input 1:1.2.3-2 X.Org X server -- mouse input driv ii xserver-xorg-input 0.14.7~git20070706-2 Synaptics TouchPad driver for X.Or ii xserver-xorg-video 2:2.2.1-1 X.Org X server -- Intel i8xx, i9xx ii xserver-xorg-video 1:1.3.0-4 X.Org X server -- VESA display dri Versions of packages xserver-xorg recommends: ii dmidecode2.9-1 Dump Desktop Management Interface ii libgl1-mesa-dri 7.0.3~rc2-1 A free implementation of the OpenG ii udev 0.114-2 /dev/ and hotplug management daemo -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#400706: xserver-xorg-core: Wrong info on /etc/X11/xorg.conf
Package: xserver-xorg-core Version: 2:1.1.1-11 Severity: minor Hi! Sorry if this bug is already reported (or if I am reporting it to the wrong package), but I saw at /etc/X11/xorg.conf this info: (...) # Edit this file with caution, and see the /etc/X11/xorg.conf manual page. # (Type "man /etc/X11/xorg.conf" at the shell prompt.) (...) Actually, it's "man xorg.conf" and not "man /etc/X11/xorg.conf" Thank you! Best regards, Nelson -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-mm1 Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Versions of packages xserver-xorg-core depends on: ii libc6 2.3.6.ds1-8 GNU C Library: Shared libraries ii libfontenc1 1:1.0.2-2X11 font encoding library ii libgcc1 1:4.2-20060923-1 GCC support library ii libxau6 1:1.0.1-2X11 authorisation library ii libxdmcp6 1:1.0.1-2X11 Display Manager Control Protoc ii libxfont1 1:1.2.2-1X11 font rasterisation library ii x11-common 1:7.1.0-7X Window System (X.Org) infrastruc ii xserver-xorg1:7.1.0-7the X.Org X server ii zlib1g 1:1.2.3-13 compression library - runtime Versions of packages xserver-xorg-core recommends: ii xkb-data 0.9-4 X Keyboard Extension (XKB) configu -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#388618: Seems to be unreproducible
tags 388618 +unreproducible thanks Hi! I am tagging this bug as unreproducible. Updating to latest Xorg it seems that things are stable again (and not freezing anymore like 2 months ago). If the system keeps stable for one week I will close this bug. Thank you! Nelson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#384561: xserver-xorg: drmSetBusid failed (7, pci:0000:00:02.0), Device or resource busy
Hi! On 8/26/06, Michel Dänzer <[EMAIL PROTECTED]> wrote: If you're running lsof as root, please provide the full output of dmesg Yes, always as root. (BTW, have you tried with a slightly less experimental kernel? :). Tested now with Kernel 2.6.17-2-686 of Debian and it works. I am sending dmesg output of the two Kernel versions. "dmesg" is from 2.6.18-rc4-mm2 and "dmesg_working" from Debian's 2.6.17-2-686. I don't understand very well this part of DRI, DRM, etc, but I saw one difference between the two Kernels. On Debian's Kernel there is: [drm] Initialized i915 1.4.0 20060119 on minor 0 While on mine there is: [drm] Initialized i915 1.5.0 20060119 on minor 0 The same date but different version. So, DRI is not working because something changed between 1.4.0 and 1.5.0 or there is something really new on -mm series of the Kernel? Thank you Michel! Best regards, Nelson dmesg Description: Binary data dmesg_working Description: Binary data
Bug#384561: xserver-xorg: drmSetBusid failed (7, pci:0000:00:02.0), Device or resource busy
Hi! On 8/25/06, Michel Dänzer <[EMAIL PROTECTED]> wrote: > (II) I810(0): [drm] DRM interface version 1.0 > (II) I810(0): [drm] drmSetBusid failed (7, pci::00:02.0), Device or resource > busy > (EE) I810(0): [dri] DRIScreenInit failed. Disabling DRI. > > Is "Device or resource busy" a problem with X server? No, it usually means another process still has the DRM device open. Does sudo lsof /dev/dri/card0 show anything? Inside X it shows nothing. Stopping X is also shows nothing and after starting X, nothing again. I went to console, stopped X, run lsof, got nothing, started X, lsof again, empty output and the error of "Device or resource busy" was there on the log again. Ghost process using my card? :-) Thank you! Best regards, Nelson
Bug#322284: x11-common: Outdated Xsession.options(5) man page and use-session-dbus option
Package: x11-common Version: 6.8.2.dfsg.1-4 Severity: minor Hi! Today while upgrading my machine, I saw that it was added a new option "use-session-dbus" to /etc/X11/Xsession.options Taking a look at /etc/X11/Xsession.options, I have found: "See Xsession.options(5) for an explanation of the available options." But, the man page of Xsession.options doesn't explain what is the option use-session-dbus! It's outdated. Thank you Nelson -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.12-rc6-mm1 Locale: LANG=pt_BR, LC_CTYPE=pt_BR (charmap=ISO-8859-1) (ignored: LC_ALL set to pt_BR) Versions of packages x11-common depends on: ii debconf 1.4.57 Debian configuration management sy ii debianutils 2.14.2 Miscellaneous utilities specific t ii lsb-base 3.0-3 Linux Standard Base 3.0 init scrip x11-common recommends no packages. -- debconf information: x11-common/experimental_packages: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#296539: xserver-xfree86: Needing too much space to upgrade
Package: xserver-xfree86 Version: 4.3.0.dfsg.1-10 Severity: important Hi # apt-get dist-upgrade Reading Package Lists... Done Building Dependency Tree... Done Calculating Upgrade... Done The following packages have been kept back: lilo The following packages will be upgraded: fortunes-min lbxproxy libdps1 libice-dev libice6 libimlib2 libsigc++-2.0-0 libsm-dev libsm6 libsvn0 libx11-6 libx11-dev libxaw7 libxaw7-dev libxext-dev libxext6 libxft1 libxi-dev libxi6 libxmu-dev libxmu6 libxmuu-dev libxmuu1 libxp-dev libxp6 libxpm-dev libxpm4 libxrandr-dev libxrandr2 libxt-dev libxt6 libxtrap-dev libxtrap6 libxtst-dev libxtst6 libxv-dev libxv1 mime-support po-debconf python2.3-subversion subversion subversion-tools xbase-clients xfs xfwp xlibmesa-gl xlibmesa-gl-dev xlibmesa-glu xlibmesa-glu-dev xlibs-static-dev xlibs-static-pic xnest xserver-common xserver-xfree86 xterm xutils xvfb 57 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 72.8MB of archives. After unpacking 111MB of additional disk space will be used. Do you want to continue? [Y/n] 111MB of additional disk space just to upgrade my packages. So I looked package by package to see wich one was going to use such space. And I found: # apt-get install xserver-xfree86 Reading Package Lists... Done Building Dependency Tree... Done Suggested packages: libglide2 The following packages will be upgraded: xserver-xfree86 1 upgraded, 0 newly installed, 0 to remove and 57 not upgraded. Need to get 50.4MB of archives. After unpacking 113MB of additional disk space will be used. Right. My question is. Why is it taking so much space just to upgrade the package? I am not installing it. I am just doing an upgrade. # apt-cache policy xserver-xfree86 xserver-xfree86: Installed: 4.3.0.dfsg.1-10 Candidate: 4.3.0.dfsg.1-12 (...) I have release -10 installed and I am going to upgrade to release -12. Did it change so much to use 111MB of additional disk? Thank you Nelson -- Package-specific info: Contents of /var/lib/xfree86/X.roster: xserver-xfree86 /etc/X11/X target unchanged from checksum in /var/lib/xfree86/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 20 2003-07-14 15:12 /etc/X11/X -> /usr/bin/X11/XFree86 -rwxr-xr-x 1 root root 1745740 2004-12-15 17:19 /usr/bin/X11/XFree86 Contents of /var/lib/xfree86/XF86Config-4.roster: xserver-xfree86 VGA-compatible devices on PCI bus: :01:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev a4) /etc/X11/XF86Config-4 does not match checksum in /var/lib/xfree86/XF86Config-4.md5sum. XFree86 X server configuration file status: -rw-r--r-- 1 root root 4016 2005-01-24 16:57 /etc/X11/XF86Config-4 Contents of /etc/X11/XF86Config-4: # XFree86 4 configuration created by pyxf86config #Section "ServerLayout" # Identifier "Default Layout" # Screen 0 "Screen0" 0 0 # InputDevice"Mouse0" "CorePointer" # InputDevice"Keyboard0" "CoreKeyboard" # InputDevice"DevInputMice" "AlwaysCore" #EndSection Section "Files" FontPath"unix/:7100"# local font server # if the local font server has problems, we can fall back on these FontPath"/usr/lib/X11/fonts/Type1" FontPath"/usr/lib/X11/fonts/CID" # FontPath"/usr/lib/X11/fonts/Speedo" FontPath"/usr/lib/X11/fonts/misc" FontPath"/usr/lib/X11/fonts/cyrillic" FontPath"/usr/lib/X11/fonts/75dpi" FontPath"/usr/lib/X11/fonts/100dpi" # RgbPath is the location of the RGB database. Note, this is the name of the # file minus the extension (like ".txt" or ".db"). There is normally # no need to change the default. # Multiple FontPath entries are allowed (they are concatenated together) # By default, Red Hat 6.0 and later now use a font server independent of # the X server to render fonts. EndSection Section "Module" # Load"GLcore" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"record" # Load"speedo" Load"type1" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xkb" Option "XkbModel" "abnt2" Option "XkbLayout" "br" EndSection Section "InputDevice" # If the normal CorePointer mouse is not a USB mouse then # this input device can be used in AlwaysCore mode to let you # also use USB mice at the same time. Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/psaux" Option "Protocol" "ImPS/2"
