All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vecu Bosseur <vecu.bosseur@gmail.com>
To: linux-pci@vger.kernel.org
Subject: [REGRESSION, bisect] Bug introduced within Linux 4.6 merge window, affecting at least x86_64 platform.
Date: Sun, 16 Oct 2016 10:13:58 +0200	[thread overview]
Message-ID: <CACivvv2MkD-QSmkt1yPzz9Lx1Lax5pQtc+W9_F0WM5LPziLvAQ@mail.gmail.com> (raw)

Hi,

It is more than 6 monthes I suffer from an unknown bug which seemed to
be a DRM or otherwise graphical bug affecting Linux 4.6-rcX on x86_64
platform. (unable to test on 32-bit platform)

For some unclear reason my AMD/ATI Radeon TURKS video card was not
initialized properly by those newer kernel versions.

I investigated hardly and found a "shallow" bug introduced by a commit
pair (sic.) :

cfeb8139a1fbbbae3f1e986133f4e9e7833eeac4
Merge branch 'pci/host-hv' into next

and

30b5b8808c12bcd947dd474980482561b69c1bcb
PCI: Restore inclusion of pci/hotplug Kconfig

I bet though this bug was hiding another real "deeper" bug, which proved right.
Here follows my findings :

In the end, I found that the real first bad commit for the bug we are
talking about is :

[0c0e0736acad4e76e718456c75d78ad95eea0011] PCI: Set ROM shadow
location in arch code, not in PCI core

I already opened a ticket for this as bug #175391 on bugzilla.kernel.org
( https://bugzilla.kernel.org/show_bug.cgi?id=175391 )
and advise you to read it in its entirety.

Since I first suffered from it while using Ubuntu with "Mainline PPA
Kernel", I also reported it as bug #1627496 on bugs.launchpad.net .
( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627496 )

Since I fed plenty of details on bugzilla, I won't copy/paste them
here, obviously.

Any comment or suggestion much appreciated.

In hope this helps.

Sincerely,
Valentin QUEQUET

                 reply	other threads:[~2016-10-16  8:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CACivvv2MkD-QSmkt1yPzz9Lx1Lax5pQtc+W9_F0WM5LPziLvAQ@mail.gmail.com \
    --to=vecu.bosseur@gmail.com \
    --cc=linux-pci@vger.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.