umass not working and other USB troubles

[Andrea Venturoli]

Hello.

On a new server I've recently installed, I'm unable to use external USB
HDs or keys.
When I connect any, I hear it spin up, but the OS won't show anything in
the logs or in "camcontrol devlist".
Of course I installed the system by booting an USB key, so it works when
booting from there.

Bonus: if I try hard, [un]plugging it several times, I may lose the
(physical) keyboard or the connection to the UPS!



> # freebsd-version -ku
> 14.3-RELEASE-p5
> 14.3-RELEASE-p5

> # pciconf -lv
> hostb0@pci0:0:0:0: class=0x060000 rev=0x01 hdr=0x00 vendor=0x8086 device=0xa711 subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'
> class = bridge
> subclass = HOST-PCI
> xhci0@pci0:0:20:0: class=0x0c0330 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a60 subvendor=0x1043 subdevice=0x88a1
> vendor = 'Intel Corporation'
> device = 'Raptor Lake USB 3.2 Gen 2x2 (20 Gb/s) XHCI Host Controller'
> class = serial bus
> subclass = USB
> none0@pci0:0:20:2: class=0x050000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a27 subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'
> device = 'Raptor Lake-S PCH Shared SRAM'
> class = memory
> subclass = RAM
> none1@pci0:0:21:0: class=0x0c8000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a4c subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'
> device = 'Raptor Lake Serial IO I2C Host Controller'
> class = serial bus
> none2@pci0:0:21:1: class=0x0c8000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a4d subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'
> device = 'Raptor Lake Serial IO I2C Host Controller'
> class = serial bus
> none3@pci0:0:21:3: class=0x0c8000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a4f subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'
> class = serial bus
> none4@pci0:0:22:0: class=0x078000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a68 subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'
> device = 'Raptor Lake CSME HECI'
> class = simple comms
> none5@pci0:0:22:1: class=0x078000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a69 subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'
> device = 'Raptor Lake CSME HECI'
> class = simple comms
> none6@pci0:0:22:4: class=0x078000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a6c subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'
> class = simple comms
> ahci0@pci0:0:23:0: class=0x010601 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a62 subvendor=0x1043 subdevice=0x889f
> vendor = 'Intel Corporation'
> device = 'Raptor Lake SATA AHCI Controller'
> class = mass storage
> subclass = SATA
> none7@pci0:0:25:0: class=0x0c8000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a7c subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'
> class = serial bus
> none8@pci0:0:25:1: class=0x0c8000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a7d subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'
> class = serial bus
> pcib1@pci0:0:28:0: class=0x060400 rev=0x11 hdr=0x01 vendor=0x8086 device=0x7a38 subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'
> device = 'Raptor Lake PCI Express Root Port'
> class = bridge
> subclass = PCI-PCI
> pcib3@pci0:0:28:2: class=0x060400 rev=0x11 hdr=0x01 vendor=0x8086 device=0x7a3a subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'
> device = 'Raptor Point-S PCH - PCI Express Root Port 3'
> class = bridge
> subclass = PCI-PCI
> pcib4@pci0:0:28:3: class=0x060400 rev=0x11 hdr=0x01 vendor=0x8086 device=0x7a3b subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'
> device = 'Raptor Lake PCI Express Root Port'
> class = bridge
> subclass = PCI-PCI
> pcib5@pci0:0:28:4: class=0x060400 rev=0x11 hdr=0x01 vendor=0x8086 device=0x7a3c subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'
> class = bridge
> subclass = PCI-PCI
> none9@pci0:0:31:0: class=0x060100 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a14 subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'
> class = bridge
> subclass = PCI-ISA
> none10@pci0:0:31:4: class=0x0c0500 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a23 subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'
> device = 'Raptor Lake-S PCH SMBus Controller'
> class = serial bus
> subclass = SMBus
> none11@pci0:0:31:5: class=0x0c8000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a24 subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'
> device = 'Raptor Lake SPI (flash) Controller'
> class = serial bus
> pcib2@pci0:1:0:0: class=0x060400 rev=0x06 hdr=0x01 vendor=0x1a03 device=0x1150 subvendor=0x1043 subdevice=0x87ed
> vendor = 'ASPEED Technology, Inc.'
> device = 'AST1150 PCI-to-PCI Bridge'
> class = bridge
> subclass = PCI-PCI
> vgapci0@pci0:2:0:0: class=0x030000 rev=0x52 hdr=0x00 vendor=0x1a03 device=0x2000 subvendor=0x1043 subdevice=0x87ed
> vendor = 'ASPEED Technology, Inc.'
> device = 'ASPEED Graphics Family'
> class = display
> subclass = VGA
> igb0@pci0:3:0:0: class=0x020000 rev=0x03 hdr=0x00 vendor=0x8086 device=0x1533 subvendor=0x1043 subdevice=0x8557
> vendor = 'Intel Corporation'
> device = 'I210 Gigabit Network Connection'
> class = network
> subclass = ethernet
> igb1@pci0:4:0:0: class=0x020000 rev=0x03 hdr=0x00 vendor=0x8086 device=0x1533 subvendor=0x1043 subdevice=0x8557
> vendor = 'Intel Corporation'
> device = 'I210 Gigabit Network Connection'
> class = network
> subclass = ethernet
> igb2@pci0:5:0:0: class=0x020000 rev=0x03 hdr=0x00 vendor=0x8086 device=0x1533 subvendor=0x8086 subdevice=0x0002
> vendor = 'Intel Corporation'
> device = 'I210 Gigabit Network Connection'
> class = network
> subclass = ethernet

