Public bug reported:
I believe this started with the upgrade from 5.0.0-15-generic to
5.0.0-16-generic.
I'm running a ZFS RAID2 pool and one of the drives is faulted. I
rebooted under 5.0.0-16-generic and the pool won't import, even with
'-f'. zpool emits a kernel oops spa_load and any zfs tool
An additional patch has been identified that will be needed to solve
this issue.
https://github.com/torvalds/linux/commit/3c677d206210f53a4be972211066c0f1cd47fe12
#diff-083bf3d2f128b616e730b7f9f8fc65c4
--
You received this bug notification because you are a member of Kernel
Packages, which is su
Public bug reported:
I just set up a new computer to back up some files to a ZFS mirror on
external USB3 drives.
I'm booting off of NVMe, with four older sata hard drives installed
internally (each with a single NTFS partition), and 3 external USB3
drives (each set as part of a 3 way mirror in ZF
After rebooting, I'm still getting errors, even some time after boot.
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863385/+attachment/5328292/+files/dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is
Still an issue after doing a full apt upgrade.
5.3.0-29-generic
--
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/1863385
Title:
System is generally unstable with amdgpu errors in syslog
Both of these patches are in Focal so I am going to close this bug
** Changed in: dell-poweredge
Status: New => Fix Released
--
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/1794110
4 of the 5 patches are in Focal. The final patch is not
PCI: pciehp: Differentiate between surprise and safe removal
https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git/commit/?h=pci/hotplug&id=e76ac5875f5d5848558edc79a0869bf20765fec3
The link to this patch currently has the followi
I think this is fixed based on the status of bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811785. I will
wait to close this bug until I can verify the fix in focal.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubu
Hi Sumit,
Can you test this in proposed, it is available now in 5.4.0-23.27
https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/proposed?field.series_filter=focal
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed.
Thank you,
Michael
,
Michael
--
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/1863574
Title:
Update mpt3sas Driver to 33.100.00.00 for Ubuntu 20.04
Status in linux package in Ubuntu:
Fix Committed
Status in
I have tested this in proposed.
** Tags added: verification-done-focal
--
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/1863581
Title:
Ubuntu 20.04: megaraid_sas driver update to version
** Tags added: verification-done-focal
--
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/1863574
Title:
Update mpt3sas Driver to 33.100.00.00 for Ubuntu 20.04
Status in linux package in Ub
For what it is worth, I have a kernel issue that appears after upgrading from
4.15.0-88 to 4.15.0-91 and it still is present in 4.15.0-96.
For my system the kernel does not panic, however it eventually starts erroring
and then mounts /tmp as ro.
If I reboot in maintenance mode fsck the disk, fi
I can confirm that this is now fixed for me on Ubuntu 18.04.4 LTS with
kernel 5.3.0-46-generic. With this kernel, my Dell Latitude E5470 with a
i5-6440HQ now consumes about 4W in idle instead of 9.W as before.
Thanks a lot!
--
You received this bug notification because you are a member of Kernel
I just tested rc4, and now I can no longer log in; same as with rc2. So
to summarize, I cannot get past the login screen with versions rc2 and
rc4, whereas I could with rc3
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
I just tested the latest kernel, and it is worse. This time it didn't
even make it to the login screen, and I let it run for 5 minutes. dmesg
from that boot attempt is attached.
Given the lack of success at booting kernels from 5.3 - 5.7, I'm
wondering whether this 2015 iMac is going to be a viabl
apport information
** Tags added: apport-collected
** Description changed:
I am encountering some very bizarre and difficult to reliably replicate
issues.
I am using a Focusrite Scarlett 2i2 USB audio interface, and am having a
number of issues that I did not have in older version of
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1877887/+attachment/5369867/+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/1877887
apport information
** Attachment added: "AudioDevicesInUse.txt"
https://bugs.launchpad.net/bugs/1877887/+attachment/5369862/+files/AudioDevicesInUse.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1877887/+attachment/5369863/+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/1877887
Ti
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1877887/+attachment/5369868/+files/Lsusb-t.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/1877
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1877887/+attachment/5369865/+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/1877887
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1877887/+attachment/5369864/+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
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1877887/+attachment/5369866/+files/Lspci-vt.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/18
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1877887/+attachment/5369874/+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: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1877887/+attachment/5369871/+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: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1877887/+attachment/5369869/+files/Lsusb-v.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/1877
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1877887/+attachment/5369870/+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/1877887/+attachment/5369873/+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: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1877887/+attachment/5369872/+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: "PulseList.txt"
https://bugs.launchpad.net/bugs/1877887/+attachment/5369875/+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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1877887/+attachment/5369876/+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/1877887
> Does using the snd_hda_intel.power_save=0 kernel option makes a
difference to the sound cracking issue?
(https://wiki.ubuntu.com/Kernel/KernelBootParameters).
It does not appear to make a difference.
> Also by USB suspend do you mean btusb.enable_autosuspend=y/n ?
I set usbcore.autosuspend=-1
** Description changed:
I am encountering some very bizarre and difficult to reliably replicate
issues.
I am using a Focusrite Scarlett 2i2 USB audio interface, and am having a
number of issues that I did not have in older version of ubuntu (these
issues started occuring sometime in 1
An update, after about a day of uptime with usb autosuspend DISABLED I
have encountered this same issue. This time the issue occured when
launching a game, however usually it just randomly fails.
I have attached the dmesg log, at the end I disconnected and reconnected
the usb interface but it does
forgot to add, after the issue occurred, I unplugged and replugged the
usb audio interface and as expected it did not power back on. This
should be contained within the log output I attached in the last
comment.
--
You received this bug notification because you are a member of Kernel
Packages, wh
I have added these parameters and by way of luck the issue happened soon
after rebooting. I attached the last 16MB of syslog (as the whole thing
was several GB by this point).
I also had some luck with hooking it to my powered USB 3.0 hub instead
of the 2.0 port on my motherboard, however I didn't
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1875884/+attachment/5370860/+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
** Tags added: apport-collected
** Description changed:
OS provided by AKS is currently Ubuntu 16.04.6 LTS, kernel
4.15.0-1077-azure.
Every block written by a k8s pod to a ceph CSI volume generates 2 warning
lines in the node's system logs (kern.log, syslog, messages
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1875884/+attachment/5370857/+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/1875884
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1875884/+attachment/5370856/+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
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1875884/+attachment/5370862/+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/1875884
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1875884/+attachment/5370859/+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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1875884/+attachment/5370858/+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: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1875884/+attachment/5370861/+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: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1875884/+attachment/5370863/+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
I obeyed the bot and ran the collector. Dunno if I need to mess with the bug
state, as it looks like "Confirmed" expects someone other than the reporter
(that's me), and the more targeted sub-bug is still in "New".
Let me know if I need to do anything else.
--
You received this bug notification
** Changed in: snapd
Status: New => Invalid
** Changed in: snapd
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1878432
Title:
rpi3a+ do
> 0x202a0 means it's no longer connected. This can be a hardware or
firmware bug.
I believe this is to be expected. I unplugged the device at this point
to show that plugging it back in does not fix the problem. If you keep
going down you will see it flounder when I attempt to reconnect the
device
Okay, I have updated to the latest mainline kernel. If it manages to
hold steady the next few days I'll go ahead and close this issue.
--
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/1877887
Unfortunately it seems to still be producing the same issue as before on
the latest kernel. Is it possible for this to be hardware failure? It
doesn't make a whole lot of sense as the issue persist even when
reconnecting the device and it works fine with a reboot. I've also
noticed that it most com
After some testing on older kernels I was indeed able to recreate these
issues. The only thing I can think of is that somehow the hardware has
partially degraded such that it causes some issues with however the
drivers are implemented in linux but not in windows. I think it may have
something to do
** Changed in: snapd
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1878432
Title:
rpi3a+ does not boot with core20
Status in pi2-kernel-sna
Public bug reported:
The boot on real HW (ARock B450, Ryzen, NVME 240Gb) takes a long time
without any visible feedback.
Video: https://photos.app.goo.gl/RmaLviXNorjeh5BP7
With grub debug: https://photos.app.goo.gl/PJuXdxp8uedr7fWp9
(google photos has degraded quality quite a bit, may upload the
** Package changed: linux-raspi (Ubuntu) => snapd (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1879290
Title:
pc: no message on the screen for ~30s on fast HW
Status in
I booted into Ubuntu 18.04 with a 4.15 kernel and had similar issues. It
has been running steady for several days now off the powered USB hub
though so I'm pretty satisfied.
It doesn't seem like that change is relevant to this issue, although
seeing as this particular interface is somewhat common
*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794
same issue here with a freeVoice headset.
as soon as I switch to hsp/hfp mode audio stops working.
funny enough the beeps while changing sound volume are hearable
--
You received this bug notification beca
Based on Daves comment I set this to invalid.
** Changed in: linux-raspi (Ubuntu Focal)
Status: New => Invalid
** Changed in: linux-raspi (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794
I fixed the problem for my laptop.
it looks like its a configuration issue in /etc/pulse/default.pa file.
I simply made a diff with a previous ubuntu version aka 19.10 and adjust the
config (I copied the co
*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794
@David is it sustainable in your case and works also after a power down of the
machine?
unfortunately, in my case it only works when I first boot ubuntu 19.10 via live
iso and reboot into installed ubuntu
This one is a bit of an improvement. Boot time to a working desktop was
about 3 minutes. But most interesting was that I could change my display
resolution almost instantly with a 200% magnification. Attempting to
change by adjusting the resolution directly (from 3840x2160 to
2560x1440) caused the
I also tried fractional scaling; got the same delay. And when I tried
adjusting the resolution to 1920x1080 directly with the resolution
setting instead of 200% magnification, I got the delay again. So the
only fast adjustment is with magnification and no fractional scaling.
Attached is the System
@advadrako would you mind sharing that file?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1859754
Title:
add ucm to make alsa/sof driver work under PA (variants of Lenovo X1
Carbo
@hui.wang Looks good here:
michael@metalmachine:~$ cat /sys/devices/virtual/dmi/id/bios_version
N2HET46W (1.29 )
michael@metalmachine:~$
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs
Looks good so far; with kernel 5.3.0-43 from proposed and the libasound2
from your ppa.
Microphone selection seems to be a bit iffy when I have a headset
plugged into the headset jack (both are available to select, and the
default seems to be the built-in one) but otherwise good.
--
You received
wever
while debugging/fixing this issue I was wondering if it would be
possible to backport the new jitter entropy patches from kernel 5.4 [1]
to the older LTS kernels.
Thanks,
Michael
[0] https://bugs.launchpad.net/plano/+bug/1866940
[1] https://lwn.net/Articles/802360/
** Affects: linux (U
Hi Sumit,
I have placed the test kernels at the following link can you please test
it?
https://people.canonical.com/~mreed/lp1863581_megaraid_sas/
Regards,
Michael
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
ugh entropy available. Snapd is using
entropy to init it's CRNG and a change in snapd broke the boot.
However while debugging/fixing this issue I was wondering if it would
be possible to backport the new jitter entropy patches from kernel 5.4
[1] to the older LTS kernels.
Thanks,
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Assignee: Michael Reed (mreed8855)
Status: In Progress
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Assignee: Michael Reed (mreed8855)
Status: In Progress
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which
** Description changed:
[IMPACT]
- This is a feature request to update megaraid_sas driver in Ubuntu 20.04
release to latest Linux upstream tip.
+ This is a feature request to update megaraid_sas driver in Ubuntu 20.04
release to latest Linux upstream tip.
The current latest upstream megar
Hi Sumit,
Have you had a chance to test this yet?
Regards,
Michael
--
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/1863581
Title:
Ubuntu 20.04: megaraid_sas driver update to version
** Tags added: focal hwcert-server
--
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/1863574
Title:
Update mpt3sas Driver to 33.100.00.00 for Ubuntu 20.04
Status in linux package in Ubuntu
** Tags added: hwcert-server
--
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/1863581
Title:
Ubuntu 20.04: megaraid_sas driver update to version 07.713.01.00-rc1
Status in linux package i
** Description changed:
- apt install ubuntu-desktop on Servers with embedded Matrox G200 Graphics
Controller issue
+ apt install ubuntu-desktop on Servers with embedded Matrox G200 Graphics
+ Controller issue
+
After install/reboot there is no gdm login displayed
Editing /etc/gdm3/custom.co
** Changed in: snapd
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1868894
Title:
[uc18] docker overlayfs* seems broken
Status in snapd:
Tri
Hi Sumit,
Any updates in regards, to testing?
Regards,
Michael
--
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/1863581
Title:
Ubuntu 20.04: megaraid_sas driver update to version
*** This bug is a duplicate of bug 1850654 ***
https://bugs.launchpad.net/bugs/1850654
** This bug has been marked a duplicate of bug 1850654
update-initramfs complains of missing amdgpu firmware files
--
You received this bug notification because you are a member of Kernel
Packages, whic
*** This bug is a duplicate of bug 1853044 ***
https://bugs.launchpad.net/bugs/1853044
** This bug has been marked a duplicate of bug 1853044
5.3.0-23-generic causes fans to spin when idle
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
Hi,
happy to see that this regression is addressed in newer Ubuntu releases!
Will this fix be backported to the 5.3.0 series used in Ubuntu 18.04.4?
I was previously running Ubuntu 18.04; then reinstalled to 18.04.4 and
was very surprised to find my time on battery was *cut by half*.
I would ad
I just want to add my comment as well.
With hddtemp I get the following:
/dev/sdc: KINGSTON SA400S37240G: 33°C
With smartctl I get the following:
194 Temperature_Celsius 0x0023 067 054 000Pre-fail Always
- 33 (Min/Max 20/46)
231 Temperature_Celsius 0x0013 100 1
Public bug reported:
I upgraded a Ubuntu 18.04 installation to 20.04 beta on my late 2015 5k
27" iMac. The new 5.4 kernel was installed and has been updated a few
times. The former LTS kernel (4.15) was retained. When I start up the
computer with the new kernel, the process is very slow and it tak
Thanks for the quick reply. I installed and tested 5.7-rc2 as per
instructions. The new kernel booted up to the login screen, but as
slowly as 5.4.0-25. (Over 2 minutes to the login screen.) When I logged
in with my password, all that happened was that I was returned to the
login screen. I tried lo
I hope this is what you were looking for. In your message, you noted
that the login bug is likely a separate issue and it could be reported
as new. I thought that this is what I already did. If not, should I
report it again? And with what attachments? Thanks.
** Attachment added: "dmesg.0"
htt
For me the problem is not fixed.
See my report here: https://ubuntuforums.org/showthread.php?t=2441385
It seems the PHY for my Realtek ethernet chip is not activated in the boot up
process.
I have to locally log in and enter "dhclient enp2s0" to get the interface
running. Only then the "PHY" sho
Next, a dmesg for that boot. Not sure which it is so I'll send two.
** Attachment added: "dmesg for 5.3 boot (I hope)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359502/+files/dmesg
--
You received this bug notification because you are a member of Kernel
Packag
I uninstalled Virtualbox and tested kernels 5.1 and 5.2. Both showed
fast boots similar to 4.15. I then tested 5.3 by downloading it from the
ppa/mailine. This is where the slow boot started. I have attached two
dmesg's and a systemd analysis of the critical chain and blame for
kernel 5.3. I can't
Next, dmesg.0
** Attachment added: "dmesg.0 for 5.3 boot (I hope)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359503/+files/dmesg.0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
Next is the first of two dmesg logs for the 5.2 kernel.
** Attachment added: "dmesg for 5.2 boot (I hope)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359510/+files/dmesg
--
You received this bug notification because you are a member of Kernel
Packages, which is
Finally, a second dmesg for the 5.2 kernel boot.(I'm not sure whether
dmesg or dmesg.0 is the right one.
** Attachment added: "dmesg.0 for 5.2 boot (I hope)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359527/+files/dmesg.0
--
You received this bug notification
This time with the last fast kernel, 5.2. The bootup was slightly slower
than with 4.15, but I think this might relate to snap module loading. I
should also point out that the difference between kernels 4.15, 5.1 and
5.2 vs the kernels after 5.3 is more than what is indicated by the
SystemD analysi
I could figure out "my" problem:
https://ubuntuforums.org/showthread.php?t=2441385
somehow the network device name seems to have changed form enp3s0 as written in
the /etc/netplan/00-installer-config.yaml config file to enp2s0. Then, my
network was not activated at boot-up any more.
--
You rec
I did the bisection and found that the bad kernels started at 5.3-rc1.
The last 5.2 kernel, 5.2.21, was good. I have attached the SystemD
analysis here of the boots of both kernels. You can see from it that the
problem in rc1 is related to the gpu-manager service.
I will attach the dmesg log of th
Here is the dmesg log for the bad boot of 5.3-rc1.
** Attachment added: "Log of 5.3-rc1 kernel boot"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359789/+files/dmesg.0
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
I should add that I tested kernels 5.2.15, 5.2.18 and 5.2.20 as well.
All were OK, so the good-bad line is clearly after 5.2.21.
--
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/1874104
Titl
It is possible to login with kernel 5.6. The bootup is slow, but it does
boot and gets past the login screen. I have attached the dmesg from that
boot, and will send the systemd analysis in the next message.
** Attachment added: "dmesg.0 for 5.6 boot"
https://bugs.launchpad.net/ubuntu/+source/
Attached is the SystemD analysis for the 5.6 boot. It looks pretty
similar to that of all the kernels I have tried that are 5.3 or newer.
** Attachment added: "SystemD critical chain and blame outputs: 5.6 kernel"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5360469
I will report the login bug as a new one. As far as bisection past
identifying the line of progression to identify the last kernel that
works and the first one that doesn't, I looked at the further steps one
would have to take and I don't think that my technical capability is up
to it. I have never
I forgot to send you the proper dmesg for the boot of kernel 5.3rc-1. It
is attached. This kernel was not only slow, but it didn't pick up my
wireless card. This was the only kernel I tried that did this.
** Attachment added: "dmesg for 5.3rc1 boot"
https://bugs.launchpad.net/ubuntu/+source/li
Instructions were to include information from About in Settings.
Screenshot attached.
** Attachment added: "About my late 2015 27" iMac with the kernel booting
issues"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875211/+attachment/5360987/+files/About%20my%20computer.png
--
You re
401 - 500 of 2450 matches
Mail list logo
