Decryption screen doesnt show for kernels 6.0.6 and 6.0.12 for Nvidia driver 525 #200
Comments
|
Duplicate of pop-os/plymouth-theme#31 I've reopened the original issue. Updating the same issue is better for us than opening new/duplicate issues. We can reopen any that need to be reopened. |
mmstick
pushed a commit
that referenced
this issue
Aug 21, 2023
commit 90f0074 upstream. BPF CI has reported the following failure: Error: #200/79 sockmap_listen/sockmap VSOCK test_vsock_redir Error: #200/79 sockmap_listen/sockmap VSOCK test_vsock_redir ./test_progs:vsock_unix_redir_connectible:1506: egress: write: Transport endpoint is not connected vsock_unix_redir_connectible:FAIL:1506 ./test_progs:vsock_unix_redir_connectible:1506: ingress: write: Transport endpoint is not connected vsock_unix_redir_connectible:FAIL:1506 ./test_progs:vsock_unix_redir_connectible:1506: egress: write: Transport endpoint is not connected vsock_unix_redir_connectible:FAIL:1506 ./test_progs:vsock_unix_redir_connectible:1514: ingress: recv() err, errno=11 vsock_unix_redir_connectible:FAIL:1514 ./test_progs:vsock_unix_redir_connectible:1518: ingress: vsock socket map failed, a != b vsock_unix_redir_connectible:FAIL:1518 ./test_progs:vsock_unix_redir_connectible:1525: ingress: want pass count 1, have 0 It’s because the recv(... MSG_DONTWAIT) syscall in the test case is called before the queued work sk_psock_backlog() in the kernel finishes executing. So the data to be read is still queued in psock->ingress_skb and cannot be read by the user program. Therefore, the non-blocking recv() reads nothing and reports an EAGAIN error. So replace recv(... MSG_DONTWAIT) with xrecv_nonblock(), which calls select() to wait for data to be readable or timeout before calls recv(). Fixes: d61bd8c ("selftests/bpf: add a test case for vsock sockmap") Signed-off-by: Xu Kuohai <xukuohai@huawei.com> Link: https://lore.kernel.org/r/20230804073740.194770-4-xukuohai@huaweicloud.com Signed-off-by: Martin KaFai Lau <martin.lau@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Note: I've also posted this on pop-os/plymouth-theme#33
I was not sure that was the correct location.
Some time ago I opened a new issue regarding the disappeared loginprompt after applying a new kernel suggested by the Pop!_shop and marked it solved after downgrading to the previous kernel.
(pop-os/plymouth-theme#31 (comment))
However it still doesn't seem to be working for me for new kernels:
6.0.6 and 6.0.12 and Nvidia driver 525 (it did work for kernel 6.0.2)
It shows the BIOS Logo of the mainboard and pressing ESC doesn't do anything,
however entering the password "blind" does work and brings up the user login prompt.
I did another test and disabled the Nvidia graphics card and used the embedded VGA graphics card (server board)
and that worked, the decryption screen was displayed.
So I assume its related to the NVidia drivers and to be sure I ran:
sudo update-initramfs -u -k all
However did didn't fix the login screen. Feel free to close this issue however I thought it might help to bring this up in case other users are also affected.
The text was updated successfully, but these errors were encountered: