Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #78950 > unrolled thread

Bug#1035587: linux: broken AHCI controller on MIPS Loongson 3 (regression from 5.10.162-1)

Started byYunQiang Su <wzssyqa@gmail.com>
First post2023-05-06 03:10 +0200
Last post2023-12-20 21:20 +0100
Articles 9 — 5 participants

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1035587: linux: broken AHCI controller on MIPS Loongson 3 (regression from 5.10.162-1) YunQiang Su <wzssyqa@gmail.com> - 2023-05-06 03:10 +0200
    Bug#1035587: linux: broken AHCI controller on MIPS Loongson 3 (regression from 5.10.162-1) Aurelien Jarno <aurel32@debian.org> - 2023-06-18 11:30 +0200
      Bug#1035587: linux: broken AHCI controller on MIPS Loongson 3 (regression from 5.10.162-1) Huacai Chen <chenhuacai@kernel.org> - 2023-06-19 03:40 +0200
        Bug#1035587: linux: broken AHCI controller on MIPS Loongson 3 (regression from 5.10.162-1) Aurelien Jarno <aurel32@debian.org> - 2023-07-08 12:20 +0200
          Bug#1035587: linux: broken AHCI controller on MIPS Loongson 3 (regression from 5.10.162-1) Huacai Chen <chenhuacai@kernel.org> - 2023-07-11 03:10 +0200
          Bug#1035587: linux: broken AHCI controller on MIPS Loongson 3 (regression from 5.10.162-1) Aurelien Jarno <aurel32@debian.org> - 2023-10-08 12:20 +0200
            Bug#1035587: linux: broken AHCI controller on MIPS Loongson 3 (regression from 5.10.162-1) Julien Cristau <jcristau@debian.org> - 2023-10-30 09:50 +0100
              Bug#1035587: linux: broken AHCI controller on MIPS Loongson 3 (regression from 5.10.162-1) Aurelien Jarno <aurel32@debian.org> - 2023-11-18 17:00 +0100
                Bug#1035587: linux: broken AHCI controller on MIPS Loongson 3 (regression from 5.10.162-1) Salvatore Bonaccorso <carnil@debian.org> - 2023-12-20 21:20 +0100

#78950 — Bug#1035587: linux: broken AHCI controller on MIPS Loongson 3 (regression from 5.10.162-1)

FromYunQiang Su <wzssyqa@gmail.com>
Date2023-05-06 03:10 +0200
SubjectBug#1035587: linux: broken AHCI controller on MIPS Loongson 3 (regression from 5.10.162-1)
Message-ID<GseAV-6UaT-3@gated-at.bofh.it>
Aurelien Jarno <aurel32@debian.org> 于2023年5月6日周六 04:30写道：
>
> Source: linux
> Version: 5.10.178-3
> Severity: important
> X-Debbugs-Cc: dsa@debian.org, debian-mips@lists.debian.org, syq@debian.org
>
> Following the point release, the buildd mipsel-osuosl-03.d.o does not
> boot anymore, with errors in the AHCI controller:
>
> [   35.912147] ata4.00: exception Emask 0x0 SAct 0x20000000 SErr 0x0 action 0x6 frozen
> [   35.919769] ata4.00: failed command: WRITE FPDMA QUEUED
> [   35.924968] ata4.00: cmd 61/20:e8:00:f0:e1/00:00:00:00:00/40 tag 29 ncq dma 16384 out
> [   35.924968]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> [   35.940097] ata4.00: status: { DRDY }
> [   35.943743] ata4: hard resetting link
>
> While that initially looks like a hardware issue, it appears that
> reverting the kernel to 5.10.162-1 (from 5.10.178-3) fixes the issue.
> Strangely mipsel.osuosl-05.d.o, which seems to be similar hardware (CPU,
> motherboard and SATA drive), does not exhibit the same issue.
>

Maybe the different firmwares are used for them...
CCed Huacai and Jiaxun.

> You'll find attached the output of /proc/cpuinfo, lspci and the full
> boot log.



-- 
YunQiang Su

[toc] | [next] | [standalone]

#79339

FromAurelien Jarno <aurel32@debian.org>
Date2023-06-18 11:30 +0200
Message-ID<GHWTn-gM8a-3@gated-at.bofh.it>
In reply to#78950
Hi,

