Attached is a zip containing updated dmesg and acpidump output against
Kernel 4.17 RC5, per the upstream maintainer's request. It also
contains other outputs (xinput, devices, Xorg.0.log, etc.) for said
Kernel version.
** Attachment added: "kernel_4.17_RC5_report.zip"
** Changed in: ubuntu-power-systems
Status: Triaged => In Progress
--
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/1771439
Title:
[LTC Test] Ubuntu 18.04: tm_sigreturn failed on
--- Comment From bssrika...@in.ibm.com 2018-05-17 00:01 EDT---
Tested with `4.4.0-124-generic #149~lp1771439`:
selftests: tm-resched-dscr
test: tm_resched_dscr
tags: git_version:unknown
Binding to cpu 8
main test running as pid 2792
Check DSCR TM
** Description changed:
[Impact]
Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and
then they can't resume the system from opening the lid.
[Test Case]
1. echo s2idle | sudo tee /sys/power/mem_sleep
2. Close the lid
3. Open the lid
[Fix]
According
@jsalisbury,
Sorry for changing the status. Please let the bug follow your policy,
thanks.
** Description changed:
[Impact]
Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and
then they can't resume the system from opening the lid.
+ [Test Case]
+ 1. echo s2idle
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1771708/+attachment/5140542/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
Please refer to my report in upstream:
http://mailman.alsa-project.org/pipermail/alsa-devel/2016-May/107715.html
--
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/1755326
Title:
Periodic
Please refer to my report in upstream:
http://mailman.alsa-project.org/pipermail/alsa-devel/2016-May/107715.html
--
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/1755326
Title:
Periodic
*** This bug is a duplicate of bug 1757008 ***
https://bugs.launchpad.net/bugs/1757008
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1757008, so it is being marked as such. Please
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1771708/+attachment/5140534/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1771708/+attachment/5140539/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1771708/+attachment/5140532/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1771708
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1771708/+attachment/5140540/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1771708/+attachment/5140541/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1771708/+attachment/5140537/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1771708/+attachment/5140538/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1771708/+attachment/5140536/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1771708/+attachment/5140535/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1771708/+attachment/5140533/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1771708
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1771708/+attachment/5140529/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1771708
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1771708/+attachment/5140531/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1771708/+attachment/5140530/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
That happens with all Ubuntu flavors: Xubuntu, Kubuntu...
Reboot and suspend are works.
(This laptop had Ubuntu 14.04 or 12.04 (don't remember) preinstalled, which
was fine)
Hardware details:
pc
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 1771708
and then change the status of the bug to 'Confirmed'.
If, due to the
Did you try the laptop-dmic parameter?
sudo nano /etc/modprobe.d/alsa-base.conf
add to the bottom of the file:
options snd-hda-intel model=laptop-dmic
And reboot.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Sorry, I meant
> And I'm not sure if I got the right
nvm_usb_0302.bin
--
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/1766825
Title:
Bluetooth issues with Dell XPS 13 (9370)
Status
Would be nice if someone from Qualcomm could have a look at it; just now
an update of the linux-firmware Ubuntu package overwrote my fix again.
And I'm not sure if I got the right ramps_0x0302_48.dfu
The Windows driver has these:
sonic@sonic-XPS-13-9370:/opt/Bluetooth_driver$ md5sum
** Tags added: bugnameltc-167748 severity-medium
--
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/1770784
Title:
ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp4g4:ubuntu1604:P8 compat: guest
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.
Please follow the instructions on
Some more data points:
An m1.small instance running a Xenial AMI (with linux-aws-xenial) works
fine in cn-north-1.
An m1.small instance running the same kernel works fine in us-west-2.
The Xen hypervisor version for m1.small in cn-north-1 differs from us-west-2:
us-west-2:
[0.00] SMBIOS
Our testing on this kernel is complete and we are good with publishing.
** Changed in: kernel-sru-workflow/stakeholder-signoff
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in
Hi Joseph,
Thank you for the quick reply.
I did as instructed and got the specified upstream kernel installed.
```
~$ uname -a
Linux ubuntu 4.17.0-041700rc5-generic #201805132030 SMP Mon May 14 00:32:50 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
```
Problem persists after reboot:
```
Hi,
how can i do this?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1768152
Title:
Brightness controll doesn't work - Samsung R560
Status in linux package in Ubuntu:
Confirmed
** Also affects: linux-aws (Ubuntu Bionic)
Importance: Undecided
Status: New
--
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/1771679
Title:
Kernel panic on boot (m1.small
Hey Frank,
I understand all of these patches are upstreamed already on Linus' tree
and most of the patches seem to be clean cherry picks (except
15b4dd7981496f51c5f9262a5e0761e48de6655f, which was backported).
--
You received this bug notification because you are a member of Kernel
Packages,
We've only seen this on m1.small instances, but we haven't tested
exhaustively (we do know, though, that m3.large is fine).
The command used to create the instance was:
aws --profile=china --region=cn-north-1 ec2 run-instances --key-
name=Odd_Bloke --image-id=ami-8fcd13e2 --security-groups
Public bug reported:
We're observing the following panic on boot when trying to boot an
m1.small in cn-north-1 (which is a region in AWS China):
[2.271681] Hardware name: Xen HVM domU, BIOS 3.4.3.amazon 11/11/2016
[2.271681] RIP: 0010:__xen_evtchn_do_upcall+0x24/0x80
[2.271681] RSP:
I built a test kernel with commit c2d2e6738a209f0f9dffa2dc8e7292fc45360d61.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1771620
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to
I built a test kernel with commit 78a3e8889b4b6b99775ed954696ff3e017f5d19b.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1771439
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to
I built a Bionic test kernel. The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1771555
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the
linux-image
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => 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/1771439
Title:
So I've tested all the way from rc2 -> rc7, and confirm that rc7 is the
issue. In two different machines:
machine1: running kernel was rc3
machine2: running kernel was rc4
In both cases, after install of rc7, and reboot, I see the issue. Logs
for the latest:
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
As the new installation keeps crashing at the login I can't run the
command in the terminal window.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Package changed: linux-signed (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 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
Vivid is now EOL. Can you see if this bug still exists on a supported
release, such as Artful or Bionic?
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
**
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in:
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Confirmed =>
** Tags added: triage-g
--
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/1770784
Title:
ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp4g4:ubuntu1604:P8 compat: guest
crashes in
** Tags removed: bugnameltc-167748 severity-medium triage-g
--
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/1770784
Title:
ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp4g4:ubuntu1604:P8
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 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
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 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
I built a test kernel with commit 13a83eac373c49c0a081cbcd137e79210fe78acd.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1771344
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to
*** This bug is a duplicate of bug 1765232 ***
https://bugs.launchpad.net/bugs/1765232
I have same problem on HP Proliant ML350 G5 on P400 smart array board,
it's a kernel issue, last working kernel from ubuntu ppa or kernel.org
is 4.13.16
>From kernel 4.14.1, no boot
Tested also other live
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Assignee:
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
**
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
**
** 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/1771431
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 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
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 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
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1771480
@Peridot,
Request from Upstream:
For the original 4.13 kernel, I don't
see any attachments that have the AMD-Vi messages in question. Were they
completion timeouts (like in the later mainline kernel test, which I'll
get to in a bit) or I/O page fault messages? Without that information it
is
Hi Juerg,
> When updating to 4.4.117 we reverted a bunch of SAUCE rfi-flush patches and
> replaced them with the
> upstream versions. Is there a possibility that your patches are no longer
> required with those updates?
None of these patches seems to be integrated int 4.4.0-124. So, we will
Hi everyone,
I also have an Asus ROG G752-VS with the same dead Elantech touchpad you have.
But I got it to work, briefly:
The Anaconda setup of Fedora 28 Atomic Workstation
(https://torrent.fedoraproject.org/torrents/Fedora-AtomicWorkstation-ostree-x86_64-28.torrent)
fully activates the
Public bug reported:
On a hosting platform running Xen hypervisor, in a virtual machine with
Ubuntu 18.04 system and the default kernel from Ubuntu, I try to detach
a virtual network interface. On the Xen side, the virtual interface is
removed from the VM but the kernel still has the interface.
The dev_disable_lro warning is happening due to some logic issues in the
features code. The LRO on the VLAN (bond0.200, e.g.) that's being
warned about does end up being disabled by a NETDEV_FEAT_CHANGE callback
when the underlying bond0's features are updated, so the warning is
spurious.
** Package changed: ubuntu => linux (Ubuntu)
** Tags added: bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1771555
Title:
dmesg Error seen on system booting from Ubuntu18.04
Just to confirm, 4.15-rc1 does not have the issue, but 4.15 final does?
If that is the case, we can try to narrow it down further. Could you
test v4.15-rc9:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc9/
--
You received this bug notification because you are a member of Kernel
Yes, you can add EXTRAVERSION info to the kernel name. This is done in
the file: ~/debian.master/changelog. The top line would be changed like
the following:
linux (4.15.0-20.21) bionic; urgency=medium
TO
linux (4.15.0-20.21~lp1770095) bionic; urgency=medium
--
You received this bug
Can you run uname -a to confirm the correct kernel is booted? You
should see this string in the output: "lp1768103".
--
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/1768103
Title:
You have been subscribed to a public bug:
Problem Description
===
dmesg Error seen on system booting from Ubuntu18.04
Is this an issue?
[2.601750] integrity: Unable to open file: /etc/keys/x509_ima.der (-2)
[2.601754] integrity: Unable to open file: /etc/keys/x509_evm.der
Found some document about size determination in pci devices
had run lspi
jean@jean-Soisy:~$ sudo lspci -vv -k - -s 03:09.0
03:09.0 VGA compatible controller: NVIDIA Corporation NV44A [GeForce 6200] (rev
a1) (prog-if 00 [VGA controller])
Control: I/O- Mem+ BusMaster+ SpecCycle-
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1771542
Title:
Suspend to idle: Open lid didn't resume
Status in
--- Comment From dougm...@us.ibm.com 2018-05-16 11:05 EDT---
(In reply to comment #8)
> Would you like me to build another test kernel with a version, so it won't
> collide?
I haven't heard back from Naveed, who was going to test last night. I
hate to ask for a new kernel if he was able
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1771238
Title:
Not able to passthrough > 32 PCIe devices to a KVM
Daniel, what do you mean by "running process"? The steps involve login
out and back in, so starting a new session, group changes should be
active on a new login no?
** Package changed: linux (Ubuntu) => gdm3 (Ubuntu)
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => New
--
You received
--- Comment From lagar...@br.ibm.com 2018-05-16 10:11 EDT---
Patch set was resent to Canonical mailing list by Ziviani.
--
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/1759723
Please always attach patches to the LP bug - this is the central tool
for bug activity and would allow everybody involved to find everything
at one place.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
--- Comment (attachment only) From gwal...@br.ibm.com 2018-05-16 10:00
EDT---
** Attachment added: "[PATCH][SRU][Bionic 1/9] scsi: qla2xxx: Fix session
cleanup for N2N"
Hi,
I'm wondering if there is anything Netronome can do to assist with
regards to this bug. Its very important to us.
--
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/1768526
Title:
--- Comment From gwal...@br.ibm.com 2018-05-16 10:04 EDT---
(In reply to comment #56)
> Created attachment 127215 [details]
> [PATCH][SRU][Bionic 1/9] scsi: qla2xxx: Fix session cleanup for N2N
sorry folks,
After the submission I have noted the wrong authority in the set by me,
and so I
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
--
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/1769696
Title:
[SRU][Bionic/Artful] fix false positives in W+X
** Package changed: linux (Ubuntu) => ibm-java71 (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/1771575
Title:
[Comm] IBM JDK 8.0.5.15 integration into Ubuntu
Status in
Public bug reported:
Uploaded the Debian packages onto the Canonical FTP Server for 8.0.5.15
foreman@cit7r02:~/sandbox/binary$ ftp archive.admin.canonical.com
Connected to archive.admin.canonical.com.
220 youngberry.canonical.com FTP server (Poppy Upload Server) ready.
Name
You have been subscribed to a public bug:
Uploaded the Debian packages onto the Canonical FTP Server for 8.0.5.15
foreman@cit7r02:~/sandbox/binary$ ftp archive.admin.canonical.com
Connected to archive.admin.canonical.com.
220 youngberry.canonical.com FTP server (Poppy Upload Server) ready.
Name
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Problem still exists in 4.16.9 kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16.9/
(#uname -r output is 4.16.9-041609-generic )
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Package changed: linux (Ubuntu) => initramfs-tools (Ubuntu)
** Changed in: initramfs-tools (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: initramfs-tools (Ubuntu Xenial)
Status: New => Fix Released
** Changed in: initramfs-tools (Ubuntu Trusty)
Importance:
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Fixed in Debian
** Project changed: linux => initramfs-tools
** Changed in: initramfs-tools
Status: Unknown => 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/1771557
Public bug reported:
[Impact]
The initramfs-tools hook-functions script cannot translate nvmeXnYpZ to nvmeXnY
block device, so it's failing and not building the initram disk.
Upstream solution is composed for at least 2 patches (it's a series, but
the 2 below are really the needed ones):
I tested with 4.17 rc4 and the problem persists
--
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/1747463
Title:
kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X
Status
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 1771546
and then change the status of the bug to 'Confirmed'.
If, due to the
** Changed in: ubuntu-power-systems
Status: Fix Released => 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/1759723
Title:
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 1771542
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
when load kernel with kexec:
/sbin/kexec -p
--command-line="root=UUID=5f248d51-af51-4178-bd4d-763d4a6648b3 ro console=ttyS0
console=tty0 irqpoll maxcpus=1 nousb"
--initrd=/boot/initrd.img-3.19.0-80-generic /boot/vmlinuz-3.19.0-80-generic
and then, triggers a panic:
1 - 100 of 153 matches
Mail list logo
