Public bug reported:
The modules-extra packages for derivative kernels (maybe just some of
them) do not get installed during ADT testing, despite what looks like
an attempt to do so with this setup-command:
--setup-commands 'apt-get install -y
@paride: Yes, I've seen this with other kernels, mostly with the nvidia
drivers. I think all of the runs of the following since March 20 show
this problem:
https://autopkgtest.ubuntu.com/packages/n/nvidia-graphics-drivers-510-server/focal/amd64
@paride: Yes, I've seen this with other kernels, mostly with the nvidia
drivers. I think all of the runs of the following since March 20 show
this problem:
https://autopkgtest.ubuntu.com/packages/n/nvidia-graphics-drivers-510-server/focal/amd64
@paride: Yes, I've seen this with other kernels, mostly with the nvidia
drivers. I think all of the runs of the following since March 20 show
this problem:
https://autopkgtest.ubuntu.com/packages/n/nvidia-graphics-drivers-510-server/focal/amd64
** Changed in: kernel-sru-workflow/abi-testing
Status: Incomplete => New
--
You received this bug notification because you are a member of hardware-
certification-users, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2052048
Title:
focal/linux-azure-5.15:
** Attachment added: "ubuntu_boot-console.log"
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2055343/+attachment/5750420/+files/ubuntu_boot-console.log
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to
Public bug reported:
Attempts to boot a c3a-standard-4 VM with the jammy/linux version
5.15.0-100.110 fails. The VM appears to get to a login prompt, but there
is no networking.
Console log is attached.
** Affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
--
You
Public bug reported:
This is not necessarily a bug, just an unsupported configuration.
Attempts to install and boot a generic-64k kernel on t2a instances
result in a failure. The collected console log states:
UEFI: Attempting to start image.
Description: ubuntu
FilePath:
@Kevin,
Thank you for testing again. This latest output indicates something may
not be correct in your test environment. This line:
WARNING:root:_pkg_get_support nvidia-driver-525: package has invalid
Support PBheader, cannot determine support level
is indicating that the driver packages are
@Kevin,
Thank you for testing again. This latest output indicates something may
not be correct in your test environment. This line:
WARNING:root:_pkg_get_support nvidia-driver-525: package has invalid
Support PBheader, cannot determine support level
is indicating that the driver packages are
I have done my typical CUDA based testing with this package using the
generic, nvidia and gcp kernels using bionic, focal, jammy and mantic
(amd64 only so far).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have done my typical CUDA based testing with this package using the
generic, nvidia and gcp kernels using bionic, focal, jammy and mantic
(amd64 only so far).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470
I have done my typical CUDA based testing with this package using the
generic, nvidia and gcp kernels using bionic, focal, jammy and mantic
(amd64 only so far).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@kevinyew, @shanew, It looks like you are hitting this on focal. Can you
please confirm?
If so, can you please retest with the latest ubuntu-drivers from focal-
proposed? This should be version 1:0.9.0~0.20.04.8. This appears to fix
a bug (discussed in
@kevinyew, @shanew, It looks like you are hitting this on focal. Can you
please confirm?
If so, can you please retest with the latest ubuntu-drivers from focal-
proposed? This should be version 1:0.9.0~0.20.04.8. This appears to fix
a bug (discussed in
I can reproduce the failure on mantic with both the DKMS and LRM
drivers. Specifically what I'm doing to install these are:
for DKMS:
sudo DEBIAN_FRONTEND=noninteractive apt-get install -y nvidia-driver-535-server
for LRM:
sudo DEBIAN_FRONTEND=noninteractive apt-get install -y
Serial console log from a ubuntu_kselftests_ftrace test run.
** Attachment added: "ubuntu_ftrace_smoke_test-console.log"
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2051378/+attachment/5742658/+files/ubuntu_ftrace_smoke_test-console.log
** Tags added: sru-20231030 sru-20240108
**
Public bug reported:
Testing on n2d-standard-4.sev_snp and possibly other sev_snp enabled
instances unexpectedly reboot during cpuhotplug operations. This is
known to happen during the following tests:
ubuntu_ftrace_smoke_test.ftrace-smoke-test
We are still looking into this issue. While we can reproduce the test
case and see difference in the performance, the delta is not as
significant and our results have not very consistent. I'm taking the
approach of setting up a more comprehensive test environment to run more
tests faster.
The latest maas images from 20231008 are booting without issue:
ubuntu@akis:~$ lsb_release -sc
No LSB modules are available.
mantic
ubuntu@akis:~$ cat /etc/cloud/build.info
build_name: server
serial: 20231008
ubuntu@akis:~$ uname -a
Linux akis 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri
The latest maas images from 20231008 are booting without issue:
ubuntu@akis:~$ lsb_release -sc
No LSB modules are available.
mantic
ubuntu@akis:~$ cat /etc/cloud/build.info
build_name: server
serial: 20231008
ubuntu@akis:~$ uname -a
Linux akis 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri
Special maas image built with util-linux, 2.39.1-4ubuntu2, from
https://ppa.launchpadcontent.net/xnox/release-critical/ubuntu is looking
good. I have one machine deployed with this:
ubuntu@rumford:~$ uname -r
6.5.0-5-lowlatency
ubuntu@rumford:~$ apt-cache policy util-linux
util-linux:
Special maas image built with util-linux, 2.39.1-4ubuntu2, from
https://ppa.launchpadcontent.net/xnox/release-critical/ubuntu is looking
good. I have one machine deployed with this:
ubuntu@rumford:~$ uname -r
6.5.0-5-lowlatency
ubuntu@rumford:~$ apt-cache policy util-linux
util-linux:
** Project changed: linux => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Milestone: None => ubuntu-23.10
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Mantic)
Importance: Undecided
Status: Confirmed
--
You
** Project changed: linux => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Milestone: None => ubuntu-23.10
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Mantic)
Importance: Undecided
Status: Confirmed
--
You
** Also affects: linux
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2037417
Title:
mantic images after 20230917 are failing
My experiments with the workaround mentioned in
https://bugs.launchpad.net/ubuntu/+source/initramfs-
tools/+bug/2037202/comments/1 did not help.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I have tested booting with various initrd/kernel/squashfs combinations.
* The mantic 6.5.0-5 kernel and modules repacked into a jammy (20230927) or
lunar (20230927) initrd and squashfs result in a deployed host.
* The mantic initrd and squashfs from 20230908 with the 6.5.0-5 kernel did not
The 6.5.0-6.6 linux kernel in mantic-proposed also fails.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2037417
Title:
mantic images after 20230917 are failing to deploy
I've confirmed this problem on amd64 and ppc64el
(https://bugs.launchpad.net/maas/+bug/2037475).
** Summary changed:
- mantic arm64 images are failing to deploy with failure to mount root and
kernel filesystems
+ mantic images after 20230917 are failing to deploy with failure to mount root
and
The last working maas image had kernel 6.3.0-7-generic, the first one to
fail has 6.5.0-5-generic.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2037417
Title:
mantic
journalctl -b --no-pager
** Attachment added: "kopter-journal.log"
https://bugs.launchpad.net/maas-images/+bug/2037417/+attachment/5704620/+files/kopter-journal.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
I have done some debugging, but I'm at a loss for what to do next.
Booting with 'apparmor=0' did not help.
Here's what the mounts look like:
# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs
eeks vs. say 26 weeks
> (i.e. our development cycle length)?
>
> Bryce
>
I would also recommend a longer period, at least 12 or 16 weeks. The
selfish reasoning is that this would give us at least 2 kernel SRU cycles
worth of (hopefully) passing logs to use when triaging a failure.
Fr
** Changed in: kernel-sru-workflow/boot-testing
Status: Opinion => New
--
You received this bug notification because you are a member of hardware-
certification-users, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2036582
Title:
lunar/linux-gcp: 6.2.0-1016.18
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2034447/+attachment/5697982/+files/acpidump.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: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2034447/+attachment/5697981/+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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2034447/+attachment/5697980/+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: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2034447/+attachment/5697979/+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: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2034447/+attachment/5697977/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2034447/+attachment/5697978/+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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2034447/+attachment/5697976/+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: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2034447/+attachment/5697975/+files/Lsusb-v.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-vt.txt"
https://bugs.launchpad.net/bugs/2034447/+attachment/5697974/+files/Lspci-vt.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/2034447/+attachment/5697973/+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/2034447
apport information
** Tags added: apport-collected jammy uec-images
** Description changed:
Seeing a panic on hidon (an Nvidia H100) after booting the
5.15.0-85-generic kernel:
[ 58.935877] [ cut here ]
[ 58.935893] refcount_t: underflow; use-after-free.
Here's the full log from where that snippet was pulled.
** Attachment added: "hidon.log.1"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034447/+attachment/5697793/+files/hidon.log.1
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
Seeing a panic on hidon (an Nvidia H100) after booting the
5.15.0-85-generic kernel:
[ 58.935877] [ cut here ]
[ 58.935893] refcount_t: underflow; use-after-free.
[ 58.935920] WARNING: CPU: 207 PID: 2985 at lib/refcount.c:28
We're not seeing this after moving our amd64 testing to the PS5 cloud.
These earlier tests were executed on the scalingstack clouds.
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
I built and tested a 6.2.0-1004-nvidia based kernel with this patch
applied and did not see the warning message on boot. I'll follow up
further with Ian on Monday.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-6.2 in
I ran through several kernels on our DGX-2 server, only the latest
6.2.0-1004-nvidia kernel emitted the warning. Here are all the kernels I
tried:
Lunar 6.2.0-24.24 generic - PASS
Jammy 5.15.0-1028-nvidia - PASS
Jammy 5.19.0-46-generic - PASS
Jammy 5.19.0-1014-nvidia - PASS
Jammy 6.2.0-25-generic
Public bug reported:
We started testing the jammy/linux-nvidia-6.2 kernels on the nvidia
servers (DGX-1/DGX-2/H100) and hit the following warning during boot:
[7.690486] [ cut here ]
[7.690487] Interrupts were enabled early
[7.690490] WARNING: CPU: 0 PID: 0 at
Automated testing of the DKMS drivers, (450-server, 470-server,
525-server, 470, 525 and 535) has completed across bionic, focal, jammy,
kinetic and lunar. This was performed with:
* Deploy host with gpgpu
* Install latest `linux-generic` kernel
* Install driver from ppa using
Thanks to everyone supplying their logs. I'm still looking through these
to try to understand what's going on here.
For most that hit this issue, the solution would be interrupt the boot
loader to boot back into the generic kernel, then remove the oracle and
lowlatency kernels.
--
You received
@navroop005,
Hello, would you mind please sharing a copy of your
`/var/log/apt/history.log`? This looks like a possible package
dependency issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-oracle in Ubuntu.
I've found a flaw in the test script in which it was installing the
wrong LRM modules for the running kernel. It was installing the generic
modules for a gcp kernel. Once I corrected this to install the gcp
modules, it now passes.
Attached are the logs with the addition of `lsmod` and `modinfo
I've reproduced this with the 6.3.0-7-generic kernel from mantic-
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/2023611
Title:
Unable to remove efi variable with 6.2.0-21.21
Public bug reported:
I'm seeing an issue on an isolated host, howzit, in which it fails to
remove boot entries. In my limited testing this worked with the
6.2.0-20.20 kernel, but not the 21.21 or 23.23 kernel. I have not yet
tried any of the 6.3 kernels.
I've only seen this on one host so far,
@paride,
We still see failures that have this same signature. For example:
https://autopkgtest.ubuntu.com/results/autopkgtest-
jammy/jammy/amd64/l/linux-ibm/20230606_191701_efaf4@/log.gz
Has this not been completely solved? Are we dealing with old autopkgtest
images that have not yet been
Public bug reported:
Installing "nvidia-driver-525-open" followed by "nvidia-headless-no-
dkms-525 linux-modules-nvidia-525-gcp nvidia-utils-525" led to a system
which complained about a "Driver/library version mismatch". Specifically
what was done is:
Deploy a clean google VM with:
gcloud
I can confirm @xnox's findings with my maas server deploying lunar.
Adding `apparmor=1` to the settings/configuration/kernel-parameters
allows for a successful deployment with the lunar 6.2.0-20.20 kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which
I can confirm @xnox's findings with my maas server deploying lunar.
Adding `apparmor=1` to the settings/configuration/kernel-parameters
allows for a successful deployment with the lunar 6.2.0-20.20 kernel.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
We discussed fixes to the maas bootloader builds and as a result, we
have a new maas bootloader which should have the latest shim and grub:
http://images.maas.io/ephemeral-v3/candidate/bootloaders/uefi/amd64/20230420.0/
I manually copied these to my test maas, it did not resolve the issue
(or
Review: Approve
This was discussed on MM between myself, Dann and Adam.
The latest lunar maas images are unusable due to
https://bugs.launchpad.net/cloud-init/+bug/2009746. Maas image builds are
failing due to a size check for these xgene systems (the kernel since moving to
6.2 has grown too
Cuda testing passed for all drivers (470, 515, 525, 450-server,
470-server, 515-server, 525-server) on bionic, focal, jammy and kinetic
using both DKMS and LRM (when using the appropriate stream 2 ppa for the
LRM packages). DKMS testing also passed on lunar.
--
You received this bug notification
Still failing on baltar.ppc64el.9 during 2023.02.27 sru cycle. The
kuzzle and scobee (another arm64 server) passed.
** Tags added: sru-20230227
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
No regressions found for either 515-server or 525-server. Both were
tested as DKMS and as LRMs using the generic kernel in all releases
(lunar could not be installed with lrm). Jammy was also tested with the
linux-nvidia kernel and LRMs.
--
You received this bug notification because you are a
Here is the full syslog from which the portion in the bug description
was extracted from.
** Attachment added: "c5.12xlarge-3-syslog.log"
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2006620/+attachment/5645600/+files/c5.12xlarge-3-syslog.log
--
You received this bug
Public bug reported:
Hibernation on AWS instances with jammy/5.19.0-1019-aws sometimes fails
due to the following failure to freeze:
Feb 1 01:09:05 ip-172-31-54-178 kernel: [ 443.247854] PM: hibernation:
hibernation entry
Feb 1 01:09:05 ip-172-31-54-178 kernel: [ 443.347353] TSC found
The A100 is down with some hardware issues and there is no ETA when it
will be up again. Given that the testing passed on the DGX2 and the A100
is having hardware issues which quite likely impacted the testing, I'm
going to consider the kinetic testing as verified.
** Tags removed:
Re-running through the testing on our DGX2 now passes for both DKMS and
LRM. I will need to retry the testing on A100 again and see if I missed
something like the fabricmanager not being ready yet.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Verification on kinetic is incomplete. Things do work on a cloud
instance with a single gpgpu. In these cases, both the DKMS and LRM
version of the driver works with the cuda samples test.
Problems are encountered when running on either the DGX2 or A100
systems. For the A100, I have not been able
Tested bionic, focal and jammy on VMs and a DGX2. All cuda tests passed.
There is no updated kinetic driver, so unable to test there.
** Tags added: verification-done-bionic verification-done-focal
verification-done-jammy verification-failed-kinetic
--
You received this bug notification
@juliank, ah, I found another detail. This appears to only break when
the package is updated in the ADT testbed. My assumption is if the
latest package version is already in the base image, there is no package
update and therefore no breakage. For example:
[1] older image, fails:
@juliank Hello, I see that you picked up
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1991676. I
just want to mention so that you are aware, that this is blocking most,
if not all, kernel ADT testing on bionic arm64.
--
You received this bug notification because you are a member
** Tags added: 5.4
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure-4.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1923114
Title:
ubuntu_kernel_selftests: ./cpu-on-off-test.sh: line 94: echo: write
error: Device or
Testing of nvidia-fabricmanager-510 and libnvidia-nscq-510 has been
successfully performed again against the packages in -proposed. These
are good to release from a testing perspective.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal
Hello Sebastian,
I've been unable to reproduce this issue with the 5.13.0-1029-aws kernel
and the docker-compose example available from [1]. Are you able to
provide complete steps to reproduce?
[1] - https://docs.docker.com/compose/gettingstarted/
Thanks
--
You received this bug notification
All of the updated 5.13 kernels have now made it to the archive and into
both the focal-updates and focal-security pockets. That list of kernels
is:
linux-aws-5.13 - 5.13.0-1029.32~20.04.1
linux-azure-5.13 - 5.13.0-1029.34~20.04.1
linux-gcp-5.13 - 5.13.0-1031.37~20.04.1
linux-oracle-5.13 -
Updated kernels are in flight. The updated kernel packages and versions
are:
linux-aws-5.13- 5.13.0-1029.32~20.04.1
linux-azure-5.13 - 5.13.0-1029.34~20.04.1
linux-gcp-5.13- 5.13.0-1031.37~20.04.1
linux-oracle-5.13 - 5.13.0-1034.40~20.04.1
The azure and gcp kernels are already in
The fabric-manager-510 and libnvidia-nscq-510 were tested across all
series on an A100 system. All testing passed the standard cuda testing.
The packages tested were from https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+packages?field.name_filter=-510_filter=published_filter=
--
Work on this issue continues. We have identified the following impacted
kernels and versions:
focal linux-aws-5.13 5.13.0-1028.31~20.04.1
focal linux-azure-5.13 5.13.0-1028.33~20.04.1
focal linux-gcp-5.13 5.13.0-1030.36~20.04.1
focal linux-oracle-5.13 5.13.0-1033.39~20.04.1
--
You received
** 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/1973034
Title:
linux generic fails to boot on azure arm64 instance
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973034
Title:
linux generic fails to boot on azure arm64 instance types
To
Artifacts were collected from a new VM running focal/linux-azure just
prior to rebooting to linux-generic (which gets stuck at initramfs).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Artifacts were collected from a new VM running focal/linux-azure just
prior to rebooting to linux-generic (which gets stuck at initramfs).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973034
Title:
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1973034/+attachment/5588652/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1973034/+attachment/5588650/+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: "acpidump.txt"
https://bugs.launchpad.net/bugs/1973034/+attachment/5588654/+files/acpidump.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: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1973034/+attachment/5588653/+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/1973034/+attachment/5588649/+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: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1973034/+attachment/5588651/+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: "acpidump.txt"
https://bugs.launchpad.net/bugs/1973034/+attachment/5588654/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973034
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1973034/+attachment/5588652/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973034
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1973034/+attachment/5588653/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973034
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1973034/+attachment/5588651/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973034
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1973034/+attachment/5588649/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1973034/+attachment/5588650/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1973034/+attachment/5588646/+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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1973034/+attachment/5588648/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1 - 100 of 2646 matches
Mail list logo
