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: Wed, 06 Feb 2019 23:56:18 +0000 [thread overview]
Message-ID: <bug-202511-2300-Zlqlv7motQ@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 #5 from Bjorn Helgaas (bhelgaas@google.com) ---
The bisect log in comment #3 shows 3a3869f1c443 ("Merge tag 'pci-v4.18-changes'
of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci") as the first bad
commit. That's a large merge commit so I can't pick out anything useful. The
previous good commit was 3036bc45364f ("Merge tag 'media/v4.18-2' of
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media").
I'm not a bisect expert, but there must be a way to bisect between those two
commits to zero in on something specific. Is this any help?
05:49:21 ~/linux (junk)$ git bisect start
05:49:47 ~/linux (junk|BISECTING)$ git bisect good
3036bc45364f98515a2c446d7fac2c34dcfbeff4
05:50:01 ~/linux (junk|BISECTING)$ git bisect bad
3a3869f1c443383ef8354ffa0e5fb8df65d8b549
Bisecting: 88 revisions left to test after this (roughly 6 steps)
[13fbadcd512c225c907d6e8147fb48a88114bf03] Merge branch 'pci/sparc'
--
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-06 23:56 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 [this message]
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
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-Zlqlv7motQ@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).