[GTALUG] USB power reporting Type-c super speed skirmish and libpartd error

Wed Sep 23 11:36:39 EDT 2020

On Wed, Sep 23, 2020 at 9:40 AM D. Hugh Redelmeier via talk <talk at gtalug.org>
wrote:

> [top posting because the information in the original message is somewhat
> holographic.]
>
> Thanks for your detailed report.  It's hard to help when not enough detail
> is included.
>

I've made some progress and then lost it again. I had to take a high def
photo of the writing on the cable to read that the cable is rated 3.0 and
my mb is only rated 3.0 but the peripheral card is usb 3.1. I think this is
why the mb connection hangs the system on usb 3.0, but the peripheral 3.1
card does not. I'm not sure which iteration of usb provides "alternative"
bus capabilities, ie. video and up to 100w power.

> Unfortunately, you seem to have perhaps five problems and it is hard to
> disentangle them.
>
> - one power failure.  Probably nothing you can do anything about.
>
> - "USB over current condition"
>   How do you know this happened?  Is there some indicator?
>   Is this connected somehow with the NVMe drive?
>   You seem to have several USB C ports: are all behaving this way?
>

The mb type-c 3.0 port reports overcurrent when the device is attached and
won't boot. On the adapter card the type is usb 3.1. and the device doesn't
hang the system when booting, but it also won't enumerate the drive

>
> - reliably powering an NVMe drive, connected via USB C.
>   What are its specified power requirements?
>   What can the ports provide?
>   USB C is a mess: one connector, several standards and options
>   within those standards, especially with respect to power.
>

I may have to get a type-c 3.1 rated cable to go much further. It was all
working fine at one point before the power outage. I am updating the kernel
regularly on Fedora 31 before reinstalling on a larger nvme PCI-e x4 m.2 on
the internal slots at some point in the future.

>
> - NVMe disk "lost its type label".
>   I can guess what you mean, but that would be surprising:
>   a surgicically precise failure.  So much so that it is
>   unlikely to be the only damage.
>   Are you using GPT or MBR partitioning?
>   Is your system booting with "legacy" or UEFI?
>

I used gdisk to reset my GPT hybrid setup to go back to mbr after the lvm
volume label disappeared. Maybe not my best choice at the time.

>
> - NVMe drive partitions mounting in /var/run
>   If this isn't where you've told them to mount (via /etc/fstab?)
>   then perhaps the partions' UUIDs have been damaged.
>
>
I just did a fresh reboot with the drive connected to Type-c on the front
breakout panel. This is what a hotplug into the front 3.1 port showsl

udevadm monitor --env
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[1589.645747] unbind
/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.2/3-1.2:1.0 (usb)
ACTION=unbind
DEVPATH=/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.2/3-1.2:1.0
SUBSYSTEM=usb
DEVTYPE=usb_interface
PRODUCT=5e3/610/9223
TYPE=9/0/2
INTERFACE=9/0/2
SEQNUM=4226

KERNEL[1589.645934] remove
/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.2/3-1.2:1.0 (usb)
ACTION=remove
DEVPATH=/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.2/3-1.2:1.0
SUBSYSTEM=usb
DEVTYPE=usb_interface
PRODUCT=5e3/610/9223
TYPE=9/0/2
INTERFACE=9/0/2
MODALIAS=usb:v05E3p0610d9223dc09dsc00dp02ic09isc00ip02in00
SEQNUM=4227

KERNEL[1589.647090] unbind
/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.2 (usb)
ACTION=unbind
DEVPATH=/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.2
SUBSYSTEM=usb
DEVNAME=/dev/bus/usb/003/083
DEVTYPE=usb_device
PRODUCT=5e3/610/9223
TYPE=9/0/2
BUSNUM=003
DEVNUM=083
SEQNUM=4228
MAJOR=189
MINOR=338

KERNEL[1589.647262] remove
/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.2 (usb)
ACTION=remove
DEVPATH=/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.2
SUBSYSTEM=usb
DEVNAME=/dev/bus/usb/003/083
DEVTYPE=usb_device
PRODUCT=5e3/610/9223
TYPE=9/0/2
BUSNUM=003
DEVNUM=083
SEQNUM=4229
MAJOR=189
MINOR=338

