New kernels

[musa]

Hi
Vmlinux-6.10-8 get a kernel panic

[xeno74]

Hi
Vmlinux-6.10-8 get a kernel panic

OK, "git bisect bad". Thank you for testing.

The next one: vmlinux-6.10-9

md5sum: 1a89be4d2b2150b34ecbd8a6fb8334c5

[musa]

Hi
Vmlinux-6.10-9 boot Fienix to lightdm.service error.
I can log in with the promt

[xeno74]

Hi
Vmlinux-6.10-9 boot Fienix to lightdm.service error.
I can log in with the promt

OK, "git bisect good". Thank you for testing.

0aa3be7b3e1f8f997312cc4705f8165e02806f8f is the first bad commit.
commit 0aa3be7b3e1f8f997312cc4705f8165e02806f8f

Code: Select all

Author: Kuniyuki Iwashima <[email protected]>
Date:   Tue Jun 4 09:52:35 2024 -0700

    af_unix: Annotate data-races around sk->sk_state in UNIX_DIAG.
    
    While dumping AF_UNIX sockets via UNIX_DIAG, sk->sk_state is read
    locklessly.
    
    Let's use READ_ONCE() there.
    
    Note that the result could be inconsistent if the socket is dumped
    during the state change.  This is common for other SOCK_DIAG and
    similar interfaces.
    
    Fixes: c9da99e6475f ("unix_diag: Fixup RQLEN extension report")
    Fixes: 2aac7a2cb0d9 ("unix_diag: Pending connections IDs NLA")
    Fixes: 45a96b9be6ec ("unix_diag: Dumping all sockets core")
    Signed-off-by: Kuniyuki Iwashima <[email protected]>
    Signed-off-by: Paolo Abeni <[email protected]>

 net/unix/diag.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

We have to check, if this commit is really the first bad commit.

Code: Select all

git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git b

Code: Select all

cp -R b a

Code: Select all

cd a

Code: Select all

git checkout 0aa3be7b3e1f8f997312cc4705f8165e02806f8f

HEAD -> 0aa3be7b3e1f af_unix: Annotate data-races around sk->sk_state in UNIX_DIAG.

Please test the following kernel: vmlinux-6.10-10

Thanks

[Hypex]

So I've tested up to the vmlinux-6.10-9 kernel. I get the same lightrdm error. Here is a little more info on it:

Code: Select all

x lightdm.service - Light Display Manager
     Loaded: loaded (/lib/systemd/system/lightdm.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Tue 2024-06-25 03:16:52 AEST; 2min 55s ago
   Duration: 60ms
       Docs: man:lightdm(1)
    Process: 2362 ExecStart=/usr/sbin/lightdm (code=exited, status=1/FAILURE)
   Main PID: 2362 (code=exited, status=1/FAILURE)
        CPU: 98ms

Jun 25 03:16:52 fienix systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5.
Jun 25 03:16:52 fienix systemd[1]: Stopped lightdm.service - Light Display Manager.
Jun 25 03:16:52 fienix systemd[1]: lightdm.service: Start request repeated too quickly.
Jun 25 03:16:52 fienix systemd[1]: lightdm.service: Failed with result 'exit-code'.
Jun 25 03:16:52 fienix systemd[1]: Failed to start lightdm.service - Light Display Manager.
Jun 25 03:16:52 fienix systemd[1]: lightdm.service: Triggering OnFailure= dependencies.
Jun 25 03:16:52 fienix systemd[1]: lightdm.service: Failed to enqueue OnFailure= job, ignoring: Unit plymouth-quit.service not found.

So what I wonder is what happened to RC5 and beyond? All these kernels are RC1 releases. Without specific modules won't they fail?

[xeno74]

So I've tested up to the vmlinux-6.10-9 kernel. I get the same lightrdm error. Here is a little more info on it:

Code: Select all

x lightdm.service - Light Display Manager
     Loaded: loaded (/lib/systemd/system/lightdm.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Tue 2024-06-25 03:16:52 AEST; 2min 55s ago
   Duration: 60ms
       Docs: man:lightdm(1)
    Process: 2362 ExecStart=/usr/sbin/lightdm (code=exited, status=1/FAILURE)
   Main PID: 2362 (code=exited, status=1/FAILURE)
        CPU: 98ms

Jun 25 03:16:52 fienix systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5.
Jun 25 03:16:52 fienix systemd[1]: Stopped lightdm.service - Light Display Manager.
Jun 25 03:16:52 fienix systemd[1]: lightdm.service: Start request repeated too quickly.
Jun 25 03:16:52 fienix systemd[1]: lightdm.service: Failed with result 'exit-code'.
Jun 25 03:16:52 fienix systemd[1]: Failed to start lightdm.service - Light Display Manager.
Jun 25 03:16:52 fienix systemd[1]: lightdm.service: Triggering OnFailure= dependencies.
Jun 25 03:16:52 fienix systemd[1]: lightdm.service: Failed to enqueue OnFailure= job, ignoring: Unit plymouth-quit.service not found.

So what I wonder is what happened to RC5 and beyond? All these kernels are RC1 releases. Without specific modules won't they fail?

This is an old bug. It was solved 4 weeks ago. Link: Xorg issue because of using macros to define ioctls
You see this bug again because of bisecting.

Could you also please test the kernel vmlinux-6.10-10?

[musa]

Hi
vmlinux-6.10-10 get a kernel panic
Have a nice day

[xeno74]

Hi
vmlinux-6.10-10 get a kernel panic
Have a nice day

Thank you for testing!

Code: Select all

cp -R b a

Code: Select all

cd a

Code: Select all

git checkout 0aa3be7b3e1f8f997312cc4705f8165e02806f8f

HEAD -> 0aa3be7b3e1f af_unix: Annotate data-races around sk->sk_state in UNIX_DIAG.

Code: Select all

git revert 0aa3be7b3e1f8f997312cc4705f8165e02806f8f

Revert "af_unix: Annotate data-races around sk->sk_state in UNIX_DIAG."
1 file changed, 4 insertions(+), 4 deletions(-)

Please test the following kernel: vmlinux-6.10-11

Thanks

[musa]

Hi
Vmkernel-6.10-11 boot fienix bot stop with lightdm.service error
I can log in from promt

[xeno74]

Hi
Vmkernel-6.10-11 boot fienix bot stop with lightdm.service error
I can log in from promt

Thanks a lot for testing. Please also test the following kernel: vmlinux-6.10-12