dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109345] drm-next-2018-12-14 -Linux PPC
Date: Thu, 09 May 2019 11:52:24 +0000	[thread overview]
Message-ID: <bug-109345-502-WH9XspBdzk@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109345-502@http.bugs.freedesktop.org/>


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

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

--- Comment #39 from Christian Zigotzky <chzigotzky@xenosoft.de> ---
Hi All,

Allan has successfully tested the eleventh test kernel.

He wrote:

Christian
DRM11 boots to Firepro.

ace

------

We have a result!

git bisect good

The following commit is responsible for the issue:

3d42f1ddc47a69c0ce155f9f30d764c4d689a5fa is the first bad commit
commit 3d42f1ddc47a69c0ce155f9f30d764c4d689a5fa
Author: Aaron Ma <aaron.ma@canonical.com>
Date:   Sat Sep 1 02:20:00 2018 +0800

    vgaarb: Keep adding VGA device in queue

    If failed to find the deivice owning the boot framebuffer,
    try to use the first VGA device instead of the last one.

    Usually the 1st device is integrated GPU who owns the boot framebuffer.

    Signed-off-by: Aaron Ma <aaron.ma@canonical.com>
    Acked-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
    Link:
https://patchwork.freedesktop.org/patch/msgid/1535739600-8842-2-git-send-email-aaron.ma@canonical.com

:040000 040000 2d69570b87946ba42095609c945f04de9ad24ef7
3d86752f71500726f20d7d503128119f9b249175 M   drivers

------

I undid these changes in the file 'drivers/gpu/vga/vgaarb.c' and created
another test kernel today.

Download: http://www.xenosoft.de/linux-image-5.2-alpha2-X1000_X5000.tar.gz

You can undo the commit with the following patch:

diff -rupN a/drivers/gpu/vga/vgaarb.c b/drivers/gpu/vga/vgaarb.c
--- a/drivers/gpu/vga/vgaarb.c    2019-05-09 07:56:27.595746473 +0200
+++ b/drivers/gpu/vga/vgaarb.c    2019-05-09 08:00:06.352660688 +0200
@@ -725,7 +725,7 @@ static bool vga_arbiter_add_pci_device(s
     vga_arbiter_check_bridge_sharing(vgadev);

     /* Add to the list */
-    list_add_tail(&vgadev->list, &vga_list);
+    list_add(&vgadev->list, &vga_list);
     vga_count++;
     vgaarb_info(&pdev->dev, "VGA device added: decodes=%s,owns=%s,locks=%s\n",
         vga_iostate_to_str(vgadev->decodes),

------

@Allan (acefnq/ace)
Please test it.

Thanks,
Christian

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

[-- Attachment #1.2: Type: text/html, Size: 3442 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-05-09 11:52 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-14  7:34 [Bug 109345] drm-next-2018-12-14 -Linux PPC bugzilla-daemon
2019-01-14 10:49 ` bugzilla-daemon
2019-01-15  7:55 ` bugzilla-daemon
2019-03-24  8:38 ` bugzilla-daemon
2019-03-25 14:25 ` bugzilla-daemon
2019-03-30  7:21 ` bugzilla-daemon
2019-04-01 16:05 ` bugzilla-daemon
2019-04-02  7:44 ` bugzilla-daemon
2019-04-02  8:35 ` bugzilla-daemon
2019-04-02 14:03 ` bugzilla-daemon
2019-04-11  7:24 ` bugzilla-daemon
2019-04-11  7:27 ` bugzilla-daemon
2019-04-29 14:04 ` bugzilla-daemon
2019-04-29 14:19 ` bugzilla-daemon
2019-04-30  7:19 ` bugzilla-daemon
2019-04-30  7:29 ` bugzilla-daemon
2019-04-30 16:00 ` bugzilla-daemon
2019-05-01 14:44 ` bugzilla-daemon
2019-05-01 14:54 ` bugzilla-daemon
2019-05-01 15:00 ` bugzilla-daemon
2019-05-01 16:06 ` bugzilla-daemon
2019-05-01 17:00 ` bugzilla-daemon
2019-05-01 17:04 ` bugzilla-daemon
2019-05-01 18:47 ` bugzilla-daemon
2019-05-02  3:44 ` bugzilla-daemon
2019-05-02  7:56 ` bugzilla-daemon
2019-05-02 21:47 ` bugzilla-daemon
2019-05-03 11:00 ` bugzilla-daemon
2019-05-03 16:37 ` bugzilla-daemon
2019-05-04 21:23 ` bugzilla-daemon
2019-05-05 10:14 ` bugzilla-daemon
2019-05-05 14:17 ` bugzilla-daemon
2019-05-06  8:09 ` bugzilla-daemon
2019-05-06 10:52 ` bugzilla-daemon
2019-05-07 21:08 ` bugzilla-daemon
2019-05-07 21:18 ` bugzilla-daemon
2019-05-08  7:08 ` bugzilla-daemon
2019-05-08 11:13 ` bugzilla-daemon
2019-05-09 10:04 ` bugzilla-daemon
2019-05-09 11:52 ` bugzilla-daemon [this message]
2019-05-10  3:45 ` bugzilla-daemon
2019-05-10 14:15 ` bugzilla-daemon
2019-05-10 15:39 ` bugzilla-daemon
2019-05-11  4:47 ` bugzilla-daemon
2019-05-11  4:51 ` bugzilla-daemon
2019-05-13  9:37 ` bugzilla-daemon
2019-05-13 14:20 ` bugzilla-daemon
2019-05-27  1:54 ` bugzilla-daemon
2019-06-03  8:42 ` bugzilla-daemon
2019-08-06  2:23 ` 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-109345-502-WH9XspBdzk@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;
as well as URLs for NNTP newsgroup(s).