Public bug reported:
Some architectures get "link_in_boot = yes" added to /etc/kernel-
img.conf by lb_chroot_linux-image; it appears that cloud images built
for these architectures (I have checked s390x and arm64) end up with an
LZMA-compressed empty regular file at /boot/initrd.img (instead of
It looks like this file is created by live-build/scripts/build
/lb_chroot_linux-image:
cat > chroot/etc/kernel-img.conf << EOF
# Kernel Image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
EOF
case "${LB_ARCHITECTURES}" in
I have tested all of the above cases with the cloud-init from -proposed
and it behaved as expected.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in
** Description changed:
On Azure, cloud-init relies on the system-uuid as based by SMBIOS a
unique ID for a cloud instance. If this ID ever changes, then cloud-
init will attempt to reprovision the VM.
- This recent kernel patch in the Ubuntu kernel corrects the endianness
- for some
Attached is a debdiff for trusty (the only affected version).
** Patch added: "lp1551419.debdiff"
https://bugs.launchpad.net/ubuntu/vivid/+source/cloud-init/+bug/1551419/+attachment/4587505/+files/lp1551419.debdiff
--
You received this bug notification because you are a member of Kernel
** Changed in: cloud-init (Ubuntu Trusty)
Status: New => In Progress
** Changed in: cloud-init (Ubuntu Trusty)
Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)
** Changed in: cloud-init (Ubuntu)
Status: In Progress => Invalid
** Changed in: cloud-ini
** Description changed:
On Azure, cloud-init relies on the system-uuid as based by SMBIOS a
unique ID for a cloud instance. If this ID ever changes, then cloud-
init will attempt to reprovision the VM.
This recent kernel patch in the Ubuntu kernel incorrectly modifies the
endianness
OK, I'm shifting this back to linux, because I think that the commit
that was backported is fixing a problem in a commit that _wasn't_
backported, therefore causing the issue. Here are the details:
In 95be58df7 [0], support for SMBIOS 3 was added, which introduces a
third version field (i.e.
Thanks to Steve Z for pointing out that it works in wily; that's what
sent me down this path.
It works in wily because wily _does_ have 95be58df7.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: cloud-init (Ubuntu)
Status: New => In Progress
--
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/1551419
Title:
Fix UUID endianness patch breaks cloud-init on Azure
will also trigger the behaviour seen in this bug.
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)
--
You received this bug notification because you are a member of Ker
** Changed in: cloud-images
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/1635223
Title:
please include mlx5_core modules in linux-image-generic
** No longer affects: cloud-images/x-series
** Changed in: cloud-images
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/1683878
Title:
blkfront: add
** No longer affects: cloud-images
--
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/1685406
Title:
ubuntu 82599 ixgbe driver has a bug,result in flow can't reach
10Gb,only 6.5Gb
Status
This does reproduce with the mainline kernel.
(Possibly worth noting that if I unplug/replug in the grub menu, the
keyboard works there _and_ once I get to the disk decryption step.)
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-bug-exists-upstream
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1723994/+attachment/4988007/+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: "RfKill.txt"
https://bugs.launchpad.net/bugs/1723994/+attachment/4988018/+files/RfKill.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: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1723994/+attachment/4988011/+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/1723994
apport information
** Tags added: apport-collected
** Description changed:
I have my external keyboard plugged in to my monitor's USB hub. Unless
I unplug and replug the USB cable that connects the monitor hub to my
machine, I can't use my keyboard on boot.
ProblemType: Bug
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1723994/+attachment/4988013/+files/ProcCpuinfoMinimal.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/1723994/+attachment/4988014/+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: "Lspci.txt"
https://bugs.launchpad.net/bugs/1723994/+attachment/4988010/+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/1723994
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1723994/+attachment/4988012/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1723994/+attachment/4988015/+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: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1723994/+attachment/4988016/+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: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1723994/+attachment/4988009/+files/JournalErrors.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: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1723994/+attachment/4988008/+files/IwConfig.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/1723994/+attachment/4988006/+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/1723994
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1723994/+attachment/4988020/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1723994/+attachment/4988017/+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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1723994/+attachment/4988019/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
On Tue, Oct 24, 2017 at 03:43:38AM -, Kai-Heng Feng wrote:
> Does this happen on older kernel or earlier Ubuntu releases?
This has been happening for the last six months, but I didn't have this
setup before then.
--
You received this bug notification because you are a member of Kernel
We've only seen this on m1.small instances, but we haven't tested
exhaustively (we do know, though, that m3.large is fine).
The command used to create the instance was:
aws --profile=china --region=cn-north-1 ec2 run-instances --key-
name=Odd_Bloke --image-id=ami-8fcd13e2 --security-groups
Public bug reported:
We're observing the following panic on boot when trying to boot an
m1.small in cn-north-1 (which is a region in AWS China):
[2.271681] Hardware name: Xen HVM domU, BIOS 3.4.3.amazon 11/11/2016
[2.271681] RIP: 0010:__xen_evtchn_do_upcall+0x24/0x80
[2.271681] RSP:
Public bug reported:
At my last reboot, I was prompted to enable SecureBoot, so I did.
When I booted, however, I noticed that the virtualbox service failed to
start because it couldn't load its kernel module. If I attempt the same
thing, I see that there's an issue with keys:
$ sudo modprobe
term.log for installation of my current kernel:
https://paste.ubuntu.com/p/3TVVFpFSNX/
term.log from the last time I see virtualbox DKMS stuff happening:
https://paste.ubuntu.com/p/7f7p6t48pn/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
I can confirm that the new module isn't signed at all:
$ hexdump -Cv /lib/modules/4.15.0-22-generic/updates/dkms/vboxdrv.ko | tail -n
100 | pastebinit
http://paste.ubuntu.com/p/BFSg9DsqR8/
Contrast with a previous kernel that was installed when virtualbox was
last upgraded:
$ hexdump -Cv
On Thu, Oct 26, 2017 at 07:38:58AM -, Kai-Heng Feng wrote:
> What's the output of `lsusb -t` with and without the monitor USB hub?
Without:
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
|__ Port 6:
On Thu, Oct 26, 2017 at 03:09:12PM -, Kai-Heng Feng wrote:
> They should work, at least at initramfs stage. You can use the keyboard
> to decrypt rootfs proves that.
I can use the keyboard to decrypt the rootfs if it's plugged in after
boot. If it's plugged in before boot, it doesn't work.
I've been seeing this issue for a while, but only just got around to
filing it. I'll test with the upstream kernel once I'm back at my desk.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: cloud-images
Status: Incomplete => 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/1626158
Title:
image won't boot after upgrading to yakkety's 4.8
** Changed in: cloud-images
Importance: Undecided => High
--
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/1726818
Title:
vagrant artful64 box filesystem too small
Status in
** Also affects: linux-kvm (Ubuntu)
Importance: Undecided
Status: New
--
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/1566468
Title:
systemd-modules-load.service: Failing due
Public bug reported:
On VMs launched in Azure, /dev/vmbus/hv_fcopy doesn't exist, so hv-
fcopy-daemon fails to start. This means that boot is degraded by
default:
$ systemctl list-units --failed --no-legend
hv-fcopy-daemon.service loaded failed failed Hyper-V File Copy Protocol Daemon
$
Hi John,
I've just tested with the latest Vagrant box, and this looks good to me
now:
$ vagrant box update
==> default: Checking for updates to 'ubuntu/cosmic64'
default: Latest installed version: 20181008.0.0
default: Version constraints:
default: Provider: virtualbox
==> default:
On Tue, Oct 16, 2018 at 12:20:21PM -, John Patrick wrote:
> Cheers all,
> Just updated myself and picked up '20181015.0.0' and vagrant up works cleanly.
> John
Great, thanks for the confirmation!
--
You received this bug notification because you are a member of Kernel
Packages, which is
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1796647/+attachment/5199144/+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/1796647
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1796647/+attachment/5199146/+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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1796647/+attachment/5199150/+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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1796647/+attachment/5199143/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 9 16:18 seq
crw-rw 1 root audio 116, 33 Oct 9 16:18 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
ArecordDevices: Error: [Errno
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1796647/+attachment/5199151/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/1796647/+attachment/5199145/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
+ In bionic, the vboxsf module was included in linux-modules-...-generic:
+
+ $ dpkg -c linux-modules-4.15.0-36-generic_4.15.0-36.39_amd64.deb | grep
vboxsf.ko
+ -rw-r--r-- root/root 63238 2018-09-24 10:08
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1796647/+attachment/5199147/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
My understanding of the issue after an IRC conversation with sforshee is
that the modules were intentionally dropped from the kernel packages,
but the corresponding Provides of virtualbox-guest-modules was _not_
dropped from the kernel packaging. This means that when we install
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1796647/+attachment/5199148/+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: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1796647/+attachment/5199149/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The box certainly needs to be fixed.
(In the meantime, a workaround if you _really_ need a cosmic box is
probably to manually install the virtualbox-guest-dkms package; I
haven't tested this locally though.)
--
You received this bug notification because you are a member of Kernel
Packages,
** Changed in: cloud-images
Status: Confirmed => 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/1726818
Title:
vagrant artful64 box filesystem too small
Status in
On disco, we're seeing the following in the cloud image testing:
Dec 17 19:37:43 jenk-ituzztgzwdxjesafyoft KVP: KVP starting; pid is:204
Dec 17 19:37:43 jenk-ituzztgzwdxjesafyoft KVP: open /dev/vmbus/hv_kvp failed;
error: 2 No such file or directory
Dec 17 19:37:43 jenk-ituzztgzwdxjesafyoft
This was from our test suite, so I don't have direct access to an
instance, but using the manifest, it is:
$ grep tools ~/manifest.txt
bcache-tools 1.0.8-3
dosfstools 4.1-2
initramfs-tools 0.131ubuntu15
initramfs-tools-bin
Yep, I have now done so:
$ ls -la /dev/vmbus/hv_kvp
crw--- 1 root root 10, 55 Dec 18 22:31 /dev/vmbus/hv_kvp
Joe, I've also imported your SSH keys in to ubuntu@test-
slgyvlgaldgcyzqkzuoz.cloudapp.net if there's any other poking around you
want to do.
--
You received this bug notification
On Wed, Dec 19, 2018 at 04:10:45PM -, Joseph Salisbury wrote:
> Are you able to manually able to start the daemon after seeing that the
> file exists?
Yes.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Jamie, are you using an ISO install or a cloud image for your test? I
was seeing this in a cloud image.
(When we were debugging on IRC, I recall that being a difference that
meant people couldn't reproduce.)
** Changed in: iptables (Ubuntu)
Status: Incomplete => New
--
You received
Added linux as there's a suspicion that this is a linux 5.0 regression,
as this only started appearing in our automated testing in the days
since that landed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
I hit this error on disco:
```
$ free -h
totalusedfree shared buff/cache available
Mem: 478Mi98Mi 311Mi 0.0Ki68Mi 366Mi
Swap:0B 0B 0B
$ sudo iptables -S
iptables
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1820114/+attachment/5246239/+files/ProcEnviron.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1820114/+attachment/5246238/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
I hit this error on disco:
```
$ free -h
totalusedfree shared buff/cache
available
Mem: 478Mi98Mi 311Mi 0.0Ki68Mi
366Mi
Hi Kai-Heng,
As an extra data point, when I attempted to boot the latest mainline
kernel for bug 1830910, it didn't fully boot but it did get far enough
to display the "kernel: xhci_hcd :07:00.2: can't setup: -110"
messages. So the mainline kernel doesn't address this issue either.
Thanks!
Hi Kai-Heng,
Thanks for the next steps! I've just installed the latest mainline
kernel and it failed to boot. I _didn't_ attempt the new firmware at
the same time, would that have made a difference?
Thanks,
Dan
--
You received this bug notification because you are a member of Kernel
Hi Kai-Heng,
Thanks for the test kernel! Unfortunately, it doesn't appear to have
changed the behaviour. :(
```
$ uname -a
Linux surprise 5.0.0-16-generic #17~lp1830905 SMP Fri May 31 13:39:26 CST 2019
x86_64 x86_64 x86_64 GNU/Linux
$ grep :07:00.2 /var/log/dmesg
[0.086533] kernel:
OK, this improves things slightly; the first timeout is gone:
[0.12] kernel: pci :07:00.1: Linked as a consumer to :07:00.0
[0.124592] kernel: PCI: CLS 64 bytes, default 64
[0.124621] kernel: Unpacking initramfs...
But the second (longer) timeout is still there, and now
I will do, thank you! Can you direct me towards the appropriate Nvidia
forum to use? And is there any way I could configure my system to
perform that blacklisting in the meantime?
Thanks again!
--
You received this bug notification because you are a member of Kernel
Packages, which is
Applying the latest vbios update (F52) has caused this problem to go
away; this isn't a kernel issue.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
>From dmesg:
[0.132667] kernel: pci :07:00.1: Linked as a consumer to :07:00.0
[5.882727] kernel: pci :07:00.2: xHCI HW not ready after 5 sec (HC
bug?) status = 0x801
[5.882781] kernel: pci :07:00.2: quirk_usb_early_handoff+0x0/0x6a6 took
Public bug reported:
When using my desktop normally, I experienced a hard lock-up. On
reboot, I was able to examine the journal to find a whole bunch of
traces (attached in journal-traces).
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.0.0-15-generic 5.0.0-15.16
I've posted https://devtalk.nvidia.com/default/topic/1054978/linux
/ubuntu-boot-delayed-by-30s-due-to-non-functional-rtx2060-usb-
controller/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug is believed to be fixed in curtin in version 19.1. If this is
still a problem for you, please make a comment and set the state back to
New
Thank you.
** Changed in: curtin
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
This bug is believed to be fixed in curtin in version 19.1. If this is
still a problem for you, please make a comment and set the state back to
New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of
Public bug reported:
I just installed a new kernel, and when I did so my Nvidia kernel
modules were handled through DKMS, as you would expect. However, during
what I believe is normal operation, I saw the following stanza (repeated
for several nvidia .ko files):
nvidia.ko:
Running module
Public bug reported:
I just installed new Nvidia drivers in a meeting room and, as I have
Secure Boot enabled, was prompted for the password to enter on next
reboot. Surprisingly, the password I entered (twice) was in clear text
both times I entered it, which gives others around me an
I can also confirm that installing linux-modules-extra-5.0.0-8-generic
(which also pulls in crda iw libnl-genl-3-200 wireless-regdb) caused
this problem to no longer appear.
(I'm happy for this to be marked duplicate, but I wonder if there's
still an iptables bug, given that memory allocation is
Now one wrinkle about it being a linux-azure bug: if you _aren't_ seeing
this on bionic but _were_ seeing it on cosmic, then there must be
something else involved, because I believe (based on the publishing
history[0]) that cosmic was on the same kernel version as bionic.
This could, of course,
(Oh, and thank you for that test run!)
--
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/1834875
Title:
cloud-init growpart race with udev
Status in cloud-init:
In Progress
Status
Based on IRC conversation, I don't believe this is a cloud-init bug.
Please set the task back to New if I'm mistaken!
** Changed in: cloud-init
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in
The lack of events is not the issue. We see all the events from the
kernel that we would expect to see during a resize, and we see the same
number (and type) of events on both the passing and the failing
instances.
The problem is that if udev processes the sda1 event first then, at
least some of
Thanks for looking at the bug! Which mainline kernel should I look to
use? Is https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.1/ the
right one?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1854789/+attachment/5309352/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1854789/+attachment/5309349/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1854789/+attachment/5309359/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1854789/+attachment/5309358/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1854789/+attachment/5309354/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1854789/+attachment/5309353/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1854789/+attachment/5309357/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1854789/+attachment/5309356/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
apport information
** Attachment added: "AudioDevicesInUse.txt"
https://bugs.launchpad.net/bugs/1854789/+attachment/5309348/+files/AudioDevicesInUse.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1854789/+attachment/5309361/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1854789/+attachment/5309355/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
1 - 100 of 157 matches
Mail list logo
