[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#777633: marked as done ([src:linux] sata_sil fails to detect some SSDs)

Your message dated Wed, 28 Apr 2021 18:14:17 +0200
with message-id <E1lbmp4-001LL0-Ds@hullmann.westfalen.local>
and subject line Closing this bug
has caused the Debian Bug report #777633,
regarding [src:linux] sata_sil fails to detect some SSDs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
777633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777633
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:linux
Version: 3.16.7-ckt2-1
Severity: important

--- Please enter the report below this line. ---
Dear maintainers,
I have recently acquired a new SSD for my computer. It is a SanDisk SSD,
its model is SDSSDP-128G-G25. When I connect it to my motherboard, it is
detected by the BIOS. However, when I boot the computer with linux, the drive isnot detected. In my dmesg, I find the following lines (obtained by grepping "ata" inside the dmesg): 
[    0.067483] libata version 3.00 loaded.
[    2.122733] sata_sil 0000:00:12.0: version 2.4
[    2.125426] scsi0 : sata_sil
[    2.128057] scsi1 : sata_sil
[    2.128166] ata1: SATA max UDMA/100 mmio m512@0xfe02f000 tf
0xfe02f080 irq 22
[    2.128170] ata2: SATA max UDMA/100 mmio m512@0xfe02f000 tf
0xfe02f0c0 irq 22
[    2.400191] scsi2 : pata_atiixp
[    2.404020] scsi3 : pata_atiixp
[    2.404420] ata3: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xf800
irq 14
[    2.404422] ata4: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xf808
irq 15
[    2.433044] ata1: SATA link down (SStatus 0 SControl 300)
[    2.564841] ata3.00: ATA-8: WDC WD3200AAJB-00J3A0, 01.03E01, max UDMA/133
[    2.564846] ata3.00: 625142448 sectors, multi 16: LBA48
[    2.565113] ata3.01: ATA-7: Maxtor 6Y160P0, YAR41BW0, max UDMA/133
[    2.565115] ata3.01: 320173056 sectors, multi 16: LBA48
[    2.571800] ata3.00: configured for UDMA/100
[    2.577705] ata3.01: configured for UDMA/100
[    2.616562] ata4.00: ATAPI: TSSTcorpCD/DVDW TS-H552L, 0614, max UDMA/33
[    2.616570] ata4.01: ATAPI: TSSTcorpDVD-ROM TS-H352C, HP02, max UDMA/33
[    2.657502] ata4.00: configured for UDMA/33
[    2.679499] ata4.01: configured for UDMA/33
[    2.738057] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    2.738165] ata2.00: NODEV after polling detection
[    2.738297] scsi 2:0:0:0: Direct-Access     ATA      WDC WD3200AAJB-0
01.0 PQ: 0 ANSI: 5
[    2.740118] scsi 2:0:1:0: Direct-Access     ATA      Maxtor 6Y160P0
YAR4 PQ: 0 ANSI: 5

This occurred with whatever version of the kernel I used, from 3.2 to
3.17, both from debian repository (linux-image-... package) and custom
built (from linux-source package).
If I rebooted the computer after the bug occurred (without powering it
off for a few seconds), moreover, the disk was no longer recognized by
the BIOS, either.

Using a Windows OS on the same hardware, instead, the drive was properly
detected and could be used without problems. The same drive worked
flawlessly on Linux, if connected to a different, AHCI controller (from
an intel ICH7 MOBO).
The bug occurred on two different SATA controllers, both using the
sata_sil driver (one is for sure a Silicon Image 3114 controller, the
other is an integrated controller in an ATI IXP400 chip). The bug could
be worked around by blacklisting sata_sil (and rebuilding the initramfs
without that module) and booting with the ata_generic.all_generic_ide=1
parameter: using that, the controller worked in ATA133 mode and the disk
was properly recognized; however, the controller was not running in SATA
mode (so the speed was reduced). Therefore, I believe the bug must be
somewhere in the sata_sil module (maybe it doesn't deal correctly with
some hardware anomaly?).
This bug makes it impossible to directly install linux on such an SSD
connected to such a controller, since the linux image contained inside
live CDs automatically loads sata_sil for this controller.
If you need any further info, I'll be glad to help.

