From: Martin Kepplinger <martink@posteo.de>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joerg Roedel <jroedel@suse.de>
Cc: Linux kernel <linux-kernel@vger.kernel.org>,
torvalds@linux-foundation.org, daniel.vetter@intel.com
Subject: Re: [BUG][REGRESSION] mangled display since -rc1
Date: Sun, 6 Nov 2016 12:43:22 +0100 [thread overview]
Message-ID: <0f63c442-29c0-bcf7-2f0b-a2733eb7794b@posteo.de> (raw)
In-Reply-To: <27a0c8f9-0f1f-fa99-fc96-6c6fcba4bfe4@leemhuis.info>
Am 2016-11-06 um 12:21 schrieb Thorsten Leemhuis:
> On 01.11.2016 12:47, Jani Nikula wrote:
>> On Tue, 01 Nov 2016, Martin Kepplinger <martink@posteo.de> wrote:
>>> I'll come up with a nouveau system example and it was quite easy to bisect. To quote the merge commit msg:
>>> This also required some changes outside of the IOMMU code, but these are acked by the respective maintainers.
>>> Any help on bisecting into it would be awesome.
>> So the information here is pretty scarce. Please file a bug at [1],
>> describe the problem, perhaps add drm.debug=14 module parameter and
>> attach dmesg from boot to reproducing the problem.
>
> Martin, did you do that and can point me to the bug? And if not: Any
> news on the issue?
>
> FWIW: I added this report to the list of regressions for Linux 4.9. I'll
> watch this thread for further updates on this issue to document progress
> in my weekly reports. Please let me know via regressions@leemhuis.info
> in case the discussion moves to a different place (bugzilla or another
> mail thread for example).
>
> tia! Ciao, Thorsten
>
I did not file a bug in bugzilla yet. I haven't given up that we can fix
this here before the release. I've ignored it the last few days though.
Again: This is the first bad commit:
[56e520c7a0a490b63b042b047ec9659fc08762a4] Merge tag
'iommu-updates-v4.9' of
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu
If you know how to bisect into this, please share your thoughts. Linus'
merge here is bigger than iommu-update-v4.9 i think and that's what I
have to look at really. I'm not sure how though.
One part of the merge is indeed iiommu-updates-v4.9:
That's the tag:
https://git.kernel.org/cgit/linux/kernel/git/joro/iommu.git/tag/?h=iommu-updates-v4.9
and the tagged object:
https://git.kernel.org/cgit/linux/kernel/git/joro/iommu.git/commit/?h=iommu-updates-v4.9&id=13a08259187c5cd3f63d98efa159ab42976d85a4
I'll have to think about how to check the iommu-updates-v4.9 part of the
merge again... to eliminate something.
next prev parent reply other threads:[~2016-11-06 11:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 10:36 Martin Kepplinger
2016-10-31 10:40 ` 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 [this message]
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=0f63c442-29c0-bcf7-2f0b-a2733eb7794b@posteo.de \
--to=martink@posteo.de \
--cc=daniel.vetter@intel.com \
--cc=jani.nikula@linux.intel.com \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
--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
all inboxes | Powered by JetHome®