From: Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
To: Jiang Liu <jiang.liu-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Cc: Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>,
Ingo Molnar <mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Regression in v4.2-rc1 caused by hierarchical irqdomain changes
Date: Mon, 27 Jul 2015 16:21:07 +0100 [thread overview]
Message-ID: <20150727152107.GA3571@codeblueprint.co.uk> (raw)
A git bisect just pointed me at commit d32932d02e18 ("x86/irq: Convert
IOAPIC to use hierarchical irqdomain interfaces") as the reason for why
the trackpad on my Dell XPS13 is no longer working with v4.2-rc1.
I'm now seeing the following errors when booting,
[ 1.615017] i2c_designware INT3433:00: controller timed out
[ 1.642496] i2c_designware INT3433:00: timeout in disabling adapter
[ 1.642500] i2c_hid i2c-DLL0665:01: hid_descr_cmd failed
I tried commit d32932d02e18~1, which works, and things definitely break
starting with commit d32932d02e18.
Any suggestions or requests to try and diagnose why the irqdomain
changes broke this i2c controller driver?
--
Matt Fleming, Intel Open Source Technology Center
next reply other threads:[~2015-07-27 15:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 15:21 Matt Fleming [this message]
[not found] ` <20150727152107.GA3571-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2015-07-27 16:35 ` Regression in v4.2-rc1 caused by hierarchical irqdomain changes Jiang Liu
[not found] ` <55B65DD8.9020002-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2015-07-27 21:15 ` Matt Fleming
[not found] ` <20150727211502.GA2492-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2015-07-29 21:03 ` Thomas Gleixner
2015-07-30 4:08 ` Jiang Liu
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=20150727152107.GA3571@codeblueprint.co.uk \
--to=matt-mf/unelci9gs6ibeejttw/xrex20p6io@public.gmane.org \
--cc=hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
--cc=jiang.liu-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.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).