From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 202511] amdgpu fails to load saying "Could not allocate 8192 bytes percpu data"
Date: Thu, 07 Feb 2019 17:33:19 +0000 [thread overview]
Message-ID: <bug-202511-2300-jGgjoDtIdU@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202511-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=202511
--- Comment #8 from Bjorn Helgaas (bhelgaas@google.com) ---
Even if this is "special", e.g., some strange kconfig or build/install issue,
this is a really painful issue to debug. It would be tremendous if we could
fail more gracefully, with some hint about what went wrong and how the user
could fix it. But it's hard to know how we could improve that until we
understand what's going on here.
--
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
next prev parent reply other threads:[~2019-02-07 17:33 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 18:06 [Bug 202511] New: amdgpu fails to load saying "Could not allocate 8192 bytes percpu data" bugzilla-daemon
2019-02-06 1:18 ` [Bug 202511] " bugzilla-daemon
2019-02-06 1:19 ` bugzilla-daemon
2019-02-06 23:06 ` bugzilla-daemon
2019-02-06 23:23 ` bugzilla-daemon
2019-02-06 23:56 ` bugzilla-daemon
2019-02-07 7:42 ` bugzilla-daemon
2019-02-07 16:46 ` bugzilla-daemon
2019-02-07 17:33 ` bugzilla-daemon [this message]
2019-02-07 19:17 ` bugzilla-daemon
2019-02-08 14:06 ` bugzilla-daemon
2019-02-08 14:15 ` bugzilla-daemon
2019-02-08 14:17 ` bugzilla-daemon
2019-02-12 2:20 ` bugzilla-daemon--- via dri-devel
2019-02-14 13:52 ` bugzilla-daemon--- via dri-devel
2019-02-14 19:00 ` bugzilla-daemon--- via dri-devel
2019-02-20 20:48 ` bugzilla-daemon
2019-02-21 19:59 ` bugzilla-daemon
2019-02-21 20:05 ` bugzilla-daemon
2019-02-21 20:06 ` bugzilla-daemon
2019-02-21 21:57 ` bugzilla-daemon
2019-02-21 22:21 ` bugzilla-daemon
2019-02-22 15:34 ` bugzilla-daemon
2019-02-22 15:57 ` bugzilla-daemon
2019-02-25 20:25 ` bugzilla-daemon
2019-02-26 16:20 ` bugzilla-daemon
2019-02-26 16:34 ` bugzilla-daemon
2019-02-26 16:59 ` bugzilla-daemon
2019-02-26 17:31 ` bugzilla-daemon
2019-02-26 18:41 ` bugzilla-daemon
2019-02-26 23:54 ` 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=bug-202511-2300-jGgjoDtIdU@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).