linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhangzhansheng <zhang.zhansheng@h3c.com>
To: Mathias Nyman <mathias.nyman@linux.intel.com>,
	Ladislav Michl <oss-lists@triops.cz>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	Sneeker Yeh <sneeker.yeh@gmail.com>,
	Wangxiaoqing <wangxiaoqing@h3c.com>,
	Xinhaining <xinhaining@h3c.com>
Subject: 答复: 答复: 答复: [Consulting about: xHCI host dies on device unplug]
Date: Wed, 24 Jan 2024 14:09:43 +0000	[thread overview]
Message-ID: <7e00c498947c4efdb8a96f970656ee03@h3c.com> (raw)
In-Reply-To: <c756521f-ea5b-7816-5d60-0c61f3275305@linux.intel.com>

Mathias:

Thank you very much!

> This issue was resolved in 5.19 kernel with patch:
> 25355e046d29 xhci: use generic command timer for stop endpoint commands.

> After this patch the timer is started when xHC start processing the command, not when driver queues it.
> I strongly recommend trying a more recent kernel where all these issues are fixed already.
 
I see 5.19 kernel has done what you say.

Because the kernel version of our company is 4.65 , I need to put the patch to our 4.65 kernel we used.
 
Today compared to the latest kernel is 6.7, I found there are a lot of changes for usb module between kernel 4.65 and 6.7.

Could you provide me for the issues patch.




-----邮件原件-----
发件人: Mathias Nyman [mailto:mathias.nyman@linux.intel.com] 
发送时间: 2024年1月24日 21:49
收件人: zhangzhansheng (操作系统开发部部门, RD) <zhang.zhansheng@h3c.com>; Ladislav Michl <oss-lists@triops.cz>
抄送: linux-usb@vger.kernel.org; Sneeker Yeh <sneeker.yeh@gmail.com>; wangxiaoqing (操作系统开发部/OM, RD) <wangxiaoqing@h3c.com>; xinhaining (操作系统开发部/OM, RD) <xinhaining@h3c.com>
主题: Re: 答复: 答复: [Consulting about: xHCI host dies on device unplug]

On 24.1.2024 13.42, Zhangzhansheng wrote:
> Mathias:
> 
> 
> In regard to the question “What the reason of the usb host controller handing the stop endpoint command timeout maybe two a) and b).”Just to add the follow  one :
> When the problem arising, the function of “xhci_halt “ operated the host controller successfully. So I think the usb host controller should be ok.
> 
> So, I gussess that the usb host controller has no enough time to handle with a large number of xhci command.
> 

This issue was resolved in 5.19 kernel with patch:
25355e046d29 xhci: use generic command timer for stop endpoint commands.

After this patch the timer is started when xHC start processing the command, not when driver queues it.

I strongly recommend trying a more recent kernel where all these issues are fixed already.

Thanks
Mathias

  reply	other threads:[~2024-01-24 14:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7b049561ce33406ab9b5d0cee7fbd497@h3c.com>
2024-01-05 11:07 ` [Consulting about: xHCI host dies on device unplug] Mathias Nyman
2024-01-22  4:03   ` 答复: " Zhangzhansheng
2024-01-23 14:49     ` Mathias Nyman
     [not found]       ` <64e4153a5cd54cf9bc3eaaf823ba0a31@h3c.com>
2024-01-24 13:49         ` 答复: " Mathias Nyman
2024-01-24 14:09           ` Zhangzhansheng [this message]
2024-01-24 14:19             ` 答复: " Greg KH
2024-01-25  1:02               ` 答复: " Zhangzhansheng
2024-01-25 23:01                 ` Greg KH

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=7e00c498947c4efdb8a96f970656ee03@h3c.com \
    --to=zhang.zhansheng@h3c.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.com \
    --cc=oss-lists@triops.cz \
    --cc=sneeker.yeh@gmail.com \
    --cc=wangxiaoqing@h3c.com \
    --cc=xinhaining@h3c.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).