All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon--- via dri-devel <dri-devel@lists.freedesktop.org>
To: dri-devel@lists.freedesktop.org
Subject: [Bug 202511] amdgpu fails to load saying "Could not allocate 8192 bytes percpu data"
Date: Thu, 14 Feb 2019 19:00:41 +0000	[thread overview]
Message-ID: <bug-202511-2300-2qDvaBE4S7@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 #15 from Bjorn Helgaas (bhelgaas@google.com) ---
Created attachment 281143
  --> https://bugzilla.kernel.org/attachment.cgi?id=281143&action=edit
per-cpu alloc debug patch

I think bisecting again would be a poor use of your time unless somebody knows
a smarter way to do it (I don't).

I suspect amdgpu might be an innocent bystander.  I don't have any good ideas,
so here's a lame one:

  - Apply this patch.
  - Figure out how to turn on pr_debug (see include/linux/printk.h and compare
with your config -- you might need to enable CONFIG_DYNAMIC_DEBUG and and then
figure out what boot parameter enables the output).  This is to turn on the
debug in module_load().  Actually, the simpler way is to change those
pr_debug() calls to pr_info().
  - Collect the dmesg log (probably large).

-- 
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

  parent reply	other threads:[~2019-02-14 19:00 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
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 [this message]
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-2qDvaBE4S7@https.bugzilla.kernel.org/ \
    --to=dri-devel@lists.freedesktop.org \
    --cc=bugzilla-daemon@bugzilla.kernel.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 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.