From: Martin Kepplinger <martink@posteo.de>
To: jroedel@suse.de
Cc: Linux kernel <linux-kernel@vger.kernel.org>,
torvalds@linux-foundation.org
Subject: [BUG][REGRESSION] mangled display since -rc1
Date: Mon, 31 Oct 2016 11:36:11 +0100 [thread overview]
Message-ID: <da26da99edcd68c05ef63a28749eff37@posteo.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
so guys,
I can't believe that nobody hits this: Since -rc1 Nautilus' list of
elements or Firefox' website window or just photos in eog (probably
among many more things) is mangled. Please have a look at the screenshot
of nautilus.
This is the same on a i3 laptop with intel graphics and a i7 with nouvau
graphics. I bisected and the problem is this merge:
first bad commit: [56e520c7a0a490b63b042b047ec9659fc08762a4] Merge tag
'iommu-updates-v4.9' of
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu
Two things I'd ask of you if this isn't already a known problem to you:
* I failed bisecting into this merge but I could easily have tried it
totally wrong, so I'd appreciate any advice on how to bisect into this.
Strangely, running joro's
https://git.kernel.org/cgit/linux/kernel/git/joro/iommu.git/commit/?h=iommu-updates-v4.9&id=13a08259187c5cd3f63d98efa159ab42976d85a4
(referenced here:
https://git.kernel.org/cgit/linux/kernel/git/joro/iommu.git/tag/?h=iommu-updates-v4.9)
is good (?)
* Please add anybody you know is involved to CC.
I'm happy to test patches too, of course.
Anyhow. This is a bad regression that prevents me from running 4.9. Just
so you know.
so long,
martin
[-- Attachment #2: nautilus_mangled.png --]
[-- Type: image/png, Size: 58905 bytes --]
next reply other threads:[~2016-10-31 10:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 10:36 Martin Kepplinger [this message]
2016-10-31 10:40 ` [BUG][REGRESSION] mangled display since -rc1 Martin Kepplinger
2016-10-31 15:21 ` Joerg Roedel
2016-10-31 20:44 ` Martin Kepplinger
2016-10-31 21:54 ` Joerg Roedel
2016-11-01 11:27 ` Martin Kepplinger
2016-11-01 11:47 ` Jani Nikula
2016-11-06 11:21 ` Thorsten Leemhuis
2016-11-06 11:43 ` Martin Kepplinger
2016-11-06 13:02 ` Martin Kepplinger
2016-11-07 8:24 ` Jani Nikula
2016-11-07 15:34 ` Martin Kepplinger
2016-11-07 16:01 ` Martin Steigerwald
2016-11-07 16:07 ` Martin Kepplinger
2016-11-07 17:36 ` Jani Nikula
2016-11-13 21:32 ` Martin Kepplinger
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=da26da99edcd68c05ef63a28749eff37@posteo.de \
--to=martink@posteo.de \
--cc=jroedel@suse.de \
--cc=linux-kernel@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 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.