On 2023-05-07 19:22, Jiaxun Yang wrote:
> 
> 
> > 2023年5月6日 01:58，YunQiang Su <wzssyqa@gmail.com> 写道：
> > 
> > Aurelien Jarno <aurel32@debian.org> 于2023年5月6日周六 04:30写道：
> >> 
> >> Source: linux
> >> Version: 5.10.178-3
> >> Severity: important
> >> X-Debbugs-Cc: dsa@debian.org, debian-mips@lists.debian.org, syq@debian.org
> >> 
> >> Following the point release, the buildd mipsel-osuosl-03.d.o does not
> >> boot anymore, with errors in the AHCI controller:
> >> 
> >> [   35.912147] ata4.00: exception Emask 0x0 SAct 0x20000000 SErr 0x0 action 0x6 frozen
> >> [   35.919769] ata4.00: failed command: WRITE FPDMA QUEUED
> >> [   35.924968] ata4.00: cmd 61/20:e8:00:f0:e1/00:00:00:00:00/40 tag 29 ncq dma 16384 out
> >> [   35.924968]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> >> [   35.940097] ata4.00: status: { DRDY }
> >> [   35.943743] ata4: hard resetting link
> >> 
> >> While that initially looks like a hardware issue, it appears that
> >> reverting the kernel to 5.10.162-1 (from 5.10.178-3) fixes the issue.
> >> Strangely mipsel.osuosl-05.d.o, which seems to be similar hardware (CPU,
> >> motherboard and SATA drive), does not exhibit the same issue.
> >> 
> > 
> > Maybe the different firmwares are used for them...
> > CCed Huacai and Jiaxun.
> 
> I’m unable to reproduce on my side. Perhaps different hardware.
> Is it possible to bisect Kernel on that machine to see of reverting that two commits do help?

I have bisected the issue and I confirm the intuition from Cyril. The
first bad commit is 654ae539254d10042869fdc77ad04c09e7eff1fd. Reverting
both commits (they are linked) indeed fixes the issue.

Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                     http://aurel32.net

[toc] | [prev] | [next] | [standalone]

#79354

FromHuacai Chen <chenhuacai@kernel.org>
Date2023-06-19 03:40 +0200
Message-ID<GIc25-gVda-3@gated-at.bofh.it>
In reply to#79339
On Sun, Jun 18, 2023 at 5:24 PM Aurelien Jarno <aurel32@debian.org> wrote:
>
> Hi,
>
> On 2023-05-07 19:22, Jiaxun Yang wrote:
> >
> >
> > > 2023年5月6日 01:58，YunQiang Su <wzssyqa@gmail.com> 写道：
> > >
> > > Aurelien Jarno <aurel32@debian.org> 于2023年5月6日周六 04:30写道：
> > >>
> > >> Source: linux
> > >> Version: 5.10.178-3
> > >> Severity: important
> > >> X-Debbugs-Cc: dsa@debian.org, debian-mips@lists.debian.org, syq@debian.org
> > >>
> > >> Following the point release, the buildd mipsel-osuosl-03.d.o does not
> > >> boot anymore, with errors in the AHCI controller:
> > >>
> > >> [   35.912147] ata4.00: exception Emask 0x0 SAct 0x20000000 SErr 0x0 action 0x6 frozen
> > >> [   35.919769] ata4.00: failed command: WRITE FPDMA QUEUED
> > >> [   35.924968] ata4.00: cmd 61/20:e8:00:f0:e1/00:00:00:00:00/40 tag 29 ncq dma 16384 out
> > >> [   35.924968]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> > >> [   35.940097] ata4.00: status: { DRDY }
> > >> [   35.943743] ata4: hard resetting link
> > >>
> > >> While that initially looks like a hardware issue, it appears that
> > >> reverting the kernel to 5.10.162-1 (from 5.10.178-3) fixes the issue.
> > >> Strangely mipsel.osuosl-05.d.o, which seems to be similar hardware (CPU,
> > >> motherboard and SATA drive), does not exhibit the same issue.
> > >>
> > >
> > > Maybe the different firmwares are used for them...
> > > CCed Huacai and Jiaxun.
> >
> > I’m unable to reproduce on my side. Perhaps different hardware.
> > Is it possible to bisect Kernel on that machine to see of reverting that two commits do help?
>
> I have bisected the issue and I confirm the intuition from Cyril. The
> first bad commit is 654ae539254d10042869fdc77ad04c09e7eff1fd. Reverting
> both commits (they are linked) indeed fixes the issue.
Seems a firmware bug, latest firmware should configure a suitable MRRS.

