[Kernel-packages] [Bug 1661170] Re: HP Z640 USB port stopped working since 4.4.0-22.38

[Po-Hsu Lin]

For the note, this bug was converted from a question on launchpad.

** Project changed: linux => linux (Ubuntu)

** Tags added: xenial

-- 
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/1661170

Title:
  HP Z640 USB port stopped working since 4.4.0-22.38

Status in linux package in Ubuntu:
  New

Bug description:
  On HP Z640 Workstations running ubuntu 16.04  with any official ubuntu
  kernel newer than 4.4.0-21-generic USB devices do not work.

  They appear to be listed correctly via lsusb and connects and
  disconnects are logged but keyboards, mice, storage devices, ethernet
  adapters do not work at all when they are connected directly via any
  USB ports on the machines or through USB hubs.

  All ubuntu packages are up to date. The BIOS version is the latest
  (2.29).

  The ubuntu 4.4.0-21.37 kernel works correctly as do older kernels from
  ubuntu 16.04. Vanilla kernel.org kernels that I've tried such as
  4.4.30 and 4.4.38 work correctly.

  Ubuntu kernels greater than 4.4.0-21.37, from 4.4.0-22.38 all the way
  to 4.4.0-59.80 and 4.8.0-34.36 are affected by this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661170/+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 1661170] [NEW] HP Z640 USB port stopped working since 4.4.0-22.38

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

On HP Z640 Workstations running ubuntu 16.04  with any official ubuntu
kernel newer than 4.4.0-21-generic USB devices do not work.

They appear to be listed correctly via lsusb and connects and
disconnects are logged but keyboards, mice, storage devices, ethernet
adapters do not work at all when they are connected directly via any USB
ports on the machines or through USB hubs.

All ubuntu packages are up to date. The BIOS version is the latest
(2.29).

The ubuntu 4.4.0-21.37 kernel works correctly as do older kernels from
ubuntu 16.04. Vanilla kernel.org kernels that I've tried such as 4.4.30
and 4.4.38 work correctly.

Ubuntu kernels greater than 4.4.0-21.37, from 4.4.0-22.38 all the way to
4.4.0-59.80 and 4.8.0-34.36 are affected by this issue.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
HP Z640 USB port stopped working since 4.4.0-22.38
https://bugs.launchpad.net/bugs/1661170
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 1661168] [NEW] In Ubuntu16.10: Kdump stuck in boot for longer time need to force reboot via HMC in 32TB Brazos System

[bugproxy]

Public bug reported:

Problem Description
===
  In Ubuntu16.10 tried  kdump in Brazos system (32TB Memory and 192 core). when 
trigger panic  kdump process  stuck in boot process  need to do force reboot 
.After reboot system captured vmcore-incomplete.

Reproducible Step:
==
1- Install Ubuntu16.10
2- boot system with 31TB and 192 Core 
3- configure kdump in system 
4- verify kdump in system that it is running 
5- Trigger panic in system

Actual Result
--
kdump process  stuck in boot process  need to do force reboot

Expected Result 
-
Kdump will proceed and vmcore captured  successfully.

LOG:

root@ltc-brazos1:~# cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinux-4.4.0-30-generic 
root=UUID=516c4b1b-6700-4b55-bd37-d61c4c5af6af ro quiet splash crashkernel=4096M
root@ltc-brazos1:~# kdump-config show
DUMP_MODE:kdump
USE_KDUMP:1
KDUMP_SYSCTL: kernel.panic_on_oops=1
KDUMP_COREDIR:/var/crash
crashkernel addr: 
   /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.4.0-30-generic
kdump initrd: 
   /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.4.0-30-generic
current state:ready to kdump

kexec command:
  /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.4.0-30-generic 
root=UUID=516c4b1b-6700-4b55-bd37-d61c4c5af6af ro quiet splash irqpoll 
nr_cpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
root@ltc-brazos1:~# 
root@ltc-brazos1:~# dpkg -l | grep kdump 
ii  kdump-tools1:1.6.0-2 all
  scripts and tools for automating kdump (Linux crash dumps)
root@ltc-brazos1:~# 
root@ltc-brazos1:~# echo c > /proc/sysrq-trigger 


ltc-brazos1 login: [  416.229464] sysrq: SysRq : Trigger a crash


[  416.229496] Unable to handle kernel paging request for data at address 
0x  
  
[  416.229502] Faulting instruction address: 0xc0670014 


[  416.229508] Oops: Kernel access of bad area, sig: 11 [#1]


[  416.229511] SMP NR_CPUS=2048 NUMA pSeries


[  416.229517] Modules linked in: pseries_rng btrfs xor raid6_pq rtc_generic 
sunrpc autofs4 ses enclosure ipr
   
[  416.229532] CPU: 65 PID: 404785 Comm: bash Not tainted 4.4.0-30-generic 
#49-Ubuntu  
 
[  416.229537] task: c1f9d583c8e0 ti: c1fa13cd8000 task.ti: 
c1fa13cd8000

[  416.229543] NIP: c0670014 LR: c06710c8 CTR: c066ffe0 


[  416.229548] REGS: c1fa13cdb990 TRAP: 0300   Not tainted  
(4.4.0-30-generic)  

[  416.229552] MSR: 80009033   CR: 2824  XER: 
0001

[  416.229565] CFAR: c0008468 DAR:  DSISR: 4200 
SOFTE: 1

GPR00: c06710c8 c1fa13cdbc10 c15b5d00 0063  


GPR04: c1fab9049c50 c1fab905b4e0 c0001f3fff3d 0313  


GPR08: 0007 0001  c0001f3fff3dec68  


GPR12: c066ffe0 c7546980  2200 
GPR16: 10170dc8 0100174901d8 10140f58 100c7570 
GPR20:  1017dd58 10153618 1017b608 
GPR24: 38966c94 0001 c14f8e58 0004 
GPR28: c14f9218 0063 c14b11dc  
[  416.229631] NIP [c0670014] sysrq_handle_crash+0x34/0x50
[  416.229636] LR [c06710c8] __handle_sysrq+0xe8/0x270
[  416.229640] Call Trace:
[  416.229645] [c1fa13cdbc10] [c0e08f

[Kernel-packages] [Bug 1661168] [NEW] In Ubuntu16.10: Kdump stuck in boot for longer time need to force reboot via HMC in 32TB Brazos System

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Problem Description
===
  In Ubuntu16.10 tried  kdump in Brazos system (32TB Memory and 192 core). when 
trigger panic  kdump process  stuck in boot process  need to do force reboot 
.After reboot system captured vmcore-incomplete.

Reproducible Step:
==
1- Install Ubuntu16.10
2- boot system with 31TB and 192 Core 
3- configure kdump in system 
4- verify kdump in system that it is running 
5- Trigger panic in system

Actual Result
--
kdump process  stuck in boot process  need to do force reboot

Expected Result 
-
Kdump will proceed and vmcore captured  successfully.

LOG:

root@ltc-brazos1:~# cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinux-4.4.0-30-generic 
root=UUID=516c4b1b-6700-4b55-bd37-d61c4c5af6af ro quiet splash crashkernel=4096M
root@ltc-brazos1:~# kdump-config show
DUMP_MODE:kdump
USE_KDUMP:1
KDUMP_SYSCTL: kernel.panic_on_oops=1
KDUMP_COREDIR:/var/crash
crashkernel addr: 
   /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.4.0-30-generic
kdump initrd: 
   /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.4.0-30-generic
current state:ready to kdump

kexec command:
  /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.4.0-30-generic 
root=UUID=516c4b1b-6700-4b55-bd37-d61c4c5af6af ro quiet splash irqpoll 
nr_cpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
root@ltc-brazos1:~# 
root@ltc-brazos1:~# dpkg -l | grep kdump 
ii  kdump-tools1:1.6.0-2 all
  scripts and tools for automating kdump (Linux crash dumps)
root@ltc-brazos1:~# 
root@ltc-brazos1:~# echo c > /proc/sysrq-trigger 


ltc-brazos1 login: [  416.229464] sysrq: SysRq : Trigger a crash


[  416.229496] Unable to handle kernel paging request for data at address 
0x  
  
[  416.229502] Faulting instruction address: 0xc0670014 


[  416.229508] Oops: Kernel access of bad area, sig: 11 [#1]


[  416.229511] SMP NR_CPUS=2048 NUMA pSeries


[  416.229517] Modules linked in: pseries_rng btrfs xor raid6_pq rtc_generic 
sunrpc autofs4 ses enclosure ipr
   
[  416.229532] CPU: 65 PID: 404785 Comm: bash Not tainted 4.4.0-30-generic 
#49-Ubuntu  
 
[  416.229537] task: c1f9d583c8e0 ti: c1fa13cd8000 task.ti: 
c1fa13cd8000

[  416.229543] NIP: c0670014 LR: c06710c8 CTR: c066ffe0 


[  416.229548] REGS: c1fa13cdb990 TRAP: 0300   Not tainted  
(4.4.0-30-generic)  

[  416.229552] MSR: 80009033   CR: 2824  XER: 
0001

[  416.229565] CFAR: c0008468 DAR:  DSISR: 4200 
SOFTE: 1

GPR00: c06710c8 c1fa13cdbc10 c15b5d00 0063  


GPR04: c1fab9049c50 c1fab905b4e0 c0001f3fff3d 0313  


GPR08: 0007 0001  c0001f3fff3dec68  


GPR12: c066ffe0 c7546980  2200 
GPR16: 10170dc8 0100174901d8 10140f58 100c7570 
GPR20:  1017dd58 10153618 1017b608 
GPR24: 38966c94 0001 c14f8e58 0004 
GPR28: c14f9218 0063 c14b11dc  
[  416.229631] NIP [c0670014] sysrq_handle_crash+0x34/0x50
[  416.229636] LR [c06710c8] __handle_sysrq+0xe8/0x270
[  416.229640] Call Trace:
[  416.229645] [c1fa13cd

[Kernel-packages] [Bug 1627217] Re: ipv6 forwarding kernel oops

[Rob Emanuele]

Corrected tag

This is still an issue.

** Tags removed: stagingkernel-bug-exists-upstream
** Tags added: kernel-bug-exists-upstream staging

-- 
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/1627217

Title:
  ipv6 forwarding kernel oops

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After a box is configured as an ipv6 router and
  net.ipv6.conf.enp1s0.accept_ra=2 is set the kernel panics when it
  tries to forward packets.  The crash occurs after a few packets go
  through.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-38-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Fri Sep 23 17:21:03 2016
  HibernationDevice: RESUME=/dev/mapper/wormhole--vg-swap_1
  InstallationDate: Installed on 2016-09-21 (2 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: MSI MS-7599
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 XGI
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic 
root=/dev/mapper/hostname--vg-root ro console=tty0 console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  StagingDrivers: xgifb
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 870-G45 (MS-7599)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd08/30/2013:svnMSI:pnMS-7599:pvr2.0:rvnMSI:rn870-G45(MS-7599):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7599
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627217/+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

Re: [Kernel-packages] [Bug 1348890] Re: Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event

[Xaver]

Worked for Asus UX303LN as well.

Is there an ETA when it (if at all) will be merged in the mainline
kernel, or for which kind of commit massage I have to lookout for?

-- 
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/1348890

Title:
  Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev
  event

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello Community,

  It seems brightness keys don't work with latest Ubuntu 14.04 LTS for
  laptop Asus Zenbook UX32LN.

  sudo dmidecode -s bios-version
  UX32LN.203

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1348890/+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 1661131] Missing required logs.

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1661131

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/1661131

Title:
  kernel crash when NVMe drive inserted in one slot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Opening this on behalf of one of my colleagues at Cisco, we're seeing
  an issue on our new S-series S3260 server that's causing the kernel to
  crash.

  If we have an NVMe device inserted into one of two drive slots, we
  will see kernel crash only with Ubuntu. With an NVMe drive in the bad
  slot, other OS's will work fine. If we move the NVMe drive out of the
  bad slot and into the other slot, everything is working fine as
  expected. We only see the kernel crash with an NVMe drive in that bad
  slot when using Ubuntu. We tested with HGST and Intel NVMe drives and
  were able to reproduce the issue with both. HGST reviewed some logs
  and they don't believe at this time the issue is with the NVMe drives.

  We're hoping someone from Canonical can take a look to understand what
  is the difference between the working and failing slot. The data
  collection was done with the NVMe drive inserted in the working slot
  so we could access the OS.

  I had a connection time out when trying to use ubuntu-bug, so I saved
  the apport file and will attach to the bug. I have collected the
  kernel and syslog as well, but they are ~9GB. I found a call trace in
  the kernel log start on Jan 25 06:02:54 and floods the logs
  afterwards. I will include the call trace in a separate text file on
  the attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661131/+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 1661131] [NEW] kernel crash when NVMe drive inserted in one slot

[jeffrey leung]

Public bug reported:

Opening this on behalf of one of my colleagues at Cisco, we're seeing an
issue on our new S-series S3260 server that's causing the kernel to
crash.

If we have an NVMe device inserted into one of two drive slots, we will
see kernel crash only with Ubuntu. With an NVMe drive in the bad slot,
other OS's will work fine. If we move the NVMe drive out of the bad slot
and into the other slot, everything is working fine as expected. We only
see the kernel crash with an NVMe drive in that bad slot when using
Ubuntu. We tested with HGST and Intel NVMe drives and were able to
reproduce the issue with both. HGST reviewed some logs and they don't
believe at this time the issue is with the NVMe drives.

We're hoping someone from Canonical can take a look to understand what
is the difference between the working and failing slot. The data
collection was done with the NVMe drive inserted in the working slot so
we could access the OS.

I had a connection time out when trying to use ubuntu-bug, so I saved
the apport file and will attach to the bug. I have collected the kernel
and syslog as well, but they are ~9GB. I found a call trace in the
kernel log start on Jan 25 06:02:54 and floods the logs afterwards. I
will include the call trace in a separate text file on the attachment.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Attachment added: "contains apport, call trace, lspci, uname, version_sig"
   
https://bugs.launchpad.net/bugs/1661131/+attachment/4811959/+files/colusa2bug.zip

-- 
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/1661131

Title:
  kernel crash when NVMe drive inserted in one slot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Opening this on behalf of one of my colleagues at Cisco, we're seeing
  an issue on our new S-series S3260 server that's causing the kernel to
  crash.

  If we have an NVMe device inserted into one of two drive slots, we
  will see kernel crash only with Ubuntu. With an NVMe drive in the bad
  slot, other OS's will work fine. If we move the NVMe drive out of the
  bad slot and into the other slot, everything is working fine as
  expected. We only see the kernel crash with an NVMe drive in that bad
  slot when using Ubuntu. We tested with HGST and Intel NVMe drives and
  were able to reproduce the issue with both. HGST reviewed some logs
  and they don't believe at this time the issue is with the NVMe drives.

  We're hoping someone from Canonical can take a look to understand what
  is the difference between the working and failing slot. The data
  collection was done with the NVMe drive inserted in the working slot
  so we could access the OS.

  I had a connection time out when trying to use ubuntu-bug, so I saved
  the apport file and will attach to the bug. I have collected the
  kernel and syslog as well, but they are ~9GB. I found a call trace in
  the kernel log start on Jan 25 06:02:54 and floods the logs
  afterwards. I will include the call trace in a separate text file on
  the attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661131/+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 1655071] Re: linux: 3.2.0-121.164 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.2.0-121.164

---
linux (3.2.0-121.164) precise; urgency=low

  [ John Donnelly ]

  * Release Tracking Bug
- LP: #1655071

  * CVE-2016-9685
- xfs: fix two memory leaks in xfs_attr_list.c error paths

  * CVE-2016-9555
- sctp: validate chunk len before actually using it

 -- John Donnelly   Mon, 09 Jan 2017
11:03:53 +

** Changed in: linux (Ubuntu Precise)
   Status: Confirmed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-9555

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-9685

-- 
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/1655071

Title:
  linux: 3.2.0-121.164 -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:
  Fix Released
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:
  Fix Committed
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Committed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Released

Bug description:
  This bug is for tracking the 3.2.0-121.164 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/1655071/+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 1655071] Re: linux: 3.2.0-121.164 -proposed tracker

[Steve Langasek]

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-updates
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve 
Langasek (vorlon)

** Changed in: kernel-sru-workflow/promote-to-security
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve 
Langasek (vorlon)

-- 
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/1655071

Title:
  linux: 3.2.0-121.164 -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:
  Fix Released
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:
  Fix Committed
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Committed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Released

Bug description:
  This bug is for tracking the 3.2.0-121.164 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/1655071/+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 1628889] Re: [17.04 FEAT] Integrate kernel message catalogue for s390x into Ubuntu distribution

[Tim Gardner]

This kernel-messages branch needs to be refactored for v4.10-rc6 as it
does not cherry-pick cleanly.

-- 
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/1628889

Title:
  [17.04 FEAT] Integrate kernel message catalogue for s390x into Ubuntu
  distribution

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  For each kernel a message catalogue is available for s390x.
  For better servicablity, customers asking for having this kernel messages as 
part of the distribution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1628889/+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 1660704] Re: linux: 4.4.0-63.84 -proposed tracker

[Brad Figg]

** 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) => Thadeu Lima de 
Souza Cascardo (cascardo)

** Description changed:

  This bug is for tracking the 4.4.0-63.84 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
+ kernel-stable-phase-changed:Wednesday, 01. February 2017 22:32 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the 4.4.0-63.84 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
- kernel-stable-phase-changed:Wednesday, 01. February 2017 22:32 UTC
- kernel-stable-phase:Uploaded
+ 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/1660704

Title:
  linux: 4.4.0-63.84 -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 upload-to-ppa series:
  Invalid
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-63.84 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/1660704/+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 1626436] Re: [4.8 regression] boot has become very slow

[Dimitrij Mijoski]

For completeness, the latest mainline.

4.10.0rc6
Startup finished in 15.387s (kernel) + 25.344s (userspace) = 40.731s

We can definitely conclude something happens between 4.7.10 and
4.8.0rc1. Detailed bisection should happen there.

-- 
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:
  In Progress
Status in linux source package in Yakkety:
  In Progress

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.4. 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 1636656] Re: [Hyper-V] netvsc: fix incorrect receive checksum offloading

[Chris Valean]

Hi Joe,

For the v2 test kernel for Trusty from comment #11:

The kernels 3.13 and 3.19 at least from our testing might not be
affected by this bug as those don't have any receive checksum
offloading, and therefore the patch here is not applicable.

Even with the cherry-pick, the behavior with only the patch for "fix
incorrect receive checksum offloading" and the related dependencies, a
file copy over scp is not completing.

So please do not backport this patch to Trusty / kernel 3.13 and/or
3.19.

-- 
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/1636656

Title:
  [Hyper-V] netvsc: fix incorrect receive checksum offloading

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  The Hyper-V netvsc driver was looking at the incorrect status bits
  in the checksum info. It was setting the receive checksum unnecessary
  flag based on the IP header checksum being correct. The checksum
  flag is skb is about TCP and UDP checksum status. Because of this
  bug, any packet received with bad TCP checksum would be passed
  up the stack and to the application causing data corruption.
  The problem is reproducible via netcat and netem.

  This had a side effect of not doing receive checksum offload
  on IPv6. The driver was also also always doing checksum offload
  independent of the checksum setting done via ethtool.

  Signed-off-by: Stephen Hemminger 

  https://patchwork.ozlabs.org/patch/685660/

  When this patch is committed I will include the commit ID in this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636656/+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 1659618] Re: Enable ARM64 support in kexec-tools

[Launchpad Bug Tracker]

This bug was fixed in the package kexec-tools - 1:2.0.14-1ubuntu1

---
kexec-tools (1:2.0.14-1ubuntu1) zesty; urgency=medium

  * Merge from Debian unstable.  Remaining changes:
- Default to not kexecing a kernel on boot in the automatically
  generated conffile
- Don't call db_stop from the postinst.
- Adjust INITCONFFILE to vmlinux if used
- Use format-security.patch instead of const_string_warning.patch
- Add maintainer script helper to handle removal of conffile
  /etc/default/grub.d/kexec-tools.cfg has been removed.
  Handle it properly
- Add Breaks: statement toward kdump-tools
   Starting with kdump-tools 1:1.5.9-6, this package takes
   over the addition of crashkernel= parameter which has
   been removed from kexec-tools.
   Make sure that it is upgraded accordingly.
  * Debian merge adds arm64 support (LP: #1659618).

 -- dann frazier   Wed, 01 Feb 2017 12:48:15 -0700

** Changed in: kexec-tools (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1659618

Title:
  Enable ARM64 support in kexec-tools

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  Confirmed
Status in kexec-tools source package in Yakkety:
  Confirmed
Status in kexec-tools package in Debian:
  Fix Released

Bug description:
  [IMPACT]
   * kexec-tools in Xenial (16.04) currently does not support ARM64
     architecture.
   * Backport support for ARM64 arch from upstream
     https://github.com/horms/kexec-tools
   * Majority of the patches are contained in kexec/arch/arm64/ except for
     one patch that impacts purgatory and common device tree routines.

  [TEST CASE]
   * I built kexec-tools for ARM64 and tested it on HW using the following
     testcase:
     $ sudo kexec -l /boot/vmlinuz--generic
   --initrd=/boot/initrd.img--generic
   --command-line="root=UUID= ro vt.handoff=7"
     $ sudo kexec -e
   * I was able to kexec the new kernel successfully.
   * [ 6702.357899] kexec_core: Starting new kernel
     [0.00] Booting Linux on physical CPU 0x200
     [0.00] Linux version -generic (buildd@bos01-arm64-008)
     (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) )
     [0.00] Boot CPU: AArch64 Processor [510f8000]

  [REGRESSION POTENTIAL]
   * Since patches are confined to arm[64] there is a low overall risk of
     regression.

  [OTHER INFO]
   * You can find a Xenial kexec-tools package built for AMD64, i386 and
     ARM64 in my PPA
     https://launchpad.net/~manjo/+archive/ubuntu/kexec-tools
   * This package is built using the Xenial source package for kexec-tools
     with ARM64 enablement patches applied.
   * Please pull the changes from my PPA package and integrate into Ubuntu
     Xenial kexec-tools after review.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1659618/+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 1626436] Re: [4.8 regression] boot has become very slow

[Dimitrij Mijoski]

I decided to test with some of the mainline kernel images posted at
http://kernel.ubuntu.com/~kernel-ppa/mainline/

4.6.4
Startup finished in 4.991s (kernel) + 23.504s (userspace) = 28.496s

4.6.6
Startup finished in 5.019s (kernel) + 24.044s (userspace) = 29.064s

