Overview & identity
1095:3112 is the sil_3112 table entry; the kernel vendor macro is CMD. This historical macro name does not turn the attached drive into a CMD-branded product.
- Curated identifiers
pci 1095:3112
A numeric match establishes a candidate family within the reviewed evidence. Marketing names, board variants, subsystem conditions and successful operation remain separate questions.
Driver & binding
sata_sil is a libata low-level driver with controller-specific interrupt/error handling. AHCI-only advice is not automatically appropriate simply because the transport is SATA.
sata_sil— kernel driver/module candidate
Firmware
Device/revision dependent
Controller firmware, option ROM and drive firmware can be separate. The reviewed sources do not establish a host-loaded filename for this profile; firmware revision and update policy require the actual controller and OEM identity.
Read-only diagnostics
Run one displayed command at a time. Replace uppercase placeholders with the affected device, interface or module from your own output. Commands are never executed here. Read-only output can still contain private identifiers.
Check the PCI function and bound driver
lspci -nnk -s BDFReplace BDF with the domain:bus:device.function address. Look for [1095:3112] and Kernel driver in use. sata_sil in Kernel modules is only a candidate, not proof of binding.
Inspect visible block-device identities
lsblk -d -o NAME,MODEL,TRAN,HCTLMODEL describes a block device or a controller-presented logical volume; it is not a PCI-controller identity. HCTL helps distinguish SCSI targets. TRAN can be absent, and this list does not establish the complete physical disk topology.
Read controller and transport messages
sudo journalctl -k -b --no-pagerElevated access may be needed. Root reads the current boot kernel journal. Associate sata_sil messages, port/host identifiers and timeout/reset timestamps with the actual controller. A reset message alone does not prove a bad disk or a firmware defect.
Limitations & related issues
A legacy controller’s source support is not a statement about modern drive-feature compatibility or measured throughput. The controller, PCI bus and each SATA link can impose independent limits.
These guides are linked for relevant observations, not as known defects of every device in this family.
- SATA CRC errors and repeated link resets · First documented next step
- ATA uncorrectable sectors and read errors · First documented next step
Choose a hardware diagnostic workflow · Inspect a log excerpt in Fix Lab
References
Source review records a checked implementation or document, not a reproduced hardware test. Version-specific tables do not establish a minimum kernel or guaranteed operation.
- Upstream Linux: drivers/ata/sata_sil.c
Reviewed upstream source
PCI_VDEVICE(CMD, 0x3112); line 115 - Upstream Linux: include/linux/pci_ids.h
Reviewed upstream source
PCI_VENDOR_ID_CMD ; line 1099 - Upstream Linux: Documentation/driver-api/libata.rst
Project or distribution documentation
SCSI<->ATA translation; line 12