Huacai
>
> Aurelien
>
> --
> Aurelien Jarno                          GPG: 4096R/1DDD8C9B
> aurelien@aurel32.net                     http://aurel32.net

[toc] | [prev] | [next] | [standalone]

#79540

FromAurelien Jarno <aurel32@debian.org>
Date2023-07-08 12:20 +0200
Message-ID<GPdcJ-3NnE-9@gated-at.bofh.it>
In reply to#79354
Hi,

On 2023-06-24 11:46, Aurelien Jarno wrote:
> Hi,
> 
> On 2023-06-19 09:37, Huacai Chen wrote:
> > On Sun, Jun 18, 2023 at 5:24 PM Aurelien Jarno <aurel32@debian.org> wrote:
> > >
> > > Hi,
> > >
> > > On 2023-05-07 19:22, Jiaxun Yang wrote:
> > > >
> > > >
> > > > > 2023年5月6日 01:58，YunQiang Su <wzssyqa@gmail.com> 写道：
> > > > >
> > > > > Aurelien Jarno <aurel32@debian.org> 于2023年5月6日周六 04:30写道：
> > > > >>
> > > > >> Source: linux
> > > > >> Version: 5.10.178-3
> > > > >> Severity: important
> > > > >> X-Debbugs-Cc: dsa@debian.org, debian-mips@lists.debian.org, syq@debian.org
> > > > >>
> > > > >> Following the point release, the buildd mipsel-osuosl-03.d.o does not
> > > > >> boot anymore, with errors in the AHCI controller:
> > > > >>
> > > > >> [   35.912147] ata4.00: exception Emask 0x0 SAct 0x20000000 SErr 0x0 action 0x6 frozen
> > > > >> [   35.919769] ata4.00: failed command: WRITE FPDMA QUEUED
> > > > >> [   35.924968] ata4.00: cmd 61/20:e8:00:f0:e1/00:00:00:00:00/40 tag 29 ncq dma 16384 out
> > > > >> [   35.924968]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> > > > >> [   35.940097] ata4.00: status: { DRDY }
> > > > >> [   35.943743] ata4: hard resetting link
> > > > >>
> > > > >> While that initially looks like a hardware issue, it appears that
> > > > >> reverting the kernel to 5.10.162-1 (from 5.10.178-3) fixes the issue.
> > > > >> Strangely mipsel.osuosl-05.d.o, which seems to be similar hardware (CPU,
> > > > >> motherboard and SATA drive), does not exhibit the same issue.
> > > > >>
> > > > >
> > > > > Maybe the different firmwares are used for them...
> > > > > CCed Huacai and Jiaxun.
> > > >
> > > > I’m unable to reproduce on my side. Perhaps different hardware.
> > > > Is it possible to bisect Kernel on that machine to see of reverting that two commits do help?
> > >
> > > I have bisected the issue and I confirm the intuition from Cyril. The
> > > first bad commit is 654ae539254d10042869fdc77ad04c09e7eff1fd. Reverting
> > > both commits (they are linked) indeed fixes the issue.
> > Seems a firmware bug, latest firmware should configure a suitable MRRS.
> 
> Ok, thanks for the feedback. Given it's not a kernel bug, I am closing
> it.
> 
> That said, can someone please send us the procedure to upgrade the
> firmware on this machine, so that we can continue using it as a buildd?

Any news about that? We need to be able to run the latest stable kernel
on the build daemon.

Thanks,
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                     http://aurel32.net

[toc] | [prev] | [next] | [standalone]

#79558

FromHuacai Chen <chenhuacai@kernel.org>
Date2023-07-11 03:10 +0200
Message-ID<GQa37-4nwD-1@gated-at.bofh.it>
In reply to#79540
On Mon, Jul 10, 2023 at 4:14 PM Jiaxun Yang <jiaxun.yang@flygoat.com> wrote:
>
> Hi all,
>
> I don't have much idea on firmware, so I don't know if firmware update
> is possible
> for that system.
>
> @Huacai, is it acceptable to revert MRRS/MPS workaround patch all MIPS based
> Loongson system? Or leave a cmdline option to configure workaround type?
Contact the machine provider to get new firmwares?

