[Kernel-packages] [Bug 1566708] Re: Failed to boot when install ubuntu16.04 beta2 desktop64 with EFI boot in Vmware ESXi
It'will be better to have a backport to ubuntu16.04 updates. best regards Yuhua Zou -- 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/1566708 Title: Failed to boot when install ubuntu16.04 beta2 desktop64 with EFI boot in Vmware ESXi Status in linux package in Ubuntu: Incomplete Bug description: I insatlled Ubuntu16.04 beta2 desktop (64bit) with EFI boot on VMware ESXi 6.0.0 build 2494585, ESXi 5.5.0 build 3029944, and the on-going develop branch vsphere2016. When finish installation and reboot, I notice this on boot: /dev/sda2: recovering journal /dev/sda2: clean, 184027/950272 files, 1023281/3801088 blocks And then it hangs right there. It happens every time I reboot the VM. WORKAROUND: Change boot mode from EFI to BIOS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634005] [NEW] linux treats first partition on sdcard as much bigger than it really is?
Public bug reported:
For some reason Linux (dd/mkfs.vfat/mkfs.ext4) treats the first
partition of my sdcard as 16GB regardless of what fdisk says it should
be. dd sees the other partitions as the correct size.
Also if I run mkfs.vfat on the first partition it is treated as a fuse
filesystem when mounted, it seems very strange. The whole card has been
zeroed out so it shouldn't be an issue of some other weird data on the
card. Pulling and reinserting the card after partitioning makes no
difference. I have also included the fdisk bootsector dump at the end of
this message.
Running linux 4.4.0-38.57 amd64
---
ii linux-headers-4.4.0-38 4.4.0-38.57
all Header files related to Linux kernel version 4.4.0
ii linux-headers-4.4.0-38-generic 4.4.0-38.57
amd64Linux kernel headers for version 4.4.0 on 64 bit x86
SMP
ii linux-image-4.4.0-38-generic 4.4.0-38.57
amd64Linux kernel image for version 4.4.0 on 64 bit x86 SMP
ii linux-image-extra-4.4.0-38-generic 4.4.0-38.57
amd64Linux kernel extra modules for version 4.4.0 on 64 bit
x86 SMP
ii linux-signed-image-4.4.0-38-generic 4.4.0-38.57
amd64Signed kernel image generic
ii linux-tools-4.4.0-38 4.4.0-38.57
amd64Linux kernel version specific tools for version
4.4.0-38
ii linux-tools-4.4.0-38-generic 4.4.0-38.57
amd64Linux kernel version specific tools for version
4.4.0-38
---
# fdisk -l /dev/sdd
Disk /dev/sdd: 29.8 GiB, 32010928128 bytes, 62521344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
# fdisk /dev/sdd
Welcome to fdisk (util-linux 2.27.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Device does not contain a recognized partition table.
Created a new DOS disklabel with disk identifier 0x57ca34c2.
Command (m for help): n
Partition type
p primary (0 primary, 0 extended, 4 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1): 1
First sector (2048-62521343, default 2048):
Last sector, +sectors or +size{K,M,G,T,P} (2048-62521343, default 62521343):
+512MiB
Created a new partition 1 of type 'Linux' and of size 512 MiB.
Command (m for help): p
Disk /dev/sdd: 29.8 GiB, 32010928128 bytes, 62521344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x57ca34c2
Device Boot Start End Sectors Size Id Type
/dev/sdd12048 1050623 1048576 512M 83 Linux
Command (m for help): n
Partition type
p primary (1 primary, 0 extended, 3 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (2-4, default 2):
First sector (1050624-62521343, default 1050624):
Last sector, +sectors or +size{K,M,G,T,P} (1050624-62521343, default 62521343):
+512MiB
Created a new partition 2 of type 'Linux' and of size 512 MiB.
Command (m for help): n
Partition type
p primary (2 primary, 0 extended, 2 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (3,4, default 3):
First sector (2099200-62521343, default 2099200):
Last sector, +sectors or +size{K,M,G,T,P} (2099200-62521343, default 62521343):
+1024MiB
Created a new partition 3 of type 'Linux' and of size 1 GiB.
Command (m for help): n
Partition type
p primary (3 primary, 0 extended, 1 free)
e extended (container for logical partitions)
Select (default e): p
Selected partition 4
First sector (4196352-62521343, default 4196352):
Last sector, +sectors or +size{K,M,G,T,P} (4196352-62521343, default 62521343):
Created a new partition 4 of type 'Linux' and of size 27.8 GiB.
Command (m for help): print
Disk /dev/sdd: 29.8 GiB, 32010928128 bytes, 62521344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x57ca34c2
Device Boot Start End Sectors Size Id Type
/dev/sdd1 2048 1050623 1048576 512M 83 Linux
/dev/sdd2 1050624 2099199 1048576 512M 83 Linux
/dev/sdd3 2099200 4196351 20971521G 83 Linux
/dev/sdd4 4196352 62521343 58324992 27.8G 83 Linux
Command (m for help): t
Partition number (1-4, default 4): 1
Partition type (type L to list all types): c
Changed type of partition 'Linux' to 'W95 FAT32 (LBA)'.
Command (m for help): print
Disk /dev/sdd: 29.8 GiB, 32010928128 bytes, 625213
[Kernel-packages] [Bug 1619552] Comment bridged from LTC Bugzilla
--- Comment From hegdevas...@in.ibm.com 2016-10-17 02:52 EDT--- (In reply to comment #16) > This bug was fixed in the package linux - 4.4.0-42.62 Thanks! -Vasant -- 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/1619552 Title: Failed to acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such file or directory) Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: == Comment: #0 - Mukesh K. Ojha - 2016-09-02 02:10:14 == ---Problem Description--- Kernel is failed to free the kobject while acknowledging the error log which has been notified two times. Contact Information = Contact Information = mukeo...@in.ibm.com ---uname output--- Ubuntu 16.04.01 LTS Machine Type = All power machine ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Steps to reproduce: 1.Boot the system to petitboot. 2. Issue FSP Soft reset of Service Processor From ASMI page. 3. After FSP comes up, boot the system to host OS. 4. In the host OS seen the failure to acknowledge for one of elog. root@p8wookie ~]# service opal_errd status Redirecting to /bin/systemctl status opal_errd.service opal_errd.service - opal_errd (PowerNV platform error handling) Service Loaded: loaded (/usr/lib/systemd/system/opal_errd.service; enabled) Active: active (running) since Wed 2016-08-03 07:55:03 CDT; 2min 4s ago Process: 3452 ExecStart=/usr/libexec/ppc64-diag/opal_errd start (code=exited, status=0/SUCCESS) Main PID: 3497 (opal_errd) CGroup: /system.slice/opal_errd.service ??3497 /usr/sbin/opal_errd Aug 03 07:57:03 p8wookie.aus.stglabs.ibm.com ELOG[3497]: LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service action required Aug 03 07:57:03 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such file or directory) Aug 03 07:57:04 p8wookie.aus.stglabs.ibm.com ELOG[3497]: LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service action required Aug 03 07:57:04 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such file or directory) Aug 03 07:57:05 p8wookie.aus.stglabs.ibm.com ELOG[3497]: LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service action required Aug 03 07:57:05 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such file or directory) Aug 03 07:57:06 p8wookie.aus.stglabs.ibm.com ELOG[3497]: LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service action required Aug 03 07:57:06 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such file or directory) Aug 03 07:57:07 p8wookie.aus.stglabs.ibm.com ELOG[3497]: LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service action required Aug 03 07:57:07 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such file or directory) [root@p8wookie ~]# cd /sys/firmware/opal/elog/ [root@p8wookie elog]# ls 0x5018d709 [root@p8wookie elog]# Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for Contact Information = mukeo...@in.ibm.com: -Attach sysctl -a output output to the bug. == Comment: #1 - Mukesh K. Ojha - 2016-09-02 02:12:45 == Upstream commit : commit a9cbf0b2195b695cbcaa4e2770948c212e9a Author: Mukesh Ojha Date: Mon Aug 22 12:17:44 2016 +0530 powerpc/powernv : Drop reference added by kset_find_obj() In a situation, where Linux kernel gets notified about duplicate error log from OPAL, it is been observed that kernel fails to remove sysfs entries (/sys/firmware/opal/elog/0x) of such error logs. This is because, we currently search the error log/dump kobject in the kset list via 'kset_find_obj()' routine. Which eventually increment the reference count by one, once it founds the kobject. Above patch is the solution of this bugzilla. Kindly pull this patch in for both Ubuntu 16.04 LTS and Ubuntu 16.10. -Mukesh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1619552/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages Mor
[Kernel-packages] [Bug 1634005] Re: linux treats first partition on sdcard as much bigger than it really is?
Taking the first sector output and decoding it shows:
00 - 00 01 01 - 0c - 3f a0 00 - 00 08 00 00 - 00 00 10 00
00 - 00 81 01 - 83 - 3f 20 00 - 00 08 10 00 - 00 00 10 00
00 - 00 01 01 - 83 - 3f 20 00 - 00 08 20 00 - 00 00 20 00
00 - 00 01 01 - 83 - 3f e0 3f - 00 08 40 00 - 00 f8 79 03
Which looks correct, so I'm not sure whats causing it to think partition
1 is 16GB, is there some kind of special casing for sdcards?
--
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/1634005
Title:
linux treats first partition on sdcard as much bigger than it really
is?
Status in linux package in Ubuntu:
New
Bug description:
For some reason Linux (dd/mkfs.vfat/mkfs.ext4) treats the first
partition of my sdcard as 16GB regardless of what fdisk says it should
be. dd sees the other partitions as the correct size.
Also if I run mkfs.vfat on the first partition it is treated as a fuse
filesystem when mounted, it seems very strange. The whole card has
been zeroed out so it shouldn't be an issue of some other weird data
on the card. Pulling and reinserting the card after partitioning makes
no difference. I have also included the fdisk bootsector dump at the
end of this message.
Running linux 4.4.0-38.57 amd64
---
ii linux-headers-4.4.0-38 4.4.0-38.57
all Header files related to Linux kernel version 4.4.0
ii linux-headers-4.4.0-38-generic 4.4.0-38.57
amd64Linux kernel headers for version 4.4.0 on 64 bit x86
SMP
ii linux-image-4.4.0-38-generic 4.4.0-38.57
amd64Linux kernel image for version 4.4.0 on 64 bit x86
SMP
ii linux-image-extra-4.4.0-38-generic 4.4.0-38.57
amd64Linux kernel extra modules for version 4.4.0 on 64
bit x86 SMP
ii linux-signed-image-4.4.0-38-generic 4.4.0-38.57
amd64Signed kernel image generic
ii linux-tools-4.4.0-38 4.4.0-38.57
amd64Linux kernel version specific tools for version
4.4.0-38
ii linux-tools-4.4.0-38-generic 4.4.0-38.57
amd64Linux kernel version specific tools for version
4.4.0-38
---
# fdisk -l /dev/sdd
Disk /dev/sdd: 29.8 GiB, 32010928128 bytes, 62521344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
# fdisk /dev/sdd
Welcome to fdisk (util-linux 2.27.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Device does not contain a recognized partition table.
Created a new DOS disklabel with disk identifier 0x57ca34c2.
Command (m for help): n
Partition type
p primary (0 primary, 0 extended, 4 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1): 1
First sector (2048-62521343, default 2048):
Last sector, +sectors or +size{K,M,G,T,P} (2048-62521343, default 62521343):
+512MiB
Created a new partition 1 of type 'Linux' and of size 512 MiB.
Command (m for help): p
Disk /dev/sdd: 29.8 GiB, 32010928128 bytes, 62521344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x57ca34c2
Device Boot Start End Sectors Size Id Type
/dev/sdd12048 1050623 1048576 512M 83 Linux
Command (m for help): n
Partition type
p primary (1 primary, 0 extended, 3 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (2-4, default 2):
First sector (1050624-62521343, default 1050624):
Last sector, +sectors or +size{K,M,G,T,P} (1050624-62521343, default
62521343): +512MiB
Created a new partition 2 of type 'Linux' and of size 512 MiB.
Command (m for help): n
Partition type
p primary (2 primary, 0 extended, 2 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (3,4, default 3):
First sector (2099200-62521343, default 2099200):
Last sector, +sectors or +size{K,M,G,T,P} (2099200-62521343, default
62521343): +1024MiB
Created a new partition 3 of type 'Linux' and of size 1 GiB.
Command (m for help): n
Partition type
p primary (3 primary, 0 extended, 1 free)
e extended (container for logical partitions)
Select (default e): p
Selected partition 4
First sector (4196352-62521343, default 4196352):
Last sector, +sectors or +size{K,M,G,T,P} (4196352-62521343, default
62521343):
Created a
[Kernel-packages] [Bug 1632252] Re: linux autopkgtest kills sshd in testbed
It is still happening. I was running journalctl -f on the testbed while it ran, and was able to copy the last 9000 lines of scrollback from tmux. ** Attachment added: "journal" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1632252/+attachment/4762321/+files/journal.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/1632252 Title: linux autopkgtest kills sshd in testbed Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: The current linux autopkgtests in yakkety are caught in an eternal "temporary failure" retry loop. They stopped timing out, but in the middle of the tests they kill sshd. Tail of test output: 09:01:00 DEBUG| [stdout] preparing apparmor_2.10.95-4ubuntu5.dsc... done 09:01:00 DEBUG| [stdout] 09:01:40 ERROR| [stderr] Run libapparmor testsuite (with python3) ... ok 09:01:40 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites) 09:01:48 DEBUG| [stdout] preparing apparmor_2.10.95-4ubuntu5.dsc... done 09:01:48 DEBUG| [stdout] 09:19:27 ERROR| [stderr] Run parser regression tests ... ok 09:19:27 ERROR| [stderr] test_regression_testsuite (__main__.ApparmorTestsuites) 09:19:33 DEBUG| [stdout] preparing apparmor_2.10.95-4ubuntu5.dsc... done 09:19:33 DEBUG| [stdout] Killed Killed Connection to 10.220.42.236 closed by remote host. Exit request sent. autopkgtest [09:24:42]: ERROR: testbed failure: testbed auxverb failed with exit code 255 Console output during the test: Ubuntu 16.10 autopkgtest ttyS0 autopkgtest login: [ 3512.996305] AppArmor: change_hat: Invalid input '^open' [ 3513.000678] AppArmor: change_hat: Invalid input '^'[ 3513.013965] AppArmor: change_hat: Invalid input, NULL hat and NULL magic [ 3513.019831] AppArmor: change_hat: Invalid input, NULL hat and NULL magic [ 3513.024872] AppArmor: change_hat: Invalid input '^open'AppArmor: change_hat: Invalid input '^' [ 3513.026539] AppArmor: change_hat: Invalid input '^'[ 3638.281408] Out of memory: Kill process 587 (rsyslogd) score 8 or sacrifice child [ 3638.284907] Killed process 587 (rsyslogd) total-vm:107460kB, anon-rss:67892kB, file-rss:2548kB, shmem-rss:0kB [ 3638.306990] Out of memory: Kill process 300 (systemd-journal) score 2 or sacrifice child [ 3638.308985] Killed process 300 (systemd-journal) total-vm:46184kB, anon-rss:460kB, file-rss:3752kB, shmem-rss:15412kB [ 3638.319337] Out of memory: Kill process 2636 (autotest-local) score 1 or sacrifice child [ 3638.320394] Killed process 10325 (autotest-local) total-vm:18092kB, anon-rss:7296kB, file-rss:3544kB, shmem-rss:0kB [ 3638.345419] Out of memory: Kill process 2636 (autotest-local) score 1 or sacrifice child [ 3638.347095] Killed process 2638 (autotest-local) total-vm:17836kB, anon-rss:7160kB, file-rss:1752kB, shmem-rss:0kB [ 3638.368917] Out of memory: Kill process 2636 (autotest-local) score 1 or sacrifice child [ 3638.369954] Killed process 2637 (autotest-local) total-vm:17836kB, anon-rss:7160kB, file-rss:1684kB, shmem-rss:0kB [ 3638.479196] Out of memory: Kill process 2636 (autotest-local) score 1 or sacrifice child [ 3638.482968] Killed process 2636 (autotest-local) total-vm:17836kB, anon-rss:7248kB, file-rss:5864kB, shmem-rss:0kB [ 3638.501050] Out of memory: Kill process 10619 (python) score 1 or sacrifice child [ 3638.502022] Killed process 14752 (make) total-vm:6052kB, anon-rss:196kB, file-rss:2032kB, shmem-rss:0kB [ 3638.511243] Out of memory: Kill process 10619 (python) score 1 or sacrifice child [ 3638.512224] Killed process 10619 (python) total-vm:16752kB, anon-rss:5836kB, file-rss:6148kB, shmem-rss:0kB [ 3638.525104] Out of memory: Kill process 3382 (python) score 0 or sacrifice child [ 3638.526060] Killed process 3382 (python) total-vm:21296kB, anon-rss:3732kB, file-rss:4080kB, shmem-rss:0kB [ 3638.545114] Out of memory: Kill process 553 (haveged) score 0 or sacrifice child [ 3638.546068] Killed process 553 (haveged) total-vm:8028kB, anon-rss:4780kB, file-rss:1468kB, shmem-rss:0kB [ 3638.573449] Out of memory: Kill process 10373 (sshd) score 0 or sacrifice child [ 3638.574353] Killed process 11430 (sshd) total-vm:1kB, anon-rss:1712kB, file-rss:2960kB, shmem-rss:0kB [ 3638.591696] Out of memory: Kill process 10373 (sshd) score 0 or sacrifice child [ 3638.595493] Killed process 10373 (sshd) total-vm:13460kB, anon-rss:752kB, file-rss:5476kB, shmem-rss:4kB [ 3638.605938] Out of memory: Kill process 898 (sshd) score 0 or sacrifice child [ 3638.607617] Killed process 911 (sshd) total-vm:13804kB, anon-rss:1120kB, file-rss:3184kB, shmem-rss:0kB [ 3638.626950] Out of memory: Kill process 898 (sshd) score 0 or sacrifice child [ 3638.627839] Killed process 898 (sshd) total-vm:13460kB, anon-rss:744kB, file-rss:5436kB, shmem-rs
[Kernel-packages] [Bug 1634005] Re: linux treats first partition on sdcard as much bigger than it really is?
blockdev also reports the wrong value:
# blockdev --getsz /dev/sdd1
32787056
strace shows that fstat() reports the wrong value.
9175 02:20:07.714355 open("/dev/sdd1", O_RDONLY) = 3
9175 02:20:07.714387 uname({sysname="Linux", nodename="desktop-clc",
release="4.4.0-38-generic", version="#57-Ubuntu SMP Tue Sep 6 15:42:33 UTC
2016", machine="x86_64", domainname="(none)"}) = 0
9175 02:20:07.714420 ioctl(3, BLKGETSIZE64, 0x7fff6d39def0) = -1
ENOTTY (Inappropriate ioctl for device)
9175 02:20:07.718949 ioctl(3, BLKGETSIZE, 0x7fff6d39de08) = -1
ENOTTY (Inappropriate ioctl for device)
9175 02:20:07.719001 ioctl(3, FDGETPRM, 0x7fff6d39de10) = -1 ENOTTY
(Inappropriate ioctl for device)
9175 02:20:07.719031 fstat(3, {st_dev=makedev(0, 6), st_ino=714,
st_mode=S_IFREG|0644, st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096,
st_blocks=32787056, st_size=16786972672,
st_atime=2016/10/17-02:15:26.246576853, st_mtime=2016/10/17-02:15:26.242576837,
st_ctime=2016/10/17-02:15:26.242576837}) = 0
--
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/1634005
Title:
linux treats first partition on sdcard as much bigger than it really
is?
Status in linux package in Ubuntu:
Incomplete
Bug description:
For some reason Linux (dd/mkfs.vfat/mkfs.ext4) treats the first
partition of my sdcard as 16GB regardless of what fdisk says it should
be. dd sees the other partitions as the correct size.
Also if I run mkfs.vfat on the first partition it is treated as a fuse
filesystem when mounted, it seems very strange. The whole card has
been zeroed out so it shouldn't be an issue of some other weird data
on the card. Pulling and reinserting the card after partitioning makes
no difference. I have also included the fdisk bootsector dump at the
end of this message.
Running linux 4.4.0-38.57 amd64
---
ii linux-headers-4.4.0-38 4.4.0-38.57
all Header files related to Linux kernel version 4.4.0
ii linux-headers-4.4.0-38-generic 4.4.0-38.57
amd64Linux kernel headers for version 4.4.0 on 64 bit x86
SMP
ii linux-image-4.4.0-38-generic 4.4.0-38.57
amd64Linux kernel image for version 4.4.0 on 64 bit x86
SMP
ii linux-image-extra-4.4.0-38-generic 4.4.0-38.57
amd64Linux kernel extra modules for version 4.4.0 on 64
bit x86 SMP
ii linux-signed-image-4.4.0-38-generic 4.4.0-38.57
amd64Signed kernel image generic
ii linux-tools-4.4.0-38 4.4.0-38.57
amd64Linux kernel version specific tools for version
4.4.0-38
ii linux-tools-4.4.0-38-generic 4.4.0-38.57
amd64Linux kernel version specific tools for version
4.4.0-38
---
# fdisk -l /dev/sdd
Disk /dev/sdd: 29.8 GiB, 32010928128 bytes, 62521344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
# fdisk /dev/sdd
Welcome to fdisk (util-linux 2.27.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Device does not contain a recognized partition table.
Created a new DOS disklabel with disk identifier 0x57ca34c2.
Command (m for help): n
Partition type
p primary (0 primary, 0 extended, 4 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1): 1
First sector (2048-62521343, default 2048):
Last sector, +sectors or +size{K,M,G,T,P} (2048-62521343, default 62521343):
+512MiB
Created a new partition 1 of type 'Linux' and of size 512 MiB.
Command (m for help): p
Disk /dev/sdd: 29.8 GiB, 32010928128 bytes, 62521344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x57ca34c2
Device Boot Start End Sectors Size Id Type
/dev/sdd12048 1050623 1048576 512M 83 Linux
Command (m for help): n
Partition type
p primary (1 primary, 0 extended, 3 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (2-4, default 2):
First sector (1050624-62521343, default 1050624):
Last sector, +sectors or +size{K,M,G,T,P} (1050624-62521343, default
62521343): +512MiB
Created a new partition 2 of type 'Linux' and of size 512 MiB.
Command (m for help): n
Partition type
p primary (2 primary, 0 extended, 2 free)
e extended (container for logical partitions)
Select (default p):
[Kernel-packages] [Bug 1634005] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1634005
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 comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1634005
Title:
linux treats first partition on sdcard as much bigger than it really
is?
Status in linux package in Ubuntu:
Incomplete
Bug description:
For some reason Linux (dd/mkfs.vfat/mkfs.ext4) treats the first
partition of my sdcard as 16GB regardless of what fdisk says it should
be. dd sees the other partitions as the correct size.
Also if I run mkfs.vfat on the first partition it is treated as a fuse
filesystem when mounted, it seems very strange. The whole card has
been zeroed out so it shouldn't be an issue of some other weird data
on the card. Pulling and reinserting the card after partitioning makes
no difference. I have also included the fdisk bootsector dump at the
end of this message.
Running linux 4.4.0-38.57 amd64
---
ii linux-headers-4.4.0-38 4.4.0-38.57
all Header files related to Linux kernel version 4.4.0
ii linux-headers-4.4.0-38-generic 4.4.0-38.57
amd64Linux kernel headers for version 4.4.0 on 64 bit x86
SMP
ii linux-image-4.4.0-38-generic 4.4.0-38.57
amd64Linux kernel image for version 4.4.0 on 64 bit x86
SMP
ii linux-image-extra-4.4.0-38-generic 4.4.0-38.57
amd64Linux kernel extra modules for version 4.4.0 on 64
bit x86 SMP
ii linux-signed-image-4.4.0-38-generic 4.4.0-38.57
amd64Signed kernel image generic
ii linux-tools-4.4.0-38 4.4.0-38.57
amd64Linux kernel version specific tools for version
4.4.0-38
ii linux-tools-4.4.0-38-generic 4.4.0-38.57
amd64Linux kernel version specific tools for version
4.4.0-38
---
# fdisk -l /dev/sdd
Disk /dev/sdd: 29.8 GiB, 32010928128 bytes, 62521344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
# fdisk /dev/sdd
Welcome to fdisk (util-linux 2.27.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Device does not contain a recognized partition table.
Created a new DOS disklabel with disk identifier 0x57ca34c2.
Command (m for help): n
Partition type
p primary (0 primary, 0 extended, 4 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1): 1
First sector (2048-62521343, default 2048):
Last sector, +sectors or +size{K,M,G,T,P} (2048-62521343, default 62521343):
+512MiB
Created a new partition 1 of type 'Linux' and of size 512 MiB.
Command (m for help): p
Disk /dev/sdd: 29.8 GiB, 32010928128 bytes, 62521344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x57ca34c2
Device Boot Start End Sectors Size Id Type
/dev/sdd12048 1050623 1048576 512M 83 Linux
Command (m for help): n
Partition type
p primary (1 primary, 0 extended, 3 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (2-4, default 2):
First sector (1050624-62521343, default 1050624):
Last sector, +sectors or +size{K,M,G,T,P} (1050624-62521343, default
62521343): +512MiB
Created a new partition 2 of type 'Linux' and of size 512 MiB.
Command (m for help): n
Partition type
p primary (2 primary, 0 extended, 2 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (3,4, default 3):
First sector (2099200-62521343, default 2099200):
Last sector, +sectors or +size{K,M,G,T,P} (2099200-62521343, default
62521343): +1024MiB
Created a new partition 3 of type 'Linux' and of size 1 GiB.
Command (m for help): n
Partition type
p primary (3 primary, 0 extended, 1 free)
e extended (container for logical partitions)
Select (default e): p
Selected partition 4
First sector (4196352-62521343, default 4196352
[Kernel-packages] [Bug 1504445] Re: FocalTech touchpad stops working after suspend
Sorry, I forgot to mention that it does work :-) -- 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/1504445 Title: FocalTech touchpad stops working after suspend Status in linux package in Ubuntu: Incomplete Bug description: I have an Asus V502LX the persian version of the Asus K501LX. I have Ubuntu 14.04 installed and the kernel 4.1.6 installed. I had to install the kernel 4.1.6 to have the touchpad recognised. Under kernel 3.19.30, as I am running now to file in this bug, the touchpad is recognised as a simple mouse (no two fingers scrolling...) and the problem I am describing below is also present... I noticed one problem. The Focaltech touchpad is not working after suspending the computer. Here is what I could find about the touchpad in /proc/bus/input/devices I: Bus=0011 Vendor=0002 Product=0012 Version= N: Name="FocalTechPS/2 FocalTech FocalTech Touchpad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input5 U: Uniq= H: Handlers=mouse0 event4 B: PROP=5 B: EV=b B: KEY=e520 1 0 0 0 0 B: ABS=2608003 Before suspending the computer, I can deactivate and activate again the touchpad with the hotkey of my keyboard without problem. However, once the computer suspended, nothing work to re-activate the touchpad. I tried a solution given on internet but it doesn't work properly. I created a file here /etc/pm/sleep.d/trackpad sudo gedit /etc/pm/sleep.d/trackpad and add the following #!/bin/sh case "$1" in suspend|hibernate) modprobe -r psmouse; resume|thaw) modprobe psmouse; esac With this file, the computer refuse to suspend. The touchpad keep working so it does something but I can't make my computer sleeping... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-30-generic 3.19.0-30.34~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 9 12:05:16 2015 InstallationDate: Installed on 2015-09-26 (12 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: linux-lts-vivid UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yogo 2073 F pulseaudio /dev/snd/controlC0: yogo 2073 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=943b03af-c1bf-489e-8e42-485931fc619c InstallationDate: Installed on 2015-09-26 (12 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. K501LX Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed root=UUID=37bd087e-a2f6-437e-8d20-b19536eb738a ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6 RelatedPackageVersions: linux-restricted-modules-3.19.0-30-generic N/A linux-backports-modules-3.19.0-30-generic N/A linux-firmware 1.127.15 Tags: trusty Uname: Linux 3.19.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True dmi.bios.date: 04/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K501LX.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K501LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK501LX.203:bd04/16/2015:svnASUSTeKCOMPUTERINC.:pnK501LX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501LX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: K501LX dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504445/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow
Confirmed with 4.8.0-040800.201610022031 from http://kernel.ubuntu.com /~kernel-ppa/mainline/v4.8/ -- 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/1626436 Title: [4.8 regression] boot has become very slow Status in linux package in Ubuntu: Triaged Bug description: With yakkety's recent update from linux 4.4 to 4.8 booting has become a lot slower. It's not one service in particular, but without "quiet" and "splash" you can now easily read every single line instead of that whole wall of text zipping by. It now takes over 20s instead of ~10 seconds to boot. This is even more dramatic when factoring out the recent boot hang of NetworkManager (bug 1622893) and disabling lightdm: sudo systemctl mask NetworkManager NetworkManager-wait-online lightdm then booting with 4.4 takes 1.5s and with 4.8 19.5s (!). Some excerps from systemd-analyze blame: 4.4: 474ms postfix@-.service 395ms lxd-containers.service 305ms networking.service 4.8: 4.578s postfix@-.service 7.300s lxd-containers.service 6.285s networking.service I attach the full outputs of critical-chain and analyze for 4.4 and 4.8 for reference. This is much less noticeable in the running system. There is no immediate feeling of sluggishness (although my system is by and large idle). I compared the time of sbuilding colord under similar circumstances (-j4, building on tmpfs, thus no hard disk delays; running with fully pre-loaded apt-cacher-ng thus no random network delays), and with 4.4 it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit slower, but much less dramatically than during boot, so this is either happening when a lot of processes run in parallel, or is perhaps related to setting up cgroups. One thing I noticed that during sbuild in 4.8 "top" shows ridiculous loads (~ 250) under 4.8, while it's around 4 or 5 under 4.8. But that doesn't reflect in actual sluggishness, so this might be just an unrelated bug. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-11-generic 4.8.0-11.12 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: martin 3049 F...m pulseaudio /dev/snd/pcmC0D0p: martin 3049 F...m pulseaudio /dev/snd/controlC0: martin 3049 F pulseaudio Date: Thu Sep 22 09:42:56 2016 EcryptfsInUse: Yes MachineType: LENOVO 2324CTO ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ systemd.debug-shell RelatedPackageVersions: linux-restricted-modules-4.8.0-11-generic N/A linux-backports-modules-4.8.0-11-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET95WW (2.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324CTO dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2324CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1504445] Re: FocalTech touchpad stops working after suspend
Hello, I didn't tested that patch following that way, https://wiki.ubuntu.com/Kernel/KernelBisection#Testing_a_newly_released_patch_from_upstream , but I did test the pacth by building my own 4.8 kernel (https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel) with the Ubuntu- lts-4.8.0-25.27_16.04.1 kernel. Sincerely, Thatoo -- 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/1504445 Title: FocalTech touchpad stops working after suspend Status in linux package in Ubuntu: Incomplete Bug description: I have an Asus V502LX the persian version of the Asus K501LX. I have Ubuntu 14.04 installed and the kernel 4.1.6 installed. I had to install the kernel 4.1.6 to have the touchpad recognised. Under kernel 3.19.30, as I am running now to file in this bug, the touchpad is recognised as a simple mouse (no two fingers scrolling...) and the problem I am describing below is also present... I noticed one problem. The Focaltech touchpad is not working after suspending the computer. Here is what I could find about the touchpad in /proc/bus/input/devices I: Bus=0011 Vendor=0002 Product=0012 Version= N: Name="FocalTechPS/2 FocalTech FocalTech Touchpad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input5 U: Uniq= H: Handlers=mouse0 event4 B: PROP=5 B: EV=b B: KEY=e520 1 0 0 0 0 B: ABS=2608003 Before suspending the computer, I can deactivate and activate again the touchpad with the hotkey of my keyboard without problem. However, once the computer suspended, nothing work to re-activate the touchpad. I tried a solution given on internet but it doesn't work properly. I created a file here /etc/pm/sleep.d/trackpad sudo gedit /etc/pm/sleep.d/trackpad and add the following #!/bin/sh case "$1" in suspend|hibernate) modprobe -r psmouse; resume|thaw) modprobe psmouse; esac With this file, the computer refuse to suspend. The touchpad keep working so it does something but I can't make my computer sleeping... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-30-generic 3.19.0-30.34~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 9 12:05:16 2015 InstallationDate: Installed on 2015-09-26 (12 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: linux-lts-vivid UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yogo 2073 F pulseaudio /dev/snd/controlC0: yogo 2073 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=943b03af-c1bf-489e-8e42-485931fc619c InstallationDate: Installed on 2015-09-26 (12 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. K501LX Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed root=UUID=37bd087e-a2f6-437e-8d20-b19536eb738a ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6 RelatedPackageVersions: linux-restricted-modules-3.19.0-30-generic N/A linux-backports-modules-3.19.0-30-generic N/A linux-firmware 1.127.15 Tags: trusty Uname: Linux 3.19.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True dmi.bios.date: 04/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K501LX.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K501LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK501LX.203:bd04/16/2015:svnASUSTeKCOMPUTERINC.:pnK501LX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501LX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: K501LX dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To mana
[Kernel-packages] [Bug 1632844] Re: linux: 3.13.0-99.146 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- 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/1632844 Title: linux: 3.13.0-99.146 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-99.146 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632806] Re: linux-armadaxp: 3.2.0-1675.101 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1632806 Title: linux-armadaxp: 3.2.0-1675.101 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-armadaxp source package in Precise: In Progress Bug description: This bug is for tracking the 3.2.0-1675.101 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true kernel-stable-master-bug: 1632801 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632802] Re: linux-ti-omap4: 3.2.0-1490.117 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1632802 Title: linux-ti-omap4: 3.2.0-1490.117 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-ti-omap4 source package in Precise: Confirmed Bug description: This bug is for tracking the 3.2.0-1490.117 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true kernel-stable-master-bug: 1632801 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632801] Re: linux: 3.2.0-112.154 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- 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/1632801 Title: linux: 3.2.0-112.154 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: Confirmed Bug description: This bug is for tracking the 3.2.0-112.154 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634034] [NEW] kvm default ubuntu kernel: Kernel panic - not syncing: Fatal exception: panic_on_oops
You have been subscribed to a public bug:
During guest/isolated container execution following kernel bug got
triggered:
[ 249.792522] Modules linked in: bridge stp llc binfmt_misc qeth_l2 chsc_sch
eadm_sch tape_3590 tape tape_class qeth ccwgroup dm_round_robin ib_iser rdma_cm
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi
scsi_transport_iscsi dm_multipath btrfs zlib_deflate raid10 raid456
async_memcpy async_raid6_recov async_pq async_xor async_tx xor raid6_pq
libcrc32c raid1 linear raid0 ghash_s390 prng aes_s390 des_s390 des_generic
sha512_s390 sha256_s390 sha1_s390 sha_common dasd_eckd_mod dasd_mod zfcp qdio
scsi_transport_fc
[ 249.792558] CPU: 1 PID: 2461 Comm: qemu-system-s39 Not tainted
4.4.0-42-generic #62-Ubuntu
[ 249.792560] task: edf44c90 ti: 7be68000 task.ti:
7be68000
[ 249.792562] User PSW : 070520018000 03ff9e683730
[ 249.792564]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0
EA:3
User GPRS: f000 0001 0001
0002
[ 249.792566]03ff9e789420 0948
03ffc7c7d480
[ 249.792568] 0948
fc00
[ 249.792569]03ff9e789000 03ff9e6845e6
03ff7f5297b0
[ 249.792577] User Code: 03ff9e683720: ec32000100d9aghik %r3,%r2,1
03ff9e683726: b9040012lgr %r1,%r2
#03ff9e68372a: c0482e7blarl
%r4,3ff9e789420
>03ff9e683730: eb134030csg %r1,%r3,0(%r4)
03ff9e683736: ec1200288064cgrj
%r1,%r2,8,3ff9e683786
03ff9e68373c: c42800082e72lgrl
%r2,3ff9e789420
03ff9e683742: c418000842aflgrl
%r1,3ff9e78bca0
03ff9e683748: a7f4ff09brc 15,3ff9e68355a
[ 249.792602] Last Breaking-Event-Address:
[ 249.792604] [<03ff9e68355e>] 0x3ff9e68355e
[ 249.792605]
[ 249.792606] Kernel panic - not syncing: Fatal exception: panic_on_oops
#===
#=== Steps to Reproduce
#===
1. Use the KVM kernel module with qemu
By applying following upstream patch this bug was not triggered again:
commit f045402984404ddc11016358411e445192919047
Author: David Hildenbrand
Date: Thu Jul 7 10:44:10 2016 +0200
s390/mm: fix gmap tlb flush issues
__tlb_flush_asce() should never be used if multiple asce belong to a
mm.
As this function changes mm logic determining if local or global tlb
flushes will be neded, we might end up flushing only the gmap asce on all
CPUs and a follow up mm asce flushes will only flush on the local CPU,
although that asce ran on multiple CPUs.
The missing tlb flushes will provoke strange faults in user space and even
low address protections in user space, crashing the kernel.
Fixes: 1b948d6caec4 ("s390/mm,tlb: optimize TLB flushing for zEC12")
Cc: sta...@vger.kernel.org # 3.15+
Reported-by: Sascha Silbe
Acked-by: Martin Schwidefsky
Signed-off-by: David Hildenbrand
Signed-off-by: Martin Schwidefsky
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-147597 severity-high
targetmilestone-inin16041
--
kvm default ubuntu kernel: Kernel panic - not syncing: Fatal exception:
panic_on_oops
https://bugs.launchpad.net/bugs/1634034
You received this bug notification because you are a member of Kernel Packages,
which is subscribed to linux in Ubuntu.
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] s2lp6g002 (s390x.zKVM) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-21.23/s2lp6g002__4.8.0-21.23__2016-10-17_08-22-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634034] Ubuntu sosreport
Default Comment by Bridge
** Attachment added: "Ubuntu sosreport"
https://bugs.launchpad.net/bugs/1634034/+attachment/4762346/+files/sosreport-PeterMorjan-20161014151342.tar.xz
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1634034
Title:
kvm default ubuntu kernel: Kernel panic - not syncing: Fatal
exception: panic_on_oops
Status in linux package in Ubuntu:
New
Bug description:
During guest/isolated container execution following kernel bug got
triggered:
[ 249.792522] Modules linked in: bridge stp llc binfmt_misc qeth_l2 chsc_sch
eadm_sch tape_3590 tape tape_class qeth ccwgroup dm_round_robin ib_iser rdma_cm
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi
scsi_transport_iscsi dm_multipath btrfs zlib_deflate raid10 raid456
async_memcpy async_raid6_recov async_pq async_xor async_tx xor raid6_pq
libcrc32c raid1 linear raid0 ghash_s390 prng aes_s390 des_s390 des_generic
sha512_s390 sha256_s390 sha1_s390 sha_common dasd_eckd_mod dasd_mod zfcp qdio
scsi_transport_fc
[ 249.792558] CPU: 1 PID: 2461 Comm: qemu-system-s39 Not tainted
4.4.0-42-generic #62-Ubuntu
[ 249.792560] task: edf44c90 ti: 7be68000 task.ti:
7be68000
[ 249.792562] User PSW : 070520018000 03ff9e683730
[ 249.792564]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0
EA:3
User GPRS: f000 0001 0001
0002
[ 249.792566]03ff9e789420 0948
03ffc7c7d480
[ 249.792568] 0948
fc00
[ 249.792569]03ff9e789000 03ff9e6845e6
03ff7f5297b0
[ 249.792577] User Code: 03ff9e683720: ec32000100d9aghik %r3,%r2,1
03ff9e683726: b9040012lgr %r1,%r2
#03ff9e68372a: c0482e7blarl
%r4,3ff9e789420
>03ff9e683730: eb134030csg %r1,%r3,0(%r4)
03ff9e683736: ec1200288064cgrj
%r1,%r2,8,3ff9e683786
03ff9e68373c: c42800082e72lgrl
%r2,3ff9e789420
03ff9e683742: c418000842aflgrl
%r1,3ff9e78bca0
03ff9e683748: a7f4ff09brc 15,3ff9e68355a
[ 249.792602] Last Breaking-Event-Address:
[ 249.792604] [<03ff9e68355e>] 0x3ff9e68355e
[ 249.792605]
[ 249.792606] Kernel panic - not syncing: Fatal exception: panic_on_oops
#===
#=== Steps to Reproduce
#===
1. Use the KVM kernel module with qemu
By applying following upstream patch this bug was not triggered again:
commit f045402984404ddc11016358411e445192919047
Author: David Hildenbrand
Date: Thu Jul 7 10:44:10 2016 +0200
s390/mm: fix gmap tlb flush issues
__tlb_flush_asce() should never be used if multiple asce belong to
a mm.
As this function changes mm logic determining if local or global tlb
flushes will be neded, we might end up flushing only the gmap asce on all
CPUs and a follow up mm asce flushes will only flush on the local CPU,
although that asce ran on multiple CPUs.
The missing tlb flushes will provoke strange faults in user space and even
low address protections in user space, crashing the kernel.
Fixes: 1b948d6caec4 ("s390/mm,tlb: optimize TLB flushing for zEC12")
Cc: sta...@vger.kernel.org # 3.15+
Reported-by: Sascha Silbe
Acked-by: Martin Schwidefsky
Signed-off-by: David Hildenbrand
Signed-off-by: Martin Schwidefsky
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634034/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] kernel02 (s390x.zVM) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-21.23/kernel02__4.8.0-21.23__2016-10-17_08-22-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1574982] Re: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler
The patch in comment #39 or the env var in comment #38 both work for me. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1574982 Title: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler Status in dkms package in Ubuntu: Invalid Status in gcc-defaults package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in dkms source package in Xenial: Invalid Status in linux source package in Xenial: Fix Released Bug description: Installing the latest 4.4.0-22 kernel ends with that error logged into dkmsbuildlog (only affect yakkety kernel; 4.4.0-22 kernel installation on xenial is fine) https://launchpadlibrarian.net/256055415/DKMSBuildLog.txt make "CC=cc" KBUILD_VERBOSE= -C /lib/modules/4.4.0-22-generic/build M=/var/lib/dkms/nvidia-361/361.42/build ARCH=x86_64 NV_KERNEL_SOURCES=/lib/modules/4.4.0-22-generic/build NV_KERNEL_OUTPUT=/lib/modules/4.4.0-22-generic/build NV_KERNEL_MODULES="nvidia nvidia-uvm nvidia-modeset" INSTALL_MOD_DIR=kernel/drivers/video modules make[1]: Entering directory '/usr/src/linux-headers-4.4.0-22-generic' arch/x86/Makefile:133: stack-protector enabled but compiler support broken Makefile:670: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler the latest error logged is: /var/lib/dkms/nvidia-361/361.42/build/nvidia/nv-frontend.c:1:0: error: code model kernel does not support PIC mode Looks like it is related to the latest changes updates: gcc-6/gcc-5 5.3.1-16ubuntu2 (some packages built with gcc-6; gcc-5 disabled for the packages built with gcc-6) Maybe some alternatives has not been updated to take care of these changes, as asked some time ago: http://askubuntu.com/questions/26498/choose-gcc-and-g-version This has been firstly reported against a nvidia crash: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1574838 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gcc 4:5.3.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Apr 26 08:41:32 2016 SourcePackage: gcc-defaults UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem2014 F pulseaudio /dev/snd/pcmC0D0p: oem2014 F...m pulseaudio /dev/snd/controlC0: oem2014 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16 IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: ubuntu ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: Tags: yakkety Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1574982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscri
[Kernel-packages] [Bug 1634034] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2016-10-17 04:23 EDT---
Canonical, please assign to the appropriate package . Thx
--
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/1634034
Title:
kvm default ubuntu kernel: Kernel panic - not syncing: Fatal
exception: panic_on_oops
Status in linux package in Ubuntu:
New
Bug description:
During guest/isolated container execution following kernel bug got
triggered:
[ 249.792522] Modules linked in: bridge stp llc binfmt_misc qeth_l2 chsc_sch
eadm_sch tape_3590 tape tape_class qeth ccwgroup dm_round_robin ib_iser rdma_cm
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi
scsi_transport_iscsi dm_multipath btrfs zlib_deflate raid10 raid456
async_memcpy async_raid6_recov async_pq async_xor async_tx xor raid6_pq
libcrc32c raid1 linear raid0 ghash_s390 prng aes_s390 des_s390 des_generic
sha512_s390 sha256_s390 sha1_s390 sha_common dasd_eckd_mod dasd_mod zfcp qdio
scsi_transport_fc
[ 249.792558] CPU: 1 PID: 2461 Comm: qemu-system-s39 Not tainted
4.4.0-42-generic #62-Ubuntu
[ 249.792560] task: edf44c90 ti: 7be68000 task.ti:
7be68000
[ 249.792562] User PSW : 070520018000 03ff9e683730
[ 249.792564]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0
EA:3
User GPRS: f000 0001 0001
0002
[ 249.792566]03ff9e789420 0948
03ffc7c7d480
[ 249.792568] 0948
fc00
[ 249.792569]03ff9e789000 03ff9e6845e6
03ff7f5297b0
[ 249.792577] User Code: 03ff9e683720: ec32000100d9aghik %r3,%r2,1
03ff9e683726: b9040012lgr %r1,%r2
#03ff9e68372a: c0482e7blarl
%r4,3ff9e789420
>03ff9e683730: eb134030csg %r1,%r3,0(%r4)
03ff9e683736: ec1200288064cgrj
%r1,%r2,8,3ff9e683786
03ff9e68373c: c42800082e72lgrl
%r2,3ff9e789420
03ff9e683742: c418000842aflgrl
%r1,3ff9e78bca0
03ff9e683748: a7f4ff09brc 15,3ff9e68355a
[ 249.792602] Last Breaking-Event-Address:
[ 249.792604] [<03ff9e68355e>] 0x3ff9e68355e
[ 249.792605]
[ 249.792606] Kernel panic - not syncing: Fatal exception: panic_on_oops
#===
#=== Steps to Reproduce
#===
1. Use the KVM kernel module with qemu
By applying following upstream patch this bug was not triggered again:
commit f045402984404ddc11016358411e445192919047
Author: David Hildenbrand
Date: Thu Jul 7 10:44:10 2016 +0200
s390/mm: fix gmap tlb flush issues
__tlb_flush_asce() should never be used if multiple asce belong to
a mm.
As this function changes mm logic determining if local or global tlb
flushes will be neded, we might end up flushing only the gmap asce on all
CPUs and a follow up mm asce flushes will only flush on the local CPU,
although that asce ran on multiple CPUs.
The missing tlb flushes will provoke strange faults in user space and even
low address protections in user space, crashing the kernel.
Fixes: 1b948d6caec4 ("s390/mm,tlb: optimize TLB flushing for zEC12")
Cc: sta...@vger.kernel.org # 3.15+
Reported-by: Sascha Silbe
Acked-by: Martin Schwidefsky
Signed-off-by: David Hildenbrand
Signed-off-by: Martin Schwidefsky
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634034/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1448942] Re: Juniper Network Connect Tun
Issues seems to reproduce again after update to 16.10. Kernel 4.8.0-22-generic. Downgrading to 4.4.0-43 helped. If some additional info is required, pls tell me how to get it. -- 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/1448942 Title: Juniper Network Connect Tun Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Released Bug description: Hi, i'm using Juniper Network Connect. With kernel Version "3.19.0-15-generic" it stops working. I the logfile of Network connect i saw: "IP Packet too small 0" I found a solution which also has implemented in Fedora: http://www.unixgr.com/juniper-ncsvc-and-linux-3-19/ and fix: https://bugzilla.kernel.org/show_bug.cgi?id=90901 --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mschroen 2784 F pulseaudio /dev/snd/controlC1: mschroen 2784 F pulseaudio /dev/snd/controlC0: mschroen 2784 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=cd8793fc-8985-4125-99f8-aff20e7ef69f InstallationDate: Installed on 2013-10-07 (566 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: LENOVO 20AY001DGE NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic root=/dev/mapper/vgubuntu-root ro quiet splash kopt=root=/dev/mapper/vgubuntu-root vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 Tags: vivid Uname: Linux 3.19.0-15-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-04-24 (3 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 07/23/2013 dmi.bios.vendor: LENOVO dmi.bios.version: J3ET32WW (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AY001DGE dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ3ET32WW(1.09):bd07/23/2013:svnLENOVO:pn20AY001DGE:pvrThinkPadS3-S440:rvnLENOVO:rn20AY001DGE:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AY001DGE dmi.product.version: ThinkPad S3-S440 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1448942/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634050] [NEW] Please enable CONFIG_VFIO_NOIOMMU
Public bug reported: Hi, for certain cases a user might want to use VFIO in NO IOMMU mode. This only enables it to be an option, it doesn't change things unless "enable_unsafe_noiommu_mode" is set. See this reference: https://patchwork.kernel.org/patch/7906971/ for more details. This is used for some setups of DPDK see this http://dpdk- guide.gitlab.io/dpdk-guide/setup/binding.html#vfio-no-iommu Usually the reason to pick vfio over uio is the isolation. But there are some cases where vfio is required for extra features but can't work unless NO-IOMMU mode is used. I watched the topic a while checking if there is some major "oh crap what have we done" but there was none. An since by only enabling it in the kernel it shouldn't change a lot I wanted to ask if you could enable this config in the kernel for Z*. Technically it would be nice to get it in Yakkety as well, but I think we should be fine only working forward and enabling it in the Z release. ** Affects: dpdk (Ubuntu) Importance: Medium Status: Incomplete ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Also affects: dpdk (Ubuntu) Importance: Undecided Status: New ** Changed in: dpdk (Ubuntu) Status: New => Triaged ** Changed in: dpdk (Ubuntu) Status: Triaged => Incomplete ** Changed in: dpdk (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/1634050 Title: Please enable CONFIG_VFIO_NOIOMMU Status in dpdk package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hi, for certain cases a user might want to use VFIO in NO IOMMU mode. This only enables it to be an option, it doesn't change things unless "enable_unsafe_noiommu_mode" is set. See this reference: https://patchwork.kernel.org/patch/7906971/ for more details. This is used for some setups of DPDK see this http://dpdk- guide.gitlab.io/dpdk-guide/setup/binding.html#vfio-no-iommu Usually the reason to pick vfio over uio is the isolation. But there are some cases where vfio is required for extra features but can't work unless NO-IOMMU mode is used. I watched the topic a while checking if there is some major "oh crap what have we done" but there was none. An since by only enabling it in the kernel it shouldn't change a lot I wanted to ask if you could enable this config in the kernel for Z*. Technically it would be nice to get it in Yakkety as well, but I think we should be fine only working forward and enabling it in the Z release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1634050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634050] Re: Please enable CONFIG_VFIO_NOIOMMU
Checks with DPDK waiting until a matching Kernel is available - incomplete until then. -- 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/1634050 Title: Please enable CONFIG_VFIO_NOIOMMU Status in dpdk package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hi, for certain cases a user might want to use VFIO in NO IOMMU mode. This only enables it to be an option, it doesn't change things unless "enable_unsafe_noiommu_mode" is set. See this reference: https://patchwork.kernel.org/patch/7906971/ for more details. This is used for some setups of DPDK see this http://dpdk- guide.gitlab.io/dpdk-guide/setup/binding.html#vfio-no-iommu Usually the reason to pick vfio over uio is the isolation. But there are some cases where vfio is required for extra features but can't work unless NO-IOMMU mode is used. I watched the topic a while checking if there is some major "oh crap what have we done" but there was none. An since by only enabling it in the kernel it shouldn't change a lot I wanted to ask if you could enable this config in the kernel for Z*. Technically it would be nice to get it in Yakkety as well, but I think we should be fine only working forward and enabling it in the Z release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1634050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] onza (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-25.27/onza__4.8.0-25.27__2016-10-17_08-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. https://bugs.launchpad.net/bugs/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] s2lp6g002 (s390x.zKVM) - tests ran: 10, failed: 2
tests ran: 10, failed: 2; http://kernel.ubuntu.com/testing/4.8.0-21.23/s2lp6g002__4.8.0-21.23__2016-10-17_08-25-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] kernel02 (s390x.zVM) - tests ran: 10, failed: 2
tests ran: 10, failed: 2; http://kernel.ubuntu.com/testing/4.8.0-21.23/kernel02__4.8.0-21.23__2016-10-17_08-25-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] modoc (ppc64el) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-25.27/modoc__4.8.0-25.27__2016-10-17_08-53-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634050] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1634050 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 comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1634050 Title: Please enable CONFIG_VFIO_NOIOMMU Status in dpdk package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hi, for certain cases a user might want to use VFIO in NO IOMMU mode. This only enables it to be an option, it doesn't change things unless "enable_unsafe_noiommu_mode" is set. See this reference: https://patchwork.kernel.org/patch/7906971/ for more details. This is used for some setups of DPDK see this http://dpdk- guide.gitlab.io/dpdk-guide/setup/binding.html#vfio-no-iommu Usually the reason to pick vfio over uio is the isolation. But there are some cases where vfio is required for extra features but can't work unless NO-IOMMU mode is used. I watched the topic a while checking if there is some major "oh crap what have we done" but there was none. An since by only enabling it in the kernel it shouldn't change a lot I wanted to ask if you could enable this config in the kernel for Z*. Technically it would be nice to get it in Yakkety as well, but I think we should be fine only working forward and enabling it in the Z release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1634050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] Re: linux: 4.8.0-25.27 -proposed tracker
** Changed in: kernel-development-workflow/regression-testing Status: Confirmed => 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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1448942] Re: Juniper Network Connect Tun
There's "Bad ip packet len" warning that I can see in pulsesvc logs that started to show up after upgrade: 20161017100453.916474 pulsesvc[p11643.t11643] session.info Tunnel setup done (session.cpp:574) 20161017100453.916580 pulsesvc[p11643.t11643] ipsec.info Creating UDP socket 10.1.1.64:0 (udp.cpp:45) 20161017100453.916598 pulsesvc[p11643.t11643] ipsec.info setting IP_PMTU_DISCOVER (0) (udp.cpp:242) 20161017100453.916616 pulsesvc[p11643.t11643] ipsec.info new ESP tunnel in:0x9BD4E0FD, out:0x993872A5 10.1.1.64:0 -> *.*.*.*:4500 (engine.cpp:481) 20161017100453.916626 pulsesvc[p11643.t11643] ipsec.info send kmp message 302 size 86 (tunnel.cpp:235) 20161017100453.916642 pulsesvc[p11643.t11643] ipsec.info IpsecEngine::setTunAdapter (nil) (engine.cpp:104) 20161017100453.916713 pulsesvc[p11643.t11643] pulsesvc.info received onConnect (pulsesvc.cpp:702) 20161017100453.916831 pulsesvc[p11643.t11643] adapter.warn Bad ip packet len 48 - should be 0 (adapter.cpp:184) -- 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/1448942 Title: Juniper Network Connect Tun Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Released Bug description: Hi, i'm using Juniper Network Connect. With kernel Version "3.19.0-15-generic" it stops working. I the logfile of Network connect i saw: "IP Packet too small 0" I found a solution which also has implemented in Fedora: http://www.unixgr.com/juniper-ncsvc-and-linux-3-19/ and fix: https://bugzilla.kernel.org/show_bug.cgi?id=90901 --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mschroen 2784 F pulseaudio /dev/snd/controlC1: mschroen 2784 F pulseaudio /dev/snd/controlC0: mschroen 2784 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=cd8793fc-8985-4125-99f8-aff20e7ef69f InstallationDate: Installed on 2013-10-07 (566 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: LENOVO 20AY001DGE NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic root=/dev/mapper/vgubuntu-root ro quiet splash kopt=root=/dev/mapper/vgubuntu-root vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 Tags: vivid Uname: Linux 3.19.0-15-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-04-24 (3 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 07/23/2013 dmi.bios.vendor: LENOVO dmi.bios.version: J3ET32WW (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AY001DGE dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ3ET32WW(1.09):bd07/23/2013:svnLENOVO:pn20AY001DGE:pvrThinkPadS3-S440:rvnLENOVO:rn20AY001DGE:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AY001DGE dmi.product.version: ThinkPad S3-S440 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1448942/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634050] Re: Please enable CONFIG_VFIO_NOIOMMU
No apport collect needed to discuss/enable this. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided => Wishlist -- 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/1634050 Title: Please enable CONFIG_VFIO_NOIOMMU Status in dpdk package in Ubuntu: Incomplete Status in linux package in Ubuntu: Confirmed Bug description: Hi, for certain cases a user might want to use VFIO in NO IOMMU mode. This only enables it to be an option, it doesn't change things unless "enable_unsafe_noiommu_mode" is set. See this reference: https://patchwork.kernel.org/patch/7906971/ for more details. This is used for some setups of DPDK see this http://dpdk- guide.gitlab.io/dpdk-guide/setup/binding.html#vfio-no-iommu Usually the reason to pick vfio over uio is the isolation. But there are some cases where vfio is required for extra features but can't work unless NO-IOMMU mode is used. I watched the topic a while checking if there is some major "oh crap what have we done" but there was none. An since by only enabling it in the kernel it shouldn't change a lot I wanted to ask if you could enable this config in the kernel for Z*. Technically it would be nice to get it in Yakkety as well, but I think we should be fine only working forward and enabling it in the Z release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1634050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] s2lp6g002 (s390x.zKVM) - tests ran: 19, failed: 8
tests ran: 19, failed: 8; http://kernel.ubuntu.com/testing/4.8.0-22.24/s2lp6g002__4.8.0-22.24__2016-10-17_09-19-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634034] Re: kvm default ubuntu kernel: Kernel panic - not syncing: Fatal exception: panic_on_oops
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Importance: Undecided => High
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
--
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/1634034
Title:
kvm default ubuntu kernel: Kernel panic - not syncing: Fatal
exception: panic_on_oops
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
New
Bug description:
During guest/isolated container execution following kernel bug got
triggered:
[ 249.792522] Modules linked in: bridge stp llc binfmt_misc qeth_l2 chsc_sch
eadm_sch tape_3590 tape tape_class qeth ccwgroup dm_round_robin ib_iser rdma_cm
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi
scsi_transport_iscsi dm_multipath btrfs zlib_deflate raid10 raid456
async_memcpy async_raid6_recov async_pq async_xor async_tx xor raid6_pq
libcrc32c raid1 linear raid0 ghash_s390 prng aes_s390 des_s390 des_generic
sha512_s390 sha256_s390 sha1_s390 sha_common dasd_eckd_mod dasd_mod zfcp qdio
scsi_transport_fc
[ 249.792558] CPU: 1 PID: 2461 Comm: qemu-system-s39 Not tainted
4.4.0-42-generic #62-Ubuntu
[ 249.792560] task: edf44c90 ti: 7be68000 task.ti:
7be68000
[ 249.792562] User PSW : 070520018000 03ff9e683730
[ 249.792564]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0
EA:3
User GPRS: f000 0001 0001
0002
[ 249.792566]03ff9e789420 0948
03ffc7c7d480
[ 249.792568] 0948
fc00
[ 249.792569]03ff9e789000 03ff9e6845e6
03ff7f5297b0
[ 249.792577] User Code: 03ff9e683720: ec32000100d9aghik %r3,%r2,1
03ff9e683726: b9040012lgr %r1,%r2
#03ff9e68372a: c0482e7blarl
%r4,3ff9e789420
>03ff9e683730: eb134030csg %r1,%r3,0(%r4)
03ff9e683736: ec1200288064cgrj
%r1,%r2,8,3ff9e683786
03ff9e68373c: c42800082e72lgrl
%r2,3ff9e789420
03ff9e683742: c418000842aflgrl
%r1,3ff9e78bca0
03ff9e683748: a7f4ff09brc 15,3ff9e68355a
[ 249.792602] Last Breaking-Event-Address:
[ 249.792604] [<03ff9e68355e>] 0x3ff9e68355e
[ 249.792605]
[ 249.792606] Kernel panic - not syncing: Fatal exception: panic_on_oops
#===
#=== Steps to Reproduce
#===
1. Use the KVM kernel module with qemu
By applying following upstream patch this bug was not triggered again:
commit f045402984404ddc11016358411e445192919047
Author: David Hildenbrand
Date: Thu Jul 7 10:44:10 2016 +0200
s390/mm: fix gmap tlb flush issues
__tlb_flush_asce() should never be used if multiple asce belong to
a mm.
As this function changes mm logic determining if local or global tlb
flushes will be neded, we might end up flushing only the gmap asce on all
CPUs and a follow up mm asce flushes will only flush on the local CPU,
although that asce ran on multiple CPUs.
The missing tlb flushes will provoke strange faults in user space and even
low address protections in user space, crashing the kernel.
Fixes: 1b948d6caec4 ("s390/mm,tlb: optimize TLB flushing for zEC12")
Cc: sta...@vger.kernel.org # 3.15+
Reported-by: Sascha Silbe
Acked-by: Martin Schwidefsky
Signed-off-by: David Hildenbrand
Signed-off-by: Martin Schwidefsky
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1634034/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] dwalin (amd64) - tests ran: 5, failed: 3
tests ran: 5, failed: 3; http://kernel.ubuntu.com/testing/4.8.0-25.27/dwalin__4.8.0-25.27__2016-10-17_08-42-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] s2lp6g002 (s390x.zKVM) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-25.27/s2lp6g002__4.8.0-25.27__2016-10-17_10-04-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] s2lp4 (s390x.LPAR) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-25.27/s2lp4__4.8.0-25.27__2016-10-17_10-20-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] kernel02 (s390x.zVM) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-25.27/kernel02__4.8.0-25.27__2016-10-17_10-24-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] s2lp6g002 (s390x.zKVM) - tests ran: 10, failed: 2
tests ran: 10, failed: 2; http://kernel.ubuntu.com/testing/4.8.0-25.27/s2lp6g002__4.8.0-25.27__2016-10-17_10-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. https://bugs.launchpad.net/bugs/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] modoc (ppc64el) - tests ran: 10, failed: 1
tests ran: 10, failed: 1; http://kernel.ubuntu.com/testing/4.8.0-25.27/modoc__4.8.0-25.27__2016-10-17_10-01-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] s2lp4 (s390x.LPAR) - tests ran: 10, failed: 2
tests ran: 10, failed: 2; http://kernel.ubuntu.com/testing/4.8.0-25.27/s2lp4__4.8.0-25.27__2016-10-17_10-22-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] kernel02 (s390x.zVM) - tests ran: 10, failed: 2
tests ran: 10, failed: 2; http://kernel.ubuntu.com/testing/4.8.0-25.27/kernel02__4.8.0-25.27__2016-10-17_10-26-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1633058] Re: ghash-clmulni-intel module fails to load
** Changed in: linux (Ubuntu)
Status: Triaged => 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/1633058
Title:
ghash-clmulni-intel module fails to load
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Trusty:
Triaged
Status in linux source package in Xenial:
Triaged
Bug description:
The module ghash-clmulni-intel always fails to load with "Invalid
argument":
$ sudo modprobe ghash-clmulni-intel
modprobe: ERROR: could not insert 'ghash_clmulni_intel': Invalid argument
That was caused by the commit 8996eafdc ("crypto: ahash - ensure
statesize is non-zero"), that added a requirement that all ahash
algorithms now need to implement import() and export() and define a
non zero statesize.
The fix is composed by two commits:
3a020a7 crypto: ghash-clmulni - Fix load failure
1a07834 crypto: cryptd - Assign statesize properly
Xenial and Trusty are affected and Yakkety already included the
solution above.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633058/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632252] Re: linux autopkgtest kills sshd in testbed
I am able to reproduce this locally by using the "ssh" runner on a manually started QEMU instance, instead of the "qemu" runner directly; so this is much easier to investigate. First this needs a small new feature in autopkgtest's ssh runner: https://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=9aa6fdbef . Easiest to just run autopkgtest from git (see reproducer below). * Take a standard autopkgtest yakkety image (autopkgtest-buildvm- ubuntu-cloud) and run it in QEMU: qemu-system-x86_64 -enable-kvm -m 4096 -smp 2 -nographic -drive file=path/to/autopkgtest-yakkety-amd64.img,if=virtio -net nic,model=virtio -net user,hostfwd=tcp::22000-:22 * Log in (ubuntu/ubuntu) and scp/install your host's ssh key info ~/.ssh/authorized_keys * Run the test: git clone https://anonscm.debian.org/git/autopkgtest/autopkgtest.git autopkgtest/runner/autopkgtest --testname ubuntu-regression-suite linux -- ssh -H localhost -l ubuntu -p 22000 --reboot --capability=isolation-machine --capability=revert --capability=revert-full-system This takes an hour or so, then the test fails with "testbed failure: testbed auxverb failed with exit code 255" and the console (in qemu) is completely dead. So notably this fails later than on the production infra (where it OOM-kills sshd during AppArmor tests), here it fails right after 12:39:40 DEBUG| [stdout] selftests: breakpoint_test [PASS] but this could be variance due to the infra instances having more CPUs and memory, or it's just an artifact of truncating the log earlier. -- 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/1632252 Title: linux autopkgtest kills sshd in testbed Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: The current linux autopkgtests in yakkety are caught in an eternal "temporary failure" retry loop. They stopped timing out, but in the middle of the tests they kill sshd. Tail of test output: 09:01:00 DEBUG| [stdout] preparing apparmor_2.10.95-4ubuntu5.dsc... done 09:01:00 DEBUG| [stdout] 09:01:40 ERROR| [stderr] Run libapparmor testsuite (with python3) ... ok 09:01:40 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites) 09:01:48 DEBUG| [stdout] preparing apparmor_2.10.95-4ubuntu5.dsc... done 09:01:48 DEBUG| [stdout] 09:19:27 ERROR| [stderr] Run parser regression tests ... ok 09:19:27 ERROR| [stderr] test_regression_testsuite (__main__.ApparmorTestsuites) 09:19:33 DEBUG| [stdout] preparing apparmor_2.10.95-4ubuntu5.dsc... done 09:19:33 DEBUG| [stdout] Killed Killed Connection to 10.220.42.236 closed by remote host. Exit request sent. autopkgtest [09:24:42]: ERROR: testbed failure: testbed auxverb failed with exit code 255 Console output during the test: Ubuntu 16.10 autopkgtest ttyS0 autopkgtest login: [ 3512.996305] AppArmor: change_hat: Invalid input '^open' [ 3513.000678] AppArmor: change_hat: Invalid input '^'[ 3513.013965] AppArmor: change_hat: Invalid input, NULL hat and NULL magic [ 3513.019831] AppArmor: change_hat: Invalid input, NULL hat and NULL magic [ 3513.024872] AppArmor: change_hat: Invalid input '^open'AppArmor: change_hat: Invalid input '^' [ 3513.026539] AppArmor: change_hat: Invalid input '^'[ 3638.281408] Out of memory: Kill process 587 (rsyslogd) score 8 or sacrifice child [ 3638.284907] Killed process 587 (rsyslogd) total-vm:107460kB, anon-rss:67892kB, file-rss:2548kB, shmem-rss:0kB [ 3638.306990] Out of memory: Kill process 300 (systemd-journal) score 2 or sacrifice child [ 3638.308985] Killed process 300 (systemd-journal) total-vm:46184kB, anon-rss:460kB, file-rss:3752kB, shmem-rss:15412kB [ 3638.319337] Out of memory: Kill process 2636 (autotest-local) score 1 or sacrifice child [ 3638.320394] Killed process 10325 (autotest-local) total-vm:18092kB, anon-rss:7296kB, file-rss:3544kB, shmem-rss:0kB [ 3638.345419] Out of memory: Kill process 2636 (autotest-local) score 1 or sacrifice child [ 3638.347095] Killed process 2638 (autotest-local) total-vm:17836kB, anon-rss:7160kB, file-rss:1752kB, shmem-rss:0kB [ 3638.368917] Out of memory: Kill process 2636 (autotest-local) score 1 or sacrifice child [ 3638.369954] Killed process 2637 (autotest-local) total-vm:17836kB, anon-rss:7160kB, file-rss:1684kB, shmem-rss:0kB [ 3638.479196] Out of memory: Kill process 2636 (autotest-local) score 1 or sacrifice child [ 3638.482968] Killed process 2636 (autotest-local) total-vm:17836kB, anon-rss:7248kB, file-rss:5864kB, shmem-rss:0kB [ 3638.501050] Out of memory: Kill process 10619 (python) score 1 or sacrifice child [ 3638.502022] Killed process 14752 (make) total-vm:6052kB, anon-rss:196kB, file-rss:2032kB, shmem-rss:0kB [ 3638.511243] Out of memory: Kill process 10619 (python) score 1 or sacrifice child [ 3638.512224] Ki
[Kernel-packages] [Bug 1632252] Re: linux autopkgtest kills sshd in testbed
After the hang, even SysRq doesn't work (I tried "sync" with Ctrl+A b s -- Ctrl+A b is the QEMU console key combo for sending SysRq, see Ctrl-A ?) -- 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/1632252 Title: linux autopkgtest kills sshd in testbed Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: The current linux autopkgtests in yakkety are caught in an eternal "temporary failure" retry loop. They stopped timing out, but in the middle of the tests they kill sshd. Tail of test output: 09:01:00 DEBUG| [stdout] preparing apparmor_2.10.95-4ubuntu5.dsc... done 09:01:00 DEBUG| [stdout] 09:01:40 ERROR| [stderr] Run libapparmor testsuite (with python3) ... ok 09:01:40 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites) 09:01:48 DEBUG| [stdout] preparing apparmor_2.10.95-4ubuntu5.dsc... done 09:01:48 DEBUG| [stdout] 09:19:27 ERROR| [stderr] Run parser regression tests ... ok 09:19:27 ERROR| [stderr] test_regression_testsuite (__main__.ApparmorTestsuites) 09:19:33 DEBUG| [stdout] preparing apparmor_2.10.95-4ubuntu5.dsc... done 09:19:33 DEBUG| [stdout] Killed Killed Connection to 10.220.42.236 closed by remote host. Exit request sent. autopkgtest [09:24:42]: ERROR: testbed failure: testbed auxverb failed with exit code 255 Console output during the test: Ubuntu 16.10 autopkgtest ttyS0 autopkgtest login: [ 3512.996305] AppArmor: change_hat: Invalid input '^open' [ 3513.000678] AppArmor: change_hat: Invalid input '^'[ 3513.013965] AppArmor: change_hat: Invalid input, NULL hat and NULL magic [ 3513.019831] AppArmor: change_hat: Invalid input, NULL hat and NULL magic [ 3513.024872] AppArmor: change_hat: Invalid input '^open'AppArmor: change_hat: Invalid input '^' [ 3513.026539] AppArmor: change_hat: Invalid input '^'[ 3638.281408] Out of memory: Kill process 587 (rsyslogd) score 8 or sacrifice child [ 3638.284907] Killed process 587 (rsyslogd) total-vm:107460kB, anon-rss:67892kB, file-rss:2548kB, shmem-rss:0kB [ 3638.306990] Out of memory: Kill process 300 (systemd-journal) score 2 or sacrifice child [ 3638.308985] Killed process 300 (systemd-journal) total-vm:46184kB, anon-rss:460kB, file-rss:3752kB, shmem-rss:15412kB [ 3638.319337] Out of memory: Kill process 2636 (autotest-local) score 1 or sacrifice child [ 3638.320394] Killed process 10325 (autotest-local) total-vm:18092kB, anon-rss:7296kB, file-rss:3544kB, shmem-rss:0kB [ 3638.345419] Out of memory: Kill process 2636 (autotest-local) score 1 or sacrifice child [ 3638.347095] Killed process 2638 (autotest-local) total-vm:17836kB, anon-rss:7160kB, file-rss:1752kB, shmem-rss:0kB [ 3638.368917] Out of memory: Kill process 2636 (autotest-local) score 1 or sacrifice child [ 3638.369954] Killed process 2637 (autotest-local) total-vm:17836kB, anon-rss:7160kB, file-rss:1684kB, shmem-rss:0kB [ 3638.479196] Out of memory: Kill process 2636 (autotest-local) score 1 or sacrifice child [ 3638.482968] Killed process 2636 (autotest-local) total-vm:17836kB, anon-rss:7248kB, file-rss:5864kB, shmem-rss:0kB [ 3638.501050] Out of memory: Kill process 10619 (python) score 1 or sacrifice child [ 3638.502022] Killed process 14752 (make) total-vm:6052kB, anon-rss:196kB, file-rss:2032kB, shmem-rss:0kB [ 3638.511243] Out of memory: Kill process 10619 (python) score 1 or sacrifice child [ 3638.512224] Killed process 10619 (python) total-vm:16752kB, anon-rss:5836kB, file-rss:6148kB, shmem-rss:0kB [ 3638.525104] Out of memory: Kill process 3382 (python) score 0 or sacrifice child [ 3638.526060] Killed process 3382 (python) total-vm:21296kB, anon-rss:3732kB, file-rss:4080kB, shmem-rss:0kB [ 3638.545114] Out of memory: Kill process 553 (haveged) score 0 or sacrifice child [ 3638.546068] Killed process 553 (haveged) total-vm:8028kB, anon-rss:4780kB, file-rss:1468kB, shmem-rss:0kB [ 3638.573449] Out of memory: Kill process 10373 (sshd) score 0 or sacrifice child [ 3638.574353] Killed process 11430 (sshd) total-vm:1kB, anon-rss:1712kB, file-rss:2960kB, shmem-rss:0kB [ 3638.591696] Out of memory: Kill process 10373 (sshd) score 0 or sacrifice child [ 3638.595493] Killed process 10373 (sshd) total-vm:13460kB, anon-rss:752kB, file-rss:5476kB, shmem-rss:4kB [ 3638.605938] Out of memory: Kill process 898 (sshd) score 0 or sacrifice child [ 3638.607617] Killed process 911 (sshd) total-vm:13804kB, anon-rss:1120kB, file-rss:3184kB, shmem-rss:0kB [ 3638.626950] Out of memory: Kill process 898 (sshd) score 0 or sacrifice child [ 3638.627839] Killed process 898 (sshd) total-vm:13460kB, anon-rss:744kB, file-rss:5436kB, shmem-rss:4kB [ 3638.641735] Out of memory: Kill process 900 (systemd) score 0 or sacrifice child [ 3638.643448] Killed process 901 ((sd-p
[Kernel-packages] [Bug 1632918] onibi (amd64) - tests ran: 5, failed: 3
tests ran: 5, failed: 3; http://kernel.ubuntu.com/testing/4.8.0-25.27/onibi__4.8.0-25.27__2016-10-17_08-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. https://bugs.launchpad.net/bugs/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] kernel02 (s390x.zVM) - tests ran: 4, failed: 3
tests ran: 4, failed: 3; http://kernel.ubuntu.com/testing/4.8.0-25.27/kernel02__4.8.0-25.27__2016-10-17_11-04-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] kernel02 (s390x.zVM) - tests ran: 19, failed: 7
tests ran: 19, failed: 7; http://kernel.ubuntu.com/testing/4.8.0-25.27/kernel02__4.8.0-25.27__2016-10-17_11-19-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1612124] External Specs for Test Case definition
--- Comment (attachment only) From heinz-werner_se...@de.ibm.com 2016-08-26 08:29 EDT--- ** Attachment added: "External Specs for Test Case definition" https://bugs.launchpad.net/bugs/1612124/+attachment/4762439/+files/KRN1521_v2-external.pdf -- 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/1612124 Title: [16.10 FEAT] PCI error reporting interface Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Kernel 4.7 enhancement that extend the "OpenCrypto solution" for user space programs to trigger a 'deconfigure and repair' action for a specific PCI device. Implementation via a new sysfs interface to disable PCI cards based on the CAP_SYS_ADMIN capability. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1612124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1612123] External Specs for Test Case definition
--- Comment (attachment only) From heinz-werner_se...@de.ibm.com 2016-08-26 08:25 EDT--- ** Attachment added: "External Specs for Test Case definition" https://bugs.launchpad.net/bugs/1612123/+attachment/4762440/+files/KRN1405-external.pdf -- 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/1612123 Title: [16.10 FEAT] PCI: Function-Measurement-Block Enhancements for z13 Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Kernel 4.7 : Enhance the PCI function-measurement interface to provide PCI type specific data, e.g. number of packets for the mellanox card and number of work units for the compression card. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1612123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1612121] External Specs for Test Case definition
--- Comment (attachment only) From heinz-werner_se...@de.ibm.com 2016-08-26 08:32 EDT--- ** Attachment added: "External Specs for Test Case definition" https://bugs.launchpad.net/bugs/1612121/+attachment/4762438/+files/LS1501_v8-external.pdf -- 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/1612121 Title: [16.10 FEAT] dasdfmt quick format Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: kernel 4.7 : Implement a quick format mode in dasdfmt. In this mode, only the first 2 tracks are formatted and filled with contents, resulting in reduced DASD volume initialization time in cases where a regular track format on the remaining tracks can be assumed. This mode is intended as preparation for a future DS8k feature that will allow customers to define a DASD volume with a pre-formatted track layout. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1612121/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1612122] External Specs for Test Case definition
--- Comment (attachment only) From heinz-werner_se...@de.ibm.com 2016-08-26 08:31 EDT--- ** Attachment added: "External Specs for Test Case definition" https://bugs.launchpad.net/bugs/1612122/+attachment/4762441/+files/LS1213-external.pdf -- 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/1612122 Title: [16.10 FEAT] Query Host Access to Volume support Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: kernel 4.7 : Provide an interface to query if a DASD volume is being used (set online) by another operating system instance. Exploit this interface in z/OS zdsfs and Linux dasdfmt to warn the user/abort processing if the DASD is online to another system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1612122/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] modoc (ppc64el) - tests ran: 2, failed: 1
tests ran: 2, failed: 1; http://kernel.ubuntu.com/testing/4.8.0-25.27/modoc__4.8.0-25.27__2016-10-17_11-17-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] onza (amd64) - tests ran: 5, failed: 3
tests ran: 5, failed: 3; http://kernel.ubuntu.com/testing/4.8.0-25.27/onza__4.8.0-25.27__2016-10-17_09-31-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634108] [NEW] intel_iommu=on causes iwlwifi to fail
Public bug reported: Enabling IOMMU (intel_iommu=on) parameter, I lose my WIFI card: [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/ubuntu--vg-root ro radeon.dpm=1 intel_iommu=on [0.00] Kernel command line: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/ubuntu--vg-root ro radeon.dpm=1 intel_iommu=on [ 14.493516] iommu: Adding device :00:00.0 to group 0 [ 14.493530] iommu: Adding device :00:01.0 to group 1 [ 14.493539] iommu: Adding device :00:14.0 to group 2 [ 14.493552] iommu: Adding device :00:16.0 to group 3 [ 14.493561] iommu: Adding device :00:16.3 to group 3 [ 14.493571] iommu: Adding device :00:19.0 to group 4 [ 14.493579] iommu: Adding device :00:1a.0 to group 5 [ 14.493587] iommu: Adding device :00:1b.0 to group 6 [ 14.493596] iommu: Adding device :00:1c.0 to group 7 [ 14.493605] iommu: Adding device :00:1c.6 to group 8 [ 14.493614] iommu: Adding device :00:1d.0 to group 9 [ 14.493630] iommu: Adding device :00:1f.0 to group 10 [ 14.493638] iommu: Adding device :00:1f.2 to group 10 [ 14.493647] iommu: Adding device :00:1f.3 to group 10 [ 14.493653] iommu: Adding device :01:00.0 to group 1 [ 14.493659] iommu: Adding device :01:00.1 to group 1 [ 14.493667] iommu: Adding device :3b:00.0 to group 11 [ 14.493677] iommu: Adding device :3c:01.0 to group 12 [ 14.493687] iommu: Adding device :3c:02.0 to group 13 [ 14.493695] iommu: Adding device :3c:03.0 to group 14 [ 14.493710] iommu: Adding device :3d:00.0 to group 15 [ 14.493725] iommu: Adding device :5f:00.0 to group 16 [ 24.379876] iwlwifi :3d:00.0: enabling device ( -> 0002) [ 24.394961] iwlwifi :3d:00.0: loaded firmware version 17.352738.0 op_mode iwlmvm [ 24.435195] iwlwifi :3d:00.0: Detected Intel(R) Dual Band Wireless AC 7260, REV=0x144 [ 24.437388] iwlwifi :3d:00.0: L1 Enabled - LTR Enabled [ 24.437841] iwlwifi :3d:00.0: L1 Enabled - LTR Enabled [ 29.454188] iwlwifi :3d:00.0: Failed to load firmware chunk! [ 29.455194] iwlwifi :3d:00.0: Could not load the [0] uCode section [ 29.456109] iwlwifi :3d:00.0: Failed to start INIT ucode: -110 [ 29.462726] iwlwifi :3d:00.0: Failed to run INIT ucode: -110 [ 29.463852] iwlwifi :3d:00.0: L1 Enabled - LTR Enabled ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-22-generic 4.8.0-22.24 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: afiergol 2914 F...m pulseaudio /dev/snd/controlC0: afiergol 2914 F pulseaudio /dev/snd/controlC1: afiergol 2914 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 17 13:48:01 2016 HibernationDevice: RESUME=UUID=7ca97ca1-ca2d-43f6-9b4c-cd61421c0831 InstallationDate: Installed on 2015-04-02 (563 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP ZBook 15 G2 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/ubuntu--vg-root ro radeon.dpm=1 intel_iommu=on RelatedPackageVersions: linux-restricted-modules-4.8.0-22-generic N/A linux-backports-modules-4.8.0-22-generic N/A linux-firmware1.161 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-10-16 (0 days ago) dmi.bios.date: 04/25/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M70 Ver. 01.15 dmi.board.name: 2253 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.12 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM70Ver.01.15:bd04/25/2016:svnHewlett-Packard:pnHPZBook15G2:pvrA3008CD10003:rvnHewlett-Packard:rn2253:rvrKBCVersion03.12:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ZBook 15 G2 dmi.product.version: A3008CD10003 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1634108 Title: intel_iommu=on causes iwlwifi to fail Status in linux package in Ubuntu: New Bug description: Enabling IOMMU (intel_iommu=on) parameter, I lose my WIFI card: [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/ubuntu--vg-root ro radeon.dpm=1 intel_iommu=on [0.00] Kernel command line: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/ubuntu--vg-root ro radeon.dpm=1 intel_iommu=on [
[Kernel-packages] [Bug 1632902] Re: kernel panic when booting 4.4.0-42 and 4.4.0-38, but not 4.4.0-36
"kernel panic when booting 4.4.0-42 and 4.4.0-38, but not 4.4.0-36" I thought the same, but I realised it is somehow "random". Only 1 of 8 attempt to boot is succesfull, no matter what kernel (despite what I thought). It all happened after update of packages few days ago. Before that all kernels worked without problem. Just test it, you'll see I am right. Bug #1633391 -- 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/1632902 Title: kernel panic when booting 4.4.0-42 and 4.4.0-38, but not 4.4.0-36 Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: This occurred after rebooting after running Kubuntu's Update Manager 5.6.2 on 2016-10-12. Unfortunately, I hadn't rebooted after the last update that required me to do so, and thus I don't know if the problem was from that update or this one. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-36-generic 4.4.0-36.55 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jacob 1494 F pulseaudio /dev/snd/controlC0: jacob 1494 F pulseaudio CurrentDesktop: KDE Date: Wed Oct 12 19:54:03 2016 HibernationDevice: RESUME=UUID=c5fdca37-edfe-4f31-928b-970bd6696164 InstallationDate: Installed on 2016-05-25 (140 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=c70ba36b-21e9-48ae-bf12-79060d17dcfc ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157.4 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-DS3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/02/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1632902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1633391] Re: Ubuntu doesn't boot anymore {REGRESSION}
The situation is crazy.
I have -43, -42, -38 and -36 kernels.
The bug is not in "quiet splash" option.
All of them can boot only 1 of 8 times, no matter which one, no matter
whether "quiet splash" is present or not.
It is probably not bug in 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/1633391
Title:
Ubuntu doesn't boot anymore {REGRESSION}
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Bug description:
After I upgraded to latest kernel, Ubuntu does not boot without messing with
grub (I had to delete quiet splash options).
Before upgrade it was OK.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-42-generic 4.4.0-42.62
ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
Uname: Linux 4.4.0-42-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: tomas 2090 F pulseaudio
/dev/snd/controlC1: tomas 2090 F pulseaudio
CurrentDesktop: Unity
Date: Fri Oct 14 11:32:56 2016
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=2ff267c2-ec30-4f81-975c-46640f436942
InstallationDate: Installed on 2016-09-13 (30 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: LENOVO 10104
ProcEnviron:
LANGUAGE=cs_CZ
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=cs_CZ.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-42-generic
root=UUID=fd50bb86-da1a-45bb-957b-ea19b330d7ff ro rootflags=subvol=@
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-42-generic N/A
linux-backports-modules-4.4.0-42-generic N/A
linux-firmware1.157.3
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/21/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: ELKT31AUS
dmi.board.name: MAHOBAY
dmi.board.vendor: LENOVO
dmi.board.version: 3193 STD
dmi.chassis.type: 13
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnLENOVO:bvrELKT31AUS:bd03/21/2013:svnLENOVO:pn10104:pvrLenovoC440:rvnLENOVO:rnMAHOBAY:rvr3193STD:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
dmi.product.name: 10104
dmi.product.version: Lenovo C440
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633391/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1612124] Re: [16.10 FEAT] PCI error reporting interface
** Attachment removed: "External Specs for Test Case definition" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1612124/+attachment/4762439/+files/KRN1521_v2-external.pdf -- 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/1612124 Title: [16.10 FEAT] PCI error reporting interface Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Kernel 4.7 enhancement that extend the "OpenCrypto solution" for user space programs to trigger a 'deconfigure and repair' action for a specific PCI device. Implementation via a new sysfs interface to disable PCI cards based on the CAP_SYS_ADMIN capability. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1612124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634108] Status changed to Confirmed
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/1634108 Title: intel_iommu=on causes iwlwifi to fail Status in linux package in Ubuntu: Confirmed Bug description: Enabling IOMMU (intel_iommu=on) parameter, I lose my WIFI card: [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/ubuntu--vg-root ro radeon.dpm=1 intel_iommu=on [0.00] Kernel command line: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/ubuntu--vg-root ro radeon.dpm=1 intel_iommu=on [ 14.493516] iommu: Adding device :00:00.0 to group 0 [ 14.493530] iommu: Adding device :00:01.0 to group 1 [ 14.493539] iommu: Adding device :00:14.0 to group 2 [ 14.493552] iommu: Adding device :00:16.0 to group 3 [ 14.493561] iommu: Adding device :00:16.3 to group 3 [ 14.493571] iommu: Adding device :00:19.0 to group 4 [ 14.493579] iommu: Adding device :00:1a.0 to group 5 [ 14.493587] iommu: Adding device :00:1b.0 to group 6 [ 14.493596] iommu: Adding device :00:1c.0 to group 7 [ 14.493605] iommu: Adding device :00:1c.6 to group 8 [ 14.493614] iommu: Adding device :00:1d.0 to group 9 [ 14.493630] iommu: Adding device :00:1f.0 to group 10 [ 14.493638] iommu: Adding device :00:1f.2 to group 10 [ 14.493647] iommu: Adding device :00:1f.3 to group 10 [ 14.493653] iommu: Adding device :01:00.0 to group 1 [ 14.493659] iommu: Adding device :01:00.1 to group 1 [ 14.493667] iommu: Adding device :3b:00.0 to group 11 [ 14.493677] iommu: Adding device :3c:01.0 to group 12 [ 14.493687] iommu: Adding device :3c:02.0 to group 13 [ 14.493695] iommu: Adding device :3c:03.0 to group 14 [ 14.493710] iommu: Adding device :3d:00.0 to group 15 [ 14.493725] iommu: Adding device :5f:00.0 to group 16 [ 24.379876] iwlwifi :3d:00.0: enabling device ( -> 0002) [ 24.394961] iwlwifi :3d:00.0: loaded firmware version 17.352738.0 op_mode iwlmvm [ 24.435195] iwlwifi :3d:00.0: Detected Intel(R) Dual Band Wireless AC 7260, REV=0x144 [ 24.437388] iwlwifi :3d:00.0: L1 Enabled - LTR Enabled [ 24.437841] iwlwifi :3d:00.0: L1 Enabled - LTR Enabled [ 29.454188] iwlwifi :3d:00.0: Failed to load firmware chunk! [ 29.455194] iwlwifi :3d:00.0: Could not load the [0] uCode section [ 29.456109] iwlwifi :3d:00.0: Failed to start INIT ucode: -110 [ 29.462726] iwlwifi :3d:00.0: Failed to run INIT ucode: -110 [ 29.463852] iwlwifi :3d:00.0: L1 Enabled - LTR Enabled ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-22-generic 4.8.0-22.24 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: afiergol 2914 F...m pulseaudio /dev/snd/controlC0: afiergol 2914 F pulseaudio /dev/snd/controlC1: afiergol 2914 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 17 13:48:01 2016 HibernationDevice: RESUME=UUID=7ca97ca1-ca2d-43f6-9b4c-cd61421c0831 InstallationDate: Installed on 2015-04-02 (563 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP ZBook 15 G2 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/ubuntu--vg-root ro radeon.dpm=1 intel_iommu=on RelatedPackageVersions: linux-restricted-modules-4.8.0-22-generic N/A linux-backports-modules-4.8.0-22-generic N/A linux-firmware1.161 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-10-16 (0 days ago) dmi.bios.date: 04/25/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M70 Ver. 01.15 dmi.board.name: 2253 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.12 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM70Ver.01.15:bd04/25/2016:svnHewlett-Packard:pnHPZBook15G2:pvrA3008CD10003:rvnHewlett-Packard:rn2253:rvrKBCVersion03.12:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ZBook 15 G2 dmi.product.version: A3008CD10003 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.l
[Kernel-packages] [Bug 1632918] kernel02 (s390x.zVM) - tests ran: 136, failed: 27
tests ran: 136, failed: 27; http://kernel.ubuntu.com/testing/4.8.0-25.27/kernel02__4.8.0-25.27__2016-10-17_11-31-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1633679] Re: upgrade to kernel 4.4.0-43 renders system unusable
Hi, just did the standard upgrade. Saw kernel files 4.4.0-43 being downloaded (+ some other files) Restarted on latest kernel uname -a : Linux UX305UA 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12 13:48:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux All works fine So I suppose we can close the case Thx -- 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/1633679 Title: upgrade to kernel 4.4.0-43 renders system unusable Status in linux package in Ubuntu: Confirmed Bug description: Hi, After the update to kernel 4.4.0-43 laptop (asus zenbook UX305UA) became unsuable : - touchpad not working - usb mouse not working - screen resultion not recognized anymore only allowing basic resolution - I did not test sound, etc... since no pointing device was accepted anymore to navigate the gui - Only possible interaction via dash/terminal Problem is solved by switching back to kernel 4.4.0-42 Tell me what you need to diagnose the cause Please give exact commands since I'm not a deep core techy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] kernel02 (s390x.zVM) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-25.27/kernel02__4.8.0-25.27__2016-10-17_12-03-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools (saucy)
Can we please have a libcpupower-dev package compatible to Debian (https://packages.debian.org/sid/libcpupower-dev)? ** No longer affects: linux (Ubuntu Saucy) ** 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/1215411 Title: libcpupower.so is not installed from linux-tools (saucy) Status in linux package in Ubuntu: Triaged Bug description: The patch for bug 1158668 installs cpupower_$(abi_version) command- line tool as well as libcpupower.so.$(abi_version). This isn't particularly suitable for projects that previously used libcpufreq and intend to migrate to libcpupower, because the libcpupower.so symlink is no longer installed. The command-line tools can also have symlinks (e.g. cpupower -> cpupower_$(abi_version)). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] s2lp6g002 (s390x.zKVM) - tests ran: 4, failed: 3
tests ran: 4, failed: 3; http://kernel.ubuntu.com/testing/4.8.0-25.27/s2lp6g002__4.8.0-25.27__2016-10-17_10-38-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632844] dwalin (amd64) - tests ran: 30, failed: 0
tests ran: 30, failed: 0; http://kernel.ubuntu.com/testing/3.13.0-99.146/dwalin__3.13.0-99.146__2016-10-17_11-23-00/results-index.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/1632844 Title: linux: 3.13.0-99.146 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-99.146 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] kernel02 (s390x.zVM) - tests ran: 64, failed: 0
tests ran: 64, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-25.27/kernel02__4.8.0-25.27__2016-10-17_12-05-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] s2lp4 (s390x.LPAR) - tests ran: 4, failed: 3
tests ran: 4, failed: 3; http://kernel.ubuntu.com/testing/4.8.0-25.27/s2lp4__4.8.0-25.27__2016-10-17_11-03-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1633414] Re: linux: 4.4.0-44.64 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-signed Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) ** Description changed: This bug is for tracking the 4.4.0-44.64 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 - kernel-stable-phase:Packaging - kernel-stable-phase-changed:Friday, 14. October 2016 10:31 UTC - -- swm properties -- derivative-trackers-created: true phase: Packaging + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Monday, 17. October 2016 12:31 UTC ** Description changed: This bug is for tracking the 4.4.0-44.64 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 -- swm properties -- derivative-trackers-created: true - phase: Packaging - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Monday, 17. October 2016 12:31 UTC + phase: Uploaded -- 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/1633414 Title: linux: 4.4.0-44.64 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: Confirmed Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-44.64 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 -- swm properties -- derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1633414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632844] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 10, failed: 2
tests ran: 10, failed: 2; http://kernel.ubuntu.com/testing/3.13.0-99.146/ms10-34-mcdivittB0-kernel__3.13.0-99.146__2016-10-17_11-34-00/results-index.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/1632844 Title: linux: 3.13.0-99.146 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-99.146 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] s2lp4 (s390x.LPAR) - tests ran: 19, failed: 7
tests ran: 19, failed: 7; http://kernel.ubuntu.com/testing/4.8.0-25.27/s2lp4__4.8.0-25.27__2016-10-17_12-32-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] s2lp6g002 (s390x.zKVM) - tests ran: 19, failed: 7
tests ran: 19, failed: 7; http://kernel.ubuntu.com/testing/4.8.0-25.27/s2lp6g002__4.8.0-25.27__2016-10-17_12-12-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634129] [NEW] Couldn't emulate instruction 0x7813427c
You have been subscribed to a public bug: Couldn't emulate instruction 0x7813427c --- Cannot boot nested VMs in Xenial or Yakkety w/ kvm accel. It worked until Vivid (in spite of not being possible in x86) TCG mode works fine, but very slow. TCG full emulation is the mode in the x86 world for nested virt. However, in Power, we've been using in OpenStack CI w/ kvm accel (native virtualization) to speed up 2nd level VMs. It worked until Vivid. Is the case that kvm accel isn't possible anymore for nested virt (aligned with x86 KVM) ? So full emulation TCG mode is the only possible mode in newer kernels ? qemu-system-ppc64le -machine pseries,accel=kvm,usb=off -m 1G -enable-kvm -cpu POWER8E -display none -nographic cirros-d161007-ppc64le-disk.img lsmod |grep kvm kvm_pr 96452 1 kvm 152984 4 kvm_pr Nested VM console: OF stdout device is: /vdevice/vty@7100 Preparing to boot Linux version 4.4.0-28-generic (buildd@bos01-ppc64el-018) (gcc version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2.1) ) #47-Ubuntu SMP Fri Jun 24 10:09:20 UTC 2016 (Ubuntu 4.4.0-28.47-generic 4.4.13) Detected machine type: 0101 Max number of cores passed to firmware: 2048 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done command line: BOOT_IMAGE=/boot/vmlinux-4.4.0-28-generic LABEL=cirros-rootfs ro memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0421 alloc_top: 1000 alloc_top_hi : 4000 rmo_top : 1000 ram_top : 4000 found display : /pci@8002000/vga@0, opening... done instantiating rtas at 0x0daf... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x0422 -> 0x04220aa9 Device tree struct 0x0423 -> 0x0424 Quiescing Open Firmware ... Booting Linux via __start() ? /var/log/syslog & /var/log/kern.log Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.186975] kvmppc_handle_exit_pr: emulation at 700 failed (7813427c) Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.187023] Couldn't emulate instruction 0x7813427c (op 30 xop 318) Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.187066] kvmppc_handle_exit_pr: emulation at 700 failed (7813427c) Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.187113] Couldn't emulate instruction 0x7813427c (op 30 xop 318) Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.187156] kvmppc_handle_exit_pr: emulation at 700 failed (7813427c) Host: cpu : POWER8E (raw), altivec supported clock : 3690.00MHz revision: 2.1 (pvr 004b 0201) timebase: 51200 platform: PowerNV model : 8247-22L machine : PowerNV 8247-22L firmware: OPAL v3 Guest: Xenial or Yakkety Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety Nested VM: CirrOS http://download.cirros-cloud.net/daily/20161007/cirros-d161007-ppc64le-disk.img This seems to be related https://patchwork.kernel.org/patch/9121881/ ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Taco Screen team (taco-screen-team) Status: New ** Tags: architecture-ppc64le bugnameltc-147569 severity-critical targetmilestone-inin16041 -- Couldn't emulate instruction 0x7813427c https://bugs.launchpad.net/bugs/1634129 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1423672] Re: ext4_mb_generate_buddy:756: group N, block bitmap and bg descriptor inconsistent: X vs Y
Chenyuchai, yes, https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?h=7dec5603b6b8dc4c3e1c65d318bd2a5a8c62a424 is the fix. It was integrated in the Trusty kernel 3.13.0-87.133 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1423672 Title: ext4_mb_generate_buddy:756: group N, block bitmap and bg descriptor inconsistent: X vs Y Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Released Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux package in Debian: Fix Released Bug description: SRU Justification: Impact: Users of VMs running 3.13/3.16 and ext4 can experience data corruption in the guest. Fix: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?h=7dec5603b6b8dc4c3e1c65d318bd2a5a8c62a424 Testcase: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818502#22 -- I noticed that one of my VM had this "dmesg -T" output: [Tue Feb 17 09:53:27 2015] systemd-udevd[5433]: starting version 204 [Thu Feb 19 06:25:08 2015] EXT4-fs error (device vda1): ext4_mb_generate_buddy:756: group 5, block bitmap and bg descriptor inconsistent: 16446 vs 16445 free clusters [Thu Feb 19 06:25:09 2015] Aborting journal on device vda1-8. [Thu Feb 19 06:25:09 2015] EXT4-fs (vda1): Remounting filesystem read-only [Thu Feb 19 06:25:09 2015] [ cut here ] [Thu Feb 19 06:25:09 2015] WARNING: CPU: 0 PID: 9946 at /build/buildd/linux-3.13.0/fs/ext4/ext4_jbd2.c:259 __ext4_handle_dirty_metadata+0x1a2/0x1c0() [Thu Feb 19 06:25:09 2015] Modules linked in: nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter ip_tables x_tables serio_raw psmouse floppy [Thu Feb 19 06:25:09 2015] CPU: 0 PID: 9946 Comm: logrotate Not tainted 3.13.0-45-generic #74-Ubuntu [Thu Feb 19 06:25:09 2015] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [Thu Feb 19 06:25:09 2015] 0009 880003a11aa0 81720eb6 [Thu Feb 19 06:25:09 2015] 880003a11ad8 810677cd 88c41340 [Thu Feb 19 06:25:09 2015] 88000a58e000 81835280 1302 880003a11ae8 [Thu Feb 19 06:25:09 2015] Call Trace: [Thu Feb 19 06:25:09 2015] [] dump_stack+0x45/0x56 [Thu Feb 19 06:25:09 2015] [] warn_slowpath_common+0x7d/0xa0 [Thu Feb 19 06:25:09 2015] [] warn_slowpath_null+0x1a/0x20 [Thu Feb 19 06:25:09 2015] [] __ext4_handle_dirty_metadata+0x1a2/0x1c0 [Thu Feb 19 06:25:09 2015] [] ? ext4_dirty_inode+0x2a/0x60 [Thu Feb 19 06:25:09 2015] [] ext4_free_blocks+0x646/0xbf0 [Thu Feb 19 06:25:09 2015] [] ? wake_up_bit+0x25/0x30 [Thu Feb 19 06:25:09 2015] [] ext4_ext_rm_leaf+0x505/0x8f0 [Thu Feb 19 06:25:09 2015] [] ? __ext4_ext_check+0x197/0x370 [Thu Feb 19 06:25:09 2015] [] ? ext4_ext_remove_space+0xc0/0x7e0 [Thu Feb 19 06:25:09 2015] [] ext4_ext_remove_space+0x31c/0x7e0 [Thu Feb 19 06:25:09 2015] [] ext4_ext_truncate+0xb0/0xe0 [Thu Feb 19 06:25:09 2015] [] ext4_truncate+0x379/0x3c0 [Thu Feb 19 06:25:09 2015] [] ext4_evict_inode+0x408/0x4d0 [Thu Feb 19 06:25:09 2015] [] evict+0xb0/0x1b0 [Thu Feb 19 06:25:09 2015] [] iput+0xf5/0x180 [Thu Feb 19 06:25:09 2015] [] __dentry_kill+0x1a8/0x200 [Thu Feb 19 06:25:09 2015] [] dput+0xa5/0x180 [Thu Feb 19 06:25:09 2015] [] __fput+0x176/0x260 [Thu Feb 19 06:25:09 2015] [] fput+0xe/0x10 [Thu Feb 19 06:25:09 2015] [] task_work_run+0xa7/0xe0 [Thu Feb 19 06:25:09 2015] [] do_notify_resume+0x97/0xb0 [Thu Feb 19 06:25:09 2015] [] int_signal+0x12/0x17 [Thu Feb 19 06:25:09 2015] ---[ end trace ebff9843d81b5c41 ]--- [Thu Feb 19 06:25:09 2015] BUG: unable to handle kernel NULL pointer dereference at 0028 [Thu Feb 19 06:25:09 2015] IP: [] __ext4_error_inode+0x31/0x160 [Thu Feb 19 06:25:09 2015] PGD 167067 PUD 161067 PMD 0 [Thu Feb 19 06:25:09 2015] Oops: [#1] SMP [Thu Feb 19 06:25:09 2015] Modules linked in: nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter ip_tables x_tables serio_raw psmouse floppy [Thu Feb 19 06:25:09 2015] CPU: 0 PID: 9946 Comm: logrotate Tainted: G W 3.13.0-45-generic #74-Ubuntu [Thu Feb 19 06:25:09 2015] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [Thu Feb 19 06:25:09 2015] task: 880009ac4800 ti: 880003a1 task.ti: 880003a1 [Thu Feb 19 06:25:09 2015] RIP: 0010:[] [] __ext4_error_inode+0x31/0x160 [Thu Feb 19 06:25:09 2015] RSP: :880003a11a5
[Kernel-packages] [Bug 1634129] [NEW] Couldn't emulate instruction 0x7813427c
Public bug reported: Couldn't emulate instruction 0x7813427c --- Cannot boot nested VMs in Xenial or Yakkety w/ kvm accel. It worked until Vivid (in spite of not being possible in x86) TCG mode works fine, but very slow. TCG full emulation is the mode in the x86 world for nested virt. However, in Power, we've been using in OpenStack CI w/ kvm accel (native virtualization) to speed up 2nd level VMs. It worked until Vivid. Is the case that kvm accel isn't possible anymore for nested virt (aligned with x86 KVM) ? So full emulation TCG mode is the only possible mode in newer kernels ? qemu-system-ppc64le -machine pseries,accel=kvm,usb=off -m 1G -enable-kvm -cpu POWER8E -display none -nographic cirros-d161007-ppc64le-disk.img lsmod |grep kvm kvm_pr 96452 1 kvm 152984 4 kvm_pr Nested VM console: OF stdout device is: /vdevice/vty@7100 Preparing to boot Linux version 4.4.0-28-generic (buildd@bos01-ppc64el-018) (gcc version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2.1) ) #47-Ubuntu SMP Fri Jun 24 10:09:20 UTC 2016 (Ubuntu 4.4.0-28.47-generic 4.4.13) Detected machine type: 0101 Max number of cores passed to firmware: 2048 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done command line: BOOT_IMAGE=/boot/vmlinux-4.4.0-28-generic LABEL=cirros-rootfs ro memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0421 alloc_top: 1000 alloc_top_hi : 4000 rmo_top : 1000 ram_top : 4000 found display : /pci@8002000/vga@0, opening... done instantiating rtas at 0x0daf... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x0422 -> 0x04220aa9 Device tree struct 0x0423 -> 0x0424 Quiescing Open Firmware ... Booting Linux via __start() ? /var/log/syslog & /var/log/kern.log Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.186975] kvmppc_handle_exit_pr: emulation at 700 failed (7813427c) Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.187023] Couldn't emulate instruction 0x7813427c (op 30 xop 318) Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.187066] kvmppc_handle_exit_pr: emulation at 700 failed (7813427c) Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.187113] Couldn't emulate instruction 0x7813427c (op 30 xop 318) Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.187156] kvmppc_handle_exit_pr: emulation at 700 failed (7813427c) Host: cpu : POWER8E (raw), altivec supported clock : 3690.00MHz revision: 2.1 (pvr 004b 0201) timebase: 51200 platform: PowerNV model : 8247-22L machine : PowerNV 8247-22L firmware: OPAL v3 Guest: Xenial or Yakkety Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety Nested VM: CirrOS http://download.cirros-cloud.net/daily/20161007/cirros-d161007-ppc64le-disk.img This seems to be related https://patchwork.kernel.org/patch/9121881/ ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Taco Screen team (taco-screen-team) Status: New ** Tags: architecture-ppc64le bugnameltc-147569 severity-critical targetmilestone-inin16041 ** Tags added: architecture-ppc64le bugnameltc-147569 severity-critical targetmilestone-inin16041 ** Changed in: ubuntu Assignee: (unassigned) => Taco Screen team (taco-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1634129 Title: Couldn't emulate instruction 0x7813427c Status in linux package in Ubuntu: New Bug description: Couldn't emulate instruction 0x7813427c --- Cannot boot nested VMs in Xenial or Yakkety w/ kvm accel. It worked until Vivid (in spite of not being possible in x86) TCG mode works fine, but very slow. TCG full emulation is the mode in the x86 world for nested virt. However, in Power, we've been using in OpenStack CI w/ kvm accel (native virtualization) to speed up 2nd level VMs. It worked until Vivid. Is the case that kvm accel isn't possible anymore for nested virt (aligned with x86 KVM) ? So full emulation TCG mode is the only possible mode in newer kernels ? qemu-system-ppc64le -machine pseries,accel=kvm,usb=off -m 1G -enable- kvm -cpu POWER8E -display none -nographic cirros-d161007-ppc64le- disk.img lsmod |grep kvm kvm_pr 96452 1 kvm 152984 4 kvm_pr Nested VM console: OF stdout device is: /vdevice/vty@7100 Preparing to boot Linux version 4.4.0-28-generic (buildd@bos01-ppc64el-018) (gcc version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2.1) ) #
[Kernel-packages] [Bug 1632918] s2lp6g002 (s390x.zKVM) - tests ran: 136, failed: 27
tests ran: 136, failed: 27; http://kernel.ubuntu.com/testing/4.8.0-25.27/s2lp6g002__4.8.0-25.27__2016-10-17_12-37-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] s2lp4 (s390x.LPAR) - tests ran: 136, failed: 27
tests ran: 136, failed: 27; http://kernel.ubuntu.com/testing/4.8.0-25.27/s2lp4__4.8.0-25.27__2016-10-17_12-44-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] s2lp6g002 (s390x.zKVM) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-25.27/s2lp6g002__4.8.0-25.27__2016-10-17_12-58-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] s2lp4 (s390x.LPAR) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-25.27/s2lp4__4.8.0-25.27__2016-10-17_13-04-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1380480] Re: network disabled after suspend - resume
Hans, note that this bug was opened before systemd was used as a system init. A quick skim of this bug's history suggests that it's been polluted beyond use. If you're having trouble, please file a new bug. With luck, it'll be focused on one thing and therefor fixable. 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/1380480 Title: network disabled after suspend - resume Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Background: this started to happen after the upgrade to Utopic Beta 1 3) When I close the laptop's lid and open, the wifi should reconnect 4) Wifi does not reconnect. It says "Wi-Fi networks" - "disconnected" when I left-click on NM icon in notif area. However the context menu (right-click) has items "Enable networking" and "Enable Wi-Fi" both with checkmarks. Workarounds: switch off - on the physical switch on laptop OR two times go and select "Enable networking" in the NM context menu (after first time it removes checkmark and the "Enable Wi-Fi" item - visual feedback of being disabled). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu27 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Oct 11 22:33:06 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-07-21 (447 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) IpRoute: default via 192.168.10.1 dev wlan0 proto static 10.9.9.0/24 dev vboxnet0 proto kernel scope link src 10.9.9.1 192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.239 metric 9 SourcePackage: network-manager UpgradeStatus: Upgraded to utopic on 2014-09-25 (16 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2014-07-19T15:03:44.847279 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1380480/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634132] [NEW] using hugepages/hugepagesz causes kexec'd kernel to OOM
Public bug reported: [Impact] Users of kdump won't be able to dump if their system uses hugepages/hugepagesz on the cmdline. [Test Case] 1) Install crashdump 2) Boot machine with hugepages= or hugepagesz= set to a significant amount of memory 3) Try to crash with 'echo 'c' | sudo tee /proc/sysrq-trigger' [Regression Potential] If users really want to have hugepages/hugepagesz on the kexec'd kernel for kdump they can add this via KDUMP_CMDLINE_APPEND in /etc/default/kdump-tools. This patch should also potentially go upstream. ** Affects: makedumpfile (Ubuntu) Importance: Medium Assignee: Chris J Arges (arges) Status: In Progress ** Changed in: makedumpfile (Ubuntu) Assignee: (unassigned) => Chris J Arges (arges) ** Changed in: makedumpfile (Ubuntu) Importance: Undecided => Medium ** Changed in: makedumpfile (Ubuntu) Status: New => In Progress -- 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/1634132 Title: using hugepages/hugepagesz causes kexec'd kernel to OOM Status in makedumpfile package in Ubuntu: In Progress Bug description: [Impact] Users of kdump won't be able to dump if their system uses hugepages/hugepagesz on the cmdline. [Test Case] 1) Install crashdump 2) Boot machine with hugepages= or hugepagesz= set to a significant amount of memory 3) Try to crash with 'echo 'c' | sudo tee /proc/sysrq-trigger' [Regression Potential] If users really want to have hugepages/hugepagesz on the kexec'd kernel for kdump they can add this via KDUMP_CMDLINE_APPEND in /etc/default/kdump-tools. This patch should also potentially go upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1634132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] s2lp4 (s390x.LPAR) - tests ran: 64, failed: 0
tests ran: 64, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-25.27/s2lp4__4.8.0-25.27__2016-10-17_13-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. https://bugs.launchpad.net/bugs/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] modoc (ppc64el) - tests ran: 19, failed: 6
tests ran: 19, failed: 6; http://kernel.ubuntu.com/testing/4.8.0-25.27/modoc__4.8.0-25.27__2016-10-17_12-44-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] s2lp6g002 (s390x.zKVM) - tests ran: 64, failed: 0
tests ran: 64, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-25.27/s2lp6g002__4.8.0-25.27__2016-10-17_13-01-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM
Grief - mainline only gets built when upstream Linux changes, hence the reason for this stale config which we've since changed in the distro kernel. I've requested a mainline rebuild which should complete presently. -- 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/1627198 Title: 4.8.0 kernels do not complete boot process on VM Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux-raspi2 source package in Yakkety: Fix Released Bug description: On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare Fusion 8.5 system, none of the 4.8.0 kernels complete the boot process. I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety- proposed. Currently I am seeing the last message in my console at boot up as: [ OK ] Started Bluetooth service and then... it just sits there. Through the use of snapshots, restores, and package bisects, I've definitively narrowed it to linux-generic linux-image-generic and linux-headers-generic. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1627198/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634132] Re: using hugepages/hugepagesz causes kexec'd kernel to OOM
** Patch added: "lp1634132-yakkety.debdiff" https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1634132/+attachment/4762494/+files/lp1634132-yakkety.debdiff -- 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/1634132 Title: using hugepages/hugepagesz causes kexec'd kernel to OOM Status in makedumpfile package in Ubuntu: In Progress Bug description: [Impact] Users of kdump won't be able to dump if their system uses hugepages/hugepagesz on the cmdline. [Test Case] 1) Install crashdump 2) Boot machine with hugepages= or hugepagesz= set to a significant amount of memory 3) Try to crash with 'echo 'c' | sudo tee /proc/sysrq-trigger' [Regression Potential] If users really want to have hugepages/hugepagesz on the kexec'd kernel for kdump they can add this via KDUMP_CMDLINE_APPEND in /etc/default/kdump-tools. This patch should also potentially go upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1634132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632844] dwalin (i386) - tests ran: 3, failed: 0
tests ran: 3, failed: 0; http://kernel.ubuntu.com/testing/3.13.0-99.146/dwalin__3.13.0-99.146__2016-10-17_12-36-00/results-index.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/1632844 Title: linux: 3.13.0-99.146 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-99.146 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1402763] Re: Multicast traffic not propating correctly over linux bridge
** Changed in: juju-core Status: Triaged => Won't Fix -- 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/1402763 Title: Multicast traffic not propating correctly over linux bridge Status in juju-core: Won't Fix Status in linux package in Ubuntu: Confirmed Bug description: There's a lot of supposition in the title of this bug but its currently my best guess. In this deployment, I have a number of services running in LXC containers across multiple physical hosts; each service is clustered across three units, all on separate physical hosts, using corosync and pacemaker; when using multicast to support cluster communication, I occasionally see a container drop out of the cluster and use its isolation response (to shutdown all managed services); when using unicast I've not yet see this same problem. LXC containers are bridged to the main physical network using a linux bridge: eth0 <-> juju-br0 <-> vethXXX <-> | vethXXX | All MTU's are standard (1500). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.6-0ubuntu0.1 ProcVersionSignature: User Name 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Mon Dec 15 17:20:08 2014 ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 17 10:16 seq crw-rw 1 root audio 116, 33 Dec 17 10:16 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: Dell Inc. PowerEdge R610 Package: lxc 1.0.6-0ubuntu0.1 PackageArchitecture: amd64 PciMultimedia: ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=5a86874d-8bbd-4e7a-b73e-17c914de390b ro ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=5a86874d-8bbd-4e7a-b73e-17c914de390b ro ProcVersionSignature: User Name 3.13.0-43.72-generic 3.13.11.11 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images trusty uec-images apparmor Uname: Linux 3.13.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy libvirtd netdev plugdev sudo video _MarkForUpload: True defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx dmi.bios.date: 08/18/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 6.0.7 dmi.board.name: 0F0XJ6 dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr6.0.7:bd08/18/2011:svnDellInc.:pnPowerEdgeR610:pvr:rvnDellInc.:rn0F0XJ6:rvrA11:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R610 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1402763/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] onibi (i386) - tests ran: 3, failed: 1
tests ran: 3, failed: 1; http://kernel.ubuntu.com/testing/4.8.0-25.27/onibi__4.8.0-25.27__2016-10-17_11-47-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM
@timg-tpi: Got it! Thanks for the explanation. As I said, I've compiled the kernel on my own, so don't worry :) But looks like a lack of testing before the release -- 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/1627198 Title: 4.8.0 kernels do not complete boot process on VM Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux-raspi2 source package in Yakkety: Fix Released Bug description: On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare Fusion 8.5 system, none of the 4.8.0 kernels complete the boot process. I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety- proposed. Currently I am seeing the last message in my console at boot up as: [ OK ] Started Bluetooth service and then... it just sits there. Through the use of snapshots, restores, and package bisects, I've definitively narrowed it to linux-generic linux-image-generic and linux-headers-generic. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1627198/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632844] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 136, failed: 0
tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/3.13.0-99.146/ms10-34-mcdivittB0-kernel__3.13.0-99.146__2016-10-17_13-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. https://bugs.launchpad.net/bugs/1632844 Title: linux: 3.13.0-99.146 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-99.146 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1632844/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632252] Re: linux autopkgtest kills sshd in testbed
** Changed in: linux (Ubuntu Yakkety) Assignee: (unassigned) => Colin Ian King (colin-king) -- 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/1632252 Title: linux autopkgtest kills sshd in testbed Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: The current linux autopkgtests in yakkety are caught in an eternal "temporary failure" retry loop. They stopped timing out, but in the middle of the tests they kill sshd. Tail of test output: 09:01:00 DEBUG| [stdout] preparing apparmor_2.10.95-4ubuntu5.dsc... done 09:01:00 DEBUG| [stdout] 09:01:40 ERROR| [stderr] Run libapparmor testsuite (with python3) ... ok 09:01:40 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites) 09:01:48 DEBUG| [stdout] preparing apparmor_2.10.95-4ubuntu5.dsc... done 09:01:48 DEBUG| [stdout] 09:19:27 ERROR| [stderr] Run parser regression tests ... ok 09:19:27 ERROR| [stderr] test_regression_testsuite (__main__.ApparmorTestsuites) 09:19:33 DEBUG| [stdout] preparing apparmor_2.10.95-4ubuntu5.dsc... done 09:19:33 DEBUG| [stdout] Killed Killed Connection to 10.220.42.236 closed by remote host. Exit request sent. autopkgtest [09:24:42]: ERROR: testbed failure: testbed auxverb failed with exit code 255 Console output during the test: Ubuntu 16.10 autopkgtest ttyS0 autopkgtest login: [ 3512.996305] AppArmor: change_hat: Invalid input '^open' [ 3513.000678] AppArmor: change_hat: Invalid input '^'[ 3513.013965] AppArmor: change_hat: Invalid input, NULL hat and NULL magic [ 3513.019831] AppArmor: change_hat: Invalid input, NULL hat and NULL magic [ 3513.024872] AppArmor: change_hat: Invalid input '^open'AppArmor: change_hat: Invalid input '^' [ 3513.026539] AppArmor: change_hat: Invalid input '^'[ 3638.281408] Out of memory: Kill process 587 (rsyslogd) score 8 or sacrifice child [ 3638.284907] Killed process 587 (rsyslogd) total-vm:107460kB, anon-rss:67892kB, file-rss:2548kB, shmem-rss:0kB [ 3638.306990] Out of memory: Kill process 300 (systemd-journal) score 2 or sacrifice child [ 3638.308985] Killed process 300 (systemd-journal) total-vm:46184kB, anon-rss:460kB, file-rss:3752kB, shmem-rss:15412kB [ 3638.319337] Out of memory: Kill process 2636 (autotest-local) score 1 or sacrifice child [ 3638.320394] Killed process 10325 (autotest-local) total-vm:18092kB, anon-rss:7296kB, file-rss:3544kB, shmem-rss:0kB [ 3638.345419] Out of memory: Kill process 2636 (autotest-local) score 1 or sacrifice child [ 3638.347095] Killed process 2638 (autotest-local) total-vm:17836kB, anon-rss:7160kB, file-rss:1752kB, shmem-rss:0kB [ 3638.368917] Out of memory: Kill process 2636 (autotest-local) score 1 or sacrifice child [ 3638.369954] Killed process 2637 (autotest-local) total-vm:17836kB, anon-rss:7160kB, file-rss:1684kB, shmem-rss:0kB [ 3638.479196] Out of memory: Kill process 2636 (autotest-local) score 1 or sacrifice child [ 3638.482968] Killed process 2636 (autotest-local) total-vm:17836kB, anon-rss:7248kB, file-rss:5864kB, shmem-rss:0kB [ 3638.501050] Out of memory: Kill process 10619 (python) score 1 or sacrifice child [ 3638.502022] Killed process 14752 (make) total-vm:6052kB, anon-rss:196kB, file-rss:2032kB, shmem-rss:0kB [ 3638.511243] Out of memory: Kill process 10619 (python) score 1 or sacrifice child [ 3638.512224] Killed process 10619 (python) total-vm:16752kB, anon-rss:5836kB, file-rss:6148kB, shmem-rss:0kB [ 3638.525104] Out of memory: Kill process 3382 (python) score 0 or sacrifice child [ 3638.526060] Killed process 3382 (python) total-vm:21296kB, anon-rss:3732kB, file-rss:4080kB, shmem-rss:0kB [ 3638.545114] Out of memory: Kill process 553 (haveged) score 0 or sacrifice child [ 3638.546068] Killed process 553 (haveged) total-vm:8028kB, anon-rss:4780kB, file-rss:1468kB, shmem-rss:0kB [ 3638.573449] Out of memory: Kill process 10373 (sshd) score 0 or sacrifice child [ 3638.574353] Killed process 11430 (sshd) total-vm:1kB, anon-rss:1712kB, file-rss:2960kB, shmem-rss:0kB [ 3638.591696] Out of memory: Kill process 10373 (sshd) score 0 or sacrifice child [ 3638.595493] Killed process 10373 (sshd) total-vm:13460kB, anon-rss:752kB, file-rss:5476kB, shmem-rss:4kB [ 3638.605938] Out of memory: Kill process 898 (sshd) score 0 or sacrifice child [ 3638.607617] Killed process 911 (sshd) total-vm:13804kB, anon-rss:1120kB, file-rss:3184kB, shmem-rss:0kB [ 3638.626950] Out of memory: Kill process 898 (sshd) score 0 or sacrifice child [ 3638.627839] Killed process 898 (sshd) total-vm:13460kB, anon-rss:744kB, file-rss:5436kB, shmem-rss:4kB [ 3638.641735] Out of memory: Kill process 900 (systemd) score 0 or sacrifice child [ 3638.643448] Killed process 901 ((sd-pam)) total-vm:10360kB, anon-rss:1300kB, file-rss:
[Kernel-packages] [Bug 1634153] [NEW] Xenial update to v4.4.25 stable release
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 Linux tree or a minimally backported form of that patch. The v4.4.25 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the v4.4.25 stable release shall be applied: timekeeping: Fix __ktime_get_fast_ns() regression ALSA: ali5451: Fix out-of-bound position reporting ALSA: usb-audio: Extend DragonFly dB scale quirk to cover other variants ALSA: usb-line6: use the same declaration as definition in header for MIDI manufacturer ID mfd: rtsx_usb: Avoid setting ucr->current_sg.status mfd: atmel-hlcdc: Do not sleep in atomic context mfd: 88pm80x: Double shifting bug in suspend/resume mfd: wm8350-i2c: Make sure the i2c regmap functions are compiled KVM: PPC: Book3s PR: Allow access to unprivileged MMCR2 register KVM: MIPS: Drop other CPU ASIDs on guest MMU changes KVM: PPC: BookE: Fix a sanity check x86/boot: Fix kdump, cleanup aborted E820_PRAM max_pfn manipulation x86/irq: Prevent force migration of irqs which are not in the vector domain x86/dumpstack: Fix x86_32 kernel_stack_pointer() previous stack access ARM: dts: mvebu: armada-390: add missing compatibility string and bracket ARM: dts: MSM8064 remove flags from SPMI/MPP IRQs ARM: cpuidle: Fix error return code ima: use file_dentry() tpm: fix a race condition in tpm2_unseal_trusted() tpm_crb: fix crb_req_canceled behavior Linux 4.4.25 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Description changed: + SRU Justification - 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 Linux tree or + a minimally backported form of that patch. The v4.4.25 upstream stable + patch set is now available. It should be included in the Ubuntu + kernel as well. - 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 Linux tree or -a minimally backported form of that patch. The v4.4.25 upstream stable -patch set is now available. It should be included in the Ubuntu -kernel as well. + git://git.kernel.org/ -git://git.kernel.org/ + TEST CASE: TBD - TEST CASE: TBD + The following patches from the v4.4.25 stable release shall be + applied: -The following patches from the v4.4.25 stable release shall be - applied: + timekeeping: Fix __ktime_get_fast_ns() regression + ALSA: ali5451: Fix out-of-bound position reporting + ALSA: usb-audio: Extend DragonFly dB scale quirk to cover other variants + ALSA: usb-line6: use the same declaration as definition in header for MIDI manufacturer ID + mfd: rtsx_usb: Avoid setting ucr->current_sg.status + mfd: atmel-hlcdc: Do not sleep in atomic context + mfd: 88pm80x: Double shifting bug in suspend/resume + mfd: wm8350-i2c: Make sure the i2c regmap functions are compiled + KVM: PPC: Book3s PR: Allow access to unprivileged MMCR2 register + KVM: MIPS: Drop other CPU ASIDs on guest MMU changes + KVM: PPC: BookE: Fix a sanity check + x86/boot: Fix kdump, cleanup aborted E820_PRAM max_pfn manipulation + x86/irq: Prevent force migration of irqs which are not in the vector domain + x86/dumpstack: Fix x86_32 kernel_stack_pointer() previous stack access + ARM: dts: mvebu: armada-390: add missing compatibility string and bracket + ARM: dts: MSM8064 remove flags from SPMI/MPP IRQs + ARM: cpuidle: Fix error return code + ima: use file_dentry() + tpm: fix a race condition in tpm2_unseal_trusted() + tpm_crb: fix crb_req_canceled behavior + Linux 4.4.25 -- 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/1634153 Title: Xenial update to v4.4.25 stable release Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Bug description: SRU Justification Impact: The upstream process for stable tree upd
[Kernel-packages] [Bug 1633690] Re: byt-max98090 not working on linux-image-4.8.0-22-generic on baytrail hardware
I'm betting it is related to commit
cfffcc66a89ab6d9961b2cde6cdab2ba056451ad ('ASoC: Intel: Load the atom
DPCM driver only')
--
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/1633690
Title:
byt-max98090 not working on linux-image-4.8.0-22-generic on baytrail
hardware
Status in linux package in Ubuntu:
Incomplete
Bug description:
After a recent 'do-release-upgrade' upgrade from Xenial's linux-
image-4.4.0-42-generic kernel to Yakkety's linux-
image-4.8.0-22-generic, I lost my audio output. Some investigation
showed that the hardware was not being detected at all, and further
investigation revealed the following:
Excerpt from dmesg:
intel_sst_acpi 80860F28:00: No matching machine driver found
After a bit of poking around I suspect that this is a kernel build
configuration issue and probably not actual code that is the root of this
issue. On a hunch I installed linux-image-4.7.2-galliumos from the galliumos
repo and got my sound working again, which to me confirms that this is a kernel
issue and not a userland issue. I was not using galliumos kernels before and
had my audio working properly in Xenial.
Please let me know if you can hunt this down with the provided
information or if you need me to boot the bad kernel again and give
you more stuff to work with.
Thanks
HARDWARE INFO:
00:00.0 Host bridge [0600]: Intel Corporation Atom Processor Z36xxx/Z37xxx
Series SoC Transaction Register [8086:0f00] (rev 0e)
Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC
Transaction Register [8086:0f31]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR-
Kernel driver in use: i915
Kernel modules: i915
00:14.0 USB controller [0c03]: Intel Corporation Atom Processor
Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI [8086:0f35] (rev 0e) (prog-if 30
[XHCI])
Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron
N2000 Series USB xHCI [8086:0f35]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+
Unsupported+
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+
TransPend-
LnkCap: Port #1, Speed 5GT/s, Width x1, ASPM L0s L1, Exit
Latency L0s <512ns, L1 <1us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+
DLActive+ BWMgmt+ ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug-
Surprise-
Slot #0, PowerLimit 10.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq-
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power-
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+
Interlock-
Changed: MRL- PresDet+ LinkState+
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Range BC, TimeoutDis+, LTR-, OBFF
Not Supported ARIFwd-
DevCtl2: Completion Timeout: 65ms to 210ms, TimeoutDis-, LTR-,
OBFF Disabled ARIFwd-
LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
Transmit Margin: Normal Operating Range,
EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -3.5dB,
EqualizationComplete-, EqualizationPhase1-
EqualizationPhase2-, EqualizationPhase3-,
LinkEqualizationRequest-
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee0300c Data: 41e2
Capabilities: [90] Subsystem: Intel Corporation Atom Processor E3800
Series PCI Express Root Port 1 [8086:0f48]
Capabilities:
[Kernel-packages] [Bug 1632918] onza (i386) - tests ran: 3, failed: 1
tests ran: 3, failed: 1; http://kernel.ubuntu.com/testing/4.8.0-25.27/onza__4.8.0-25.27__2016-10-17_12-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. https://bugs.launchpad.net/bugs/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1633414] Re: linux: 4.4.0-44.64 -proposed tracker
** 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) => Stefan Bader (smb) -- 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/1633414 Title: linux: 4.4.0-44.64 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Confirmed Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-44.64 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 -- swm properties -- derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1633414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] modoc (ppc64el) - tests ran: 136, failed: 0
tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-25.27/modoc__4.8.0-25.27__2016-10-17_13-42-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632252] Re: linux autopkgtest kills sshd in testbed
With the QEMU runner this gets further, but it fails for me with 14:33:01 DEBUG| Running 'git clone https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/yakkety linux' 14:33:01 ERROR| [stderr] Cloning into 'linux'... autopkgtest [16:02:54]: ERROR: timed out on command "..." (kind: test) autopkgtest [16:02:54]: test ubuntu-regression-suite: ---] Exception in thread copyin: OSError: [Errno 28] No space left on device Which bears the questions: (1) why is this timing out -- shouldn't failures like this cause an immediate exit? ISTM that the test suite is very prone to just hanging when anything goes wrong; can this be robustified somehow? (2) Is it really necessary to clone the entire kernel for the test? This will both take ages (it is running through a proxy in the infra!) and also take lots of disk space. If this just needs a few files, can you get them individually instead? If this needs to compile some helper/test binaries, can this happen during package build and you ship them in linux-source, linux-tools-XX, or maybe the -dbgsym package? -- 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/1632252 Title: linux autopkgtest kills sshd in testbed Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: The current linux autopkgtests in yakkety are caught in an eternal "temporary failure" retry loop. They stopped timing out, but in the middle of the tests they kill sshd. Tail of test output: 09:01:00 DEBUG| [stdout] preparing apparmor_2.10.95-4ubuntu5.dsc... done 09:01:00 DEBUG| [stdout] 09:01:40 ERROR| [stderr] Run libapparmor testsuite (with python3) ... ok 09:01:40 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites) 09:01:48 DEBUG| [stdout] preparing apparmor_2.10.95-4ubuntu5.dsc... done 09:01:48 DEBUG| [stdout] 09:19:27 ERROR| [stderr] Run parser regression tests ... ok 09:19:27 ERROR| [stderr] test_regression_testsuite (__main__.ApparmorTestsuites) 09:19:33 DEBUG| [stdout] preparing apparmor_2.10.95-4ubuntu5.dsc... done 09:19:33 DEBUG| [stdout] Killed Killed Connection to 10.220.42.236 closed by remote host. Exit request sent. autopkgtest [09:24:42]: ERROR: testbed failure: testbed auxverb failed with exit code 255 Console output during the test: Ubuntu 16.10 autopkgtest ttyS0 autopkgtest login: [ 3512.996305] AppArmor: change_hat: Invalid input '^open' [ 3513.000678] AppArmor: change_hat: Invalid input '^'[ 3513.013965] AppArmor: change_hat: Invalid input, NULL hat and NULL magic [ 3513.019831] AppArmor: change_hat: Invalid input, NULL hat and NULL magic [ 3513.024872] AppArmor: change_hat: Invalid input '^open'AppArmor: change_hat: Invalid input '^' [ 3513.026539] AppArmor: change_hat: Invalid input '^'[ 3638.281408] Out of memory: Kill process 587 (rsyslogd) score 8 or sacrifice child [ 3638.284907] Killed process 587 (rsyslogd) total-vm:107460kB, anon-rss:67892kB, file-rss:2548kB, shmem-rss:0kB [ 3638.306990] Out of memory: Kill process 300 (systemd-journal) score 2 or sacrifice child [ 3638.308985] Killed process 300 (systemd-journal) total-vm:46184kB, anon-rss:460kB, file-rss:3752kB, shmem-rss:15412kB [ 3638.319337] Out of memory: Kill process 2636 (autotest-local) score 1 or sacrifice child [ 3638.320394] Killed process 10325 (autotest-local) total-vm:18092kB, anon-rss:7296kB, file-rss:3544kB, shmem-rss:0kB [ 3638.345419] Out of memory: Kill process 2636 (autotest-local) score 1 or sacrifice child [ 3638.347095] Killed process 2638 (autotest-local) total-vm:17836kB, anon-rss:7160kB, file-rss:1752kB, shmem-rss:0kB [ 3638.368917] Out of memory: Kill process 2636 (autotest-local) score 1 or sacrifice child [ 3638.369954] Killed process 2637 (autotest-local) total-vm:17836kB, anon-rss:7160kB, file-rss:1684kB, shmem-rss:0kB [ 3638.479196] Out of memory: Kill process 2636 (autotest-local) score 1 or sacrifice child [ 3638.482968] Killed process 2636 (autotest-local) total-vm:17836kB, anon-rss:7248kB, file-rss:5864kB, shmem-rss:0kB [ 3638.501050] Out of memory: Kill process 10619 (python) score 1 or sacrifice child [ 3638.502022] Killed process 14752 (make) total-vm:6052kB, anon-rss:196kB, file-rss:2032kB, shmem-rss:0kB [ 3638.511243] Out of memory: Kill process 10619 (python) score 1 or sacrifice child [ 3638.512224] Killed process 10619 (python) total-vm:16752kB, anon-rss:5836kB, file-rss:6148kB, shmem-rss:0kB [ 3638.525104] Out of memory: Kill process 3382 (python) score 0 or sacrifice child [ 3638.526060] Killed process 3382 (python) total-vm:21296kB, anon-rss:3732kB, file-rss:4080kB, shmem-rss:0kB [ 3638.545114] Out of memory: Kill process 553 (haveged) score 0 or sacrifice child [ 3638.546068] Killed process 553 (haveged) total-vm:8028kB, anon-rs
[Kernel-packages] [Bug 1634050] Re: Please enable CONFIG_VFIO_NOIOMMU
** Also affects: linux (Ubuntu Z-series) Importance: Undecided Status: New ** Also affects: dpdk (Ubuntu Z-series) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Z-series) Status: New => In Progress ** Changed in: linux (Ubuntu Z-series) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- 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/1634050 Title: Please enable CONFIG_VFIO_NOIOMMU Status in dpdk package in Ubuntu: Incomplete Status in linux package in Ubuntu: Confirmed Status in dpdk source package in z-series: New Status in linux source package in z-series: In Progress Bug description: Hi, for certain cases a user might want to use VFIO in NO IOMMU mode. This only enables it to be an option, it doesn't change things unless "enable_unsafe_noiommu_mode" is set. See this reference: https://patchwork.kernel.org/patch/7906971/ for more details. This is used for some setups of DPDK see this http://dpdk- guide.gitlab.io/dpdk-guide/setup/binding.html#vfio-no-iommu Usually the reason to pick vfio over uio is the isolation. But there are some cases where vfio is required for extra features but can't work unless NO-IOMMU mode is used. I watched the topic a while checking if there is some major "oh crap what have we done" but there was none. An since by only enabling it in the kernel it shouldn't change a lot I wanted to ask if you could enable this config in the kernel for Z*. Technically it would be nice to get it in Yakkety as well, but I think we should be fine only working forward and enabling it in the Z release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1634050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634034] Re: kvm default ubuntu kernel: Kernel panic - not syncing: Fatal exception: panic_on_oops
** Also affects: linux (Ubuntu Yakkety)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux (Ubuntu Yakkety)
Status: New => In Progress
** Changed in: linux (Ubuntu Yakkety)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Tim Gardner
(timg-tpi)
--
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/1634034
Title:
kvm default ubuntu kernel: Kernel panic - not syncing: Fatal
exception: panic_on_oops
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Yakkety:
In Progress
Bug description:
During guest/isolated container execution following kernel bug got
triggered:
[ 249.792522] Modules linked in: bridge stp llc binfmt_misc qeth_l2 chsc_sch
eadm_sch tape_3590 tape tape_class qeth ccwgroup dm_round_robin ib_iser rdma_cm
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi
scsi_transport_iscsi dm_multipath btrfs zlib_deflate raid10 raid456
async_memcpy async_raid6_recov async_pq async_xor async_tx xor raid6_pq
libcrc32c raid1 linear raid0 ghash_s390 prng aes_s390 des_s390 des_generic
sha512_s390 sha256_s390 sha1_s390 sha_common dasd_eckd_mod dasd_mod zfcp qdio
scsi_transport_fc
[ 249.792558] CPU: 1 PID: 2461 Comm: qemu-system-s39 Not tainted
4.4.0-42-generic #62-Ubuntu
[ 249.792560] task: edf44c90 ti: 7be68000 task.ti:
7be68000
[ 249.792562] User PSW : 070520018000 03ff9e683730
[ 249.792564]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0
EA:3
User GPRS: f000 0001 0001
0002
[ 249.792566]03ff9e789420 0948
03ffc7c7d480
[ 249.792568] 0948
fc00
[ 249.792569]03ff9e789000 03ff9e6845e6
03ff7f5297b0
[ 249.792577] User Code: 03ff9e683720: ec32000100d9aghik %r3,%r2,1
03ff9e683726: b9040012lgr %r1,%r2
#03ff9e68372a: c0482e7blarl
%r4,3ff9e789420
>03ff9e683730: eb134030csg %r1,%r3,0(%r4)
03ff9e683736: ec1200288064cgrj
%r1,%r2,8,3ff9e683786
03ff9e68373c: c42800082e72lgrl
%r2,3ff9e789420
03ff9e683742: c418000842aflgrl
%r1,3ff9e78bca0
03ff9e683748: a7f4ff09brc 15,3ff9e68355a
[ 249.792602] Last Breaking-Event-Address:
[ 249.792604] [<03ff9e68355e>] 0x3ff9e68355e
[ 249.792605]
[ 249.792606] Kernel panic - not syncing: Fatal exception: panic_on_oops
#===
#=== Steps to Reproduce
#===
1. Use the KVM kernel module with qemu
By applying following upstream patch this bug was not triggered again:
commit f045402984404ddc11016358411e445192919047
Author: David Hildenbrand
Date: Thu Jul 7 10:44:10 2016 +0200
s390/mm: fix gmap tlb flush issues
__tlb_flush_asce() should never be used if multiple asce belong to
a mm.
As this function changes mm logic determining if local or global tlb
flushes will be neded, we might end up flushing only the gmap asce on all
CPUs and a follow up mm asce flushes will only flush on the local CPU,
although that asce ran on multiple CPUs.
The missing tlb flushes will provoke strange faults in user space and even
low address protections in user space, crashing the kernel.
Fixes: 1b948d6caec4 ("s390/mm,tlb: optimize TLB flushing for zEC12")
Cc: sta...@vger.kernel.org # 3.15+
Reported-by: Sascha Silbe
Acked-by: Martin Schwidefsky
Signed-off-by: David Hildenbrand
Signed-off-by: Martin Schwidefsky
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1634034/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1448942] Re: Juniper Network Connect Tun
This turned out to be an issue in juniper client. Newer version works find -- 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/1448942 Title: Juniper Network Connect Tun Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Released Bug description: Hi, i'm using Juniper Network Connect. With kernel Version "3.19.0-15-generic" it stops working. I the logfile of Network connect i saw: "IP Packet too small 0" I found a solution which also has implemented in Fedora: http://www.unixgr.com/juniper-ncsvc-and-linux-3-19/ and fix: https://bugzilla.kernel.org/show_bug.cgi?id=90901 --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mschroen 2784 F pulseaudio /dev/snd/controlC1: mschroen 2784 F pulseaudio /dev/snd/controlC0: mschroen 2784 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=cd8793fc-8985-4125-99f8-aff20e7ef69f InstallationDate: Installed on 2013-10-07 (566 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: LENOVO 20AY001DGE NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic root=/dev/mapper/vgubuntu-root ro quiet splash kopt=root=/dev/mapper/vgubuntu-root vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 Tags: vivid Uname: Linux 3.19.0-15-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-04-24 (3 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 07/23/2013 dmi.bios.vendor: LENOVO dmi.bios.version: J3ET32WW (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AY001DGE dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ3ET32WW(1.09):bd07/23/2013:svnLENOVO:pn20AY001DGE:pvrThinkPadS3-S440:rvnLENOVO:rn20AY001DGE:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AY001DGE dmi.product.version: ThinkPad S3-S440 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1448942/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632918] modoc (ppc64el) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-25.27/modoc__4.8.0-25.27__2016-10-17_14-51-00/results-index.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/1632918 Title: linux: 4.8.0-25.27 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-25.27 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 -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1632918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
