On a fresh AWS instance I already see it stalling on package install, I
do not even need to reboot :-/
ubuntu@ip-172-31-16-15:~$ sudo apt install linux-cloud-tools-common
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages
Public bug reported:
I see a boot stall on a normal qemu/libvirt based KVM guest using an almost
fresh cloud image a stall on boot:
While live on the console I see:
[ OK ] Reached target System Time Set.
[ OK ] Finished Load AppArmor pro…s managed internally by snapd.
[* ] A start job is
** Package changed: kvm (Ubuntu) => linux (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/1967894
Title:
KVM IPI Virtualization support for SPR
Status in linux package in
This is actually fixed already in 5.13.0.39.44 as shown above, but the
root cause that I'm facing is that edge-Kernel is behind non -egde:
$ rmadison -a amd64 -u ubuntu linux-image-generic-hwe-20.04-edge | grep focal
linux-image-generic-hwe-20.04-edge | 5.13.0.27.29~20.04.13 | focal-security |
FYI for a different test I upgraded the system to Impish and on the
5.13.0-39-generic there neither of the two kernel bugs happens.
--
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/1966870
I tried things once more, this time OVS wasn't active at all (in the
former try it was active after boot and then disabled) - still failing.
Next I tried to use a different kernel(5.4.0-105-generic)
I don't know when in >5.4 this started to fail, it surely worked a few
months ago already using
As the last stage in the crash is in
? blk_mq_exit_hctx+0x160/0x160
I was looking if there was anything else with block devices going on.
I found another crash right at boot/init time (this one is also in the attached
currentDmesg.txt).
[ 537.566942] [ cut here ]
[
I have tried the same again, this time with openvswitch unconfigured (but still
running).
ubuntu@node-horsea:~$ sudo ovs-vsctl del-br ovsbr0
ubuntu@node-horsea:~$ sudo ovs-vsctl show
8dfc2067-7b9b-48d7-a50a-df17bbd3cb6c
ovs_version: "2.13.5"
chcpu disabling/enabling still crashes.
Ok, I have manually retried this - we do not need the KVM guest, it is the
chcpu that kills it.
Simplifying description ...
** Summary changed:
- Focal 20.04.4 crashing when using openvswitch/hugepages
+ Focal 20.04.4 crashing when using openvswitch and disabling CPUs
** Description changed:
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574134/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574141/+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: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574136/+files/Lsusb-t.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/1966870/+attachment/5574145/+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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574138/+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/1966870/+attachment/5574143/+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: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574144/+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: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574137/+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: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574142/+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/1966870/+attachment/5574139/+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/1966870/+attachment/5574140/+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/1966870/+attachment/5574133/+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/1966870
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574135/+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/1966870
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574132/+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: "CRDA.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574131/+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/1966870
Public bug reported:
Hi I'm facing the following crash now two times in a row while runnign the same
test - so somewhat reproducible it seems:
[ 1444.399448] BUG: kernel NULL pointer dereference, address: 0008
[ 1444.431172] #PF: supervisor write access in kernel mode
[ 1444.454715]
works correctly.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1890 F pulseaudio
/dev/snd/controlC0: christian 1890 F pulseaudio
CasperMD5CheckResult
** Tags removed: server-todo
--
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/1964093
Title:
nfsver=3,udp not working anymore
Status in linux package in Ubuntu:
Confirmed
Bug
There's a new firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=c784d7a3e3c2a83e3911fd3dd0e105911a323a5f
But this needs a driver feature-patch to work:
https://patchwork.kernel.org/project/linux-
** Bug watch added: Debian Bug tracker #900821
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900821
** Also affects: debian via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900821
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
n User Target.
Feb 26 09:35:05 lenou2004 systemd[1152]: Startup finished in 11.699s.
...
Feb 26 09:35:13 lenou2004 gdm-password][1829]: pam_unix(gdm-
password:session): session opened for user christian by (uid=0)
...
Feb 26 09:35:20 lenou2004 gnome-shell[1266]: Failed to set CRTC gamma:
drmMode
yeah sure, I've upgraded to the proposed "linux-firmware 1.201.5". So
far it keeps the connection to the Modem well enough for daily use...
nevertheless, I'll keep an eye out for future improvements.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
This was on a new Lenovo P14s Gen2 AMD. I'm using Ubuntu 21.10 (impish)
The current linux-firmware package (1.201.4+1.201.3) ships with realtek
rtw89_pci firmware (/lib/firmware/rtw89/rtw8852a_fw.bin) version
v0.13.8.0.
My wifi chip wasn't able to keep a connection for more
8-generic with same result, I have reverted back to
5.11.0.40 which works correctly.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1890 F pulseaudio
/dev/snd/co
FYI: If you want/need a test - builds of the qemu that have that are in
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4753
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thanks a bunch. It also works on a ThinkPad E14 Gen 2 with Ryzen 7 4700u
and AMD Renoir.
When I started with the new kernel I first had graphics issues. No
animations, only internal monitor working, black screen after sleep.
That was caused by a missing graphics driver. Software Updater suggested
: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1896 F pulseaudio
/dev/snd/controlC0: christian 1896 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1896 F pulseaudio
/dev/snd/controlC0: christian 1896 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-05-06 (609
.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1896 F pulseaudio
/dev/snd/controlC0: christian 1896 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20
ermanently on after wake-up.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1896 F pulseaudio
/dev/snd/controlC0: christian 1896 F pulseaudio
CasperMD5C
y on after wake-up.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1896 F pulseaudio
/dev/snd/controlC0: christian 1896 F pulseaudio
CasperMD5CheckRe
and stays permanently on after wake-up.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1896 F pulseaudio
/dev/snd/controlC0: christian 1896 F pulseaudio
CasperMD5C
ermanently on after wake-up.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1896 F pulseaudio
/dev/snd/controlC0: christian 1896 F pulseaudio
CasperMD5CheckRe
ermanently on after wake-up.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1896 F pulseaudio
/dev/snd/controlC0: christian 1896 F pulseaudio
CasperMD5C
y on after wake-up.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1896 F pulseaudio
/dev/snd/controlC0: christian 1896 F pulseaudio
CasperMD5CheckRe
y on after wake-up.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1896 F pulseaudio
/dev/snd/controlC0: christian 1896 F pulseaudio
CasperMD5CheckRe
ght blinks)
and stays permanently on after wake-up.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1896 F pulseaudio
/dev/snd/controlC0: christian 1896 F
and stays permanently on after wake-up.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1896 F pulseaudio
/dev/snd/controlC0: christian 1896 F pulseaudio
CasperMD5C
and stays permanently on after wake-up.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1896 F pulseaudio
/dev/snd/controlC0: christian 1896 F
and stays permanently on after wake-up.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1896 F pulseaudio
/dev/snd/controlC0: christian 1896 F
ermanently on after wake-up.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1896 F pulseaudio
/dev/snd/controlC0: christian 1896 F pulseaudio
CasperMD5CheckRe
and stays permanently on after wake-up.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1896 F pulseaudio
/dev/snd/controlC0: christian 1896 F pulseaudio
CasperMD5C
ermanently on after wake-up.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1896 F pulseaudio
/dev/snd/controlC0: christian 1896 F pulseaudio
CasperMD5CheckRe
after wake-up.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1896 F pulseaudio
/dev/snd/controlC0: christian 1896 F pulseaudio
CasperMD5CheckRe
y on after wake-up.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1896 F pulseaudio
/dev/snd/controlC0: christian 1896 F pulseaudio
CasperMD5CheckRe
ermanently on after wake-up.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1896 F pulseaudio
/dev/snd/controlC0: christian 1896 F pulseaudio
CasperMD5CheckRe
ermanently on after wake-up.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1896 F pulseaudio
/dev/snd/controlC0: christian 1896 F pulseaudio
CasperMD5CheckRe
to suspend mode (sleep) functions as expected (power light blinks)
and stays permanently on after wake-up.
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.21
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC1: christian 1896 F
** Description changed:
After kernel upgrade from 5.11.0.40 to versions 5.11.0.41, 5.11.0.43,
5.11.0.44 power-button light fails to switch off, after shutdown.
- shutdown can be triggered on command line or via desktop menu, result is
- the same. After rebooting from 5.11.0.40 normal
Public bug reported:
After kernel upgrade from 5.11.0.40 to versions 5.11.0.41, 5.11.0.43,
5.11.0.44 power-button light fails to switch off, after shutdown.
shutdown can be triggered from command line or via desktop menu, result
is the same. After rebooting from 5.11.0.40 normal functionality is
Proposed fix.
** Patch added:
"0001-ALSA-hda-cs8409-Increase-delay-during-jack-detection.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950900/+attachment/5550496/+files/0001-ALSA-hda-cs8409-Increase-delay-during-jack-detection.patch
--
You received this bug notification
Propsed fix is here:
https://lore.kernel.org/all/20211231131221.itwotyfk5qomn...@cae.in-
ulm.de/
--
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/1950900
Title:
Internal Speakers on DELL
** Tags added: intel-bug-december-2021
--
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/1954473
Title:
KVM Shared Virtual Memory (SVM)
Status in linux package in Ubuntu:
Incomplete
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
** Tags added: intel-bug-december-2021
--
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/1954465
Title:
KVM AIA User IPI
Status in linux package in Ubuntu:
Incomplete
Bug description:
** Tags added: intel-bug-december-2021
--
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/1954468
Title:
KVM Architectural LBRs
Status in linux package in Ubuntu:
Incomplete
Bug
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
** Tags added: intel-bug-december-2021
--
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/1954464
Title:
kvm SPR support for AMX
Status in linux package in Ubuntu:
Incomplete
Bug
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
** Tags added: intel-bug-december-2021
--
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/1954472
Title:
KVM Scalable I/O Virtualization
Status in linux package in Ubuntu:
Incomplete
** Tags added: intel-bug-december-2021
--
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/1954466
Title:
KVM Protection Keys for Supervisor Pages (PKS)
Status in linux package in Ubuntu:
** Tags added: intel-bug-december-2021
--
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/1954474
Title:
KVM notify VM Exit
Status in linux package in Ubuntu:
Incomplete
Bug
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
bisect und ubuntu-impish complete:
c8c30feea9b2373eaab7d1ed60803305b8c2f9c3 is the first bad commit
commit c8c30feea9b2373eaab7d1ed60803305b8c2f9c3
Author: Stefan Binding
Date: Thu Aug 19 14:14:21 2021 +0800
ALSA: hda/cs8409: Remove unnecessary delays
BugLink:
Thanks for the advice. Unfortunately, the problem is still there.
I'm currently bisecting this on ubuntu-impish. So I've been booting
kernels back an forth and it keeps looking like a kernel issue to me. At
least the distro kernel is consitently broken while other kernels
consitently work.
--
Another observation:
In the broken configuration the audio output is initially detected as "internal
speaker" by gnome.
However, as soon as an attempt to access the speaker is made (play an alarm
sound, change volume) the device morphs into Headphones.
--
You received this bug notification
I did a bit more research and the problem seems to be related to the
recent cirrus audio codec changes. At least dmesg between the non-
working and working kernel shows the following diff
Bluetooth: hci0: Found device firmware: intel/ibt-19-0-0.sfi
snd_hda_intel :00:1f.3: enabling device
*** This bug is a duplicate of bug 1952246 ***
https://bugs.launchpad.net/bugs/1952246
Hi Masato, I think I have re-discovered that with more detail in bug 1952246
Still waiting for the kernel team to look at.
** This bug has been marked a duplicate of bug 1952246
5.13 (I/J/F-HWE) Hosts
FYI this was reported earlier as bug 1944104 and still waits kernel team action
there.
Since this bug here has more data/details I've marked the other a dup.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Since it seems to depend on the host it likely is the chip, so here some info
about that.
This is the bad system.
** Attachment added: "cpuinfo-badsystem.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952246/+attachment/5543370/+files/cpuinfo-badsystem.txt
--
You received this
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543353/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Now I have completed attaching (apport-collect) data of both:
- Host (hostname: node-horse)
- first level guest (hostname: f)
--
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/1952246
Title:
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543349/+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: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543352/+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: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543347/+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/1952246
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543355/+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: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543351/+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: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543368/+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: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543364/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Now that all data is in place I set it to confirmed to silence the bots.
@Kernel people - is this known, if so where? If it is not known what else would
you need here?
--
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/1952246/+attachment/5543363/+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: "acpidump.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543369/+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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543358/+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: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543356/+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: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543366/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
101 - 200 of 1329 matches
Mail list logo