Huacai
>
> Thanks
> - Jiaxun
>
> 在 2023/7/8 18:11, Aurelien Jarno 写道:
> > Hi,
> >
> > On 2023-06-24 11:46, Aurelien Jarno wrote:
> >> Hi,
> >>
> >> On 2023-06-19 09:37, Huacai Chen wrote:
> >>> On Sun, Jun 18, 2023 at 5:24 PM Aurelien Jarno <aurel32@debian.org> wrote:
> >>>> Hi,
> >>>>
> >>>> On 2023-05-07 19:22, Jiaxun Yang wrote:
> >>>>>
> >>>>>> 2023年5月6日 01:58，YunQiang Su <wzssyqa@gmail.com> 写道：
> >>>>>>
> >>>>>> Aurelien Jarno <aurel32@debian.org> 于2023年5月6日周六 04:30写道：
> >>>>>>> Source: linux
> >>>>>>> Version: 5.10.178-3
> >>>>>>> Severity: important
> >>>>>>> X-Debbugs-Cc: dsa@debian.org, debian-mips@lists.debian.org, syq@debian.org
> >>>>>>>
> >>>>>>> Following the point release, the buildd mipsel-osuosl-03.d.o does not
> >>>>>>> boot anymore, with errors in the AHCI controller:
> >>>>>>>
> >>>>>>> [   35.912147] ata4.00: exception Emask 0x0 SAct 0x20000000 SErr 0x0 action 0x6 frozen
> >>>>>>> [   35.919769] ata4.00: failed command: WRITE FPDMA QUEUED
> >>>>>>> [   35.924968] ata4.00: cmd 61/20:e8:00:f0:e1/00:00:00:00:00/40 tag 29 ncq dma 16384 out
> >>>>>>> [   35.924968]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> >>>>>>> [   35.940097] ata4.00: status: { DRDY }
> >>>>>>> [   35.943743] ata4: hard resetting link
> >>>>>>>
> >>>>>>> While that initially looks like a hardware issue, it appears that
> >>>>>>> reverting the kernel to 5.10.162-1 (from 5.10.178-3) fixes the issue.
> >>>>>>> Strangely mipsel.osuosl-05.d.o, which seems to be similar hardware (CPU,
> >>>>>>> motherboard and SATA drive), does not exhibit the same issue.
> >>>>>>>
> >>>>>> Maybe the different firmwares are used for them...
> >>>>>> CCed Huacai and Jiaxun.
> >>>>> I’m unable to reproduce on my side. Perhaps different hardware.
> >>>>> Is it possible to bisect Kernel on that machine to see of reverting that two commits do help?
> >>>> I have bisected the issue and I confirm the intuition from Cyril. The
> >>>> first bad commit is 654ae539254d10042869fdc77ad04c09e7eff1fd. Reverting
> >>>> both commits (they are linked) indeed fixes the issue.
> >>> Seems a firmware bug, latest firmware should configure a suitable MRRS.
> >> Ok, thanks for the feedback. Given it's not a kernel bug, I am closing
> >> it.
> >>
> >> That said, can someone please send us the procedure to upgrade the
> >> firmware on this machine, so that we can continue using it as a buildd?
> > Any news about that? We need to be able to run the latest stable kernel
> > on the build daemon.
> >
> > Thanks,
> > Aurelien
> >
>

[toc] | [prev] | [next] | [standalone]

#80622

FromAurelien Jarno <aurel32@debian.org>
Date2023-10-08 12:20 +0200
Message-ID<Hmz3b-emNB-5@gated-at.bofh.it>
In reply to#79540
On 2023-07-19 16:28, Jiaxun Yang wrote:
> 
> 
> 在 2023/7/8 18:11, Aurelien Jarno 写道:
> [...]
> > Any news about that? We need to be able to run the latest stable kernel
> > on the build daemon.
> 
> Hi all,
> 
> After receiving more reports on that patch I think we shoud workaround it in
> Kernel.
> 
> I had posted a patch to kernel, kernel bug tracker [1].
> 
> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=217680

Any news about that? I haven't spotted any fix for this in Linus' tree
nor in next.

Thanks
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                     http://aurel32.net

[toc] | [prev] | [next] | [standalone]

#80760

FromJulien Cristau <jcristau@debian.org>
Date2023-10-30 09:50 +0100
Message-ID<Huw89-1RdF-5@gated-at.bofh.it>
In reply to#80622
Hi,