UDEV  [1589.652761] unbind
/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.2/3-1.2:1.0 (usb)
ACTION=unbind
DEVPATH=/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.2/3-1.2:1.0
SUBSYSTEM=usb
DEVTYPE=usb_interface
PRODUCT=5e3/610/9223
TYPE=9/0/2
INTERFACE=9/0/2
SEQNUM=4226
USEC_INITIALIZED=1566463583
ID_PATH=pci-0000:72:00.0-usb-0:1.2:1.0
ID_PATH_TAG=pci-0000_72_00_0-usb-0_1_2_1_0

UDEV  [1589.653736] remove
/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.2/3-1.2:1.0 (usb)
ACTION=remove
DEVPATH=/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.2/3-1.2:1.0
SUBSYSTEM=usb
DEVTYPE=usb_interface
PRODUCT=5e3/610/9223
TYPE=9/0/2
INTERFACE=9/0/2
MODALIAS=usb:v05E3p0610d9223dc09dsc00dp02ic09isc00ip02in00
SEQNUM=4227
USEC_INITIALIZED=1566463583
ID_PATH=pci-0000:72:00.0-usb-0:1.2:1.0
ID_PATH_TAG=pci-0000_72_00_0-usb-0_1_2_1_0

UDEV  [1589.655002] unbind
/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.2 (usb)
ACTION=unbind
DEVPATH=/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.2
SUBSYSTEM=usb
DEVNAME=/dev/bus/usb/003/083
DEVTYPE=usb_device
PRODUCT=5e3/610/9223
TYPE=9/0/2
BUSNUM=003
DEVNUM=083
SEQNUM=4228
USEC_INITIALIZED=1566457398
ID_PATH=pci-0000:72:00.0-usb-0:1.2
ID_PATH_TAG=pci-0000_72_00_0-usb-0_1_2
MAJOR=189
MINOR=338

UDEV  [1589.655791] remove
/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.2 (usb)
ACTION=remove
DEVPATH=/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.2
SUBSYSTEM=usb
DEVNAME=/dev/bus/usb/003/083
DEVTYPE=usb_device
PRODUCT=5e3/610/9223
TYPE=9/0/2
BUSNUM=003
DEVNUM=083
SEQNUM=4229
USEC_INITIALIZED=1566457398
ID_PATH=pci-0000:72:00.0-usb-0:1.2
ID_PATH_TAG=pci-0000_72_00_0-usb-0_1_2
MAJOR=189
MINOR=338

KERNEL[1589.693214] unbind
/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.2/4-1.2:1.0 (usb)
ACTION=unbind
DEVPATH=/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.2/4-1.2:1.0
SUBSYSTEM=usb
DEVTYPE=usb_interface
PRODUCT=5e3/612/9223
TYPE=9/0/3
INTERFACE=9/0/0
SEQNUM=4230

KERNEL[1589.693407] remove
/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.2/4-1.2:1.0 (usb)
ACTION=remove
DEVPATH=/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.2/4-1.2:1.0
SUBSYSTEM=usb
DEVTYPE=usb_interface
PRODUCT=5e3/612/9223
TYPE=9/0/3
INTERFACE=9/0/0
MODALIAS=usb:v05E3p0612d9223dc09dsc00dp03ic09isc00ip00in00
SEQNUM=4231

KERNEL[1589.694714] unbind
/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.2 (usb)
ACTION=unbind
DEVPATH=/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.2
SUBSYSTEM=usb
DEVNAME=/dev/bus/usb/004/007
DEVTYPE=usb_device
PRODUCT=5e3/612/9223
TYPE=9/0/3
BUSNUM=004
DEVNUM=007
SEQNUM=4232
MAJOR=189
MINOR=390

KERNEL[1589.694895] remove
/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.2 (usb)
ACTION=remove
DEVPATH=/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.2
SUBSYSTEM=usb
DEVNAME=/dev/bus/usb/004/007
DEVTYPE=usb_device
PRODUCT=5e3/612/9223
TYPE=9/0/3
BUSNUM=004
DEVNUM=007
SEQNUM=4233
MAJOR=189
MINOR=390