4.6.7
Startup finished in 5.063s (kernel) + 24.008s (userspace) = 29.072s


4.7.0rc1
Startup finished in 6.260s (kernel) + 24.199s (userspace) = 30.460s
^^
we see the first small jump here in 4.7rc1

4.7.0rc7
Startup finished in 6.800s (kernel) + 22.748s (userspace) = 29.548s

4.7.10
Startup finished in 5.718s (kernel) + 23.185s (userspace) = 28.904s
Startup finished in 6.632s (kernel) + 22.865s (userspace) = 29.498s

4.8.0rc1
Startup finished in 17.619s (kernel) + 23.272s (userspace) = 40.892s
Startup finished in 17.364s (kernel) + 29.914s (userspace) = 47.278s
^^
first large jump in 4.8rc1 

4.8.0
Startup finished in 16.631s (kernel) + 23.861s (userspace) = 40.493s

-- 
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:
  In Progress
Status in linux source package in Yakkety:
  In Progress

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.4. 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/1

[Kernel-packages] [Bug 1655683] Re: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch]

[Tim Gardner]

This patch should be released with 3.13.0-109.156

** Changed in: linux (Ubuntu Trusty)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1655683

Title:
  kernel BUG at skbuff.h:1486 Insufficient linear data in skb
  __skb_pull.part.7+0x4/0x6 [openvswitch]

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  Since 2016-12-30 EST we have been experiencing repeated crashes of our
  OpenStack Icehouse / Trusty Neutron node with a kernel BUG at skbuff.h
  line 1486:

  1471 /**
  1472 * skb_peek - peek at the head of an &sk_buff_head
  1473 * @list_: list to peek at
  1474 *
  1475 * Peek an &sk_buff. Unlike most other operations you _MUST_
  1476 * be careful with this one. A peek leaves the buffer on the
  1477 * list and someone else may run off with it. You must hold
  1478 * the appropriate locks or have a private queue to do this.
  1479 *
  1480 * Returns %NULL for an empty list or a pointer to the head element.
  1481 * The reference count is not incremented and the reference is therefore
  1482 * volatile. Use with caution.
  1483 */
  1484 static inline struct sk_buff *skb_peek(const struct sk_buff_head *list_)
  1485 {
  1486 struct sk_buff *skb = list_->next;
  1487
  1488 if (skb == (struct sk_buff *)list_)
  1489 skb = NULL;
  1490 return skb;
  1491 }

  This generally results in a full panic crash of the Neutron node and
  connectivity breaking for VMs within the cloud. However, after using
  crash-dumptools to collect information on the crashes over the past
  three days, the kernel loaded by kexec during the crashdump appears in
  about 2 out of 3 crash instances to continue running, and we see a
  flap of the neutron services instead of a full panic that brings the
  Neutron server down and necessitates a hard reboot.

  I believe that this is a manifestation of the openvswitch and issue
  described on 2017-01-08 as:

  "OVS can only process L2 packets. But OVS GRE receive handler
  can accept IP-GRE packets. When such packet is processed by
  OVS datapath it can trigger following assert failure due
  to insufficient linear data in skb."

  https://patchwork.ozlabs.org/patch/712373/

  I have not tested the patch provided above yet.

  Other information and a few sample dmesg outputs from the crash:
  (multiple dumps available)

  # lsb_release -rd
  Description: Ubuntu 14.04.5 LTS
  Release: 14.04

  # apt-cache policy openvswitch
  N: Unable to locate package openvswitch
  root@neutron01:/var/crash# apt-cache policy openvswitch-common
  openvswitch-common:
Installed: 2.0.2-0ubuntu0.14.04.3
Candidate: 2.0.2-0ubuntu0.14.04.3
Version table:
   *** 2.0.2-0ubuntu0.14.04.3 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.0.1+git20140120-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  # apt-cache policy openvswitch-switch
  openvswitch-switch:
Installed: 2.0.2-0ubuntu0.14.04.3
Candidate: 2.0.2-0ubuntu0.14.04.3
Version table:
   *** 2.0.2-0ubuntu0.14.04.3 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.0.1+git20140120-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  # apt-cache policy neutron-plugin-openvswitch-agent
  neutron-plugin-openvswitch-agent:
Installed: 1:2014.1.5-0ubuntu7
Candidate: 1:2014.1.5-0ubuntu7
Version table:
   *** 1:2014.1.5-0ubuntu7 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:2014.1.3-0ubuntu1.1 0
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
   1:2014.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  example dmesg:

  ## dmesg.201701060019

  > [33100.131019] [ cut here ]
  > [33100.131176] kernel BUG at 
/build/linux-mi9H1O/linux-3.13.0/include/linux/skbuff.h:1486!
  > [33100.131424] invalid opcode:  [#1] SMP
  > [33100.131560] Modules linked in: xt_nat xt_conntrack ip6table_filter 
ip6_tables iptable_filter xt_REDIRECT xt_tcpudp iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables veth 
openvswitch gre vxlan ip_tunnel libcrc32c ipmi_devintf gpio_ich cdc_ether 
x86_pkg_temp_thermal intel_powerclamp coretemp usbnet kvm_intel mii kvm 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd sb_edac edac_core lpc_ich wmi ipmi_si 
bonding shpchp ioatdma lp mac_hid parport ahci libahci sfc igb e1000e mtd dca 
i2c_algo_bit ptp pps_core megaraid_sas mdio

[Kernel-packages] [Bug 1510570] Re: BLE pairing fail

[grafviktor]

Apologize, not 26, but 27. Haven't found how to edit my previous
comment.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  BLE pairing fail

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.

  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used 
instead of udev rules.

  here is a commit with this parameter: 
http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138
  And a ppa to test it: 
https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570/+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 1510570] Re: BLE pairing fail

[grafviktor]

#23 resolved my problem, I haven't changed any other files, like 25 and
26 suggested.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  BLE pairing fail

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.

  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used 
instead of udev rules.

  here is a commit with this parameter: 
http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138
  And a ppa to test it: 
https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570/+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 1659340] Re: Linux kernel 4.8 hangs at boot up

[kjellahl]

Correction:
v4.8.0-34.36-commit129766708reverted passed

Yes, it was linux-signed-image-4.8.0-34-generic that made the test fail.
When I temporarily changed
  linux /boot/vmlinuz-4.8.0-34-generic.efi.signed .
to
  linux /boot/vmlinuz-4.8.0-34-generic ..
in grub's startup script, the test passed.

/boot/vmlinuz-4.8.0-34-generic, but not 
/boot/vmlinuz-4.8.0-34-generic.efi.signed,
was updated when I installed the new packages.

The output from uname -a is now
Linux kjell-Aspire-V5-551G 4.8.0-34-generic 
#36~lp1659340Commit129766708Reverted SMP Wed Feb 1 18:01:53 UTC  x86_64 x86_64 
x86_64 GNU/Linux

-- 
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/1659340

Title:
  Linux kernel 4.8 hangs at boot up

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot,
  Windows 10 and Ubuntu 16.10.

  Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45.
  When I try to start with any of the 4.8.0 kernels delivered with regular
  Ubuntu updates, they all hang after printing

Läser in Linux 4.8.0-34-generic ...
Läser in initial ramdisk ...

  Sorry for the partly Swedish text. I guess that the lines would start with
  "Loading" instead of "Läser in" on an English version.

  The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34
  and with -generic, -generic (upstart) and -generic (recovery mode).

  After a while the fan runs at full speed, as if the processor is working
  hard, but nothing happens.

  After I've tried in vain to start with Linux 4.8.0-xx, and then starts
  with 4.4.0-45, the following errors are usually printed:

  [  2.511733] usb 4-3: string descriptor 0 read error: -22
  [  3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight 
controller
  /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks
  [ 21.335117] usb 4-3: string descriptor 0 read error: -22

  When a successful start has not been immediately preceded by a failed start,
  only the line beginning "/dev/sda7" is printed.

  I have previously commented on bug #1635447. As recommended there, I've
  also tested with the upstream kernel 4.10-rc3. It worked just as bad as
  4.8.0.

  I tried to report this bug with 'ubuntu-bug linux' after I had booted with
  the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45-
  generic is not an official Ubuntu package.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kjell  2022 F pulseaudio
   /dev/snd/controlC1:  kjell  2022 F pulseaudio
   /dev/snd/controlC0:  kjell  2022 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb
  InstallationDate: Installed on 2013-09-25 (1218 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V5-551G
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.4.0-45-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/11/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Havok
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire V5-551G
  dmi.product.version: V2.14
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+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 1555786] Re: [Hyper-V] VM with ubuntu 32bit with linux-next does not boot

[Joseph Salisbury]

Testing in comment #5 confirmed this bug was only happening with the
upstream kernels and not Ubuntu kernels.  Is that still the case with
Xenial?

Also, can you confirm the patch in comment #26 is needed in Yakkety and
Zesty to get 32 bit Ubuntu VMs to boot?  If so, I will submit it for SRU
to whatever releases need it.

** No longer affects: linux (Ubuntu Xenial)

-- 
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/1555786

Title:
  [Hyper-V] VM with ubuntu 32bit with linux-next does not boot

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  We identified that at least ubuntu (let's take 15.10) does not boot if
  installed in the 32bit architecture, and using the linux-next upstream
  kernel 4.5 on it. This has been seen on other distributions as well.

  We took both the official linux-next branch from kernel.org and the one from 
kernel.ubuntu.com v4.5-rc7.
  For the compilation process we went either with the 4.2 kernel config file 
from the installed running kernel, and also built the config separately. 
  No errors have been encountered during the build or install process of the 
4.5 kernel, however at boot, the VM will just hang.
  There are no call traces or messages at boot to show any pottential issue.

  Have you seen this on your end when testing the 32bit build?
  Attaching the full serial log for reference, however I don't see any errors 
in the kernel boot process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555786/+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 1659340] Re: Linux kernel 4.8 hangs at boot up

[Joseph Salisbury]

After installing and rebooting into the new kernel, can you run the
following from a terminal:

uanme -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/1659340

Title:
  Linux kernel 4.8 hangs at boot up

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot,
  Windows 10 and Ubuntu 16.10.

  Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45.
  When I try to start with any of the 4.8.0 kernels delivered with regular
  Ubuntu updates, they all hang after printing

Läser in Linux 4.8.0-34-generic ...
Läser in initial ramdisk ...

  Sorry for the partly Swedish text. I guess that the lines would start with
  "Loading" instead of "Läser in" on an English version.

  The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34
  and with -generic, -generic (upstart) and -generic (recovery mode).

  After a while the fan runs at full speed, as if the processor is working
  hard, but nothing happens.

  After I've tried in vain to start with Linux 4.8.0-xx, and then starts
  with 4.4.0-45, the following errors are usually printed:

  [  2.511733] usb 4-3: string descriptor 0 read error: -22
  [  3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight 
controller
  /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks
  [ 21.335117] usb 4-3: string descriptor 0 read error: -22

  When a successful start has not been immediately preceded by a failed start,
  only the line beginning "/dev/sda7" is printed.

  I have previously commented on bug #1635447. As recommended there, I've
  also tested with the upstream kernel 4.10-rc3. It worked just as bad as
  4.8.0.

  I tried to report this bug with 'ubuntu-bug linux' after I had booted with
  the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45-
  generic is not an official Ubuntu package.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kjell  2022 F pulseaudio
   /dev/snd/controlC1:  kjell  2022 F pulseaudio
   /dev/snd/controlC0:  kjell  2022 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb
  InstallationDate: Installed on 2013-09-25 (1218 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V5-551G
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.4.0-45-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/11/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Havok
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire V5-551G
  dmi.product.version: V2.14
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+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 1659618] Re: Enable ARM64 support in kexec-tools

[dann frazier]

** Changed in: kexec-tools (Ubuntu)
 Assignee: Louis Bouchard (louis-bouchard) => dann frazier (dannf)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1659618

Title:
  Enable ARM64 support in kexec-tools

Status in kexec-tools package in Ubuntu:
  Confirmed
Status in kexec-tools source package in Xenial:
  Confirmed
Status in kexec-tools source package in Yakkety:
  Confirmed
Status in kexec-tools package in Debian:
  Fix Released

Bug description:
  [IMPACT]
   * kexec-tools in Xenial (16.04) currently does not support ARM64
     architecture.
   * Backport support for ARM64 arch from upstream
     https://github.com/horms/kexec-tools
   * Majority of the patches are contained in kexec/arch/arm64/ except for
     one patch that impacts purgatory and common device tree routines.

  [TEST CASE]
   * I built kexec-tools for ARM64 and tested it on HW using the following
     testcase:
     $ sudo kexec -l /boot/vmlinuz--generic
   --initrd=/boot/initrd.img--generic
   --command-line="root=UUID= ro vt.handoff=7"
     $ sudo kexec -e
   * I was able to kexec the new kernel successfully.
   * [ 6702.357899] kexec_core: Starting new kernel
     [0.00] Booting Linux on physical CPU 0x200
     [0.00] Linux version -generic (buildd@bos01-arm64-008)
     (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) )
     [0.00] Boot CPU: AArch64 Processor [510f8000]

  [REGRESSION POTENTIAL]
   * Since patches are confined to arm[64] there is a low overall risk of
     regression.

  [OTHER INFO]
   * You can find a Xenial kexec-tools package built for AMD64, i386 and
     ARM64 in my PPA
     https://launchpad.net/~manjo/+archive/ubuntu/kexec-tools
   * This package is built using the Xenial source package for kexec-tools
     with ARM64 enablement patches applied.
   * Please pull the changes from my PPA package and integrate into Ubuntu
     Xenial kexec-tools after review.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1659618/+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 1635063] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From ferse...@br.ibm.com 2017-02-01 14:30 EDT---
I have added the workaround to recommendations in our wiki page at:

https://wiki.ubuntu.com/ppc64el/Recommendations#Kdump_not_generating_crash_dump_file

Please check it out and let me know if it looks ok.

Cheers

-- 
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/1635063

Title:
  Ubuntu 16.10: System hangs after crash on Ubuntu KVM guest.

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---

  Ubuntu 16.10: System hangs after crash on Ubuntu KVM guest.

  ---Steps to Reproduce---

  1) apt-get install linux-crashdump
  2) increase crashdump size:
  sudo vim /etc/default/grub.d/kexec-tools.cfg

  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel
  =2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M"

  3) sudo update-grub ; reboot the machine
  4) sudo sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools
  5) kdump-config show
  6) echo "c" > /proc/sysrq-trigger

  Logs
  
  root@ubuntu:/var/crash# uname -a
  Linux ubuntu 4.8.0-17-generic #19-Ubuntu SMP Sun Sep 25 06:35:40 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  root@ubuntu:/var/crash# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.8.0-17-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.8.0-17-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.8.0-17-generic 
root=UUID=70f3c690-fe90-444d-a74c-71c05eef8b0e ro splash quiet irqpoll 
nr_cpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@ubuntu:/var/crash# echo c > /proc/sysrq-trigger
  [  202.677946] sysrq: SysRq : Trigger a crash
  [  202.678018] Unable to handle kernel paging request for data at address 
0x
  [  202.678098] Faulting instruction address: 0xc06de134
  [  202.678169] Oops: Kernel access of bad area, sig: 11 [#1]
  [  202.678222] SMP NR_CPUS=2048 NUMA pSeries
  [  202.678281] Modules linked in: vmx_crypto ip_tables x_tables autofs4 
ibmvscsi crc32c_vpmsum 8139too 8139cp mii
  [  202.678465] CPU: 3 PID: 1992 Comm: bash Not tainted 4.8.0-17-generic 
#19-Ubuntu
  [  202.678547] task: c4c5ce00 task.stack: c428c000
  [  202.678612] NIP: c06de134 LR: c06df218 CTR: 
c06de100
  [  202.678716] REGS: c428f990 TRAP: 0300   Not tainted  
(4.8.0-17-generic)
  [  202.678796] MSR: 80009033   CR: 2824  
XER: 2000
  [  202.678992] CFAR: c0014f84 DAR:  DSISR: 4200 
SOFTE: 1 
  GPR00: c06df218 c428fc10 c14e5e00 0063 
  GPR04: c0007fecaca0 c0007fedfb40 c168d278 4b78 
  GPR08: 0007 0001  0001 
  GPR12: c06de100 c7b81b00  2200 
  GPR16: 10170dc8 010020c60488 10140f58 100c7570 
  GPR20:  1017dd58 10153618 1017b608 
  GPR24: 3fffd5f377c4 0001 c13fe5d0 0004 
  GPR28: c13fe990 0063 c13b2590  
  [  202.680090] NIP [c06de134] sysrq_handle_crash+0x34/0x50
  [  202.680159] LR [c06df218] __handle_sysrq+0xe8/0x280
  [  202.680213] Call Trace:
  [  202.680246] [c428fc10] [c0e79720] 
_fw_tigon_tg3_bin_name+0x2f1a8/0x36f48 (unreliable)
  [  202.680356] [c428fc30] [c06df218] __handle_sysrq+0xe8/0x280
  [  202.680440] [c428fcd0] [c06df9c8] 
write_sysrq_trigger+0x78/0xa0
  [  202.680535] [c428fd00] [c03cf890] proc_reg_write+0xb0/0x110
  [  202.680618] [c428fd50] [c032b5dc] __vfs_write+0x6c/0xe0
  [  202.680702] [c428fd90] [c032cae4] vfs_write+0xd4/0x240
  [  202.680783] [c428fde0] [c032e7fc] SyS_write+0x6c/0x110
  [  202.680867] [c428fe30] [c0009584] system_call+0x38/0xec
  [  202.680948] Instruction dump:
  [  202.680991] 38427d00 7c0802a6 f8010010 f821ffe1 6000 6000 3d22001a 
3949d1e0 
  [  202.681133] 3921 912a 7c0004ac 3940 <992a> 38210020 
e8010010 7c0803a6 
  [  202.681276] ---[ end trace 3e9cbc319000fff4 ]---
  [  202.684658] 
  [  202.684718] Sending IPI to other CPUs
  [  202.686765] IPI complete
  I'm in purgatory
   -> smp_release_cpus()
  spinning_secondaries = 3
   <- smp_release_cpus()
  Linux ppc64le
  #19-Ubuntu SMP S[  242.661649] INFO: task swapper/0:1 blocked for more than 
120 seconds.
  [  242.661708]   Not tainted 4.8.0-

[Kernel-packages] [Bug 1591618] Re: [Feature] KBL - New device ID for Kabypoint(KbP)

[Robert Hooker]

** Changed in: intel
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1591618

Title:
  [Feature] KBL - New device ID for Kabypoint(KbP)

Status in intel:
  Fix Released
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
Status in linux source package in Zesty:
  Fix Released

Bug description:
  identify what new device IDs are required for Kabypoint (KBP): HS-
  UART,SPI, I2C, SMBUS,SPI-NOR,NPK,xHCI,usb device, SD

  Platform: Kabylake-S with Kabypoint PCH

  upstream schedule: 4.9

  X-HWE-Bug: Bug #1622469

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1591618/+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 1645928] Re: [Bug] (Purley) x86/hpet: Reduce HPET counter read contention

[Robert Hooker]

** Changed in: intel
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1645928

Title:
  [Bug] (Purley) x86/hpet: Reduce HPET counter read contention

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  Issue description:
  Boot ubuntu 16.10 and upstream v4.8 kernel on Purley, sometimes we saw 
following call trace:

  [8.740679] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0, 0, 0, 0, 0, 0^M
  [8.747701] hpet0: 8 comparators, 64-bit 24.00 MHz counter^M
  [   32.765648] NMI watchdog: BUG: soft lockup - CPU#129 stuck for 22s! 
[watchdog/129:913]^M
  [   32.779913] NMI watchdog: BUG: soft lockup - CPU#130 stuck for 22s! 
[swapper/130:0]^M
  [   32.779915] Modules linked in:^M
  [   32.779918] CPU: 130 PID: 0 Comm: swapper/130 Not tainted 
3.10.0-481.el7.x86_64 #1^M
  [   32.779919] Hardware name: Intel Corporation PURLEY/PURLEY, BIOS 
PLYDCRB1.86B.0095.D20.1607292025 07/29/2016^M
  [   32.779921] task: 8830b3fb3ec0 ti: 8801738e task.ti: 
8801738e^M
  [   32.779930] RIP: 0010:[]  [] 
native_safe_halt+0x6/0x10^M
  [   32.779932] RSP: :8801738e3e98  EFLAGS: 0286^M
  

  (All cpus are stuck and NMI dump resulting in a large amount of
  output.)

  Issue solution:
  v4.9 kernel has a commit to fix this issue, please backport it to 16.10:
  f99fd22 x86/hpet: Reduce HPET counter read contention

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1645928/+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 1659381] Re: linux: 4.8.0-37.39 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-updates
   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/1659381

Title:
  linux: 4.8.0-37.39 -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:
  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 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:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-37.39 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/1659381/+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 1659340] Re: Linux kernel 4.8 hangs at boot up

[kjellahl]

v4.8-rc7-201702011104 passed
v4.8.0-34.36-commit129766708reverted failed

For the first time my result is not the same as lotek's. I installed the same
4 packages. Do you think it's worthwhile to uninstall and then reinstall?
"dpkg -l" reports that there is also a linux-signed-image-4.8.0-34-generic
package. Can it spoil the test?

-- 
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/1659340

Title:
  Linux kernel 4.8 hangs at boot up

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot,
  Windows 10 and Ubuntu 16.10.

  Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45.
  When I try to start with any of the 4.8.0 kernels delivered with regular
  Ubuntu updates, they all hang after printing

