--- Comment From heinz-werner_se...@de.ibm.com 2018-08-03 02:48 EDT---
IBM Bugzilla status -> closed; Problem solved with latest kernel
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
+ == Justification ==
+ In the Xenial / Bionic KVM kernel, the CONFIG_ZRAM was not set, it's
impossible for users to use zram module on it. And the ubuntu_zram_smoke_test
regression test is failing due to the missing module.
+
+ == Test ==
+ Before enabling CONFIG_ZRAM
Public bug reported:
This test failed due to:
mkfs.vfat: /dev/loop0 contains a mounted filesystem.
tst_mkfs.c:94: BROK: mkfs.vfat:1: tst_test.c failed with 732
<<>>
tag=fallocate05 stime=1533288629
cmdline="fallocate05"
contacts=""
analysis=exit
<<>>
tst_device.c:230: INFO: Using test
Public bug reported:
<<>>
tag=shmctl05 stime=1533290233
cmdline="shmctl05"
contacts=""
analysis=exit
<<>>
tst_test.c:1018: INFO: Timeout per run is 0h 00m 20s
incrementing stop
tst_safe_sysv_ipc.c:111: BROK: shmctl05.c:51: shmget(61455, 4096, 3c0) failed:
ENOSPC
shmctl05.c:104: WARN:
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/1785209
Title:
shmctl05 in
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/1785207
Title:
openat03 in
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/1785204
Title:
keyctl06.c in
** Summary changed:
- linux-oem: -proposed tracker
+ linux-oem: 4.15.0-1014.17 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-signed
Assignee: Canonical Kernel Team
Including VFIO in the kernel would be great! This would resolve all
kinds of pass-through crashes.
Currently, the only way to do this is to hope that the USB controller
behaves properly during reclamation by the kernel (most of them do not),
which varies wildly by vendor. In my case, it gets as
** 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 and testing results related to that upload.
For an explanation of the tasks and the
** Summary changed:
- fallocate05 in ubuntu_ltp_syscall failed with Trusty
+ fallocate05 / fsync01 in ubuntu_ltp_syscall failed with mkfs.vfat error on
Trusty
** Description changed:
This test failed due to:
- mkfs.vfat: /dev/loop0 contains a mounted filesystem.
- tst_mkfs.c:94:
I still think there are multiple bugs here. Some of us have a network that
absolutely will not come back up after suspend with kernel version
>4.15.0-23, even after reloading the driver. So there is a very clear
regression that I would really like see resolved / rolled back. Breaking
stuff in an
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux-kvm (Ubuntu)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux-kvm (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-kernel-tests
Well, what is the situation ? I really need this bug fixed !!!
This morning I had to make a Presentation on a Projector in front of a
couple of people.
Since I am running in "recovery mode" with no Video Drivers loaded (lshw
-c video -> Display: UNCLAIMED), the system didn't detect my secondary
Public bug reported:
<<>>
tag=keyctl06 stime=1533289300
cmdline="keyctl06"
contacts=""
analysis=exit
<<>>
tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s
incrementing stop
keyctl06.c:64: FAIL: KEYCTL_READ overran the buffer
Summary:
passed 0
failed 0
skipped 0
warnings 0
ProblemType:
** Changed in: linux-kvm (Ubuntu)
Status: New => 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/1782721
Title:
DEBUG_WX is not set in Bionic KVM kernel
Status
Maybe try 'acpi_osi=! acpi_osi="Windows 2009"'.
--
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/1784878
Title:
Backlight Not Functional - Origin EVO 15-S (Clevo)
Status in linux package
Public bug reported:
<<>>
tag=openat03 stime=1533289807
cmdline="openat03"
contacts=""
analysis=exit
<<>>
openat030 TINFO : creating a file with O_TMPFILE flag
incrementing stop
openat030 TINFO : writing data to the file
openat030 TINFO : file size is '4096'
openat030
Ok, I can confirm what I wrote on #28 on another installation.
Very hard for me to tackle this down - since bisecting obviously didn't
work.
Here is a summary of what I found out about this bug:
- Artful (or any other previous Ubuntu version) was not affected (at least not
to that extend, see
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/1785198
Title:
mkfs.vfat is causing failure
** Summary changed:
- fallocate05 / fsync01 / msync04 in ubuntu_ltp_syscall failed with mkfs.vfat
error on Trusty
+ [T] mkfs.vfat is causing failure on fallocate05 / fsync01 / msync04 /
preadv03 / pwritev03 / setxattr01 tests in ubuntu_ltp_syscall on Trusty
** Summary changed:
- [T] mkfs.vfat
** Changed in: gnome-shell (Ubuntu)
Status: Fix Committed => Fix Released
** No longer affects: gnome-shell (Ubuntu Bionic)
** Changed in: mutter (Ubuntu Bionic)
Status: New => In Progress
** Changed in: mutter (Ubuntu Bionic)
Importance: Undecided => High
** Changed in:
I think it's basically the same one as
https://bugzilla.redhat.com/show_bug.cgi?id=1543769
** Bug watch added: Red Hat Bugzilla #1543769
https://bugzilla.redhat.com/show_bug.cgi?id=1543769
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
@Kai-Heng
Weird, I reinstalled and tested 4.15.0-23 again, and it seems that with
4.15.0-23 it can also happen that network is not coming up after suspend and
the driver has to be reloaded.
I'm going to further test this on another installation.
--
You received this bug notification because
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
Public bug reported:
So far I have only triggered this while running bitcoind (or bitcoin-qt)
with the z3fold module loaded. I will do further testing to see if I can
trigger it any other ways.
[54075.373045] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kswapd0:41]
[54075.377042] watchdog:
** Summary changed:
- linux-azure: -proposed tracker
+ linux-azure: 4.15.0-1020.20~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-signed
Assignee: Canonical Kernel
** Description changed:
After a new Kernel e.g. 4.4.0-131 is installed on our Ubuntu 16.04 LTS
clients, unneeded (waste) 14 bytes paddings are unexpectedly present
after PPPoE payload in client's Ethernet frames which are sent towards a
NAS access router. The content of such a waste
** Also affects: nvidia-settings (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-settings (Ubuntu)
Importance: Undecided => High
** Changed in: nvidia-settings (Ubuntu)
Status: New => In Progress
** Changed in: nvidia-settings (Ubuntu)
Assignee:
Can you attach dmesg under latest mainline kernel?
--
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/1783957
Title:
Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no
** Summary changed:
- linux-gcp: -proposed tracker
+ linux-gcp: 4.15.0-1016.17~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
** Description changed:
This test failed due to:
mkfs.vfat: /dev/loop0 contains a mounted filesystem.
tst_mkfs.c:94: BROK: mkfs.vfat:1: tst_test.c failed with 732
fallocate05 / fsync01 / msync04 / preadv03 / preadv03_64 / pwritev03 /
pwrite03_64 / setxattr01 are failing with
Since dae55b6 is tagged with v4.17-rc1~78^2~13 and we have 4.17 in
cosmic proposed, I change 'linux (Ubuntu)' to Fix Committed.
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: kernel-sru-workflow/snap-release-to-stable
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1784292
Title:
linux-azure:
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
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/1781535
Title:
qdio: don't retry EQBS after CCQ 96
Status in
$ git tag --contains fa89adba1941e4f3b213399b81732a5c12fd9131 Ubuntu-4.17.0-6.7
Ubuntu-4.17.0-6.7
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Public bug reported:
This bug is for tracking the 4.17.0-7.8 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
** Affects:
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
comm stress-ng: bg 4705: bad block bitmap
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
comm stress-ng: bg 4705: bad block bitmap
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
comm stress-ng: bg 4705: bad block bitmap
*** This bug is a duplicate of bug 1783396 ***
https://bugs.launchpad.net/bugs/1783396
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
comm stress-ng: bg 4705: bad block bitmap
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
comm stress-ng: bg 4705: bad block bitmap
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
comm stress-ng: bg 4705: bad block bitmap
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
comm stress-ng: bg 4705: bad block bitmap
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
comm stress-ng: bg 4705: bad block bitmap
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
comm stress-ng: bg 4705: bad block bitmap
$ git tag --contains dae55b6 Ubuntu-4.17.0-6.7
Ubuntu-4.17.0-6.7
And released.
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
comm stress-ng: bg 4705: bad block bitmap
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
comm stress-ng: bg 4705: bad block bitmap
Please try this kernel:
https://people.canonical.com/~khfeng/bionic-r8169-backport/
--
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/1784542
Title:
Realtek ethernet not functional on
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
comm stress-ng: bg 4705: bad block bitmap
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
comm stress-ng: bg 4705: bad block bitmap
** Description changed:
After a new Kernel e.g. 4.4.0-131 is installed on our Ubuntu 16.04 LTS
clients, unneeded (waste) 14 bytes paddings are unexpectedly present
after PPPoE payload in client's Ethernet frames which are sent towards a
- NAS access router. The content of the waste padding
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-release
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for
The commits that causes the regression is a fix for another issue, LP:
#1752772. So we can't simply revert those fixes because it will regress
other users.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Looks like it's i386 instead of AMD64?
Please try linux-next [1] since there are some new PTI fixes.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
comm stress-ng: bg 4705: bad block bitmap
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
comm stress-ng: bg 4705: bad block bitmap
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
comm stress-ng: bg 4705: bad block bitmap
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
comm stress-ng: bg 4705: bad block bitmap
Please try this kernel:
https://people.canonical.com/~khfeng/bionic-r8169-backport/
--
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/1779817
Title:
r8169 no internet after suspending
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
comm stress-ng: bg 4705: bad block bitmap
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
comm stress-ng: bg 4705: bad block bitmap
*** This bug is a duplicate of bug 1783396 ***
https://bugs.launchpad.net/bugs/1783396
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error
*** This bug is a duplicate of bug 1783396 ***
https://bugs.launchpad.net/bugs/1783396
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error
*** This bug is a duplicate of bug 1783396 ***
https://bugs.launchpad.net/bugs/1783396
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
comm stress-ng: bg 4705: bad block bitmap
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
comm stress-ng: bg 4705: bad block bitmap
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
comm stress-ng: bg 4705: bad block bitmap
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
comm stress-ng: bg 4705: bad block bitmap
This bug was fixed in the package linux - 4.17.0-6.7
---
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
comm stress-ng: bg 4705: bad block bitmap
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Cosmic)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Any progress on this? The bug is still biting me.
--
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/1776887
Title:
Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
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/1785204
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
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/1785207
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
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/1785198
You might be right!
--
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/1778087
Title:
ELAN1200 touchpad jumps around and disconnects
Status in linux package in Ubuntu:
Confirmed
Bug
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
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/1785209
Hi Joseph, thanks for your response.
The issue started to happen since we started to run on this cloud, which
was around 2 months ago more or less. So I am not sure if before that
the issue was present.
This kernel should be handled in the baremetal host, right?
If so, I'll try to see if our
** 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
I think I've found a workaround for this issue, in my case adding 'acpi_osi='
to the linux kernel parameters solved it.
I am running a Dell Inspiron 15 5577 (with latest BIOS, v1.1.0).
For a permanent solution, I changed this line at:
```/etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet
** Description changed:
This is a request to make a change in the hv-kvp-daemon systemd service
which is part of the linux-cloud-tools-common package to ensure the hv-
kvp-daemon service starts before the walinuxagent service. The default
dependencies make hv-kvp-daemon wait until the
You have been subscribed to a public bug:
I've turned up many, many new server and workstation systems over the
years on both Linux and Windows. Never seen anything like this behaviour
I'm witnessing on Ubuntu Server 18.04 before where I simply lose
Internet connectivity while using a browser.
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this
** 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/1784302
Title:
linux: 4.4.0-132.158
** Description changed:
This is a request to make a change in the hv-kvp-daemon systemd service
which is part of the linux-cloud-tools-common package to ensure the hv-
kvp-daemon service starts before the walinuxagent service. The default
dependencies make hv-kvp-daemon wait until the
VGA fix has been released in ver. 4.18 rc7. SSDT will not be fixed I
think.
--
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/1776563
Title:
Acer Aspire A315 IOAPIC failure on
** 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
** Package changed: 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/1785171
Title:
Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver
keeps
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Tags removed: kernel-key
--
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/1783358
Title:
Xenial linux 4.15.0-29-generic kernel panic.
Status in linux package in Ubuntu:
Confirmed
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.18
Confirming the fix in in the latest kernel release, can you point in the
direction of the original bug, as I've not been able to find a reference to it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hello
I have the same problem since 4 years!
I can perfectly use this key on a usb2 port.
I can not detect this key on a usb3 port. The dmesg command sees nothing
at all!
But if I plug it with an adapter cable to the usb3 standard, it is seen
but remains unusable.See file USB3.txt
However,
Bougron (francis-bougron), it most helpful if you use the computer the problem
is reproducible with, and provide necessary debugging logs by filing a new
report with Ubuntu via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
** Attachment removed: "seven seven failures on
*** This bug is a duplicate of bug 1709889 ***
https://bugs.launchpad.net/bugs/1709889
** This bug has been marked a duplicate of bug 1709889
Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for
a very long time.
--
You received this bug notification because you
*** This bug is a duplicate of bug 1763594 ***
https://bugs.launchpad.net/bugs/1763594
** This bug has been marked a duplicate of bug 1763594
xhci hangs; reset results in NULL pointer dereference
--
You received this bug notification because you are a member of Kernel
Packages, which is
** 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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1784306
Title:
linux-aws:
*** This bug is a duplicate of bug 1763594 ***
https://bugs.launchpad.net/bugs/1763594
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** This bug has been marked a duplicate of bug 1763594
xhci hangs; reset results in NULL pointer dereference
--
You received this bug
1 - 100 of 145 matches
Mail list logo
