[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
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/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
This is still a problem in 396.45 on Ubuntu 16.04. The minimal test case
fails, and EGL doesn't work cleanly. Tested on clean installation with
an Nvidia Titan Xp and Titan X (Pascal).
** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
Importance: Undecided
Status: New
** Also
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Incomplete
--
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 -proposed
I am experiencing what I think is the same problem with kernel
4.17.0-996-generic.
** Attachment added: "journalctl with 2 hibernation attempts"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724265/+attachment/5171300/+files/journalctl.log
--
You received this bug notification
This solved the issue for me:
https://ubuntuforums.org/showthread.php?t=2338349
Basically, what I did was
Start alsamixer with this command:
alsamixer -c1
And then:
1. Navigate to the Loopback channel rightmost with arrow-key
2. Disable the Channel by pressing the arrow-down-key once
3. Save
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1785326/+attachment/5171288/+files/dmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
Public bug reported:
1,2) Please see the apport attachments
3) Fast booting without errors as with xenial non-hwe kernels
4) The booting is too long
The errors are similar to this:
[drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR*
[CRTC:41:pipe B] flip_done timed out
@Kai-Heng
With this kernel version, unfortunately my network doesn't come up at all (even
after fresh power on. Reloading driver does not help).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Maybe this additional information will help:
*-network
description: Ethernet interface
product: Ethernet Connection (2) I219-V
vendor: Intel Corporation
physical id: 1f.6
bus info: pci@:00:1f.6
logical name: enp0s31f6
version:
Thanks for the replies.
The "Internet dropping" issue started as soon as I installed this
complete new Ubuntu Server 18.04 on the ASRock z370m Pro4 motherboard.
Then added the GNOME Desktop, and had to change the Ethernet network
configuration to use Netplan and NetworkManager service.
Note: I
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in:
Just had similar episodes as what is described here.
My CPU apparently was close to overheating (though the maximum temperature I
afterwards observed was 95°C, with a specified high/max of 100°C). The Ubuntu
18.04 on my laptop (Asus Zenbook UX301LA) consistently became unresponsive
after
Right on. Yeah apparently there are two different models for this
touchpad, AFAIK.
Good to know you have the same. Then this bug report concerns you and
feel free to add any helpful information.
You might be right, it could have been nouveau trying to take over. I
actually have nouveau
Dear Alistair,
Many thanks for having me onboard!
With regards to the touchpad model I can confirm that I have the same. I
got the same spam in my dmesg
[timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete
report (16/65535)
and that's how I came here in the first place. This was
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Fix Released
--
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: 4.4.0-1064.74
For some reason my wired connection in 18.04 suddenly stopped working.
Wifi was fine. I spend 24 hours trying everything to get it back,
including factory resetting the router, changing network cables, and
reinstalling Xubuntu many times. After fighting with Acer's buggy secure
boot system I
** 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:
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in:
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
Hello Vassilis and welcome to the bug report!
Your touchpad might be slightly different though I doubt it.
Check this out: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782653
Are you able to reload i2c_hid during runtime? I think reloading it
gives me a blackscreen
You might be right
Hello all
The same happens to my laptop that I've bought a week ago (Asus FX503VM,
GTX1060).
I had already seen that the touchpad had issues with the default 4.15
kernel on Ubuntu 18.04 that I have installed. Therefore I have installed
Ukuu and managed to load later kernels.
Indeed running
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => Fix Committed
** 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
Public bug reported:
[Impact]
ARM systems w/ an SMMUv3 that uses MSI control interrupts fail to initialize
them, which can e.g. prevent detected device errors from being reported.
[Test Case]
dmesg | grep "failed to allocate MSIs"
grep arm-smmu-v3 /proc/interrupts
[Fix]
Upstream fixes that add
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
fugounashi, it is 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.
** Changed in: linux (Ubuntu)
Status: Confirmed =>
This issue is affecting me. When I wake from suspend my ethernet
connection doesn't work, just says "connecting..."
Ubuntu 18.04
4.15.0-29-generic
r8169
This workaround succeeds:
modprobe -r r8169
modprobe -i r8169
$ uname -r
4.15.0-29-generic
$ apt policy linux-image-generic
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,
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.
** 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
** 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
Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.4 stable kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel
** 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
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 1785171
and then change the status of the bug to 'Confirmed'.
If, due to the
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 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
Updated bug description and added Bionic bug task. Marked bug 1785081
as a duplicate of this bug.
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Triaged
** Changed in: linux (Ubuntu Bionic)
*** 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
** 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 => 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
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.
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
** 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
** 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
** 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
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
** 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, 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
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
** 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.
** 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:
$ 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.
** 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
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
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 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
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
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:
** 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
1 - 100 of 145 matches
Mail list logo
