Mark:
With a LUKS encrypted system, when a new kernel is installed "update-
initramfs -u -k $KERNEL_VERSION" is executed.
As part of that cryptsetup hooks scripts are called. They examine
/etc/fstab and /etc/crypttabto determine if the root file-system, or
swap (which may be used for
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-
cosmic' to 'verification-done-cosmic'. 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-
cosmic' to 'verification-done-cosmic'. 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-
cosmic' to 'verification-done-cosmic'. 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-
cosmic' to 'verification-done-cosmic'. 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-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1779848
Title:
Cleanup Meltdown/Spectre implementation
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-
cosmic' to 'verification-done-cosmic'. 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-
cosmic' to 'verification-done-cosmic'. 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-
cosmic' to 'verification-done-cosmic'. 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-
cosmic' to 'verification-done-cosmic'. 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-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag
Status update: we believe that the off-lined cores are being
intentionally forced off-line by the f/w after f/w tests have determined
that the some cores are faulty. Waiting on IBM to confirm this
interpretation.
Marking as "Incomplete" while awaiting this confirmation.
** 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-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag
Marking as "incomplete" while awaiting test results from Thadeu's PPA
kernel.
** Changed in: ubuntu-power-systems
Status: Triaged => Incomplete
** Changed in: makedumpfile (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
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-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag
Marking as "incomplete" while awaiting test results from Thadeu's PPA.
** Changed in: ubuntu-power-systems
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
** 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:
** 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
Yes, that's the one. The kbuild maintainer modified the commit message
to add a maintainer Signed-off-by line.
I would say that any kernel versions that are shipped for actively
maintained versions of Ubuntu that support hardware platforms that don't
use the C version of recordmcount:
for file
TL;DR only occurs with HWE kernel - odd
Results of:
$ cat /sys/devices/system/cpu/vulnerabilities/mds
Host Bionic: 4.18.0-20-generic / 2.11+dfsg-1ubuntu7.13
Guest-lvl1: 3.13.0-170-generic / 2.0.0+dfsg-2ubuntu1.46
Vulnerable: Clear CPU buffers attempted, SMT Host state unknown
Guest-lvl2:
Issue is now "Fix Released" everywhere except Xenial. Should this now be
backported to Xenial or would that incur too much regression risk?
** Changed in: ubuntu-power-systems
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Kernel
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-xenial
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1829208
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1829213
** Summary changed:
- linux-oracle: -proposed tracker
+ linux-oracle: 4.15.0-1014.16 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
$ cat /boot/config-5.0.0-16-generic | grep LOG_BUF
CONFIG_LOG_BUF_SHIFT=18
CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13
$ uname -a
Linux doerfel 5.0.0-16-generic #17-Ubuntu SMP Wed May 15 10:54:19 UTC 2019
aarch64 aarch64 aarch64 GNU/Linux
And journal shows complete kernel boot messages, thus this all
It is, sorry about that. If we have no other need to re-spin we will
have to hijack this bug report for verification and then reset things
back after it claims to be released (the correct bug report would have
been bug #1828234).
--
You received this bug notification because you are a member of
** Changed in: kernel-sru-workflow/snap-release-to-candidate
Status: Confirmed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
This has been applied to Disco (and I believe to Eoan, too) but the bug
reference was pointing to a different bug (just libbfd and libbfp
looking too similar to notice): bug #1826410. This will require some
care to untangle without requiring to do the kernel again.
** Changed in: linux (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
** Description changed:
This bug will contain status and test results related to a kernel source
(My apologies for the delay. I needed to turn off SecureBoot to do this
testing.)
Still occurs in packages for:
v5.2.0-rc1
modprobe mwifiex_pcie
tail -f /var/log/syslog -n 1000 | grep mwifiex_pcie
May 20 22:27:52 darkblue kernel: [ 157.644559] mwifiex_pcie: try
set_consistent_dma_mask(32)
May
** Changed in: kernel-sru-workflow/snap-release-to-candidate
Status: Confirmed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
I have backported the patch and built a test kernel in ppa:ubuntu-power-
triage/lp1827755 could you please verify that this kernel works for you?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-5.1.3
--
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/1828168
Title:
[Surface Pro 3] Marvell 88W8897 wifi (module
Public bug reported:
Please add support for zipl ("z/ecureBoot") signing.
It should be similar to opal signing, but using the new zipl signing
key.
I am expecting to sign s390-tools stage3.bin and kernel images using
this key.
s390-tools -> can be signed already
kernels -> should only sign
** Changed in: kernel-sru-workflow/snap-release-to-beta
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/snap-release-to-candidate
Status: New => Confirmed
** Changed in: kernel-sru-workflow/snap-release-to-edge
Status: Confirmed => Fix Released
**
** Changed in: kernel-sru-workflow/snap-release-to-beta
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/snap-release-to-candidate
Status: New => Confirmed
** Changed in: kernel-sru-workflow/snap-release-to-edge
Status: Confirmed => Fix Released
**
And for amd64 bionic+ it fails to generate syscall info too.
--
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/1802495
Title:
lttng-smoke test failed on i386 4.18 kernel
Status in
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Incomplete
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1829182
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1829185
It was a great article, I am overwhelmed
If your Toshiba Printer showing offline on Windows 10 and Mac, there is nothing
to worry about. Call +1-888-209-3034 to Fix
https://www.printererrorsupport.com/blog/toshiba-printer-offline/
Toll-Free No- +1-888-209-3034
--
You received this bug
It appears that syscalls are not available on i386, got zero syscalls on
bionic, cosmic, disco. It works OK on xenial.
sudo lttng list --kernel --syscall
..produces zero syscalls.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** 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-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1829183
Title:
linux-gcp:
** 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:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1829182
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1829213
** 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
cmartin@cockatoo:~$ ls /sys/class/leds/dell::kbd_backlight
als_enabled brightness_hw_changed power subsystem
als_setting device start_triggers trigger
brightness max_brightness stop_timeoutuevent
--
You received this bug notification because you are a
** 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-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1829214
Title:
linux-azure:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1829213
** 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:
** Tags added: originate-from-1828968 somerville
--
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/1829737
Title:
Bluetooth: hci0: request failed to create LE connection: status
** 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:
** Changed in: kernel-sru-workflow/snap-release-to-candidate
Status: Confirmed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
Public bug reported:
For kernel version >= @TO_BE_FILLED@, it fails to pair with BT4.0 HID
devices and leave error messages in syslog:
Bluetooth: hci0: request failed to create LE connection: status 0x0c
Which can be detailed by btmon:
< HCI Command: LE Extended Create Connection
** 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:
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Incomplete
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1829214
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Incomplete
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Incomplete
** Changed in: kernel-sru-workflow/snap-release-to-candidate
Status: Confirmed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
** 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:
** 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
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
This bug was fixed in the package linux-oem - 4.15.0-1038.43
---
linux-oem (4.15.0-1038.43) bionic; urgency=medium
[ Ubuntu: 4.15.0-50.54 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- x86/cpu: Sanitize FAM6_ATOM
This bug was fixed in the package linux-oem - 4.15.0-1038.43
---
linux-oem (4.15.0-1038.43) bionic; urgency=medium
[ Ubuntu: 4.15.0-50.54 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- x86/cpu: Sanitize FAM6_ATOM
Test passed with Bionic i386.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is
This bug was fixed in the package linux-aws - 5.0.0-1006.6
---
linux-aws (5.0.0-1006.6) disco; urgency=medium
[ Ubuntu: 5.0.0-15.16 ]
* CVE-2019-11683
- udp: fix GRO reception in case of length mismatch
- udp: fix GRO packet of death
* CVE-2018-12126 // CVE-2018-12127
This bug was fixed in the package linux-raspi2 - 5.0.0-1008.8
---
linux-raspi2 (5.0.0-1008.8) disco; urgency=medium
[ Ubuntu: 5.0.0-15.16 ]
* CVE-2019-11683
- udp: fix GRO reception in case of length mismatch
- udp: fix GRO packet of death
* CVE-2018-12126 //
This bug was fixed in the package linux-oem - 4.15.0-1038.43
---
linux-oem (4.15.0-1038.43) bionic; urgency=medium
[ Ubuntu: 4.15.0-50.54 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- x86/cpu: Sanitize FAM6_ATOM
This bug was fixed in the package linux-gcp - 5.0.0-1006.6
---
linux-gcp (5.0.0-1006.6) disco; urgency=medium
[ Ubuntu: 5.0.0-15.16 ]
* CVE-2019-11683
- udp: fix GRO reception in case of length mismatch
- udp: fix GRO packet of death
* CVE-2018-12126 // CVE-2018-12127
This bug was fixed in the package linux-kvm - 5.0.0-1006.6
---
linux-kvm (5.0.0-1006.6) disco; urgency=medium
[ Ubuntu: 5.0.0-15.16 ]
* CVE-2019-11683
- udp: fix GRO reception in case of length mismatch
- udp: fix GRO packet of death
* CVE-2018-12126 // CVE-2018-12127
This bug was fixed in the package linux-azure - 5.0.0-1006.6
---
linux-azure (5.0.0-1006.6) disco; urgency=medium
[ Ubuntu: 5.0.0-15.16 ]
* CVE-2019-11683
- udp: fix GRO reception in case of length mismatch
- udp: fix GRO packet of death
* CVE-2018-12126 //
** Tags removed: verification-needed-bionic
** Tags added: verification-done-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/1826385
Title:
ftrace in ubuntu_kernel_selftests hang
Verified on B-amd64, the test itself has passed, and the final result is
passed as well.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** 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:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1829213
Verified on X-amd64, the test itself has passed, and the final result is
passed as well.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Changed in: ubuntu-power-systems
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1655280
Title:
ISST-LTE:pVM:roselp4:ubuntu 16.04:
** 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
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1829195
Title:
linux-kvm:
Patch available in D/E, mark this as fix released for them.
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: ubuntu-kernel-tests
Status: New => In Progress
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Po-Hsu Lin
This bug was fixed in the package makedumpfile -
1:1.6.5-1ubuntu1~18.04.1
---
makedumpfile (1:1.6.5-1ubuntu1~18.04.1) bionic; urgency=low
* Backport back to bionic. (LP: #1655280) (LP: #1790788)
makedumpfile (1:1.6.5-1ubuntu1) disco; urgency=low
[ Ubuntu Merge-o-Matic ]
*
This bug was fixed in the package makedumpfile -
1:1.6.5-1ubuntu1~18.04.1
---
makedumpfile (1:1.6.5-1ubuntu1~18.04.1) bionic; urgency=low
* Backport back to bionic. (LP: #1655280) (LP: #1790788)
makedumpfile (1:1.6.5-1ubuntu1) disco; urgency=low
[ Ubuntu Merge-o-Matic ]
*
This bug was fixed in the package makedumpfile -
1:1.6.5-1ubuntu1~18.04.1
---
makedumpfile (1:1.6.5-1ubuntu1~18.04.1) bionic; urgency=low
* Backport back to bionic. (LP: #1655280) (LP: #1790788)
makedumpfile (1:1.6.5-1ubuntu1) disco; urgency=low
[ Ubuntu Merge-o-Matic ]
*
iceboy, to confirm this is resolved in Ubuntu, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?
** Changed in: linux (Ubuntu)
Importance: High => Low
** Summary changed:
- Radeon driver only provides 1024x768 resolution
+ [Radeon HD 7950] Unable
Marius Helmeseanu, it is most helpful if you use the computer the problem is
reproducible with and file a new report with Ubuntu by first ensuring the
package xdiagnose is installed, and click the Yes button for attaching
additional debugging information after running the following from a
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
derivatives: bug 1829178
** Description changed:
On Ubuntu desktop, without a network connection, the user can select to
install 3rd party drivers (which states that it'll install graphics
driver) but even if he selects this option, nVidia proprietary drivers
won't be installed because they are not on the pool of
** 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 was posting some patches on the Nouveau mailing list in order to fix
this issue. I also wanted some PCI folks to look at it, but nobody
replied yet...
I am sure that this is in no way a driver issue, but an issue within the
PCI subsystem or the PCIe controller, so we are kind of reluctant to
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1829179
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1829204
Title:
linux-kvm:
Public bug reported:
LTP: starting af_alg06
BUG: unable to handle kernel paging request at 9cbe
IP: sha256_transform+0x28/0x1b20
PGD 4d341067 P4D 4d341067 PUD 4d345067 PMD 4d346067 PTE 0
Oops: [#1] SMP PTI
Modules linked in: authenc algif_aead xfrm_user xfrm_algo
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
101 - 200 of 252 matches
Mail list logo
