** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Seth Forshee
(sforshee)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Yu Kei (office-liquid-light)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https
** Changed in: ubuntu-z-systems
Status: Triaged => 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/1762719
Title:
System Z {kernel} UBUNTU18.04 wrong kernel config
Sta
Yes it looks like the same bug (at least for the GUI part), and it's a
Thinkpad as well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1762603
Title:
bluetooth keeps turning off
Status
[22596.884250] sysrq: SysRq : This sysrq operation is disabled.
I got this, if I try to trigger those sysreq events by echoing t/m into
that procfs file. I'm anyway curious how sysreq stuffs can be
enabled/disabled, since I seldom use ALT-SYSREQ- combos as well, and
many of them just reports t
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1761557/+attachment/5109287/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1761557/+attachment/5109285/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bug
just to be clear:
I received a call on my bluetooth headphones...
I "copied" this workaround from here:
https://bbs.archlinux.org/viewtopic.php?id=226312
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://
** Tags added: regression-testing-passed
--
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/1761177
Title:
linux: 4.15.0-15.16 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
*** This bug is a duplicate of bug 1761179 ***
https://bugs.launchpad.net/bugs/1761179
** This bug has been marked a duplicate of bug 1761179
linux-aws: 4.15.0-1003.3 -proposed tracker
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1761557/+attachment/5109280/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1761557/+attachment/5109282/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.
Tested kernel from xenial-proposed on an affected system, and the issue
there appears to be resolved.
$ uname -r
4.4.0-120-generic
$ apt policy linux-image-generic
linux-image-generic:
Installed: 4.4.0.120.126
Candidate: 4.4.0.120.126
Version table:
*** 4.4.0.120.126 400
400 http:/
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1761557/+attachment/5109284/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1761557/+attachment/5109283/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launch
** Changed in: kernel-sru-workflow/snap-release-to-beta
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/snap-release-to-edge
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/snap-certification-testing
Status: New => Confirmed
--
You
I've tested the artful kernel on a UEFI system (and tracked own how the
signed kernel is produced from the unsigned on in the debs at he same
time - see #76).
It fixes the issue (tag already changed).
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
Public bug reported:
Kernel config 4.15.0-13-generic #14 (and same for 4.15.0-15-generic) is
not OK, because both security mechanisms nobp AND expoline are enabled:
CONFIG_KERNEL_NOBP=y
CONFIG_EXPOLINE=y
# CONFIG_EXPOLINE_OFF is not set
# CONFIG_EXPOLINE_MEDIUM is not set
CONFIG_EXPOLINE_FULL=y
You have been subscribed to a public bug:
Kernel config 4.15.0-13-generic #14 (and same for 4.15.0-15-generic) is
not OK, because both security mechanisms nobp AND expoline are enabled:
CONFIG_KERNEL_NOBP=y
CONFIG_EXPOLINE=y
# CONFIG_EXPOLINE_OFF is not set
# CONFIG_EXPOLINE_MEDIUM is not set
CON
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1761557/+attachment/5109281/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1761557/+attachment/5109279/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1761557/+attachment/5109286/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bug
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-release
Status: New => Confirmed
** Tags removed: block-proposed-bionic
** Tags removed: block-proposed
--
You received this bug notification beca
hi Joseph,
I tested on both versions and the kernel solves the problem:
== Xenial ==
# uname -a
Linux 1604 4.4.0-116-generic #140~lp1744174 SMP Tue Mar 6 14:15:54 UTC 2018
ppc64le ppc64le ppc64le GNU/Linux
== Artful ==
# uname -a
Linux 1710 4.13.0-36-generic #40~lp1744173 SMP Tue Mar 6 14:17:1
** Also affects: nvidia-common (Ubuntu Bionic)
Importance: Undecided
Status: Invalid
** Also affects: ubuntu-drivers-common (Ubuntu Bionic)
Importance: High
Assignee: Alberto Milone (albertomilone)
Status: Fix Released
** Changed in: ubuntu-drivers-common (Ubuntu Bionic)
On Tue, Apr 10, 2018 at 2:44 AM, Colin Ian King
<1760...@bugs.launchpad.net> wrote:
> Would an immediate return with some error/warning message be more
> appropriate that a 10 second delay?
Yes. I would think that the amount of time to wait could be an option.
I've read that in some scenarios user
@brad-figg #98:
I've tested the Xenial-proposed kernel on a machine that was previously broken
(even performed a fresh install to this effect). The proposed kernel
(4.13.0-39) fixes the problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
Verified artful-proposed.
root@ubuntu:~# cat /etc/cloud/build.info
build_name: server
serial: 20180404
root@ubuntu:~# uname -a
Linux ubuntu 4.13.0-38-generic #43-Ubuntu SMP Wed Mar 14 15:20:44 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
root@ubuntu:~# mount /dev/sda /mnt
root@ubuntu:~# grep sda /pr
Cherry picked the auto-detection patches into bionic, set
CONFIG_EXPOLINE_AUTO=y and CONFIG_KERNEL_NOBP=n.
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because y
The module already has an alias that should allow it to autoload:
alias: acpi*:PNP0CA0:*
What is the output of ls /sys/bus/acpi/devices/*PNP0CA0* on such a system?
Or grep -H . /sys/bus/acpi/devices/*PNP0CA0*/modalias?
Cascardo.
--
You received this bug notification because you are a
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1762719
Title:
System Z {kernel} UBUNTU18.04 wrong kernel confi
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1762353
Title:
[Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioct
** Changed in: ubuntu-z-systems
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1762353
Title:
[Ubuntu 18.04] cryptsetup: 'device-mapper: reload io
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1762695
Title:
Backport USB core quirks
Status in linux package i
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1729128
Title:
Raspberry Pi 3 microSD support missing from t
*** This bug is a duplicate of bug 1729128 ***
https://bugs.launchpad.net/bugs/1729128
** This bug has been marked a duplicate of bug 1729128
Raspberry Pi 3 microSD support missing from the installer
--
You received this bug notification because you are a member of Kernel
Packages, which
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
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/1758471
Title:
apparmor: fix bad __initdata tagging on,
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1729128
** Tags added: iso-testing
--
You received this bug notification because you are a member of Kernel
Packages, which
We have two Briggs system at Canonical, one is offsite and the other is
being used actively by the security cert team. IBM, could you please
help testing the kernel Joe noted in the previous comment?
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
Public bug reported:
HiSilicon hip08 systems support a cq/rq record feature for RDMA that is
currently not supported by the kernel.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
--
You received this bug notification becaus
** Changed in: linux (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
Canonical Kernel Team (canonical-kernel-team)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Pack
** Changed in: linux (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
Canonical Kernel Team (canonical-kernel-team)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Pack
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1759791
Title:
NFS + sec=krb5 is broken
Status in linux p
Snap beta testing complete, no regressions found. Ready for promotion.
Results here: https://trello.com/c/Ro5UWGBF/234-pc-kernel-440-120144-110
** Changed in: kernel-sru-workflow/snap-certification-testing
Status: Confirmed => Fix Released
--
You received this bug notification because you
Public bug reported:
The LPC patchset for HiSilicon boards landed upstream in the v4.17
merge window. We're currently carrying an earlier version (v14) of the
patches as SAUCE, while v17 + a bug fix is what was eventually merged.
There is at least one notable bug fix in the upstream version (a
Co
Public bug reported:
We backported RDMA/hns support for HiSilicon hip08 systems in bug
1756097. I noticed that there's a new commit that fixes a bug in this
support that should also be backported:
commit 38759d6175d338fbf9282c8ea2b51f3b7ab9bc98
Author: Colin Ian King
Date: Mon Mar 26 16:10:18
** Changed in: kernel-sru-workflow/snap-release-to-candidate
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/1761438
Title:
linux: 4.4.0-120.144 -proposed
Fix verified on linux-image-4.13.0-39-generic/artful-proposed.
Thank you for the great work!
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubu
I built another test kernel with a revert of the following commits:
0ce3fca PCI / PM: Restore PME Enable after config space restoration
de3ef1e PM / core: Drop run_wake flag from struct dev_pm_info
0847684 PCI / PM: Simplify device wakeup settings code
The test kernel can be downloaded from:
http
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
--- Comment From wenxi...@us.ibm.com 2018-04-10 11:41 EDT---
Naveed, Can you verify the kernel if you want the patch in Ubuntu18.04?
--
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/1
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also affects: linux (Ubuntu Bionic)
Importance: High
Status: 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
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
** Tags added: artful
--
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/1762652
Title:
perf DWARF unwind failed
Status in linux package in Ubuntu:
Incomplete
Bug description:
Ubuntu 1
** Changed in: linux (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/1762462
Title:
PSL traces reset after PERST for debug AFU image
Status in
Ok, I will investigate as soon as I have time. By the way, I am
wondering if using BFQ as I/O scheduler can be the problem, ie:
# cat /etc/udev/rules.d/60-schedulers.rules
## set noop scheduler for non-rotating disks
ACTION=="add|change", KERNEL=="sd[a-z]", ATTR{queue/rotational}=="0",
ATTR{queu
This Problem persist at kernel 4.13.0.32 i report the same problem in all
kernels
4.13.0.36 - Bug Report #1751622
4.13.0.37 - Bug Report #1757548
Afect too TP-Link TL-WN822N
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
ubuntu@alekhin:~$ cat /proc/version
Linux version 4.13.0-39-generic (buildd@bos02-arm64-024) (gcc version 5.4.0
20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9)) #44~16.04.1-Ubuntu SMP Thu Apr
5 16:44:45 UTC 2018
ubuntu@alekhin:~$ dmesg | grep "failed to claim resource for efifb"
** Tags removed:
Will try to do so, but Friday at the earliest since I am not at home during
the week.
Hope I get it right with uninstalling VirtualBox and stuff and getting all
necessary packages for the mainline build.
Joseph Salisbury schrieb am Di., 10. Apr.
2018, 17:51:
> Would it be possible for you to tes
** Also affects: linux (Ubuntu Bionic)
Importance: High
Assignee: Canonical Kernel Team (canonical-kernel-team)
Status: In Progress
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ke
Tested with 4.16
kernel-bug-exists-upstream
--
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/1762535
Title:
BUG: unable to handle kernel paging request at 9cca20d6e1a0
Status in linu
** Also affects: linux (Ubuntu Bionic)
Importance: High
Assignee: Canonical Kernel Team (canonical-kernel-team)
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, w
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I may have experienced this issue also on bionic (18.04) with the
current kernel version as of today (4.15.0-13.14).
I upgraded one affected system with "do-release-upgrade -d". After
completing the upgrade and rebooting, the system froze the same way as
with the affected 17.10 kernel and microcod
Thanks Paolo and Seth for looking into this and the patches. There's a
few things that could be done to make life on the pi better. For
example, are there any plans to add support for the relatively new pi3b+
to bionic? Adding efi stub to the raspi2 kernels would be great. The
upstream and down
You have been subscribed to a public bug:
It looks like the usbip package is very outdated and expects old kernel
modules:
root@ubuntu64:~# lsmod | grep usbip
usbip_host 28672 0
usbip_core 36864 1 usbip_host
root@ubuntu64:~# usbipd -D
usbip err: stub_driver.c: 33 (open_
Removing packages from bionic:
usbip 0.1.7-3 in bionic
libusbip-dev 0.1.7-3 in bionic amd64
libusbip-dev 0.1.7-3 in bionic arm64
libusbip-dev 0.1.7-3 in bionic armhf
libusbip-dev 0.1.7-3 in bionic i386
libusbip-
Debian builds a binary package usbip from the kernel package. Should
that be done in Ubuntu as well?
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubu
the usbip source is now removed from 18.04 LTS. reassigning to the
kernel package
** Package changed: usbip (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/165483
'kernel-fixed-upstream'
after removing all older kernel versions and another reboot, the Problem
seems to be fixed. First was seen after upgrading from 17.10.
Thank you so much.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
Linux-next commit 2be8ffed093b91536d52b5cd2c99b52f605c9ba6 does not
apply cleanly to v4.15. The commit was cc'd to upstream stable, but
without a backport. I'd like to see what upstream stable applies for a
backport.
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Triaged
** Ta
> I may have experienced this issue also on bionic (18.04) with the
current kernel version as of today (4.15.0-13.14).
I have a system running bionic and it's fine (see #34). Always has been. It's
never run anything else (just over 2 weeks old...). It's always had the "new"
(3.20180312.0~ubuntu1
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1723717
and then change the status of the bug to 'Confirmed'.
If, due to the nature
--- Comment From jos...@br.ibm.com 2018-04-10 12:56 EDT---
Hello Indira!
Not yet. I just checked the most recent upstream version and the code
fix isn't there. I'll keep my eye on the next updates.
--
You received this bug notification because you are a member of Kernel
Packages, which i
On 04/10/2018 11:43 AM, Janne Snabb wrote:
> I may have experienced this issue also on bionic (18.04) with the
> current kernel version as of today (4.15.0-13.14).
It wouldn't be this same exact bug as the 4.15.0-13.14 kernel doesn't
call __ptrace_may_access() when deciding to make use of IBPB whi
Ok I troubleshot this problem.
Apparently, it came from the package `connman`, an Intel utility to
manage wlan and bluetooth that I installed wrongly since it's intended
for embedded systems.
Removing it solved all my problems.
** Package changed: bluez (Ubuntu) => connman (Ubuntu)
** Changed i
** 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.launchpad.net/bugs/1762758
Title:
Replace LPC patchset with upstream version
Status
I started a kernel bisect between v4.15-rc2 and v4.15-rc3. The kernel
bisect will require testing of about 7-10 test kernels.
I built the first test kernel, up to the following commit:
78d9b048446c3c0a83313444fb706f8f3bccdae7
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsali
** 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.launchpad.net/bugs/1762755
Title:
Support cq/rq record doorbell for RDMA on HSilicon
** 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.launchpad.net/bugs/1762757
Title:
RDMA/hns: ensure for-loop actually iterates and fr
Well this is more about the user space tool perf, not really the kernel
itself. And I can't really imagine why DWARF unwinding would have
anything to do with the kernel used. I'm on stock ubuntu
4.13.0-38-generic btw.
When I compile perf from the kernel source (commit
2bf1ab321a06a7faeb95c56d02139
Yes, the problem does occur in mainline 4.16 and I have added the
requested tag.
If anything, 4.16.1 seems slower than 4.15 release kernel even for no
cryptswap. It could be that my disk is too slow for cryptswap, but it
did work in 17.10.
The obvious work around is not to use cryptswap, of cour
101 - 200 of 295 matches
Mail list logo
