mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, shuah@kernel.org,
	patches@kernelci.org, lkft-triage@lists.linaro.org,
	pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de
Subject: Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
Date: Tue, 14 Feb 2023 19:05:55 +0100	[thread overview]
Message-ID: <Y+vNg6Dy3zUJ7pjp@kroah.com> (raw)
In-Reply-To: <1cd10087-87fe-048e-c9ed-0a5d32c50764@roeck-us.net>

On Tue, Feb 14, 2023 at 09:51:39AM -0800, Guenter Roeck wrote:
> On 2/14/23 09:15, Guenter Roeck wrote:
> > On 2/13/23 06:49, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 5.10.168 release.
> > > There are 139 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 Wed, 15 Feb 2023 14:46:51 +0000.
> > > Anything received after that time might be too late.
> > > 
> > 
> > Seen with several x86_64 boot tests during reboot:
> > 
> > [   13.465146] ------------[ cut here ]------------
> > [   13.465644] list_del corruption. prev->next should be ffff9836448a5008, but was ffff9836448a2010
> > ILLOPC: ffffffffae597813: 0f 0b
> > [   13.466452] WARNING: CPU: 0 PID: 302 at lib/list_debug.c:59 __list_del_entry_valid+0xb3/0xe0
> > [   13.466710] Modules linked in:
> > [   13.467103] CPU: 0 PID: 302 Comm: init Not tainted 5.10.168-rc1+ #1
> > [   13.467281] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015
> > [   13.467545] RIP: 0010:__list_del_entry_valid+0xb3/0xe0
> > [   13.468234] Code: cc cc cc 4c 89 c2 48 c7 c7 f8 c6 82 af e8 ad c9 8e 00 0f 0b 31 c0 c3 cc cc cc cc 4c 89 c2 48 c7 c7 30 c7 82 af e8 95 c9 8e 00 <0f> 0b 31 c0 c3 cc cc cc cc 4c 89 c6 48 c7 c7 70 c7 82 af e8 7d c9
> > [   13.468694] RSP: 0018:ffff9f160017bde0 EFLAGS: 00000282
> > [   13.469076] RAX: 0000000000000000 RBX: ffff9836448a5008 RCX: 0000000000000006
> > [   13.469297] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffffae0e03dd
> > [   13.469494] RBP: ffff98364482c2f0 R08: 0000000000000001 R09: 0000000000000001
> > [   13.469699] R10: 0000000000000001 R11: ffffffffafa6f3e0 R12: ffff9836448a5000
> > [   13.469974] R13: ffff9836448a3910 R14: 00000000fee1dead R15: 0000000000000000
> > [   13.470122] FS:  00007ff4118d7b28(0000) GS:ffff98365f600000(0000) knlGS:0000000000000000
> > [   13.470230] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > [   13.470311] CR2: 00007fd877982830 CR3: 0000000005218000 CR4: 00000000001506f0
> > [   13.470438] Call Trace:
> > [   13.470532]  device_shutdown+0xae/0x1c0
> > [   13.470610]  __do_sys_reboot.cold+0x2f/0x5b
> > [   13.470675]  ? __lock_acquire+0x5bd/0x2640
> > [   13.470777]  ? lock_acquire+0xc6/0x2b0
> > [   13.470934]  ? lockdep_hardirqs_on_prepare+0xdc/0x1a0
> > [   13.471015]  ? syscall_enter_from_user_mode+0x1d/0x50
> > [   13.471101]  do_syscall_64+0x33/0x40
> > [   13.471162]  entry_SYSCALL_64_after_hwframe+0x61/0xc6
> > [   13.471313] RIP: 0033:0x7ff411860aa6
> > [   13.471437] Code: ff 5a c3 48 63 ff b8 bb 00 00 00 0f 05 48 89 c7 e9 95 e9 ff ff 48 63 d7 bf ad de e1 fe 50 be 69 19 12 28 b8 a9 00 00 00 0f 05 <48> 89 c7 e8 78 e9 ff ff 5a c3 49 89 ca 50 48 63 d2 4d 63 c0 b8 d8
> > [   13.471627] RSP: 002b:00007ffd01d415e0 EFLAGS: 00000246 ORIG_RAX: 00000000000000a9
> > [   13.471741] RAX: ffffffffffffffda RBX: 000000000000000f RCX: 00007ff411860aa6
> > [   13.471899] RDX: 0000000001234567 RSI: 0000000028121969 RDI: 00000000fee1dead
> > [   13.472008] RBP: 0000000001234567 R08: 0000000000000000 R09: 0000000000000000
> > [   13.472099] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
> > [   13.472185] R13: 00007ffd01d417a8 R14: 00007ff4118d7b28 R15: 0000000000000000
> > [   13.472384] irq event stamp: 479
> > [   13.472453] hardirqs last  enabled at (487): [<ffffffffae0e03dd>] console_unlock+0x4dd/0x5e0
> > [   13.472560] hardirqs last disabled at (494): [<ffffffffae0e0334>] console_unlock+0x434/0x5e0
> > [   13.472666] softirqs last  enabled at (242): [<ffffffffaf000fe2>] asm_call_irq_on_stack+0x12/0x20
> > [   13.472775] softirqs last disabled at (237): [<ffffffffaf000fe2>] asm_call_irq_on_stack+0x12/0x20
> > [   13.472964] ---[ end trace 34290884cd36b277 ]---
> > 
> > Currently bisecting.
> > 
> Reverting the nvmem patches fixed this problem.

nvmem patches are now dropped and a -rc2 is pushed out.

thanks,

greg k-h

  parent reply	other threads:[~2023-02-14 18:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13 14:49 Greg Kroah-Hartman
2023-02-13 17:26 ` Pavel Machek
2023-02-13 19:50 ` Florian Fainelli
2023-02-14  6:20   ` Greg Kroah-Hartman
2023-02-14 13:20     ` Russell King (Oracle)
2023-02-14 14:53     ` Russell King (Oracle)
2023-02-14 15:09       ` Sasha Levin
2023-02-14 15:25         ` Russell King (Oracle)
2023-02-14 15:33           ` Sasha Levin
2023-02-14 15:39             ` Russell King (Oracle)
2023-02-14  9:16   ` Naresh Kamboju
2023-02-14 13:21     ` Naresh Kamboju
2023-02-13 23:33 ` Shuah Khan
2023-02-14  6:51 ` Guenter Roeck
2023-02-14 11:05 ` Sudip Mukherjee (Codethink)
2023-02-14 17:04 ` Guenter Roeck
2023-02-14 17:59   ` Guenter Roeck
2023-02-14 17:15 ` Guenter Roeck
2023-02-14 17:51   ` Guenter Roeck
2023-02-14 17:54     ` Linus Torvalds
2023-02-14 18:09       ` Guenter Roeck
2023-02-14 18:05     ` Greg Kroah-Hartman [this message]
2023-02-14 19:45 ` Salvatore Bonaccorso
2023-02-14 19:57   ` Guenter Roeck
2023-02-14 20:30     ` Salvatore Bonaccorso
2023-02-15  7:30 ` zhouzhixiu

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=Y+vNg6Dy3zUJ7pjp@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=f.fainelli@gmail.com \
    --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=pavel@denx.de \
    --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

all inboxes | Powered by JetHome®