Läser in Linux 4.8.0-34-generic ...
Läser in initial ramdisk ...

  Sorry for the partly Swedish text. I guess that the lines would start with
  "Loading" instead of "Läser in" on an English version.

  The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34
  and with -generic, -generic (upstart) and -generic (recovery mode).

  After a while the fan runs at full speed, as if the processor is working
  hard, but nothing happens.

  After I've tried in vain to start with Linux 4.8.0-xx, and then starts
  with 4.4.0-45, the following errors are usually printed:

  [  2.511733] usb 4-3: string descriptor 0 read error: -22
  [  3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight 
controller
  /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks
  [ 21.335117] usb 4-3: string descriptor 0 read error: -22

  When a successful start has not been immediately preceded by a failed start,
  only the line beginning "/dev/sda7" is printed.

  I have previously commented on bug #1635447. As recommended there, I've
  also tested with the upstream kernel 4.10-rc3. It worked just as bad as
  4.8.0.

  I tried to report this bug with 'ubuntu-bug linux' after I had booted with
  the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45-
  generic is not an official Ubuntu package.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kjell  2022 F pulseaudio
   /dev/snd/controlC1:  kjell  2022 F pulseaudio
   /dev/snd/controlC0:  kjell  2022 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb
  InstallationDate: Installed on 2013-09-25 (1218 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V5-551G
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.4.0-45-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/11/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Havok
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire V5-551G
  dmi.product.version: V2.14
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+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 1659340] Re: Linux kernel 4.8 hangs at boot up

[lotek]

4.8.0-34-generic #36~lp1659340Commit129766708Reverted  passed (!)

some comments:
I installed on "Lenovo 710S (KabyLake i5-7200)" these 4 packages only: OK?

linux-headers-4.8.0-34-generic_4.8.0-34.36~lp1659340Commit129766708Reverted_amd64.deb
linux-headers-4.8.0-34_4.8.0-34.36~lp1659340Commit129766708Reverted_all.deb
linux-image-4.8.0-34-generic_4.8.0-34.36~lp1659340Commit129766708Reverted_amd64.deb
linux-image-extra-4.8.0-34-generic_4.8.0-34.36~lp1659340Commit129766708Reverted_amd64.deb

during installation I got these 2 messages, but same as on all other kernel. 
missing intel-drivers...
W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915

-- 
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/1659340

Title:
  Linux kernel 4.8 hangs at boot up

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot,
  Windows 10 and Ubuntu 16.10.

  Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45.
  When I try to start with any of the 4.8.0 kernels delivered with regular
  Ubuntu updates, they all hang after printing

Läser in Linux 4.8.0-34-generic ...
Läser in initial ramdisk ...

  Sorry for the partly Swedish text. I guess that the lines would start with
  "Loading" instead of "Läser in" on an English version.

  The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34
  and with -generic, -generic (upstart) and -generic (recovery mode).

  After a while the fan runs at full speed, as if the processor is working
  hard, but nothing happens.

  After I've tried in vain to start with Linux 4.8.0-xx, and then starts
  with 4.4.0-45, the following errors are usually printed:

  [  2.511733] usb 4-3: string descriptor 0 read error: -22
  [  3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight 
controller
  /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks
  [ 21.335117] usb 4-3: string descriptor 0 read error: -22

  When a successful start has not been immediately preceded by a failed start,
  only the line beginning "/dev/sda7" is printed.

  I have previously commented on bug #1635447. As recommended there, I've
  also tested with the upstream kernel 4.10-rc3. It worked just as bad as
  4.8.0.

  I tried to report this bug with 'ubuntu-bug linux' after I had booted with
  the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45-
  generic is not an official Ubuntu package.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kjell  2022 F pulseaudio
   /dev/snd/controlC1:  kjell  2022 F pulseaudio
   /dev/snd/controlC0:  kjell  2022 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb
  InstallationDate: Installed on 2013-09-25 (1218 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V5-551G
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.4.0-45-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/11/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Havok
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire V5-551G
  dmi.product.version: V2.14
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kern

[Kernel-packages] [Bug 1555786] Re: [Hyper-V] VM with ubuntu 32bit with linux-next does not boot

[Joseph Salisbury]

** Also affects: linux (Ubuntu Zesty)
   Importance: Medium
 Assignee: Joseph Salisbury (jsalisbury)
   Status: In Progress

** Also affects: linux (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Yakkety)
   Status: New => In Progress

** Changed in: linux (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux (Ubuntu Yakkety)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

-- 
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/1555786

Title:
  [Hyper-V] VM with ubuntu 32bit with linux-next does not boot

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
Status in linux source package in Zesty:
  In Progress

Bug description:
  We identified that at least ubuntu (let's take 15.10) does not boot if
  installed in the 32bit architecture, and using the linux-next upstream
  kernel 4.5 on it. This has been seen on other distributions as well.

  We took both the official linux-next branch from kernel.org and the one from 
kernel.ubuntu.com v4.5-rc7.
  For the compilation process we went either with the 4.2 kernel config file 
from the installed running kernel, and also built the config separately. 
  No errors have been encountered during the build or install process of the 
4.5 kernel, however at boot, the VM will just hang.
  There are no call traces or messages at boot to show any pottential issue.

  Have you seen this on your end when testing the 32bit build?
  Attaching the full serial log for reference, however I don't see any errors 
in the kernel boot process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555786/+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 1248289] Re: Missing libunwind support in perf

[Jon Gjengset]

For what it's worth, recompiling `perf` from source fixes the problem.

-- 
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/1248289

Title:
  Missing libunwind support in perf

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:
  Hi,

  I'm trying to use perf's libunwind support in 13.04 with kernel
  3.11.0-12-generic on amd64.  Typically you can do this by using the
  "-g dwarf" flag, but it appears the perf command included in linux-
  tools-3.11.0-12-generic was not compiled with libunwind.  This may be
  as simple as the build machine didn't have libunwind installed.
  Having dwarf support in perf with default Ubuntu kernels would be very
  useful as it provides a way to get profiling information when
  -fomitframepointer is used.

  Relevant upstream code:

  https://github.com/torvalds/linux/blob/v3.11/tools/perf/Makefile#L459
  https://github.com/torvalds/linux/blob/v3.11/tools/perf/builtin-record.c#L758

  Let me know if I can provide any other information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248289/+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 1555786] Re: [Hyper-V] VM with ubuntu 32bit with linux-next does not boot

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1555786

Title:
  [Hyper-V] VM with ubuntu 32bit with linux-next does not boot

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
Status in linux source package in Zesty:
  In Progress

Bug description:
  We identified that at least ubuntu (let's take 15.10) does not boot if
  installed in the 32bit architecture, and using the linux-next upstream
  kernel 4.5 on it. This has been seen on other distributions as well.

  We took both the official linux-next branch from kernel.org and the one from 
kernel.ubuntu.com v4.5-rc7.
  For the compilation process we went either with the 4.2 kernel config file 
from the installed running kernel, and also built the config separately. 
  No errors have been encountered during the build or install process of the 
4.5 kernel, however at boot, the VM will just hang.
  There are no call traces or messages at boot to show any pottential issue.

  Have you seen this on your end when testing the 32bit build?
  Attaching the full serial log for reference, however I don't see any errors 
in the kernel boot process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555786/+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 1348890] Re: Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event

[Vasya Pupkin]

I can confirm that current drm-intel-next kernel fixes issue for UX301LA
as well.

-- 
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/1348890

Title:
  Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev
  event

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello Community,

  It seems brightness keys don't work with latest Ubuntu 14.04 LTS for
  laptop Asus Zenbook UX32LN.

  sudo dmidecode -s bios-version
  UX32LN.203

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1348890/+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 1555786] Re: [Hyper-V] VM with ubuntu 32bit with linux-next does not boot

[Joshua R. Poulson]

https://git.kernel.org/cgit/linux/kernel/git/next/linux-
next.git/commit/?id=68ab2d76e4be785a7003fdb42b7c4ed8bba56ae2

-- 
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/1555786

Title:
  [Hyper-V] VM with ubuntu 32bit with linux-next does not boot

Status in linux package in Ubuntu:
  Triaged

Bug description:
  We identified that at least ubuntu (let's take 15.10) does not boot if
  installed in the 32bit architecture, and using the linux-next upstream
  kernel 4.5 on it. This has been seen on other distributions as well.

  We took both the official linux-next branch from kernel.org and the one from 
kernel.ubuntu.com v4.5-rc7.
  For the compilation process we went either with the 4.2 kernel config file 
from the installed running kernel, and also built the config separately. 
  No errors have been encountered during the build or install process of the 
4.5 kernel, however at boot, the VM will just hang.
  There are no call traces or messages at boot to show any pottential issue.

  Have you seen this on your end when testing the 32bit build?
  Attaching the full serial log for reference, however I don't see any errors 
in the kernel boot process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555786/+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 1659340] Re: Linux kernel 4.8 hangs at boot up

[Joseph Salisbury]

The bisect reported the following as the first bad commit:

commit 1297667083d5442aafe3e337b9413bf02b114edb
Author: Matt Fleming 
Date:   Mon Sep 19 13:09:09 2016 +0100

x86/efi: Only map RAM into EFI page tables if in mixed-mode


I built a yakkety test kernel with this commit reverted.  The test kernel can 
be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1659340/

Can you test that kernel and report back if it has the bug or not?


Note, with this test kernel you need to install both the linux-image and 
linux-image-extra .deb packages.

-- 
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/1659340

Title:
  Linux kernel 4.8 hangs at boot up

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot,
  Windows 10 and Ubuntu 16.10.

  Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45.
  When I try to start with any of the 4.8.0 kernels delivered with regular
  Ubuntu updates, they all hang after printing

Läser in Linux 4.8.0-34-generic ...
Läser in initial ramdisk ...

  Sorry for the partly Swedish text. I guess that the lines would start with
  "Loading" instead of "Läser in" on an English version.

  The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34
  and with -generic, -generic (upstart) and -generic (recovery mode).

  After a while the fan runs at full speed, as if the processor is working
  hard, but nothing happens.

  After I've tried in vain to start with Linux 4.8.0-xx, and then starts
  with 4.4.0-45, the following errors are usually printed:

  [  2.511733] usb 4-3: string descriptor 0 read error: -22
  [  3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight 
controller
  /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks
  [ 21.335117] usb 4-3: string descriptor 0 read error: -22

  When a successful start has not been immediately preceded by a failed start,
  only the line beginning "/dev/sda7" is printed.

  I have previously commented on bug #1635447. As recommended there, I've
  also tested with the upstream kernel 4.10-rc3. It worked just as bad as
  4.8.0.

  I tried to report this bug with 'ubuntu-bug linux' after I had booted with
  the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45-
  generic is not an official Ubuntu package.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kjell  2022 F pulseaudio
   /dev/snd/controlC1:  kjell  2022 F pulseaudio
   /dev/snd/controlC0:  kjell  2022 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb
  InstallationDate: Installed on 2013-09-25 (1218 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V5-551G
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.4.0-45-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/11/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Havok
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire V5-551G
  dmi.product.version: V2.14
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+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 1650058] Re: [Hyper-V/Azure] Please include Mellanox OFED drivers in Azure kernel and image

[Joshua R. Poulson]

Mellanox assures us that all the ConnectX3 drivers are upstream now, so
I will switch focus on the kernel side to integrating those once I have
the commits. DPDK however has userspace which come from this repo:
http://linux.mellanox.com/public/repo/mlnx_rdma_minimal/3.4-2.0.5.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/1650058

Title:
  [Hyper-V/Azure] Please include Mellanox OFED drivers in Azure kernel
  and image

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  In order to have the correct VF driver to support SR-IOV in Azure, the
  Mellanox OFED distribution needs to be included in the kernel and the
  image. Mellanox's drivers are not upstream, but they are available
  from here:

  
https://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers&ssn=3nnhohirh5htv6dnp1uk7tf487

  While this configuration is not explicitly listed as supported in the
  release notes, Microsoft and Mellanox engineers are working on the
  corresponding Windows Server 2016 PF driver to support this VF driver
  in operation in Ubuntu guests.

  I file file a corresponding rebase request to pick up the PCI
  passthrough and other SR-IOV work done for the Hyper-V capabilities in
  the upstream 4.9 kernel.

  Only 64-bit support for Ubuntu 16.04's HWE kernel is needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650058/+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 1248289] Re: Missing libunwind support in perf

[Jon Gjengset]

In fact, on Yakkety with 4.8.0-34, the results of running perf --call-
graph are even more bizarre:

$ perf record --call-graph dwarf sleep 1
Error:
The sys_perf_event_open() syscall returned with 22 (Invalid argument) for event 
(cycles).
/bin/dmesg may provide additional information.
No CONFIG_PERF_EVENTS=y kernel support configured?
$ grep -i config_perf_events /boot/config-$(uname -r)
CONFIG_PERF_EVENTS=y
CONFIG_PERF_EVENTS_INTEL_UNCORE=y
CONFIG_PERF_EVENTS_INTEL_RAPL=m
CONFIG_PERF_EVENTS_INTEL_CSTATE=m
# CONFIG_PERF_EVENTS_AMD_POWER is not set

-- 
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/1248289

Title:
  Missing libunwind support in perf

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:
  Hi,

  I'm trying to use perf's libunwind support in 13.04 with kernel
  3.11.0-12-generic on amd64.  Typically you can do this by using the
  "-g dwarf" flag, but it appears the perf command included in linux-
  tools-3.11.0-12-generic was not compiled with libunwind.  This may be
  as simple as the build machine didn't have libunwind installed.
  Having dwarf support in perf with default Ubuntu kernels would be very
  useful as it provides a way to get profiling information when
  -fomitframepointer is used.

  Relevant upstream code:

  https://github.com/torvalds/linux/blob/v3.11/tools/perf/Makefile#L459
  https://github.com/torvalds/linux/blob/v3.11/tools/perf/builtin-record.c#L758

  Let me know if I can provide any other information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248289/+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 1384955] Re: support compressed kernels on arm64

[dann frazier]

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Andy Whitcroft (apw)

** Also affects: linux-hwe-edge (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: linux (Ubuntu Xenial)

** Changed in: linux-hwe-edge (Ubuntu Xenial)
 Assignee: (unassigned) => Andy Whitcroft (apw)

** Changed in: flash-kernel (Ubuntu Xenial)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: flash-kernel (Ubuntu Xenial)
   Status: Triaged => In Progress

** Description changed:

- When building an upstream kernel using "make deb-pkg" and not any of the
- Ubuntu-specific kernel build methods (such as debian/rules binary-
- headers binary-generic), the resulting linux-image deb package includes
- a gzip-compressed kernel image (copied from Image.gz, not Image). When
- such a deb package is installed on an arm64 system (such as McDivitt)
- and flash-kernel is run, it always calls "mkimage" with "-C none", which
- results in a uImage that can't boot.
+ [Impact]
+ Ubuntu kernels >= hwe-y (4.8) will no longer boot on xgene/uboot systems. The 
image size appears to have outgrown the defined firmware region, and u-boot 
will error out with a checksum mismatch error. A solution for this is to start 
shipping a compressed kernel (Image.gz target). flash-kernel needs updating to 
detect a compressed kernel and set the appropriate uImage compression flag. 
Similarly, d-i needs updating because it does it's own uImage generation.
  
- The attached patch adds a check to the mkimage_kernel() function in
- /usr/share/flash-kernel/functions to determine whether the kernel image
- is gzip-compressed or not, and calls "mkimage" with the appropriate "-C
- gzip" or "-C none" option. I have tested this patch on McDivitt, with
- both standard Ubuntu 3.13.0-37 and upstream 3.18-rc1 kernels, and it
- works for me.
+ [Test Case]
+ Boot an hwe-y kernel on an xgene/uboot system (APM Mustang, HP ProLiant m400).
+ 
+ [Regression Risk]
+ The necessary code is in place and in-use for yakkety, and no issues have 
been discovered there. The SRU involves clean cherry-picks of that code for d-i 
& f-k. The kernel side needs to be modified to pull in the correct version of 
flash-kernel for xenial.

** Changed in: debian-installer (Ubuntu Xenial)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: debian-installer (Ubuntu Xenial)
   Status: Triaged => Fix Committed

** Changed in: debian-installer (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: debian-installer (Ubuntu)
   Importance: Undecided => High

** Changed in: flash-kernel (Ubuntu)
   Importance: Undecided => High

** Changed in: flash-kernel (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: flash-kernel (Ubuntu)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: debian-installer (Ubuntu)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** Changed in: linux-hwe-edge (Ubuntu Xenial)
   Importance: Undecided => High

-- 
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/1384955

Title:
  support compressed kernels on arm64

Status in debian-installer package in Ubuntu:
  Fix Released
Status in flash-kernel package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-edge package in Ubuntu:
  New
Status in debian-installer source package in Xenial:
  Fix Committed
Status in flash-kernel source package in Xenial:
  In Progress
Status in linux-hwe-edge source package in Xenial:
  New
Status in flash-kernel package in Debian:
  New

Bug description:
  [Impact]
  Ubuntu kernels >= hwe-y (4.8) will no longer boot on xgene/uboot systems. The 
image size appears to have outgrown the defined firmware region, and u-boot 
will error out with a checksum mismatch error. A solution for this is to start 
shipping a compressed kernel (Image.gz target). flash-kernel needs updating to 
detect a compressed kernel and set the appropriate uImage compression flag. 
Similarly, d-i needs updating because it does it's own uImage generation.

  [Test Case]
  Boot an hwe-y kernel on an xgene/uboot system (APM Mustang, HP ProLiant m400).

  [Regression Risk]
  The necessary code is in place and in-use for yakkety, and no issues have 
been discovered there. The SRU involves clean cherry-picks of that code for d-i 
& f-k. The kernel side needs to be modified to pull in the correct version of 
flash-kernel for xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1384955/+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 1660949] Re: No HDMI out on Asus UX51 running 16.10 or 16.04

[Nathan Willis]

That's not possible for me to do; sorry.

Is there a specific reason to think that the bug is fixed in 4.10?

-- 
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/1660949

Title:
  No HDMI out on Asus UX51 running 16.10 or 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 16.10 on an Asus UX51 laptop; i915+Nvidia dual graphics
  using the Nouveau driver.

  The machine has both VGA out and HDMI out; VGA works like a charm but
  HDMI is not even detected. Meaning that none of (xrandr, lspci, aplay,
  get-edid) even reports the HDMI port as present.

  It's not clear to me whether or not this is an X or a kernel issue at
  the heart of it.  I did, however, upgrade recently from 16.04 (where
  this bug was also present!) to see if that made any difference (which
  it did not) and I did try the proprietary Nvidia drivers (340 and 367)
  to see if either of them made a difference (which they did not).

  I can assure you that I've read every relevant-sounding bug report and
  askubuntu question from the past year on this topic without
  discovering any fixes.  Happy to try what needs to be tried.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660949/+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 1384955] Re: support compressed kernels on arm64

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-core-dev/debian-installer/xenial-proposed

-- 
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/1384955

Title:
  support compressed kernels on arm64

Status in debian-installer package in Ubuntu:
  Fix Released
Status in flash-kernel package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-edge package in Ubuntu:
  New
Status in debian-installer source package in Xenial:
  Fix Committed
Status in flash-kernel source package in Xenial:
  In Progress
Status in linux-hwe-edge source package in Xenial:
  New
Status in flash-kernel package in Debian:
  New

Bug description:
  [Impact]
  Ubuntu kernels >= hwe-y (4.8) will no longer boot on xgene/uboot systems. The 
image size appears to have outgrown the defined firmware region, and u-boot 
will error out with a checksum mismatch error. A solution for this is to start 
shipping a compressed kernel (Image.gz target). flash-kernel needs updating to 
detect a compressed kernel and set the appropriate uImage compression flag. 
Similarly, d-i needs updating because it does it's own uImage generation.

  [Test Case]
  Boot an hwe-y kernel on an xgene/uboot system (APM Mustang, HP ProLiant m400).

  [Regression Risk]
  The necessary code is in place and in-use for yakkety, and no issues have 
been discovered there. The SRU involves clean cherry-picks of that code for d-i 
& f-k. The kernel side needs to be modified to pull in the correct version of 
flash-kernel for xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1384955/+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 1626436] Re: [4.8 regression] boot has become very slow

[Dimitrij Mijoski]

I had slow boot with 16.10 few months ago. I moved back to 16.04. Today
I had time to test some of the kernels above from the bisection process.
These are the results

4.4.0-59-generic# Ubuntu 16.04 official January 2017
Startup finished in 4.889s (kernel) + 28.001s (userspace) = 32.890s

4.6.0-040600-generic# from comment 29 ... actually from #34
Startup finished in 5.274s (kernel) + 23.561s (userspace) = 28.836s

4.6.0-040600-generic# comment 36
Startup finished in 5.111s (kernel) + 25.192s (userspace) = 30.304s

4.6.0-040600rc1-generic # comment 54
Startup finished in 4.979s (kernel) + 21.904s (userspace) = 26.883s

4.8.0-26-generic# official Ubuntu 16.10 at November 2016
Startup finished in 15.025s (kernel) + 35.067s (userspace) = 50.093s

4.8.0-29-generic# comment 61
Startup finished in 14.808s (kernel) + 32.516s (userspace) = 47.325s
Startup finished in 15.674s (kernel) + 26.293s (userspace) = 41.967s

4.8.0-34-generic# Official 16.04 repo, apt install 
linux-generic-hwe-16.04-edge
Startup finished in 15.717s (kernel) + 26.583s (userspace) = 42.301s

Basically the two patches on my (old) laptop reduce the total boot from
50 to 40 something. Obviously there is another issue. On 4.8 kernels
(with or without the two patches) I get a short freeze of 1-2 secs when
I open a window of System Settings.

I'd suggest we should continue the bisection that Joseph Salisbury
started. We should continue after the kernel in comment 54 which is
GOOD.

-- 
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:
  In Progress
Status in linux source package in Yakkety:
  In Progress

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.4. 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.as

[Kernel-packages] [Bug 1661046] Status changed to Confirmed

[Brad Figg]

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/1661046

Title:
  ACPI cannot be activated on my MSI GE62 laptop.  acpi-ht already
  causes failure, so the hyperthreading is responsible.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am including what you suggest on
  https://wiki.ubuntu.com/DebuggingACPI

  WIth acpi off, the fan doesn't work at top capacity, and the trackpad
  doesn't work at all.

  I'm including the uname, lspci, and dmidecode.

  I am not including the /proc/acpi directory, as it doesn't exist at
  all.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  benjones   1849 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Feb  1 10:09:36 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=ad294c16-796f-449c-943b-a5f0f6dbb961
  InstallationDate: Installed on 2017-01-31 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Micro-Star International Co., Ltd. GE62 6QD
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=cf5aded0-f481-4da8-9b31-78b854cd2a66 ro acpi=off
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/29/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J5IMS.114
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.A
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16J5IMS.114:bd04/29/2016:svnMicro-StarInternationalCo.,Ltd.:pnGE626QD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J5:rvrREV0.A:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
  dmi.product.name: GE62 6QD
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661046/+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 1601954] Re: ensure all items are included in changelog and standardise packaging

[Thadeu Lima de Souza Cascardo]

** Changed in: linux-meta-raspi2 (Ubuntu Xenial)
   Status: Confirmed => Fix Committed

** Changed in: linux-meta-snapdragon (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Also affects: linux-meta-aws (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux-meta-aws (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux-meta-aws (Ubuntu Xenial)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1601954

Title:
  ensure all items are included in changelog and standardise packaging

Status in linux-meta package in Ubuntu:
  Fix Released
Status in linux-meta-aws package in Ubuntu:
  New
Status in linux-meta-lts-trusty package in Ubuntu:
  New
Status in linux-meta-lts-xenial package in Ubuntu:
  New
Status in linux-meta-raspi2 package in Ubuntu:
  New
Status in linux-meta-snapdragon package in Ubuntu:
  New
Status in linux-signed package in Ubuntu:
  Fix Released
Status in linux-meta source package in Precise:
  New
Status in linux-meta-aws source package in Precise:
  New
Status in linux-meta-lts-trusty source package in Precise:
  New
Status in linux-meta-lts-xenial source package in Precise:
  Invalid
Status in linux-meta-raspi2 source package in Precise:
  New
Status in linux-meta-snapdragon source package in Precise:
  New
Status in linux-signed source package in Precise:
  New
Status in linux-meta source package in Trusty:
  New
Status in linux-meta-aws source package in Trusty:
  New
Status in linux-meta-lts-trusty source package in Trusty:
  Invalid
Status in linux-meta-lts-xenial source package in Trusty:
  New
Status in linux-meta-raspi2 source package in Trusty:
  New
Status in linux-meta-snapdragon source package in Trusty:
  New
Status in linux-signed source package in Trusty:
  New
Status in linux-meta source package in Xenial:
  Fix Committed
Status in linux-meta-aws source package in Xenial:
  In Progress
Status in linux-meta-lts-trusty source package in Xenial:
  Invalid
Status in linux-meta-lts-xenial source package in Xenial:
  Invalid
Status in linux-meta-raspi2 source package in Xenial:
  Fix Committed
Status in linux-meta-snapdragon source package in Xenial:
  Fix Committed
Status in linux-signed source package in Xenial:
  New

Bug description:
  simplify packaging and ensure all items are included in changelog.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1601954/+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 1659340] Re: Linux kernel 4.8 hangs at boot up

[lotek]

4.8.0-040800rc7.201702011104  passed

-- 
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/1659340

Title:
  Linux kernel 4.8 hangs at boot up

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot,
  Windows 10 and Ubuntu 16.10.

  Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45.
  When I try to start with any of the 4.8.0 kernels delivered with regular
  Ubuntu updates, they all hang after printing

Läser in Linux 4.8.0-34-generic ...
Läser in initial ramdisk ...

  Sorry for the partly Swedish text. I guess that the lines would start with
  "Loading" instead of "Läser in" on an English version.

  The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34
  and with -generic, -generic (upstart) and -generic (recovery mode).

  After a while the fan runs at full speed, as if the processor is working
  hard, but nothing happens.

  After I've tried in vain to start with Linux 4.8.0-xx, and then starts
  with 4.4.0-45, the following errors are usually printed:

  [  2.511733] usb 4-3: string descriptor 0 read error: -22
  [  3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight 
controller
  /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks
  [ 21.335117] usb 4-3: string descriptor 0 read error: -22

  When a successful start has not been immediately preceded by a failed start,
  only the line beginning "/dev/sda7" is printed.

  I have previously commented on bug #1635447. As recommended there, I've
  also tested with the upstream kernel 4.10-rc3. It worked just as bad as
  4.8.0.

  I tried to report this bug with 'ubuntu-bug linux' after I had booted with
  the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45-
  generic is not an official Ubuntu package.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kjell  2022 F pulseaudio
   /dev/snd/controlC1:  kjell  2022 F pulseaudio
   /dev/snd/controlC0:  kjell  2022 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb
  InstallationDate: Installed on 2013-09-25 (1218 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V5-551G
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.4.0-45-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/11/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Havok
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire V5-551G
  dmi.product.version: V2.14
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+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 1661046] [NEW] ACPI cannot be activated on my MSI GE62 laptop. acpi-ht already causes failure, so the hyperthreading is responsible.

[Benjamin Jones]

Public bug reported:

I am including what you suggest on https://wiki.ubuntu.com/DebuggingACPI

WIth acpi off, the fan doesn't work at top capacity, and the trackpad
doesn't work at all.

I'm including the uname, lspci, and dmidecode.

I am not including the /proc/acpi directory, as it doesn't exist at all.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-59-generic 4.4.0-59.80
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  benjones   1849 F pulseaudio
CurrentDesktop: Unity
Date: Wed Feb  1 10:09:36 2017
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=ad294c16-796f-449c-943b-a5f0f6dbb961
InstallationDate: Installed on 2017-01-31 (1 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Micro-Star International Co., Ltd. GE62 6QD
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=cf5aded0-f481-4da8-9b31-78b854cd2a66 ro acpi=off
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-59-generic N/A
 linux-backports-modules-4.4.0-59-generic  N/A
 linux-firmware1.157.4
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/29/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16J5IMS.114
dmi.board.asset.tag: Default string
dmi.board.name: MS-16J5
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:0.A
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16J5IMS.114:bd04/29/2016:svnMicro-StarInternationalCo.,Ltd.:pnGE626QD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J5:rvrREV0.A:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
dmi.product.name: GE62 6QD
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug xenial

** Attachment added: "attachments.tar"
   
https://bugs.launchpad.net/bugs/1661046/+attachment/4811847/+files/attachments.tar

-- 
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/1661046

Title:
  ACPI cannot be activated on my MSI GE62 laptop.  acpi-ht already
  causes failure, so the hyperthreading is responsible.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am including what you suggest on
  https://wiki.ubuntu.com/DebuggingACPI

  WIth acpi off, the fan doesn't work at top capacity, and the trackpad
  doesn't work at all.

  I'm including the uname, lspci, and dmidecode.

  I am not including the /proc/acpi directory, as it doesn't exist at
  all.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  benjones   1849 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Feb  1 10:09:36 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=ad294c16-796f-449c-943b-a5f0f6dbb961
  InstallationDate: Installed on 2017-01-31 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Micro-Star International Co., Ltd. GE62 6QD
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=cf5aded0-f481-4da8-9b31-78b854cd2a66 ro acpi=off
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/29/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J5IMS.114
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.A
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16J5IMS.114:bd04/29/2016:svnMicro-StarInternationalCo.,Ltd.:pnGE626QD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J5:rvrREV0.A:c

[Kernel-packages] [Bug 1659621] Re: Random freezes and reboots since last kernel update

[luca]

Still happening after downgrading to libdrm2 2.4.60-2. :(

-- 
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/1659621

Title:
  Random freezes and reboots since last kernel update

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete

Bug description:
  I noticed my Laptop () started to freeze and reboot randomly and
  checking the apt logs the date where this started matches a kernel
  update:

  Start-Date: 2017-01-22  18:09:20
  Commandline: apt full-upgrade
  Requested-By: luca (1000)
  Install: linux-image-4.4.0-62-lowlatency:amd64 (4.4.0-62.83, automatic)
  Upgrade: linux-libc-dev:amd64 (4.4.0-59.80, 4.4.0-62.83), 
linux-image-lowlatency:amd64 (4.4.0.59.62, 4.4.0.62.65), libapt-inst2.0:amd64 
(1.2.18, 1.2.19), libsystemd0:amd64 (229-4ubuntu15, 229-4ubuntu16), 
libsystemd0:i386 (229-4ubuntu15, 229-4ubuntu16), apt:amd64 (1.2.18, 1.2.19), 
sudo:amd64 (1.8.16-0ubuntu1.2, 1.8.16-0ubuntu1.3), udev:amd64 (229-4ubuntu15, 
229-4ubuntu16), libapt-pkg5.0:amd64 (1.2.18, 1.2.19), libudev1:amd64 
(229-4ubuntu15, 229-4ubuntu16), libudev1:i386 (229-4ubuntu15, 229-4ubuntu16), 
docker-engine:amd64 (1.12.6-0~ubuntu-xenial, 1.13.0-0~ubuntu-xenial), 
firefox-locale-de:amd64 (50.1.0+build2-0ubuntu0.16.04.1, 
51.0+build2-0ubuntu0.16.04.1), systemd-sysv:amd64 (229-4ubuntu15, 
229-4ubuntu16), firefox-locale-en:amd64 (50.1.0+build2-0ubuntu0.16.04.1, 
51.0+build2-0ubuntu0.16.04.1), libpam-systemd:amd64 (229-4ubuntu15, 
229-4ubuntu16), systemd:amd64 (229-4ubuntu15, 229-4ubuntu16), 
mysql-common:amd64 (5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1), 
apt-utils:amd64 (1.2.18, 1.2.19), libmysqlclient20:i386 
(5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1), firefox:amd64 
(50.1.0+build2-0ubuntu0.16.04.1, 51.0+build2-0ubuntu0.16.04.1), 
apt-transport-https:amd64 (1.2.18, 1.2.19), linux-tools-common:amd64 
(4.4.0-59.80, 4.4.0-62.83)
  Purge: linux-image-4.4.0-57-lowlatency:amd64 (4.4.0-57.78)
  End-Date: 2017-01-22  18:10:27

  Looking at /var/log/kernel.log (attached fragment) I found a backtrace
  including the i915 module.

  
  Attached is the output from lspci and lshw. Let me know if you need anything 
else.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-62-lowlatency 4.4.0-62.83
  ProcVersionSignature: Ubuntu 4.4.0-62.83-lowlatency 4.4.40
  Uname: Linux 4.4.0-62-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   luca   2999 F...m pulseaudio
   /dev/snd/controlC1:  luca   2999 F pulseaudio
   /dev/snd/controlC0:  luca   2999 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Thu Jan 26 18:59:53 2017
  HibernationDevice: RESUME=UUID=841aac03-34a5-409e-a845-fdb0c6d7284a
  InstallationDate: Installed on 2015-11-12 (440 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 20DT001TGE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-lowlatency 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-lowlatency N/A
   linux-backports-modules-4.4.0-62-lowlatency  N/A
   linux-firmware   1.157.8
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-12-05 (52 days ago)
  dmi.bios.date: 08/19/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JDET54WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: Intel powered classmate PC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJDET54WW(1.16):bd08/19/2015:svnLENOVO:pn20DT001TGE:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20DT001TGE
  dmi.product.version: ThinkPad L450
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659621/+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 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Joseph Salisbury]

Correct, the v4.4-wily kernel is an upstream version of the kernel with
no Ubuntu customization.  That is the reason we need to go back in time
and test the older Ubuntu kernels to find the specific version when the
bug was introduced.  That will allow us to bisect and find the exact
commit that caused the regression.

Can you test test the 4.2.0-16.19 kernel:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/8099558

That is the earliest pre-built Xenial kernel, so if that kernel has the
bug, I'll have to build older versions.

-- 
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/1656605

Title:
  No server console display after Grub screen until fully booted and
  pressing Ctrl-Alt-F1/8

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Today I did our first production 14.04 to 16.04 LTS server upgrade. I
  had done so a couple of times successfully on test server machines.
  Upon booting up on the 16.04 system/kernel, after the Grub screen the
  server console screen is completely blank.

  Someone suggested using Ctrl-Alt-F1/8, and indeed pressing those
  hotkeys does toggle through the tty screens.

  There is no boot process logged to the server console screen.

  I did have the last 14.04 kernel yet installed, so selected that one
  from the Grub menu. Booting that 14.04 kernel, then server console
  display behaves normally.

  So I suspected perhaps a bum install of the 16.04 kernel. I used the
  following commands while booted to the 14.04 kernel to reinstall the
  16.04 kernel:

  $ sudo dpkg -P linux-image-4.4.0-59-generic 
linux-image-extra-4.4.0-59-generic linux-image-generic
  $ sudo apt-get install linux-image-generic

  Same results booting the 16.04 kernel after those steps.

  Hardware spec is an Intel Atom D945GCLF2D boxed motherboard with Intel
  Atom 330 Dual-Core processor and 2GB RAM. RAID is 3Ware SATA RAID.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+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 1661026] Re: Grub Menu Not Shown Alongside Win 10 in Kylin 17.04

[Joseph Salisbury]

** Package changed: linux (Ubuntu) => grub (Ubuntu)

** Changed in: grub (Ubuntu)
   Status: Confirmed => New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1661026

Title:
  Grub Menu Not Shown Alongside Win 10 in Kylin 17.04

Status in grub package in Ubuntu:
  New

Bug description:
  Was able to reproduce the bug a second time (see bug #1660558)
  1. Machine boots directly in Kylin with no Grub menu
  2. Was not ask to removed media (long lasting bug in Kylin)
  3. ISO was made with the new version of Rufus: 2.12.1054
  4. Machine is set English us
  4. Win ten is invisible
  5. To recover sda1 and sda2, must delete Grub with Win10 installer: 
bootrec.exe / fixmbr
  6. The 2 previous issues are gone: Don’t see the Firmware bug + do not boot 
in Try Ubuntu
  7. Did not do any updates yet nor troubleshooting
  8. Partitions scheme BIOS mode:

  Number  Start   End SizeType  File system Flags
   1  1049kB  525MB   524MB   primary   ntfsboot
   2  525MB   785GB   785GB   primary   ntfs
   3  785GB   786GB   256MB   primary   ext2
   4  786GB   1000GB  215GB   extended
   5  786GB   790GB   4095MB  logical   linux-swap(v1)
   6  790GB   814GB   24.6GB  logical   ext4
   7  814GB   1000GB  186GB   logical   ext4
  --- 
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zz 1601 F pulseaudio
   /dev/snd/controlC0:  zz 1601 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=f825d75e-e7fb-4eaa-a113-22c3249880ae
  InstallationDate: Installed on 2017-02-01 (0 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170130)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
   
   tun0  no wireless extensions.
  MachineType: HP 24-b019
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-12-generic 
root=UUID=c203e327-153e-408b-b8d8-ba3607d8b02b ro locale=zh_CN quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-12-generic N/A
   linux-backports-modules-4.9.0-12-generic  N/A
   linux-firmware1.162
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.9.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/25/2016
  dmi.bios.vendor: AMI
  dmi.bios.version: F.02
  dmi.board.asset.tag: 8CC6351M4W
  dmi.board.name: 81B8
  dmi.board.vendor: HP
  dmi.board.version: 0100
  dmi.chassis.asset.tag: 8CC6351M4W
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr:
  dmi.product.name: 24-b019
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub/+bug/1661026/+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 1659340] Re: Linux kernel 4.8 hangs at boot up

[Joseph Salisbury]

I built the next test kernel, up to the following commit:
e535ec0899d1fe52ec3a84c9bc03457ac67ad6f7

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1659340/e535ec0899d1fe52ec3a84c9bc03457ac67ad6f7

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

-- 
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/1659340

Title:
  Linux kernel 4.8 hangs at boot up

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot,
  Windows 10 and Ubuntu 16.10.

  Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45.
  When I try to start with any of the 4.8.0 kernels delivered with regular
  Ubuntu updates, they all hang after printing

Läser in Linux 4.8.0-34-generic ...
Läser in initial ramdisk ...

  Sorry for the partly Swedish text. I guess that the lines would start with
  "Loading" instead of "Läser in" on an English version.

  The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34
  and with -generic, -generic (upstart) and -generic (recovery mode).

  After a while the fan runs at full speed, as if the processor is working
  hard, but nothing happens.

  After I've tried in vain to start with Linux 4.8.0-xx, and then starts
  with 4.4.0-45, the following errors are usually printed:

  [  2.511733] usb 4-3: string descriptor 0 read error: -22
  [  3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight 
controller
  /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks
  [ 21.335117] usb 4-3: string descriptor 0 read error: -22

  When a successful start has not been immediately preceded by a failed start,
  only the line beginning "/dev/sda7" is printed.

  I have previously commented on bug #1635447. As recommended there, I've
  also tested with the upstream kernel 4.10-rc3. It worked just as bad as
  4.8.0.

  I tried to report this bug with 'ubuntu-bug linux' after I had booted with
  the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45-
  generic is not an official Ubuntu package.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kjell  2022 F pulseaudio
   /dev/snd/controlC1:  kjell  2022 F pulseaudio
   /dev/snd/controlC0:  kjell  2022 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb
  InstallationDate: Installed on 2013-09-25 (1218 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V5-551G
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.4.0-45-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/11/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Havok
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire V5-551G
  dmi.product.version: V2.14
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+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 1659111] Re: UbuntuKVM guest crashed while running I/O stress test with Ubuntu kernel 4.4.0-47-generic

[bugproxy]

** Tags removed: bugnameltc-149014 severity-critical

-- 
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/1659111

Title:
  UbuntuKVM guest crashed while running I/O stress test with Ubuntu
  kernel  4.4.0-47-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Attn. Canonical: For your awareness only at this time.

  == Comment: #0 - LEKSHMI C. PILLAI  - 2016-11-22 03:49:38 ==

  Machine INFO

  KVM HOST: luckyv1

  Guest :lucky05

  lucky05 crashed while running the I/O stress test for SAN disks.

  Installed lucky05 and enabled the xmon on that.After that started the
  RAW disk test on around 50 disks.After 6-7 hours after running,Now
  machine dropped into xmon.

  Logs:
  [25023.224182] Unable to handle kernel paging request for data at address 
0x
  [25023.224257] Faulting instruction address: 0xc0324c60
  cpu 0x3: Vector: 300 (Data Access) at [c000fffc3620]
  pc: c0324c60: locked_inode_to_wb_and_lock_list+0x50/0x290
  lr: c032831c: writeback_sb_inodes+0x30c/0x590
  sp: c000fffc38a0
 msr: 80019033
 dar: 0
   dsisr: 4000
current = 0xc000ff99e470
paca= 0xcfb41c80   softe: 0irq_happened: 0x01
  pid   = 14736, comm = kworker/u16:8
  enter ? for help
  [c000fffc3900] c032831c writeback_sb_inodes+0x30c/0x590
  [c000fffc3a10] c0328684 __writeback_inodes_wb+0xe4/0x150
  [c000fffc3a70] c0328aec wb_writeback+0x30c/0x450
  [c000fffc3b40] c03296b4 wb_workfn+0x264/0x570
  [c000fffc3c50] c00dd930 process_one_work+0x1e0/0x5a0
  [c000fffc3ce0] c00dde84 worker_thread+0x194/0x680
  [c000fffc3d80] c00e6980 kthread+0x110/0x130
  [c000fffc3e30] c0009538 ret_from_kernel_thread+0x5c/0xa4
  3:mon> f
  3:mon> th
  [c000fffc3900] c032831c writeback_sb_inodes+0x30c/0x590
  [c000fffc3a10] c0328684 __writeback_inodes_wb+0xe4/0x150
  [c000fffc3a70] c0328aec wb_writeback+0x30c/0x450
  [c000fffc3b40] c03296b4 wb_workfn+0x264/0x570
  [c000fffc3c50] c00dd930 process_one_work+0x1e0/0x5a0
  [c000fffc3ce0] c00dde84 worker_thread+0x194/0x680
  [c000fffc3d80] c00e6980 kthread+0x110/0x130
  [c000fffc3e30] c0009538 ret_from_kernel_thread+0x5c/0xa4 
  3:mon> sh
  [27384.651055] INFO: rcu_sched detected stalls on CPUs/tasks:
  [27384.651220]  (detected by 4, t=40598 jiffies, g=2849830, c=2849829, q=992)
  [27384.651286] All QSes seen, last rcu_sched kthread activity 40596 
(4301188714-4301148118), jiffies_till_next_fqs=1, root ->qsmask 0x0
  [27384.651501] rcu_sched kthread starved for 40596 jiffies! g2849830 c2849829 
f0x2 s3 ->state=0x0
  [27384.651747] INFO: rcu_sched detected stalls on CPUs/tasks:
  [27384.651905]  (detected by 4, t=590354 jiffies, g=2849830, c=2849829, 
q=1285)
  [27384.652012] All QSes seen, last rcu_sched kthread activity 590352 
(4301738470-4301148118), jiffies_till_next_fqs=1, root ->qsmask 0x0
  [27384.652191] rcu_sched kthread starved for 590352 jiffies! g2849830 
c2849829 f0x2 s3 ->state=0x0
  [27384.730645] Unable to handle kernel paging request for data at address 
0xffd8
  [27384.730781] Faulting instruction address: 0xc00e7258
  cpu 0x3: Vector: 300 (Data Access) at [c000fffc3000]
  pc: c00e7258: kthread_data+0x28/0x40
  lr: c00de940: wq_worker_sleeping+0x30/0x110
  sp: c000fffc3280
 msr: 80019033
 dar: ffd8
   dsisr: 4000
current = 0xc000ff99e470
paca= 0xcfb41c80   softe: 0irq_happened: 0x01
  pid   = 14736, comm = kworker/u16:8
  enter ? for help

  == Comment: #1 - LEKSHMI C. PILLAI - 2016-11-22 04:05:41 ==
  3:mon> th
  [c000fffc32b0] c00de940 wq_worker_sleeping+0x30/0x110
  [c000fffc32f0] c0af31bc __schedule+0x6ec/0x990
  [c000fffc33c0] c0af34a8 schedule+0x48/0xc0
  [c000fffc33f0] c00bd3d0 do_exit+0x760/0xc30
  [c000fffc34b0] c0020bf4 die+0x314/0x470
  [c000fffc3540] c0050d98 bad_page_fault+0xd8/0x150
  [c000fffc35b0] c0008680 handle_page_fault+0x2c/0x30
  --- Exception: 300 (Data Access) at c0324c60 
locked_inode_to_wb_and_lock_list+0x50/0x290
  [c000fffc3900] c032831c writeback_sb_inodes+0x30c/0x590
  [c000fffc3a10] c0328684 __writeback_inodes_wb+0xe4/0x150
  [c000fffc3a70] c0328aec wb_writeback+0x30c/0x450
  [c000fffc3b40] c03296b4 wb_workfn+0x264/0x570
  [c000fffc3c50] c00dd930 process_one_work+0x1e0/0x5a0
  [c000fffc3ce0] c00dde84 worker_thread+0x194/0x680
  [c000fffc3d80] c00e6980 kthread+0x110/0x130
  [c000fffc3e30] c0009538 ret_from_kernel_thread+0

[Kernel-packages] [Bug 1658625] Re: linux i386 ADT apparmor self-tests OOM machine with linux-4.9.0-12.13

[Colin Ian King]

Thanks John. I've tested this and it's not breaking now so that's a win.
However, I'm seeing the aa tests breaking, I've filed a new bug for
this, bug 1661030

-- 
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/1658625

Title:
  linux i386 ADT apparmor self-tests OOM machine with linux-4.9.0-12.13

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Seems we are getting into an OOM situation when running ADT testing.
  This looks to be in the apparmor tests:

09:57:14 ERROR| [stderr] Run kernel regression tests from 14.04's 
apparmor_2.8.95~2430-0ubuntu5.3 ... ok
09:57:14 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites)
09:57:20 DEBUG| [stdout] (skipped: This test is only for 14.04 systems with 
the apparmor 2.10.95 SRU or newer installed) (skipped: This test is only for 
14.04 systems with the apparmor 2.10.95 SRU or newer installed)
10:15:45 ERROR| [stderr] Run parser regression tests ... ok
10:15:46 ERROR| [stderr] test_regression_testsuite 
(__main__.ApparmorTestsuites)
10:15:48 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.2.dsc... done
10:15:48 DEBUG| [stdout]
Killed

  Console:

  autopkgtest login: [ 2838.328079] AppArmor: change_hat: Invalid input 
'^open'[ 2838.334310] AppArmor: change_hat: Invalid input '^'
  [ 2838.341460] AppArmor: change_hat: Invalid input, NULL hat and NULL magic[ 
2838.349735] AppArmor: change_hat: Invalid input, NULL hat and NULL magic[ 
2838.357374]
  AppArmor: change_hat: Invalid input '^open'
  AppArmor: change_hat: Invalid input '^'[ 2838.359310] AppArmor: change_hat: 
Invalid input '^'
  [ 2955.837326] Out of memory: Kill process 1554 (rsyslogd) score 6 or 
sacrifice child
  [ 2955.840293] Killed process 1554 (rsyslogd) total-vm:91072kB, 
anon-rss:52204kB, file-rss:2356kB, shmem-rss:0kB
  [ 3012.314564] Out of memory: Kill process 13148 (autotest-local) score 1 or 
sacrifice child
  [ 3012.315622] Killed process 24345 (autotest-local) total-vm:18040kB, 
anon-rss:7280kB, file-rss:3544kB, shmem-rss:0kB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658625/+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 1651454] Re: [Lenovo Thinkpad T460p] Ultra Dock external displays not detected after suspend/resume cycle

[Donjan Rodic]

Upgraded the kernel through the standard channels:
$ uname -a
Linux talas 4.8.0-34-generic #36-Ubuntu SMP Wed Dec 21 17:24:18 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux

The original problem seems fixed, it exhibits practically the same behaviour as 
with 4.9.
Docking lights up the monitors, I still have to 'killall unity-settings-daemon' 
to load the configured monitor settings (order and rotation).
I also had X crash to login on two occasions when suspend->dock->resume, but 
this is not reliably reproducible (works most of the time, will report when it 
happens again) and never when docking while awake.

If this is considered as fix released, I shall file a bug with unity-
settings-daemon about the config reload.

-- 
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/1651454

Title:
  [Lenovo Thinkpad T460p] Ultra Dock external displays not detected
  after suspend/resume cycle

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The bug is identical to the expired
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568573 where a
  new report was requested.

  This time around with a fresh install of 16.10 amd64 on a Thinkpad
  T460p and a Lenovo Ultra Dock with two external monitors.

  The setup does work when freshly booting with the laptop on the dock. 
Suspending undocked, docking, resuming doesn't light up the external monitors. 
Neither does just docking awake.
  The relevant error messages seem to be these:

  Dec 20 13:21:50 talas kernel: [265391.482117] 
[drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage 
retries, give up
  Dec 20 13:21:50 talas kernel: [265391.498583] [drm:intel_wait_ddi_buf_idle 
[i915]] *ERROR* Timeout waiting for DDI BUF D idle bit

  Other relevant bug reports might be:
  https://bugzilla.redhat.com/show_bug.cgi?id=1316877
  https://bbs.archlinux.org/viewtopic.php?id=209791

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-30-generic 4.8.0-30.32
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  donjan 2341 F pulseaudio
   /dev/snd/pcmC1D0p:   donjan 2341 F...m pulseaudio
   /dev/snd/controlC1:  donjan 2341 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Tue Dec 20 15:36:08 2016
  InstallationDate: Installed on 2016-10-25 (56 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 20FXS0Y200
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=104820cc-7d87-46d1-a1aa-e650ff221603 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-30-generic N/A
   linux-backports-modules-4.8.0-30-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET71W (2.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FXS0Y200
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET71W(2.11):bd09/26/2016:svnLENOVO:pn20FXS0Y200:pvrThinkPadT460p:rvnLENOVO:rn20FXS0Y200:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FXS0Y200
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651454/+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 1660829] Re: Undefined func on include/linux/huge_mm.h

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1660829

Title:
  Undefined func on include/linux/huge_mm.h

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Functions from mm/huge_memory.c is exported with include/linux/huge_mm.h 
header but only when
   context CONFIG_TRANSPARENT_HUGEPAGE is defined , when 
CONFIG_TRANSPARENT_HUGEPAGE is not set 
  missing errors from compiler i expect this on include/linux/huge_mm.h bellow:

  #ifdef CONFIG_TRANSPARENT_HUGEPAGE
  extern int copy_huge_pmd(struct mm_struct *dst_mm, struct mm_struct *src_mm,
   pmd_t *dst_pmd, pmd_t *src_pmd, unsigned long addr,
   struct vm_area_struct *vma);
  #else
  static inline int copy_huge_pmd(struct mm_struct *dst_mm, struct mm_struct 
*src_mm,
   pmd_t *dst_pmd, pmd_t *src_pmd, unsigned long addr,
   struct vm_area_struct *vma)
  {
  return 1;
  }
  #endif
  Ensuring to exist defined function when  CONFIG_TRANSPARENT_HUGEPAGE is not 
set.
  On this momment errors message from compiler is suppressed when 
CONFIG_TRANSPARENT_HUGEPAGE is not set.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asu3544 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Feb  1 00:08:47 2017
  InstallationDate: Installed on 2016-04-29 (277 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: Olidata S.p.A. ALABAMA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic 
root=/dev/mapper/192--168--0--108--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: S0101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: ALABAMA
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: Olidata S.p.A.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660829/+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 1660949] Re: No HDMI out on Asus UX51 running 16.10 or 16.04

[Joseph Salisbury]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.10 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc6

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Tags added: kernel-da-key

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1660949

Title:
  No HDMI out on Asus UX51 running 16.10 or 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 16.10 on an Asus UX51 laptop; i915+Nvidia dual graphics
  using the Nouveau driver.

  The machine has both VGA out and HDMI out; VGA works like a charm but
  HDMI is not even detected. Meaning that none of (xrandr, lspci, aplay,
  get-edid) even reports the HDMI port as present.

  It's not clear to me whether or not this is an X or a kernel issue at
  the heart of it.  I did, however, upgrade recently from 16.04 (where
  this bug was also present!) to see if that made any difference (which
  it did not) and I did try the proprietary Nvidia drivers (340 and 367)
  to see if either of them made a difference (which they did not).

  I can assure you that I've read every relevant-sounding bug report and
  askubuntu question from the past year on this topic without
  discovering any fixes.  Happy to try what needs to be tried.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660949/+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 1661026] UdevDb.txt

[Mikemecanic]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1661026/+attachment/4811801/+files/UdevDb.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/1661026

Title:
  Grub Menu Not Shown Alongside Win 10 in Kylin 17.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Was able to reproduce the bug a second time (see bug #1660558)
  1. Machine boots directly in Kylin with no Grub menu
  2. Was not ask to removed media (long lasting bug in Kylin)
  3. ISO was made with the new version of Rufus: 2.12.1054
  4. Machine is set English us
  4. Win ten is invisible
  5. To recover sda1 and sda2, must delete Grub with Win10 installer: 
bootrec.exe / fixmbr
  6. The 2 previous issues are gone: Don’t see the Firmware bug + do not boot 
in Try Ubuntu
  7. Did not do any updates yet nor troubleshooting
  8. Partitions scheme BIOS mode:

  Number  Start   End SizeType  File system Flags
   1  1049kB  525MB   524MB   primary   ntfsboot
   2  525MB   785GB   785GB   primary   ntfs
   3  785GB   786GB   256MB   primary   ext2
   4  786GB   1000GB  215GB   extended
   5  786GB   790GB   4095MB  logical   linux-swap(v1)
   6  790GB   814GB   24.6GB  logical   ext4
   7  814GB   1000GB  186GB   logical   ext4
  --- 
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zz 1601 F pulseaudio
   /dev/snd/controlC0:  zz 1601 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=f825d75e-e7fb-4eaa-a113-22c3249880ae
  InstallationDate: Installed on 2017-02-01 (0 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170130)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
   
   tun0  no wireless extensions.
  MachineType: HP 24-b019
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-12-generic 
root=UUID=c203e327-153e-408b-b8d8-ba3607d8b02b ro locale=zh_CN quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-12-generic N/A
   linux-backports-modules-4.9.0-12-generic  N/A
   linux-firmware1.162
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.9.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/25/2016
  dmi.bios.vendor: AMI
  dmi.bios.version: F.02
  dmi.board.asset.tag: 8CC6351M4W
  dmi.board.name: 81B8
  dmi.board.vendor: HP
  dmi.board.version: 0100
  dmi.chassis.asset.tag: 8CC6351M4W
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr:
  dmi.product.name: 24-b019
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661026/+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 1661026] CurrentDmesg.txt

[Mikemecanic]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1661026/+attachment/4811792/+files/CurrentDmesg.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/1661026

Title:
  Grub Menu Not Shown Alongside Win 10 in Kylin 17.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Was able to reproduce the bug a second time (see bug #1660558)
  1. Machine boots directly in Kylin with no Grub menu
  2. Was not ask to removed media (long lasting bug in Kylin)
  3. ISO was made with the new version of Rufus: 2.12.1054
  4. Machine is set English us
  4. Win ten is invisible
  5. To recover sda1 and sda2, must delete Grub with Win10 installer: 
bootrec.exe / fixmbr
  6. The 2 previous issues are gone: Don’t see the Firmware bug + do not boot 
in Try Ubuntu
  7. Did not do any updates yet nor troubleshooting
  8. Partitions scheme BIOS mode:

  Number  Start   End SizeType  File system Flags
   1  1049kB  525MB   524MB   primary   ntfsboot
   2  525MB   785GB   785GB   primary   ntfs
   3  785GB   786GB   256MB   primary   ext2
   4  786GB   1000GB  215GB   extended
   5  786GB   790GB   4095MB  logical   linux-swap(v1)
   6  790GB   814GB   24.6GB  logical   ext4
   7  814GB   1000GB  186GB   logical   ext4
  --- 
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zz 1601 F pulseaudio
   /dev/snd/controlC0:  zz 1601 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=f825d75e-e7fb-4eaa-a113-22c3249880ae
  InstallationDate: Installed on 2017-02-01 (0 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170130)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
   
   tun0  no wireless extensions.
  MachineType: HP 24-b019
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-12-generic 
root=UUID=c203e327-153e-408b-b8d8-ba3607d8b02b ro locale=zh_CN quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-12-generic N/A
   linux-backports-modules-4.9.0-12-generic  N/A
   linux-firmware1.162
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.9.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/25/2016
  dmi.bios.vendor: AMI
  dmi.bios.version: F.02
  dmi.board.asset.tag: 8CC6351M4W
  dmi.board.name: 81B8
  dmi.board.vendor: HP
  dmi.board.version: 0100
  dmi.chassis.asset.tag: 8CC6351M4W
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr:
  dmi.product.name: 24-b019
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661026/+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 1661026] JournalErrors.txt

[Mikemecanic]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1661026/+attachment/4811793/+files/JournalErrors.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/1661026

Title:
  Grub Menu Not Shown Alongside Win 10 in Kylin 17.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Was able to reproduce the bug a second time (see bug #1660558)
  1. Machine boots directly in Kylin with no Grub menu
  2. Was not ask to removed media (long lasting bug in Kylin)
  3. ISO was made with the new version of Rufus: 2.12.1054
  4. Machine is set English us
  4. Win ten is invisible
  5. To recover sda1 and sda2, must delete Grub with Win10 installer: 
bootrec.exe / fixmbr
  6. The 2 previous issues are gone: Don’t see the Firmware bug + do not boot 
in Try Ubuntu
  7. Did not do any updates yet nor troubleshooting
  8. Partitions scheme BIOS mode:

  Number  Start   End SizeType  File system Flags
   1  1049kB  525MB   524MB   primary   ntfsboot
   2  525MB   785GB   785GB   primary   ntfs
   3  785GB   786GB   256MB   primary   ext2
   4  786GB   1000GB  215GB   extended
   5  786GB   790GB   4095MB  logical   linux-swap(v1)
   6  790GB   814GB   24.6GB  logical   ext4
   7  814GB   1000GB  186GB   logical   ext4
  --- 
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zz 1601 F pulseaudio
   /dev/snd/controlC0:  zz 1601 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=f825d75e-e7fb-4eaa-a113-22c3249880ae
  InstallationDate: Installed on 2017-02-01 (0 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170130)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
   
   tun0  no wireless extensions.
  MachineType: HP 24-b019
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-12-generic 
root=UUID=c203e327-153e-408b-b8d8-ba3607d8b02b ro locale=zh_CN quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-12-generic N/A
   linux-backports-modules-4.9.0-12-generic  N/A
   linux-firmware1.162
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.9.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/25/2016
  dmi.bios.vendor: AMI
  dmi.bios.version: F.02
  dmi.board.asset.tag: 8CC6351M4W
  dmi.board.name: 81B8
  dmi.board.vendor: HP
  dmi.board.version: 0100
  dmi.chassis.asset.tag: 8CC6351M4W
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr:
  dmi.product.name: 24-b019
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661026/+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 1661026] CRDA.txt

[Mikemecanic]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1661026/+attachment/4811791/+files/CRDA.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1661026

Title:
  Grub Menu Not Shown Alongside Win 10 in Kylin 17.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Was able to reproduce the bug a second time (see bug #1660558)
  1. Machine boots directly in Kylin with no Grub menu
  2. Was not ask to removed media (long lasting bug in Kylin)
  3. ISO was made with the new version of Rufus: 2.12.1054
  4. Machine is set English us
  4. Win ten is invisible
  5. To recover sda1 and sda2, must delete Grub with Win10 installer: 
bootrec.exe / fixmbr
  6. The 2 previous issues are gone: Don’t see the Firmware bug + do not boot 
in Try Ubuntu
  7. Did not do any updates yet nor troubleshooting
  8. Partitions scheme BIOS mode:

  Number  Start   End SizeType  File system Flags
   1  1049kB  525MB   524MB   primary   ntfsboot
   2  525MB   785GB   785GB   primary   ntfs
   3  785GB   786GB   256MB   primary   ext2
   4  786GB   1000GB  215GB   extended
   5  786GB   790GB   4095MB  logical   linux-swap(v1)
   6  790GB   814GB   24.6GB  logical   ext4
   7  814GB   1000GB  186GB   logical   ext4
  --- 
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zz 1601 F pulseaudio
   /dev/snd/controlC0:  zz 1601 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=f825d75e-e7fb-4eaa-a113-22c3249880ae
  InstallationDate: Installed on 2017-02-01 (0 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170130)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
   
   tun0  no wireless extensions.
  MachineType: HP 24-b019
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-12-generic 
root=UUID=c203e327-153e-408b-b8d8-ba3607d8b02b ro locale=zh_CN quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-12-generic N/A
   linux-backports-modules-4.9.0-12-generic  N/A
   linux-firmware1.162
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.9.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/25/2016
  dmi.bios.vendor: AMI
  dmi.bios.version: F.02
  dmi.board.asset.tag: 8CC6351M4W
  dmi.board.name: 81B8
  dmi.board.vendor: HP
  dmi.board.version: 0100
  dmi.chassis.asset.tag: 8CC6351M4W
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr:
  dmi.product.name: 24-b019
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661026/+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 1661026] Status changed to Confirmed

[Brad Figg]

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/1661026

Title:
  Grub Menu Not Shown Alongside Win 10 in Kylin 17.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Was able to reproduce the bug a second time (see bug #1660558)
  1. Machine boots directly in Kylin with no Grub menu
  2. Was not ask to removed media (long lasting bug in Kylin)
  3. ISO was made with the new version of Rufus: 2.12.1054
  4. Machine is set English us
  4. Win ten is invisible
  5. To recover sda1 and sda2, must delete Grub with Win10 installer: 
bootrec.exe / fixmbr
  6. The 2 previous issues are gone: Don’t see the Firmware bug + do not boot 
in Try Ubuntu
  7. Did not do any updates yet nor troubleshooting
  8. Partitions scheme BIOS mode:

  Number  Start   End SizeType  File system Flags
   1  1049kB  525MB   524MB   primary   ntfsboot
   2  525MB   785GB   785GB   primary   ntfs
   3  785GB   786GB   256MB   primary   ext2
   4  786GB   1000GB  215GB   extended
   5  786GB   790GB   4095MB  logical   linux-swap(v1)
   6  790GB   814GB   24.6GB  logical   ext4
   7  814GB   1000GB  186GB   logical   ext4
  --- 
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zz 1601 F pulseaudio
   /dev/snd/controlC0:  zz 1601 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=f825d75e-e7fb-4eaa-a113-22c3249880ae
  InstallationDate: Installed on 2017-02-01 (0 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170130)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
   
   tun0  no wireless extensions.
  MachineType: HP 24-b019
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-12-generic 
root=UUID=c203e327-153e-408b-b8d8-ba3607d8b02b ro locale=zh_CN quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-12-generic N/A
   linux-backports-modules-4.9.0-12-generic  N/A
   linux-firmware1.162
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.9.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/25/2016
  dmi.bios.vendor: AMI
  dmi.bios.version: F.02
  dmi.board.asset.tag: 8CC6351M4W
  dmi.board.name: 81B8
  dmi.board.vendor: HP
  dmi.board.version: 0100
  dmi.chassis.asset.tag: 8CC6351M4W
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr:
  dmi.product.name: 24-b019
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661026/+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 1661026] Lspci.txt

[Mikemecanic]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1661026/+attachment/4811794/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1661026

Title:
  Grub Menu Not Shown Alongside Win 10 in Kylin 17.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Was able to reproduce the bug a second time (see bug #1660558)
  1. Machine boots directly in Kylin with no Grub menu
  2. Was not ask to removed media (long lasting bug in Kylin)
  3. ISO was made with the new version of Rufus: 2.12.1054
  4. Machine is set English us
  4. Win ten is invisible
  5. To recover sda1 and sda2, must delete Grub with Win10 installer: 
bootrec.exe / fixmbr
  6. The 2 previous issues are gone: Don’t see the Firmware bug + do not boot 
in Try Ubuntu
  7. Did not do any updates yet nor troubleshooting
  8. Partitions scheme BIOS mode:

  Number  Start   End SizeType  File system Flags
   1  1049kB  525MB   524MB   primary   ntfsboot
   2  525MB   785GB   785GB   primary   ntfs
   3  785GB   786GB   256MB   primary   ext2
   4  786GB   1000GB  215GB   extended
   5  786GB   790GB   4095MB  logical   linux-swap(v1)
   6  790GB   814GB   24.6GB  logical   ext4
   7  814GB   1000GB  186GB   logical   ext4
  --- 
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zz 1601 F pulseaudio
   /dev/snd/controlC0:  zz 1601 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=f825d75e-e7fb-4eaa-a113-22c3249880ae
  InstallationDate: Installed on 2017-02-01 (0 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170130)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
   
   tun0  no wireless extensions.
  MachineType: HP 24-b019
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-12-generic 
root=UUID=c203e327-153e-408b-b8d8-ba3607d8b02b ro locale=zh_CN quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-12-generic N/A
   linux-backports-modules-4.9.0-12-generic  N/A
   linux-firmware1.162
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.9.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/25/2016
  dmi.bios.vendor: AMI
  dmi.bios.version: F.02
  dmi.board.asset.tag: 8CC6351M4W
  dmi.board.name: 81B8
  dmi.board.vendor: HP
  dmi.board.version: 0100
  dmi.chassis.asset.tag: 8CC6351M4W
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr:
  dmi.product.name: 24-b019
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661026/+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 1661026] ProcEnviron.txt

[Mikemecanic]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1661026/+attachment/4811797/+files/ProcEnviron.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/1661026

Title:
  Grub Menu Not Shown Alongside Win 10 in Kylin 17.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Was able to reproduce the bug a second time (see bug #1660558)
  1. Machine boots directly in Kylin with no Grub menu
  2. Was not ask to removed media (long lasting bug in Kylin)
  3. ISO was made with the new version of Rufus: 2.12.1054
  4. Machine is set English us
  4. Win ten is invisible
  5. To recover sda1 and sda2, must delete Grub with Win10 installer: 
bootrec.exe / fixmbr
  6. The 2 previous issues are gone: Don’t see the Firmware bug + do not boot 
in Try Ubuntu
  7. Did not do any updates yet nor troubleshooting
  8. Partitions scheme BIOS mode:

  Number  Start   End SizeType  File system Flags
   1  1049kB  525MB   524MB   primary   ntfsboot
   2  525MB   785GB   785GB   primary   ntfs
   3  785GB   786GB   256MB   primary   ext2
   4  786GB   1000GB  215GB   extended
   5  786GB   790GB   4095MB  logical   linux-swap(v1)
   6  790GB   814GB   24.6GB  logical   ext4
   7  814GB   1000GB  186GB   logical   ext4
  --- 
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zz 1601 F pulseaudio
   /dev/snd/controlC0:  zz 1601 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=f825d75e-e7fb-4eaa-a113-22c3249880ae
  InstallationDate: Installed on 2017-02-01 (0 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170130)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
   
   tun0  no wireless extensions.
  MachineType: HP 24-b019
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-12-generic 
root=UUID=c203e327-153e-408b-b8d8-ba3607d8b02b ro locale=zh_CN quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-12-generic N/A
   linux-backports-modules-4.9.0-12-generic  N/A
   linux-firmware1.162
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.9.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/25/2016
  dmi.bios.vendor: AMI
  dmi.bios.version: F.02
  dmi.board.asset.tag: 8CC6351M4W
  dmi.board.name: 81B8
  dmi.board.vendor: HP
  dmi.board.version: 0100
  dmi.chassis.asset.tag: 8CC6351M4W
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr:
  dmi.product.name: 24-b019
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661026/+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 1661026] ProcModules.txt

[Mikemecanic]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1661026/+attachment/4811799/+files/ProcModules.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/1661026

Title:
  Grub Menu Not Shown Alongside Win 10 in Kylin 17.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Was able to reproduce the bug a second time (see bug #1660558)
  1. Machine boots directly in Kylin with no Grub menu
  2. Was not ask to removed media (long lasting bug in Kylin)
  3. ISO was made with the new version of Rufus: 2.12.1054
  4. Machine is set English us
  4. Win ten is invisible
  5. To recover sda1 and sda2, must delete Grub with Win10 installer: 
bootrec.exe / fixmbr
  6. The 2 previous issues are gone: Don’t see the Firmware bug + do not boot 
in Try Ubuntu
  7. Did not do any updates yet nor troubleshooting
  8. Partitions scheme BIOS mode:

  Number  Start   End SizeType  File system Flags
   1  1049kB  525MB   524MB   primary   ntfsboot
   2  525MB   785GB   785GB   primary   ntfs
   3  785GB   786GB   256MB   primary   ext2
   4  786GB   1000GB  215GB   extended
   5  786GB   790GB   4095MB  logical   linux-swap(v1)
   6  790GB   814GB   24.6GB  logical   ext4
   7  814GB   1000GB  186GB   logical   ext4
  --- 
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zz 1601 F pulseaudio
   /dev/snd/controlC0:  zz 1601 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=f825d75e-e7fb-4eaa-a113-22c3249880ae
  InstallationDate: Installed on 2017-02-01 (0 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170130)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
   
   tun0  no wireless extensions.
  MachineType: HP 24-b019
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-12-generic 
root=UUID=c203e327-153e-408b-b8d8-ba3607d8b02b ro locale=zh_CN quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-12-generic N/A
   linux-backports-modules-4.9.0-12-generic  N/A
   linux-firmware1.162
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.9.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/25/2016
  dmi.bios.vendor: AMI
  dmi.bios.version: F.02
  dmi.board.asset.tag: 8CC6351M4W
  dmi.board.name: 81B8
  dmi.board.vendor: HP
  dmi.board.version: 0100
  dmi.chassis.asset.tag: 8CC6351M4W
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr:
  dmi.product.name: 24-b019
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661026/+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 1661026] AlsaInfo.txt

[Mikemecanic]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1661026/+attachment/4811790/+files/AlsaInfo.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/1661026

Title:
  Grub Menu Not Shown Alongside Win 10 in Kylin 17.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Was able to reproduce the bug a second time (see bug #1660558)
  1. Machine boots directly in Kylin with no Grub menu
  2. Was not ask to removed media (long lasting bug in Kylin)
  3. ISO was made with the new version of Rufus: 2.12.1054
  4. Machine is set English us
  4. Win ten is invisible
  5. To recover sda1 and sda2, must delete Grub with Win10 installer: 
bootrec.exe / fixmbr
  6. The 2 previous issues are gone: Don’t see the Firmware bug + do not boot 
in Try Ubuntu
  7. Did not do any updates yet nor troubleshooting
  8. Partitions scheme BIOS mode:

  Number  Start   End SizeType  File system Flags
   1  1049kB  525MB   524MB   primary   ntfsboot
   2  525MB   785GB   785GB   primary   ntfs
   3  785GB   786GB   256MB   primary   ext2
   4  786GB   1000GB  215GB   extended
   5  786GB   790GB   4095MB  logical   linux-swap(v1)
   6  790GB   814GB   24.6GB  logical   ext4
   7  814GB   1000GB  186GB   logical   ext4
  --- 
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zz 1601 F pulseaudio
   /dev/snd/controlC0:  zz 1601 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=f825d75e-e7fb-4eaa-a113-22c3249880ae
  InstallationDate: Installed on 2017-02-01 (0 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170130)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
   
   tun0  no wireless extensions.
  MachineType: HP 24-b019
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-12-generic 
root=UUID=c203e327-153e-408b-b8d8-ba3607d8b02b ro locale=zh_CN quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-12-generic N/A
   linux-backports-modules-4.9.0-12-generic  N/A
   linux-firmware1.162
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.9.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/25/2016
  dmi.bios.vendor: AMI
  dmi.bios.version: F.02
  dmi.board.asset.tag: 8CC6351M4W
  dmi.board.name: 81B8
  dmi.board.vendor: HP
  dmi.board.version: 0100
  dmi.chassis.asset.tag: 8CC6351M4W
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr:
  dmi.product.name: 24-b019
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661026/+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 1661026] PulseList.txt

[Mikemecanic]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1661026/+attachment/4811800/+files/PulseList.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/1661026

Title:
  Grub Menu Not Shown Alongside Win 10 in Kylin 17.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Was able to reproduce the bug a second time (see bug #1660558)
  1. Machine boots directly in Kylin with no Grub menu
  2. Was not ask to removed media (long lasting bug in Kylin)
  3. ISO was made with the new version of Rufus: 2.12.1054
  4. Machine is set English us
  4. Win ten is invisible
  5. To recover sda1 and sda2, must delete Grub with Win10 installer: 
bootrec.exe / fixmbr
  6. The 2 previous issues are gone: Don’t see the Firmware bug + do not boot 
in Try Ubuntu
  7. Did not do any updates yet nor troubleshooting
  8. Partitions scheme BIOS mode:

  Number  Start   End SizeType  File system Flags
   1  1049kB  525MB   524MB   primary   ntfsboot
   2  525MB   785GB   785GB   primary   ntfs
   3  785GB   786GB   256MB   primary   ext2
   4  786GB   1000GB  215GB   extended
   5  786GB   790GB   4095MB  logical   linux-swap(v1)
   6  790GB   814GB   24.6GB  logical   ext4
   7  814GB   1000GB  186GB   logical   ext4
  --- 
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zz 1601 F pulseaudio
   /dev/snd/controlC0:  zz 1601 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=f825d75e-e7fb-4eaa-a113-22c3249880ae
  InstallationDate: Installed on 2017-02-01 (0 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170130)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
   
   tun0  no wireless extensions.
  MachineType: HP 24-b019
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-12-generic 
root=UUID=c203e327-153e-408b-b8d8-ba3607d8b02b ro locale=zh_CN quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-12-generic N/A
   linux-backports-modules-4.9.0-12-generic  N/A
   linux-firmware1.162
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.9.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/25/2016
  dmi.bios.vendor: AMI
  dmi.bios.version: F.02
  dmi.board.asset.tag: 8CC6351M4W
  dmi.board.name: 81B8
  dmi.board.vendor: HP
  dmi.board.version: 0100
  dmi.chassis.asset.tag: 8CC6351M4W
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr:
  dmi.product.name: 24-b019
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661026/+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 1661026] ProcCpuinfo.txt

[Mikemecanic]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1661026/+attachment/4811796/+files/ProcCpuinfo.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/1661026

Title:
  Grub Menu Not Shown Alongside Win 10 in Kylin 17.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Was able to reproduce the bug a second time (see bug #1660558)
  1. Machine boots directly in Kylin with no Grub menu
  2. Was not ask to removed media (long lasting bug in Kylin)
  3. ISO was made with the new version of Rufus: 2.12.1054
  4. Machine is set English us
  4. Win ten is invisible
  5. To recover sda1 and sda2, must delete Grub with Win10 installer: 
bootrec.exe / fixmbr
  6. The 2 previous issues are gone: Don’t see the Firmware bug + do not boot 
in Try Ubuntu
  7. Did not do any updates yet nor troubleshooting
  8. Partitions scheme BIOS mode:

  Number  Start   End SizeType  File system Flags
   1  1049kB  525MB   524MB   primary   ntfsboot
   2  525MB   785GB   785GB   primary   ntfs
   3  785GB   786GB   256MB   primary   ext2
   4  786GB   1000GB  215GB   extended
   5  786GB   790GB   4095MB  logical   linux-swap(v1)
   6  790GB   814GB   24.6GB  logical   ext4
   7  814GB   1000GB  186GB   logical   ext4
  --- 
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zz 1601 F pulseaudio
   /dev/snd/controlC0:  zz 1601 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=f825d75e-e7fb-4eaa-a113-22c3249880ae
  InstallationDate: Installed on 2017-02-01 (0 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170130)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
   
   tun0  no wireless extensions.
  MachineType: HP 24-b019
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-12-generic 
root=UUID=c203e327-153e-408b-b8d8-ba3607d8b02b ro locale=zh_CN quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-12-generic N/A
   linux-backports-modules-4.9.0-12-generic  N/A
   linux-firmware1.162
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.9.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/25/2016
  dmi.bios.vendor: AMI
  dmi.bios.version: F.02
  dmi.board.asset.tag: 8CC6351M4W
  dmi.board.name: 81B8
  dmi.board.vendor: HP
  dmi.board.version: 0100
  dmi.chassis.asset.tag: 8CC6351M4W
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr:
  dmi.product.name: 24-b019
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661026/+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 1661026] WifiSyslog.txt

[Mikemecanic]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1661026/+attachment/4811802/+files/WifiSyslog.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/1661026

Title:
  Grub Menu Not Shown Alongside Win 10 in Kylin 17.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Was able to reproduce the bug a second time (see bug #1660558)
  1. Machine boots directly in Kylin with no Grub menu
  2. Was not ask to removed media (long lasting bug in Kylin)
  3. ISO was made with the new version of Rufus: 2.12.1054
  4. Machine is set English us
  4. Win ten is invisible
  5. To recover sda1 and sda2, must delete Grub with Win10 installer: 
bootrec.exe / fixmbr
  6. The 2 previous issues are gone: Don’t see the Firmware bug + do not boot 
in Try Ubuntu
  7. Did not do any updates yet nor troubleshooting
  8. Partitions scheme BIOS mode:

  Number  Start   End SizeType  File system Flags
   1  1049kB  525MB   524MB   primary   ntfsboot
   2  525MB   785GB   785GB   primary   ntfs
   3  785GB   786GB   256MB   primary   ext2
   4  786GB   1000GB  215GB   extended
   5  786GB   790GB   4095MB  logical   linux-swap(v1)
   6  790GB   814GB   24.6GB  logical   ext4
   7  814GB   1000GB  186GB   logical   ext4
  --- 
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zz 1601 F pulseaudio
   /dev/snd/controlC0:  zz 1601 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=f825d75e-e7fb-4eaa-a113-22c3249880ae
  InstallationDate: Installed on 2017-02-01 (0 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170130)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
   
   tun0  no wireless extensions.
  MachineType: HP 24-b019
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-12-generic 
root=UUID=c203e327-153e-408b-b8d8-ba3607d8b02b ro locale=zh_CN quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-12-generic N/A
   linux-backports-modules-4.9.0-12-generic  N/A
   linux-firmware1.162
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.9.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/25/2016
  dmi.bios.vendor: AMI
  dmi.bios.version: F.02
  dmi.board.asset.tag: 8CC6351M4W
  dmi.board.name: 81B8
  dmi.board.vendor: HP
  dmi.board.version: 0100
  dmi.chassis.asset.tag: 8CC6351M4W
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr:
  dmi.product.name: 24-b019
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661026/+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 1661026] ProcInterrupts.txt

[Mikemecanic]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1661026/+attachment/4811798/+files/ProcInterrupts.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/1661026

Title:
  Grub Menu Not Shown Alongside Win 10 in Kylin 17.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Was able to reproduce the bug a second time (see bug #1660558)
  1. Machine boots directly in Kylin with no Grub menu
  2. Was not ask to removed media (long lasting bug in Kylin)
  3. ISO was made with the new version of Rufus: 2.12.1054
  4. Machine is set English us
  4. Win ten is invisible
  5. To recover sda1 and sda2, must delete Grub with Win10 installer: 
bootrec.exe / fixmbr
  6. The 2 previous issues are gone: Don’t see the Firmware bug + do not boot 
in Try Ubuntu
  7. Did not do any updates yet nor troubleshooting
  8. Partitions scheme BIOS mode:

  Number  Start   End SizeType  File system Flags
   1  1049kB  525MB   524MB   primary   ntfsboot
   2  525MB   785GB   785GB   primary   ntfs
   3  785GB   786GB   256MB   primary   ext2
   4  786GB   1000GB  215GB   extended
   5  786GB   790GB   4095MB  logical   linux-swap(v1)
   6  790GB   814GB   24.6GB  logical   ext4
   7  814GB   1000GB  186GB   logical   ext4
  --- 
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zz 1601 F pulseaudio
   /dev/snd/controlC0:  zz 1601 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=f825d75e-e7fb-4eaa-a113-22c3249880ae
  InstallationDate: Installed on 2017-02-01 (0 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170130)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
   
   tun0  no wireless extensions.
  MachineType: HP 24-b019
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-12-generic 
root=UUID=c203e327-153e-408b-b8d8-ba3607d8b02b ro locale=zh_CN quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-12-generic N/A
   linux-backports-modules-4.9.0-12-generic  N/A
   linux-firmware1.162
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.9.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/25/2016
  dmi.bios.vendor: AMI
  dmi.bios.version: F.02
  dmi.board.asset.tag: 8CC6351M4W
  dmi.board.name: 81B8
  dmi.board.vendor: HP
  dmi.board.version: 0100
  dmi.chassis.asset.tag: 8CC6351M4W
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr:
  dmi.product.name: 24-b019
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661026/+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 1661026] Lsusb.txt

[Mikemecanic]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1661026/+attachment/4811795/+files/Lsusb.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1661026

Title:
  Grub Menu Not Shown Alongside Win 10 in Kylin 17.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Was able to reproduce the bug a second time (see bug #1660558)
  1. Machine boots directly in Kylin with no Grub menu
  2. Was not ask to removed media (long lasting bug in Kylin)
  3. ISO was made with the new version of Rufus: 2.12.1054
  4. Machine is set English us
  4. Win ten is invisible
  5. To recover sda1 and sda2, must delete Grub with Win10 installer: 
bootrec.exe / fixmbr
  6. The 2 previous issues are gone: Don’t see the Firmware bug + do not boot 
in Try Ubuntu
  7. Did not do any updates yet nor troubleshooting
  8. Partitions scheme BIOS mode:

  Number  Start   End SizeType  File system Flags
   1  1049kB  525MB   524MB   primary   ntfsboot
   2  525MB   785GB   785GB   primary   ntfs
   3  785GB   786GB   256MB   primary   ext2
   4  786GB   1000GB  215GB   extended
   5  786GB   790GB   4095MB  logical   linux-swap(v1)
   6  790GB   814GB   24.6GB  logical   ext4
   7  814GB   1000GB  186GB   logical   ext4
  --- 
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zz 1601 F pulseaudio
   /dev/snd/controlC0:  zz 1601 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=f825d75e-e7fb-4eaa-a113-22c3249880ae
  InstallationDate: Installed on 2017-02-01 (0 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170130)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
   
   tun0  no wireless extensions.
  MachineType: HP 24-b019
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-12-generic 
root=UUID=c203e327-153e-408b-b8d8-ba3607d8b02b ro locale=zh_CN quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-12-generic N/A
   linux-backports-modules-4.9.0-12-generic  N/A
   linux-firmware1.162
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.9.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/25/2016
  dmi.bios.vendor: AMI
  dmi.bios.version: F.02
  dmi.board.asset.tag: 8CC6351M4W
  dmi.board.name: 81B8
  dmi.board.vendor: HP
  dmi.board.version: 0100
  dmi.chassis.asset.tag: 8CC6351M4W
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr:
  dmi.product.name: 24-b019
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661026/+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 1661026] [NEW] Grub Menu Not Shown Alongside Win 10 in Kylin 17.04

[Mikemecanic]

Public bug reported:

Was able to reproduce the bug a second time (see bug #1660558)
1. Machine boots directly in Kylin with no Grub menu
2. Was not ask to removed media (long lasting bug in Kylin)
3. ISO was made with the new version of Rufus: 2.12.1054
4. Machine is set English us
4. Win ten is invisible
5. To recover sda1 and sda2, must delete Grub with Win10 installer: bootrec.exe 
/ fixmbr
6. The 2 previous issues are gone: Don’t see the Firmware bug + do not boot in 
Try Ubuntu
7. Did not do any updates yet nor troubleshooting
8. Partitions scheme BIOS mode:

Number  Start   End SizeType  File system Flags
 1  1049kB  525MB   524MB   primary   ntfsboot
 2  525MB   785GB   785GB   primary   ntfs
 3  785GB   786GB   256MB   primary   ext2
 4  786GB   1000GB  215GB   extended
 5  786GB   790GB   4095MB  logical   linux-swap(v1)
 6  790GB   814GB   24.6GB  logical   ext4
 7  814GB   1000GB  186GB   logical   ext4
--- 
ApportVersion: 2.20.4-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  zz 1601 F pulseaudio
 /dev/snd/controlC0:  zz 1601 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 17.04
HibernationDevice: RESUME=UUID=f825d75e-e7fb-4eaa-a113-22c3249880ae
InstallationDate: Installed on 2017-02-01 (0 days ago)
InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170130)
IwConfig:
 lono wireless extensions.
 
 enp1s0no wireless extensions.
 
 tun0  no wireless extensions.
MachineType: HP 24-b019
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-12-generic 
root=UUID=c203e327-153e-408b-b8d8-ba3607d8b02b ro locale=zh_CN quiet splash 
vt.handoff=7
ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
RelatedPackageVersions:
 linux-restricted-modules-4.9.0-12-generic N/A
 linux-backports-modules-4.9.0-12-generic  N/A
 linux-firmware1.162
RfKill:
 
Tags:  zesty
Uname: Linux 4.9.0-12-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/25/2016
dmi.bios.vendor: AMI
dmi.bios.version: F.02
dmi.board.asset.tag: 8CC6351M4W
dmi.board.name: 81B8
dmi.board.vendor: HP
dmi.board.version: 0100
dmi.chassis.asset.tag: 8CC6351M4W
dmi.chassis.type: 13
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr:
dmi.product.name: 24-b019
dmi.sys.vendor: HP

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: apport-collected grub windows10 zesty

** Tags added: apport-collected zesty

** Description changed:

  Was able to reproduce the bug a second time (see bug #1660558)
  1. Machine boots directly in Kylin with no Grub menu
  2. Was not ask to removed media (long lasting bug in Kylin)
  3. ISO was made with the new version of Rufus: 2.12.1054
  4. Machine is set English us
  4. Win ten is invisible
  5. To recover sda1 and sda2, must delete Grub with Win10 installer: 
bootrec.exe / fixmbr
  6. The 2 previous issues are gone: Don’t see the Firmware bug + do not boot 
in Try Ubuntu
  7. Did not do any updates yet nor troubleshooting
  8. Partitions scheme BIOS mode:
  
  Number  Start   End SizeType  File system Flags
   1  1049kB  525MB   524MB   primary   ntfsboot
   2  525MB   785GB   785GB   primary   ntfs
   3  785GB   786GB   256MB   primary   ext2
   4  786GB   1000GB  215GB   extended
   5  786GB   790GB   4095MB  logical   linux-swap(v1)
   6  790GB   814GB   24.6GB  logical   ext4
   7  814GB   1000GB  186GB   logical   ext4
+ --- 
+ ApportVersion: 2.20.4-0ubuntu1
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  zz 1601 F pulseaudio
+  /dev/snd/controlC0:  zz 1601 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 17.04
+ HibernationDevice: RESUME=UUID=f825d75e-e7fb-4eaa-a113-22c3249880ae
+ InstallationDate: Installed on 2017-02-01 (0 days ago)
+ InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170130)
+ IwConfig:
+  lono wireless extensions.
+  
+  enp1s0no wireless extensions.
+  
+  tun0  no wireless extensions.
+ MachineType: HP 24-b019
+ Package: linux (not installed)
+ ProcFB: 0 amdgpudrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-12-generic 
root=UUID=c203e327-153e-408b-b8d8-ba3607d8b02b ro locale=zh_CN quiet splash 
vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
+ RelatedPackageVersions:
+  linux-restricted-modules-4.9.0-12-generic N/A
+  linux-backports-modules-4.9.0-12-generic  N/A
+  linux-firmware1.162
+ RfKill:
+  
+ Tags:  zesty
+ Uname: Linux 4.9.0-12-generic x86_64
+ UpgradeStatus: No upgrade log pr

[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)

[Rod Smith]

linux-image-3.13.0-101-generic_3.13.0-101.148~lp1649326Commit6edf523
boots fine for me.

-- 
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/1649326

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Confirmed

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic

  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)

  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101
  kernel. See this Kubuntu forum thread for details:

  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels

  Note that early on, this thread focuses on rEFInd; however, the bug
  can be reproduced with other boot managers, including the EFI shell,
  as described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
  kernel, and I believe it's this component that's failing. The problem
  does NOT occur when using GRUB to launch the kernel. (GRUB does not
  rely on the EFI stub loader.)

  I have NOT encountered the problem with Xenial and its 4.4.0-series kernels 
(last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last 
tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from 
series beyond 3.13.0.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rodsmith   1675 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc
  InstallationDate: Installed on 2014-04-27 (960 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-106-generic N/A
   linux-backports-modules-3.13.0-106-generic  N/A
   linux-firmware  1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-106-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+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 1518457] Re: kswapd0 100% CPU usage

[Dan Streetman]

As a comment to those expecting that disabling swap will prevent kswapd
from doing anything, that's incorrect.  kswapd also is responsible for
clearing out the page cache, so even with swap disabled you'll still see
it doing work, especially during heavy IO that uses the page cache.  For
example, copying large files from fast drives.  That's completely
normal.  What this bug is about, is kswapd trying over and over to do
its normal work, but making no progress, so it continues to use 100% cpu
while the rest of the system is doing nothing.  That bug should be fixed
now.

If anyone continues to see *this* bug - kswapd using 100% cpu while your
system is doing nothing and kswapd never recovers - you can report it
here, but you should also open a new bug and reference it in your
comment (this bug is fixed and closed).  However, if all you see is
kswapd using cpu while you're doing things - especially file IO - that
isn't this bug, and it probably isn't actually a bug at all.

-- 
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/1518457

Title:
  kswapd0 100% CPU usage

Status in Linux:
  Unknown
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:
  As per bug 721896 and various others:

  I'm on an AWS t2.micro instance (Xeon E5-2670, 991MiB of memory).
  Occasionally (about once a day), kswapd0 falls into a busy loop and
  spins on 100% CPU usage indefinitely. This can be provoked by
  copying/writing large files (e.g. dding a 256MB file), but it happens
  occasionally otherwise. System memory usage (not including
  buffers/caches) currently sits at 36%, which is typical[1]. Initially
  I had no swap space configured; I've since tried enabling a 256MB swap
  file, but the problem continues to occur and no swap space is used.
  The system can be recovered with `echo 1 > /proc/sys/vm/drop_caches`.

  Happy to provide further information/take further debugging actions.

  
  [1] Full output from `free`:
   total   used   free sharedbuffers cached
  Mem:   1014936 483448 531488  28556   9756 112700
  -/+ buffers/cache: 360992 653944
  Swap:   262140  0 262140

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 19 19:40 seq
   crw-rw 1 root audio 116, 33 Nov 19 19:40 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Fri Nov 20 20:44:30 2015
  Ec2AMI: ami-1c552a76
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: t2.micro
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 xen
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=35bc01f4-4602-4823-976e-508edef899df ro console=tty1 console=ttyS0 
net.ifnames=0
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2015
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd05/06/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1518457/+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 1660993] Re: Xenial update to v4.4.45 stable release

[Tim Gardner]

** 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.45 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.45 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.45 stable release shall be
+ applied:
  
-The following patches from the v4.4.45 stable release shall be
- applied:
+ ftrace/x86: Set ftrace_stub to weak to prevent gcc from using short jumps to 
it
+ IB/mlx5: Wait for all async command completions to complete
+ IB/mlx4: Set traffic class in AH
+ IB/mlx4: Fix out-of-range array index in destroy qp flow
+ IB/mlx4: Fix port query for 56Gb Ethernet links
+ IB/mlx4: When no DMFS for IPoIB, don't allow NET_IF QPs
+ IB/IPoIB: Remove can't use GFP_NOIO warning
+ perf scripting: Avoid leaking the scripting_context variable
+ ARM: dts: imx31: fix clock control module interrupts description
+ ARM: dts: imx31: move CCM device node to AIPS2 bus devices
+ ARM: dts: imx31: fix AVIC base address
+ tmpfs: clear S_ISGID when setting posix ACLs
+ x86/PCI: Ignore _CRS on Supermicro X8DTH-i/6/iF/6F
+ svcrpc: don't leak contexts on PROC_DESTROY
+ fuse: clear FR_PENDING flag when moving requests out of pending queue
+ PCI: Enumerate switches below PCI-to-PCIe bridges
+ HID: corsair: fix DMA buffers on stack
+ HID: corsair: fix control-transfer error handling
+ mmc: mxs-mmc: Fix additional cycles after transmission stop
+ ieee802154: atusb: do not use the stack for buffers to make them DMA able
+ mtd: nand: xway: disable module support
+ x86/ioapic: Restore IO-APIC irq_chip retrigger callback
+ qla2xxx: Fix crash due to null pointer access
+ ubifs: Fix journal replay wrt. xattr nodes
+ clocksource/exynos_mct: Clear interrupt when cpu is shut down
+ svcrdma: avoid duplicate dma unmapping during error recovery
+ ARM: 8634/1: hw_breakpoint: blacklist Scorpion CPUs
+ ceph: fix bad endianness handling in parse_reply_info_extra
+ ARM: dts: da850-evm: fix read access to SPI flash
+ arm64/ptrace: Preserve previous registers for short regset write
+ arm64/ptrace: Preserve previous registers for short regset write - 2
+ arm64/ptrace: Preserve previous registers for short regset write - 3
+ arm64/ptrace: Avoid uninitialised struct padding in fpr_set()
+ arm64/ptrace: Reject attempts to set incomplete hardware breakpoint fields
+ ARM: dts: imx6qdl-nitrogen6_max: fix sgtl5000 pinctrl init
+ ARM: ux500: fix prcmu_is_cpu_in_wfi() calculation
+ ARM: 8613/1: Fix the uaccess crash on PB11MPCore
+ blackfin: check devm_pinctrl_get() for errors
+ ite-cir: initialize use_demodulator before using it
+ dmaengine: pl330: Fix runtime PM support for terminated transfers
+ selftest/powerpc: Wrong PMC initialized in pmc56_overflow test
+ arm64: avoid returning from bad_mode
+ Linux 4.4.45

-- 
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/1660993

Title:
  Xenial update to v4.4.45 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 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.45 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.45 stable release shall be
  applied:

  ftrace/x86: Set ftrace_stub to weak to prevent gcc from using short jumps to 
it
  IB/mlx5: Wait for all async command completions to complete
  IB/mlx4: Set traffic class in AH
  IB/mlx4: Fix out-of-range array index in destroy qp flow
  IB/mlx4: Fix port query for 56Gb Ethernet links
  IB/mlx4: When no 

[Kernel-packages] [Bug 1660949] Re: No HDMI out on Asus UX51 running 16.10 or 16.04

[Nathan Willis]

Seriously: please tell me *what* logs are needed here if apport-collect
cannot — and I will provide them.

-- 
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/1660949

Title:
  No HDMI out on Asus UX51 running 16.10 or 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 16.10 on an Asus UX51 laptop; i915+Nvidia dual graphics
  using the Nouveau driver.

  The machine has both VGA out and HDMI out; VGA works like a charm but
  HDMI is not even detected. Meaning that none of (xrandr, lspci, aplay,
  get-edid) even reports the HDMI port as present.

  It's not clear to me whether or not this is an X or a kernel issue at
  the heart of it.  I did, however, upgrade recently from 16.04 (where
  this bug was also present!) to see if that made any difference (which
  it did not) and I did try the proprietary Nvidia drivers (340 and 367)
  to see if either of them made a difference (which they did not).

  I can assure you that I've read every relevant-sounding bug report and
  askubuntu question from the past year on this topic without
  discovering any fixes.  Happy to try what needs to be tried.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660949/+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 1660994] [NEW] Xenial update to v4.4.46 stable release

[Tim Gardner]

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.46 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.46 stable release shall be
applied:

fbdev: color map copying bounds checking
tile/ptrace: Preserve previous registers for short regset write
drm: Fix broken VT switch with video=1366x768 option
mm/mempolicy.c: do not put mempolicy before using its nodemask
sysctl: fix proc_doulongvec_ms_jiffies_minmax()
ISDN: eicon: silence misleading array-bounds warning
RDMA/cma: Fix unknown symbol when CONFIG_IPV6 is not enabled
s390/ptrace: Preserve previous registers for short regset write
can: c_can_pci: fix null-pointer-deref in c_can_start() - set device pointer
can: ti_hecc: add missing prepare and unprepare of the clock
ARC: udelay: fix inline assembler by adding LP_COUNT to clobber list
ARC: [arcompact] handle unaligned access delay slot corner case
parisc: Don't use BITS_PER_LONG in userspace-exported swab.h header
nfs: Don't increment lock sequence ID after NFS4ERR_MOVED
NFSv4.0: always send mode in SETATTR after EXCLUSIVE4
SUNRPC: cleanup ida information when removing sunrpc module
drm/i915: Don't leak edid in intel_crt_detect_ddc()
IB/ipoib: move back IB LL address into the hard header
IB/umem: Release pid in error and ODP flow
s5k4ecgx: select CRC32 helper
pinctrl: broxton: Use correct PADCFGLOCK offset
platform/x86: intel_mid_powerbtn: Set IRQ_ONESHOT
mm, memcg: do not retry precharge charges
Linux 4.4.46

** 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.46 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.46 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.46 stable release shall be
+ applied:
  
-The following patches from the v4.4.46 stable release shall be
- applied:
+ fbdev: color map copying bounds checking
+ tile/ptrace: Preserve previous registers for short regset write
+ drm: Fix broken VT switch with video=1366x768 option
+ mm/mempolicy.c: do not put mempolicy before using its nodemask
+ sysctl: fix proc_doulongvec_ms_jiffies_minmax()
+ ISDN: eicon: silence misleading array-bounds warning
+ RDMA/cma: Fix unknown symbol when CONFIG_IPV6 is not enabled
+ s390/ptrace: Preserve previous registers for short regset write
+ can: c_can_pci: fix null-pointer-deref in c_can_start() - set device pointer
+ can: ti_hecc: add missing prepare and unprepare of the clock
+ ARC: udelay: fix inline assembler by adding LP_COUNT to clobber list
+ ARC: [arcompact] handle unaligned access delay slot corner case
+ parisc: Don't use BITS_PER_LONG in userspace-exported swab.h header
+ nfs: Don't increment lock sequence ID after NFS4ERR_MOVED
+ NFSv4.0: always send mode in SETATTR after EXCLUSIVE4
+ SUNRPC: cleanup ida information when removing sunrpc module
+ drm/i915: Don't leak edid in intel_crt_detect_ddc()
+ IB/ipoib: move back IB LL address into the hard header
+ IB/umem: Release pid in error and ODP flow
+ s5k4ecgx: select CRC32 helper
+ pinctrl: broxton: Use correct PADCFGLOCK offset
+ platform/x86: intel_mid_powerbtn: Set IRQ_ONESHOT
+ mm, memcg: do not retry precharge charges
+ Linux 4.4.46

-- 
You received this bug notification because you are a member of Kernel
Packages, which is sub

[Kernel-packages] [Bug 1611124] Re: W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915

[Seth Forshee]

@Gerardus: These messages are in reference to firmware for the i915
graphics driver, so it definitely has no relationship to your networking
issues.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1611124

Title:
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin
  for module i915

Status in xen:
  Unknown
Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  $sudo dpkg -i linux-image-4.8.0-040800rc1-lowlatency

  [...]

  update-initramfs: Generating /boot/initrd.img-4.8.0-040800rc1-lowlatency
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for 
module i915
  W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-firmware 1.159
  Uname: Linux 4.8.0-040800rc1-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  Date: Mon Aug  8 17:50:38 2016
  Dependencies:
   
  InstallationDate: Installed on 2015-07-26 (379 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xen/+bug/1611124/+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 1660993] [NEW] Xenial update to v4.4.45 stable release

[Tim Gardner]

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.45 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.45 stable release shall be
applied:

ftrace/x86: Set ftrace_stub to weak to prevent gcc from using short jumps to it
IB/mlx5: Wait for all async command completions to complete
IB/mlx4: Set traffic class in AH
IB/mlx4: Fix out-of-range array index in destroy qp flow
IB/mlx4: Fix port query for 56Gb Ethernet links
IB/mlx4: When no DMFS for IPoIB, don't allow NET_IF QPs
IB/IPoIB: Remove can't use GFP_NOIO warning
perf scripting: Avoid leaking the scripting_context variable
ARM: dts: imx31: fix clock control module interrupts description
ARM: dts: imx31: move CCM device node to AIPS2 bus devices
ARM: dts: imx31: fix AVIC base address
tmpfs: clear S_ISGID when setting posix ACLs
x86/PCI: Ignore _CRS on Supermicro X8DTH-i/6/iF/6F
svcrpc: don't leak contexts on PROC_DESTROY
fuse: clear FR_PENDING flag when moving requests out of pending queue
PCI: Enumerate switches below PCI-to-PCIe bridges
HID: corsair: fix DMA buffers on stack
HID: corsair: fix control-transfer error handling
mmc: mxs-mmc: Fix additional cycles after transmission stop
ieee802154: atusb: do not use the stack for buffers to make them DMA able
mtd: nand: xway: disable module support
x86/ioapic: Restore IO-APIC irq_chip retrigger callback
qla2xxx: Fix crash due to null pointer access
ubifs: Fix journal replay wrt. xattr nodes
clocksource/exynos_mct: Clear interrupt when cpu is shut down
svcrdma: avoid duplicate dma unmapping during error recovery
ARM: 8634/1: hw_breakpoint: blacklist Scorpion CPUs
ceph: fix bad endianness handling in parse_reply_info_extra
ARM: dts: da850-evm: fix read access to SPI flash
arm64/ptrace: Preserve previous registers for short regset write
arm64/ptrace: Preserve previous registers for short regset write - 2
arm64/ptrace: Preserve previous registers for short regset write - 3
arm64/ptrace: Avoid uninitialised struct padding in fpr_set()
arm64/ptrace: Reject attempts to set incomplete hardware breakpoint fields
ARM: dts: imx6qdl-nitrogen6_max: fix sgtl5000 pinctrl init
ARM: ux500: fix prcmu_is_cpu_in_wfi() calculation
ARM: 8613/1: Fix the uaccess crash on PB11MPCore
blackfin: check devm_pinctrl_get() for errors
ite-cir: initialize use_demodulator before using it
dmaengine: pl330: Fix runtime PM support for terminated transfers
selftest/powerpc: Wrong PMC initialized in pmc56_overflow test
arm64: avoid returning from bad_mode
Linux 4.4.45

** 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

-- 
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/1660993

Title:
  Xenial update to v4.4.45 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 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.45 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.45 stable release shall be
  applied:

  ftrace/x86: Set ftrace_stub to weak to prevent gcc from using short jumps to 
it
  IB/mlx5: Wait for all async command completions to complete
  IB/mlx4: Set traffic class in AH
  IB/mlx4: Fix out-of-range array index in destroy qp flow
  IB/mlx4: Fix port query for 56Gb Ethernet links
  IB/mlx4: When no DMFS for IPoIB, don't allow NET_IF QPs
  IB/IPoIB: Remove can't use GFP_NOIO warning
  perf scripting: Avoid leaking the scripting_context variable
  ARM: dts: imx31: fix clock control module interrupts description
  ARM: dts: imx31: move CCM device node to AIPS2 bus devices
  ARM: dts: imx31: fix AVIC base address
  tmpfs: clear S_ISGID when setting posix ACLs
  x86/PCI: Ignore _CRS on Supermicro X8DTH-i/6/iF/6F
  svcrpc: don't leak co

[Kernel-packages] [Bug 1601954] Re: ensure all items are included in changelog and standardise packaging

[Thadeu Lima de Souza Cascardo]

** Also affects: linux-meta-snapdragon (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux-meta-snapdragon (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux-meta-snapdragon (Ubuntu Xenial)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1601954

Title:
  ensure all items are included in changelog and standardise packaging

Status in linux-meta package in Ubuntu:
  Fix Released
Status in linux-meta-lts-trusty package in Ubuntu:
  New
Status in linux-meta-lts-xenial package in Ubuntu:
  New
Status in linux-meta-raspi2 package in Ubuntu:
  New
Status in linux-meta-snapdragon package in Ubuntu:
  New
Status in linux-signed package in Ubuntu:
  Fix Released
Status in linux-meta source package in Precise:
  New
Status in linux-meta-lts-trusty source package in Precise:
  New
Status in linux-meta-lts-xenial source package in Precise:
  Invalid
Status in linux-meta-raspi2 source package in Precise:
  New
Status in linux-meta-snapdragon source package in Precise:
  New
Status in linux-signed source package in Precise:
  New
Status in linux-meta source package in Trusty:
  New
Status in linux-meta-lts-trusty source package in Trusty:
  Invalid
Status in linux-meta-lts-xenial source package in Trusty:
  New
Status in linux-meta-raspi2 source package in Trusty:
  New
Status in linux-meta-snapdragon source package in Trusty:
  New
Status in linux-signed source package in Trusty:
  New
Status in linux-meta source package in Xenial:
  Fix Committed
Status in linux-meta-lts-trusty source package in Xenial:
  Invalid
Status in linux-meta-lts-xenial source package in Xenial:
  Invalid
Status in linux-meta-raspi2 source package in Xenial:
  Confirmed
Status in linux-meta-snapdragon source package in Xenial:
  In Progress
Status in linux-signed source package in Xenial:
  New

Bug description:
  simplify packaging and ensure all items are included in changelog.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1601954/+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 1660986] [NEW] Zesty update to v4.9.7 stable release

[Tim Gardner]

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.9.7 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.9.7 stable release shall be
applied:

fbdev: color map copying bounds checking
tile/ptrace: Preserve previous registers for short regset write
drm: Schedule the output_poll_work with 1s delay if we have delayed event
drm: Fix broken VT switch with video=1366x768 option
drm/i915: Ignore bogus plane coordinates on SKL when the plane is not visible
drm/vc4: Fix memory leak of the CRTC state.
drm/vc4: Fix an integer overflow in temporary allocation layout.
drm/vc4: Return -EINVAL on the overflow checks failing.
drm/vc4: fix a bounds check
Revert "drm/radeon: always apply pci shutdown callbacks"
drm/atomic: clear out fence when duplicating state
mm/huge_memory.c: respect FOLL_FORCE/FOLL_COW for thp
mm/mempolicy.c: do not put mempolicy before using its nodemask
mm, page_alloc: fix check for NULL preferred_zone
mm, page_alloc: fix fast-path race with cpuset update or removal
mm, page_alloc: move cpuset seqcount checking to slowpath
mm, page_alloc: fix premature OOM when racing with cpuset mems update
vring: Force use of DMA API for ARM-based systems with legacy devices
userns: Make ucounts lock irq-safe
sysctl: fix proc_doulongvec_ms_jiffies_minmax()
xfs: prevent quotacheck from overloading inode lru
ISDN: eicon: silence misleading array-bounds warning
Btrfs: remove old tree_root case in btrfs_read_locked_inode()
Btrfs: disable xattr operations on subvolume directories
Btrfs: remove ->{get, set}_acl() from btrfs_dir_ro_inode_operations
RDMA/cma: Fix unknown symbol when CONFIG_IPV6 is not enabled
s390/mm: Fix cmma unused transfer from pgste into pte
s390/ptrace: Preserve previous registers for short regset write
IB/cxgb3: fix misspelling in header guard
IB/iser: Fix sg_tablesize calculation
IB/srp: fix mr allocation when the device supports sg gaps
IB/srp: fix invalid indirect_sg_entries parameter value
can: c_can_pci: fix null-pointer-deref in c_can_start() - set device pointer
can: ti_hecc: add missing prepare and unprepare of the clock
ARC: udelay: fix inline assembler by adding LP_COUNT to clobber list
ARC: [arcompact] handle unaligned access delay slot corner case
parisc: Don't use BITS_PER_LONG in userspace-exported swab.h header
nfs: Don't increment lock sequence ID after NFS4ERR_MOVED
NFSv4.1: Fix a deadlock in layoutget
NFSv4.0: always send mode in SETATTR after EXCLUSIVE4
SUNRPC: cleanup ida information when removing sunrpc module
iw_cxgb4: free EQ queue memory on last deref
pctv452e: move buffer to heap, no mutex
v4l: tvp5150: Reset device at probe time, not in get/set format handlers
v4l: tvp5150: Fix comment regarding output pin muxing
v4l: tvp5150: Don't override output pinmuxing at stream on/off time
drm/i915: Clear ret before unbinding in i915_gem_evict_something()
drm/i915: prevent crash with .disable_display parameter
drm/i915: Don't leak edid in intel_crt_detect_ddc()
drm/i915: Don't init hpd polling for vlv and chv from runtime_suspend()
drm/i915: Fix calculation of rotated x and y offsets for planar formats
drm/i915: Check for NULL atomic state in intel_crtc_disable_noatomic()
IB/umem: Release pid in error and ODP flow
IB/rxe: Fix rxe dev insertion to rxe_dev_list
IB/rxe: Prevent from completer to operate on non valid QP
s5k4ecgx: select CRC32 helper
pinctrl: broxton: Use correct PADCFGLOCK offset
pinctrl: uniphier: fix Ethernet (RMII) pin-mux setting for LD20
pinctrl: baytrail: Rectify debounce support
memory_hotplug: make zone_can_shift() return a boolean value
virtio_mmio: Set DMA masks appropriately
platform/x86: mlx-platform: free first dev on error
platform/x86: intel_mid_powerbtn: Set IRQ_ONESHOT
mm, memcg: do not retry precharge charges
perf/core: Fix concurrent sys_perf_event_open() vs. 'move_group' race
drm/i915: Remove WaDisableLSQCROPERFforOCL KBL workaround.
Linux 4.9.7

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Zesty)
 Importance: Undecided
 Status: New


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Zesty)
   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 originat

[Kernel-packages] [Bug 1655002] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From gpicc...@br.ibm.com 2017-02-01 08:08 EDT---
(In reply to comment #9)
> 4.4.0-63.84 and 4.8.0-38.40

Thanks very much Tim!

-- 
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/1655002

Title:
  Move some kernel modules to the main kernel package (part 2)

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  Hello Canonical,

  there are important kernel modules that are required on POWER systems,
  and they are currently on the linux-image-extra packages.

  So, in this case, every Power system needs to install the -extra
  package, which makes the -extra package required.

  Our suggestion is to add these important modules to the main kernel
  package, so we do not require the installation of the -extra package.

  One round of additions was already completed. But we verified some
  modules we need were missing, so we are hereby requesting a 2nd round
  of module additions to linux-image main package of Xenial and Yakkety
  (and all future releases).

  The list is:


  (AST stack)
  1. ast
  2. i2c-core
  3. sysfillrect
  4. syscopyarea
  5. sysimgblt
  6. fb_sys_fops
  7. drm
  8. drm_kms_helper
  9. ttm
  10. i2c-algo-bit

  11. kvm
  12. kvm_pr
  13. kvm_hv
  14. vmx_crypto
  15. at24
  16. nvmem_core
  17. cmdlinepart
  18. input_leds
  19. uio
  20. uio_pdrv_genirq
  21. ofpart

  (USB stack)
  22. usb_storage
  23. uas
  24. hid
  25. hid_generic
  26. usbhid


  Thanks in advance,

  
  Guilherme

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655002/+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 1601954] Re: ensure all items are included in changelog and standardise packaging

[Thadeu Lima de Souza Cascardo]

** Also affects: linux-meta-raspi2 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux-meta-raspi2 (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: linux-meta-raspi2 (Ubuntu Xenial)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1601954

Title:
  ensure all items are included in changelog and standardise packaging

Status in linux-meta package in Ubuntu:
  Fix Released
Status in linux-meta-lts-trusty package in Ubuntu:
  New
Status in linux-meta-lts-xenial package in Ubuntu:
  New
Status in linux-meta-raspi2 package in Ubuntu:
  New
Status in linux-signed package in Ubuntu:
  Fix Released
Status in linux-meta source package in Precise:
  New
Status in linux-meta-lts-trusty source package in Precise:
  New
Status in linux-meta-lts-xenial source package in Precise:
  Invalid
Status in linux-meta-raspi2 source package in Precise:
  New
Status in linux-signed source package in Precise:
  New
Status in linux-meta source package in Trusty:
  New
Status in linux-meta-lts-trusty source package in Trusty:
  Invalid
Status in linux-meta-lts-xenial source package in Trusty:
  New
Status in linux-meta-raspi2 source package in Trusty:
  New
Status in linux-signed source package in Trusty:
  New
Status in linux-meta source package in Xenial:
  Fix Committed
Status in linux-meta-lts-trusty source package in Xenial:
  Invalid
Status in linux-meta-lts-xenial source package in Xenial:
  Invalid
Status in linux-meta-raspi2 source package in Xenial:
  Confirmed
Status in linux-signed source package in Xenial:
  New

Bug description:
  simplify packaging and ensure all items are included in changelog.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1601954/+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 1655002] Re: Move some kernel modules to the main kernel package (part 2)

[Tim Gardner]

4.4.0-63.84 and 4.8.0-38.40

-- 
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/1655002

Title:
  Move some kernel modules to the main kernel package (part 2)

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  Hello Canonical,

  there are important kernel modules that are required on POWER systems,
  and they are currently on the linux-image-extra packages.

  So, in this case, every Power system needs to install the -extra
  package, which makes the -extra package required.

  Our suggestion is to add these important modules to the main kernel
  package, so we do not require the installation of the -extra package.

  One round of additions was already completed. But we verified some
  modules we need were missing, so we are hereby requesting a 2nd round
  of module additions to linux-image main package of Xenial and Yakkety
  (and all future releases).

  The list is:


  (AST stack)
  1. ast
  2. i2c-core
  3. sysfillrect
  4. syscopyarea
  5. sysimgblt
  6. fb_sys_fops
  7. drm
  8. drm_kms_helper
  9. ttm
  10. i2c-algo-bit

  11. kvm
  12. kvm_pr
  13. kvm_hv
  14. vmx_crypto
  15. at24
  16. nvmem_core
  17. cmdlinepart
  18. input_leds
  19. uio
  20. uio_pdrv_genirq
  21. ofpart

  (USB stack)
  22. usb_storage
  23. uas
  24. hid
  25. hid_generic
  26. usbhid


  Thanks in advance,

  
  Guilherme

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655002/+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 1590844] Re: Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition]

