LibreOffice Base still crash with test kernel:
~$ uname -a
Linux WS 4.4.0-112-generic #135~lp1699772v2 SMP Thu Feb 22 00:00:50 UTC 2018
i686 i686 i686 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
The 4.4.0-116-generic still hangs my laptop during boot the same way
-112 did. And noibpb still solves the problem.
--
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/1745349
Title:
Hard loc
Public bug reported:
after installing Kernel 4.13.0.36 it disables or stops my wireless card
, i have tried that many times.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which
The kernel was compiled in Bionic, so it has wrong dependency on Xenial.
I built a new one, please give it a try:
http://people.canonical.com/~khfeng/lp1447664-xenial/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
You have been subscribed to a public bug:
This failure could be found on both Moonshot and Cavium ThunderX ARM64
systems.
Steps:
1. Install necessary packages
2. git clone --depth=1
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
3. cd kvm-unit-tests; ./configure; make
4. TESTNAME
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 1750986
and then change the status of the bug to 'Confirmed'.
If, due to the nature
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1751000/+attachment/5060190/+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
Public bug reported:
This failure could be found on both Moonshot and Cavium ThunderX ARM64
systems.
Steps:
1. Install necessary packages
2. git clone --depth=1
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
3. cd kvm-unit-tests; ./configure; make
4. TESTNAME=pmu TIMEOUT=90s ACCE
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1751000/+attachment/5060193/+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
--- Comment From shriy...@in.ibm.com 2018-02-22 03:43 EDT---
Hi ,
Can you please let us know in which build we are expecting the fix ?
Thanks
--
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: "Lspci.txt"
https://bugs.launchpad.net/bugs/1751000/+attachment/5060189/+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/1751000
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1751000/+attachment/5060187/+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/1751000
Ti
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1751000/+attachment/5060188/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1751000/+attachment/5060194/+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/1751000
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1751000/+attachment/5060195/+files/WifiSyslog.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/bug
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1751000/+attachment/5060192/+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: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1751000/+attachment/5060191/+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
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 1751000
and then change the status of the bug to 'Confirmed'.
If, due to the nature
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/snap-release-to-stable
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for tra
It's still failing on Xenial, let keep this bug open.
# TESTNAME=emulator TIMEOUT=90s ACCEL= ./powerpc/run powerpc/emulator.elf -smp 1
timeout -k 1s --foreground 90s /usr/bin/qemu-system-ppc64 -nodefaults -machine
pseries,accel=kvm -bios powerpc/boot_rom.bin -display none -serial stdio
-kernel p
You were using 16.10, did the suspend work in 16.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/1740175
Title:
Ubuntu 17.10 not resuming from suspend, freezing on shut down
Status i
This bug is the same as #1745349 and is not solved with 4.4.0-116 but
can be prevented with the noipbp kernel option.
--
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/1748505
Title:
Boot f
** Summary changed:
- Failed to build upstream bpf test on Artful ppc64le
+ Failed to build upstream bpf test on Artful/Bionic ppc64le
** Tags added: bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
Please find the first bad -rc* kernel between v4.10 to v4.13 from [1]
that has this issue, thanks.
http://kernel.ubuntu.com/~kernel-ppa/mainline
--
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
Am 22.02.2018 um 09:05 schrieb ake sandgren:
> The 4.4.0-116-generic still hangs my laptop during boot the same way
> -112 did. And noibpb still solves the problem.
Confirming for Asus H110M-C boards, still the hardlocks.
--
You received this bug notification because you are a member of Kernel
P
Hi Po-Hsu,
are you still debugging this - or do you want to ask this to be mirrored to IBM?
It could again be something that is only working in latter versions - and
depending on the change we might (or not) backport the fix.
--
You received this bug notification because you are a member of Kern
Public bug reported:
The .retpoline files in the current abi are actually blank.
This is due to incorrect handling in retpoline-extract.
** Affects: linux (Ubuntu)
Importance: High
Assignee: Andy Whitcroft (apw)
Status: In Progress
** Changed in: linux (Ubuntu)
Status:
** Tags added: bionic
--
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/1711299
Title:
ubuntu_bpf test failed to build on s390x system
Status in linux package in Ubuntu:
Confirmed
Status
Public bug reported:
Hi,
Applying the Spectre/Meltdown patched kernel (3.2.0-133-generic -
precise ESM), it's not possible to boot my xen domUs anymore (dom0 is
fine). It works fine with 3.2.0-131-generic and 3.13.0-141-generic (lts-
trusty with Spectre/Meltdown mitigations).
This is with xen 4.
$ cat /proc/version_signature
Ubuntu 3.13.0-141.190~precise1-generic 3.13.11-ckt39
$ sudo lspci -vnvn
00:03.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] ES1000 [1002:515e] (rev 02) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Device [103c:
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-propos
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-precise
** Tags removed: block-proposed
--
You received this bug notification because you
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 1751028
and then change the status of the bug to 'Confirmed'.
If, due to the nature
*** This bug is a duplicate of bug 1554613 ***
https://bugs.launchpad.net/bugs/1554613
Very similar situation here, however:
In my case there is absolutely no prediction of crashing. It just
happens: instant shutdown followed by automatic reboot. Nothing to be
seen in the logs. Happens under
I updated again this morning and installed the latest 4.13.0-36-generic
kernel. Unfortunately it still panics on boot. I've attached another
slo-mo video.
** Attachment added: "Slo-mo video of failing boot of 4.13.0-36-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742675/+atta
No message comes from the terminal when press the hotkey (only the wifi
one), the other events are detected normally.
--
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/1745636
Title:
RT3290
On 4.15.4 I see a lot of:
Feb 21 15:43:31 localhost kernel: [18401.483078] pcieport :00:1d.6: AER:
Corrected error received: id=00ee
Feb 21 15:43:31 localhost kernel: [18401.483095] pcieport :00:1d.6: PCIe
Bus Error: severity=Corrected, type=Data Link Layer, id=00ee(Transmitter ID)
Feb 2
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1751028/+attachment/5060313/+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/1751028
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1751028/+attachment/5060311/+files/IwConfig.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/17
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1751028/+attachment/5060315/+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
** Tags added: apport-collected
** Description changed:
Hi,
Applying the Spectre/Meltdown patched kernel (3.2.0-133-generic -
precise ESM), it's not possible to boot my xen domUs anymore (dom0 is
fine). It works fine with 3.2.0-131-generic and 3.13.0-141-generic (lt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1751028/+attachment/5060318/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1751028/+attachment/5060312/+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/1751028
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1751028/+attachment/5060317/+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/1751028
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1751028/+attachment/5060314/+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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1751028/+attachment/5060310/+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
--- Comment From sthou...@in.ibm.com 2018-02-22 07:10 EDT---
Canonical, Any update on this ?
--
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/1711283
Title:
few kernel selftest fai
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1751028/+attachment/5060316/+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: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1751028/+attachment/5060309/+files/BootDmesg.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/
I have tested 4.13 final from your link and it boots up.
--
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/1746418
Title:
System freezes when starting Xorg after installing linux-
image-4
@kaihengfeng
Thanks, I will repost it there. Can confirm the adapter dropping out
with the same errors on 5520/TB16 at 1Gbps with latest 16.04 LTS though.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
It can also be prevented by booting without quit splash kernel option.
--
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/1748505
Title:
Boot failed with hard LOCKUP linux-image-4.4.0-112
S
I mean quiet, not quit. Sorry.
--
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/1748505
Title:
Boot failed with hard LOCKUP linux-image-4.4.0-112
Status in linux package in Ubuntu:
Inco
The verification of the Stable Release Update for openvswitch has
completed successfully and the package has now been released to
-updates. In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update
This bug was fixed in the package openvswitch - 2.8.1-0ubuntu0.17.10.2~cloud0
---
openvswitch (2.8.1-0ubuntu0.17.10.2~cloud0) xenial-pike; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
openvswitch (2.8.1-0ubuntu0.17.10.2) artful; urgency=medium
.
* d/p/dpif-k
Update to my October post in LP#1667750 which turned out to be a
separate issue (1Gbps mode dropouts) on the same adapter.
Dell Precision 5520 and BIOS 1.7 using TB16. This is on Ubuntu 16.04.3,
kernel 4.13.0
The issue is still present. I tried limiting the bandwidth using
`ethtool -s eth0 speed
Are these self-test failures leading to any "real-world" or workload-
related issues? If so, we will reprioritize.
** Changed in: linux (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubunt
Hi, I do not believe canonical is committing to fix all the
upstream/mainline selftest failures. However, if there are additional
selftest regressions with the ubuntu kernel which are not seen with the
mainline build, those are worth looking into. If these selftests never
pass on POWER maybe it is
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 directly
** Description changed:
-
- 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 originat
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
This bug was fixed in the package linux - 3.13.0-142.191
---
linux (3.13.0-142.191) trusty; urgency=medium
* linux: 3.13.0-142.191 -proposed tracker (LP: #1746900)
* CVE-2017-17806
- crypto: hmac - require that the underlying hash algorithm is unkeyed
* CVE-2017-18017
This bug was fixed in the package linux - 3.13.0-142.191
---
linux (3.13.0-142.191) trusty; urgency=medium
* linux: 3.13.0-142.191 -proposed tracker (LP: #1746900)
* CVE-2017-17806
- crypto: hmac - require that the underlying hash algorithm is unkeyed
* CVE-2017-18017
This bug was fixed in the package linux - 3.13.0-142.191
---
linux (3.13.0-142.191) trusty; urgency=medium
* linux: 3.13.0-142.191 -proposed tracker (LP: #1746900)
* CVE-2017-17806
- crypto: hmac - require that the underlying hash algorithm is unkeyed
* CVE-2017-18017
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-updates
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Status: New => Triaged
** Changed in: ubuntu-z-systems
Importance: Undecided => High
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Canonical Kernel Team (canon
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Importance: Undecided => High
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
** Changed in: ubuntu-z-systems
Statu
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: In Progress => Fix Released
** Changed in: kernel-sru-wo
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sr
Hasn't completed testing or been integrated into the archives.
--
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/1729674
Title:
TB16 dock ethernet corrupts data with hw checksum silently fa
@pandasauce ... Fix committed means it's in the git archive, but has
completed testing nor been integrated into the archives yet.
Also please refrain from repeating things we already know in the thread
or otherwise +1'ing or me-tooing. It just wastes developers time that
could be spent actually f
Can confirm kernel makes no difference.
--
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/1750379
Title:
Distortion Realtek ALC887
Status in linux package in Ubuntu:
Incomplete
Status in
Paolo has respun a new KPTI backport:
https://git.launchpad.net/~p-pisati/ubuntu/+source/linux/log/?h=artful-master-next-arm64-kpti-414-backport
A linux/artful test build is available at:
ppa:p-pisati/arm64-kpti-backport
And a linux-hwe/xenial test build is available at:
ppa:dannf/kpti
We
I got this bug on xenial 16.04.3
kernel 4.4.0-112-generic
CPU model name: Intel(R) Xeon(R) CPU E3-1220 V2 @ 3.10GHz
$ sudo kvm-ok
INFO: /dev/kvm exists
KVM acceleration can be used
$ uname -a
Linux vmlab 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36 UTC 2018
x86_64 x86_64 x86_64 GNU/Linu
** Attachment added: "Test results from a Cavium Sabre ThunderX2 system. All
failures are expected."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5060398/+files/submission_2018-02-22T15.25.59.985213.html
--
You received this bug notification because you are a memb
Hmm, there are several subsystems might affect xHC, so we need to bisect
between v4.12 and v4.13-rc3.
Before we do that, can you try latest (v4.16-rc2) mainline kernel again?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
Fix will land in the stress-ng 0.09.17 release in the next 24 hours
--
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/1750787
Title:
enosys test in ubuntu_stress_smoke will failed on Artful
This bug was fixed in the package linux - 4.15.0-10.11
---
linux (4.15.0-10.11) bionic; urgency=medium
* linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)
* "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warni
This bug was fixed in the package linux - 4.15.0-10.11
---
linux (4.15.0-10.11) bionic; urgency=medium
* linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)
* "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warni
*** This bug is a duplicate of bug 1749250 ***
https://bugs.launchpad.net/bugs/1749250
This bug was fixed in the package linux - 4.15.0-10.11
---
linux (4.15.0-10.11) bionic; urgency=medium
* linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)
* "swiotlb: coherent allocatio
This bug was fixed in the package linux - 4.15.0-10.11
---
linux (4.15.0-10.11) bionic; urgency=medium
* linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)
* "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warni
This bug was fixed in the package linux - 4.15.0-10.11
---
linux (4.15.0-10.11) bionic; urgency=medium
* linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)
* "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warni
This bug was fixed in the package linux - 4.15.0-10.11
---
linux (4.15.0-10.11) bionic; urgency=medium
* linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)
* "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warni
*** This bug is a duplicate of bug 1749250 ***
https://bugs.launchpad.net/bugs/1749250
This bug was fixed in the package linux - 4.15.0-10.11
---
linux (4.15.0-10.11) bionic; urgency=medium
* linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)
* "swiotlb: coherent allocatio
This bug was fixed in the package linux - 4.15.0-10.11
---
linux (4.15.0-10.11) bionic; urgency=medium
* linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)
* "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warni
This bug was fixed in the package linux - 4.15.0-10.11
---
linux (4.15.0-10.11) bionic; urgency=medium
* linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)
* "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warni
This bug was fixed in the package linux - 4.15.0-10.11
---
linux (4.15.0-10.11) bionic; urgency=medium
* linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)
* "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warni
This bug was fixed in the package linux - 4.15.0-10.11
---
linux (4.15.0-10.11) bionic; urgency=medium
* linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)
* "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warni
This bug was fixed in the package linux - 4.15.0-10.11
---
linux (4.15.0-10.11) bionic; urgency=medium
* linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)
* "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warni
This bug was fixed in the package linux - 4.15.0-10.11
---
linux (4.15.0-10.11) bionic; urgency=medium
* linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)
* "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warni
This bug was fixed in the package linux - 4.15.0-10.11
---
linux (4.15.0-10.11) bionic; urgency=medium
* linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)
* "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warni
This bug was fixed in the package linux - 4.15.0-10.11
---
linux (4.15.0-10.11) bionic; urgency=medium
* linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)
* "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warni
Thanks for testing. That could mean that a SAUCE patch caused this
regression. I review the git log. If nothing sticks out, we can
perform a regular kernel bisect of the Ubuntu kernels.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
This bug was fixed in the package linux - 4.15.0-10.11
---
linux (4.15.0-10.11) bionic; urgency=medium
* linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)
* "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warni
This bug was fixed in the package linux - 4.15.0-10.11
---
linux (4.15.0-10.11) bionic; urgency=medium
* linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)
* "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warni
*** This bug is a duplicate of bug 1749250 ***
https://bugs.launchpad.net/bugs/1749250
This bug was fixed in the package linux - 4.15.0-10.11
---
linux (4.15.0-10.11) bionic; urgency=medium
* linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)
* "swiotlb: coherent allocatio
This bug was fixed in the package linux - 4.15.0-10.11
---
linux (4.15.0-10.11) bionic; urgency=medium
* linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)
* "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warni
This bug was fixed in the package linux - 4.15.0-10.11
---
linux (4.15.0-10.11) bionic; urgency=medium
* linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)
* "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warni
This bug was fixed in the package linux - 4.15.0-10.11
---
linux (4.15.0-10.11) bionic; urgency=medium
* linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)
* "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10
(LP: #1749202)
- swiotlb: suppress warni
*** This bug is a duplicate of bug 1749250 ***
https://bugs.launchpad.net/bugs/1749250
This bug was fixed in the package linux - 4.15.0-10.11
---
linux (4.15.0-10.11) bionic; urgency=medium
* linux: 4.15.0-10.11 -proposed tracker (LP: #1749250)
* "swiotlb: coherent allocatio
1 - 100 of 207 matches
Mail list logo
