From: marius@psihoexpert.ro
To: "Damien Le Moal" <damien.lemoal@opensource.wdc.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Bug report for ahci-mvebu driver
Date: Tue, 07 Feb 2023 18:40:01 +0000 [thread overview]
Message-ID: <6936c460663c956b5c77215eeef140d7@psihoexpert.ro> (raw)
In-Reply-To: <1e069565-a391-0f33-0714-ba9cc3792a42@opensource.wdc.com>
January 31, 2023 9:28 AM, "Damien Le Moal" <damien.lemoal@opensource.wdc.com> wrote:
> I did testing on Intel & AMD machines with different adpaters/drives/pmp that I
> have (AHCI, ASMedia and Marvell adapters). Everything was OK on my end.
>
> The tag is for this kernel only. If backporting to 5.15 does not solve the
> issue, we will need to take that separately and redo debugging on that version.
> I would like to send the patch to Linus by the end of the week...
>
> --
> Damien Le Moal
> Western Digital Research
I saw that the patch was applied to v5.15 too. That was probably not a good ideea. This weekend I tried to test the patch in OpenWrt kernel v5.15. It doesn't work:
--- RAID box connected ---
[ 1772.100899] ata2: SATA link down (SStatus 111 SControl 310)
[ 1772.114132] ata2: limiting SATA link speed to 1.5 Gbps
...and these two lines repeat forever. There is no "giving up".
I tried the workaround "libata.force=2:1.5Gbps". It works, but with a delay:
[ 116.705772] ata2: SATA link down (SStatus 101 SControl 300)
[ 119.175752] ata2: COMRESET failed (errno=-32)
[ 119.180133] ata2: reset failed (errno=-32), retrying in 8 secs
[ 127.205713] ata2: limiting SATA link speed to <unknown>
[ 129.475703] ata2: COMRESET failed (errno=-32)
[ 129.480084] ata2: reset failed (errno=-32), retrying in 8 secs
[ 137.445667] ata2: limiting SATA link speed to <unknown>
[ 139.715666] ata2: COMRESET failed (errno=-32)
[ 139.720052] ata2: reset failed (errno=-32), retrying in 33 secs
[ 172.645529] ata2: limiting SATA link speed to <unknown>
[ 173.585525] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 3D0)
[ 173.591831] ata2.15: Port Multiplier 1.2, 0x197b:0x0325 r193, 8 ports, feat 0xf/0x1f
[ 173.600838] ahci-mvebu f10a8000.sata: FBS is enabled
[ 173.605977] ata2.00: hard resetting link
[ 173.937078] ata2.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 173.943563] ata2.01: hard resetting link
[ 174.277073] ata2.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 174.283555] ata2.02: hard resetting link
[ 174.617075] ata2.02: SATA link down (SStatus 0 SControl 300)
[ 174.622787] ata2.03: hard resetting link
[ 174.957074] ata2.03: SATA link down (SStatus 0 SControl 300)
[ 174.962785] ata2.04: hard resetting link
[ 175.297075] ata2.04: SATA link down (SStatus 0 SControl 300)
[ 175.302784] ata2.05: hard resetting link
[ 175.637072] ata2.05: SATA link down (SStatus 0 SControl 300)
[ 175.642781] ata2.06: hard resetting link
[ 175.977071] ata2.06: SATA link down (SStatus 0 SControl 300)
[ 175.982781] ata2.07: hard resetting link
[ 176.317063] ata2.07: SATA link down (SStatus 0 SControl 300)
[ 176.322839] ata2.00: ATA-6: WDC WD50ARC-5040-VOL#01, 0100 AX, max UDMA/133
[ 176.329758] ata2.00: 976773168 sectors, multi 0: LBA48
[ 176.335595] ata2.00: configured for UDMA/133
[ 176.339944] ata2.01: ATA-6: Areca Archive, 0100 AX, max UDMA/133
[ 176.346160] ata2.01: 23437498368 sectors, multi 0: LBA48
[ 176.351830] ata2.01: configured for UDMA/133
[ 176.356303] ata2: EH complete
So probably some other commit needs backporting before this one works. Any ideea which might it be?
I will try another bisect when I have time. Any clues would help a lot.
Marius Dinu
next prev parent reply other threads:[~2023-02-07 18:40 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 19:21 Bug report for ahci-mvebu driver Dinu Marius
2022-11-06 7:05 ` 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 [this message]
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=6936c460663c956b5c77215eeef140d7@psihoexpert.ro \
--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