[First Last]

Are there any news on fixing this bug?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1590844

Title:
  Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition]

Status in Canonical System Image:
  Confirmed
Status in turbo:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  My bluetooth headset perfectly connects to my Meizu Pro 5. However,
  the sound quality is so poor (a lot of noise) such that you don't
  understand your communication partner. Note that the headset works
  perfectly together with Ubuntu on my Nexus 4.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+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 1660949] Re: No HDMI out on Asus UX51 running 16.10 or 16.04

[Nathan Willis]

I don't believe that the "issue I have encountered" has an effect on
this, but running apport-collect as suggested does nothing but initiate
an OAuth token loop at the Launchpad site, with me authorizing this
machine followed by ... nothing happening on the terminal or on the
site.

Repeating the apport-collect command a second time produces exactly the
same effect: complaint about authorization, me authorizing on the site,
nothing happening afterward.

Setting aside the issue of opening a new bug report against apport-
collect, what is *supposed* to be the result?

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1660949

Title:
  No HDMI out on Asus UX51 running 16.10 or 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 16.10 on an Asus UX51 laptop; i915+Nvidia dual graphics
  using the Nouveau driver.

  The machine has both VGA out and HDMI out; VGA works like a charm but
  HDMI is not even detected. Meaning that none of (xrandr, lspci, aplay,
  get-edid) even reports the HDMI port as present.

  It's not clear to me whether or not this is an X or a kernel issue at
  the heart of it.  I did, however, upgrade recently from 16.04 (where
  this bug was also present!) to see if that made any difference (which
  it did not) and I did try the proprietary Nvidia drivers (340 and 367)
  to see if either of them made a difference (which they did not).

  I can assure you that I've read every relevant-sounding bug report and
  askubuntu question from the past year on this topic without
  discovering any fixes.  Happy to try what needs to be tried.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660949/+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 1660949] Missing required logs.

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1660949

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/1660949