On Mon, Oct  9, 2023 at 09:08:31 +0100, Jiaxun Yang wrote:

> 
> 
> 在2023年10月8日十月 上午11:11，Aurelien Jarno写道：
> > On 2023-07-19 16:28, Jiaxun Yang wrote:
> >> 
> >> 
> >> 在 2023/7/8 18:11, Aurelien Jarno 写道:
> >> [...]
> >> > Any news about that? We need to be able to run the latest stable kernel
> >> > on the build daemon.
> >> 
> >> Hi all,
> >> 
> >> After receiving more reports on that patch I think we shoud workaround it in
> >> Kernel.
> >> 
> >> I had posted a patch to kernel, kernel bug tracker [1].
> >> 
> >> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=217680
> >
> > Any news about that? I haven't spotted any fix for this in Linus' tree
> > nor in next.
> 
> Still waiting for a response from PCI folks.
> Will resend the patch later.
> 
Any news on this?  It's been several months...

Thanks,
Julien

[toc] | [prev] | [next] | [standalone]

#80898

FromAurelien Jarno <aurel32@debian.org>
Date2023-11-18 17:00 +0100
Message-ID<HBvTH-6jGY-5@gated-at.bofh.it>
In reply to#80760
Hi,

On 2023-10-30 09:46, Julien Cristau wrote:
> Hi,
> 
> On Mon, Oct  9, 2023 at 09:08:31 +0100, Jiaxun Yang wrote:
> 
> > 
> > 
> > 在2023年10月8日十月 上午11:11，Aurelien Jarno写道：
> > > On 2023-07-19 16:28, Jiaxun Yang wrote:
> > >> 
> > >> 
> > >> 在 2023/7/8 18:11, Aurelien Jarno 写道:
> > >> [...]
> > >> > Any news about that? We need to be able to run the latest stable kernel
> > >> > on the build daemon.
> > >> 
> > >> Hi all,
> > >> 
> > >> After receiving more reports on that patch I think we shoud workaround it in
> > >> Kernel.
> > >> 
> > >> I had posted a patch to kernel, kernel bug tracker [1].
> > >> 
> > >> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=217680
> > >
> > > Any news about that? I haven't spotted any fix for this in Linus' tree
> > > nor in next.
> > 
> > Still waiting for a response from PCI folks.
> > Will resend the patch later.
> > 
> Any news on this?  It's been several months...

Gentle ping about the issue.

Thanks,
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                     http://aurel32.net

[toc] | [prev] | [next] | [standalone]

#81299

FromSalvatore Bonaccorso <carnil@debian.org>
Date2023-12-20 21:20 +0100
Message-ID<HNbcR-eW2V-3@gated-at.bofh.it>
In reply to#80898
Hi,

On Sat, Nov 18, 2023 at 04:50:36PM +0100, Aurelien Jarno wrote:
> Hi,
> 
> On 2023-10-30 09:46, Julien Cristau wrote:
> > Hi,
> > 
> > On Mon, Oct  9, 2023 at 09:08:31 +0100, Jiaxun Yang wrote:
> > 
> > > 
> > > 
> > > 在2023年10月8日十月 上午11:11，Aurelien Jarno写道：
> > > > On 2023-07-19 16:28, Jiaxun Yang wrote:
> > > >> 
> > > >> 
> > > >> 在 2023/7/8 18:11, Aurelien Jarno 写道:
> > > >> [...]
> > > >> > Any news about that? We need to be able to run the latest stable kernel
> > > >> > on the build daemon.
> > > >> 
> > > >> Hi all,
> > > >> 
> > > >> After receiving more reports on that patch I think we shoud workaround it in
> > > >> Kernel.
> > > >> 
> > > >> I had posted a patch to kernel, kernel bug tracker [1].
> > > >> 
> > > >> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=217680
> > > >
> > > > Any news about that? I haven't spotted any fix for this in Linus' tree
> > > > nor in next.
> > > 
> > > Still waiting for a response from PCI folks.
> > > Will resend the patch later.
> > > 
> > Any news on this?  It's been several months...
> 
> Gentle ping about the issue.

Good news: The issue got fixed in mainline in 6.7-rc6, and the change
backported to 6.6.8, 6.1.69, 5.10.205. So it will be in each of the
next rebases.

Regards,
Salvatore

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web