> # usbconfig
> ugen0.1: <XHCI root HUB Intel> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA)
> ugen0.3: <UPS American Power Conversion> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (10mA)
> ugen0.4: <CP2112 HID I2C Bridge Silicon Labs> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA)
> ugen0.5: <Virtual Hub American Megatrends, Inc.> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
> ugen0.6: <Virtual CDROM American Megatrends, Inc.> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA)
> ugen0.7: <Virtual HDisk Device American Megatrends, Inc.> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA)
> ugen0.8: <Virtual Ethernet. American Megatrends, Inc.> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA)
> ugen0.9: <Virtual Keyboard and Mouse American Megatrends, Inc.> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA)

> # camcontrol devlist
> <KINGSTON SEDC600M1920G SCEKH5.3> at scbus0 target 0 lun 0 (pass0,ada0)
> <KINGSTON SEDC600M1920G SCEKH5.3> at scbus1 target 0 lun 0 (pass1,ada1)
> <KINGSTON SEDC600M1920G SCEKH5.3> at scbus2 target 0 lun 0 (pass2,ada2)
> <AHCI SGPIO Enclosure 2.00 0001> at scbus8 target 0 lun 0 (ses0,pass3)
> <AMI Virtual CDROM0 1.00> at scbus9 target 0 lun 0 (cd0,pass4)
> <AMI Virtual HDisk0 1.00> at scbus10 target 0 lun 0 (da0,pass5)



I have scbus, da, xhci (not uhci, ohci or ehci), usb, usbhid, hkbd,
ukbd, umass in the kernel.



Any hint?

I have XHCI handoff disabled in the BIOS (from physical console), but I
see it as enabled if I connect through BMC!!!
Can this matter?

bye & Thanks
av.

[nahn03]

Hello:

One idea that may work is making sure the USB devices are unplugged, then issue the command:

sudo tail -f /var/log/messages

Then plug a single device back into a USB port and please report back what the log says.






Sent with Proton Mail secure email.

[Andrea Venturoli]

On 1/26/26 18:20, nahn03 wrote:
> Hello:
>
> One idea that may work is making sure the USB devices are unplugged, then issue the command:
>
> sudo tail -f /var/log/messages
>
> Then plug a single device back into a USB port and please report back what the log says.

Well.

Plugging an HD or a key when the UPS is connected just logs nothing (as
I said).
Plugging an HD or a key when the UPS and a keyboard are connected shows
nothing.
Plugging a keyboard when the UPS is connected logs nothing (keyboard
only works if connected at boot).
Plugging the UPS when nothing else is connected logs nothing (again, it
only works if connected at boot).