Title:
  No HDMI out on Asus UX51 running 16.10 or 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running Ubuntu 16.10 on an Asus UX51 laptop; i915+Nvidia dual graphics
  using the Nouveau driver.

  The machine has both VGA out and HDMI out; VGA works like a charm but
  HDMI is not even detected. Meaning that none of (xrandr, lspci, aplay,
  get-edid) even reports the HDMI port as present.

  It's not clear to me whether or not this is an X or a kernel issue at
  the heart of it.  I did, however, upgrade recently from 16.04 (where
  this bug was also present!) to see if that made any difference (which
  it did not) and I did try the proprietary Nvidia drivers (340 and 367)
  to see if either of them made a difference (which they did not).

  I can assure you that I've read every relevant-sounding bug report and
  askubuntu question from the past year on this topic without
  discovering any fixes.  Happy to try what needs to be tried.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660949/+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 1528684] Re: Error parsing PCC subspaces from PCCT

[schwobi]

Update:

The system crashes I mentioned are likely unrelated; I noticed a 3rd party 
daemon to randomly hog up all of my CPU.
... Nevermind.

##

Interestingly tough, I observed the 'Error parsing PCC subspaces from
PCCT' also while booting and running from a live-USB on the same system
as mentioned above (with all other /dev/sdX drives unmounted since I
intended to run a fsck check).