Here is an extract from the dmesg obtained from kernel 3.16.0-4-amd64
with sata_sil disabled and ata_generic used instead: as you see, the SSD
is detected (ata3). There still appear to be some warnings, though.
[    1.957327] libata version 3.00 loaded.
[    1.967141] scsi0 : pata_atiixp
[    1.976042] scsi1 : pata_atiixp
[    1.976114] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xf800
irq 14
[    1.976117] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xf808
irq 15
[    1.985180] scsi2 : ata_generic
[    1.989543] scsi3 : ata_generic
[    1.989617] ata3: PATA max UDMA/100 cmd 0xfe00 ctl 0xfd00 bmdma
0xfa00 irq 22
[    1.989619] ata4: PATA max UDMA/100 cmd 0xfc00 ctl 0xfb00 bmdma
0xfa08 irq 22
[    2.149595] ata1.00: ATA-8: WDC WD3200AAJB-00J3A0, 01.03E01, max UDMA/133
[    2.149598] ata1.00: 625142448 sectors, multi 16: LBA48
[    2.149851] ata1.01: ATA-7: Maxtor 6Y160P0, YAR41BW0, max UDMA/133
[    2.149853] ata1.01: 320173056 sectors, multi 16: LBA48
[    2.164745] ata1.00: configured for UDMA/100
[    2.180704] ata1.01: configured for UDMA/100
[    2.180816] scsi 0:0:0:0: Direct-Access     ATA      WDC WD3200AAJB-0
3E01 PQ: 0 ANSI: 5
[    2.181181] scsi 0:0:1:0: Direct-Access     ATA      Maxtor 6Y160P0
1BW0 PQ: 0 ANSI: 5
[    2.192560] ata2.00: ATAPI: TSSTcorpCD/DVDW TS-H552L, 0614, max UDMA/33
[    2.192565] ata2.01: ATAPI: TSSTcorpDVD-ROM TS-H352C, HP02, max UDMA/33
[    2.232498] ata2.00: configured for UDMA/33
[    2.264498] ata2.01: configured for UDMA/33
[    7.152060] ata3.00: qc timeout (cmd 0x27)
[    7.152063] ata3.00: failed to read native max address (err_mask=0x4)
[    7.152065] ata3.00: HPA support seems broken, skipping HPA handling
[    7.316490] ata3.00: ATA-9: SanDisk SDSSDP128G, 3.2.0, max UDMA/133
[    7.316492] ata3.00: 246162672 sectors, multi 1: LBA48 NCQ (depth 0/32)
[    7.317438] ata3.00: configured for UDMA/133
[    7.317537] scsi 2:0:0:0: Direct-Access     ATA      SanDisk SDSSDP12
0    PQ: 0 ANSI: 5
[    7.480487] ata4.00: ATA-7: FUJITSU MHV2100BH PL, 892C, max UDMA/100
[    7.480489] ata4.00: 195371568 sectors, multi 16: LBA48
[    7.480493] ata4.00: configured for UDMA/100
[    7.480557] scsi 3:0:0:0: Direct-Access     ATA      FUJITSU MHV2100B
892C PQ: 0 ANSI: 5

--- System information. ---
Architecture: amd64
Kernel: Linux 3.16.0-4-amd64

Debian Release: 8.0
900 solydxk ftp.nluug.nl
900 solydxk community.solydxk.com
850 testing security.debian.org
850 testing debian.fastweb.it
800 unstable debian.fastweb.it
750 experimental debian.fastweb.it
500 debtest debs.slavino.sk
400 testing debian.linuxmint.com
400 debian packages.linuxmint.com

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.

--- End Message ---
--- Begin Message --- 
This bug was filed for a very old kernel. If you can reproduce it with
- the current version in unstable/testing
- the latest kernel from buster.backports
please reopen the bug, see https://www.debian.org/Bugs/server-control

--- End Message ---
Reply to: