Public bug reported:
The kernel module ptp_kvm.po is for syncing the time between VM and host in a
KVM environment.
BUT: this module is missing in the -kvm kernel or module flavored packages.
It *IS* inside these packages:
/lib/modules/5.4.0-1009-aws/kernel/drivers/ptp/ptp_kvm.ko
linux-m
Sorry, was a bit busy lately.
For users that needs DKMS, please use this PPA before official kernel has the
fix:
https://launchpad.net/~kaihengfeng/+archive/ubuntu/lp1853277
--
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.
https://bugs.launchpad.net/bu
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => 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/1896303
Title:
Intel AX201 (Wireless-AC 9462)
Public bug reported:
Ubuntu certification list includes 20.04 running on the Lenovo X1 Carbon Gen 8:
https://certification.ubuntu.com/hardware/202005-27937
But wifi does not work, at all ('iwlist scanning' returns 'No scan
results' despite more than a dozen 2.4ghz networks and a half dozen 5ghz
n
Please close this bug. I was wrong about the queue depth being the
source of this issue. Currently I've tried including pci=nomsi at the
kernel command line, and I seem to be the avoiding SATA errors.
--
You received this bug notification because you are a member of Kernel
Packages, which is su
guess that's fine, next would be to file it upstream to Intel.. If
you're up for it, the place would be
https://gitlab.freedesktop.org/drm/intel/-/issues
needs an account there, of course
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
should it be enough to add that commit next cycle?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1896008
Title:
linux-libc-dev in proposed cause seccomp_bpf from seccomp in
ub
Patched kernel packages (based on focal master-next and groovy master-
next) are available here for further testing:
https://people.canonical.com/~fheimes/lp189284/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
Confirmed verification is done on Bionic. Switched status. Conversation
from Mattermost:
kmously
@cascardo Does LP#1886860 need verification? I'm trying to verify it myself,
but I'm getting some strange behaviour on bionic.
With the -updates kernel, your reproducer reboots the machine in
Patch request submitted for groovy:
https://lists.ubuntu.com/archives/kernel-team/2020-September/thread.html#113599
changing status to 'In Progress' for groovy.
** Changed in: linux (Ubuntu Groovy)
Status: New => In Progress
** Changed in: ubuntu-z-systems
Status: New => In Progress
Same here; the upgrade to alsa-ucm-conf 1.2.2-1ubuntu0.3 alone wasn't
enough to fix the issue on my Regolith install (Ubuntu 20.04.1).
However, after upgrading I once more tried the fixes described in the
following article (essentially the same workarounds that others have
suggested in this thread
I pushed a version for focal on my ppa. It is based on the latest
version found on groovy, so there should be other changes besides the
one for setting a better default of crashkernel on /etc/zipl.conf.
It's at ppa:cascardo/kdump2. Note that if the user has changed the value
from the previous defa
That update hasn't fixed the bass on my ubuntu 20.04 install
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/1872108
Title:
Bass not on working Lenovo ThinkPad X1 Carbon 7th gen r
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1886860
Title:
cgroup refcount is bogus when cg
Driver version 440.100
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-common in Ubuntu.
https://bugs.launchpad.net/bugs/1054458
Title:
nvidia-detector crashed with ValueError in __get_value_from_name():
invalid literal for int
Ubuntu MATE 20.04, same issue with an nVidia GeForce MX150 on an ASUS
Zenbook 14
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-common in Ubuntu.
https://bugs.launchpad.net/bugs/1054458
Title:
nvidia-detector crashed with ValueE
https://bugzilla.kernel.org/show_bug.cgi?id=209317
** Bug watch added: Linux Kernel Bug Tracker #209317
https://bugzilla.kernel.org/show_bug.cgi?id=209317
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
Commit afdf9550e546 landed upstream in linux-next and is currently
tagged with 'next-20200915' only - probably planned to end up in 5.10.
--
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/1896
Operator error. I was apparently using the wrong UART. See
https://github.com/raspberrypi/linux/issues/3821.
** Bug watch added: github.com/raspberrypi/linux/issues #3821
https://github.com/raspberrypi/linux/issues/3821
** Changed in: linux-raspi (Ubuntu Focal)
Status: New => Invalid
*
Same here BUT ... I have delete the /var/crash/* and init splash stop to
consume 100% cpu.
This is the clue :
```
sept. 18 15:15:26 rige systemd[1]: apport-autoreport.service: Succeeded.
sept. 18 15:15:26 rige systemd[1]: Finished Process error reports when
automatic reporting is enabled.
sept.
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status:
Sorry, wasn't sure how to upload it in a text file, so here's the output
of the stack trace.
--
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/1836701
Title:
ubuntu18.04: ipmitool failed: C
0.00 execve("/usr/bin/ipmitool", ["ipmitool", "lan", "print"],
0x7ffd94ec9220 /* 19 vars */) = 0 <0.001210>
0.001285 brk(NULL) = 0x562dedd8e000 <0.04>
0.55 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory) <0.07>
0.26 acc
** Attachment added: "Easier way to read it."
https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1836701/+attachment/5412162/+files/ipmitool.strace.10279
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
On Fri, Sep 18, 2020 at 2:15 PM Ventsislav Georgiev
<1836...@bugs.launchpad.net> wrote:
>
> Yeah I did try that (saw it somewhere among the web) but it pretty much
> gives nothing, because of the main error.
>
> root@x:~# strace -rT -ff -o ipmitool.strace ipmitool lan print
> Could not open device
Yeah I did try that (saw it somewhere among the web) but it pretty much
gives nothing, because of the main error.
root@x:~# strace -rT -ff -o ipmitool.strace ipmitool lan print
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such
file or directory
So I guess that ipmitoo
Hmm, so your system indeed has /dev/ipmi0 then (also you had that implicitly in
comment #4 already) - thanks.
But that means we are back at the beginning with the but triggering for you but
being non reproducible in other places :-/
For the sake of generating more ideas what could happen in your
** Attachment added: "strace good case"
https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1836701/+attachment/5412154/+files/ipmitool.strace.183665
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
Correct Stefan, this is for Focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Title:
Add/Backport EPYC-v3 and EPYC-Rome CPU model
Status in libvirt package in Ubuntu:
Incom
I got a link from kernel maintainers to a tool that can help to hack
Windows i2c bus.
https://github.com/bentiss/SimplePeripheralBusProbe
If anyone wants to try to get the command, it will be very helpful.
--
You received this bug notification because you are a member of Kernel
Packages, which
It's a pity - it's a great laptop apart from this problem, but not being
able to shut the lid without losing sound is a significant drawback. It
wouldn't be so bad if there were a workaround of some sort, but I've not
seen one and I don't know how to go about looking for one.
I tried it with Ubunt
--- Comment From niklas.schne...@ibm.com 2020-09-18 06:41 EDT---
Note I just checked and this cherry-picks cleanly on focal/master-next.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
Same machine with current 5.8.0-19-generic tip and the issue is now
resolved.
** Changed in: linux (Ubuntu)
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.launchpa
This test will pass with commit 47e33c05f9f07cac3de833e531bcac9ae052c7ca
("seccomp: Fix ioctl number for SECCOMP_IOCTL_NOTIF_ID_VALID")
Test kernel could be found here:
https://people.canonical.com/~phlin/kernel/lp-1896008-linux-libc-dev/
--
You received this bug notification because you are a m
Public bug reported:
Commit "s390/pci: adapt events for zbus" removed the
zpci_disable_device() call for a zPCI event with PEC 0x0304 (hot unplug)
becausethe device is already deconfigured by the platform.
This however skips the Linux side of the disable in particular it leads
to leaking the DMA
You have been subscribed to a public bug:
Commit "s390/pci: adapt events for zbus" removed the
zpci_disable_device() call for a zPCI event with PEC 0x0304 (hot unplug)
becausethe device is already deconfigured by the platform.
This however skips the Linux side of the disable in particular it lead
This issue can be found on Focal as well.
** Tags added: 5.4
** Tags added: focal
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Summary changed:
- Test 20 in fanotify10 fr
The Groovy version is already on the ml, looking at the Focal version
now but s/disk_{start,end}_io_acct/generic_{start,end}_io_acct/g is not
enough.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Status: New => Fix Committed
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
I had the same thought reading the last message,
best wishes to everyone that will try to solve the problem that is sadly
ignored by the official developers.
Many thanks, If you need any kind of support providing logs of any other
things please let me know, I will be happy to help.
Cheers,
Andrea
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Bionic)
Status: New => Fix Committed
--
You received this bug notification because you are a member of K
Note that the dist-upgrade will be performed after the deployment with
MAAS (before the test starts).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1896008
Title:
linux-libc-dev
Hello,
This is the first encouraging message I read on the subject!
Unfortunately, I don't have the skills to help you but I hope with all
my heart that someone will be able to help you so that we can finally
enjoy our touchpad with the numberpad function.
--
You received this bug notification b
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kern
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kern
I'd confirmed it with package from -proposed and it works as expected.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1896008
Title:
linux-libc-dev in prop
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1896008/+attachment/5412076/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1896008/+attachment/5412082/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896008
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1896008/+attachment/5412078/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1896008/+attachment/5412080/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1896008/+attachment/5412079/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1896008/+attachment/5412081/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1896008/+attachment/5412077/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1896008/+attachment/5412083/+files/WifiSyslog.txt
** Also affects: linux-oem-5.6 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ke
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1896008/+attachment/5412072/+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/1896008
I have tested the following combination:
Kernel 5.6.0-1028 + Source code 5.6.0-1028
Kernel 5.6.0-1028 + Source code 5.6.0-1027
Kernel 5.6.0-1027 + Source code 5.6.0-1028
Kernel 5.6.0-1027 + Source code 5.6.0-1027
All these combination can pass without any issue, the key point is the
dist-upgrade
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1896008/+attachment/5412074/+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/1896008
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1896008/+attachment/5412070/+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/1896008
Ti
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1896008/+attachment/5412075/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1896008/+attachment/5412073/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/18
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1896008/+attachment/5412071/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
A quick update here. After running the test on the following build, the
symptom still can be observed. If test config configured as RAID mode,
the system can not find any disk. Moreover, after rolling back the
change (RAID -> AHCI), the system ran the recovery process instead of
booting into the de
Arch is affected as well: https://mailman.alsa-project.org/pipermail
/alsa-devel/2016-June/109296.html
** Also affects: archlinux
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
65 matches
Mail list logo
