From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 14535] Memory corruption detected in low memory
Date: Mon, 18 Jan 2010 14:29:22 GMT [thread overview]
Message-ID: <201001181429.o0IETMdB022927@demeter.kernel.org> (raw)
In-Reply-To: <bug-14535-2300@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=14535
--- Comment #8 from erki85@ut.ee 2010-01-18 14:29:19 ---
Tried mesa-git (+ati-dri-git and libgl-git) with xf86-video-ati-git today. Xorg
1.7.3.902.
With KMS enabled, glxgears's gears are red and green again (no blue) and
running etracer just produces blank screen. Although I can restart X and
continue normal working.
With KMS disabled, glxgears does not display error message about radeon_tcl.c
anymore, but running etracer locks up the system. I can sort of see the first
screen, which has "Press any key to continue", but the rest that should be
there is garbled. When I press any key X stops and I cannot close it. REISUB
works though this time (didn't before).
When I ran HOMM4 in wine, I got the usual Memory corruption detected in low
memory thingie. Couldn't restart X, couldn't REISUB.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
--
next prev parent reply other threads:[~2010-01-18 14:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14535-2300@http.bugzilla.kernel.org/>
2010-01-03 16:22 ` [Bug 14535] Memory corruption detected in low memory bugzilla-daemon
2010-01-09 23:03 ` bugzilla-daemon
2010-01-11 14:36 ` bugzilla-daemon
2010-01-17 23:51 ` bugzilla-daemon
2010-01-18 0:29 ` bugzilla-daemon
2010-01-18 0:59 ` bugzilla-daemon
2010-01-18 14:29 ` bugzilla-daemon [this message]
2010-01-19 1:26 ` bugzilla-daemon
2010-01-19 1:32 ` bugzilla-daemon
2010-01-19 1:38 ` bugzilla-daemon
2010-01-19 1:53 ` bugzilla-daemon
2010-01-19 2:19 ` bugzilla-daemon
2010-01-19 15:42 ` bugzilla-daemon
2010-01-19 16:01 ` bugzilla-daemon
2010-02-20 11:38 ` bugzilla-daemon
2010-02-22 13:44 ` bugzilla-daemon
2010-02-23 0:35 ` bugzilla-daemon
2010-02-23 1:32 ` bugzilla-daemon
2010-02-23 15:13 ` bugzilla-daemon
2010-02-24 0:50 ` bugzilla-daemon
2010-02-24 7:23 ` bugzilla-daemon
2010-02-24 7:24 ` bugzilla-daemon
2010-02-24 7:33 ` bugzilla-daemon
2010-02-24 9:25 ` bugzilla-daemon
2010-02-24 17:17 ` bugzilla-daemon
2010-02-24 17:25 ` bugzilla-daemon
[not found] <bug-14535-2300@https.bugzilla.kernel.org/>
2011-07-21 8:42 ` bugzilla-daemon
2012-06-14 16:43 ` bugzilla-daemon
2012-06-14 16:44 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201001181429.o0IETMdB022927@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.