public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux PM <linux-pm@vger.kernel.org>,
	Andreas Noever <andreas.noever@gmail.com>,
	Michael Jamet <michael.jamet@intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [RFC][PATCH] thunderbolt: icm: Ignore mailbox errors in icm_suspend()
Date: Thu, 27 Jul 2017 11:50:11 +0300	[thread overview]
Message-ID: <20170727085011.GY2369@lahna.fi.intel.com> (raw)
In-Reply-To: <4165239.xHgWvuTePe@aspire.rjw.lan>

On Wed, Jul 26, 2017 at 07:05:01PM +0200, Rafael J. Wysocki wrote:
> On Wednesday, July 26, 2017 04:12:59 PM Mika Westerberg wrote:
> > On Wed, Jul 26, 2017 at 02:48:54PM +0200, Rafael J. Wysocki wrote:
> > > On Wednesday, July 26, 2017 11:32:44 AM Mika Westerberg wrote:
> > > > On Tue, Jul 25, 2017 at 06:10:57PM +0200, Rafael J. Wysocki wrote:
> > > > > On Tuesday, July 25, 2017 01:00:12 PM Mika Westerberg wrote:
> > > > > > On Tue, Jul 25, 2017 at 01:31:00AM +0200, Rafael J. Wysocki wrote:
> > > > > > > From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> > > > > > > 
> > > > > > > On one of my test machines nhi_mailbox_cmd() called from icm_suspend()
> > > > > > > times out and returnes an error which then is propagated to the
> > > > > > > caller and causes the entire system suspend to be aborted which isn't
> > > > > > > very useful.
> > > > > > > 
> > > > > > > Instead of aborting system suspend, print the error into the log
> > > > > > > and continue.
> > > > > > 
> > > > > > I agree, it should not prevent suspend but I wonder why it fails in the
> > > > > > first place? Can you check what is the return value?
> > > > > 
> > > > > As per the above, the error is a timeout, ie. -ETIMEDOUT.
> > > > 
> > > > Ah, right I somehow missed that.
> > > > 
> > > > Does it have Falcon Ridge controller or Alpine Ridge?
> > > 
> > > I'll check later today, but i guess you'll know (see below).
> > 
> > No need to check, it is Alpine Ridge (since it is Dell 9360).
> > 
> > > > Just to make sure, can you increase the timeout in nhi_mailbox_cmd()
> > > > to 1000ms or so. It should not take that long though but better to check.
> > > 
> > > Well, I can do that, but I don't think it will help.
> > > 
> > > It just looks like the chip is not responding at all at that point.
> > 
> > I see.
> > 
> > Then I think we should apply your patch now and we can investigate this
> > further offline and hopefully find the root cause for the problem.
> > 
> > For this patch:
> > 
> > Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> 
> OK
> 
> I guess I can apply it, then, or if anyone else in the CC wants to do that,
> please let me know.

Greg typically takes these but I'm fine either way.

(Eventually we should probably establish Thunderbolt tree/branch in
 kernel.org where we gather all Thunderbolt related patches and just send
 pull request to Greg or something like that).

> > > > Which system this is BTW?
> > > 
> > > It's the Dell 9360. :-)
> > > 
> > > Sometimes after a reboot or a power cycle it starts in a state in which the
> > > TBT controller and a USB one (which seem to be somehow connected)
> > > appear to be dead or at least really flaky.  Basically, the box needs to be
> > > power-cycled again to get rid of this condition and then everything works.
> > 
> > The xHCI controller is part of the Thunderbolt controller so whenever
> > you have normal USB-C device connected there, you should also see the
> > Alpine Ridge hierarchy in lspci output but the Thunderbolt host
> > controller is not there.
> 
> I don't have any USB-C devices, though, so I can't really test it this way ATM.
> 
> It's jjust never used now. :-)

OK. We have one 9365 which I think should be pretty similar. I'll give
it a try once I find it ;-)

  reply	other threads:[~2017-07-27  8:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24 23:31 [RFC][PATCH] thunderbolt: icm: Ignore mailbox errors in icm_suspend() Rafael J. Wysocki
2017-07-25 10:00 ` Mika Westerberg
2017-07-25 16:10   ` Rafael J. Wysocki
2017-07-26  8:32     ` Mika Westerberg
2017-07-26 12:48       ` Rafael J. Wysocki
2017-07-26 13:12         ` Mika Westerberg
2017-07-26 17:05           ` Rafael J. Wysocki
2017-07-27  8:50             ` Mika Westerberg [this message]
2017-07-27 23:56               ` Rafael J. Wysocki
2017-07-31  7:00             ` Jamet, Michael
2017-07-31  9:36               ` Andy Shevchenko
2017-07-31 16:01               ` Greg Kroah-Hartman

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=20170727085011.GY2369@lahna.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=andreas.noever@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=michael.jamet@intel.com \
    --cc=rjw@rjwysocki.net \
    /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