linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Mario Limonciello <mario.limonciello@dell.com>,
	Mathias Nyman <mathias.nyman@intel.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
	andreas.noever@gmail.com, michael.jamet@intel.com,
	YehezkelShB@gmail.com, ck@xatom.net,
	linux-kernel@vger.kernel.org,
	Anthony Wong <anthony.wong@canonical.com>
Subject: Re: USB devices on Dell TB16 dock stop working after resuming
Date: Wed, 5 Feb 2020 14:10:38 +0100	[thread overview]
Message-ID: <e9205ed2-68d2-e08d-2a50-00fe17a08a29@molgen.mpg.de> (raw)
In-Reply-To: <20ad18e8-08ca-f62a-dd7b-cdd671dcd997@molgen.mpg.de>


Dear Mario, dear Mathias,


Am 27.01.20 um 23:16 schrieb Paul Menzel:

> Am 18.01.20 um 10:15 schrieb Paul Menzel:
> 
>> Am 17.01.20 um 19:33 schrieb Mario.Limonciello@dell.com:
>>>>> I was able to reproduce the issue with an external HS hub as well, 
>>>>> so  this issue appears to be more related to ASMedia host
>>>>> than the built in HS hub in TB16
>>>>
>>>> I contacted the (German) Dell support, and they asked me to
>>>> update the laptop firmware to 1.9.1 claiming that these issues
>>>> might be fixed there (despite the change-log not containing
>>>> that). Anyway, after the update, the user is still able to
>>>> reproduce the issue.
>>>>
>>>> Mario, what can I do, so the issue is escalated to your team, so you 
>>>> can work with ASMedia to solve this?
>>
>>> From this thread it does sound to me like an ASMedia firmware problem,
>>> not a Linux kernel problem.
>>>
>>> I do know there is an updated ASMedia firmware binary available. 
>>> Right now however there is unfortunately not a way to update
>>> ASMedia hub firmware using free software.
>>
>> The fwupd issue *Dell TB16: ASMedia USB controller can't be updated* 
>> [1] was closed by the “stale robot”.
>>
>>> If possible, I would recommend that you try to update the
>>> firmware using a Windows machine and see if it helps the problem.
>>
>> Thank you. I’ll try to do that on Monday.
>>
>>> I'm sorry and I don't intend to "pass the buck" but if that doesn't 
>>> help this needs to be prioritized and escalated with Dell support.
>>>
>>> They will then work with the appropriate engineering team who owns 
>>> the relationship to ASMedia to resolve it.
>>
>> That’s how it should work theoretically, but have you ever dealt with 
>> Dell’s first level support? They have little experience with Ubuntu, 
>> and if you are unlucky, they say that Ubuntu support is not done by 
>> Dell but “by the Linux community”. If you are lucky to not get this 
>> answer, they do (Google) searches, telling you, your problem is solved 
>> by referencing only similar sounding problems from the Ubuntu *user* 
>> forums. If the firmware has a bug (in the UI!), they ask you to 
>> install Microsoft Windows to see if that solves the issue. If you tell 
>> them, the Linux developers analyzed the problem, and they say the 
>> following solution have to be found, they do not know what that means. 
>> It’s very annoying and time consuming often for naught.
> 
> As reported in [1], updating the Dell TB16 firmware using a *Dell* 
> laptop (with updated firmware and Thunderbolt drivers) and Dell’s 
> Microsoft Windows update utility, the firmware parts below were updated, 
> everything seems to work now.
> 
> MST1                 3.10.002    3.12.002
> MST2                 3.10.002    3.12.002
> ASM USB 3.0 Cntlr    10.11.23    10.11.A9
> Dock NVM             00.00.16    00.00.27
> 
> Mathias, can you please confirm, and maybe also approach ASMedia from 
> Intel to ask them to improve the situation?
> 
> Can the Linux kernel (or some user space) carry a list of non-working 
> firmware versions, and output a warning, that a firmware update is needed?

After testing this some more, the user reports, that the situation 
actually got worse.

No the docking station additionally disconnects randomly when working 
with the system. This did not happen before. Only the Ethernet port of 
the docking station works more reliably now.

Mathias, can you confirm this behavior? Is it the same problem as before?


Kind regards,

Paul


>> [1]: https://github.com/fwupd/fwupd/issues/1351

      reply	other threads:[~2020-02-05 13:10 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04 13:13 USB devices on Dell TB16 dock stop working after resuming Paul Menzel
2019-11-04 14:24 ` Mika Westerberg
2019-11-04 14:44   ` Mika Westerberg
2019-11-04 15:44     ` Mika Westerberg
2019-11-04 15:49       ` Mario.Limonciello
2019-11-04 16:11         ` Paul Menzel
2019-11-04 16:17           ` Mario.Limonciello
2019-11-04 16:22             ` Paul Menzel
2019-11-04 16:21           ` Mika Westerberg
2019-11-19 16:55             ` Paul Menzel
2019-11-19 17:20               ` Paul Menzel
2019-11-20 10:50               ` Mika Westerberg
2019-11-20 14:15                 ` Mario.Limonciello
2019-11-20 15:23                   ` Mika Westerberg
2019-11-20 17:06                     ` Mario.Limonciello
2019-11-20 17:16                       ` Yehezkel Bernat
2019-11-20 17:41                         ` Mario.Limonciello
2019-11-20 17:43                         ` Mika Westerberg
2019-11-20 17:39                       ` Mika Westerberg
2019-11-22 10:50                 ` Mika Westerberg
2019-11-22 11:05                   ` Paul Menzel
2019-11-22 11:29                     ` Mika Westerberg
2019-11-22 11:33                       ` Paul Menzel
2019-11-22 11:41                         ` Mika Westerberg
2019-11-25  9:20                           ` Mathias Nyman
2019-11-26 11:33                             ` Paul Menzel
2019-11-26 12:44                               ` Mathias Nyman
2019-12-20 14:25                                 ` Paul Menzel
2019-12-23  9:39                                   ` Mathias Nyman
2020-01-17  9:56                                     ` Paul Menzel
2020-01-17 18:33                                       ` Mario.Limonciello
2020-01-18  9:15                                         ` Paul Menzel
2020-01-27 22:16                                           ` Paul Menzel
2020-02-05 13:10                                             ` Paul Menzel [this message]

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=e9205ed2-68d2-e08d-2a50-00fe17a08a29@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=anthony.wong@canonical.com \
    --cc=ck@xatom.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@dell.com \
    --cc=mathias.nyman@intel.com \
    --cc=michael.jamet@intel.com \
    --cc=mika.westerberg@linux.intel.com \
    /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).