2017-11-08 02:33:18 |
Alice Liu |
bug |
|
|
added bug |
2017-11-08 02:33:28 |
Alice Liu |
information type |
Proprietary |
Private |
|
2017-12-13 06:21:05 |
Alice Liu |
description |
Description
xHCI compatible USB host controllers(i.e. super-speed USB3 controllers)
can be implemented with the Debug Capability(DbC). It presents a debug
device which is fully compliant with the USB framework and provides the
equivalent of a very high performance full-duplex serial link. The debug
capability operation model and registers interface are defined in 7.6.8
of the xHCI specification, revision 1.1.
The DbC debug device shares a root port with the xHCI host. By default,
the debug capability is disabled and the root port is assigned to xHCI.
When the DbC is enabled, the root port will be assigned to the DbC debug
device, and the xHCI sees nothing on this port. This implementation uses
a sysfs node named <dbc> under the xHCI device to manage the enabling
and disabling of the debug capability.
When the debug capability is enabled, it will present a debug device
through the debug port. This debug device is fully compliant with the
USB3 framework, and it can be enumerated by a debug host on the other
end of the USB link. As soon as the debug device is configured, a TTY
serial device named /dev/ttyDBC0 will be created.
One use of this link is running a login service on the debug target.
Hence it can be remote accessed by a debug host. Another use case can
probably be found in servers. It provides a peer-to-peer USB link
between two host-only machines. This provides a reasonable out-of-band
communication method between two servers.
Target Kernel: TBD
Target Release: 18.04 |
Description
xHCI compatible USB host controllers(i.e. super-speed USB3 controllers)
can be implemented with the Debug Capability(DbC). It presents a debug
device which is fully compliant with the USB framework and provides the
equivalent of a very high performance full-duplex serial link. The debug
capability operation model and registers interface are defined in 7.6.8
of the xHCI specification, revision 1.1.
The DbC debug device shares a root port with the xHCI host. By default,
the debug capability is disabled and the root port is assigned to xHCI.
When the DbC is enabled, the root port will be assigned to the DbC debug
device, and the xHCI sees nothing on this port. This implementation uses
a sysfs node named <dbc> under the xHCI device to manage the enabling
and disabling of the debug capability.
When the debug capability is enabled, it will present a debug device
through the debug port. This debug device is fully compliant with the
USB3 framework, and it can be enumerated by a debug host on the other
end of the USB link. As soon as the debug device is configured, a TTY
serial device named /dev/ttyDBC0 will be created.
One use of this link is running a login service on the debug target.
Hence it can be remote accessed by a debug host. Another use case can
probably be found in servers. It provides a peer-to-peer USB link
between two host-only machines. This provides a reasonable out-of-band
communication method between two servers.
Target Kernel: 4.16
Target Release: 18.04 |
|
2018-02-24 00:25:42 |
Leann Ogasawara |
tags |
|
kernel |
|
2018-02-24 00:25:45 |
Leann Ogasawara |
intel: status |
New |
Incomplete |
|
2018-03-02 13:37:04 |
Leann Ogasawara |
information type |
Private |
Public |
|
2018-03-02 13:37:14 |
Leann Ogasawara |
bug task added |
|
linux (Ubuntu) |
|
2018-03-02 13:37:22 |
Leann Ogasawara |
nominated for series |
|
Ubuntu Bionic |
|
2018-03-02 13:37:22 |
Leann Ogasawara |
bug task added |
|
linux (Ubuntu Bionic) |
|
2018-03-02 13:37:29 |
Leann Ogasawara |
linux (Ubuntu Bionic): status |
New |
Triaged |
|
2018-03-02 13:37:32 |
Leann Ogasawara |
intel: status |
Incomplete |
Triaged |
|
2018-03-02 13:37:36 |
Leann Ogasawara |
linux (Ubuntu Bionic): importance |
Undecided |
Medium |
|
2018-03-02 13:37:39 |
Leann Ogasawara |
intel: importance |
Undecided |
Medium |
|
2018-03-02 13:37:49 |
Leann Ogasawara |
linux (Ubuntu Bionic): assignee |
|
Canonical Kernel Team (canonical-kernel-team) |
|
2018-03-02 14:20:06 |
Joseph Salisbury |
linux (Ubuntu Bionic): status |
Triaged |
In Progress |
|
2018-03-02 14:20:09 |
Joseph Salisbury |
linux (Ubuntu Bionic): assignee |
Canonical Kernel Team (canonical-kernel-team) |
Joseph Salisbury (jsalisbury) |
|
2018-03-07 09:27:49 |
Thadeu Lima de Souza Cascardo |
linux (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
2018-03-15 02:26:24 |
Launchpad Janitor |
linux (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
2018-03-15 02:26:24 |
Launchpad Janitor |
cve linked |
|
2017-5754 |
|
2018-04-04 22:17:13 |
Leann Ogasawara |
intel: status |
Triaged |
Fix Released |
|
2019-02-14 12:12:05 |
Brad Figg |
tags |
kernel |
kernel verification-needed-bionic |
|
2019-02-14 15:53:22 |
Andy Whitcroft |
tags |
kernel verification-needed-bionic |
kernel kernel-fixup-verification-needed-bionic |
|
2019-02-14 16:08:57 |
Brad Figg |
tags |
kernel kernel-fixup-verification-needed-bionic |
kernel kernel-fixup-verification-needed-bionic verification-needed-bionic |
|
2019-02-14 16:14:39 |
Andy Whitcroft |
tags |
kernel kernel-fixup-verification-needed-bionic verification-needed-bionic |
kernel kernel-fixup-verification-needed-bionic |
|
2019-02-14 16:18:47 |
Andy Whitcroft |
tags |
kernel kernel-fixup-verification-needed-bionic |
kernel kernel-fixup-verification-needed-bionic verification-done-bionic |
|
2019-07-24 21:07:57 |
Brad Figg |
tags |
kernel kernel-fixup-verification-needed-bionic verification-done-bionic |
cscc kernel kernel-fixup-verification-needed-bionic verification-done-bionic |
|