This is the start of the stable review cycle for the 5.15.107 release.
There are 93 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 Fri, 14 Apr 2023 08:28:02 +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.15.107-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.15.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <[email protected]>
Linux 5.15.107-rc1
Alistair Popple <[email protected]>
mm: take a page reference when removing device exclusive entries
Robert Foss <[email protected]>
drm/bridge: lt9611: Fix PLL being unable to lock
Rongwei Wang <[email protected]>
mm/swap: fix swap_info_struct race between swapoff and get_swap_pages()
Zheng Yejian <[email protected]>
ring-buffer: Fix race while reader and writer are on the same page
Karol Herbst <[email protected]>
drm/nouveau/disp: Support more modes by checking with lower bpc
Boris Brezillon <[email protected]>
drm/panfrost: Fix the panfrost_mmu_map_fault_addr() error path
Yafang Shao <[email protected]>
mm: vmalloc: avoid warn_alloc noise caused by fatal signal
Jason Montleon <[email protected]>
ASoC: hdac_hdmi: use set_stream() instead of set_tdm_slots()
Steven Rostedt (Google) <[email protected]>
tracing: Free error logs of tracing instances
Michal Sojka <[email protected]>
can: isotp: isotp_ops: fix poll() to not report false EPOLLOUT events
Oleksij Rempel <[email protected]>
can: j1939: j1939_tp_tx_dat_new(): fix out-of-bounds memory access
Christian Brauner <[email protected]>
fs: drop peer group ids under namespace lock
Zheng Yejian <[email protected]>
ftrace: Fix issue that 'direct->addr' not restored in modify_ftrace_direct()
John Keeping <[email protected]>
ftrace: Mark get_lock_parent_ip() __always_inline
Kan Liang <[email protected]>
perf/core: Fix the same task check in perf_event_set_output
Thiago Rafael Becker <[email protected]>
cifs: sanitize paths in cifs_update_super_prepath.
Steve French <[email protected]>
smb3: lower default deferred close timeout to address perf regression
Steve French <[email protected]>
smb3: allow deferred close timeout to be configurable
Zhong Jinghua <[email protected]>
scsi: iscsi_tcp: Check that sock is valid before iscsi_set_param()
Li Zetao <[email protected]>
scsi: qla2xxx: Fix memory leak in qla2x00_probe_one()
Nuno Sá <[email protected]>
iio: adc: ad7791: fix IRQ flags
Steve Clevenger <[email protected]>
coresight-etm4: Fix for() loop drvdata->nr_addr_cmp range bug
Suzuki K Poulose <[email protected]>
coresight: etm4x: Do not access TRCIDR1 for identification
Jeremy Soller <[email protected]>
ALSA: hda/realtek: Add quirk for Clevo X370SNW
Marios Makassikis <[email protected]>
ksmbd: do not call kvmalloc() with __GFP_NORETRY | __GFP_NO_WARN
Geert Uytterhoeven <[email protected]>
dt-bindings: serial: renesas,scif: Fix 4th IRQ for 4-IRQ SCIFs
Ryusuke Konishi <[email protected]>
nilfs2: fix sysfs interface lifetime
Ryusuke Konishi <[email protected]>
nilfs2: fix potential UAF of struct nilfs_sc_info in nilfs_segctor_thread()
Sherry Sun <[email protected]>
tty: serial: fsl_lpuart: avoid checking for transfer complete when UARTCTRL_SBK is asserted in lpuart32_tx_empty
Biju Das <[email protected]>
tty: serial: sh-sci: Fix Rx on RZ/G2L SCI
Biju Das <[email protected]>
tty: serial: sh-sci: Fix transmit end interrupt handler
Kai-Heng Feng <[email protected]>
iio: light: cm32181: Unregister second I2C client if present
William Breathitt Gray <[email protected]>
iio: dac: cio-dac: Fix max DAC write value check for 12-bit
Lars-Peter Clausen <[email protected]>
iio: adc: ti-ads7950: Set `can_sleep` flag for GPIO chip
Arnd Bergmann <[email protected]>
iio: adis16480: select CONFIG_CRC32
Bjørn Mork <[email protected]>
USB: serial: option: add Quectel RM500U-CN modem
Enrico Sau <[email protected]>
USB: serial: option: add Telit FE990 compositions
RD Babiera <[email protected]>
usb: typec: altmodes/displayport: Fix configure initial pin assignment
Kees Jan Koster <[email protected]>
USB: serial: cp210x: add Silicon Labs IFS-USB-DATACABLE IDs
Heikki Krogerus <[email protected]>
usb: dwc3: pci: add support for the Intel Meteor Lake-S
Pawel Laszczak <[email protected]>
usb: cdnsp: Fixes error: uninitialized symbol 'len'
D Scott Phillips <[email protected]>
xhci: also avoid the XHCI_ZERO_64B_REGS quirk with a passthrough iommu
Wayne Chang <[email protected]>
usb: xhci: tegra: fix sleep in atomic call
Masahiro Yamada <[email protected]>
kbuild: refactor single builds of *.ko
Shailend Chand <[email protected]>
gve: Secure enough bytes in the first TX desc for all TCP pkts
Andy Roulin <[email protected]>
ethtool: reset #lanes when lanes is omitted
Lingyu Liu <[email protected]>
ice: Reset FDIR counter in FDIR init stage
Simei Su <[email protected]>
ice: fix wrong fallback logic for FDIR
Dai Ngo <[email protected]>
NFSD: callback request does not use correct credential for AUTH_SYS
Jeff Layton <[email protected]>
sunrpc: only free unix grouplist after RCU settles
Corinna Vinschen <[email protected]>
net: stmmac: fix up RX flow hash indirection table when setting channels
Siddharth Vadapalli <[email protected]>
net: ethernet: ti: am65-cpsw: Fix mdio cleanup in probe
Dhruva Gole <[email protected]>
gpio: davinci: Add irq chip flag to skip set wake
Mark Pearson <[email protected]>
platform/x86: think-lmi: Clean up display of current_value on Thinkstation
Mark Pearson <[email protected]>
platform/x86: think-lmi: Fix memory leaks when parsing ThinkStation WMI strings
Armin Wolf <[email protected]>
platform/x86: think-lmi: Fix memory leak when showing current settings
Ziyang Xuan <[email protected]>
ipv6: Fix an uninit variable access bug in __ip6_make_skb()
Sricharan Ramabadhran <[email protected]>
net: qrtr: Do not do DEL_SERVER broadcast after DEL_CLIENT
Xin Long <[email protected]>
sctp: check send stream number after wait_for_sndbuf
Gustav Ekelund <[email protected]>
net: dsa: mv88e6xxx: Reset mv88e6393x force WD event bit
Jakub Kicinski <[email protected]>
net: don't let netpoll invoke NAPI if in xmit context
Eric Dumazet <[email protected]>
icmp: guard against too small mtu
Chuck Lever <[email protected]>
NFSD: Avoid calling OPDESC() with ops->opnum == OP_ILLEGAL
Ziyang Xuan <[email protected]>
net: qrtr: Fix a refcount bug in qrtr_recvmsg()
Luca Weiss <[email protected]>
net: qrtr: combine nameservice into main module
Felix Fietkau <[email protected]>
wifi: mac80211: fix invalid drv_sta_pre_rcu_remove calls for non-uploaded sta
Nico Boehr <[email protected]>
KVM: s390: pv: fix external interruption loop not always detected
Uwe Kleine-König <[email protected]>
pwm: sprd: Explicitly set .polarity in .get_state()
Uwe Kleine-König <[email protected]>
pwm: cros-ec: Explicitly set .polarity in .get_state()
Mohammed Gamal <[email protected]>
Drivers: vmbus: Check for channel allocation before looking up relids
Randy Dunlap <[email protected]>
gpio: GPIO_REGMAP: select REGMAP instead of depending on it
Tonghao Zhang <[email protected]>
bpf: hash map, avoid deadlock with suitable hash mask
Christian König <[email protected]>
drm/amdgpu: fix amdgpu_job_free_resources v2
Andrey Grodzovsky <[email protected]>
drm/amdgpu: Prevent race between late signaled fences and GPU reset.
Matthew Howell <[email protected]>
serial: exar: Add support for Sealevel 7xxxC serial cards
Andy Shevchenko <[email protected]>
serial: 8250_exar: derive nr_ports from PCI ID for Acces I/O cards
Daniil Tatianin <[email protected]>
iavf/iavf_main: actually log ->src mask when talking about it
Jacob Keller <[email protected]>
iavf: return errno code instead of status code
Hans de Goede <[email protected]>
platform/x86: int3472/discrete: Ensure the clk/power enable pins are in output mode
Hans de Goede <[email protected]>
platform/x86: int3472: Split into 2 drivers
Mustafa Ismail <[email protected]>
RDMA/irdma: Do not request 2-level PBLEs for CQ alloc
Brian Foster <[email protected]>
NFSD: pass range end to vfs_fsync_range() instead of count
Chuck Lever <[email protected]>
NFSD: Fix sparse warning
Li Zetao <[email protected]>
ocfs2: fix memory leak in ocfs2_mount_volume()
Heming Zhao via Ocfs2-devel <[email protected]>
ocfs2: rewrite error handling of ocfs2_fill_super
Heming Zhao via Ocfs2-devel <[email protected]>
ocfs2: ocfs2_mount_volume does cleanup job before return error
Yang Yingliang <[email protected]>
soc: sifive: ccache: fix missing of_node_put() in sifive_ccache_init()
Yang Yingliang <[email protected]>
soc: sifive: ccache: fix missing free_irq() in error path in sifive_ccache_init()
Yang Yingliang <[email protected]>
soc: sifive: ccache: fix missing iounmap() in error path in sifive_ccache_init()
Ben Dooks <[email protected]>
soc: sifive: ccache: use pr_fmt() to remove CCACHE: prefixes
Ben Dooks <[email protected]>
soc: sifive: ccache: reduce printing on init
Zong Li <[email protected]>
soc: sifive: ccache: determine the cache level from dts
Greentime Hu <[email protected]>
soc: sifive: ccache: Rename SiFive L2 cache to Composable cache.
-------------
Diffstat:
.../devicetree/bindings/serial/renesas,scif.yaml | 4 +-
Makefile | 20 +-
arch/s390/kvm/intercept.c | 32 ++-
drivers/edac/Kconfig | 2 +-
drivers/edac/sifive_edac.c | 12 +-
drivers/gpio/Kconfig | 2 +-
drivers/gpio/gpio-davinci.c | 2 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 4 +
drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c | 18 ++
drivers/gpu/drm/amd/amdgpu/amdgpu_job.c | 10 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_ring.h | 1 +
drivers/gpu/drm/bridge/lontium-lt9611.c | 1 +
drivers/gpu/drm/nouveau/dispnv50/disp.c | 32 +++
drivers/gpu/drm/nouveau/nouveau_dp.c | 8 +-
drivers/gpu/drm/panfrost/panfrost_mmu.c | 1 +
drivers/hv/connection.c | 4 +
drivers/hwtracing/coresight/coresight-etm4x-core.c | 24 +-
drivers/hwtracing/coresight/coresight-etm4x.h | 20 +-
drivers/iio/adc/ad7791.c | 2 +-
drivers/iio/adc/ti-ads7950.c | 1 +
drivers/iio/dac/cio-dac.c | 4 +-
drivers/iio/imu/Kconfig | 1 +
drivers/iio/light/cm32181.c | 12 +
drivers/infiniband/hw/irdma/verbs.c | 15 +-
drivers/net/dsa/mv88e6xxx/chip.c | 2 +-
drivers/net/dsa/mv88e6xxx/global2.c | 20 ++
drivers/net/dsa/mv88e6xxx/global2.h | 1 +
drivers/net/ethernet/google/gve/gve.h | 2 +
drivers/net/ethernet/google/gve/gve_tx.c | 12 +-
drivers/net/ethernet/intel/iavf/iavf_main.c | 22 +-
drivers/net/ethernet/intel/ice/ice_virtchnl_fdir.c | 23 +-
drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 6 +-
drivers/net/ethernet/ti/am65-cpsw-nuss.c | 6 +-
drivers/platform/x86/intel/int3472/Makefile | 9 +-
...472_clk_and_regulator.c => clk_and_regulator.c} | 5 +-
drivers/platform/x86/intel/int3472/common.c | 54 +++++
.../{intel_skl_int3472_common.h => common.h} | 3 -
.../{intel_skl_int3472_discrete.c => discrete.c} | 32 ++-
.../x86/intel/int3472/intel_skl_int3472_common.c | 106 --------
.../{intel_skl_int3472_tps68470.c => tps68470.c} | 23 +-
drivers/platform/x86/think-lmi.c | 20 +-
drivers/pwm/pwm-cros-ec.c | 1 +
drivers/pwm/pwm-sprd.c | 1 +
drivers/scsi/iscsi_tcp.c | 3 +-
drivers/scsi/qla2xxx/qla_os.c | 1 +
drivers/soc/sifive/Kconfig | 6 +-
drivers/soc/sifive/Makefile | 2 +-
drivers/soc/sifive/sifive_ccache.c | 266 +++++++++++++++++++++
drivers/soc/sifive/sifive_l2_cache.c | 237 ------------------
drivers/tty/serial/8250/8250_exar.c | 51 ++--
drivers/tty/serial/fsl_lpuart.c | 8 +-
drivers/tty/serial/sh-sci.c | 10 +-
drivers/usb/cdns3/cdnsp-ep0.c | 3 +-
drivers/usb/dwc3/dwc3-pci.c | 4 +
drivers/usb/host/xhci-tegra.c | 6 +-
drivers/usb/host/xhci.c | 6 +-
drivers/usb/serial/cp210x.c | 1 +
drivers/usb/serial/option.c | 10 +
drivers/usb/typec/altmodes/displayport.c | 6 +-
fs/cifs/cifsfs.c | 1 +
fs/cifs/connect.c | 2 +
fs/cifs/file.c | 4 +-
fs/cifs/fs_context.c | 22 +-
fs/cifs/fs_context.h | 11 +
fs/cifs/misc.c | 2 +-
fs/ksmbd/connection.c | 5 +-
fs/namespace.c | 2 +-
fs/nfsd/nfs4callback.c | 4 +-
fs/nfsd/nfs4proc.c | 7 +-
fs/nfsd/nfs4xdr.c | 4 +-
fs/nilfs2/segment.c | 3 +-
fs/nilfs2/super.c | 2 +
fs/nilfs2/the_nilfs.c | 12 +-
fs/ocfs2/journal.c | 2 +-
fs/ocfs2/journal.h | 1 +
fs/ocfs2/super.c | 105 ++++----
include/linux/ftrace.h | 2 +-
include/soc/sifive/sifive_ccache.h | 16 ++
include/soc/sifive/sifive_l2_cache.h | 16 --
kernel/bpf/hashtab.c | 4 +-
kernel/events/core.c | 2 +-
kernel/trace/ftrace.c | 15 +-
kernel/trace/ring_buffer.c | 13 +-
kernel/trace/trace.c | 1 +
mm/memory.c | 16 +-
mm/swapfile.c | 3 +-
mm/vmalloc.c | 8 +-
net/can/isotp.c | 17 +-
net/can/j1939/transport.c | 5 +-
net/core/netpoll.c | 19 +-
net/ethtool/linkmodes.c | 7 +-
net/ipv4/icmp.c | 5 +
net/ipv6/ip6_output.c | 7 +-
net/mac80211/sta_info.c | 3 +-
net/qrtr/Makefile | 3 +-
net/qrtr/{qrtr.c => af_qrtr.c} | 2 +
net/qrtr/ns.c | 15 +-
net/sctp/socket.c | 4 +
net/sunrpc/svcauth_unix.c | 17 +-
sound/pci/hda/patch_realtek.c | 1 +
sound/soc/codecs/hdac_hdmi.c | 17 +-
101 files changed, 968 insertions(+), 639 deletions(-)
On 4/12/23 01:33, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.15.107 release.
> There are 93 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 Fri, 14 Apr 2023 08:28:02 +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.15.107-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.15.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
On ARCH_BRCMSTB using 32-bit and 64-bit ARM kernels, build tested on
BMIPS_GENERIC:
Tested-by: Florian Fainelli <[email protected]>
--
Florian
On 4/12/23 02:33, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.15.107 release.
> There are 93 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 Fri, 14 Apr 2023 08:28:02 +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.15.107-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.15.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>
Compiled and booted on my test system. No dmesg regressions.
Tested-by: Shuah Khan <[email protected]>
thanks,
-- Shuah
On Wed, Apr 12, 2023 at 10:33:01AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.15.107 release.
> There are 93 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 Fri, 14 Apr 2023 08:28:02 +0000.
> Anything received after that time might be too late.
>
Build results:
total: 160 pass: 160 fail: 0
Qemu test results:
total: 499 pass: 499 fail: 0
Tested-by: Guenter Roeck <[email protected]>
Guenter
Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.15.107 release.
> There are 93 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 Fri, 14 Apr 2023 08:28:02 +0000.
> Anything received after that time might be too late.
>
I think I'm seeing a regression here in the amdgpu driver, though not
being a kernel dev I could be wrong.
I built and booted this today on an x86_64 machine (AMD Ryzen 7 3700X,
Gigabyte X570 UD motherboard) with 3 x AMD graphics cards (using names
from lspci output):
- Cape Verde GL [FirePro W4100]
- Oland XT [Radeon HD 8670 / R5 340X OEM / R7 250/350/350X OEM] (rev 83)
- Bonaire [Radeon R7 200 Series]
All three using the amdgpu driver (radeon module blacklisted).
This machine has been running vanilla 5.15 stable releases for a good
while, with the kernel updated with whatever the latest 5.15 release is
every 6 weeks or so. Never had any amdgpu problems.
To build 5.15.107-rc1 I applied the contents of the queue-5.15 directory
on top of 5.15.106, having synced the stable queue git repo up until
commit 344d8ad1b5dde387d1ce4d1be2641753b89dd10d (still the latest commit
as a type). This is what I have done for years running vanilla stable
kernels.
There was nothing out of the ordinary in the build output, but on
rebooting into 5.15.107-rc1 I had the following error in dmesg from 1
card only:
amdgpu 0000:0d:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test
failed on vce0 (-110).
[drm:process_one_work] *ERROR* ib ring test failed (-110).
This was during bootup immediately after driver loading. X is not
running. 0000:0d:00.0 is the Bonaire card.
I then shutdown and fully powered off for a few minutes, booted
5.15.107-rc1 again, but the error on that card persisted exactly the same.
This was a regression for me as I've never had that error before on any
kernel release (I grepped through old kernel logs to check).
I then rebuilt 5.15.107-rc1 but without applying the following 4 patches:
drm-panfrost-fix-the-panfrost_mmu_map_fault_addr-error-path.patch
drm-amdgpu-fix-amdgpu_job_free_resources-v2.patch
drm-amdgpu-prevent-race-between-late-signaled-fences.patch
drm-bridge-lt9611-fix-pll-being-unable-to-lock.patch
On booting into the newly built kernel there was no error anymore,
amdgpu dmesg output was as normal, and the machine is running fine now
on that.
So I'm quite confident one of those patches introduced the error for me.
Having now looked at the contents of them I see the lt9611 is entirely
different hardware and I'm guessing the panfrost one probably is as
well, so most likely I didn't need to remove those 2.
This is not a great report and maybe not helpful (sorry) as
unfortunately I cannot try and narrow it down further to a single patch
as this machine has to stay running now for a while. I just crudely
tried yanking those 4 to hopefully get rid of the error and get the
machine running again. Also I didn't go on to test whether the card
actually worked as expected, maybe the error is harmless after all,
though it doesn't look insignificant.
As the error was only output for the Bonaire card (the other two were
fine), below is lspci -vvv output for that card only in case it helps.
If anyone would like further info just let me know.
Eddie
0d:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Bonaire [Radeon R7 200 Series] (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] Bonaire
[Radeon R7 200 Series]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 135
IOMMU group: 29
Region 0: Memory at 880000000 (64-bit, prefetchable) [size=1G]
Region 2: Memory at 860000000 (64-bit, prefetchable) [size=8M]
Region 4: I/O ports at f000 [size=256]
Region 5: Memory at fce00000 (32-bit, non-prefetchable) [size=256K]
Expansion ROM at fce40000 [disabled] [size=128K]
Capabilities: [48] Vendor Specific Information: Len=08 <?>
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Legacy Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s
<4us, L1 unlimited
ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 256 bytes, MaxReadReq 512 bytes
DevSta: CorrErr+ NonFatalErr- FatalErr- UnsupReq+
AuxPwr- TransPend-
LnkCap: Port #0, Speed 8GT/s, Width x16, ASPM L0s L1,
Exit Latency L0s <64ns, L1 <1us
ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+
LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 8GT/s, Width x16
TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-
NROPrPrP- LTR-
10BitTagComp- 10BitTagReq- OBFF Not Supported,
ExtFmt+ EETLPPrefix+, MaxEETLPPrefixes 1
EmergencyPowerReduction Not Supported,
EmergencyPowerReductionInit-
FRS-
AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-
LTR- 10BitTagReq- OBFF Disabled,
AtomicOpsCtl: ReqEn-
LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink-
Retimer- 2Retimers- DRS-
LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance-
SpeedDis-
Transmit Margin: Normal Operating Range,
EnterModifiedCompliance- ComplianceSOS-
Compliance Preset/De-emphasis: -6dB
de-emphasis, 0dB preshoot
LnkSta2: Current De-emphasis Level: -3.5dB,
EqualizationComplete+ EqualizationPhase1+
EqualizationPhase2+ EqualizationPhase3+
LinkEqualizationRequest-
Retimer- 2Retimers- CrosslinkRes: unsupported
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: 00000000fee00000 Data: 0000
Capabilities: [100 v1] Vendor Specific Information: ID=0001
Rev=1 Len=010 <?>
Capabilities: [150 v2] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt-
UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt-
UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt-
UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout-
AdvNonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout-
AdvNonFatalErr+
AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn-
ECRCChkCap+ ECRCChkEn-
MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
HeaderLog: 00000000 00000000 00000000 00000000
Capabilities: [200 v1] Physical Resizable BAR
BAR 0: current size: 1GB, supported: 256MB 512MB 1GB
Capabilities: [270 v1] Secondary PCI Express
LnkCtl3: LnkEquIntrruptEn- PerformEqu-
LaneErrStat: 0
Capabilities: [2b0 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable+, Smallest Translation Unit: 00
Capabilities: [2c0 v1] Page Request Interface (PRI)
PRICtl: Enable- Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 00000020, Page Request
Allocation: 00000000
Capabilities: [2d0 v1] Process Address Space ID (PASID)
PASIDCap: Exec+ Priv+, Max PASID Width: 10
PASIDCtl: Enable- Exec- Priv-
Kernel driver in use: amdgpu
Kernel modules: radeon, amdgpu
On Wed, Apr 12, 2023 at 10:33:01AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.15.107 release.
> There are 93 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.
>
Successfully cross-compiled for arm64 (bcm2711_defconfig, GCC 10.2.0) and
powerpc (ps3_defconfig, GCC 12.2.0).
Tested-by: Bagas Sanjaya <[email protected]>
--
An old man doll... just what I always wanted! - Clara
On 4/12/23 1:33 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.15.107 release.
> There are 93 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 Fri, 14 Apr 2023 08:28:02 +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.15.107-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.15.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
Built and booted successfully on RISC-V RV64 (HiFive Unmatched).
Note: This was built with a .config change from CONFIG_SIFIVE_L2 to
CONFIG_SIFIVE_CCACHE.
Tested-by: Ron Economos <[email protected]>
On Wed, 12 Apr 2023 at 14:06, Greg Kroah-Hartman
<[email protected]> wrote:
>
> This is the start of the stable review cycle for the 5.15.107 release.
> There are 93 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 Fri, 14 Apr 2023 08:28:02 +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.15.107-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.15.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
Results from Linaro’s test farm.
No regressions on arm64, arm, x86_64, and i386.
Tested-by: Linux Kernel Functional Testing <[email protected]>
## Build
* kernel: 5.15.107-rc1
* git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc
* git branch: linux-5.15.y
* git commit: 415a9d81c640534731472ca364ec9cb77008a8e0
* git describe: v5.15.105-194-g415a9d81c640
* test details:
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.15.y/build/v5.15.105-194-g415a9d81c640
## Test Regressions (compared to v5.15.105)
## Metric Regressions (compared to v5.15.105)
## Test Fixes (compared to v5.15.105)
## Metric Fixes (compared to v5.15.105)
## Test result summary
total: 126997, pass: 105591, fail: 3746, skip: 17417, xfail: 243
## Build Summary
* arc: 5 total, 5 passed, 0 failed
* arm: 115 total, 114 passed, 1 failed
* arm64: 43 total, 41 passed, 2 failed
* i386: 33 total, 30 passed, 3 failed
* mips: 27 total, 26 passed, 1 failed
* parisc: 8 total, 8 passed, 0 failed
* powerpc: 27 total, 26 passed, 1 failed
* riscv: 11 total, 11 passed, 0 failed
* s390: 12 total, 11 passed, 1 failed
* sh: 14 total, 12 passed, 2 failed
* sparc: 8 total, 8 passed, 0 failed
* x86_64: 36 total, 34 passed, 2 failed
## Test suites summary
* boot
* fwts
* igt-gpu-tools
* kselftest-android
* kselftest-arm64
* kselftest-breakpoints
* kselftest-capabilities
* kselftest-cgroup
* kselftest-clone3
* kselftest-core
* kselftest-cpu-hotplug
* kselftest-cpufreq
* kselftest-drivers-dma-buf
* kselftest-efivarfs
* kselftest-filesystems
* kselftest-filesystems-binderfs
* kselftest-firmware
* kselftest-fpu
* kselftest-ftrace
* kselftest-futex
* kselftest-gpio
* kselftest-intel_pstate
* kselftest-ipc
* kselftest-ir
* kselftest-kcmp
* kselftest-kexec
* kselftest-kvm
* kselftest-lib
* kselftest-livepatch
* kselftest-membarrier
* kselftest-memfd
* kselftest-memory-hotplug
* kselftest-mincore
* kselftest-mount
* kselftest-mqueue
* kselftest-net
* kselftest-net-forwarding
* kselftest-net-mptcp
* kselftest-netfilter
* kselftest-nsfs
* kselftest-openat2
* kselftest-pid_namespace
* kselftest-pidfd
* kselftest-proc
* kselftest-pstore
* kselftest-ptrace
* kselftest-rseq
* kselftest-rtc
* kselftest-seccomp
* kselftest-sigaltstack
* kselftest-size
* kselftest-splice
* kselftest-static_keys
* kselftest-sync
* kselftest-sysctl
* kselftest-tc-testing
* kselftest-timens
* kselftest-timers
* kselftest-tmpfs
* kselftest-tpm2
* kselftest-user
* kselftest-vm
* kselftest-x86
* kselftest-zram
* kunit
* kvm-unit-tests
* libhugetlbfs
* log-parser-boot
* log-parser-test
* ltp-cap_bounds
* ltp-commands
* ltp-containers
* ltp-controllers
* ltp-cpuhotplug
* ltp-crypto
* ltp-cve
* ltp-dio
* ltp-fcntl-locktests
* ltp-filecaps
* ltp-fs
* ltp-fs_bind
* ltp-fs_perms_simple
* ltp-fsx
* ltp-hugetlb
* ltp-io
* ltp-ipc
* ltp-math
* ltp-mm
* ltp-nptl
* ltp-pty
* ltp-sched
* ltp-securebits
* ltp-smoke
* ltp-syscalls
* ltp-tracing
* network-basic-tests
* perf
* rcutorture
* v4l2-compliance
* vdso
--
Linaro LKFT
https://lkft.linaro.org
On Wed, Apr 12, 2023 at 10:47:13PM +0100, Eddie Chapman wrote:
> Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.15.107 release.
> > There are 93 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 Fri, 14 Apr 2023 08:28:02 +0000.
> > Anything received after that time might be too late.
> >
>
> I think I'm seeing a regression here in the amdgpu driver, though not being
> a kernel dev I could be wrong.
>
> I built and booted this today on an x86_64 machine (AMD Ryzen 7 3700X,
> Gigabyte X570 UD motherboard) with 3 x AMD graphics cards (using names from
> lspci output):
> - Cape Verde GL [FirePro W4100]
> - Oland XT [Radeon HD 8670 / R5 340X OEM / R7 250/350/350X OEM] (rev 83)
> - Bonaire [Radeon R7 200 Series]
>
> All three using the amdgpu driver (radeon module blacklisted).
>
> This machine has been running vanilla 5.15 stable releases for a good while,
> with the kernel updated with whatever the latest 5.15 release is every 6
> weeks or so. Never had any amdgpu problems.
>
> To build 5.15.107-rc1 I applied the contents of the queue-5.15 directory on
> top of 5.15.106, having synced the stable queue git repo up until commit
> 344d8ad1b5dde387d1ce4d1be2641753b89dd10d (still the latest commit as a
> type). This is what I have done for years running vanilla stable kernels.
>
> There was nothing out of the ordinary in the build output, but on rebooting
> into 5.15.107-rc1 I had the following error in dmesg from 1 card only:
>
> amdgpu 0000:0d:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test
> failed on vce0 (-110).
> [drm:process_one_work] *ERROR* ib ring test failed (-110).
>
> This was during bootup immediately after driver loading. X is not running.
> 0000:0d:00.0 is the Bonaire card.
>
> I then shutdown and fully powered off for a few minutes, booted 5.15.107-rc1
> again, but the error on that card persisted exactly the same.
>
> This was a regression for me as I've never had that error before on any
> kernel release (I grepped through old kernel logs to check).
>
> I then rebuilt 5.15.107-rc1 but without applying the following 4 patches:
>
> drm-panfrost-fix-the-panfrost_mmu_map_fault_addr-error-path.patch
> drm-amdgpu-fix-amdgpu_job_free_resources-v2.patch
> drm-amdgpu-prevent-race-between-late-signaled-fences.patch
> drm-bridge-lt9611-fix-pll-being-unable-to-lock.patch
>
> On booting into the newly built kernel there was no error anymore, amdgpu
> dmesg output was as normal, and the machine is running fine now on that.
>
> So I'm quite confident one of those patches introduced the error for me.
> Having now looked at the contents of them I see the lt9611 is entirely
> different hardware and I'm guessing the panfrost one probably is as well, so
> most likely I didn't need to remove those 2.
>
> This is not a great report and maybe not helpful (sorry) as unfortunately I
> cannot try and narrow it down further to a single patch as this machine has
> to stay running now for a while. I just crudely tried yanking those 4 to
> hopefully get rid of the error and get the machine running again. Also I
> didn't go on to test whether the card actually worked as expected, maybe the
> error is harmless after all, though it doesn't look insignificant.
>
> As the error was only output for the Bonaire card (the other two were fine),
> below is lspci -vvv output for that card only in case it helps. If anyone
> would like further info just let me know.
Ok, I've dropped the two drm-amdgpu-* patches from the tree for now.
Let me know if the release works properly for you or not.
thanks for testing and letting us know!
greg k-h
Hi Greg,
On 12/04/23 2:03 pm, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.15.107 release.
> There are 93 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.
>
No problems seen on x86_64 and aarch64.
Tested-by: Harshit Mogalapalli <[email protected]>
Thanks,
Harshit
On 13/04/2023 15:46, Greg Kroah-Hartman wrote:
> On Wed, Apr 12, 2023 at 10:47:13PM +0100, Eddie Chapman wrote:
>> Greg Kroah-Hartman wrote:
>>> This is the start of the stable review cycle for the 5.15.107 release.
>>> There are 93 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 Fri, 14 Apr 2023 08:28:02 +0000.
>>> Anything received after that time might be too late.
>>>
>>
>> I think I'm seeing a regression here in the amdgpu driver, though not being
>> a kernel dev I could be wrong.
>>
>> I built and booted this today on an x86_64 machine (AMD Ryzen 7 3700X,
>> Gigabyte X570 UD motherboard) with 3 x AMD graphics cards (using names from
>> lspci output):
>> - Cape Verde GL [FirePro W4100]
>> - Oland XT [Radeon HD 8670 / R5 340X OEM / R7 250/350/350X OEM] (rev 83)
>> - Bonaire [Radeon R7 200 Series]
>>
>> All three using the amdgpu driver (radeon module blacklisted).
>>
>> This machine has been running vanilla 5.15 stable releases for a good while,
>> with the kernel updated with whatever the latest 5.15 release is every 6
>> weeks or so. Never had any amdgpu problems.
>>
>> To build 5.15.107-rc1 I applied the contents of the queue-5.15 directory on
>> top of 5.15.106, having synced the stable queue git repo up until commit
>> 344d8ad1b5dde387d1ce4d1be2641753b89dd10d (still the latest commit as a
>> type). This is what I have done for years running vanilla stable kernels.
>>
>> There was nothing out of the ordinary in the build output, but on rebooting
>> into 5.15.107-rc1 I had the following error in dmesg from 1 card only:
>>
>> amdgpu 0000:0d:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test
>> failed on vce0 (-110).
>> [drm:process_one_work] *ERROR* ib ring test failed (-110).
>>
>> This was during bootup immediately after driver loading. X is not running.
>> 0000:0d:00.0 is the Bonaire card.
>>
>> I then shutdown and fully powered off for a few minutes, booted 5.15.107-rc1
>> again, but the error on that card persisted exactly the same.
>>
>> This was a regression for me as I've never had that error before on any
>> kernel release (I grepped through old kernel logs to check).
>>
>> I then rebuilt 5.15.107-rc1 but without applying the following 4 patches:
>>
>> drm-panfrost-fix-the-panfrost_mmu_map_fault_addr-error-path.patch
>> drm-amdgpu-fix-amdgpu_job_free_resources-v2.patch
>> drm-amdgpu-prevent-race-between-late-signaled-fences.patch
>> drm-bridge-lt9611-fix-pll-being-unable-to-lock.patch
>>
>> On booting into the newly built kernel there was no error anymore, amdgpu
>> dmesg output was as normal, and the machine is running fine now on that.
>>
>> So I'm quite confident one of those patches introduced the error for me.
>> Having now looked at the contents of them I see the lt9611 is entirely
>> different hardware and I'm guessing the panfrost one probably is as well, so
>> most likely I didn't need to remove those 2.
>>
>> This is not a great report and maybe not helpful (sorry) as unfortunately I
>> cannot try and narrow it down further to a single patch as this machine has
>> to stay running now for a while. I just crudely tried yanking those 4 to
>> hopefully get rid of the error and get the machine running again. Also I
>> didn't go on to test whether the card actually worked as expected, maybe the
>> error is harmless after all, though it doesn't look insignificant.
>>
>> As the error was only output for the Bonaire card (the other two were fine),
>> below is lspci -vvv output for that card only in case it helps. If anyone
>> would like further info just let me know.
>
> Ok, I've dropped the two drm-amdgpu-* patches from the tree for now.
> Let me know if the release works properly for you or not.
>
> thanks for testing and letting us know!
>
> greg k-h
Hello Greg,
My apologies just realised I never got back to you, as requested, to
confirm that, yes, that final release of 5.15.107 as well as other
5.15.x releases I've tried since then (including 5.15.115) have booted
up fine, without any unexpected errors, with these 3 AMD cards all using
the amdgpu driver, each with monitors connected.
Eddie