From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id C3DC43858C55; Sun,  3 Mar 2024 11:01:12 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C3DC43858C55
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1709463672;
	bh=rtQ29buhDxa8Drovc1QMLvToXLy7p9GIU4rp4gFVbsY=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=UGHUrh94CAHdAtU5Au2mXlvkyzwsh2xGiT7Vmv8+q2mOBIlqEFiMndF0qzddhMrbp
	 dWqSA5H5mf7vqAKhHoryo9MeI7KcyDM2+wdAKtOHvRCQ+ZeDkUIKpwJhTp+Wsjkt29
	 nTuAiwCxWySm0NJCYoFa7eU9et4jdvfP7dOyJDr8=
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/31442] [gdb/tdep, arm, SIGILL] FAIL:
 gdb.threads/sigstep-threads.exp: step 92
Date: Sun, 03 Mar 2024 11:01:11 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: tdep
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-31442-4717-x2ToTmVdDQ@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-31442-4717@http.sourceware.org/bugzilla/>
References: <bug-31442-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gdb-prs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D31442

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
This could be related to kernel commits:
...
commit 5f41f9198f296091c6a58bc2e86af1e9f019b2a3
Author: Marek Szyprowski <m.szyprowski@samsung.com>
Date:   Tue May 28 09:38:14 2019 +0100

    ARM: 8864/1: Add workaround for I-Cache line size mismatch between CPU
cores
...
and:
...
commit 116c81f427ff6c5380850963e3fb8798cc821d2b
Author: Suzuki K Poulose <suzuki.poulose@arm.com>
Date:   Fri Sep 9 14:07:16 2016 +0100

    arm64: Work around systems with mismatched cache line sizes
...

I'm using 32-bit arm user land on 64-bit kernel on aarch64, so I'm not sure
which commit would apply.  The arm commit first appears in v5.3, the arm64 =
one
in v4.9.

The kernel used is 4.4.190.

This is because the pinebook came with
https://github.com/mrfixit2001/debian_desktop , and the update script never
work for me, so I hacked the user land to be plain debian, but I got stuck =
with
the kernel from this (
https://github.com/mrfixit2001/debian_desktop/releases/tag/190905 ) release.

So, it could be that I don't have the necessary fix for this, I'm not sure =
how
to check.

I confirmed that this is a big.little issue, I ran with taskset -c 0-3 and
taskset -c 4-5 and the issue no longer reproduces.

I looked into upgrading the kernel to 6.1, but it seems that this is diffic=
ult
because /boot is read-only due to being flash, so I'm avoiding that for now.

I'm going to work around this by running tests using taskset -c 4-5,
restricting testing to the 2 big cores.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=