apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1644047/+attachment/4782242/+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: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1644047/+attachment/4782239/+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: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1644047/+attachment/4782237/+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/1644047
Public bug reported:
The port of KVM's HyperV SynIC patches (and other HyperV related KVM
Patches) broke QEMU's --machine kernel_irqchip=split for Ubuntu Xenial
on x86. Guests hang in early boot.
Ubuntu Xenial dropped the upstream patch
abdb080f7ac8a85547f5e0246362790043bbd3f2 while backporting.
Hardware Certification have begun testing this -proposed kernel.
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/certification-testing
Assignee: Canonical Hardware Certification (canonical-hw-cert) => Pierre
Can confirm that the 4.9.0-040900rc6-generic kernel fixes this issue!
/sys/bus/iio/devices $> $cat iio\:device*/name
gyro_3d
magn_3d
gyro_3d
accel_3d
als
thanks!
** Tags removed: apport-collected yakkety
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status:
** Also affects: linux (Ubuntu Trusty)
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/1644302
Title:
Possible regression on
I can also confirm that it is solved in 4.9rc6.
On a Latitude 7370:
:~$ uname -r
4.9.0-040900rc6-generic
:~$ xinput list
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)]
⎜ ↳ ELAN
[I've CC'ed the people that signed-off/acked the original backport.]
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1644394
Title:
Botched backport breaks level triggered EOIs in QEMU
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1644047/+attachment/4782232/+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/1644047
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1644047/+attachment/4782241/+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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1644047/+attachment/4782244/+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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1644047/+attachment/4782238/+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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1644047/+attachment/4782233/+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
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1644047/+attachment/4782245/+files/WifiSyslog.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/1644047/+attachment/4782236/+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/1644047
Did not start happening after an upgrade. New install of 16.10.
Yes, I can test a new 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/1644047
Title:
cannot use accelerometer
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1644047/+attachment/4782243/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1644047/+attachment/4782240/+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: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1644047/+attachment/4782234/+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: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1644047/+attachment/4782235/+files/JournalErrors.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 yakkety
** Description changed:
The Lenovo yoga 460 kernel does not seem to have support for the
accelerometer and other sensors.
I can see the same description: "Non-VGA unclassified device" as this
thread:
** Changed in: hwe-next
Assignee: Liming Wang (wangliming) => (unassigned)
** Changed in: hwe-next
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
4.4 kernel. enables mgag200. Just for test.
** Attachment added: "linux-image-mgag200-deb.7z"
https://bugs.launchpad.net/hwe-next/+bug/1642470/+attachment/4782296/+files/linux-image-mgag200-deb.7z
--
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.
>From a terminal window please run:
apport-collect 1644394
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
Steve, this patch looks good to me.
Thanks
--
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/1644302
Title:
Possible regression on 3.13.0-102.149~precise1 x86_64 (gce)
Status in linux
Those logs shouldn't be necessary. Identified the underlying bug by code
inspection of your public tree (and local testing). Marking as
confirmed.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
** Description changed:
- For some new Dell laptops, they are using Matrox graphics cards.
+ A new Dell Precision workstation uses Matrox graphics cards.
And in order to let Xorg mga driver work. We need to enable
CONFIG_DRM_MGAG200.
MGAG200 is disabled by this bug.
The microcode on DELL KNL-D machine is 0x01a0, while our SDV is
0x01a3. So it is possible to upgrade bios first.
Another strange thing in cpuinfo is cpu frequency is 998.962MHz, why is
it not 1.3GHz ?
--
You received this bug notification because you are a member of Kernel
Packages,
** Tags added: patch
--
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/1644394
Title:
Botched backport breaks level triggered EOIs in QEMU guests with
--machine kernel_irqchip=split
Source for comment #2. For a record.
** Attachment added:
"linux-4.4.24.mgag200-1-amd64_4.4.24.mgag200-1-amd64.orig.tar.xz"
https://bugs.launchpad.net/hwe-next/+bug/1642470/+attachment/4782300/+files/linux-4.4.24.mgag200-1-amd64_4.4.24.mgag200-1-amd64.orig.tar.xz
--
You received this bug
** 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/1644056
Title:
kernel BUG at
Derivative packages from packages here can be worked on, the following tracking
bugs were opened for them:
linux-raspi2 - bug 1644181
linux-snapdragon - bug 1644182
Backport packages from packages here can be worked on, the following tracking
bugs were opened for them:
linux-lts-xenial
Running OK so far with the kernel team PPA and the proposed 4.8 kernel
updates.
--
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/1643622
Title:
[drm:intel_cpu_fifo_underrun_irq_handler
*** This bug is a duplicate of bug 1644169 ***
https://bugs.launchpad.net/bugs/1644169
** This bug is no longer a duplicate of bug 1640921
linux: 4.4.0-49.70 -proposed tracker
** This bug has been marked a duplicate of bug 1644169
linux: 4.4.0-50.71 -proposed tracker
--
You received
*** This bug is a duplicate of bug 1644169 ***
https://bugs.launchpad.net/bugs/1644169
** This bug has been marked a duplicate of bug 1644169
linux: 4.4.0-50.71 -proposed tracker
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux (Ubuntu Xenial)
Status: Triaged => 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/1644165
Title:
xenial 4.4.0-49.70 kernel breaks LXD userspace
I'll try with trusty
--
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/1641593
Title:
unable to enable iommu on HPE Proliant Gen9 server
Status in linux package in Ubuntu:
Confirmed
Public bug reported:
Fixes for bug #1634964 actually break LXD userspace tools as they
include some 4.8 backports that aren't supported by the userspace in
xenial. The following patches in particular require support from
userspace:
ac7f3f73cb39 (namespace) vfs: Don't modify inodes with a
** Changed in: hwe-next
Status: New => 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/1640418
Title:
WiFi LED doesn't work on some Edge Gateway units
Status in HWE
Public bug reported:
This bug is for tracking the 4.4.0-50.71 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:
** Changed in: linux (Ubuntu)
Assignee: Luis Henriques (henrix) => Skymathrix (asstaroid)
--
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/1644165
Title:
xenial 4.4.0-49.70 kernel
** Changed in: linux (Ubuntu Xenial)
Status: Fix Committed => 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/1634964
Title:
Allow fuse user namespace mounts by default in
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-102.149~precise1-generic/onza__3.13.0-102.149~precise1__2016-11-21_23-02-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-102.149~precise1-generic/onza__3.13.0-102.149~precise1__2016-11-23_09-49-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in
OK so tripped on another issue trying with trusty - the servers I'm
using have NVMe SSD's for caching, and it looks like trusty blkid is
unable to read meta from from nvme devices.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Radeon 3650 HD same problem here. No UMS Support
--
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/1568211
Title:
Unable to boot
Status in linux package in Ubuntu:
Expired
Bug
I've tested the kernel on Ubuntu 16.04 32 bit and everything works fine,
even with kdump through NMI.
Note: Kdump through NMI on Ubuntu 16.04 32 bit with kernel
4.4.0-21-generic is not working. I've also tested Ubuntu 15.04 but this
version is End of life.
--
You received this bug notification
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1644256
Title:
package
Public bug reported:
I have nothing more to report, as I was informed of a package
installation failure. I allowed a partial upgrade and ended up with
this bug report and an incomplete installation. My system appears to be
working.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package:
Public bug reported:
This issue was found in the ubuntu_qrt_apparmor test, it failed with
"kernel regression test" on 3.13.0-102.149~precise1
Error message:
11/21 17:51:18 ERROR| utils:0153| [stderr] Run kernel regression tests ... FAIL
Full test log can be found here:
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1644302
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
James,
Can you please clarify running OK. For me everything runs okay if I use
the main display on the laptop or connect a monitor to the DisplayPort
port. However, I get the error messages when I connect the external
docking station (Thinkpad Onelink+). As per my post, the error message
was
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1639345
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
** Information type changed from Private Security to Public Security
--
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/1639345
Title:
lxc-attach to malicious container allows access to
** Tags added: kernel-fixed-upstream
** 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/1643341
Title:
Unexpected
Tested. 16 minutes uptime, no fan, no shutdown.
uname -a
Linux zoo 4.9.0-040900rc6-generic #201611201731 SMP Sun Nov 20 22:33:21 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux
** Description changed:
This happens twice in between a short time, 2-5 minutes, after the computer
was turned on and
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques
(henrix)
** Description changed:
This bug is for tracking the
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1639345
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
** 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/1639345
Title:
lxc-attach to malicious container allows access to host
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1644322
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-50.71-generic/onza__4.4.0-50.71__2016-11-23_17-57-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
--- Comment From mu...@br.ibm.com 2016-11-23 12:56 EDT---
I am not sure why, but 'verification-done-yakkety' is already set instead of
'verification-needed-yakkety'. So just adding a comment that the proposed
kernel was tested and it indeed solves this issue.
--
You received this bug
(sorry to many i's - its late :-))
--
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/1643622
Title:
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
FIFO underrun
Hi Iilija
I don't use a docking station, but I was seeing occasion blanking of the
screen with an external monitor plugged into the display port.
Running with the proposed 4.8 kernel from the kernel team PPA has
appeared to resolve the issue - I've not see the original drm kernel
error message,
So from the best I can determine it looks like configure_networking out
of scripts/functions of the initramfs is failing to properly bring up
the network device. I'm going through the process now to figure out
what logic might actually be stopping it from functioning. I'll let you
know more when
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/kernel01__4.4.0-49.70__2016-11-23_17-35-00/results-index.html
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: Confirmed => Fix Released
** Changed in:
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/s2lp6g001__4.4.0-49.70__2016-11-23_17-35-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/s2lp3__4.4.0-49.70__2016-11-23_17-35-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
I am using a distro based on Ubuntu (Linux Deepin). Following the steps
of the DebuggingTouchpadDetection I found that it's a kernel problem (I
can use a mouse but not my mousepad). I have tried using Fedora Live USB
and the mousepad worked there.
I have attached the
--- Comment From mu...@br.ibm.com 2016-11-23 13:02 EDT---
Just for documentation:
grep "CONFIG_TIGON3\|CONFIG_VIRTIO_NET\|CONFIG_VIRTIO_BLK"
/boot/config-4.8.0-28-generic
CONFIG_VIRTIO_BLK=m
CONFIG_VIRTIO_NET=m
CONFIG_TIGON3=m
The three drivers could be added / removed with modprobe
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-50.71-generic/modoc__4.4.0-50.71__2016-11-23_18-06-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-50.71-generic/ms10-35-mcdivittB0-kernel__4.4.0-50.71__2016-11-23_18-07-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Considering that https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/trusty/commit/?h=master-
next=74a2b3a087989058f29a195c706e2740fbfed258 between
Ubuntu-3.13.0-101.148 and Ubuntu-3.13.0-102.149, I think this is a
potentially serious regression.
That patch was to fix a bug (bug
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Tags added: bot-stop-nagging
--
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/1639345
Title:
lxc-attach to malicious
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-50.71-lowlatency/onza__4.4.0-50.71__2016-11-23_18-45-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
One difference between the userspaces in precise and trusty is that the
trusty version supports mount rules.
Also, Luis noticed that in aa_new_mount(), "struct path dev_path" is
redefined, and thus shadowed. He's doing a test kernel with the
following patch applied:
diff --git
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1644302
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-50.71-generic/onza__4.4.0-50.71__2016-11-23_18-21-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I'm able to reproduce this on an amd64 guest with the lts-backport-
trusty kernel installed, though I get a different signal:
ubuntu@sec-precise-amd64:~/tmp/apparmor-2.7.102/tests/regression/apparmor$ sudo
sh -c 'VERBOSE=1 bash mount.sh'
ok: MOUNT (unconfined)
ok: UMOUNT (unconfined)
>From the initramfs shell can you provide me the output for
ls -la /sys/class/net/*
and
cat /sys/class/net/*/address
I have a feeling you'll only see lo and enx847beb55c195. Specifially I'm
looking for the device name that matches your BOOTIF mac address. However if
it's showing up please
If the device is not being detected I have a feeling there may be
something going wrong with udev.
--
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/1639202
Title:
Cannot enlist/commission
Dear Dan, user reshen on the github Docker issue thread [1] did some
extensive testing using kernel 4.8.8. He has not been able to reproduce
the issue using that version. I've also done testing using the ubuntu
mainline kernel builds and also not been able to reproduce the issue
anymore.
He has
I should also note, the latest upstream kernel has similar timeout
problems while probing, so this isn't restricted to only the xenial
kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-50.71-lowlatency/onza__4.4.0-50.71__2016-11-23_19-10-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Okay, I can confirm that Luis' patch fixes the oops and test failures
that I am seeing.
Also, the mount.sh test in the apparmor userspace package is a bit
broken, even when things are working correctly, it aborts early (but
does an exit 0, so it doesn't get noticed), skipping 3 of the tests.
86 matches
Mail list logo
