From: Jerome Glisse <jglisse@redhat.com>
To: Krzysztof Grygiencz <kfgz@interia.pl>
Cc: dan.j.williams@intel.com, akpm@linux-foundation.org,
dri-devel@lists.freedesktop.org, hch@lst.de,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
logang@deltatee.com, stable@vger.kernel.org,
torvalds@linux-foundation.org
Subject: Re: [PATCH v8 3/7] mm, devm_memremap_pages: Fix shutdown handling
Date: Mon, 11 Feb 2019 14:57:07 -0500 [thread overview]
Message-ID: <20190211195706.GE3908@redhat.com> (raw)
In-Reply-To: <30d86b36-8421-f899-205e-4b9c6a5fcc9d@interia.pl>
On Sun, Feb 10, 2019 at 12:09:08PM +0100, Krzysztof Grygiencz wrote:
> Dear Sir,
>
> I'm using ArchLinux distribution. After kernel upgrade form 4.19.14 to
> 4.19.15 my X environment stopped working. I have AMD HD3300 (RS780D)
> graphics card. I have bisected kernel and found a failing commit:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v4.19.20&id=ec5471c92fb29ad848c81875840478be201eeb3f
This is a false positive, you should skip that commit. It will not impact
the GPU driver for your specific GPUs. My advice is to first bisect on
drivers/gpu/drm/radeon only.
Cheers,
Jérôme
next prev parent reply other threads:[~2019-02-11 19:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-10 11:09 [PATCH v8 3/7] mm, devm_memremap_pages: Fix shutdown handling Krzysztof Grygiencz
2019-02-11 19:57 ` Jerome Glisse [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-20 23:12 [PATCH v8 0/7] mm: Merge hmm into devm_memremap_pages, mark GPL-only Dan Williams
2018-11-20 23:13 ` [PATCH v8 3/7] mm, devm_memremap_pages: Fix shutdown handling Dan Williams
2018-11-27 21:43 ` Logan Gunthorpe
2018-11-29 3:10 ` Dan Williams
2018-11-29 17:06 ` Logan Gunthorpe
2018-11-29 17:30 ` Dan Williams
2018-11-29 17:50 ` Logan Gunthorpe
2018-11-29 18:51 ` Dan Williams
2018-11-30 22:19 ` Logan Gunthorpe
2018-11-30 22:28 ` Dan Williams
2018-11-30 22:34 ` Logan Gunthorpe
2018-11-30 22:47 ` Dan Williams
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=20190211195706.GE3908@redhat.com \
--to=jglisse@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@lst.de \
--cc=kfgz@interia.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=logang@deltatee.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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).