From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 14535] Memory corruption detected in low memory
Date: Sat, 9 Jan 2010 23:03:49 GMT [thread overview]
Message-ID: <201001092303.o09N3nwb031727@demeter.kernel.org> (raw)
In-Reply-To: <bug-14535-2300@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=14535
Torsten Landschoff <torsten@debian.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |torsten@debian.org
--- Comment #3 from Torsten Landschoff <torsten@debian.org> 2010-01-09 23:03:45 ---
I still have this problem as well, but I originally ran into this with a 2.6.24
kernel (with OpenVZ support). I first blamed it on my old + patched kernel, but
upgrading the kernel did not resolve the problems.
So I'd expect it to be either a bug in Mesa or some kernel bug only exposed
with latest Mesa changes.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
--
next prev parent reply other threads:[~2010-01-09 23:03 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 [this message]
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
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=201001092303.o09N3nwb031727@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.