From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36072] celestia causes kernel oops when allocation a lot of memory (for textures)
Date: Wed, 28 Feb 2018 21:12:29 +0000 [thread overview]
Message-ID: <bug-36072-2300-5q3qz6ufTy@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-36072-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=36072
aceman (acelists@atlas.sk) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |OBSOLETE
--- Comment #11 from aceman (acelists@atlas.sk) ---
I no longer have that particular GPU but I also haven't seen the problem in
ages. I added the vmalloc argument to the kernel cmdline, that may also have
helped.
With the recent amdgpu kernel driver I am trying to run without this argument
and haven't seen any problems with Celestia yet. I also have 4GB of VRAM on a
Polaris11 GPU now.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2018-02-28 21:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-28 10:52 [Bug 36072] New: celestia causes kernel oops when allocation a lot of memory (for textures) bugzilla-daemon
2011-05-28 10:53 ` [Bug 36072] " bugzilla-daemon
2011-08-30 18:15 ` bugzilla-daemon
2011-08-31 10:22 ` bugzilla-daemon
2011-08-31 10:53 ` bugzilla-daemon
2011-08-31 11:04 ` bugzilla-daemon
2011-08-31 18:19 ` bugzilla-daemon
2012-08-24 12:44 ` bugzilla-daemon
2012-08-30 15:32 ` bugzilla-daemon
2013-12-23 13:37 ` bugzilla-daemon
2013-12-23 14:36 ` bugzilla-daemon
2013-12-23 21:55 ` bugzilla-daemon
2018-02-28 21:12 ` bugzilla-daemon [this message]
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=bug-36072-2300-5q3qz6ufTy@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/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;
as well as URLs for NNTP newsgroup(s).