Just speculation from a Linux-beginner on my side, but doesn't this
indicate an issue with the motherboard firmware; i.e. conflicts in
either the BIOS/UEFI, MBR, etc.?

-- 
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/1528684

Title:
  Error parsing PCC subspaces from PCCT

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Thinkpad laptop I am seeing this error every time after the boot
  in the dmesg output:

  "Error parsing PCC subspaces from PCCT" (Portable C Compiler)

  The attached log files should reveal more. I have no idea what it
  means but seems serious. Hope you can solve this for once and all?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-22-generic 4.2.0-22.27
  ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael-heuberger   2972 F pulseaudio
   /dev/snd/controlC1:  michael-heuberger   2972 F pulseaudio
  Date: Wed Dec 23 09:36:44 2015
  HibernationDevice: RESUME=UUID=bb8b6759-8fdb-4e4b-879b-7701cb217d2a
  InstallationDate: Installed on 2015-05-22 (214 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20A7006KAU
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic 
root=UUID=b2f035dd-f14c-4a64-8834-5116d2df7864 ro cgroup_enable=memory 
swapaccount=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-22-generic N/A
   linux-backports-modules-4.2.0-22-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-11-15 (36 days ago)
  dmi.bios.date: 11/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GRET42WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20A7006KAU
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGRET42WW(1.19):bd11/20/2014:svnLENOVO:pn20A7006KAU:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7006KAU:rvr0B98417WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20A7006KAU
  dmi.product.version: ThinkPad X1 Carbon 2nd
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1528684/+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 1626436] Re: [4.8 regression] boot has become very slow