All the above were tried when the UPS (and eventually the keyboard) were
plugged in initially (at boot).
I can try to boot without nothing, if needed, but I won't have the
chance to be physically at this site any time soon.

bye & Thanks
av.

[Andrea Venturoli]

On 1/26/26 18:38, Andrea Venturoli wrote:

> I can try to boot without nothing, if needed, but I won't have the
> chance to be physically at this site any time soon.

Sorry, I meant:
"I can try to boot without *anyhing*.

Really, what I'm trying to get is a bunch of ideas to try when I'll be
onsite again.

bye & Thanks
av.

[Daniel Lysfjord]

Hi,

XHCI handoff is advised to keep on unless there's something not working
with it on.
Since your equipment works when booting with it connected, but is not
detected at all when OS is running, makes me suspect that setting.

[Andrea Venturoli]

On 1/26/26 18:57, Daniel Lysfjord wrote:

> XHCI handoff is advised to keep on unless there's something not working
> with it on.
> Since your equipment works when booting with it connected, but is not
> detected at all when OS is running, makes me suspect that setting.

I've always kept it off on every machine and never experienced such trouble.
In any case, I'll try switching it.

bye & Thanks
av.

[Andrea Venturoli]

On 1/26/26 18:57, Daniel Lysfjord wrote:

> XHCI handoff is advised to keep on unless there's something not working
> with it on.

That was it! Thanks.

(As it's described as "a workaround for OSes that don't support..." I
always thought it should have been off).

bye
av.

[Daniel Lysfjord]

It's the other way around, disabling it is a workaround for OSs that
don't support handling USB3 (like windows 7 without the proper
drivers):)

[Andrea Venturoli]

On 2/25/26 15:10, Andrea Venturoli wrote:
> On 1/26/26 18:57, Daniel Lysfjord wrote:
>
>> XHCI handoff is advised to keep on unless there's something not
>> working with it on.
>
> That was it! Thanks.

Hello.

Sorry if so long a time has passed...
This only half solved.

Now when I plug the hard disk in, it doesn't get detected.
I need to issue "usbconfig reset" and it will come up.


I'll repeat all data:

> # freebsd-version -ku
> 14.4-RELEASE-p7
> 14.4-RELEASE-p7

> # pciconf -lv
> hostb0@pci0:0:0:0: class=0x060000 rev=0x01 hdr=0x00 vendor=0x8086 device=0xa711 subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'
> class = bridge
> subclass = HOST-PCI
> xhci0@pci0:0:20:0: class=0x0c0330 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a60 subvendor=0x1043 subdevice=0x88a1
> vendor = 'Intel Corporation'
> device = 'Raptor Lake USB 3.2 Gen 2x2 (20 Gb/s) XHCI Host Controller'
> class = serial bus
> subclass = USB
> none0@pci0:0:20:2: class=0x050000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a27 subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'

> device = 'Raptor Lake PCH Shared SRAM'

> class = memory
> subclass = RAM
> none1@pci0:0:21:0: class=0x0c8000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a4c subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'
> device = 'Raptor Lake Serial IO I2C Host Controller'
> class = serial bus
> none2@pci0:0:21:1: class=0x0c8000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a4d subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'
> device = 'Raptor Lake Serial IO I2C Host Controller'
> class = serial bus
> none3@pci0:0:21:3: class=0x0c8000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a4f subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'
> device = 'Raptor Lake Serial IO I2C Host Controller'
> class = serial bus

> none4@pci0:0:22:0: class=0x078000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a68 subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'
> device = 'Raptor Lake CSME HECI'
> class = simple comms
> none5@pci0:0:22:1: class=0x078000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a69 subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'
> device = 'Raptor Lake CSME HECI'
> class = simple comms
> none6@pci0:0:22:4: class=0x078000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a6c subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'
> device = 'Raptor Lake CSME HECI'
> class = simple comms

> ahci0@pci0:0:23:0: class=0x010601 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a62 subvendor=0x1043 subdevice=0x889f
> vendor = 'Intel Corporation'
> device = 'Raptor Lake SATA AHCI Controller'
> class = mass storage
> subclass = SATA
> none7@pci0:0:25:0: class=0x0c8000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a7c subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'

