dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110822] booting with kernel version 5.1.0 or higher on RX 580 hangs
Date: Tue, 04 Jun 2019 18:54:21 +0000	[thread overview]
Message-ID: <bug-110822-502-a4EbkLvM3W@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110822-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1374 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=110822

--- Comment #7 from Gobinda Joy <gobinda.joy@gmail.com> ---
(In reply to Sylvain BERTRAND from comment #6)
> bisect is quite common in the git world. You'll find tons of tutorials on the
> web, namely you're good for a little bit of reading.
> Just don't forget to "git reset --hard" before calling "git bisect good|bad".
> (just performed a bisection on linux yesterday).

Figured out how to bisect but the problem is building the rpm packages to
install in my fedora system. As the guide they put out in wiki is almost 6
years old and the python script for building the kernel/modules rpm doesn't
work.

However I found the pre-built kernel packages at
https://koji.fedoraproject.org/koji/packageinfo?buildStart=0&packageID=8&buildOrder=-completion_time&tagOrder=name&tagStart=50#buildlist

I've tested the kernels from there. It seems they used the snapshot from
mainline tree.

I started from the working version 5.0.0 and tested all the kernels until the
problem occurred at version 5.1.0-0.rc3.git3.1.fc31.x86_64

I can bisect the kernel at that tag but can't build the rpm packages, have to
research further I guess.

Attached the logs from the problematic version and the immediate earlier
working version.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2461 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-06-04 18:54 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-03  9:37 [Bug 110822] booting with kernel version 5.1.0 or higher on RX 580 hangs bugzilla-daemon
2019-06-03  9:42 ` bugzilla-daemon
2019-06-03 22:03 ` bugzilla-daemon
2019-06-04  6:29 ` bugzilla-daemon
2019-06-04  6:44 ` bugzilla-daemon
2019-06-04  8:34 ` bugzilla-daemon
2019-06-04 13:35   ` sylvain.bertrand
2019-06-04 13:35 ` bugzilla-daemon
2019-06-04 18:54 ` bugzilla-daemon [this message]
2019-06-04 18:55 ` bugzilla-daemon
2019-06-04 18:56 ` bugzilla-daemon
2019-06-04 18:56 ` bugzilla-daemon
2019-06-04 18:57 ` bugzilla-daemon
2019-06-05  9:51 ` bugzilla-daemon
2019-06-05 11:47 ` bugzilla-daemon
2019-06-06 18:43 ` [Bug 110822] [Bisected]Booting " bugzilla-daemon
2019-06-10 11:09 ` bugzilla-daemon
2019-06-10 11:19 ` bugzilla-daemon
2019-06-10 11:27 ` bugzilla-daemon
2019-06-10 14:08 ` bugzilla-daemon
2019-06-10 15:00 ` bugzilla-daemon
2019-06-10 16:22 ` bugzilla-daemon
2019-06-11 14:44 ` bugzilla-daemon
2019-06-12  4:35 ` bugzilla-daemon
2019-06-12 18:30 ` bugzilla-daemon
2019-06-13  7:44 ` bugzilla-daemon
2019-06-28  9:44 ` bugzilla-daemon
2019-11-19  9:29 ` 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-110822-502-a4EbkLvM3W@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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