[Tomas Janousek]

Are you guys aware of any other patches that went to mainline and may
affect this? I've been hit by this issue since 4.6/4.7-ish days and can
still reproduce it with 4.9.7. The two patches do help, but it's far
from perfect:

4.9.7:
Startup finished in 3.498s (kernel) + 20.462s (userspace) = 23.961s

4.9.7 + 
https://github.com/torvalds/linux/commit/89e364db71fb5e7fc8d93228152abfa67daf35fa
 + 
https://github.com/torvalds/linux/commit/13583c3d3224508582ec03d881d0b68dd3ee8e10:
Startup finished in 3.518s (kernel) + 13.027s (userspace) = 16.546s

4.4.28:
Startup finished in 2.698s (kernel) + 11.761s (userspace) = 14.459s

There's consistently a ~second difference in kernel and another ~second
in userspace. It's not a statistical error, I checked. I think it is
even more pronounced in shutdown, but I don't have exact measurements
from that.

(I don't use a Ubuntu kernel so I apologize for being slightly off-
topic. If you're aware of an upstream issue tracking this, feel free to
refer me to 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/1626436

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

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.4. 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

--

[Kernel-packages] [Bug 1649292] Re: NFS client : permission denied when trying to access subshare, since kernel 4.4.0-31

[Thomas Fili]

This looks very good.
Access to the subshares is possible without permission denied :)

