From: "Dinu Marius" <marius@psihoexpert.ro>
To: <damien.lemoal@opensource.wdc.com>
Cc: <linux-ide@vger.kernel.org>
Subject: Bug report for ahci-mvebu driver
Date: Tue, 1 Nov 2022 21:21:37 +0200 [thread overview]
Message-ID: <ABCCF36A7F484055A8E63A8B739DC7B8@graph> (raw)
Hello.
I'm contacting you because your email is listed in www.kernel.org/doc/linux/MAINTAINERS
I encountered a problem with the ahci-mvebu driver. I think it's a bug.
Hardware:
Areca ARC-5040 RAID enclosure (DAS), eSATA port, 8 SATA drive bays with 1x 500GB HDD stand-alone and 7x 2TB HDDs in RAID5.
Linksys WRT-1900ACS v2 router, Marvell Armada 385 (88F6820), one eSATAp using ahci-mvebu driver with port-multiplier support.
The router runs OpenWrt with kernel version 5.15.
Problem encountered:
Areca DAS is not detected properly. When I connect it, I get these repeating errors in kernel log:
[--- from boot log ---]
<4>[ 1.490840] ahci-mvebu f10a8000.sata: supply ahci not found, using dummy regulator
<4>[ 1.498512] ahci-mvebu f10a8000.sata: supply phy not found, using dummy regulator
<4>[ 1.506053] ahci-mvebu f10a8000.sata: supply target not found, using dummy regulator
<6>[ 1.513896] ahci-mvebu f10a8000.sata: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl platform mode
<6>[ 1.522994] ahci-mvebu f10a8000.sata: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs
<6>[ 1.532212] scsi host0: ahci-mvebu
<6>[ 1.535848] scsi host1: ahci-mvebu
<6>[ 1.539353] ata1: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff] port 0x100 irq 49
<6>[ 1.547313] ata2: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff] port 0x180 irq 49
[--- Areca connected ---]
<6>[ 742.795979] ata2: SATA link down (SStatus 100 SControl 300)
<3>[ 745.465974] ata2: COMRESET failed (errno=-32)
<4>[ 745.470361] ata2: reset failed (errno=-32), retrying in 8 secs
<3>[ 755.365973] ata2: COMRESET failed (errno=-32)
<4>[ 755.370361] ata2: reset failed (errno=-32), retrying in 8 secs
<6>[ 764.655979] ata2: SATA link down (SStatus 100 SControl 300)
<6>[ 766.045984] ata2: SATA link down (SStatus 101 SControl 300)
<6>[ 767.576004] ata2: SATA link down (SStatus 100 SControl 300)
<6>[ 768.325978] ata2: SATA link down (SStatus 100 SControl 300)
<3>[ 770.865973] ata2: COMRESET failed (errno=-32)
<4>[ 770.870360] ata2: reset failed (errno=-32), retrying in 8 secs
<6>[ 779.515985] ata2: SATA link down (SStatus 101 SControl 300)
<6>[ 780.275979] ata2: SATA link down (SStatus 100 SControl 300)
The same errors appear if I leave it connected during reboot.
I tried to limit SATA speed to 150 and to disable NCQ from Areca admin interface. It didn't work.
I found no way of making it work.
The same router works perfectly when I connect a laptop HDD.
The same DAS, including the same eSATA cable, works perfectly when connected to an older
Linksys WRT-1900AC v1 with Marvell Armada XP (MV78230), using sata-mv driver.
This is the kernel log from the older router:
[--- from boot log ---]
<7>[ 1.612541] sata_mv f10a0000.sata: version 1.28
<6>[ 1.612652] sata_mv f10a0000.sata: slots 32 ports 1
<6>[ 1.618121] scsi host0: sata_mv
<6>[ 1.621486] ata1: SATA max UDMA/133 irq 36
[--- Areca connected ---]
<6>[88761.966331] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
<6>[88761.975472] ata1.15: Port Multiplier 1.2, 0x197b:0x0325 r193, 8 ports, feat 0xf/0x1f
<6>[88764.670933] ata1.00: ATA-6: WDC WD50ARC-5040-VOL#01, 0100 AX, max UDMA/133
<6>[88764.677860] ata1.00: 976773168 sectors, multi 0: LBA48
<6>[88764.683599] ata1.00: configured for UDMA/133
<6>[88764.688391] ata1.01: ATA-6: Areca Archive, 0100 AX, max UDMA/133
<6>[88764.694596] ata1.01: 23437498368 sectors, multi 0: LBA48
<6>[88764.700779] ata1.01: configured for UDMA/133
<5>[88764.705557] scsi 0:0:0:0: Direct-Access ATA WDC WD50ARC-5040 n/a PQ: 0 ANSI: 5
<5>[88764.714802] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB)
<5>[88764.722521] sd 0:0:0:0: [sda] Write Protect is off
<7>[88764.727558] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
<5>[88764.727915] scsi 0:1:0:0: Direct-Access ATA Areca Archive n/a PQ: 0 ANSI: 5
<5>[88764.728706] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
<5>[88764.745574] sd 0:1:0:0: [sdb] 23437498368 512-byte logical blocks: (12.0 TB/10.9 TiB)
<5>[88764.753819] sd 0:1:0:0: [sdb] Write Protect is off
<7>[88764.758886] sd 0:1:0:0: [sdb] Mode Sense: 00 3a 00 00
<5>[88764.759101] sd 0:1:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
<5>[88764.760537] sd 0:0:0:0: [sda] Attached SCSI disk
<5>[88764.772600] sd 0:1:0:0: [sdb] Attached SCSI disk
I'm not currently using the new router, so it's available for tests.
Thanks.
Marius Dinu
next reply other threads:[~2022-11-01 19:53 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 19:21 Dinu Marius [this message]
2022-11-06 7:05 ` Bug report for ahci-mvebu driver Damien Le Moal
2022-11-07 9:22 ` marius
2022-11-08 6:27 ` Damien Le Moal
2022-11-09 19:52 ` marius
2022-11-09 19:55 ` marius
2022-11-10 2:05 ` Damien Le Moal
2022-11-11 22:32 ` marius
2022-11-12 1:57 ` Damien Le Moal
2022-11-14 20:52 ` marius
2022-11-15 3:02 ` Damien Le Moal
2022-11-15 7:28 ` marius
2022-11-15 8:10 ` Damien Le Moal
2022-11-18 18:24 ` Dinu Marius
2022-11-24 2:40 ` Damien Le Moal
2022-12-04 1:41 ` marius
2022-12-04 10:22 ` Pali Rohár
2022-12-04 21:14 ` marius
2022-12-04 21:46 ` Pali Rohár
2022-12-05 2:02 ` Damien Le Moal
2022-12-06 6:08 ` Damien Le Moal
2022-12-07 18:27 ` marius
2022-12-07 21:54 ` Damien Le Moal
2022-12-07 22:51 ` Damien Le Moal
2022-12-08 18:06 ` marius
2022-12-09 0:34 ` Damien Le Moal
2022-12-09 2:58 ` Damien Le Moal
2022-12-09 7:31 ` marius
2022-12-09 9:28 ` Damien Le Moal
2022-12-09 18:30 ` marius
2023-01-14 18:01 ` marius
2023-01-15 23:37 ` Damien Le Moal
2023-01-17 8:26 ` Damien Le Moal
2023-01-18 19:43 ` marius
2023-01-19 0:29 ` Damien Le Moal
2023-01-19 18:46 ` marius
2023-01-23 7:02 ` Damien Le Moal
2023-01-23 20:00 ` marius
2023-01-23 23:00 ` Damien Le Moal
2023-01-24 8:04 ` marius
2023-01-24 9:53 ` Damien Le Moal
2023-01-24 17:02 ` marius
2023-01-27 5:13 ` Damien Le Moal
2023-01-27 6:28 ` Damien Le Moal
2023-01-28 17:08 ` marius
2023-01-29 2:23 ` Damien Le Moal
2023-01-29 10:24 ` marius
2023-01-30 1:16 ` Damien Le Moal
2023-01-30 2:38 ` Damien Le Moal
2023-01-30 7:23 ` marius
2023-01-30 7:37 ` Damien Le Moal
2023-01-30 23:22 ` Damien Le Moal
2023-01-31 7:20 ` marius
2023-01-31 7:28 ` Damien Le Moal
2023-02-07 18:40 ` marius
2023-02-07 23:39 ` Damien Le Moal
2023-02-08 12:17 ` marius
2023-02-08 23:00 ` Damien Le Moal
2023-02-12 13:14 ` marius
2023-02-12 23:11 ` Damien Le Moal
2023-01-24 17:06 ` Bug report for sata_via driver marius
2023-01-25 1:26 ` Damien Le Moal
2022-12-08 21:26 ` Bug report for ahci-mvebu driver Pali Rohár
2022-12-09 1:54 ` Damien Le Moal
2022-11-26 14:26 ` Pali Rohár
2023-01-23 9:10 ` Hajo Noerenberg
2023-01-23 12:13 ` Damien Le Moal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ABCCF36A7F484055A8E63A8B739DC7B8@graph \
--to=marius@psihoexpert.ro \
--cc=damien.lemoal@opensource.wdc.com \
--cc=linux-ide@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox