Public bug reported:
Newly installed kernel linux-image-5.19.0-43-generic 5.19.0.43.39 does
not boot with the following diagnostics:
-
error: cannot allocate kernel buffer.
error: you need to load the kernel first.
Press any key to continue...
Failed to boot both default and fallback
5.13.0-25 fixed for me amdgpu graphics init issue on AMD Ryzen 5 3400G.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1956401
Title:
amdgpu hangs for 90 seconds at a time in 5.13.0-23,
Enabled proposed, kernel updated to 5.13.0-24-generic. Works fine!
Thanks a lot for the quick fix.
System:Host: alrock Kernel: 5.13.0-24-generic x86_64 bits: 64 Desktop:
GNOME 40.5 Distro: Ubuntu 21.10 (Impish Indri)
CPU: Info: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega Graph
Another "slow" kernel on AMD CPU, see also bug 1956408 and bug 1956396
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1956532
Title:
Linux Kernel 5.13.0-23 Slows everything
Status in li
Observe the same, confirmed that it is an issue with amdgpu failing to
init graphics, see bug 1956399
Not sure how dupes are supposed to be handled.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
This one and bug 1956396 look like duplicates.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1956408
Title:
Ubuntu 21.10 very slow after kernel update to 5.13.0-23-generic
Status in li
There is a bunch of AMD graphics related bugs associated with the latest
kernel update on 21.10. I wonder whether they could have common root
cause. Personally, I observe the same behavior as described in comment
#4 above, I've submitted bug 1956399.
--
You received this bug notification because
Confirmed that graphics init fails: when system is restarted with broken
kernel, it is accessible via ssh.
Grepping for amdgpu in kern.log results in:
Jan 5 18:50:53 alrock kernel: [3.910928] [drm] amdgpu kernel modesetting
enabled.
Jan 5 18:50:53 alrock kernel: [3.911042] amdgpu: Topo
Public bug reported:
After latest upgrade of linux-image to 5.13.0.23.34 system seem to boot,
but it looks like graphics does not initialize correctly. After showing
initial init logging, at the moment when X should init and graphics
login should appear, monitor just goes to sleep and provides dia
Something in the updates made it work for me.
On the latest series of updates I've noticed kernel update to
4.18.0.9.10 and gave it a try. I still observe in dmesg diagnostics dump
about "Bad or missing usercopy whitelist? Kernel memory exposure
attempt..." but I am able to start session with nvid
@NiBu what do you mean by: "Booting in recovery mode and resuming normal
start works."?
On Tue, 9 Oct 2018, 22:15 NiBu, <1796...@bugs.launchpad.net> wrote:
> Booting in recovery mode and resuming normal start works.
>
> --
> You received this bug notification because you are subscribed to the bug
Also seen it. It was first thing I did. Forgot to mention it.
See comment #4 above: it was done with libelf-dev installed.
On Tue, Oct 9, 2018 at 1:10 PM Cristian Aravena Romero
wrote:
> Hello,
>
> In 'make.log':
>
> 'Makefile:958: "Cannot use CONFIG_STACK_VALIDATION=y, please install
> libelf
Found patch [0] fixing module build. Observe the same behavior.
[0]
https://www.hlmjr.com/index.php/2018/08/21/nvidia-drivers-390-77-vs-linux-kernel-4-18
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
Yes it is started right after the upgrade from 18.04. 18.04 with the
latest SW was running just fine (on kernel 4.15.0-36-generic). Have not
seen it working on 18.10.
Tried 4.19-rc7.
Observations:
* Update manager "enables" driver, but it is not loaded
* Manual install of nvidia-driver-390 xserve
*** This bug is a duplicate of bug 1796726 ***
https://bugs.launchpad.net/bugs/1796726
Data collected by "ubuntu-bug linux", while system was using proprietary
nvidia driver can be found in bug 1796730
--
You received this bug notification because you are a member of Kernel
Packages, which i
Public bug reported:
Extra info for bug 1796433
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-8-generic 4.18.0-8.9
ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
Uname: Linux 4.18.0-8-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20
Public bug reported:
Extra info for bug 1796433
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-8-generic 4.18.0-8.9
ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
Uname: Linux 4.18.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
AudioDevic
Submitted bug 1796726
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1796433
Title:
Ubuntu 18.10 regression: nvidia driver does not work
Status in nvidia-graphics-
Public bug reported:
Problems started after upgrade to 18.10 and first reboot.
Symptoms:
* Login screen appears
* After providing credentials desktop does not start
Part of dmesg:
-
...
[ 10.482929] resource sanity check: requesting [mem 0x000c000
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1796433/+attachment/5197786/+files/dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubu
Sorry for late reply. Fixed in 4.15.0.24.26. Just checked changelog,
indeed #1752772 fixed in this kernel version.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1759644
Title:
[18.04] R
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1759644
Title:
[18.04] Regression: wired network does not work upon re
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095248/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1759644
Ti
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095253/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1759644
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095261/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095255/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095250/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/17
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095256/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095258/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095252/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1759644
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095260/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1759644
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095259/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095254/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095257/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095249/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Tags added: apport-collected
** Description changed:
After upgrade to 18.04 (bionic) I've encountered the following
regression: wired network connection does not work, when system is
resumed from suspend.
Reloading the kernel driver module seems to help:
sudo m
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095251/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
Looks like duplicate of https://bugs.launchpad.net/ubuntu/+source
/network-manager/+bug/1676547
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1687262
Title:
16.10, 17.04, 17.10 Wired co
@Joseph: no point, as indicated multiple times, network card works with
current kernel 4.12.0-13, when configured in /etc/network/interfaces
When similar was observed after upgrading of another system with completely
different hardware:
*-network DISABLED
description: Ethernet interface
** Tags removed: kernel-request-4.10.0-22.24
** Tags added: regression-release
** Description changed:
+ == Regression details ==
+ Discovered in version: yakkety
+ Last known good version: xenial
+
This is a regression.
Upon upgrading 16.04 -> 16.10. Wired connection provided by
"RTL81
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
** Summary changed:
- 16.10, 17.04 Wired connection stopped working RTL 8111/8168/8411
+ 16.10, 17.04, 17.10 Wired connection stopped working RTL 8111/8168/8411
** Tags added: artful
--
You received this bug notification because
Upgraded to artful beta - the issue persists.
$ lsb_release -a
LSB Version:
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:printing-9.20160110ubuntu5-amd64:printing-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
Distributor ID: Ubuntu
De
** Changed in: linux (Ubuntu Zesty)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1687262
Title:
16.10, 17.04 Wired connection stopped working RTL 81
Bug is still relevant.
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.04
Release:17.04
Codename: zesty
uname -a
Linux hosty 4.10.0-26-generic #30-Ubuntu SMP Tue Jun 27 09:30:12 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
$ apt-cache po
Live Ubuntu 17.04 session is running OK (mentioned in original report) and it
is using:
-
$ apt-cache-policy linux-image-generic
linux-image-generic:
Installed: 4.10.0.19.21
Candidate: 4.10.0.19.21
Version table:
*** 4.10.0.19.21 500
500 http://archiv
Public bug reported:
This is a regression.
Upon upgrading 16.04 -> 16.10. Wired connection provided by
"RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller" has stopped
working.
Quickly looked around for possible solution, and decided to go on with
upgrade to 17.04, since it was my initial
Yes. After re-install of grub kernel boots fine.
On Fri, Dec 2, 2016 at 5:19 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> Are you no longer having issues booting 4.4.0-51.72 after re-installing
> grub?
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => High
>
> **
Public bug reported:
After kernel upgrade system could not detect boot device anymore.
Right after BIOS the following was prompted:
Reboot and select proper Boot device
or Insert Boot Media in Selected Boot device and press a key
Problem was resolved (thanks to Eric^^ support at #ubuntu irc) by
48 matches
Mail list logo
