Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: Florian Bezdeka <florian.bezdeka@siemens.com>
Cc: Chris Paterson <Chris.Paterson2@renesas.com>,
	Pavel Machek <pavel@denx.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"patches@lists.linux.dev" <patches@lists.linux.dev>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"linux@roeck-us.net" <linux@roeck-us.net>,
	"shuah@kernel.org" <shuah@kernel.org>,
	"patches@kernelci.org" <patches@kernelci.org>,
	"lkft-triage@lists.linaro.org" <lkft-triage@lists.linaro.org>,
	"jonathanh@nvidia.com" <jonathanh@nvidia.com>,
	"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
	"sudipm.mukherjee@gmail.com" <sudipm.mukherjee@gmail.com>,
	"srw@sladewatkins.net" <srw@sladewatkins.net>,
	"rwarsow@gmx.de" <rwarsow@gmx.de>,
	"conor@kernel.org" <conor@kernel.org>,
	"allen.lkml@gmail.com" <allen.lkml@gmail.com>,
	"broonie@kernel.org" <broonie@kernel.org>,
	Quirin Gylstorff <quirin.gylstorff@siemens.com>
Subject: Re: [PATCH 6.10 00/25] 6.10.6-rc3 review
Date: Tue, 20 Aug 2024 11:49:13 +0200	[thread overview]
Message-ID: <ZsRmmQOLiZ1KtQ1T@duo.ucw.cz> (raw)
In-Reply-To: <0e62552b7b9c1cd1eca6aa1af64006c53230c4f0.camel@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 4079 bytes --]

Hi!

> > So we could blame it on the qemu-cip-siemens-muc machine, however, it was quite happily booting 6.10.6-rc1 a few days ago:
> > https://lava.ciplatform.org/scheduler/job/1180857
> > 6.10.6-rc2 was also okay:
> > https://lava.ciplatform.org/scheduler/job/1181017
> 
> As Chris pointed out that this might be related to our qemu instance in
> the CIP lab. We had a look and found the attached kernel splat. This
> seems not a guest but a host problem (which is Debian/6.1 based and not
> 6.10).

Aha, thanks a lot, things make sense now.

> I think you can continue, ignore the test result for this 6.10 release
> for now. 
> 
> We will investigate further. Let's see.
> 
> For completeness the kernel log of the host is attached. LAVA runs into
> a timeout and marks the job as failed.

Thanks for the log. It seems something is seriously wrong with the
machine, likely deadlock in ext4 or storage subsystems. If there are
any suspect messages before this one, they may be useful.

Best regards,
								Pavel

> [1639290.742208] INFO: task lava-run [job: :70173 blocked for more than 120 seconds.
> [1639290.742223]       Not tainted 6.1.0-22-amd64 #1 Debian 6.1.94-1
> [1639290.742231] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> [1639290.742241] task:lava-run [job:  state:D stack:0     pid:70173 ppid:2131   flags:0x00000002
> [1639290.742244] Call Trace:
> [1639290.742245]  <TASK>
> [1639290.742247]  __schedule+0x34d/0x9e0
> [1639290.742253]  schedule+0x5a/0xd0
> [1639290.742255]  wb_wait_for_completion+0x82/0xb0
> [1639290.742258]  ? cpuusage_read+0x10/0x10
> [1639290.742261]  __writeback_inodes_sb_nr+0xa0/0xd0
> [1639290.742263]  try_to_writeback_inodes_sb+0x55/0x70
> [1639290.742266]  ext4_nonda_switch+0x80/0x90 [ext4]
> [1639290.742289]  ext4_da_write_begin+0x61/0x2c0 [ext4]
> [1639290.742306]  ? __file_remove_privs+0xbb/0x150
> [1639290.742309]  generic_perform_write+0xcd/0x210
> [1639290.742313]  ext4_buffered_write_iter+0x84/0x140 [ext4]
> [1639290.742328]  vfs_write+0x232/0x3e0
> [1639290.742332]  ksys_write+0x6b/0xf0
> [1639290.742334]  do_syscall_64+0x55/0xb0
> [1639290.742337]  ? ksys_read+0x6b/0xf0
> [1639290.742339]  ? exit_to_user_mode_prepare+0x44/0x1f0
> [1639290.742342]  ? syscall_exit_to_user_mode+0x1e/0x40
> [1639290.742344]  ? do_syscall_64+0x61/0xb0
> [1639290.742345]  ? syscall_exit_to_user_mode+0x1e/0x40
> [1639290.742347]  ? do_syscall_64+0x61/0xb0
> [1639290.742349]  ? do_syscall_64+0x61/0xb0
> [1639290.742350]  ? __do_sys_newfstatat+0x4e/0x80
> [1639290.742353]  ? exit_to_user_mode_prepare+0x44/0x1f0
> [1639290.742355]  ? syscall_exit_to_user_mode+0x1e/0x40
> [1639290.742357]  ? do_syscall_64+0x61/0xb0
> [1639290.742358]  ? syscall_exit_to_user_mode+0x1e/0x40
> [1639290.742360]  ? do_syscall_64+0x61/0xb0
> [1639290.742362]  ? syscall_exit_to_user_mode+0x1e/0x40
> [1639290.742363]  ? do_syscall_64+0x61/0xb0
> [1639290.742365]  ? do_syscall_64+0x61/0xb0
> [1639290.742366]  ? do_syscall_64+0x61/0xb0
> [1639290.742367]  ? do_syscall_64+0x61/0xb0
> [1639290.742369]  entry_SYSCALL_64_after_hwframe+0x6e/0xd8
> [1639290.742371] RIP: 0033:0x7fc69729e240
> [1639290.742373] RSP: 002b:00007ffcfc6840e8 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
> [1639290.742375] RAX: ffffffffffffffda RBX: 0000000000a860f8 RCX: 00007fc69729e240
> [1639290.742376] RDX: 0000000000004000 RSI: 00000000019198d0 RDI: 000000000000000d
> [1639290.742378] RBP: 0000000000004000 R08: 0000000000000000 R09: 0000000000000000
> [1639290.742378] R10: 0000000000000003 R11: 0000000000000202 R12: 00007fc6971a4fc0
> [1639290.742380] R13: 000000000000000d R14: 0000000000a440e0 R15: 0000000000000000
> [1639290.742382]  </TASK>
> [1639411.519101] INFO: task lava-run [job: :70173 blocked for more than 241 seconds.
> [1639411.519115]       Not tainted 6.1.0-22-amd64 #1 Debian 6.1.94-1


-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2024-08-20  9:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-18  8:53 [PATCH 6.10 00/25] 6.10.6-rc3 review Greg Kroah-Hartman
2024-08-18 12:50 ` Anders Roxell
2024-08-18 15:28 ` Jon Hunter
2024-08-19  9:16 ` Pavel Machek
2024-08-19 15:18   ` Chris Paterson
2024-08-20  7:37     ` Florian Bezdeka
2024-08-20  9:35       ` Gylstorff Quirin
2024-08-20  9:49       ` Pavel Machek [this message]
2024-08-20 18:04 ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2024-08-18 12:32 Ronald Warsow

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZsRmmQOLiZ1KtQ1T@duo.ucw.cz \
    --to=pavel@denx.de \
    --cc=Chris.Paterson2@renesas.com \
    --cc=akpm@linux-foundation.org \
    --cc=allen.lkml@gmail.com \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=florian.bezdeka@siemens.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=quirin.gylstorff@siemens.com \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox