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:
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 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
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
** 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
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
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.
** 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 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
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
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
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
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:
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
** 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:
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:
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
** 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
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
** 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
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
@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
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
** 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
** 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
--- 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
101 - 145 of 145 matches
Mail list logo