-- 
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/1649292

Title:
  NFS client : permission denied when trying to access subshare, since
  kernel 4.4.0-31

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Triaged

Bug description:
  Similar like Bug #1603719 or Bug #1604396 i got a "Permission denied"
  when trying to access a NFS subshare from our NFSv4 Server.

  I tried this under (K)ubuntu Trusty and Xenial and also with the
  ubuntu based Mint Versions 17.3 Rosa an 18 Sarah.

  Kernel Versions higher than 4.4.0-31 from offical Ubuntu Repository has the 
problem.
  Before 4.4.0-31 not. For safety reasons i used the linux-generic-lts-wily 
meta package

  The 4.4 mainline kernel also works without problem currently
  (4.4.37-040437-generic)

  Our NFS server runs under FreeBSD 11, but same problems to the clients
  with FreeBSD 10.3 and OmniOS r151018.

  All NFS servers use ZFS as the filesystem and NFSv4 with kerberos for
  sharing. For the basic structure we use  also ZFS filesystems.

  So my homefolder is located on the server under
  /apool/AIS/share/home/staff/fili/linux ... each level is a ZFS
  filesystem. On the client nfs share /apool/AIS/share/home is mounted
  under /home/VI

  My posix homedirectory path is /home/VI/staff/fili/linux

  When i try to login i got access to /home/VI/staff/fili ... but when i
  try to access the linux directory / zfs filesystem i got the
  permission denied.

  The fstab options for /home/VI are
  _netdev,rw,sync,sec=krb5,nfsvers=4,clientaddr=w.x.y.z

  I tried also autofs but with the same result.

  ---
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1812 F pulseaudio
   /dev/snd/controlC0:  system 1812 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.5
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 09/24/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1205
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T WS PRO
  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.:bvr1205:bd09/24/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TWSPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system 1876 F pulseaudio
   /dev/snd/controlC0:  system 1876 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=85a1880e-b78e-49d6-888c-342e47405712
  InstallationDate: Installed on 2016-10-17 (56 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp7s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=db11df78-a07d-44b5-8fe3-0f67e7a5ff51 ro
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restric

[Kernel-packages] [Bug 1655002] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From gpicc...@br.ibm.com 2017-02-01 07:03 EDT---
Thanks Tim!

In which versions of Yakkety kernel (4.8) and Xenial's (4.4) this modification 
was included?
Per above comment, you already modified it on both versions, but I'm not sure 
which release I should test that contains the modifications  heheh

Thanks in advance,

Guilherme

-- 
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/1655002

Title:
  Move some kernel modules to the main kernel package (part 2)

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  Hello Canonical,

  there are important kernel modules that are required on POWER systems,
  and they are currently on the linux-image-extra packages.

  So, in this case, every Power system needs to install the -extra
  package, which makes the -extra package required.

  Our suggestion is to add these important modules to the main kernel
  package, so we do not require the installation of the -extra package.

  One round of additions was already completed. But we verified some
  modules we need were missing, so we are hereby requesting a 2nd round
  of module additions to linux-image main package of Xenial and Yakkety
  (and all future releases).

  The list is:


  (AST stack)
  1. ast
  2. i2c-core
  3. sysfillrect
  4. syscopyarea
  5. sysimgblt
  6. fb_sys_fops
  7. drm
  8. drm_kms_helper
  9. ttm
  10. i2c-algo-bit

  11. kvm
  12. kvm_pr
  13. kvm_hv
  14. vmx_crypto
  15. at24
  16. nvmem_core
  17. cmdlinepart
  18. input_leds
  19. uio
  20. uio_pdrv_genirq
  21. ofpart

  (USB stack)
  22. usb_storage
  23. uas
  24. hid
  25. hid_generic
  26. usbhid


  Thanks in advance,

  
  Guilherme

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655002/+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 1660949] [NEW] No HDMI out on Asus UX51 running 16.10 or 16.04

[Nathan Willis]

Public bug reported:

Running Ubuntu 16.10 on an Asus UX51 laptop; i915+Nvidia dual graphics
using the Nouveau driver.

The machine has both VGA out and HDMI out; VGA works like a charm but
HDMI is not even detected. Meaning that none of (xrandr, lspci, aplay,
get-edid) even reports the HDMI port as present.

It's not clear to me whether or not this is an X or a kernel issue at
the heart of it.  I did, however, upgrade recently from 16.04 (where
this bug was also present!) to see if that made any difference (which it
did not) and I did try the proprietary Nvidia drivers (340 and 367) to
see if either of them made a difference (which they did not).

I can assure you that I've read every relevant-sounding bug report and
askubuntu question from the past year on this topic without discovering
any fixes.  Happy to try what needs to be tried.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "lspci output"
   
https://bugs.launchpad.net/bugs/1660949/+attachment/4811692/+files/lspci-vnvn.log

-- 
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/1660949

Title:
  No HDMI out on Asus UX51 running 16.10 or 16.04

Status in linux package in Ubuntu:
  New

Bug description:
  Running Ubuntu 16.10 on an Asus UX51 laptop; i915+Nvidia dual graphics
  using the Nouveau driver.

  The machine has both VGA out and HDMI out; VGA works like a charm but
  HDMI is not even detected. Meaning that none of (xrandr, lspci, aplay,
  get-edid) even reports the HDMI port as present.

  It's not clear to me whether or not this is an X or a kernel issue at
  the heart of it.  I did, however, upgrade recently from 16.04 (where
  this bug was also present!) to see if that made any difference (which
  it did not) and I did try the proprietary Nvidia drivers (340 and 367)
  to see if either of them made a difference (which they did not).

  I can assure you that I've read every relevant-sounding bug report and
  askubuntu question from the past year on this topic without
  discovering any fixes.  Happy to try what needs to be tried.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660949/+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 1601954] Re: ensure all items are included in changelog and standardise packaging

[Thadeu Lima de Souza Cascardo]

** Changed in: linux-meta (Ubuntu Xenial)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1601954

Title:
  ensure all items are included in changelog and standardise packaging

Status in linux-meta package in Ubuntu:
  Fix Released
Status in linux-meta-lts-trusty package in Ubuntu:
  New
Status in linux-meta-lts-xenial package in Ubuntu:
  New
Status in linux-signed package in Ubuntu:
  Fix Released
Status in linux-meta source package in Precise:
  New
Status in linux-meta-lts-trusty source package in Precise:
  New
Status in linux-meta-lts-xenial source package in Precise:
  Invalid
Status in linux-signed source package in Precise:
  New
Status in linux-meta source package in Trusty:
  New
Status in linux-meta-lts-trusty source package in Trusty:
  Invalid
Status in linux-meta-lts-xenial source package in Trusty:
  New
Status in linux-signed source package in Trusty:
  New
Status in linux-meta source package in Xenial:
  Fix Committed
Status in linux-meta-lts-trusty source package in Xenial:
  Invalid
Status in linux-meta-lts-xenial source package in Xenial:
  Invalid
Status in linux-signed source package in Xenial:
  New

Bug description:
  simplify packaging and ensure all items are included in changelog.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1601954/+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 1601954] Re: ensure all items are included in changelog and standardise packaging

[Stefan Bader]

** Also affects: linux-meta-lts-xenial (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux-meta (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-signed (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-meta-lts-xenial (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-meta (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux-signed (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux-meta-lts-xenial (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux-meta (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: linux-signed (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: linux-meta-lts-xenial (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Changed in: linux-meta-lts-xenial (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-meta-lts-xenial (Ubuntu Precise)
   Status: New => Invalid

** Also affects: linux-meta-lts-trusty (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux-meta-lts-trusty (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-meta-lts-trusty (Ubuntu Xenial)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1601954

Title:
  ensure all items are included in changelog and standardise packaging

Status in linux-meta package in Ubuntu:
  Fix Released
Status in linux-meta-lts-trusty package in Ubuntu:
  New
Status in linux-meta-lts-xenial package in Ubuntu:
  New
Status in linux-signed package in Ubuntu:
  Fix Released
Status in linux-meta source package in Precise:
  New
Status in linux-meta-lts-trusty source package in Precise:
  New
Status in linux-meta-lts-xenial source package in Precise:
  Invalid
Status in linux-signed source package in Precise:
  New
Status in linux-meta source package in Trusty:
  New
Status in linux-meta-lts-trusty source package in Trusty:
  Invalid
Status in linux-meta-lts-xenial source package in Trusty:
  New
Status in linux-signed source package in Trusty:
  New
Status in linux-meta source package in Xenial:
  New
Status in linux-meta-lts-trusty source package in Xenial:
  Invalid
Status in linux-meta-lts-xenial source package in Xenial:
  Invalid
Status in linux-signed source package in Xenial:
  New

Bug description:
  simplify packaging and ensure all items are included in changelog.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1601954/+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 1579917] Re: Skylake processor never reaches low power states on X1 Carbon gen 4 with NVMe drive

[Francois Thirioux]

I hit this exact bug running Zesty, kernel 4.9 or 4.10 (or 4.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/1579917

Title:
  Skylake processor never reaches low power states on X1 Carbon gen 4
  with NVMe drive

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Reproducer
  1. Find a skylake machine. - in my case Lenovo x1 carbon gen 4. In my case 
with an NVME drive.
  2. run powertop, and switch to idle stats tab
  3. do nothing. *(as in let the machine idle till the cores regularly reach 
low power states.
  4. Watch the watts fly.  On my  machine the package never gets into any power 
state other than PC2.

  Expected results: PC3-PC10 power states should all show some usage.

  I also tried the mainline build of 4.6-rc7 with no benefits.

  Public conversations about the issue
  https://mjg59.dreamwidth.org/42156.html
  https://mjg59.dreamwidth.org/41713.html

  As far as I can tell having the nvme drive is part of the overall
  problem here.  Please keep this case to skylake + nvme.  Skylake +
  sata appears to have a number of fixes in the 4.6 and newer kernels
  that enable some of the higher sleep states, but I have not tested
  with a sata drive.  Those fixes as of testing 4.6-rc7 do not resolve
  this issue with users who have nvme drives.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.39
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chiluk 3139 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon May  9 15:55:03 2016
  HibernationDevice: RESUME=UUID=4f4ea88e-642e-4be5-bdf0-bbc7f47f5628
  InstallationDate: Installed on 2016-04-25 (14 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b531 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FBCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=249f91bb-7789-41cc-9cc0-8ba25d7f55bb ro quiet splash pcie_aspm=force 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/15/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET37W (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FBCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET37W(1.11):bd03/15/2016:svnLENOVO:pn20FBCTO1WW:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FBCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FBCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579917/+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 1660833] Re: apparmor reference count bug in label_merge_insert()

[John Johansen]

** Changed in: linux (Ubuntu Xenial)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu Yakkety)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu Zesty)
   Status: Incomplete => 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/1660833

Title:
  apparmor reference count bug in label_merge_insert()

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
Status in linux source package in Zesty:
  In Progress

Bug description:
  @new does not have a reference taken locally and should not have its  
  
  reference put locally either.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660833/+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 1660840] Re: apparmor oops in bind_mnt when dev_path lookup fails

[John Johansen]

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Zesty)
   Importance: Undecided
   Status: Incomplete

** Also affects: linux (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Zesty)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu Yakkety)
   Status: New => In Progress

** Changed in: linux (Ubuntu Xenial)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1660840

Title:
  apparmor oops in bind_mnt when dev_path lookup fails

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
Status in linux source package in Zesty:
  In Progress

Bug description:
  Bind mounts can oops when devname lookup fails because the devname is 
  
  unintialized and used in auditing the denial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660840/+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 1660846] Re: apparmor leaking securityfs pin count

[John Johansen]

** Changed in: linux (Ubuntu Xenial)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu Yakkety)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu Zesty)
   Status: Incomplete => 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/1660846

Title:
  apparmor leaking securityfs pin count

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
Status in linux source package in Zesty:
  In Progress

Bug description:
  apparmor is leaking pinfs refcoutn when inode setup fails.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660846/+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 1660834] Re: apparmor label leak when new label is unused

[John Johansen]

** Changed in: linux (Ubuntu Xenial)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu Yakkety)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu Zesty)
   Status: Incomplete => 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/1660834

Title:
  apparmor label leak when new label is unused

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
Status in linux source package in Zesty:
  In Progress

Bug description:
  When a new label is created, it is created with a proxy in a circular 
  
  ref count that is broken by replacement. However if the label is not  
  
  used it will never be replaced and the circular ref count will never  
  
  be broken resulting in a leak.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660834/+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 1660836] Re: apparmor auditing denied access of special apparmor .null fi\ le

[John Johansen]

** Changed in: linux (Ubuntu Xenial)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu Yakkety)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu Zesty)
   Status: Incomplete => 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/1660836

Title:
  apparmor  auditing denied access of special apparmor .null fi\ le

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
Status in linux source package in Zesty:
  In Progress

Bug description:
  When an fd is disallowed from being inherited during exec, instead of 
  
  closed it is duped to a special apparmor/.null file. This prevents the
  
  fd from being reused by another file in case the application expects  
  
  the original file on a give fd (eg stdin/stdout etc). This results in 
  
  a denial message like 
  
  [32375.561535] audit: type=1400 audit(1478825963.441:358): apparmor="DENIED" 
op\
  eration="file_inherit" namespace="root//lxd-t_" 
profile="/sbin/dhc\
  lient" name="/dev/pts/1" pid=16795 comm="dhclient" requested_mask="wr" 
denied_m\
  ask="wr" fsuid=165536 ouid=165536 
  

  
  Further access to the fd is resultin in the rather useless denial message 
  
  of
  
  [32375.566820] audit: type=1400 audit(1478825963.445:359): apparmor="DENIED" 
op\
  eration="file_perm" namespace="root//lxd-t_" 
profile="/sbin/dhclie\
  nt" name="/apparmor/.null" pid=16795 comm="dhclient" requested_mask="w" 
denied_\
  mask="w" fsuid=165536 ouid=0  
  

  
  since we have the original denial, the noisy and useless .null based  
  
  denials can be skipped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660836/+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 1660842] Re: apparmor not checking error if security_pin_fs() fails

[John Johansen]

** Changed in: linux (Ubuntu Xenial)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu Yakkety)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu Zesty)
   Status: Incomplete => 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/1660842

Title:
  apparmor not checking error if security_pin_fs() fails

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
Status in linux source package in Zesty:
  In Progress

Bug description:
  The error condition of security_pin_fs() was not being checked which
  will result can result in an oops or use after free, due to the fs pin
  count not being incremented.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660842/+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 1660845] Re: apparmor reference count leak when securityfs_setup_d_inode\ () fails

[John Johansen]

** Changed in: linux (Ubuntu Xenial)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu Yakkety)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu Zesty)
   Status: Incomplete => 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/1660845

Title:
  apparmor reference count leak when securityfs_setup_d_inode\ () fails

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
Status in linux source package in Zesty:
  In Progress

Bug description:
  apparmor is leaking the parent ns ref count, by directly returning the
  error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660845/+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 1660849] Re: apparmor refcount leak of profile namespace when removing profiles

[John Johansen]

** Changed in: linux (Ubuntu Xenial)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu Yakkety)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu Zesty)
   Status: Incomplete => 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/1660849

Title:
  apparmor refcount leak of profile namespace when removing profiles

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
Status in linux source package in Zesty:
  In Progress

Bug description:
  When doing profile removal, the parent ns of the profiles is taken,
  but the reference isn't being put, resulting in the ns never being
  freed even after it is removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660849/+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