I've just seen it again, with a backtrace similar to my previous one
(i.e. DeleteInputDeviceRequest rather than i830_bind_memory). I don't
understand why libdbus and libhal are in the stack trace, though; are
these callbacks?
*** glibc detected *** /usr/X11R6/bin/X: free(): invalid next size
I'm now running with valgrind, using a slightly modified version of
Steve's script:
perseus:[~] cat /usr/bin/X
#!/bin/sh
savelog -c 7 /var/log/Xorg-valgrind.log
exec valgrind --error-limit=no --log-file=/var/log/Xorg-valgrind.log
X.valgrind-madness $@
I tried a single suspend/resume cycle and
I just saw this bug in a new circumstance: during installation using
Ubiquity on an Acer Aspire One with the following graphics chipset:
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express
Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel
The previous comment also means that this is not limited to 64-bit,
which was also common in the other reports.
** Description changed:
Binary package hint: xorg
- I have been experiencing X server crashes during suspend/resume testing,
- but no apport report was being left behind. The
** Attachment added: backtrace
http://launchpadlibrarian.net/24244032/%3A0.log.1
--
*** glibc detected *** free(): invalid next size (fast) for xf86Wakeup() call
https://bugs.launchpad.net/bugs/328035
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Here's a recipe for running your X server under valgrind that might be
helpful.
$ sudo dpkg-divert --local --rename --divert /usr/bin/X.valgrind-madness
/usr/bin/X
$ sudo tee /usr/bin/X
#!/bin/sh
exec valgrind --error-limit=no --log-file=/var/log/Xorg-valgrind.log
X.valgrind-madness $@
^D
$
Has anyone ever seen this happen outside of xf86Wakeup()?
It's curious that we always crash there, even though the point of
failure is generally in the logging functions (which are called many
other times). That points to the corruption happening sometime shortly
before.
--
*** glibc detected
I am having the same problem on up-to-date Kubuntu on x200s with Intel
graphics. If suspend is done by PowerDevil (KDE4 power manager), either
by closing lid or selecting Suspend from menu, I get KDM login screen
after resume.
If I start suspend from command line (sudo pm-suspend), resume works
I get this error in /var/log/kdm.log:
X: ../../src/i830_batchbuffer.h:78: intel_batch_emit_dword: Assertion
`pI830-batch_ptr != ((void *)0)' failed.
--
*** glibc detected *** free(): invalid next size (fast) for xf86Wakeup() call
https://bugs.launchpad.net/bugs/328035
You received this bug
On Mon, Mar 23, 2009 at 08:47:59PM -, Luka Renko wrote:
I get this error in /var/log/kdm.log:
X: ../../src/i830_batchbuffer.h:78: intel_batch_emit_dword: Assertion
`pI830-batch_ptr != ((void *)0)' failed.
You are experiencing a different bug; please file it separately with
ubuntu-bug
Submitted bug 347587. Sorry for cluttering this bug.
--
*** glibc detected *** free(): invalid next size (fast) for xf86Wakeup() call
https://bugs.launchpad.net/bugs/328035
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I'm definitely still seeing this with:
linux-image-2.6.28-11-generic 2.6.28-11.36
xserver-xorg-core 2:1.6.0-0ubuntu4
xserver-xorg-video-intel 2:2.6.3-0ubuntu2
Thanks to Kees' patch, I have the latest stack trace in the log (which
is
Hi,
I seem to have what Matt is describing in his last step (6). I'm not
watching movies and sleeping however, I rather work away with gajim,
terminator, firefox and thunderbird opened. Suspend by closing the lid
and then wake up by opening it in the next data centre (after
travelling). I've
I should also mention this crash isn't always the case. Haven't really
got any good statics on how often it happens either.
--
*** glibc detected *** free(): invalid next size (fast) for xf86Wakeup() call
https://bugs.launchpad.net/bugs/328035
You received this bug notification because you are a
Thanks to a patch from Kees Cook, users running current Jaunty should be
able to tell if they have this bug by checking /var/log/gdm:
xorg-server (2:1.6.0-0ubuntu4) jaunty; urgency=low
* Add 168_glibc_trace_to_stderr.patch:
- Catch glibc internal abort traces on stderr instead of to the
I have just confirmed that my X server still crashes with
2:2.6.3-0ubuntu2. The usual scenario is:
1. I watch a DVD using totem-xine
2. I close totem-xine
3. I suspend the laptop using Fn+F4
4. I go to sleep
5. In the morning, I resume the laptop using the power button
6. The screen flickers and
I should also mention that my usual setup is to use an external VGA
display, with the internal LCD switched off using xrandr.
--
*** glibc detected *** free(): invalid next size (fast) for xf86Wakeup() call
https://bugs.launchpad.net/bugs/328035
You received this bug notification because you are
After upgrading to xserver-xorg-video-intel 2:2.6.3-0ubuntu1 (the
version from the archive, not one built with an older toolchain), I have
so far been unable to reproduce the original crash. Matt, are you still
seeing this with 2.6.3?
--
*** glibc detected *** free(): invalid next size (fast)
On Fri, Mar 20, 2009 at 08:19:36AM -, Steve Langasek wrote:
After upgrading to xserver-xorg-video-intel 2:2.6.3-0ubuntu1 (the
version from the archive, not one built with an older toolchain), I have
so far been unable to reproduce the original crash. Matt, are you still
seeing this with
I was waiting for a new upstream version to be uploaded to jaunty, but Bryce
says even this may not be new
enough.
AFAIK, what's in jaunty now should be new enough. I put 2.4.5 in last
week. I found there was also a kernel dependency (which unfortunately I
think the kernel team just didn't
On Thu, Mar 19, 2009 at 01:03:57AM -, Bryce Harrington wrote:
I was waiting for a new upstream version to be uploaded to jaunty, but
Bryce says even this may not be new
enough.
AFAIK, what's in jaunty now should be new enough. I put 2.4.5 in last
week. I found there was also a
Okay, since it's sounding like the issue here is outside my normal
purview I'm de-assigning myself this bug. Sounds like it may not be
-intel either, but will leave it to someone else to assign it to the
correct package. I'll stay subscribed to follow the progress though, so
if there's anything
According to the upstream bug, this can cause subtle and unpredictable bugs
depending upon when the kernel interrupts this code.
yes, the comment was before the second fix was checked in; the
4.3.3-3ubuntu4 upload includes both checkins.
--
*** glibc detected *** free(): invalid next size
ok, I just had a crash with the rebuilt -1ubuntu1 version on resume from
suspend. So it looks as though this might be a bug with the *current*
toolchain. I'll try to rebuild the current version of the driver now
with the older toolchain instead.
--
*** glibc detected *** free(): invalid next
Suspecting a possible toolchain bug, I reviewed the relevant gcc
changes:
https://edge.launchpad.net/ubuntu/+source/gcc-4.3
It looks like -1ubuntu2 will have been built prior to:
gcc-4.3 (4.3.3-3ubuntu4) jaunty; urgency=low
* Fix PR target/39118 (wrong code on x86_64 with -O2 -fomit-frame-
On Fri, Mar 13, 2009 at 09:16:54AM -, Matt Zimmerman wrote:
Steve, if you don't have any problems with you current test case, I
think the next thing to try is a recompile of -1ubuntu5 with the current
toolchain.
Well, the problem is present in the -1ubuntu4 build also, and the build log
Yes, this bug has not recurred since I downgraded.
--
*** glibc detected *** free(): invalid next size (fast) for xf86Wakeup() call
https://bugs.launchpad.net/bugs/328035
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
The changes in 2:2.6.1-1ubuntu2 (http://launchpadlibrarian.net/22429963
/xserver-xorg-video-intel_2%3A2.6.1-1ubuntu1_2%3A2.6.1-1ubuntu2.diff.gz)
seem so innocuous, I wonder if there isn't some secondary effect here.
Maybe a toolchain problem? Does recompiling 2:2.6.1-1ubuntu1 still
produce a
I've rebuilt 1ubuntu1 here with current toolchain and am running it now.
So far, the hokey pokey routine hasn't caused it to crash, but it's also
only been an hour.
--
*** glibc detected *** free(): invalid next size (fast) for xf86Wakeup() call
https://bugs.launchpad.net/bugs/328035
You
Fwiw, the change in 1u2 has been in the upstream git tree as well for
some time now, and none of the referenced upstream bug #'s have further
chatter.
--
*** glibc detected *** free(): invalid next size (fast) for xf86Wakeup() call
https://bugs.launchpad.net/bugs/328035
You received this bug
Thanks for narrowing it to that. Given that it's been 5 days since the
last comment, am I correct in assuming with that version reverted, that
you're no longer seeing the issue?
--
*** glibc detected *** free(): invalid next size (fast) for xf86Wakeup() call
** Changed in: xorg-server (Ubuntu Jaunty)
Assignee: (unassigned) = Bryce (bryce)
** Changed in: xorg-server (Ubuntu Jaunty)
Assignee: Bryce (bryce) = Bryce Harrington (bryceharrington)
--
*** glibc detected *** free(): invalid next size (fast) for xf86Wakeup() call
Was going to bisect, then noticed that the first xserver-xorg-video-
intel version where I started seeing the problem had a changelog entry
describing a single fix related to switching video output - which is
precisely what appears to trigger the bug for me. Have downgraded to
2:2.6.1-1ubuntu1,
** Description changed:
Binary package hint: xorg
I have been experiencing X server crashes during suspend/resume testing,
but no apport report was being left behind. By stracing the X server, I
was able to see that this was due to glibc detecting heap corruption and
aborting the
Marked my bug (332347) as a duplicate of this one, and targeting to
jaunty.
--
*** glibc detected *** free(): invalid next size (fast) for xf86Wakeup() call
https://bugs.launchpad.net/bugs/328035
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This is still happening to me once out of every few resumes.
--
*** glibc detected *** free(): invalid next size (fast) for xf86Wakeup() call
https://bugs.launchpad.net/bugs/328035
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
After a couple of days of normal use (including suspend/resume), I
caught it in gdb. Again, the actual corruption may be happening
elsewhere, but at least we can see exactly where the server is dying.
Program received signal SIGABRT, Aborted.
0x7f7ccea1cfb5 in raise () from /lib/libc.so.6
** Summary changed:
- *** glibc detected *** free(): invalid next size (fast)
+ *** glibc detected *** free(): invalid next size (fast) for xf86Wakeup() call
--
*** glibc detected *** free(): invalid next size (fast) for xf86Wakeup() call
https://bugs.launchpad.net/bugs/328035
You received this
38 matches
Mail list logo
