Re: [PATCH 5.13 000/156] 5.13.5-rc1 review

4 messages, 2 authors, 2021-07-23 · open the first message on its own page

Re: [PATCH 5.13 000/156] 5.13.5-rc1 review

From: Naresh Kamboju <hidden>
Date: 2021-07-23 11:56:38

On Thu, 22 Jul 2021 at 22:17, Greg Kroah-Hartman
[off-list ref] wrote:
This is the start of the stable review cycle for the 5.13.5 release.
There are 156 patches in this series, all will be posted as a response
to this one.  If anyone has any issues with these being applied, please
let me know.

Responses should be made by Sat, 24 Jul 2021 15:56:00 +0000.
Anything received after that time might be too late.

The whole patch series can be found in one patch at:
        https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.13.5-rc1.gz
or in the git tree and branch at:
        git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.13.y
and the diffstat can be found below.

thanks,

greg k-h
The following error is due to SATA drive format failing with arm64 64k-page
size ( CONFIG_ARM64_64K_PAGES=y ) kernel.
while running LTP syscalls test suite on running 5.13.3 and 5.13.5-rc1 kernel.

First it was noticed on the stable-rc 5.13.3-rc2 kernel.

Whereas 64bit kernel and 32bit kernel pass with 4K page size.

Initially, I thought it could be a Hard drive fault but it is reproducible on
other devices but not always. Which is a blocker to bisect the problem.

The steps to reproduce:
 - Boot arm64 juno device with 64k page stable-rc 5.13 kernel Image [1]
   - CONFIG_ARM64_64K_PAGES=y
 - format connected SATA drives and mount /scratch
 - Use the mounted /scratch for LTP runs to create and delete files from this
 - cd /opt/ltp
 - ./runltp -d /scratch -f syscalls


error log:
-------------
tst_device.c:89: TINFO: Found free device 0 '/dev/loop0'
tst_test.c:889: TINFO: Formatting /dev/loop0 with ext2 opts='' extra opts=''
mke2fs 1.43.8 (1-Jan-2018)
[  776.850122] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
[  776.874645] ata1.00: configured for UDMA/100
[  776.879042] ata1: EH complete
[  776.912010] ata1.00: exception Emask 0x20 SAct 0xc0 SErr 0x0 action
0x6 frozen
[  776.919299] ata1.00: irq_stat 0x00020002, PCI target abort while
transferring data
[  776.926983] ata1.00: failed command: WRITE FPDMA QUEUED
[  776.932263] ata1.00: cmd 61/08:30:00:10:84/00:00:06:00:00/40 tag 6
ncq dma 4096 out
[  776.932263]          res e6/ff:00:00:00:00/00:00:00:00:e6/00 Emask
0x22 (host bus error)
[  776.948089] ata1.00: status: { Busy }
[  776.951766] ata1.00: error: { ICRC UNC AMNF IDNF ABRT }

374 more lines

Re: [PATCH 5.13 000/156] 5.13.5-rc1 review

From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date: 2021-07-23 12:03:41

On Fri, Jul 23, 2021 at 05:26:22PM +0530, Naresh Kamboju wrote:
On Thu, 22 Jul 2021 at 22:17, Greg Kroah-Hartman
[off-list ref] wrote:
quoted
This is the start of the stable review cycle for the 5.13.5 release.
There are 156 patches in this series, all will be posted as a response
to this one.  If anyone has any issues with these being applied, please
let me know.

Responses should be made by Sat, 24 Jul 2021 15:56:00 +0000.
Anything received after that time might be too late.

The whole patch series can be found in one patch at:
        https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.13.5-rc1.gz
or in the git tree and branch at:
        git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.13.y
and the diffstat can be found below.

thanks,

greg k-h
The following error is due to SATA drive format failing with arm64 64k-page
size ( CONFIG_ARM64_64K_PAGES=y ) kernel.
while running LTP syscalls test suite on running 5.13.3 and 5.13.5-rc1 kernel.

First it was noticed on the stable-rc 5.13.3-rc2 kernel.

Whereas 64bit kernel and 32bit kernel pass with 4K page size.

Initially, I thought it could be a Hard drive fault but it is reproducible on
other devices but not always. Which is a blocker to bisect the problem.

