I find why my system not boot.
After some googling and test, i used kernel parameters "amdgpu.aspm=0" and
system booted. Seems it now set to auto for default.
aspm
ASPM support (1 = enable, 0 = disable, -1 = auto)
Also booted old kernels from 5.14 . Now i am on 5.17
$ uname -a
Linux
Running 5.13.0-xx on Parallels Desktop on M1 Macbook. 5.13.0-12-generic
is the last kernel that will boot. -13 and -14 have been withdrawn,
apparently. -15 and -16 just hang as soon as control is given to the
kernel back from the EFI loader. Some fail code was backported post -12
from more recent
Had a similar issue on a 20.04 install today after updating to 5.14.
Woke it up from suspend on 5.10.0-1057-oem. Rebooted once (some screen
issues that turned out to be the screen), installed updates via update-
manager, rebooted using the new 5.14.0-1024-oem kernel and it just hung.
Black
Still the same with v5.16-rc8.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942684
Title:
Kernel 5.14.X / 5.13.14 fails to boot
To manage notifications about this bug go to:
New system. Ubuntu 21.10
I am on official kernel, but wanted use latest.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942684
Title:
Kernel 5.14.X / 5.13.14 fails to boot
To manage notifications
Is it a new or old system?
What's the last working kernel version for you?
Have you considered going back to the official kernel version for your
Ubuntu (if it works?)?
Another option you may have would be to try disabling that
"...SANITZE_ALL" config and rebuild the kernel from kernel.org using
Does not find it.
Only find by word "UBSAN":
CONFIG_ARCH_HAS_UBSAN_SANITIZE_ALL=y
# CONFIG_UBSAN is not set
My system hangs up on early start. Not response any key. Alt+SysRq+b not work
too.
But if I choose Recovery mode, an then continue booting, it boots.
--
You received this bug
1) Do an $ ls -lah /boot
2) look for config-5.15.6 file and nano into it. That's the
config for the kernel that Ubuntu used for building it.
3) ctrl+w and type or paste "CONFIG_UBSAN_TRAP" and hit enter. (paste
is ctrl+shift+v)
If it doesn't find it, then it is odd that it doesn't work for
I'm trying kernel from
https://kernel.ubuntu.com/~kernel-ppa/mainline/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942684
Title:
Kernel 5.14.X / 5.13.14 fails to boot
To manage notifications
Does it have "CONFIG_UBSAN_TRAP" set in the config?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942684
Title:
Kernel 5.14.X / 5.13.14 fails to boot
To manage notifications about this bug go to:
5.15.6 still fails to boot on my desktop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942684
Title:
Kernel 5.14.X / 5.13.14 fails to boot
To manage notifications about this bug go to:
Kernel works ok.
So as it stands, new 5.15.3 has no "CONFIG_UBSAN_TRAP" in config.
So for new kernels you can probably close this bug off as long as they
don't reintroduce it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looks like they may have removed "CONFIG_UBSAN_TRAP" from the kernel
config of 5.15.3!
Only this is in the config...
```
# CONFIG_UBSAN is not set
```
I'm building it now to see if it is ok and works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Fails for me too 5.15.1 on Penryn, Ivybridge, Haswell and guest VMs on
Zen3.
I had to rebuild the kernel from kernel.org using the config from Ubuntu
Mainline but disabling the debian pem certs and "CONFIG_UBSAN_TRAP".
After that it worked on all the above architectures.
--
You received this
Seems Ubuntu Mainline Kernel team doesn't hear us as 5.15.1 still fails
to boot but they're don't care about it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942684
Title:
Kernel 5.14.X / 5.13.14
On another test, using vanilla Ubuntu mainline 5.14.14 on a guest VBOX
VM runs ok for about half a day then crashes to black screen. This has
happened 4x!
Replacing the vanilla Ubuntu mainline 5.14.14 with a custom build of
5.14.14 using point 1 above (see comment 43) has so far worked for 3
Done
Point 1) above WORKS on zen3, haswell, and ivybridge.
That means disabled 'CONFIG_UBSAN_TRAP' in the kernel config prior to building.
Just nano or vim into the ".config" and put a '#' in front of the line to
disable it. before running "$ make olddefconfig"
I built the kernel using LLVM-13
Tried building 5.14.14 from vanilla upstream
https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.14.14.tar.xz
using the config from ubuntu mainline config-5.14.14-051414-generic
but removing the debian "pem" for a custom kernel build; and...
It fails to boot after grub for ivybridge and haswell
How to disable "CONFIG_UBSAN_TRAP" and check boot? Or need recompiled
kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942684
Title:
Kernel 5.14.X / 5.13.14 fails to boot
To manage
Adding
i915.fastboot=0
to the kernel params allows booting on these kernels.
(Tested working on a XPS 9575)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942684
Title:
Kernel 5.14.X / 5.13.14
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942377
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942684
Title:
Kernel 5.14.X / 5.13.14 fails to boot
To manage notifications about this
Install linux 5.14.8 and my system not boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942684
Title:
Kernel 5.14.X / 5.13.14 fails to boot
To manage notifications about this bug go to:
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: vladimir 1867 F pipewire-media-
/dev/snd/controlC2: vladimir 1867 F pipewire-media-
/dev/snd/controlC0: vladimir 1867 F
NVIDIA driver version 470.74 fixes my usb-c displayport issues.
But I still think leaving the CONFIG_UBSAN_TRAP flag in the build is
concerning (at least, based on the documentation for the flag). It's
probably okay for testing
--
You received this bug notification because you are a member of
I can confirm that 5.14.7 boots, but my usb-c displayport out using my
Kensington dock doesn't work. I'll try upgrading the NVIDIA drivers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942684
"Fixed a bug that caused nvidia-drm.ko to crash when loading with DRM-KMS
enabled (modeset=1) on Linux v5.14"
Could this be the fix then?
https://www.nvidia.com/Download/driverResults.aspx/180475/en-us
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Linux 5.15-rc2 is booting ok with the latest nvidia driver (470.74)
It seems the RIP: 0010:nv_drm_format_array_alloc+0xb3/0xb5 [nvidia_drm] is not
CONFIG_UBSAN_TRAP fault.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The patch "drm/amd/amdgpu: Increase HWIP_MAX_INSTANCE to 10" fixes the
KOOPS. I am currently on 5.15-rc2 and have not experienced any issues. I
reckon that 5.14.7 will also be fine since the changelog shows that the
same patch was backported.
Looks like this bug has always been there but was
CONFIG_UBSAN_TRAP was added from this issue:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914685
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942684
Title:
Kernel 5.14.X / 5.13.14 fails
It looks like the following patch from Aug. 20, 2021 enabled CONFIG_UBSAN_TRAP:
https://patchwork.ozlabs.org/project/ubuntu-kernel/patch/20210820071002.3560053-5-keesc...@chromium.org/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just to confirm, Ubuntu's mainline 5.14.5 kernel does boot successfully
on my machine with CONFIG_UBSAN_TRAP not set.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942684
Title:
Kernel 5.14.X /
I also can't boot the mainline 5.14-4 or 5.14-5 kernels on a Lenovo S7
(AMD 5800H and NVIDIA GPU) - it goes to a blank screen when trying to
boot graphics and freezes - I can't open a tty and have to hard reset
the system.
It looks like I have the laptop in the same mode as the other posters,
ie
@ernstp, what can we do to bypass this? Or what info do we need to
provide in order to catch what is making the kerel to stop?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942684
Title:
Kernel
From my investigation the issue was not caused by a kernel patch but by
the Mainline ppa enabling CONFIG_UBSAN_TRAP
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942684
Title:
Kernel 5.14.X /
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942684
Title:
Kernel 5.14.X / 5.13.14 fails to boot
To manage notifications about this bug go to:
Patch file of commit that caused the regression
** Patch added: "patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942684/+attachment/5524711/+files/5.14.X-KOOPS.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK, so none of the 5.14.0/1/2/3 kernels will boot. As I mentioned
before...1 of the 3 pacthes introduced the regression:
Borislav Petkov (1):
drm/amdgpu: Fix build with missing pm_suspend_target_state module export
Christian König (1):
drm/amdgpu: use the preferred pin domain after
** Summary changed:
- Kernel 5.14.0/1/5.13.14 fails to boot
+ Kernel 5.14.X / 5.13.14 fails to boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942684
Title:
Kernel 5.14.X / 5.13.14 fails to
38 matches
Mail list logo
