** Package changed: linux (Ubuntu) => console-setup (Ubuntu)
--
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/1880266
Title:
console-setup defaults prevent using automatic highdpi fonts
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1880266
and then change the status of the bug to 'Confirmed'.
If, due to the
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
console-setup defaults prevent using automatic highdpi fonts
Kernel has built-in Terminus fonts, at multiple sizes, and it picks font
based on screen resolution, including selecting high-dpi version of the
font.
The autogenerated default of FONTFACE=VGA and FONTSIZE=16 for
** This bug is no longer a duplicate of bug 1879939
Audio stopped working after 5.4.0-31 kernel update
--
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/1879760
Title:
PCI/internal
*** This bug is a duplicate of bug 1876065 ***
https://bugs.launchpad.net/bugs/1876065
** This bug is no longer a duplicate of bug 1879939
Audio stopped working after 5.4.0-31 kernel update
** This bug has been marked a duplicate of bug 1876065
After unplug headphones and plug them
Odd Behavior of this Bug:
1. The audio device is not detected (not by gnome and not by lshw -C
multimedia) and won't play sounds unless it's the "bell" from the
terminal.
2. If headphones are plugged in, there won't be an detected audio device
but lightly distorted sound is played thru
*** This bug is a duplicate of bug 1876065 ***
https://bugs.launchpad.net/bugs/1876065
** This bug is no longer a duplicate of bug 1875252
Ubuntu 20.04 LTS update causing no sound coming from built-in speakers
** This bug has been marked a duplicate of bug 1876065
After unplug
*** This bug is a duplicate of bug 1876065 ***
https://bugs.launchpad.net/bugs/1876065
** This bug has been marked a duplicate of bug 1876065
After unplug headphones and plug them again no sound can be heard
--
You received this bug notification because you are a member of Kernel
*** This bug is a duplicate of bug 1879939 ***
https://bugs.launchpad.net/bugs/1879939
** This bug has been marked a duplicate of bug 1879939
Audio stopped working after 5.4.0-31 kernel update
--
You received this bug notification because you are a member of Kernel
Packages, which is
Hi Hui Wang,
5.4.0-33 is installed on my machines and nothing was fixed. Please keep an eye
on this bug.
--
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/1879939
Title:
Audio stopped
*** This bug is a duplicate of bug 1879939 ***
https://bugs.launchpad.net/bugs/1879939
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879939/comments/3
Mentions, that Kernel 5.4.0-32 is going to fix the problem, which is not
right. 5.4.0-33 still has the problem.
** This bug has been
*** This bug is a duplicate of bug 1879939 ***
https://bugs.launchpad.net/bugs/1879939
Judging on the described behaviour this Bug also is present in Ubuntu 14.04
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879869
--
You received this bug notification because you are a
1) No, it is not appropriate to test a non LTS kernel on a LTS
distribution.
2) I did you a favor and tested on the previous LTS kernel (linux-
image-5.4.0-28-generic) and the latest LTS kernel (linux-
image-5.4.0-31-generic) and could not reproduce on either after running
dd 3-5 times on each.
New images do not appear to be available quite yet, still getting the
May 18 image.
$ vagrant box update
==> default: Checking for updates to 'ubuntu/focal64'
default: Latest installed version: 20200518.0.0
default: Version constraints:
default: Provider: virtualbox
==> default: Box
** Tags added: rls-gg-incoming
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in grub2 package in Ubuntu:
Won't Fix
Status
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-raspi2 (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-raspi2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
Attaching ubuntu-style information for the case that works fine where
the laptop was booted from the Live-USB.
** Attachment added: "ubuntu-bug style info when fan works fine booting with
Live-USB"
The fan is working when booting with the Live-USB I used to install
Ubuntu 20.04
The Linux kernel from the Live-USB is
Linux ubuntu 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux
in case it makes any difference.
--
You received this bug notification
*** This bug is a duplicate of bug 1880012 ***
https://bugs.launchpad.net/bugs/1880012
I'm sorry filing this bug automatically (from Ubuntu 20.04 LTS Live-USB) has
failed since no technical information was joined.
So I'd like to remove this bug.
** Changed in: linux (Ubuntu)
Status:
*** This bug is a duplicate of bug 1880012 ***
https://bugs.launchpad.net/bugs/1880012
I'm going to immediately link the present bug report to bug #1880012 and
mark the current one as duplicate. The only purpose of the current bug
report is to provide more information for bug #1880012. Sorry
*** This bug is a duplicate of bug 1880012 ***
https://bugs.launchpad.net/bugs/1880012
Public bug reported:
The attached logs correspond to booting the same ASUS UX533FN laptop,
but this time using the Ubuntu 20.04 live-USB that was used to install
Ubuntu 20.04 in the first place.
Here,
It was not fixed, in the 5.3.0-53 kernel !!! In the 5.7.0-994 kernel it
is functional, but in the previous one it is not
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: thermald (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1874933
Title:
Performance workaround for Dell 7390
systemd debdiff with a fix to skip creating /dev/disk/by-uuid for bcache
backing, caching devices.
** Patch added: "lp1861941-skip-bcache-links.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+attachment/5375730/+files/lp1861941-skip-bcache-links.debdiff
--
You
debdiff of the changes
** Attachment added: "bcache-tools-debdiff-1.0.8-4_to_1.0.8-4ubuntu1"
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1861941/+attachment/5375722/+files/bcache-tools-debdiff-1.0.8-4_to_1.0.8-4ubuntu1
--
You received this bug notification because you are a
Updated test to be a bit more resilient.
** Attachment added: "test-bcache-byuuid-links-fixed.sh"
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1861941/+attachment/5375723/+files/test-bcache-byuuid-links-fixed.sh
--
You received this bug notification because you are a member
Agreed
--
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/1853044
Title:
5.3.0-23-generic causes fans to spin when idle
Status in linux package in Ubuntu:
Fix Released
Status in linux
Tarball of a source package with a fix for this issue:
bcache-tools_1.0.8.orig.tar.gz
bcache-tools_1.0.8-4ubuntu1_amd64.build
bcache-tools_1.0.8-4ubuntu1_amd64.buildinfo
bcache-tools_1.0.8-4ubuntu1_amd64.changes
bcache-tools_1.0.8-4ubuntu1_amd64.deb
bcache-tools_1.0.8-4ubuntu1.debian.tar.xz
*** This bug is a duplicate of bug 1573095 ***
https://bugs.launchpad.net/bugs/1573095
Eric, I'll close this LP as dup of #1879987 - seems it's the same issue.
I'll try also the Debian release top see what's different there...we can
comment in the other bug about Debian status and what are
*** This bug is a duplicate of bug 1573095 ***
https://bugs.launchpad.net/bugs/1573095
Sorry, dup of LP #1573095.
** This bug has been marked a duplicate of bug 1573095
Cloud images fail to boot when a serial port is not available
--
You received this bug notification because you are a
It's still very slow. When I don't attach a serial device like you gave
an example for to the virtualbox, it still has that 90s pause between
mentioned 'printk' lines during booting and booting is slow in general.
When I do attach the serial device, it still panics the first time, but
the whole
Unfortunately this bug is back with linux-5.3.0-53.47.
It got reintroduced somewhere between linux-5.3.0-53.47 and 5.3.0-51.44.
System is Dell XPS 9550 with Skylake HD Graphics 530.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Additional conversations for the bug are happening in bug 1874544
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1856375
Title:
[linux-azure] Request to autoload mlx4/mlx5 modules
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Vagrant boxes with updated kernels have been pushed. My current tests
are showing boot times in the 30s range.
Could folks commenting on slow boot speeds in Focal and Eoan please run
a `vagrant box update` on their current setups?
Focal and Eoan boxes with the above kernels have been pushed to Vagrant
and verified. Please run a `vagrant box update` to get the latest
versions.
** Changed in: cloud-images
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Hi You-Sheng Yang,
I appreciate that you took the effort to fix this bug. Unfortunately, I
don't have Ubuntu 20.04 installed in my system as I needed wifi urgently
which made me switch to Ubuntu 18.04 LTS. For the time being, unless
someone faces the same problem, I request that you can close the
I'm several steps down the bisect at this point and have overcome
several compilation issues along the way (old kernels won't compile with
gcc-9, so installed gcc-8, patched around an issue building with newer
headers,
Thanks, this eliminated the problem.
The only unexplained thing is what was the urge to break the "old" package
which perfectly worked before. If Ubuntu planned to reorder/restructure package
names, the reasonable way would be to turn 'bcmwl-kernel-source' into a
dummy/transitional package
OK.
I've reviewed the kernel code, and there are no unexpected changes w.r.t
the CACHED_UUID change event. So I don't think we will need any kernel
changes which is good.
With the small change to the 60-persistent-storage.rules to not attempt
to create a /dev/disk/by-uuid symlink for the
I see this when running sudo apt dist-upgrade.
$ uname -a
Linux andradeii 5.4.0-7629-generic #33~1589834512~20.04~ff6e79e-Ubuntu
SMP Mon May 18 23:29:32 UTC x86_64 x86_64 x86_64 GNU/Linux
$ sudo apt dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state
My bad. Looks like 5.4.0-32 never made it out of -proposed.
--
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/1879690
Title:
Docker registry doesn't stay up and keeps restarting
Status in
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1880213
and then change the status of the bug to 'Confirmed'.
If, due to the
It's the same upstream patchlevel as the previous kernel:
$ cat /proc/version_signature
Ubuntu 5.4.0-31.35-generic 5.4.34
--
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/1879690
Title:
@Hui,
Thank you for looking deeper into the problem, and for your explanation.
I tried disconnecting and reconnecting the speaker to the audio output
jack as you suggested, however it did not change the behavior. The
'Dummy Output' remains, and no sound is heard.
@Kai, I added the PPA you
Public bug reported:
[Impact]
Build failure when building ext2
fs/ext2/xattr.c:828:18: error: 'ext2_xattr_cache' undeclared (first use in this
function)
atomic_read(_xattr_cache->c_entry_count));
[Fix]
The fix is upstream commit 32302085a8d90859c40cf1a5e8313f575d06ec75 "ext2: fix
debug
** Changed in: cloud-images
Assignee: (unassigned) => John Chittum (jchittum)
--
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/1873506
Title:
ubuntu/focal64 fails to mount Vagrant
Same issue on XPS 9560, 8GB USB stick. Created in Rufus from
ubuntu-20.04-desktop-amd64.iso, both ISO and DD mode behave the same.
Can't install 20.04 as a result. No way to collect the logs, because the
laptop shuts down after disks checks and there is no interaction other
than Ctrl+C to cancel
I don't believe so as I am able to discover SCSI devices on my Emulex
fabric-attached, Emulex direct-connect, and Qlogic fabric-attached hosts
before starting this test.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I believe it's a bug with the inbox Qlogic driver
--
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/1860724
Title:
QLogic Direct-Connect host can't discover SCSI-FC or NVMe/FC devices
Test kernel has been tested successfully so far by
original reporter and has fixed the Docker breakage
and so on.
--
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/1879658
Title:
Cannot
a) When I do a short press, then immediately after a release, the next option
is selected (the dialog does not have time to appear even).
b) When I do a long press, then the options start to circle very quickly until
I release the key (see the screencast)
I think the bug is caused by this: When
Is this dupe of #1860724?
--
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/1867686
Title:
FC hosts become unresponsive during array upgrade
Status in linux package in Ubuntu:
Confirmed
I've never used a complex setup like this, so I have to ask, are we sure
it's kernel bug?
--
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/1860724
Title:
QLogic Direct-Connect host can't
@kaihengfeng, not sure how to capture dmesg, as the boot process never
completes preventing me from accessing a command line. Also, I am
unable to switch to another TTY session. Can you please provide guidance
or direct me to a article that explains how to capture the log?
--
You received this
I am still seeing this with Ubuntu 20.04 LTS
--
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/1860724
Title:
QLogic Direct-Connect host can't discover SCSI-FC or NVMe/FC devices
Status
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
It still crashes on 5.4.0-31-generic #35-Ubuntu
I'm still looking for that damm __i915_schedule+0x261/0x350, still
haven't been able to pinpoint that to code.
[ 9640.917215] BUG: kernel NULL pointer dereference, address: 00e0
[ 9640.917262] #PF: supervisor read access in kernel mode
OK, I've installed those (at first I kept trying and failing to install
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc5/linux-image-
unsigned-5.7.0-050700rc5-generic_5.7.0-050700rc5.202005101931_amd64.deb
, but it worked once I installed https://kernel.ubuntu.com/~kernel-
"pcie_aspm=off" on grub or enter the console don't help.
--
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/1865471
Title:
USB 3.1 Gen 1 not work after using suspend
Status in linux
I have the same problem on 20.04 on a ThinkPad P50.
It started when I upgrade from 19.10. It started after some time of being
running.
I did a new installation of the 20.04 and the problem persists but now only
after wake up and if I put it to sleep and wake up again it stops.
--
You received
I noticed something unexpected with the kernel in -proposed:
/proc/version_signature reverts the upstream patchlevel to 5.4.34. If
there's a mistake and it's really reverting all the upstream SRU
patches, I may have a problem.
--
You received this bug notification because you are a member of
I installed
linux-modules-5.7.0-994-generic_5.7.0-994.202005192206_amd64.deb
then
linux-image-unsigned-5.7.0-994-generic_5.7.0-994.202005192206_amd64.deb
(because of dependency, has to be that order), and then rebooted and
selected the 994 version (I have vmlinuz-5.3.0-51-generic as
https://lists.ubuntu.com/archives/kernel-team/2020-May/110153.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1876165
Title:
Binder and ashmem drivers are missing from AWS
I am still affected by this bug on focal with intel gpu/hda on kernel
5.4.0-26
Adding the value to /etc/modprobe.d/alsa-base.conf does not help me
Linux Ashen-One 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux
➜ ~ lspci -v
00:00.0 Host bridge: Intel
I tested with debian buster and I wasn't able to reproduce (w/o quiet
parameter)
I'm not yet too sure if it's a pure initramfs-tools or something
introduced by a package hooks.
I first thought that plymouth could have beeb a potential candidate, but
I disabled it and even purge it and problem
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => Fix Committed
--
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/1861284
Title:
Build and ship a signed wireguard.ko
Status
** Changed in: linux (Ubuntu Eoan)
Assignee: (unassigned) => Andy Whitcroft (apw)
--
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/1861284
Title:
Build and ship a signed wireguard.ko
I installed both of the packages in reverse order due to dependencies. On
reboot, the screen behaved the same, hanging with a white background. The
latest boot log is attached.
Thanks for the continued effort.
** Attachment added: "vmlinuz-5.7.0-994-generic boot.log"
This needs to be enabled for {eoan,focal}/linux-aws, and then for the
bionic/linux-aws-5.3 and bionic/linux-aws-5.4 derivatives.
** No longer affects: linux-aws (Ubuntu Bionic)
** Summary changed:
- Binder and ashmem drivers are missing from aws-edge kernel
+ Binder and ashmem drivers are
** No longer affects: linux-raspi2 (Ubuntu Focal)
--
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/1878377
Title:
USB keyboard doesn't work with rpi3 (armhf)
Status in
** Also affects: linux-aws (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux-aws (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux-aws (Ubuntu Bionic)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
--
You received this bug
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Eoan)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Please follow this one:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877871/comments/8
--
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/1879185
Title:
fails with kernel 5.3 on
There are two things:
- On servers, ubuntu-server depends on mdadm, so removing mdadm also
removes ubuntu-server package, which means it's not really supported
- In general, the installers don't offer installing like that.
I don't know why we did not have a task for xenial.
** Description
Sorry, I didn't actually test Focal and Groovy.
Xenial will be supported for about a year, so I think it worth to fix it
there as well; however it's relative what worth to fix and what not, as
most users probably left Xenial behind already or applied a workaround
if they were ever affected by
I'm running Linux Mint 19.3 Mate. I'm willing to put up a VirtualBox VM in
20.04,
but really can't do a reinstall right now, as there's about a weeks' worth of
custom updates. (I write application software for numerical stuff, but can't
pretend knowledge of kernel / module level stuff.)
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1880103/+attachment/5375616/+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/1880103
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1880103/+attachment/5375617/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1880103/+attachment/5375619/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1880103/+attachment/5375620/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1880103/+attachment/5375614/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1880103/+attachment/5375621/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1880103/+attachment/5375623/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1880103/+attachment/5375622/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1880103/+attachment/5375613/+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/1880103
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1880103/+attachment/5375624/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1880103/+attachment/5375618/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/2020-05-20/
Download and install the following deb:
linux-image-unsigned-5.7.0-994-generic_5.7.0-994.202005192206_amd64.deb
linux-modules-5.7.0-994-generic_5.7.0-994.202005192206_amd64.deb
--
You received this bug notification because
apport information
** Tags added: apport-collected tessa
** Description changed:
- 101 kernel seems to be better than 99, when the problem happened almost
- every time. Nevertheless, it happened again with 2+days uptime and
- suspending over night. Maybe it depends on my wireless keyboard? I
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1880103/+attachment/5375615/+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/1880103
Hmm, could you please try 20.04?
I wonder how you made rootfs Btrfs?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc6/
If latest kernel doesn't work then we need to do kernel bisection...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag
Disable misbehaved ACPI GPE as a temporary workaround:
https://unix.stackexchange.com/questions/242013/disable-gpe-acpi-interrupts-on-boot
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages,
Did it happen under 19.10?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
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/1878918
Title:
Button power don’t
Did this issue happen to 16.04.1?
--
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/1878919
Title:
kworker/0:1+kacpid uses 100% of one CPU core
Status in linux package in Ubuntu:
1 - 100 of 149 matches
Mail list logo
