** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
** Changed in: hwe-next
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
Many thanks, iLugo!
I followed your instructions from 2018-07-09 and wmplayer 12.5.9 worked at
once! I run ubuntu 18.04.
Before that it wouldn't start with this error: Relink `/lib/x86_64
-linux-gnu/libbsd.so.0' with `/lib/x86_64-linux-gnu/librt.so.1' for
IFUNC symbol `clock_gettime'.
Great
Dear Joseph
Unfortunately, installing
vmlinuz-4.19.0-041900rc2-generic
with modules did not help. Both pm-suspend and pm-hibernate freeze the system -
pm-hibernate succeeded partially only, i.e. the fan runs and the power led is
not flashing.
By the way, I could not install the headers due to
testing with kernel image provide by Joseph, all passed.
Thanks Joseph!
--
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/1771248
Title:
[ICL] SPI support
Status in intel:
Fix
You have been subscribed to a public bug:
== Comment: #0 - Michael Ranweiler - 2018-09-10
19:26:14 ==
Due to a recent change for powernv, now the total GPU memory is no
longer available. This impacts performance for any application/benchmark
has a large GPU memory utilization.
Previous amount
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1783746
Title:
ipmmu is always registered
Status in
This bug has been waiting for feedback for questions in comment #35 and
#36 for months. I'm going to mark this bug as Won't fix because of
limited responses. If this bug is still an issue, please re-open it.
** Changed in: zfs-linux (Ubuntu)
Status: Incomplete => Won't Fix
--
You
Public bug reported:
We are seeing deadlocks during hotplug of devices under vfio.
As per the Linux kernel source code, there is a deadlock situation
between vfio_pci_remove() and vfio_pci_release() on PCIe hotplug events.
This issue can be avoided either by skipping the PCIe reset
Public bug reported:
I cannot load a kernel beyond 4.15.0-32-generic on my machine.
Both 4.15.0-33-generic and 4.15.0-34-generic hang at "loading initial
ramdisk...".
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-34-generic 4.15.0-34.37
ProcVersionSignature: Ubuntu
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/1792100
Title:
Boot hangs at "loading
Unfortunately this won't make it to the bionic kernel. For 4.15, as a
temporary solution, please try
https://launchpad.net/~wenchien/+archive/ubuntu/rtl8821c .
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
** Changed in: kernel-sru-workflow/promote-to-proposed
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/1791745
Title:
linux: 4.4.0-136.162
AaronMa, does your model have NFC? You can tell by a symbol printed on
the touchpad just below the middle physical button of the trackpoint,
looks like this one: https://i.redd.it/el9qai4evu811.jpg
I'm now on kernel 4.18.7 and that does not help in any way. I also tried
installing the libinput
** Description changed:
+ [Impact]
+
+ Attempts to hotplug devices shared to userspace (qemu) via vfio triggers
+ a deadlock in the kernel. A reboot is required to resolve this.
+
+ [Test Case]
+
+ Set up a KVM instance with attached devices, attempt to hotplug those
+ using ipmitool.
+
+
--- Comment From mranw...@us.ibm.com 2018-09-12 02:26 EDT---
This bug is difficult to recreate - I don't have a number for about how often
it happens. I ran through about 10 cycles (sysrq c) and I haven't been able to
recreate it on the test kernel.
--
You received this bug
I did NOT solve the dependency problem, and headers were not installed.
--
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/1790606
Title:
Acer Aspire ES-512 cannot hibernate/suspend on
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Description changed:
This bug is for tracking the upload package. This
bug will contain status
script output from a recreate on bionic demonstrating the failure
** Attachment added: "script.broken"
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1792189/+attachment/5188055/+files/script.broken
--
You received this bug notification because you are a member of Kernel
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-trusty
** Tags added: block-proposed
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that
Patch to add the dependency
** Patch added: "linux-firmware_1.173.1ubuntu1_source.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1792189/+attachment/5188056/+files/linux-firmware_1.173.1ubuntu1_source.debdiff
--
You received this bug notification because you are a
script output from bionic with a linux-firmware deb with the above patch
applied performing the installation without issue
** Attachment added: "script.fix"
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1792189/+attachment/5188057/+files/script.fix
--
You received this bug
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 1769937
and then change the status of the bug to 'Confirmed'.
If, due to the
I built a test kernel with the patch posted in comment #12. The test kernel
can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1789118
Can you test this kernel and see if it resolves this bug? If it does,
I'll submit it as an SRU, so we don't have to wait for the patch to come
down
I built a 18.10 test kernel using the latest master-next branch of the
repo. This branch has the patch applied.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1789146
Can you test this kernel and see if it resolves this bug?
--
You received this bug
** Also affects: zfs-linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: zfs-linux (Ubuntu Cosmic)
Importance: Medium
Assignee: Colin Ian King (colin-king)
Status: In Progress
** Also affects: zfs-linux (Ubuntu Bionic)
Importance: Undecided
Public bug reported:
Since the recent update (kernel included) the laptop will wakeup several
seconds after sleep. The problem seems to be related to USB3.0 since
running `echo XHC1 > /proc/acpi/wakeup` solved the problem.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package:
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1791749
Title:
linux-aws: 4.4.0-1068.78
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/1792183
Title:
Wakeup immediately after
** Description changed:
+ == SRU Justification, Xenial, Bionic ==
+
+ Bug:
+
When creating a pool with the -t option on Ubuntu 18.04 LTS, it will
report an error and return a non-zero exit code, but the pool appears to
be successfully created.
For example:
# zpool create -O
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
Hi Joseph,
As this problem only affects 32-bit, there would need to be an i686
kernel there. As far as I can see there are only amd64 packages.
I have already tested this patch on the linux source package from 18.04
(comment #9), but I don't have the binary packages around any more.
If you want
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) =>
** Tags removed: verification-done-xenial
** Tags added: verification-required-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1781364
Title:
Kernel error "task zfs:pid
I built a Bionic test kernel with a revert of commit 120645513f55. The test
kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1736390
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic)
Public bug reported:
In bug #1646197 the linux-firmware.postinst was added to call update-
initramfs (provided by initramfs-tools. If the initramfs-tools package
is not installed the installation of linux-firmware will fail.
Recreate:
sudo apt-get purge --assume-yes '^linux-.*' 'linux-base+'
It is solved with proposed kernel on Xenial, tag updated
:~# uname -a
Linux pf42.mutu.online.net 4.4.0-136-generic #162-Ubuntu SMP Tue Sep 11
15:12:40 UTC 2018
:~# cat /sys/devices/system/cpu/vulnerabilities/l1tf
Mitigation: PTE Inversion
** Tags removed: verification-needed-xenial
** Tags
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1791751
Title:
linux-kvm:
apport-collect ignores local proxy and hangs.
apport-bug doesn't show any relevant information and does not find any
crash-reports (because there's noc crash, but only a dark screen)
all necessary info should be available in initial post.
if there is further detailled-information needed, give
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in:
Hi Joseph,
Give me a moment to try testing the upstream kernel; I haven't done that
before.
This issue was first reported by a customer sometime back, we worked
around it by changing the way we called fallocate. I believe I confirmed
it back in 16.04, but I haven't tested beyond that.
Charles
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188113/+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: "PciNetwork.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188111/+files/PciNetwork.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/1789949/+attachment/5188115/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188114/+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: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188112/+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: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188101/+files/Dependencies.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: "IpAddr.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188102/+files/IpAddr.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188103/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1789949/+attachment/5188100/+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/1789949/+attachment/5188119/+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/1789949/+attachment/5188118/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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.19
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 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
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 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
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.19
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.19
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.19
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 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
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Bionic)
Status: New => Triaged
**
Absolutely, please allow a few days until I have access to the device
it's not mine)
--
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/1791372
Title:
Keyboard backlight not working on Asus
very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.
** Changed in: ubuntu-kernel-tests
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 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
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** 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.
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 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
closing bug per last comment
** Changed in: ubuntu-kernel-tests
Status: New => Won't Fix
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.
** Changed in: ubuntu-kernel-tests
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a
very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.
** Changed in: ubuntu-kernel-tests
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 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
very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.
** Changed in: ubuntu-kernel-tests
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: linux (Ubuntu Xenial)
Status:
Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of a
regression, and when this regression was introduced. If this is a
regression, we can
** Summary changed:
- linux-kvm: -proposed tracker
+ linux-kvm: 4.15.0-1022.22 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
parsing through ubuntu-kernel-tests bugs, this one is actively being
worked on, taking ownership and will touch base when I'm done.
** Changed in: ubuntu-kernel-tests
Status: New => In Progress
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Sean Feole (sfeole)
**
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 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
Hi Sam, is this still an issue?
+60 day bug with no action on it, marking bug as incomplete and will
close in 5 days if no update.
** Changed in: ubuntu-kernel-tests
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 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
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.19
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 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
the reported bug was marked invalid, doing the same here
** Changed in: qa-regression-testing
Status: New => Invalid
** Changed in: ubuntu-kernel-tests
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification
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.19
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
apport information
** Attachment added: "AplayDevices.txt"
https://bugs.launchpad.net/bugs/1791979/+attachment/5188078/+files/AplayDevices.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/1791979/+attachment/5188081/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1791979/+attachment/5188082/+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: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1791979/+attachment/5188080/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
The USB devices are detected/enumerated correctly with system start, but when
disconnected later and connected once again are not recognized / enumerated
anymore.
Also removal of ci_hdrc_imx module causes the
I built a 4.15.0-35 test kernel.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1792100
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 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
I've checked behaviour of generic armhf kernel 4.18.7 from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18.7/
and the bug I report is not visible there - I can connect / disconnect USB
device from host and is is properly enumerated, also can unload/load
ci_hdrc_imx module and keep USB host
I built a 4.15.0-35 test kernel.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1792100
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the
Can you see if this bug still exists in the latest Cosmic 4.18 based
kernel?
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also affects: linux (Ubuntu Cosmic)
Importance: High
Status: Confirmed
** Tags added: kernel-key
--
You received this bug notification
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1791979/+attachment/5188085/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
The upstream bug states that the following commit resolves this bug:
7306e32 drm/i915/bios: filter out invalid DDC pins from VBT child
devices
That commit has been in Bionic since v4.15.0-23. Do you still see this
bug with that kernel or newer?
** Tags added: bionic kernel-da-key
--
You
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
yes, unfortunately we still see this bug (else we haven't filed it
here).
so, when the given patch is already added in -23 and we're using -33, it
seems to be that that patch doesn't help for our problem, even the
behaviour is really similar.
so. should we file a bug at freedesktop?
--
You
1 - 100 of 279 matches
Mail list logo
