All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 14535] Memory corruption detected in low memory
Date: Tue, 23 Feb 2010 15:13:57 GMT	[thread overview]
Message-ID: <201002231513.o1NFDvJi012006@demeter.kernel.org> (raw)
In-Reply-To: <bug-14535-2300@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=14535





--- Comment #24 from Gary <gary.pajer@gmail.com>  2010-02-23 15:13:46 ---
I'm more than willing to help, but I need some help with implementation and
reporting.  And it'll take a couple of days to find time.

Me, summary:  Kubuntu 9.10,  Thinkpad T41, Radeon Mobility 7500. Excerpt from
xorg.conf in Comment #15 above. I've tried mesa 7.6.0, 7.7, and 7.5, and
kernels 2.6.32, 2.6.31-19, 2.6.31-14.  Mostly from packages that someone else
compiled, and not every possible combination.  I get file system corruption
almost always.  The exception: Mesa 7.5 appears to be corruption-free, but it
introduced something annoying but unrelated to this issue ... can't recall what
right now.  I'm considering downgrading to 7.5 again.

1. Page flipping:  I'm using EXA, so I think that means no page flipping.
2. Need an open app?  I've gotten crashes with just about every 3D program I've
tried.  For testing, I've been using google earth and vpython
(www.vpython.org). I'll find another if you want.

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--

  parent reply	other threads:[~2010-02-23 15:13 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
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 [this message]
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=201002231513.o1NFDvJi012006@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.