[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic

2022-10-11 Thread Karl Klein
*** This bug is a duplicate of bug 1991704 *** https://bugs.launchpad.net/bugs/1991704 Hi Andrea, Many thanks for the fixed kernel. I tried installing it with "sudo dpkg -i --force-overwrite *" but it would not boot. I see multiple error messages like "failed to validate module

[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic

2022-10-10 Thread Daniel Swarbrick
*** This bug is a duplicate of bug 1991704 *** https://bugs.launchpad.net/bugs/1991704 I tried the suggested workaround of purging nvidia packages and running ubuntu-drivers install. What I observed is that the nvidia-driver-510 packages were removed, and ubuntu-drivers subsequently installed

[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic

2022-10-10 Thread Andrea Righi
*** This bug is a duplicate of bug 1991704 *** https://bugs.launchpad.net/bugs/1991704 ** This bug has been marked a duplicate of bug 1991704 Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic

2022-10-10 Thread Heinrich Schuchardt
sudo apt-get --purge remove '*nvidia*' sudo ubuntu-drivers install solved the problem for me. I am in KDE running in 5.19.0-19-generic with Nvidia 515 drivers. Thanks a lot. Best regards Heinrich -- You received this bug notification because you are a member of Kernel Packages, which is

[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic

2022-10-10 Thread Alberto Milone
Hi Heinrich, I can see the following in your dmesg log: NVRM: API mismatch: the client has the version 515.65.01, but NVRM: this kernel module has the version 510.85.02 Can you follow these steps, please, so that we can rule out this being the main problem? Remove any nvidia package left on

[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic

2022-10-10 Thread Andrea Righi
So, it looks like there are multiple issues here. The NULL pointer dereference bug that I see in comment #25 seems to be fixed by 458ec0c8f359 ("drm/i915: fix null pointer dereference"), but this can happen only when i915 is used. For the other problem(s) do you happen to have a kernel oops /

[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic

2022-10-10 Thread Heinrich Schuchardt
Hello Andrea, As expected an i915 fix is irrelevant for a system without an i915 GPU. The problem persists with your kernel. Best regards Heinrich -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu.

[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic

2022-10-10 Thread Andrea Righi
Test kernel (5.19.0-19.19+i915fix) available here: https://kernel.ubuntu.com/~arighi/lp-1991703/ It would be great if someone affected by this problem could test this out. Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed

[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic

2022-10-10 Thread Heinrich Schuchardt
Thanks Andrea for looking into the issue. Would the code changed in 458ec0c8f359 ("drm/i915: fix null pointer dereference") ever be executed on an AMD Ryzen processor with an Nvidia card? Doesn't the driver framework detect that there is no i915 GPU? -- You received this bug notification

[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic

2022-10-10 Thread Andrea Righi
This bug should be fixed by 458ec0c8f359 ("drm/i915: fix null pointer dereference"), I'll prepare a test kernel with this fix applied on top of 5.19.0-19.19. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu.

[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic

2022-10-10 Thread Heinrich Schuchardt
The same problem exists with linux-image-5.19.0-19-generic ** Summary changed: - Failure to boot with linux-image-5.19.0-18-generic + Failure to boot with linux-image-5.19.0-18-generic and -5.19.0-19-generic -- You received this bug notification because you are a member of Kernel Packages,

[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic

2022-10-08 Thread Jeffrey Baker
I don't know how to bring this to the attention of the relevant people, but this is clearly a show-stopper. It renders most intel systems unbootable. It's really unfortunate that a diff of this size was slipped in moments before the kernel freeze. In my opinion having the system in a non-working

[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic

2022-10-07 Thread Karl Klein
I suspect that my installation has the same issue (Ubuntu 22.04 upgraded to 22.10 on Framework i5-1240p). I am using Gnome. Linux 5.19.0-18-generic fails to boot. It just stops during the boot process and does not show the login screen. It does boot with the kernel parameter "nomodeset" but then

[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic

2022-10-06 Thread Kim Botherway
Also affected is linux-image-5.19.0-19-generic in Kinetic proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1991703 Title: Failure to boot with

[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic

2022-10-05 Thread Jeffrey Baker
This seems to be the relevant utterance of the kernel that fails to boot: i915 :00:02.0: vgaarb: deactivate vga console BUG: kernel NULL pointer dereference, address: 002e #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD 0 P4D 0 Oops:

[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic

2022-10-05 Thread Jeffrey Baker
I'm also seeing failure to boot with -18 (-15 works) and I do not have nvidia graphics, I have i915. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1991703 Title: Failure to boot

[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic

2022-10-05 Thread Daniel Swarbrick
I'm also seeing failure to boot with linux-image-5.19.0-18-generic, on a Dell XPS 15 9510 (with NVIDIA RTX 3050 Ti). It was the only update that I installed yesterday. Prior to that, kinetic has been remarkably reliable for a pre-release. -- You received this bug notification because you are a

[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic

2022-10-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-515 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu.

[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic

2022-10-04 Thread Heinrich Schuchardt
Could this be a problem with the Nvidia DKMS driver? On a laptop using the Radeon driver I have no problem. ** Also affects: nvidia-graphics-drivers-515 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which

[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic

2022-10-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu.