All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: david@redhat.com, linux-kernel@vger.kernel.org,
	wsa+renesas@sang-engineering.com, nicholas@linux.ibm.com,
	windhl@126.com, cuigaosheng1@huawei.com, mikey@neuling.org,
	paul@paul-moore.com, haren@linux.ibm.com, joel@jms.id.au,
	lukas.bulwahn@gmail.com, nathanl@linux.ibm.com,
	ajd@linux.ibm.com, ye.xingchen@zte.com.cn, npiggin@gmail.com,
	nathan@kernel.org, rmclure@linux.ibm.com, hbathini@linux.ibm.com,
	atrajeev@linux.vnet.ibm.com, yuanjilin@cdjrlc.com,
	pali@kernel.org, farosas@linux.ibm.com, geoff@infradead.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	gustavoars@kernel.org, lihuafei1@huawei.com,
	aneesh.kumar@linux.ibm.com, zhengyongjun3@huawei.com,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [GIT PULL] Please pull powerpc/linux.git powerpc-6.1-1 tag
Date: Wed, 12 Oct 2022 10:45:46 -0600	[thread overview]
Message-ID: <Y0bvOreqH2BdyVqt@zx2c4.com> (raw)
In-Reply-To: <Y0biBtCUtc2mowbQ@zx2c4.com>

On Wed, Oct 12, 2022 at 09:49:26AM -0600, Jason A. Donenfeld wrote:
> On Wed, Oct 12, 2022 at 07:18:27AM -0700, Guenter Roeck wrote:
> > NIP [c000000000031630] .replay_soft_interrupts+0x60/0x300
> > LR [c000000000031964] .arch_local_irq_restore+0x94/0x1c0
> > Call Trace:
> > [c000000007df3870] [c000000000031964] .arch_local_irq_restore+0x94/0x1c0 (unreliable)
> > [c000000007df38f0] [c000000000f8a444] .__schedule+0x664/0xa50
> > [c000000007df39d0] [c000000000f8a8b0] .schedule+0x80/0x140
> > [c000000007df3a50] [c00000000092f0dc] .try_to_generate_entropy+0x118/0x174
> > [c000000007df3b40] [c00000000092e2e4] .urandom_read_iter+0x74/0x140
> > [c000000007df3bc0] [c0000000003b0044] .vfs_read+0x284/0x2d0
> > [c000000007df3cd0] [c0000000003b0d2c] .ksys_read+0xdc/0x130
> > [c000000007df3d80] [c00000000002a88c] .system_call_exception+0x19c/0x330
> > [c000000007df3e10] [c00000000000c1d4] system_call_common+0xf4/0x258
> 
> Obviously the first couple lines of this concern me a bit. But I think
> actually this might just be a catalyst for another bug. You could view
> that function as basically just:
> 
>     while (something)
>     	schedule();
> 
> And I guess in the process of calling the scheduler a lot, which toggles
> interrupts a lot, something got wedged.
> 
> Curious, though, I did try to reproduce this, to no avail. My .config is
> https://xn--4db.cc/rBvHWfDZ . What's yours?

I also just tried using your github linux-build-test scripts as a guide
for construction a config -- https://xn--4db.cc/B0HpEQDQ -- and loaded
up your rootfs over sdhci and such, and still couldn't manage to
reproduce. I tried commenting out the line "if (!bits)" in
_credit_init_bits(), so that the rng would never initialize, so that the
schedule() loop would just keep on running indefinitely, but still no
dice.

But also, I'm running Linus' tree. From your log, I see
"6.0.0-rc2-00163-ga5edf9815dd7". So maybe these bugs got fixed
elsewhere?

Jason

WARNING: multiple messages have this Message-ID (diff)
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	ajd@linux.ibm.com, aneesh.kumar@linux.ibm.com,
	atrajeev@linux.vnet.ibm.com, christophe.leroy@csgroup.eu,
	cuigaosheng1@huawei.com, david@redhat.com, farosas@linux.ibm.com,
	geoff@infradead.org, gustavoars@kernel.org, haren@linux.ibm.com,
	hbathini@linux.ibm.com, joel@jms.id.au, lihuafei1@huawei.com,
	linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	lukas.bulwahn@gmail.com, mikey@neuling.org, nathan@kernel.org,
	nathanl@linux.ibm.com, nicholas@linux.ibm.com, npiggin@gmail.com,
	pali@kernel.org, paul@paul-moore.com, rmclure@linux.ibm.com,
	ruscur@russell.cc, windhl@126.com,
	wsa+renesas@sang-engineering.com, ye.xingchen@zte.com.cn,
	yuanjilin@cdjrlc.com, zhengyongjun3@huawei.com
Subject: Re: [GIT PULL] Please pull powerpc/linux.git powerpc-6.1-1 tag
Date: Wed, 12 Oct 2022 10:45:46 -0600	[thread overview]
Message-ID: <Y0bvOreqH2BdyVqt@zx2c4.com> (raw)
In-Reply-To: <Y0biBtCUtc2mowbQ@zx2c4.com>

On Wed, Oct 12, 2022 at 09:49:26AM -0600, Jason A. Donenfeld wrote:
> On Wed, Oct 12, 2022 at 07:18:27AM -0700, Guenter Roeck wrote:
> > NIP [c000000000031630] .replay_soft_interrupts+0x60/0x300
> > LR [c000000000031964] .arch_local_irq_restore+0x94/0x1c0
> > Call Trace:
> > [c000000007df3870] [c000000000031964] .arch_local_irq_restore+0x94/0x1c0 (unreliable)
> > [c000000007df38f0] [c000000000f8a444] .__schedule+0x664/0xa50
> > [c000000007df39d0] [c000000000f8a8b0] .schedule+0x80/0x140
> > [c000000007df3a50] [c00000000092f0dc] .try_to_generate_entropy+0x118/0x174
> > [c000000007df3b40] [c00000000092e2e4] .urandom_read_iter+0x74/0x140
> > [c000000007df3bc0] [c0000000003b0044] .vfs_read+0x284/0x2d0
> > [c000000007df3cd0] [c0000000003b0d2c] .ksys_read+0xdc/0x130
> > [c000000007df3d80] [c00000000002a88c] .system_call_exception+0x19c/0x330
> > [c000000007df3e10] [c00000000000c1d4] system_call_common+0xf4/0x258
> 
> Obviously the first couple lines of this concern me a bit. But I think
> actually this might just be a catalyst for another bug. You could view
> that function as basically just:
> 
>     while (something)
>     	schedule();
> 
> And I guess in the process of calling the scheduler a lot, which toggles
> interrupts a lot, something got wedged.
> 
> Curious, though, I did try to reproduce this, to no avail. My .config is
> https://xn--4db.cc/rBvHWfDZ . What's yours?

I also just tried using your github linux-build-test scripts as a guide
for construction a config -- https://xn--4db.cc/B0HpEQDQ -- and loaded
up your rootfs over sdhci and such, and still couldn't manage to
reproduce. I tried commenting out the line "if (!bits)" in
_credit_init_bits(), so that the rng would never initialize, so that the
schedule() loop would just keep on running indefinitely, but still no
dice.

But also, I'm running Linus' tree. From your log, I see
"6.0.0-rc2-00163-ga5edf9815dd7". So maybe these bugs got fixed
elsewhere?