UDEV  [1589.698505] unbind
/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.2/4-1.2:1.0 (usb)
ACTION=unbind
DEVPATH=/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.2/4-1.2:1.0
SUBSYSTEM=usb
DEVTYPE=usb_interface
PRODUCT=5e3/612/9223
TYPE=9/0/3
INTERFACE=9/0/0
SEQNUM=4230
USEC_INITIALIZED=1566312548
ID_PATH=pci-0000:72:00.0-usb-0:1.2:1.0
ID_PATH_TAG=pci-0000_72_00_0-usb-0_1_2_1_0

UDEV  [1589.702282] remove
/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.2/4-1.2:1.0 (usb)
ACTION=remove
DEVPATH=/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.2/4-1.2:1.0
SUBSYSTEM=usb
DEVTYPE=usb_interface
PRODUCT=5e3/612/9223
TYPE=9/0/3
INTERFACE=9/0/0
MODALIAS=usb:v05E3p0612d9223dc09dsc00dp03ic09isc00ip00in00
SEQNUM=4231
USEC_INITIALIZED=1566312548
ID_PATH=pci-0000:72:00.0-usb-0:1.2:1.0
ID_PATH_TAG=pci-0000_72_00_0-usb-0_1_2_1_0

UDEV  [1589.707568] unbind
/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.2 (usb)
ACTION=unbind
DEVPATH=/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.2
SUBSYSTEM=usb
DEVNAME=/dev/bus/usb/004/007
DEVTYPE=usb_device
PRODUCT=5e3/612/9223
TYPE=9/0/3
BUSNUM=004
DEVNUM=007
SEQNUM=4232
USEC_INITIALIZED=1566307617
ID_PATH=pci-0000:72:00.0-usb-0:1.2
ID_PATH_TAG=pci-0000_72_00_0-usb-0_1_2
MAJOR=189
MINOR=390

UDEV  [1589.711676] remove
/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.2 (usb)
ACTION=remove
DEVPATH=/devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.2
SUBSYSTEM=usb
DEVNAME=/dev/bus/usb/004/007
DEVTYPE=usb_device
PRODUCT=5e3/612/9223
TYPE=9/0/3
BUSNUM=004
DEVNUM=007
SEQNUM=4233
USEC_INITIALIZED=1566307617
ID_PATH=pci-0000:72:00.0-usb-0:1.2
ID_PATH_TAG=pci-0000_72_00_0-usb-0_1_2
MAJOR=189
MINOR=390

Here is what lspci shows.

lspci
00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host
Bridge/DRAM Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation 6th-9th Gen Core Processor PCIe
Controller (x16) (rev 07)
00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family
USB 3.0 xHCI Controller
00:16.0 Communication controller: Intel Corporation 200 Series PCH CSME
HECI #1
00:17.0 SATA controller: Intel Corporation 200 Series PCH SATA controller
[AHCI mode]
00:1b.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port
#17 (rev f0)
00:1b.4 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port
#21 (rev f0)
00:1c.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port
#1 (rev f0)
00:1c.1 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port
#2 (rev f0)
00:1c.4 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port
#5 (rev f0)
00:1c.7 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port
#8 (rev f0)
00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port
#9 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Z370 Chipset LPC/eSPI Controller
00:1f.2 Memory controller: Intel Corporation 200 Series/Z370 Chipset Family
Power Management Controller
00:1f.3 Audio device: Intel Corporation 200 Series PCH HD Audio
00:1f.4 SMBus: Intel Corporation 200 Series/Z370 Chipset Family SMBus
Controller
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2)
I219-V
01:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX
1050 Ti] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio
Controller (rev a1)
02:00.0 Non-Volatile memory controller: Sandisk Corp WD Black 2018/PC SN720
NVMe SSD
6e:00.0 PCI bridge: Pericom Semiconductor PI7C9X2G304 EL/SL PCIe2
3-Port/4-Lane Packet Switch (rev 05)
6f:01.0 PCI bridge: Pericom Semiconductor PI7C9X2G304 EL/SL PCIe2
3-Port/4-Lane Packet Switch (rev 05)
6f:02.0 PCI bridge: Pericom Semiconductor PI7C9X2G304 EL/SL PCIe2
3-Port/4-Lane Packet Switch (rev 05)
70:00.0 Multimedia video controller: Conexant Systems, Inc. CX23887/8 PCIe
Broadcast Audio and Video Decoder with 3D Comb (rev 04)
71:00.0 Multimedia video controller: Conexant Systems, Inc. CX23887/8 PCIe
Broadcast Audio and Video Decoder with 3D Comb (rev 04)
72:00.0 USB controller: Renesas Technology Corp. uPD720201 USB 3.0 Host
Controller (rev 03)
73:00.0 USB controller: ASMedia Technology Inc. ASM2142 USB 3.1 Host
Controller
74:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
75:00.0 Non-Volatile memory controller: Micron/Crucial Technology P1 NVMe
PCIe SSD (rev 03)

> I would think that the key to getting anywhere is to separately address
> each problem.  Of course you cannot do that in just any order.  I suggest
> the order in which I've listed them: each problem should only depend on
> the ones above.
>

Thanks for looking at this. I'm hoping that a 3.1 rated cable may help to
solve this.

What I find most puzzling is that it was all working well before the power
outage. When I was first using the drive for data, I could plug it into the
type-c port and it would automount the drive. I then made it a boot drive
and it all worked and showed up in bios as a boot selection and booted,
then the power issue and now all this.

One caveat, I am doing all the kernel updates coming in. This is something
I never usually do, but with all the mitigations going on, I thought it
might be best to do this before doing a release upgrade. I have yet to use
dnf upgrade release, in place, so to speak.

>
> Good luck!
>

Thanks I'm hoping a proper alignment of 3.1 cable and 3.1 port will make it
easier, if not actually solve the problem

One of the first mantras I learned first coming to TLUG meetings was that
it's almost never hardware.  That may have changed somewhat.

To paraphrase Bob Dylan, linux is now a jet plane, it flies too fast. ;-)

>
>
> | From: Russell Reiter via talk <talk at gtalug.org>
> | To: GTALUG Talk <talk at gtalug.org>
> | Cc: Russell Reiter <rreiter91 at gmail.com>
> | Date: Thu, 17 Sep 2020 12:26:02 -0400
> | Subject: [GTALUG] USB power reporting Type-c super speed skirmish and
> libpartd
> |      error
> |
> | I had a power outage a couple of weeks ago which lasted longer than my
> UPS
> | battery life and have had a number of USB issues since then.
> |
> | While I was separately recharging the UPS, which took about 5 hours, I
> | rebooted the system which then immediately froze on boot with an USB over
> | current condition. This appeared to be related to the MB front panel
> | connection and at first I thought that somehow a surge made it through
> the
> | UPS and had toasted the motherboards own front port connection. This
> turns
> | out not to have been the case. It’s what happened next that puzzles me
> tho.
> |
> | I have an external NVME enclosure with a PCI-e X4 512 G M.2 storage
> which I
> | have been tinkering with. After disconnecting the front ports on the MB
> | and, I do have a PCI-e 5 port card with 4 x A + 1 Type-C connectors,
> which
> | I had configured to provide four more front ports, with two of them
> Type-C.
> | NB I don’t have the supplemental power connected as I was anticipating
> only
> | to use these ports to use data, for the time being. (This is part of what
> | makes me think the voltage demand reporting might be the culprit)
> |
> | When the front adapter is plugged in this also isolates the Type-C port
> on
> | the actual PCI-e card from being used. After I removed all connections
> from
> | that card and I plugged my M.2 device into the motherboard’s one Type-C
> | port the system turned off like a light switch, no hang, just off.
> |
> | After much fooling around, starting with connecting the keyboard and
> mouse
> | to the onboard legacy USB 2.0 slots, I’m sort of back where I started.
> The
> | two stock USB 3 front ports are connected and working. The supplemental
> | front ports are connected to the expansion card and working, sort of,
> | Type-A works, Type-C does not.
> |
> | Connecting the device, if I connect using a cord adapter to Type-A, the
> | mounts show up in /run/media. It is configured as a boot device. At
> first I
> | thought the over current was related to the fact that that particular
> cord
> | adapter is 3 ft long, but I’m rethinking that although consistent power
> | negotiating and impedance seem to be part of the problem.
> |
> | What did happen was that the M.2 drive had lost it’s type label and I
> | thought I did the right thing by using gdisk to relabel the volume, but
> now
> | it shows up as W95 Ext d (LBA). Also, gparted now shows a libparted error
> | for the actual volume I am currently booting from, although gnome-disks
> is
> | fine with it.
> |
> | Perhaps the libparted error is related to my kernel version and non
> | complementary libparted updates. I have seen this as an old issue of out
> of
> | but I cannot so far consistently switch from connecting the device via
> Type
> | A and Type C connections. Maybe this is a memory hangover concerning the
> | voltage requested by Type-A vs Type-C
> |
> |
> | My current kernel.
> |
> | Linux archon 5.8.8-100.fc31.x86_64 #1 SMP Wed Sep 9 20:29:23 UTC 2020
> | x86_64 x86_64 x86_64 GNU/Linux
> |
> |
> | Here is what happens when I’m using the Type-A to C adapter cable.
> | Everything is detected and mounted in /run/media
> |
> |
> | udevadm monitor
> |
> | monitor will print the received events for:
> |
> | UDEV - the event which udev sends out after rule processing
> |
> | KERNEL - the kernel uevent
> |
> |
> | KERNEL[1144.231633] add
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4 (usb)
> |
> | KERNEL[1144.236767] add
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0
> (usb)
> |
> | KERNEL[1144.250366] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4
> | (scsi)
> |
> | KERNEL[1144.250424] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/scsi_host/host4
> | (scsi_host)
> |
> | KERNEL[1144.250509] bind
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0
> (usb)
> |
> | KERNEL[1144.250602] bind
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4 (usb)
> |
> | KERNEL[1144.251689] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/target4:0:0
> | (scsi)
> |
> | KERNEL[1144.251774] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/target4:0:0/4:0:0:0
> | (scsi)
> |
> | KERNEL[1144.251822] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/target4:0:0/4:0:0:0/scsi_device/4:0:0:0
> | (scsi_device)
> |
> | KERNEL[1144.251933] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/target4:0:0/4:0:0:0/scsi_disk/4:0:0:0
> | (scsi_disk)
> |
> | KERNEL[1144.252009] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/target4:0:0/4:0:0:0/scsi_generic/sg2
> | (scsi_generic)
> |
> | KERNEL[1144.252393] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/target4:0:0/4:0:0:0/bsg/4:0:0:0
> | (bsg)
> |
> | UDEV [1144.259793] add
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4 (usb)
> |
> | UDEV [1144.261835] add
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0
> (usb)
> |
> | UDEV [1144.262732] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4
> | (scsi)
> |
> | UDEV [1144.263715] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/scsi_host/host4
> | (scsi_host)
> |
> | UDEV [1144.264976] bind
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0
> (usb)
> |
> | UDEV [1144.268728] bind
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4 (usb)
> |
> | UDEV [1144.269850] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/target4:0:0
> | (scsi)
> |
> | UDEV [1144.270851] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/target4:0:0/4:0:0:0
> | (scsi)
> |
> | UDEV [1144.271941] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/target4:0:0/4:0:0:0/scsi_device/4:0:0:0
> | (scsi_device)
> |
> | UDEV [1144.272716] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/target4:0:0/4:0:0:0/scsi_disk/4:0:0:0
> | (scsi_disk)
> |
> | UDEV [1144.273540] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/target4:0:0/4:0:0:0/bsg/4:0:0:0
> | (bsg)
> |
> | UDEV [1144.273563] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/target4:0:0/4:0:0:0/scsi_generic/sg2
> | (scsi_generic)
> |
> | KERNEL[1145.985198] add /devices/virtual/bdi/8:16 (bdi)
> |
> | UDEV [1145.987911] add /devices/virtual/bdi/8:16 (bdi)
> |
> | KERNEL[1145.988867] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/target4:0:0/4:0:0:0/block/sdb
> | (block)
> |
> | KERNEL[1145.989065] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb1
> | (block)
> |
> | KERNEL[1145.989186] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb2
> | (block)
> |
> | KERNEL[1145.989308] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb3
> | (block)
> |
> | KERNEL[1145.989450] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb4
> | (block)
> |
> | KERNEL[1145.989584] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb5
> | (block)
> |
> | KERNEL[1145.990843] bind
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/target4:0:0/4:0:0:0
> | (scsi)
> |
> | UDEV [1146.031257] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/target4:0:0/4:0:0:0/block/sdb
> | (block)
> |
> | UDEV [1146.035268] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb4
> | (block)
> |
> | UDEV [1146.045437] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb1
> | (block)
> |
> | UDEV [1146.046036] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb3
> | (block)
> |
> | UDEV [1146.046869] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb2
> | (block)
> |
> | UDEV [1146.051277] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb5
> | (block)
> |
> | UDEV [1146.052469] bind
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.4/4-1.4:1.0/host4/target4:0:0/4:0:0:0
> | (scsi)
> |
> |
> |
> | This is what the Type-C connection reports on the front panel (w/o the
> | supplemental power connection from the card to the expansion panel) when
> I
> | attempt to hot switch from Type-A to C, even if I had un-mounted the
> | partitions from the disks app GUI, The first event is unbind.
> |
> |
> | udevadm monitor
> |
> | monitor will print the received events for:
> |
> | UDEV - the event which udev sends out after rule processing
> |
> | KERNEL - the kernel uevent
> |
> |
> | KERNEL[1460.229192] unbind
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.2/4-1.2:1.0
> (usb)
> |
> | KERNEL[1460.229310] remove
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.2/4-1.2:1.0
> (usb)
> |
> | KERNEL[1460.230680] unbind
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.2 (usb)
> |
> | KERNEL[1460.230806] remove
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.2 (usb)
> |
> | UDEV [1460.235695] unbind
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.2/4-1.2:1.0
> (usb)
> |
> | UDEV [1460.236812] remove
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.2/4-1.2:1.0
> (usb)
> |
> | UDEV [1460.237925] unbind
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.2 (usb)
> |
> | UDEV [1460.238627] remove
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb4/4-1/4-1.2 (usb)
> |
> | KERNEL[1460.434274] unbind
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.2/3-1.2:1.0
> (usb)
> |
> | KERNEL[1460.434407] remove
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.2/3-1.2:1.0
> (usb)
> |
> | KERNEL[1460.436020] unbind
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.2 (usb)
> |
> | KERNEL[1460.436183] remove
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.2 (usb)
> |
> | UDEV [1460.439331] unbind
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.2/3-1.2:1.0
> (usb)
> |
> | UDEV [1460.443163] remove
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.2/3-1.2:1.0
> (usb)
> |
> | UDEV [1460.445660] unbind
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.2 (usb)
> |
> | UDEV [1460.446564] remove
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.2 (usb)
> |
> |
> | Here is what udev reports with the front extension panel disconnected
> from
> | the PCI-e card and the drive is plugged into the expansion card's single
> | Type-C connection.
> |
> |
> | udevadm monitor
> |
> | monitor will print the received events for:
> |
> | UDEV - the event which udev sends out after rule processing
> |
> | KERNEL - the kernel uevent
> |
> |
> | KERNEL[93.288656] add
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3 (usb)
> |
> | KERNEL[93.297154] add
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0
> (usb)
> |
> | KERNEL[93.297182] bind
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3 (usb)
> |
> | UDEV [93.303112] add
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3 (usb)
> |
> | KERNEL[93.310552] add /module/usb_storage (module)
> |
> | KERNEL[93.310602] add /bus/usb/drivers/usb-storage (drivers)
> |
> | UDEV [93.311904] add /module/usb_storage (module)
> |
> | UDEV [93.312259] add /bus/usb/drivers/usb-storage (drivers)
> |
> | KERNEL[93.312655] add /module/uas (module)
> |
> | UDEV [93.313198] add /module/uas (module)
> |
> | KERNEL[93.324476] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4
> | (scsi)
> |
> | KERNEL[93.324491] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/scsi_host/host4
> | (scsi_host)
> |
> | KERNEL[93.324517] bind
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0
> (usb)
> |
> | KERNEL[93.324525] add /bus/usb/drivers/uas (drivers)
> |
> | UDEV [93.324646] add
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0
> (usb)
> |
> | UDEV [93.325326] add /bus/usb/drivers/uas (drivers)
> |
> | KERNEL[93.325718] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/target4:0:0
> | (scsi)
> |
> | KERNEL[93.325745] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/target4:0:0/4:0:0:0
> | (scsi)
> |
> | KERNEL[93.325760] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/target4:0:0/4:0:0:0/scsi_device/4:0:0:0
> | (scsi_device)
> |
> | KERNEL[93.325772] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/target4:0:0/4:0:0:0/scsi_disk/4:0:0:0
> | (scsi_disk)
> |
> | KERNEL[93.325837] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/target4:0:0/4:0:0:0/scsi_generic/sg2
> | (scsi_generic)
> |
> | KERNEL[93.325898] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/target4:0:0/4:0:0:0/bsg/4:0:0:0
> | (bsg)
> |
> | UDEV [93.329778] bind
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3 (usb)
> |
> | UDEV [93.331051] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4
> | (scsi)
> |
> | UDEV [93.332395] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/scsi_host/host4
> | (scsi_host)
> |
> | UDEV [93.334102] bind
> | /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0
> (usb)
> |
> | UDEV [93.335352] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/target4:0:0
> | (scsi)
> |
> | UDEV [93.336749] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/target4:0:0/4:0:0:0
> | (scsi)
> |
> | UDEV [93.338326] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/target4:0:0/4:0:0:0/scsi_device/4:0:0:0
> | (scsi_device)
> |
> | UDEV [93.338504] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/target4:0:0/4:0:0:0/scsi_disk/4:0:0:0
> | (scsi_disk)
> |
> | UDEV [93.339426] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/target4:0:0/4:0:0:0/scsi_generic/sg2
> | (scsi_generic)
> |
> | UDEV [93.340162] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/target4:0:0/4:0:0:0/bsg/4:0:0:0
> | (bsg)
> |
> | KERNEL[94.516320] add /devices/virtual/bdi/8:16 (bdi)
> |
> | UDEV [94.519016] add /devices/virtual/bdi/8:16 (bdi)
> |
> | KERNEL[94.520794] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/target4:0:0/4:0:0:0/block/sdb
> | (block)
> |
> | KERNEL[94.520944] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb1
> | (block)
> |
> | KERNEL[94.521091] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb2
> | (block)
> |
> | KERNEL[94.521209] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb3
> | (block)
> |
> | KERNEL[94.521326] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb4
> | (block)
> |
> | KERNEL[94.521431] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb5
> | (block)
> |
> | KERNEL[94.523245] bind
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/target4:0:0/4:0:0:0
> | (scsi)
> |
> | UDEV [94.603863] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/target4:0:0/4:0:0:0/block/sdb
> | (block)
> |
> | UDEV [94.611530] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb4
> | (block)
> |
> | UDEV [94.700559] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb1
> | (block)
> |
> | UDEV [94.716164] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb2
> | (block)
> |
> | UDEV [94.731543] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb5
> | (block)
> |
> | UDEV [94.737275] add
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb3
> | (block)
> |
> | UDEV [94.738283] bind
> |
> /devices/pci0000:00/0000:00:1c.1/0000:72:00.0/usb3/3-1/3-1.3/3-1.3:1.0/host4/target4:0:0/4:0:0:0
> | (scsi)
> |
> | KERNEL[113.079306] add /devices/virtual/bdi/0:39 (bdi)
> |
> | UDEV [113.083466] add /devices/virtual/bdi/0:39 (bdi)
> |
> | Unfortunately the cable for connecting the supplementary power to the
> front
> | expansion port was too short so I’m wondering if this is at all related
> to
> | the system registering one voltage demand for the Type-C connection and
> not
> | releasing that info and then re-probing for the increased voltage the SS
> | port connection allows for.
> |
> | Does anyone have any suggestions on how I can unwind some of this?
> |
> | Perhaps sourcing a longer cable for connecting the expansion cards power
> to
> | the slot might do the trick. I can't say for sure, but I don't recall
> this
> | being an issue before the power issue.
> | --
> | Russell
> | ---
> Post to this mailing list talk at gtalug.org
> Unsubscribe from this mailing list
> https://gtalug.org/mailman/listinfo/talk
>

-- 
Russell
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gtalug.org/pipermail/talk/attachments/20200923/bd2bb956/attachment.html>