From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 23622] null-pointer deref in ttm_bo_reserve() during using KDE 4.5 compositing session with radeon kms
Date: Tue, 23 Nov 2010 21:09:09 GMT [thread overview]
Message-ID: <201011232109.oANL99xd024795@demeter2.kernel.org> (raw)
In-Reply-To: <bug-23622-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=23622
--- Comment #7 from Alex Deucher <alexdeucher@gmail.com> 2010-11-23 21:09:04 ---
You can try increasing your AGP aperture size in the bios, but there's not a
lot you can do if you run out of graphics memory other than trying to handle
things more gracefully.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
--
next prev parent reply other threads:[~2010-11-23 21:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 11:06 [Bug 23622] New: probably radeon kms / memory shortage related scheduling while atomic bugzilla-daemon
2010-11-23 12:32 ` [Bug 23622] " bugzilla-daemon
2010-11-23 20:05 ` bugzilla-daemon
2010-11-23 20:23 ` bugzilla-daemon
2010-11-23 20:29 ` [Bug 23622] null-pointer deref in ttm_bo_reserve() during using KDE 4.5 compositing session with radeon kms bugzilla-daemon
2010-11-23 20:41 ` bugzilla-daemon
2010-11-23 20:45 ` bugzilla-daemon
2010-11-23 20:47 ` bugzilla-daemon
2010-11-23 21:09 ` bugzilla-daemon [this message]
2010-11-24 10:52 ` bugzilla-daemon
2013-01-12 17:28 ` 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=201011232109.oANL99xd024795@demeter2.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox