Chris, I seem to be experiencing this bug in Linux 4.7rc3 on an x220
ThinkPad with Intel HD 3000 chipset. I was getting random full system
freeze, non responsive over network.
The main messages before the crash were:
Jun 23 19:11:18 athena kernel: [drm:fw_domains_get [i915]] *ERROR* render:
Public bug reported:
I can't deploy Bioinc on the P8 system "modoc", it will run into a
kernel-panic situation (power9 system works fine).
Output from IPMI console:
[1.910940] Loaded X.509 cert 'Build time autogenerated kernel key:
c68a20e7bfd228430401173121559235d0c5ceb1'
[1.911145]
Since they might be related, lets focus on the second issue first, which
is cause by the missing files.
I'll set up a test system to try and reproduce.
It seems like this is a regression, but it would be good to confirm.
Can you test these two kernels?
Last 4.14 Bionic kernel:
Hi Joseph,
I couldn't exactly reproduce this as it happens during deployment. BUT
the closest I could get was deploying 16.04.4 (4.13) and then installing
4.17 once I was up and running. So I did that, and I am able to reboot
the system into 4.17:
ubuntu@fesenkov:~$ uname -a
Linux fesenkov
Sorry for the late reply.
Can you try 18.04? Without any "acpi_osi=" parameter of course...
Also, please ask the vendor which device should control the brightness?
I can see the PEGP's _BCM method reference to GFX0's _BCM, maybe it can
only be called on GFX0 directly?
--
You received this bug
I built a second test kernel with the updated patch you posted in comment #3.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1775235
Can you test this kernel and see if it resolves this bug?
--
You received this bug notification because you are a member of
** 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/1775526
Title:
package linux-image-4.15.0-22-generic 4.15.0-22.24
Public bug reported:
[Impact]
When registering a new binfmt_misc handler, it is possible to overflow
the offset to get a negative value, which might crash the system, or
possibly leak kernel data.
Here is a crash log when 25 was used as an offset:
BUG: unable to handle kernel paging
Output from an IPMI console.
** Attachment added: "ppc-log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775855/+attachment/5150279/+files/ppc-log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
*** Bug 100245 has been marked as a duplicate of this bug. ***
--
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/1041790
Title:
[snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001,
(In reply to Jari Tahvanainen from comment #45)
> Peter - could we close this bug or is this still valid?
Hi Jari,
You can close. I can't confirm whether it's still valid since I no
longer have that machine.
Best,
Peter
--
You received this bug notification because you are a member of Kernel
Haven't tried more recent kernels.. Will try to get around to that soon.
--
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/1251065
Title:
HP Mini 1000 fails to resume from suspend
Status
Peter - could we close this bug or is this still valid?
--
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/1251065
Title:
HP Mini 1000 fails to resume from suspend
Status in Linux:
Fix
*** Bug 98294 has been marked as a duplicate of this bug. ***
--
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/1041790
Title:
[snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001,
>From the test history, this P8 node was tested with 4.15.0-21, which
mean that the deployment works with some version earlier than
4.15.0-21, and at least it can boot with 4.15.0-21 in the last cycle.
So it's a bit odd to me to see the deployment failure here, as it should
be deployed with
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 1775858
and then change the status of the bug to 'Confirmed'.
If, due to the
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 1775856
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
[Impact]
It is not possible to perform a network install over the onboard NIC.
[Test Case]
Perform a d-i network install.
[Fix]
There are fixes for this upstream that cleanly cherry-pick back to bionic's
kernel.
[Regression Risk]
Fixes are restricted to the netsec driver
** Summary changed:
- Fixes for NIC on socionext board
+ Network installs fail on SocioNext board
--
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/1775884
Title:
Network installs fail on
@Mark Stosberg - thank you for adding your voice to the bug report. I
was wondering if this particular bug was mainly to do with Bay Trail
(Celeron/Atom) based CPU's using an SSD as their main storage, but if it
is affecting the Dell XPS 9370 then that rather scuppers my theory ;)
Can you just
--- Comment From gwal...@br.ibm.com 2018-06-08 12:57 EDT---
I got a Boston
I used a kernel with proposed patches and I did not see a hang of error
in dmesg after ipmi test in KVM guest.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received
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 1758378
and then change the status of the bug to 'Confirmed'.
If, due to the
4.4.0-128.154 - lowlatency
Regression test CMPL, RTB.
Issue to note in amd64:
ubuntu_kvm_unit_tests - 21 failed on michael, 28 failed on pepe, 18 failed on
zeppo
ubuntu_ltp_syscalls - fcntl35 / fcntl35_64 in LTP syscall test failed with
T/X/X-LTS kernel (bug 1774394) getxattr04 in LTP
You have been subscribed to a public bug:
<<>>
tag=inotify08 stime=1527762360
cmdline="inotify08"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
inotify08.c:201: INFO: ovl/test_file ino=27918358, dev=8:1
inotify08.c:212: INFO: ovl/test_file
** Description changed:
-
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 directly
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/oem/4.13.0-1030.33/oem-4.13-proposed-published.html
** Tags added: certification-testing-passed
** Changed in:
I will close this now.
--
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/1041790
Title:
[snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround
i915.semaphores=0
Status in
*** Bug 97304 has been marked as a duplicate of this bug. ***
--
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/1041790
Title:
[snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001,
*** Bug 98807 has been marked as a duplicate of this bug. ***
--
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/1041790
Title:
[snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001,
** Description changed:
I can't deploy Bioinc on the P8 system "modoc", it will run into a
kernel-panic situation (power9 system works fine).
+
+ From the testing history, it looks like this can be deployed with
+ 4.15.0-21.22
Output from IPMI console:
[1.910940] Loaded X.509 cert
--- Comment From wenxi...@us.ibm.com 2018-06-08 11:10 EDT---
linux-x6bg:/usr/src/packages/BUILD/systemd-v234+suse.160.gd5dfab21f # ./udevadm
test-builtin path_id /sys/block/nvme1n1
calling: test-builtin
Load module index
Network interface NamePolicy= disabled by default.
Parsed
Hi Joseph,
We gave it a try internally and it looks good. Passed the same set of
tests I ran with the previous kernel you provided: works with mq
disabled, enabled and also passes a simple io integrity test.
Thanks,
F.
--
You received this bug notification because you are a member of Kernel
(In reply to Thaddaeus Tintenfisch from comment #22)
> I was able to resolve the FPS drop by running the following two commands:
>
> echo battery > /sys/class/drm/card0/device/power_dpm_state
> echo balanced > /sys/class/drm/card0/device/power_dpm_state
In this case, I guess this now becomes bug
I don't think Jesse will be working on this anymore...
Have you tried more recent kernels?
--
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/1251065
Title:
HP Mini 1000 fails to resume
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Invalid
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Marcelo Cerri
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
** Changed in: ubuntu-power-systems
Importance: Undecided => Medium
** Tags added: triage-g
--
Public bug reported:
$ /sbin/hwclock --debug --set --date "2004/10/20 04:10:00"
hwclock from util-linux 2.31.1
System Time: 1528467313.266333
Trying to open: /dev/rtc0
No usable clock interface found.
hwclock: Cannot access the Hardware Clock via any known method.
ProblemType: Bug
DistroRelease:
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Precise)
Marking this task as "Incomplete" for bug 1775855, note that ppc64le
deployment works for P9, just not for P8
4.15.0-23.25 - generic
Regression test CMPL, RTB.
Issue to note in amd64:
libhugetlbfs - Unable to build libghugetlbfs test on 4.15 Bionic (bug 1765279)
ubuntu_bpf - test_maps in
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 1775875
and then change the status of the bug to 'Confirmed'.
If, due to the
Created attachment 135173
gpu error file on 4.13.5-200.fc26.x86_64
This problem reappeared on 4.13.5-200.fc26.x86_64 last Friday.
[774249.632109] [drm] GPU HANG: ecode 6:0:0x85f8, in Xorg [696], reason:
Hang on rcs0, action: reset
[774249.632110] [drm]
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 1775855
and then change the status of the bug to 'Confirmed'.
If, due to the
** Description changed:
I can't deploy Bioinc on the P8 system "modoc", it will run into a
kernel-panic situation (power9 system works fine).
- From the testing history, it looks like this can be tested with
- 4.15.0-21.22
+ From the test history, this P8 node was tested with 4.15.0-21,
Public bug reported:
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04 LTS
Release:18.04
Codename: bionic
uname -r
4.15.0-22-generic
How to reproduce:
1) connect dock station
2) disconnect dock station
3) type: systemctl suspend
** Tags added: kernel-bug
--
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/1775875
Title:
Ubuntu 18.04 Lenovo X1 Carbon 5th fails to suspend after detaching
dock station (NULL pointer
** Summary changed:
- inotify07 and inotify08 in LTP syscall test failed with X/X-LTS/A kernel
+ inotify07 and inotify08 in LTP syscall test failed with X/X-LTS/X-HWE/A kernel
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Changed in: linux-meta-oem (Ubuntu)
Assignee: (unassigned) => AceLan Kao (acelankao)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1775586
Title:
after S3 bt icon
..plus it can be easily checked w/o any special privilege.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1760173
Title:
zfs, zpool commands hangs for 10 seconds without a /dev/zfs
So, I am pretty confident that systemd will create
"/run/systemd/container" if we're inside a container, so I'll check for
that
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1760173
Mitch, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767611/comments/8
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line
** Changed in: linux-azure (Ubuntu Bionic)
Status: Confirmed => In Progress
--
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/1762554
Title:
[Hyper-V] IB/mlx5: Respect new UMR
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.17
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.17
PS : I tried the "hwe" 16.04 kernel (which is the kernel from 17.10) and
it does not work either...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1763748
Title:
Integrated Webcam
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
** Tags
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
in any case someone faces the same problem, installing
bluez_5.46-0ubuntu3_amd64.deb from artful (together with libreadline7)
solved the problem for me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Does the bug go away if you boot back into the 16.04 kernel?
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** 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.
It can be built on Bionic now. But still not working on Artful
I will keep this bug open.
** Tags removed: 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/1675395
Title:
*** Bug 104772 has been marked as a duplicate of this bug. ***
--
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/1041790
Title:
[snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001,
** Changed in: linux-kvm (Ubuntu)
Status: New => Invalid
--
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/1770245
Title:
getlogin will fail to open /proc/self/loginuid
Status
3.13.0-151.201 - generic
Regression test CMPL, RTB.
Issue to note in amd64:
ubuntu_kvm_smoke_test - uvt-kvm wait issue on Trusty(bug 1732883)
ubuntu_kvm_unit_tests - 39 failed on pepe
ubuntu_ltp_syscalls - fcntl35 / fcntl35_64 in LTP syscall test failed with
T/X/X-LTS kernel (bug 1774394)
*** Bug 106119 has been marked as a duplicate of this bug. ***
--
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/1041790
Title:
[snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001,
Public bug reported:
This is not a regression, this can be found on 4.15.0-21.22 as well.
* Command:
./ubuntu_fan_smoke_test.sh 10.245.0.0/16
Exit status: 1
Duration: 58.4590229988
stdout:
Running in the Canonical CI environment
Testing Fan Networking (pre-0.13.0 API)
docker
** Also affects: ubuntu-kernel-tests
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/1750793
Title:
Failed to build upstream bpf test on
commit 0da715ee60774401bea00dc71fca6fd1096c734a
Author: Chris Wilson
Date: Mon Nov 20 20:55:02 2017 +
drm/i915: Disable semaphores on Sandybridge
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Adding tag into "Whiteboard" field - ReadyForDev
The bug still active
*Status is correct
*Platform is included
*Feature is included
*Priority and Severity correctly set
*Logs included
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
I doesn't seem to be getting mentioned Gnome crashes on my sandybridge
anymore with mainline kernels, that is currently 4.11 and I think even
with 4.10 I was not getting any issues, with mainline longterm 4.4.61
and default centos 7 kernels I am definitely getting very frequent GPU
crashes that
*** Bug 104304 has been marked as a duplicate of this bug. ***
--
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/1041790
Title:
[snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001,
@jason108:
This patch has been landed in upstream since 4.11, so, yes, we have it
in bionic.
>From the log in askubuntu, there's a line:
"[ 31.964068] Bluetooth: hci0: BCM: Patch command 0a0a failed (-110)"
This indicates that something goes wrong when the driver is sending firmware to
the
*** Bug 104243 has been marked as a duplicate of this bug. ***
--
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/1041790
Title:
[snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001,
(In reply to samuel.rakitnican from comment #260)
> I doesn't seem to be getting mentioned Gnome crashes on my sandybridge
> anymore with mainline kernels, that is currently 4.11 and I think even with
> 4.10 I was not getting any issues, with mainline longterm 4.4.61 and default
> centos 7 kernels
(In reply to Elizabeth from comment #261)
> (In reply to samuel.rakitnican from comment #260)
> > I doesn't seem to be getting mentioned Gnome crashes on my sandybridge
> > anymore with mainline kernels, that is currently 4.11 and I think even with
> > 4.10 I was not getting any issues, with
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
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-signed (Ubuntu)
Importance: Undecided => Low
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.17
** 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.
https://bugs.launchpad.net/bugs/1775452
Title:
Nouveau problems
Status in linux package in Ubuntu:
I'll mark this bug incomplete until there are test results using the
latest Xenial 4.4 kernel.
** Tags added: kernel-da-key
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Changed in: linux
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.17
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
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 1775847
and then change the status of the bug to 'Confirmed'.
If, due to the
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 1775412
and then change the status of the bug to 'Confirmed'.
If, due to the
** Tags added: artful 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/1775784
Title:
inotify08 in LTP syscall test failed with X/X-LTS/X-HWE/A/B kernel
Status in
*** Bug 97451 has been marked as a duplicate of this bug. ***
--
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/1041790
Title:
[snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001,
I was able to resolve the FPS drop by running the following two
commands:
echo battery > /sys/class/drm/card0/device/power_dpm_state
echo balanced > /sys/class/drm/card0/device/power_dpm_state
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Hi Joseph,
Thank you for looking into it. Can't answer yet - I'll have to boot 4.4
kernel and run it for two days at least to make sure - going to start
tonight. Also will attach more logs - apport-collect didn't work with
mainline kernel.
--
You received this bug notification because you are a
Closing resolved+fixed which has been verified.
--
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/1384342
Title:
kernel messages intel_crtc_wait_for_pending_flips correlate to compiz
You have been subscribed to a public bug:
---Problem Description---
Update to ocxl driver
---uname output---
4.15.0-22-generic
---Additional Hardware Info---
opencapi adapter needed
Machine Type = any POWER9 system
---Debugger---
A debugger is not configured
== Comment: #1 - Frederic
Public bug reported:
We're fetching the test from the upstream repo [1] because the lxc-test
package is no longer exist in Bionic (bug 1758255)
Not all the test binaries were pre-built there.
Compare the test result from Artful, there are 39 tests shipped by the
lxc-test package, but only 10
Verified with the 4.15.0-1010-kvm Bionic kvm kernel + uvtool 0~git140-0ubuntu1,
it works.
I will close this bug.
Thanks.
** Changed in: ubuntu-kernel-tests
Status: New => Fix Released
** Changed in: linux-kvm (Ubuntu)
Status: New => Invalid
--
You received this bug notification
4.4.0-1027.32 - kvm
Regression test CMPL, RTB.
Issue to note in amd64:
ubuntu_blktrace_smoke_test - ubuntu_blktrace_smoke_test failed with 4.4 /
4.15 kvm kernel (bug 1760636)
ubuntu_fan_smoke_test - ubuntu_fan_smoke_test failed on 4.4 X-kvm kernel (bug
1763323)
ubuntu_kvm_unit_tests - 18
Affecting Xenial as well.
** Summary changed:
- inotify07 and inotify08 in LTP syscall test failed with X-LTS / A kernel
+ inotify07 and inotify08 in LTP syscall test failed with X/X-LTS/A kernel
** Tags added: xenial
** Tags added: amd64
--
You received this bug notification because you are
List of previously applied patches:
* mac80211_hwsim: fix possible memory leak in hwsim_new_radio_nl()
* bpf: fix selftests/bpf test_kmod.sh failure when CONFIG_BPF_JIT_ALWAYS_ON=y
* virtio-net: Fix operstate for virtio when no VIRTIO_NET_F_STATUS
--
You received this bug notification
Fixed has landed here:
http://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?h=master-next=3710a21c706d1bb0fedbff9948e0c02b21c4b2b4
** No longer affects: linux (Ubuntu)
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
** No longer affects: lxc
4.15.0-1013.13~16.04.2 - azure
Regression test CMPL, RTB.
Issue to note in x86_64 (azure):
ebizzy - failed on Standard_A0, passed on the rest
libhugetlbfs - 1 failed (brk_near_huge, bug 1653597), Killed by signal 1, bad
config 3, passed on the rest
monotonic_time - all two tests (or just
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 1775816
and then change the status of the bug to 'Confirmed'.
If, due to the
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/bionic/4.15.0-23.25
/bionic-proposed-published.html
** Tags added: certification-testing-passed
** Changed in:
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 directly from a mainline/stable
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1755705
Title:
CFL systems are not responsive to TB16 DP/HDMI (un)plugging
1 - 100 of 215 matches
Mail list logo