Jason

  parent reply	other threads:[~2022-10-12 16:46 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-09 11:01 [GIT PULL] Please pull powerpc/linux.git powerpc-6.1-1 tag Michael Ellerman
2022-10-09 11:01 ` Michael Ellerman
2022-10-09 21:17 ` pr-tracker-bot
2022-10-09 21:17   ` pr-tracker-bot
2022-10-10 19:25 ` Jason A. Donenfeld
2022-10-10 19:25   ` Jason A. Donenfeld
2022-10-10 20:03   ` Jason A. Donenfeld
2022-10-10 20:03     ` Jason A. Donenfeld
2022-10-10 22:26     ` Jason A. Donenfeld
2022-10-10 22:26       ` Jason A. Donenfeld
2022-10-11  0:00       ` Andrew Donnellan
2022-10-11  0:00         ` Andrew Donnellan
2022-10-11  0:13         ` Jason A. Donenfeld
2022-10-11  0:13           ` Jason A. Donenfeld
2022-10-11  1:44           ` Michael Ellerman
2022-10-11  1:44             ` Michael Ellerman
2022-10-11  2:57             ` Jason A. Donenfeld
2022-10-11  2:57               ` Jason A. Donenfeld
2022-10-11  9:34               ` Michael Ellerman
2022-10-11  9:34                 ` Michael Ellerman
2022-10-11  1:53     ` Michael Ellerman
2022-10-11  1:53       ` Michael Ellerman
2022-10-11  2:57       ` Jason A. Donenfeld
2022-10-11  2:57         ` Jason A. Donenfeld
2022-10-11  9:35         ` Michael Ellerman
2022-10-11  9:35           ` Michael Ellerman
2022-10-11 11:10           ` Nicholas Piggin
2022-10-11 11:10             ` Nicholas Piggin
2022-10-12 14:18 ` Guenter Roeck
2022-10-12 14:18   ` Guenter Roeck
2022-10-12 15:49   ` Jason A. Donenfeld
2022-10-12 15:49     ` Jason A. Donenfeld
2022-10-12 16:44     ` Guenter Roeck
2022-10-12 16:44       ` Guenter Roeck
2022-10-12 17:20       ` Jason A. Donenfeld
2022-10-12 17:20         ` Jason A. Donenfeld
2022-10-12 17:48         ` Guenter Roeck
2022-10-12 17:48           ` Guenter Roeck
2022-10-12 18:37           ` Jason A. Donenfeld
2022-10-12 18:37             ` Jason A. Donenfeld
2022-10-13  5:17             ` Nicholas Piggin
2022-10-13  5:17               ` Nicholas Piggin
2022-10-12 22:16         ` Guenter Roeck
2022-10-12 22:16           ` Guenter Roeck
2022-10-13  0:03           ` Michael Ellerman
2022-10-13  0:03             ` Michael Ellerman
2022-10-13  0:21             ` Guenter Roeck
2022-10-13  0:21               ` Guenter Roeck
2022-10-13  5:03               ` Nicholas Piggin
2022-10-13  5:03                 ` Nicholas Piggin
2022-10-13  5:19                 ` Jason A. Donenfeld
2022-10-13  5:19                   ` Jason A. Donenfeld
2022-10-13  5:20                 ` Guenter Roeck
2022-10-13  5:20                   ` Guenter Roeck
2022-10-13  5:22               ` Nicholas Piggin
2022-10-13  5:22                 ` Nicholas Piggin
2022-10-13  4:43         ` Guenter Roeck
2022-10-13  4:43           ` Guenter Roeck
2022-10-13  5:14           ` Nicholas Piggin
2022-10-13  5:14             ` Nicholas Piggin
2022-10-13 18:55             ` Guenter Roeck
2022-10-13 18:55               ` Guenter Roeck
2022-10-12 16:45     ` Jason A. Donenfeld [this message]
2022-10-12 16:45       ` Jason A. Donenfeld
2022-10-12 16:49       ` Guenter Roeck
2022-10-12 16:49         ` Guenter Roeck

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=Y0bvOreqH2BdyVqt@zx2c4.com \
    --to=jason@zx2c4.com \
    --cc=ajd@linux.ibm.com \
    --cc=aneesh.kumar@linux.ibm.com \
    --cc=atrajeev@linux.vnet.ibm.com \
    --cc=cuigaosheng1@huawei.com \
    --cc=david@redhat.com \
    --cc=farosas@linux.ibm.com \
    --cc=geoff@infradead.org \
    --cc=gustavoars@kernel.org \
    --cc=haren@linux.ibm.com \
    --cc=hbathini@linux.ibm.com \
    --cc=joel@jms.id.au \
    --cc=lihuafei1@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=mikey@neuling.org \
    --cc=nathan@kernel.org \
    --cc=nathanl@linux.ibm.com \
    --cc=nicholas@linux.ibm.com \
    --cc=npiggin@gmail.com \
    --cc=pali@kernel.org \
    --cc=paul@paul-moore.com \
    --cc=rmclure@linux.ibm.com \
    --cc=torvalds@linux-foundation.org \
    --cc=windhl@126.com \
    --cc=wsa+renesas@sang-engineering.com \
    --cc=ye.xingchen@zte.com.cn \
    --cc=yuanjilin@cdjrlc.com \
    --cc=zhengyongjun3@huawei.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.