> device = 'Raptor Lake Serial IO I2C Host Controller'
> class = serial bus

> none8@pci0:0:25:1: class=0x0c8000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a7d subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'

> device = 'Raptor Lake Serial IO I2C Host Controller'
> class = serial bus

> pcib1@pci0:0:28:0: class=0x060400 rev=0x11 hdr=0x01 vendor=0x8086 device=0x7a38 subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'
> device = 'Raptor Lake PCI Express Root Port'
> class = bridge
> subclass = PCI-PCI
> pcib3@pci0:0:28:2: class=0x060400 rev=0x11 hdr=0x01 vendor=0x8086 device=0x7a3a subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'
> device = 'Raptor Lake PCI Express Root Port'
> class = bridge
> subclass = PCI-PCI

> pcib4@pci0:0:28:3: class=0x060400 rev=0x11 hdr=0x01 vendor=0x8086 device=0x7a3b subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'
> device = 'Raptor Lake PCI Express Root Port'
> class = bridge
> subclass = PCI-PCI
> pcib5@pci0:0:28:4: class=0x060400 rev=0x11 hdr=0x01 vendor=0x8086 device=0x7a3c subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'

> device = 'Raptor Lake PCI Express Root Port'
> class = bridge
> subclass = PCI-PCI

> none9@pci0:0:31:0: class=0x060100 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a14 subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'

> device = 'C262 Chipset LPC/eSPI Controller'

> class = bridge
> subclass = PCI-ISA
> none10@pci0:0:31:4: class=0x0c0500 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a23 subvendor=0x8086 subdevice=0x7270
> vendor = 'Intel Corporation'

> device = '700 Series Chipset SMBus Controller'

> ugen0.2: <UPS American Power Conversion> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (10mA)
> ugen0.3: <CP2112 HID I2C Bridge Silicon Labs> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA)
> ugen0.4: <Virtual Hub American Megatrends, Inc.> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
> ugen0.5: <Virtual CDROM American Megatrends, Inc.> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA)
> ugen0.6: <Virtual HDisk Device American Megatrends, Inc.> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA)
> ugen0.7: <Virtual Ethernet. American Megatrends, Inc.> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA)
> ugen0.8: <Virtual Keyboard and Mouse American Megatrends, Inc.> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA)
> ugen0.9: <EXTERNALUSB Toshiba America Inc> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON (224mA)



If someone has any hint, I'd be happy to let the user manage the disk by
himself by just plugging/unplugging it.


bye & Thanks
av.

[Daniel Lysfjord]

On 2026-08-06 15:19, Andrea Venturoli wrote:
> On 2/25/26 15:10, Andrea Venturoli wrote:
>> On 1/26/26 18:57, Daniel Lysfjord wrote:
>>
>>> XHCI handoff is advised to keep on unless there's something not
>>> working with it on.
>>
>> That was it! Thanks.
>
> Hello.
>
> Sorry if so long a time has passed...
> This only half solved.
>
> Now when I plug the hard disk in, it doesn't get detected.
> I need to issue "usbconfig reset" and it will come up.
>

do you have devd(8) running?

output of "dmeg | tail" and "usbconfig list" before and after plugging
in the hard disk?


-------------8<---snip------>8----------

>
> bye & Thanks
> av.

Regards,
Daniel

[Andrea Venturoli]

On 8/6/26 18:25, Daniel Lysfjord wrote:

> do you have devd(8) running?

Sure.
It's by default and I also need it to start an action (backup) when the
disk is plugged in.

> output of "dmeg | tail" and "usbconfig list" before and after plugging
> in the hard disk?

I don't have those.
I'll provide them next time I have the chance, but it'll probably not
happen before September (as this customer is now closed).


bye & Thanks
av.

[Daniel Lysfjord]

"dmesg | tail", not "dmeg | tail", of course:)

>
> bye & Thanks
> av.

running "devd -d" in a terminal (presumably after stopping the running
one), and/or looking at /var/run/devd.seqpacket.pipe are other options,
to see if things are firing events at all.

Regards,
Daniel