The steps to reproduce:
 - Boot arm64 juno device with 64k page stable-rc 5.13 kernel Image [1]
   - CONFIG_ARM64_64K_PAGES=y
 - format connected SATA drives and mount /scratch
 - Use the mounted /scratch for LTP runs to create and delete files from this
 - cd /opt/ltp
 - ./runltp -d /scratch -f syscalls
And does that also fail for 5.13.2?

Re: [PATCH 5.13 000/156] 5.13.5-rc1 review

From: Naresh Kamboju <hidden>
Date: 2021-07-23 12:25:31

On Fri, 23 Jul 2021 at 17:33, Greg Kroah-Hartman
[off-list ref] wrote:
On Fri, Jul 23, 2021 at 05:26:22PM +0530, Naresh Kamboju wrote:
quoted
On Thu, 22 Jul 2021 at 22:17, Greg Kroah-Hartman
[off-list ref] wrote:
quoted
This is the start of the stable review cycle for the 5.13.5 release.
There are 156 patches in this series, all will be posted as a response
to this one.  If anyone has any issues with these being applied, please
let me know.

Responses should be made by Sat, 24 Jul 2021 15:56:00 +0000.
Anything received after that time might be too late.

The whole patch series can be found in one patch at:
        https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.13.5-rc1.gz
or in the git tree and branch at:
        git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.13.y
and the diffstat can be found below.

thanks,

greg k-h
The following error is due to SATA drive format failing with arm64 64k-page
size ( CONFIG_ARM64_64K_PAGES=y ) kernel.
while running LTP syscalls test suite on running 5.13.3 and 5.13.5-rc1 kernel.

First it was noticed on the stable-rc 5.13.3-rc2 kernel.

Whereas 64bit kernel and 32bit kernel pass with 4K page size.

Initially, I thought it could be a Hard drive fault but it is reproducible on
other devices but not always. Which is a blocker to bisect the problem.

The steps to reproduce:
 - Boot arm64 juno device with 64k page stable-rc 5.13 kernel Image [1]
   - CONFIG_ARM64_64K_PAGES=y
 - format connected SATA drives and mount /scratch
 - Use the mounted /scratch for LTP runs to create and delete files from this
 - cd /opt/ltp

3 more quoted lines

Yes. It failed on 5.13.2 also.

Ref failed log:
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.13.y/build/v5.13.2/testrun/5147287/suite/ltp-syscalls-tests/test/copy_file_range01/log

- Naresh

Re: [PATCH 5.13 000/156] 5.13.5-rc1 review

From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date: 2021-07-23 13:19:40

On Fri, Jul 23, 2021 at 05:55:15PM +0530, Naresh Kamboju wrote:
On Fri, 23 Jul 2021 at 17:33, Greg Kroah-Hartman
[off-list ref] wrote:
quoted
On Fri, Jul 23, 2021 at 05:26:22PM +0530, Naresh Kamboju wrote:
quoted
On Thu, 22 Jul 2021 at 22:17, Greg Kroah-Hartman
[off-list ref] wrote:
quoted
This is the start of the stable review cycle for the 5.13.5 release.
There are 156 patches in this series, all will be posted as a response
to this one.  If anyone has any issues with these being applied, please
let me know.

Responses should be made by Sat, 24 Jul 2021 15:56:00 +0000.
Anything received after that time might be too late.

The whole patch series can be found in one patch at:
        https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.13.5-rc1.gz
or in the git tree and branch at:
        git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.13.y
and the diffstat can be found below.

thanks,

greg k-h
The following error is due to SATA drive format failing with arm64 64k-page
size ( CONFIG_ARM64_64K_PAGES=y ) kernel.
while running LTP syscalls test suite on running 5.13.3 and 5.13.5-rc1 kernel.

First it was noticed on the stable-rc 5.13.3-rc2 kernel.

Whereas 64bit kernel and 32bit kernel pass with 4K page size.

Initially, I thought it could be a Hard drive fault but it is reproducible on
other devices but not always. Which is a blocker to bisect the problem.

The steps to reproduce:
 - Boot arm64 juno device with 64k page stable-rc 5.13 kernel Image [1]
   - CONFIG_ARM64_64K_PAGES=y
 - format connected SATA drives and mount /scratch

10 more quoted lines

Great, not a new problem?

5.13.0?

bisection would be most helpful.

thanks,

greg k-h
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help