On Wed, Jul 15, 2020 at 09:36:44AM -0400, Veronika Kabatova wrote: > > > ----- Original Message ----- > > From: "CKI Project" <cki-project@xxxxxxxxxx> > > To: "Linux Stable maillist" <stable@xxxxxxxxxxxxxxx> > > Cc: "Xiong Zhou" <xzhou@xxxxxxxxxx> > > Sent: Wednesday, July 15, 2020 3:33:45 PM > > Subject: 💥 PANICKED: Test report for kernel 5.7.9-rc1-c2fb28a.cki (stable) > > > > > > Hello, > > > > We ran automated tests on a recent commit from this kernel tree: > > > > Kernel repo: > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > > Commit: c2fb28a4b6e4 - Linux 5.7.9-rc1 > > > > The results of these automated tests are provided below. > > > > Overall result: FAILED (see details below) > > Merge: OK > > Compile: OK > > Tests: PANICKED > > > > All kernel binaries, config files, and logs are available for download here: > > > > https://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawarehouse/2020/07/14/610210 > > > > One or more kernel tests failed: > > > > s390x: > > ❌ Boot test > > ❌ Boot test > > 💥 Boot test > > > > Hi, > > we started observing boot panics with 5.7 on s390x yesterday: > > [ 0.388965] Kernel panic - not syncing: Corrupted kernel text > [ 0.388970] CPU: 0 PID: 5 Comm: kworker/0:0 Not tainted 5.7.8-0930ce5.cki #1 > [ 0.388971] Hardware name: IBM 2964 N96 400 (z/VM 6.4.0) > [ 0.388975] Workqueue: events timer_update_keys > [ 0.388977] Call Trace: > [ 0.388980] [<00000001378c868a>] show_stack+0x8a/0xd0 > [ 0.388983] [<0000000137e0c9c2>] dump_stack+0x8a/0xb8 > [ 0.388985] [<00000001378fa372>] panic+0x112/0x308 > [ 0.388989] [<00000001378d20b6>] jump_label_bug+0x7e/0x80 > [ 0.388990] [<00000001378d1fb8>] __jump_label_transform+0xa8/0xd8 > [ 0.388992] [<00000001378d200e>] arch_jump_label_transform+0x26/0x40 > [ 0.388995] [<0000000137a8d448>] __jump_label_update+0xb8/0x128 > [ 0.388996] [<0000000137a8dca6>] static_key_enable_cpuslocked+0x8e/0xd0 > [ 0.388998] [<0000000137a8dd18>] static_key_enable+0x30/0x40 > [ 0.389000] [<000000013798a0d2>] timer_update_keys+0x3a/0x50 > [ 0.389003] [<000000013791cdde>] process_one_work+0x206/0x458 > [ 0.389005] [<000000013791d078>] worker_thread+0x48/0x460 > [ 0.389007] [<0000000137924912>] kthread+0x12a/0x160 > [ 0.389013] [<00000001381b9a70>] ret_from_fork+0x2c/0x30 > > I only released one of the reports to not spam too much but the panics are > still happening with the most recent code. > > These panics are NOT present on the current mainline. All other arches are OK. > > Given the call trace, I'm guessing it is something related to > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?h=linux-5.7.y&id=477d4930b0c7e70c1ac3e3c35e5ad15c5ebde8be Can you bisect to see if that really is the issue or not? thanks, greg k-h
