No subject
Tue Aug 24 12:13:45 PDT 2010
(E17 init)
E17 INIT: XINERAMA CHOSEN: [1], 1080x1920+1280+0
E17 INIT: XINERAMA CHOSEN: [0], 1280x1024+0+896
(output blinking starts)
E17 INIT: XINERAMA SCREEN: [0], 1280x1024+0+0
E17 INIT: XINERAMA CHOSEN: [153045780], 0x153045764+0+153046580
(e17 crash, try to recover)
E17 INIT: XINERAMA CHOSEN: [1], 1920x1080+1280+0
E17 INIT: XINERAMA CHOSEN: [0], 1280x1024+0+0
(rotation lost on [1], position lost on [0])
E17 INIT: XINERAMA CHOSEN: [1], 1080x1920+1280+0
E17 INIT: XINERAMA CHOSEN: [141138596], 0x141138580+0+141139396
E17 INIT: XINERAMA CHOSEN: [0], 1280x1024+0+896
(restoring rotation confuses E17)
###!!! ABORT: X_CreatePixmap: BadAlloc (insufficient resources for
operation);
6 requests ago: file nsX11ErrorHandler.cpp, line 182
UNKNOWN [/usr/lib/xulrunner-1.9.2/libxul.so +0x001CA781]
(firefox crashing)
Now, the reason for the E17 crash looks like a use-after-free bug. Question is:
who is freeing the Xinerama structures, and why are they freed at all? I never
had these problems before, and when using stock 2.6.32 (from Debian) I don't
have these problems either, so I'm ruling out hardware failure.
I can see the following lines logged by the kernel (KMS enabled on radeon
9550):
[12045.280155] [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a monitor but
no|invalid EDID
[13500.386132] [drm:radeon_vga_detect] *ERROR* VGA-1: probed a monitor but
no|invalid EDID
[13797.568760] [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a monitor but
no|invalid EDID
And I believe these are harmless (and reported in #27708). I can see these
messages being reported for as long my kernel logs go back. But when the
crashes occur, they are followed by these lines:
[35753.097508] i2c i2c-1: sendbytes: NAK bailout.
[35762.752866] i2c i2c-1: sendbytes: NAK bailout.
[35772.912023] i2c i2c-1: readbytes: ack/nak timeout
Which I believe are not so harmless. Or they could be a red herring, I'm not
qualified to tell.
Since the same time, I've been seeing a lot of lines logged by g-s-d, like
gdk_pixbuf_format_get_name: assertion `format != NULL' failed
But I do not believe these are relevant.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the dri-devel
mailing list