fixed 688082 xserver-xorg-video-nouveau/1:1.0.10-1
thanks
fastercrash doesn't succeed to kill jessie's X on my machine.
Cheers,
Thiemo
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://li
found xserver-xorg-video-nouveau/1:1.0.1-5
retitle 688082 xserver-xorg-video-nouveau: X server crashes when
attemping to display large images
thanks
I can reproduce this bug using eog to display an image larger than
3138x3138 pixels on:
05:00.0 VGA compatible controller: NVIDIA Corporation NV44 [
On 03/06/2011 08:07 PM, Cyril Brulebois wrote:
thanks. Could you please get a full backtrace from that core?
It's attached.
Cheers,
Thiemo
#0 0xb778e424 in __kernel_vsyscall ()
No symbol table info available.
#1 0xb74cc751 in *__GI_raise (sig=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
reopen 582456
found 582456 2:2.13.0-6
thanks
Dear KiBi,
I've been very busy in the last months and as a consequence didn't pay
attention to X crashes. But looking in /etc/X11 today I've found a core
file that's only 3 days old. I've attached the corresponding server
logfile.
I'm running li
On 06/06/2010 07:53 PM, Julien Cristau wrote:
The crash log was from an earlier version of the driver. Did you
ever reproduce the crash?
Not yet.
If so it would be good to get a backtrace from gdb, either by
attaching gdb to Xorg from ssh, or getting X to dump core (the -core
command line op
close 576751
thanks
With the recent kernel, I can't reproduce the problem anymore.
Cheers!
Thiemo
--
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/4bcd9c3a.1020...@goog
On 04/07/2010 07:04 AM, Brice Goglin wrote:
First thing to do is to use linux-image-2.6.32-4-686 since it contains
many DRM updates (from 2.6.32.x and 2.6.33)
Thank you, somehow I missed that. Will install and report back.
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a
On 02/06/2010 10:06 PM, Chris Burkhardt wrote:
Disabling kernel mode setting seems to have fixed things for me:
$ cat /etc/modprobe.d/i915-kms.conf
options i915 modeset=0
Works like a charm.
Thank you!
Thiemo
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of
howing one suspend/resume cycle with the intel driver.
Let me know, if you need more info.
Cheers!
Thiemo Nagel
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'proposed-updates'), (500,
'oldstable-pro
Funny thing I only notice this now: The patch above indeed is really
bad, it kills all key repeating. :-)
Thiemo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
be cured (cf. attached patch) in a haphazard way by always
returning 0 in AccessXRepeatKeyExpire(), which of course will break
something else (filterkeys?), but works well for me.
Kind regards,
Thiemo Nagel
--
+-+-+
| TU Muenchen |
I patched (see attachment) xserver-xorg-input-keyboard's kbd.c to log
the input that it's getting from the kernel. To me, kernel input looks
valid, so I think the X server is messing things up.
For example the following input to kbd.c
[1225291057.843404] kbd driver rec scancode: 0x022 down
[1
Another thing: Even though gdm respawns a new X server, something more
profound breaks in the process of crashing. The new X server isn't
stable anymore, for example using Ctrl-Alt-# to switch to a different VT
leads to a crash most of the time.
Might be related to the truncated backtrac
create a backtrace as the word "Backtrace:"
is the last thing
to be found in /var/log/Xorg.0.log, but that attempt seems to have failed.
I'm willing to investigate further if I get a little guidance.
Kind regards,
Thiemo Nagel
-- System Information:
Debian Release: lenny/sid
APT
14 matches
Mail list logo
