date:20160927

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

2016-09-27 Thread bugproxy

--- Comment From nasas...@in.ibm.com 2016-09-28 00:58 EDT---
(In reply to comment #7)
> Could you try upgrading to the newer 4.8.0-17.19 kernel that was promoted to
> the release pocket last night:
>
> https://launchpad.net/ubuntu/+source/linux/4.8.0-17.19
>

Tested with latest kernel i.e. 4.8.0-17.19, not seeing OOPs or any other
error messages.

root@pkvmhab010:~# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.8.0-17-generic
W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast

root@pkvmhab010:~# apt install -y btrfs-progs/yakkety
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '4.7-1' (Ubuntu:16.10/yakkety [ppc64el]) for 'btrfs-progs'
The following NEW packages will be installed:
btrfs-progs
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/562 kB of archives.
After this operation, 5,656 kB of additional disk space will be used.
Selecting previously unselected package btrfs-progs.
(Reading database ... 130815 files and directories currently installed.)
Preparing to unpack .../btrfs-progs_4.7-1_ppc64el.deb ...
Unpacking btrfs-progs (4.7-1) ...
Processing triggers for initramfs-tools (0.125ubuntu3) ...
update-initramfs: Generating /boot/initrd.img-4.8.0-17-generic
W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast
Processing triggers for libc-bin (2.24-0ubuntu1) ...
Setting up btrfs-progs (4.7-1) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for initramfs-tools (0.125ubuntu3) ...
update-initramfs: Generating /boot/initrd.img-4.8.0-17-generic
W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast
Processing triggers for libc-bin (2.24-0ubuntu1) ...

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

Title:
  [Ubuntu16.10]KV4.8: OOPs while updating initramfs

Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - NAGESWARA R. SASTRY  - 2016-09-22 
06:40:59 ==
  ---Problem Description---
  Try installing btrfs-progs using 'apt install -y btrfs-progs'
  At the time of updating initramfs seeing a 'segfault' and kernel OOPs
   
  Contact Information = nasas...@in.ibm.com 
   
  ---uname output---
  Linux pkvmhab010 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8348-21C 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   # apt install -y btrfs-progs/yakkety
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Selected version '4.7-1' (Ubuntu:16.10/yakkety [ppc64el]) for 'btrfs-progs'
  The following package was automatically installed and is no longer required:
libprotobuf-lite9v5
  Use 'apt autoremove' to remove it.
  The following additional packages will be installed:
liblzo2-2
  The following NEW packages will be installed:
btrfs-progs liblzo2-2
  0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
  Need to get 629 kB of archives.
  After this operation, 5,987 kB of additional disk space will be used.
  Get:1 http://us.ports.ubuntu.com/ubuntu-ports yakkety/main ppc64el liblzo2-2 
ppc64el 2.08-1.2 [67.2 kB]
  Get:2 http://us.ports.ubuntu.com/ubuntu-ports yakkety/main ppc64el 
btrfs-progs ppc64el 4.7-1 [562 kB]
  Fetched 629 kB in 0s (2,416 kB/s)
  Selecting previously unselected package liblzo2-2:ppc64el.
  (Reading database ... 129624 files and directories currently installed.)
  Preparing to unpack .../0-liblzo2-2_2.08-1.2_ppc64el.deb ...
  Unpacking liblzo2-2:ppc64el (2.08-1.2) ...
  Selecting previously unselected package btrfs-progs.
  Preparing to unpack .../1-btrfs-progs_4.7-1_ppc64el.deb ...
  Unpacking btrfs-progs (4.7-1) ...
  Processing triggers for initramfs-tools (0.125ubuntu3) ...
  update-initramfs: Generating /boot/initrd.img-4.8.0-11-generic
  Segmentation fault
   
   
  Oops output:
   [  643.673740] Unable to handle kernel paging request for data at address 
0x0020
  [  643.674688] Faulting instruction address: 0xc0185040
  [  643.675418] Oops: Kernel access of bad area, sig: 11 [#1]
  [  643.676115] SMP NR_CPUS=2048 NUMA PowerNV
  [  643.676650] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
tun bridge stp llc kvm_hv kvm_pr kvm ebtable_filter ebtables ip6table_filter 
ip6_tables iptable_filter evdev joydev at24 ghash_generic gf128mul vmx_crypto 
nvmem_core sg powernv_rng rng_core ip_tables x_tables autofs4 ext4 crc16 jbd2 
fscrypto mbcache dm_mod sr_mod cdrom ses enclosure scsi_transport_sas sd_mod 
hid_generic usbhid hid uas usb_storage xhci_pci bnx2x ast xhci_hcd i2c_algo_bit 
ttm

[Kernel-packages] [Bug 1606178] Re: Can't suspend to ram, since linux3.11 and more

2016-09-27 Thread Launchpad Bug Tracker

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Can't suspend to ram, since linux3.11 and more

Status in linux package in Ubuntu:
  Expired

Bug description:
  I can't suspend to ram since linux 3.11, with ubuntu12.04. Older version 
(3.8, 3.5 etc..) suspend perfectly.
  So, I can't suspend with ubuntu 14.04 and 16.04. :(
  Solutions from here (specially test newer kernels) don't work for me: 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566302
  ASRock N68C-S UCC, with phenomIIx4 processor.

  ~$ uname -a
  Linux DDX-STUDIO 4.4.0-28-generic #47-Ubuntu SMP Fri Jun 24 10:09:13 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux


  ~$ sudo dmidecode -t baseboard
  # dmidecode 2.11
  SMBIOS 2.4 present.

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
Manufacturer: ASRock
Product Name: N68C-S UCC
Version:   
Serial Number:   
Asset Tag:   
Features:
Board is a hosting board
Board is replaceable
Location In Chassis:   
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: XFCE
  Date: Mon Jul 25 12:00:17 2016
  HibernationDevice: RESUME=UUID=3d14e312-ebd4-4129-9183-dcb17519893d
  IwConfig:
   lono wireless extensions.
   
   enp0s7no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0810:0001 Personal Communication Systems, Inc. Dual 
PSX Adaptor
   Bus 002 Device 003: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
   Bus 002 Device 002: ID 056a:00b2 Wacom Co., Ltd Intuos3 9x12
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=7411581c-dc6e-4be3-85ba-bf5ae0c61bbc ro splash quiet vt.handoff=7
  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-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: N68C-S UCC
  dmi.board.vendor: ASRock
  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.:bvrP1.60:bd09/19/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-SUCC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1606178/+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 1600759] Re: Kernel crashes

2016-09-27 Thread Launchpad Bug Tracker

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Kernel crashes

Status in linux package in Ubuntu:
  Expired

Bug description:
  Recently, Ubuntu moved to kernel 4.4.x. On my ASUS X751L, this results
  in my LVDS+external VGA displays to regularly go to sleep/energy
  saving mode (even when being actively used) or to "scramble". As a
  consequence, I reverted to kernel 4.2.0-35-generic. This worked very
  well until I dist-upgraded last thursday. Now, the computer crashes
  regularly, notably when it is (xscreensaver-)locked (mostly while
  executing the "molecule" (OpenGL) screensaver).

  I'm not sure if the crash occurs because of kernel, xscreensaver or an
  mplayer script I run with cron to play a beep every hour (don't ask
  why...).

  This is a critical crash, so I assume there is a security issue
  behind...

  Some extracts of my syslog:

  [computer working...]
  Jul  8 17:55:05 user-X751LAB sSMTP[10137]: Sent mail for r...@gmail.com (221 
2.0.0 closing connection c74sm3677627wme.1 - gsmtp) uid=0 username=root 
outbytes=691
  Jul  8 17:56:01 user-X751LAB CRON[15626]: (user) CMD 
(/home/user/Softs/alarm_bat.sh)
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  [computer rebooted...]
  Jul  8 17:59:44 user-X751LAB rsyslogd: [origin software="rsyslogd" 
swVersion="8.16.0" x-pid="927" x-info="http://www.rsyslog.com;] start
  Jul  8 17:59:44 user-X751LAB rsyslogd-: command 
'KLogPermitNonKernelFacility' is currently not permitted - did you already set 
it via a RainerScript command (v6+ config)? [v8.16.0 try 
http://www.rsyslog.com/e/ ]
  Jul  8 17:59:44 user-X751LAB rsyslogd: rsyslogd's groupid changed to 109

  Jul  8 17:59:44 user-X751LAB sensors[1049]: Adapter: Virtual device
  Jul  8 17:59:44 user-X751LAB sensors[1049]: temp1:+42.0°C  (crit = 
+108.0°C)
  Jul  8 17:59:44 user-X751LAB sensors[1049]: temp2:+27.8°C  (crit = 
+105.0°C)
  Jul  8 17:59:44 user-X751LAB sensors[1049]: temp3:+29.8°C  (crit = 
+105.0°C)
  Jul  8 17:59:44 user-X751LAB sensors[1049]: coretemp-isa-
  Jul  8 17:59:44 user-X751LAB sensors[1049]: Adapter: ISA adapter
  Jul  8 17:59:44 user-X751LAB sensors[1049]: Physical id 0:  +45.0°C  (high = 
+105.0°C, crit = +105.0°C)
  Jul  8 17:59:44 user-X751LAB sensors[1049]: Core 0: +45.0°C  (high = 
+105.0°C, crit = +105.0°C)
  Jul  8 17:59:44 user-X751LAB sensors[1049]: Core 1: +45.0°C  (high = 
+105.0°C, crit = +105.0°C)

  Jul  8 17:59:51 user-X751LAB kernel: [   50.525061] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!
  Jul  8 17:59:51 user-X751LAB kernel: [   50.526028] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!
  Jul  8 17:59:51 user-X751LAB kernel: [   50.526578] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!
  Jul  8 17:59:51 user-X751LAB kernel: [   50.527439] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!
  Jul  8 17:59:51 user-X751LAB kernel: [   50.527866] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!
  Jul  8 17:59:51 user-X751LAB kernel: [   50.528311] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!
  Jul  8 17:59:51 user-X751LAB kernel: [   50.528739] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!
  Jul  8 17:59:51 user-X751LAB kernel: [   50.529184] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!
  Jul  8 17:59:51 user-X751LAB kernel: [   50.529588] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!
  Jul  8 17:59:51 user-X751LAB kernel: [   50.530410] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!
  Jul  8 17:59:51 user-X751LAB kernel: [   50.530827] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!
  Jul  8 17:59:51 user-X751LAB kernel: [   50.530965] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!
  Jul  8 17:59:51 user-X751LAB kernel: [   50.533857] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!
  Jul  8 17:59:51 user-X751LAB kernel: [   50.534398] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!

  Jul  8 18:01:31 user-X751LAB kernel: [  151.296804] [ cut here 
]
  Jul  8 18:01:31 user-X751LAB kernel: [  151.296868] WARNING: CPU: 3 PID: 1095 
at /build/linux-HVWSXI/linux-4.2.0/drivers/gpu/drm/i915/intel_uncore.c:620 
hsw_unclaimed_reg_debug+0x6d/0x90 [i915]()
  Jul  8 18:01:31 user-X751LAB kernel: [  151.296871]

[Kernel-packages] [Bug 1604310] Re: Plugging DisplayPort in L530 causes WiFi disconnection

2016-09-27 Thread Launchpad Bug Tracker

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Plugging DisplayPort in L530 causes WiFi disconnection

Status in linux package in Ubuntu:
  Expired

Bug description:
  I connect running laptop to DisplayPort and wifi is going down (its
  not sending any packages, however the status is still connected for
  2-3 mins).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dawid  1918 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jul 19 10:38:28 2016
  HibernationDevice: RESUME=UUID=2d05849f-f06c-4368-88da-7c7e963ee647
  InstallationDate: Installed on 2015-08-10 (343 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 2478CK2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (85 days ago)
  dmi.bios.date: 10/14/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G3ETA2WW(2.62)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2478CK2
  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: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG3ETA2WW(2.62):bd10/14/2014:svnLENOVO:pn2478CK2:pvrThinkPadL530:rvnLENOVO:rn2478CK2:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2478CK2
  dmi.product.version: ThinkPad L530
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1604310/+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 1602238] Re: Boot hangs on 3.19 /4.2 backported kernels on Trusty

2016-09-27 Thread Launchpad Bug Tracker

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Boot hangs on 3.19 /4.2 backported kernels on Trusty

Status in linux package in Ubuntu:
  Expired

Bug description:
  we have been trying to install 3.19 /4.2 kernels on our DELL machines
  after successful installation on boot the system simply doesn't boot
  to run level (see attachment where its stuck).Some machines of 4.2
  kernel suceed to boot and subsequent reboots fail and drops with the
  same error (See attachment)

  Isolated the issue to be out of grub since grub is able to be detected
  and boot from the mentioned identified device

  Isolated the issue to be out of initramfs since if the modules are
  missing it will not pass to the next stage of boot process

  Issue is seen in a boot stage before the kernel loads completely

  Same issue is not seen in virtual environment (KVM) since the device
  drivers that is needed to boot is completely different compared to the
  baremetals (DELL/HP) suspect something really messy with the ata,ide
  drivers that goes missing but too early to comment

  While booting to recovery mode it just drops to initramfs shell

  Could be possibly related to  #1308264 but i see none assigned to the
  BUG. Too many work arounds suggested in  #1308264 as well in internet
  nothing helped

  VERSION 14.04 (trusty) 
  Kernel Version 3.19 * 4.2 * 
  Works fine with lts-utopic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602238/+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 1603564] Re: USB unplug crashes system - Assuming host is dying, halting host

2016-09-27 Thread Launchpad Bug Tracker

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  USB unplug crashes system - Assuming host is dying, halting host

Status in linux package in Ubuntu:
  Expired

Bug description:
  Occasionally, when I unplug my Android phone (connected over USB), my machine 
crashes.
  At first, I presumed the entire machine had halted since the keyboard and 
mouse stopped working.
  However, I'm still able to SSH in although the screen is completely 
non-responsive. Pressing the power button on the CPU seems to bring up a window 
with Ubuntu's power options.

  My Ubuntu version:
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04
  Codename: trusty

  Kernel version:
  Linux nixentor 3.13.0-91-generic #138-Ubuntu SMP Fri Jun 24 17:00:34 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  I see the following output on dmesg:
  [15563.650717] [ cut here ]
  [15563.650730] WARNING: CPU: 7 PID: 0 at 
/build/linux-3r7mVb/linux-3.13.0/drivers/usb/host/xhci-ring.c:1590 
handle_cmd_completion+0xe56/0xe60()
  [15563.650732] Modules linked in: qcserial usb_wwan usbserial ip6table_filter 
ip6_tables iptable_filter ip_tables x_tables cachefiles cfg80211 rfcomm bnep 
nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache snd_hda_codec_hdmi btusb 
bluetooth usb_storage mxm_wmi x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul 
glue_helper ablk_helper cryptd uvcvideo videobuf2_vmalloc videobuf2_memops 
joydev videobuf2_core snd_hda_codec_realtek videodev snd_usb_audio 
snd_usbmidi_lib 8812au(OX) snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_hda_intel snd_hda_codec snd_seq serio_raw snd_hwdep radeon snd_pcm mei_me 
snd_page_alloc mei snd_seq_device snd_timer snd ttm drm_kms_helper soundcore 
drm parport_pc i2c_algo_bit ppdev lp wmi parport video intel_smartconnect 
shpchp acpi_pad mac_hid hid_generic usbhid hid e1000e ahci psmouse ptp libahci 
pps_core
  [15563.650804] CPU: 7 PID: 0 Comm: swapper/7 Tainted: G   OX 
3.13.0-91-generic #138-Ubuntu
  [15563.650807] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./Z97 Extreme4, BIOS P1.30 05/23/2014
  [15563.650809]   88041edc3d90 81729906 

  [15563.650813]  0009 88041edc3dc8 8106987d 
880404062d60
  [15563.650817]  8804040606b0 0010 0004040606b0 
8804041a
  [15563.650822] Call Trace:
  [15563.650824][] dump_stack+0x64/0x82
  [15563.650836]  [] warn_slowpath_common+0x7d/0xa0
  [15563.650840]  [] warn_slowpath_null+0x1a/0x20
  [15563.650845]  [] handle_cmd_completion+0xe56/0xe60
  [15563.650852]  [] ? check_preempt_curr+0x75/0xa0
  [15563.650857]  [] xhci_irq+0x33b/0xa50
  [15563.650861]  [] ? sched_clock_cpu+0xb5/0x100
  [15563.650865]  [] xhci_msi_irq+0x11/0x20
  [15563.650870]  [] handle_irq_event_percpu+0x4e/0x220
  [15563.650874]  [] handle_irq_event+0x3d/0x60
  [15563.650878]  [] handle_edge_irq+0x77/0x130
  [15563.650886]  [] handle_irq+0x1e/0x30
  [15563.650893]  [] do_IRQ+0x4d/0xc0
  [15563.650898]  [] common_interrupt+0x6d/0x6d
  [15563.650900][] ? cpuidle_enter_state+0x52/0xc0
  [15563.650910]  [] ? cpuidle_enter_state+0x48/0xc0
  [15563.650915]  [] cpuidle_idle_call+0xdc/0x220
  [15563.650921]  [] arch_cpu_idle+0xe/0x30
  [15563.650924]  [] cpu_startup_entry+0xc1/0x2b0
  [15563.650931]  [] start_secondary+0x21d/0x2d0
  [15563.650934] ---[ end trace d9b5447d0ddb440a ]---
  [15565.486066] xhci_hcd :00:14.0: xHCI host not responding to stop 
endpoint command.
  [15565.486075] xhci_hcd :00:14.0: Assuming host is dying, halting host.
  [15565.486120] xhci_hcd :00:14.0: HC died; cleaning up
  [15568.853140] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [15568.853149] xhci_hcd :00:14.0: Abort the command ring, but the xHCI is 
dead.
  [15569.057055] usb 3-14: device not accepting address 92, error -108
  [15574.055575] xhci_hcd :00:14.0: Timeout while waiting for a slot
  [15574.055587] xhci_hcd :00:14.0: Abort the command ring, but the xHCI is 
dead.
  [15579.054167] xhci_hcd :00:14.0: Timeout while waiting for a slot
  [15579.054176] xhci_hcd :00:14.0: Abort the command ring, but the xHCI is 
dead.
  [15584.052706] xhci_hcd :00:14.0: Timeout while waiting for a slot
  [15584.052715] xhci_hcd :00:14.0: Abort the command ring, but the xHCI is 
dead.
  [15584.052841] usb 3-3: USB disconnect, device number 2
  [15584.052854] usb 3-3.2: USB disconnect, device number 13
  [15584.085404] usb 3-4: USB disconnect, device number 3
  [15584.108793] usb 3-6: USB disconnect,

[Kernel-packages] [Bug 1606384] Re: Ubuntu does not boot with systemd

2016-09-27 Thread Launchpad Bug Tracker

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Ubuntu does not boot with systemd

Status in linux package in Ubuntu:
  Expired

Bug description:
  Ubuntu does not boot with systemd, it boots with upstart choice in
  grub.

  Workaround - alt+f1 during start and then start lightdm manually.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC2D0', 
'/dev/snd/pcmC2D8p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', 
'/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/midiC0D3', 
'/dev/snd/midiC0D2', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/midiC0D1', 
'/dev/snd/midiC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: XFCE
  Date: Mon Jul 25 23:52:19 2016
  HibernationDevice: RESUME=UUID=7b4a2bc3-8fd2-4684-b322-2c990980a5ac
  InstallationDate: Installed on 2015-12-13 (225 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: MSI MS-7693
  ProcEnviron:
   LANGUAGE=cs_CZ
   PATH=(custom, no user)
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=520db00b-7805-4f04-8c0c-31acfe536389 ro iommu=soft quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-03-21 (126 days ago)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V22.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970 GAMING (MS-7693)
  dmi.board.vendor: MSI
  dmi.board.version: 4.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 4.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV22.4:bd12/21/2015:svnMSI:pnMS-7693:pvr4.0:rvnMSI:rn970GAMING(MS-7693):rvr4.0:cvnMSI:ct3:cvr4.0:
  dmi.product.name: MS-7693
  dmi.product.version: 4.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1606384/+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 1607006] Re: [Regression] latest kernel boots to distorted graphics (systemd) or does not boot at all (upstart)

2016-09-27 Thread Launchpad Bug Tracker

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [Regression] latest kernel boots to distorted graphics (systemd) or
  does not boot at all (upstart)

Status in linux package in Ubuntu:
  Expired

Bug description:
  Latest kernel boots to distorted graphics (systemd) or does not boot at all 
(upstart).
  Doesn't matter whether I use nouveau or nvidia drivers.
  Graphics is distorted even in tty

  Booting to kernel before that workarounds this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-headers-4.4.0-31 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tomas  3017 F pulseaudio
   /dev/snd/controlC2:  tomas  3017 F pulseaudio
   /dev/snd/controlC0:  tomas  3017 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Jul 27 19:36:14 2016
  HibernationDevice: RESUME=UUID=7b4a2bc3-8fd2-4684-b322-2c990980a5ac
  InstallationDate: Installed on 2016-07-26 (1 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  MachineType: MSI MS-7693
  PackageArchitecture: all
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=2aaf2167-aca2-41be-b11e-930925090f92 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V22.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970 GAMING (MS-7693)
  dmi.board.vendor: MSI
  dmi.board.version: 4.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 4.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV22.4:bd12/21/2015:svnMSI:pnMS-7693:pvr4.0:rvnMSI:rn970GAMING(MS-7693):rvr4.0:cvnMSI:ct3:cvr4.0:
  dmi.product.name: MS-7693
  dmi.product.version: 4.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607006/+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 1607239] Re: mdadm raid gets frozen

2016-09-27 Thread Launchpad Bug Tracker

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  mdadm raid gets frozen

Status in linux package in Ubuntu:
  Expired

Bug description:
  Servers periodically became unresponsive, and report the following
  problem:

  Jul 28 01:26:36 osd1-05 kernel: [1644406.270794] kworker/12:2D 
88085fcd3180 0 25000  2 0x
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270813] Workqueue: dio/bdev 
dio_aio_complete_work
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270821]  88003694dc10 
0046 8805621b4800 00013180
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270830]  88003694dfd8 
00013180 8805621b4800 88003694dd38
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270836]  88003694dd40 
7fff 8805621b4800 a6fd7000
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270842] Call Trace:
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270857]  [] 
schedule+0x29/0x70
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270870]  [] 
schedule_timeout+0x279/0x310
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270880]  [] ? 
md_make_request+0xd5/0x220
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270889]  [] 
wait_for_completion+0xa6/0x150
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270900]  [] ? 
wake_up_state+0x20/0x20
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270906]  [] 
submit_bio_wait+0x5e/0x70
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270914]  [] 
blkdev_issue_flush+0x5a/0x90
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270919]  [] 
blkdev_fsync+0x35/0x50
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270928]  [] 
generic_write_sync+0x48/0x60
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270934]  [] 
dio_complete+0x103/0x120
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270939]  [] 
dio_aio_complete_work+0x21/0x30
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270948]  [] 
process_one_work+0x178/0x470
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270953]  [] ? 
manage_workers.isra.25+0x1f7/0x2e0
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270959]  [] 
worker_thread+0x121/0x410
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270964]  [] ? 
rescuer_thread+0x430/0x430
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270971]  [] 
kthread+0xc9/0xe0
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270976]  [] ? 
kthread_create_on_node+0x1c0/0x1c0
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270984]  [] 
ret_from_fork+0x58/0x90
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270988]  [] ? 
kthread_create_on_node+0x1c0/0x1c0
  Jul 28 01:28:36 osd1-05 kernel: [1644526.317504] INFO: task 
kworker/12:2:25000 blocked for more than 120 seconds.
  Jul 28 01:28:36 osd1-05 kernel: [1644526.326399]   Not tainted 
3.13.0-87-generic #133-Ubuntu

  The actual raid configurations is:
  Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] 
[raid10]
  md0 : active raid1 sdb1[1] sda1[0]
937123648 blocks super 1.2 [2/2] [UU]

  md1 : active raid1 sdb2[1] sda2[0]
39473024 blocks super 1.2 [2/2] [UU]

  md60 : active raid6 sdw[0] sdz[3] sdaa[4] sdx[1] sdy[2]
585689088 blocks super 1.2 level 6, 512k chunk, algorithm 2 [5/5] 
[U]

  unused devices: 

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-87-generic 3.13.0-87.133
  ProcVersionSignature: Ubuntu 3.13.0-87.133-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-87-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 28 06:17 seq
   crw-rw 1 root audio 116, 33 Jul 28 06:17 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.21
  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: Error: [Errno 2] No such file or directory: 'iw'
  CurrentDmesg: [   29.441344] init: plymouth-upstart-bridge main process 
ended, respawning
  Date: Thu Jul 28 07:33:28 2016
  HibernationDevice: RESUME=UUID=a049dacc-3f5b-4282-b507-24d3a7382389
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Supermicro SSG-6047R-E1R36L
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-87-generic 
root=UUID=7052bcbe-dccf-47e4-a7f7-a95a09176541 ro quiet

[Kernel-packages] [Bug 1627074] dwalin (amd64) - tests ran: 136, failed: 0

2016-09-27 Thread Brad Figg

*** This bug is a duplicate of bug 1628204 ***
https://bugs.launchpad.net/bugs/1628204

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/dwalin__4.4.0-40.60__2016-09-28_03-28-00/results-index.html

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

Title:
  linux: 4.4.0-40.60 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-40.60 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/1627074/+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 1628284] Re: yakkety: daily powerpc server ISO fails to find cdrom during install in a VM

2016-09-27 Thread Leann Ogasawara

** Tags added: kernel-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/1628284

Title:
  yakkety: daily powerpc server ISO fails to find cdrom during install
  in a VM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  xenial daily ISO successfully installs using the same method on the
  same system, but yakkety reports:

  Sep 27 21:13:14 cdrom-detect: Searching for Ubuntu installation media...
  Sep 27 21:13:18 cdrom-detect: Devices: ''
  Sep 27 21:13:23 cdrom-detect: Devices: ''
  Sep 27 21:13:24 kernel: [  154.649279] random: crng init done
  Sep 27 21:13:28 cdrom-detect: Devices: ''
  Sep 27 21:13:33 cdrom-detect: Devices: ''
  Sep 27 21:13:38 cdrom-detect: Devices: ''
  Sep 27 21:13:43 cdrom-detect: Devices: ''
  Sep 27 21:13:48 cdrom-detect: Devices: ''
  Sep 27 21:13:53 cdrom-detect: Devices: ''
  Sep 27 21:13:58 cdrom-detect: Devices: ''
  Sep 27 21:14:06 cdrom-detect: CDROM-detect failed; unmounting CD just to be 
sure
  Sep 27 21:14:06 main-menu[267]: WARNING **: Configuring 'cdrom-detect' failed 
with error code 1
  Sep 27 21:14:06 main-menu[267]: WARNING **: Menu item 'cdrom-detect' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628284/+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 1628336] Re: mount-image-callback cannot mount partitioned disk image

2016-09-27 Thread Leann Ogasawara

** Tags added: kernel-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/1628336

Title:
  mount-image-callback cannot mount partitioned disk image

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This fails on 4.8.0-17-generic and passes on

  $ sudo apt-get update
  $ sudo apt-get install -qy cloud-image-utils
  $ wget 
http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-disk1.img
  $ cp xenial-server-cloudimg-amd64-disk1.img disk.img
  $ sudo mount-image-callback xenial-server-cloudimg-amd64-disk1.img -v ls 
_MOUNTPOINT_
  replaced string _MOUNTPOINT_ in arguments arg 1
  waiting on pidfile for /dev/nbd0 in /sys/block/nbd0/pid
  connected xenial-server-cloudimg-amd64-disk1.img (qcow2) to /dev/nbd0. 
waiting for device.
  partitioned disk.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  gave up on waiting for /dev/nbd0p1
  $ echo $?
  1

  
  On an identical system other than 'apt-get install linux-virtual' to get the 
new kernel, you see:

  $ uname -r
  4.4.0-9136-generic

  $ sudo mount-image-callback disk.img -v ls _MOUNTPOINT_
  replaced string _MOUNTPOINT_ in arguments arg 1
  waiting on pidfile for /dev/nbd0 in /sys/block/nbd0/pid
  connected disk.img (qcow2) to /dev/nbd0. waiting for device.
  partitioned disk.
  mounted /dev/nbd0p1 via qemu-nbd /dev/nbd0
  invoking: MOUNTPOINT=/tmp/mount-image-callback.Y8D4lk/mp ls 
/tmp/mount-image-callback.Y8D4lk/mp
  bin   etc lib   media  proc  sbin  sys  var
  boot  homelib64   mntroot  snap  tmp  vmlinuz
  dev   initrd.img  lost+found  optrun   srv   usr
  cmd returned 0. unmounting /tmp/mount-image-callback.Y8D4lk/mp

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-generic 4.8.0-17.19
  ProcVersionSignature: User Name 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 27 19:04 seq
   crw-rw 1 root audio 116, 33 Sep 27 19:04 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.3-0ubuntu7
  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: Wed Sep 28 00:58:49 2016
  Ec2AMI: ami-0438
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=072136f3-5666-4381-83bd-8d7175059be3 ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1~cloud0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-vivid
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1~cloud0:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr12.0.3:cvnQEMU:ct1:cvrpc-i440fx-vivid:
  dmi.product.name: OpenStack Nova
  dmi.product.version: 12.0.3
  dmi.sys.vendor: OpenStack Foundation

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

2016-09-27 Thread 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/1628363

Title:
  VIA VL812 hub stops working with 4.4.0-40.60

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  VIA VL812 hub stops working with 4.4.0-40.60.  Works fine with
  4.4.0-39.59.

  Logs include both boot with 4.4.0-39 *(most recent) and 4.4.0-40
  (previous boot).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.40.42
  ProcVersionSignature: Ubuntu 4.4.0-39.59-generic 4.4.21
  Uname: Linux 4.4.0-39-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep 27 22:48:35 2016
  HibernationDevice: RESUME=UUID=1cb62c08-3564-4d8a-846c-6963690d
  InstallationDate: Installed on 2016-01-15 (256 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160115)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-39-generic 
root=UUID=029afe58-00c3-4872-9556-b3fd990c5cf1 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
scsi_mod.use_blk_mq=y dm_mod.use_blk_mq=y crashkernel=384M-:128M
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-39-generic N/A
   linux-backports-modules-4.4.0-39-generic  N/A
   linux-firmware1.157.4
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: SIX7910J.86A.0594.2013.0806.2241
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DX79SI
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG28808-500
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrSIX7910J.86A.0594.2013.0806.2241:bd08/06/2013:svn:pn:pvr:rvnIntelCorporation:rnDX79SI:rvrAAG28808-500:cvn:ct3:cvr:
  klp-taint: 12289

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628363/+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 1628363] [NEW] VIA VL812 hub stops working with 4.4.0-40.60

2016-09-27 Thread Dave Chiluk

Public bug reported:

VIA VL812 hub stops working with 4.4.0-40.60.  Works fine with
4.4.0-39.59.

Logs include both boot with 4.4.0-39 *(most recent) and 4.4.0-40
(previous boot).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-generic 4.4.0.40.42
ProcVersionSignature: Ubuntu 4.4.0-39.59-generic 4.4.21
Uname: Linux 4.4.0-39-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Sep 27 22:48:35 2016
HibernationDevice: RESUME=UUID=1cb62c08-3564-4d8a-846c-6963690d
InstallationDate: Installed on 2016-01-15 (256 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160115)
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-39-generic 
root=UUID=029afe58-00c3-4872-9556-b3fd990c5cf1 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
scsi_mod.use_blk_mq=y dm_mod.use_blk_mq=y crashkernel=384M-:128M
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-39-generic N/A
 linux-backports-modules-4.4.0-39-generic  N/A
 linux-firmware1.157.4
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/06/2013
dmi.bios.vendor: Intel Corp.
dmi.bios.version: SIX7910J.86A.0594.2013.0806.2241
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DX79SI
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG28808-500
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrSIX7910J.86A.0594.2013.0806.2241:bd08/06/2013:svn:pn:pvr:rvnIntelCorporation:rnDX79SI:rvrAAG28808-500:cvn:ct3:cvr:
klp-taint: 12289

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


** Tags: amd64 apport-bug package-from-proposed third-party-packages 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/1628363

Title:
  VIA VL812 hub stops working with 4.4.0-40.60

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  VIA VL812 hub stops working with 4.4.0-40.60.  Works fine with
  4.4.0-39.59.

  Logs include both boot with 4.4.0-39 *(most recent) and 4.4.0-40
  (previous boot).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.40.42
  ProcVersionSignature: Ubuntu 4.4.0-39.59-generic 4.4.21
  Uname: Linux 4.4.0-39-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep 27 22:48:35 2016
  HibernationDevice: RESUME=UUID=1cb62c08-3564-4d8a-846c-6963690d
  InstallationDate: Installed on 2016-01-15 (256 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160115)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-39-generic 
root=UUID=029afe58-00c3-4872-9556-b3fd990c5cf1 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
scsi_mod.use_blk_mq=y dm_mod.use_blk_mq=y crashkernel=384M-:128M
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-39-generic N/A
   linux-backports-modules-4.4.0-39-generic  N/A
   linux-firmware1.157.4
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: SIX7910J.86A.0594.2013.0806.2241
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DX79SI
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG28808-500
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrSIX7910J.86A.0594.2013.0806.2241:bd08/06/2013:svn:pn:pvr:rvnIntelCorporation:rnDX79SI:rvrAAG28808-500:cvn:ct3:cvr:
  klp-taint: 12289

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628363/+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 1625794] modoc (ppc64el) - tests ran: 81, failed: 19

2016-09-27 Thread Brad Figg

tests ran:  81, failed: 19;
  
http://kernel.ubuntu.com/testing/3.19.0-70.78~14.04.1/modoc__3.19.0-70.78~14.04.1__2016-09-28_03-10-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-70.78~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-70.78~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1625788
  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/1625794/+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 1620317] Re: ISST-LTE:pNV: system ben is hung during ST (nvme)

2016-09-27 Thread bugproxy

--- Comment From gbert...@br.ibm.com 2016-09-27 23:02 EDT---
Hi Canonical,

Our test teams had problems with booting the Ubuntu-4.4.0-40.60 kernel.
They hit an Oops in the NVMe probe path.

My current understanding is that this is already fixed in your kernel by
the fixup commit: e9820e415895 (" UBUNTU: (fix) NVMe: Don't unmap
controller registers on reset") which will be published in kernel
Ubuntu-4.4.0-41.61.

We will try again with that version.

While we are here, I noticed another issue with the backport of
30d6592fce71 (" NVMe: Don't unmap controller registers on reset").
Looks like you are missing the fixup commit that went later into the
4.4.y tree:

81e9a969c441 ('nvme: Call pci_disable_device on the error path") #4.4.y
tree.

I opened Bug 146899 to track this.  It will be mirrored soon.

** Tags removed: verification-needed-xenial
** Tags added: verification-failed-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/1620317

Title:
  ISST-LTE:pNV: system ben is hung during ST (nvme)

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 Released

Bug description:
  On when we are running I/O intensive tasks and CPU addition/removal,
  the block may hang stalling the entire machine.

  The backtrace below is one of the symptoms:

  [12747.49] ---[ end trace b4d8d720952460b5 ]---
  [12747.126885] Trying to free IRQ 357 from IRQ context!
  [12747.146930] [ cut here ]
  [12747.166674] WARNING: at 
/build/linux-iLHNl3/linux-4.4.0/kernel/irq/manage.c:1438
  [12747.184069] Modules linked in: minix nls_iso8859_1 rpcsec_gss_krb5 
auth_rpcgss nfsv4 nfs lockd grace fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) configfs ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) 
mlx4_ib(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) ib_addr(OE) mlx4_en(OE) 
mlx4_core(OE) binfmt_misc xfs joydev input_leds mac_hid ofpart cmdlinepart 
powernv_flash ipmi_powernv mtd ipmi_msghandler at24 opal_prd powernv_rng 
ibmpowernv uio_pdrv_genirq uio sunrpc knem(OE) autofs4 btrfs xor raid6_pq 
hid_generic usbhid hid uas usb_storage nouveau ast bnx2x i2c_algo_bit ttm 
drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mlx5_core(OE) ahci 
drm mdio libcrc32c mlx_compat(OE) libahci vxlan nvme ip6_udp_tunnel udp_tunnel
  [12747.349013] CPU: 80 PID: 0 Comm: swapper/80 Tainted: GW  OEL  
4.4.0-21-generic #37-Ubuntu
  [12747.369046] task: c00f1fab89b0 ti: c00f1fb6c000 task.ti: 
c00f1fb6c000
  [12747.404848] NIP: c0131888 LR: c0131884 CTR: 
300303f0
  [12747.808333] REGS: c00f1fb6e550 TRAP: 0700   Tainted: GW  OEL   
(4.4.0-21-generic)
  [12747.867658] MSR: 900100029033   CR: 2802  
XER: 2000
  [12747.884783] CFAR: c0aea8f4 SOFTE: 1 
  GPR00: c0131884 c00f1fb6e7d0 c15b4200 0028 
  GPR04: c00f2a409c50 c00f2a41b4e0 000f2948 33da 
  GPR08: 0007 c0f8b27c 000f2948 90011003 
  GPR12: 2200 c7b6f800 c00f2a40a938 0100 
  GPR16: c00f1148 3a98   
  GPR20:  d9521008 d95146a0 f000 
  GPR24: c4a19ef0  0003 007d 
  GPR28: 0165 c00eefeb1800 c00eef830600 0165 
  [12748.243270] NIP [c0131888] __free_irq+0x238/0x370
  [12748.254089] LR [c0131884] __free_irq+0x234/0x370
  [12748.269738] Call Trace:
  [12748.286740] [c00f1fb6e7d0] [c0131884] __free_irq+0x234/0x370 
(unreliable)
  [12748.289687] [c00f1fb6e860] [c0131af8] free_irq+0x88/0xb0
  [12748.304594] [c00f1fb6e890] [d9514528] 
nvme_suspend_queue+0xc8/0x150 [nvme]
  [12748.333825] [c00f1fb6e8c0] [d951681c] 
nvme_dev_disable+0x3fc/0x400 [nvme]
  [12748.340913] [c00f1fb6e9a0] [d9516ae4] nvme_timeout+0xe4/0x260 
[nvme]
  [12748.357136] [c00f1fb6ea60] [c0548a34] 
blk_mq_rq_timed_out+0x64/0x110
  [12748.383939] [c00f1fb6ead0] [c054c540] bt_for_each+0x160/0x170
  [12748.399292] [c00f1fb6eb40] [c054d4e8] 
blk_mq_queue_tag_busy_iter+0x78/0x110
  [12748.402665] [c00f1fb6eb90] [c0547358] 
blk_mq_rq_timer+0x48/0x140
  [12748.438649] [c00f1fb6ebd0] [c014a13c] call_timer_fn+0x5c/0x1c0
  [12748.468126] [c00f1fb6ec60] [c014a5fc] 
run_timer_softirq+0x31c/0x3f0
  [12748.483367] [c00f1fb6ed30] [c00beb78] __do_softirq+0x188/0x3e0
  [12748.498378] [c00f1fb6ee20] [c00bf048] irq_exit+0xc8/0x100
  [12748.501048] [c00f1fb6ee40] [c001f954] timer_interrupt+0xa4/0xe0
  [12748.516377]

[Kernel-packages] [Bug 1447909] Re: external mic not detected on machines with alc256 codec

2016-09-27 Thread Hui Wang

sudo apt install alsa-tools

Then you will have this command.

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

Title:
  external mic not detected on machines with alc256 codec

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  This bug is used for tracking, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1447909/+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 1627074] dwalin (amd64) - tests ran: 19, failed: 0

2016-09-27 Thread Brad Figg

*** This bug is a duplicate of bug 1628204 ***
https://bugs.launchpad.net/bugs/1628204

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/dwalin__4.4.0-40.60__2016-09-28_01-49-00/results-index.html

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

Title:
  linux: 4.4.0-40.60 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-40.60 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/1627074/+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 1606103] Re: modeset driver is missing some modes that the intel driver (and Mir) has

2016-09-27 Thread Rocko

Ok, thanks for the info re dpkg-buildpackage.

xf86DefModeSet.c is created by hw/xfree86/common/modeline2c.awk. If you
run dpkg-buildpackage, you'll find it two places:

$ find -name xf86DefModeSet.c
./build-main/hw/xfree86/common/xf86DefModeSet.c
./build-udeb/hw/xfree86/common/xf86DefModeSet.c

xf86DefModeSet.c is built using the files hw/xfree86/common/vesamodes
and hw/xfree86/common/extramodes. extramodes is modified in the build
process by debian/patches/001_fedora_extramodes.patch, so editing
extramodes directly means the patch and therefore build fails. The
packages do build if I add my missing modes to vesamodes and because all
the modes are combined into the one xf86DefModeSet.c, I assume it'll
work for testing purposes.

dpkg-buildpackage builds a whole bunch of debs:

xserver-common_1.18.4-1ubuntu6_all.deb   
xserver-xorg-core-udeb_1.18.4-1ubuntu6_amd64.udeb
xserver-xephyr_1.18.4-1ubuntu6_amd64.deb 
xserver-xorg-dev_1.18.4-1ubuntu6_amd64.deb
xserver-xorg-core_1.18.4-1ubuntu6_amd64.deb  
xserver-xorg-legacy_1.18.4-1ubuntu6_amd64.deb
xserver-xorg-core-dbg_1.18.4-1ubuntu6_amd64.deb  
xserver-xorg-xmir_1.18.4-1ubuntu6_all.deb

It looks like installing xserver-common and xserver-xorg-core should be
sufficient to test my changes, is that correct or do I need the udeb or
any of the other 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/1606103

Title:
  modeset driver is missing some modes that the intel driver (and Mir)
  has

Status in linux package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xorg-server package in Debian:
  New

Bug description:
  My laptop's 4K screen (Dell XPS 15 9550) has these resolutions,
  according to the intel driver:

 3840x2160 60.00 +
 3200x1800 60.00
 2880x1620 60.00
 2560x1440 60.00*
 2048x1536 60.00
 1920x1440 60.00
 1856x1392 60.01
 1792x1344 60.01
 2048x1152 60.00
 1920x1200 59.95
 1920x1080 60.0059.93
 1600x1200 60.00
 1680x1050 59.9559.88
 1600x1024 60.17
 1400x1050 59.98
 1600x900  60.00
 1280x1024 60.02
 1440x900  59.89
 1280x960  60.00
 1368x768  60.00
 1360x768  59.8059.96
 1152x864  60.00
 1280x720  60.00
 1024x768  60.00
 1024x576  60.00
 960x540   60.00
 800x600   60.3256.25
 864x486   60.00
 640x480   59.94
 720x405   60.00
 640x360   60.00

  But with the modeset driver, it detects these resolutions:

 3840x2160 60.00*+
 2048x1536 60.00
 1920x1440 60.00
 1856x1392 60.01
 1792x1344 60.01
 1920x1200 59.95
 1920x1080 59.93
 1600x1200 60.00
 1680x1050 59.9559.88
 1600x1024 60.17
 1400x1050 59.98
 1280x1024 60.02
 1440x900  59.89
 1280x960  60.00
 1360x768  59.8059.96
 1152x864  60.00
 1024x768  60.0460.00
 960x720   60.00
 928x696   60.05
 896x672   60.01
 960x600   60.00
 960x540   59.99
 800x600   60.0060.3256.25
 840x525   60.0159.88
 800x512   60.17
 700x525   59.98
 640x512   60.02
 720x450   59.89
 640x480   60.0059.94
 680x384   59.8059.96
 576x432   60.06
 512x384   60.00
 400x300   60.3256.34
 320x240   60.05

  It seems to be picking up some extra super-low resolutions (like
  320x240) but not the higher 16:9 resolutions. I normally run it at
  2560x1440, because the native resolution is too high with an external
  monitor attached at 1980x1080, but I can't do this with the modeset
  driver.

  I'm reporting this as per https://tjaalton.wordpress.com/2016/07/23
  /intel-graphics-gen4-and-newer-now-defaults-to-modesetting-driver-
  on-x/, although note that there are several inaccuracies in that post
  - there's a typo in ‘cp /usr/share/doc/xserver-xoeg-video-
  intel/xorg.conf /etc/X11‘, the file doesn't exist in any case if you
  correct the typo, and I couldn't use ubuntu-bug to report this against
  xorg-xserver, because ubuntu-bug said the xorg-xserver package doesn't
  exist.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg-server-source (not installed)
  Uname: Linux 4.6.4-040604-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Jul 25 11:09:00 2016
  DistUpgraded: 2016-07-25

[Kernel-packages] [Bug 1607920] Re: zfs services fail on firstboot if zfs-utils is integrated into the deployment image

2016-09-27 Thread Eric Desrochers

** Description changed:

  [Impact]
  
   * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.
  
   * Output from systemd -
  sudo systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
  ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning
  ● zfs-mount.service loaded failed failed Mount ZFS filesystems
  
   * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted before
  showing as clean.
  
   * This failure is due to zfs services starting up before /etc/mtab has
  a chance to be symlinked to /proc/mounts.
  
  [Test Case]
  
   1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it.
   2. Boot machine
   3. Check systemctl --failed.
  
  [Regression Potential]
  
-  * none expected, patch has been merged upstream and ubuntu package has
- been tested by people from the community.
+  * none expected, patch has been intensively tested by the zfs test
+ scripts and then merged upstream.
+ 
+  * A ubuntu package has been tested as well by a user of the community
+ facing this bug, and confirmed it fixes the problem (see comment #7).
  
  [Other Info]
  
-  * Author: Eric Desrochers 
-  
-  * Origin: 
https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a
+  * Author: Eric Desrochers 
  
-  * Bug: https://github.com/zfsonlinux/zfs/issues/4680
+  * Origin:
+ 
https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a
+ 
+  * Bug: https://github.com/zfsonlinux/zfs/issues/4680

** Tags added: sts-sponsor sts-sru

** Description changed:

  [Impact]
  
   * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.
  
   * Output from systemd -
  sudo systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
  ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning
  ● zfs-mount.service loaded failed failed Mount ZFS filesystems
  
   * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted before
  showing as clean.
  
   * This failure is due to zfs services starting up before /etc/mtab has
  a chance to be symlinked to /proc/mounts.
  
  [Test Case]
  
   1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it.
   2. Boot machine
   3. Check systemctl --failed.
  
  [Regression Potential]
  
   * none expected, patch has been intensively tested by the zfs test
  scripts and then merged upstream.
  
-  * A ubuntu package has been tested as well by a user of the community
+  * A ubuntu package has been tested as well by a user of the community
  facing this bug, and confirmed it fixes the problem (see comment #7).
  
  [Other Info]
  
   * Author: Eric Desrochers 
  
-  * Origin:
+  * Upstream commit :
  
https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a
  
-  * Bug: https://github.com/zfsonlinux/zfs/issues/4680
+  * Upstream bug: https://github.com/zfsonlinux/zfs/issues/4680

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

Title:
  zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image

Status in sysvinit package in Ubuntu:
  Won't Fix
Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.

   * Output from systemd -
  sudo systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
  ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning
  ● zfs-mount.service loaded failed failed Mount ZFS filesystems

   * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted
  before showing as clean.

   * This failure is due to zfs services starting up before /etc/mtab
  has a chance to be symlinked to /proc/mounts.

  [Test Case]

   1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it.
   2. Boot machine
   3. Check systemctl --failed.

  [Regression Potential]

   * none expected, patch has been intensively tested by the zfs test
  scripts and then merged upstream.

   * A ubuntu package has been tested as well by a user of the community
  facing this bug, and confirmed it fixes the problem (see comment #7).

  [Other Info]

   * Author: Eric Desrochers 

   * Upstream commit :
  
https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a

   * Upstream bug: https://github.com/zfsonlinux/zfs/issues/4680

To manage notifications about this bug go to:

Re: [Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

2016-09-27 Thread Barry Warsaw

On Sep 27, 2016, at 11:12 PM, Joseph Salisbury wrote:

>I built a mainline kenel with commit
>2deb4be28077638591fe5fc593b7f8aabc140f42 reverted.
>
>Can you test this kernel to see if it also has the new desktop issue?

That one gets a little farther but ultimately doesn't give me a desktop
either.

The previous kernels, once I logged in all I was left with was the lightdm
wallpaper.  With this kernel, the screen goes black, but that's it.  No
response on the desktop to mouse or keyboard clicks, but ssh works and htop
doesn't show any abnormal stats.

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

Title:
  4.8.0 kernels do not complete boot process on VM

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

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

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

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

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

2016-09-27 Thread 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/1628336

Title:
  mount-image-callback cannot mount partitioned disk image

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This fails on 4.8.0-17-generic and passes on

  $ sudo apt-get update
  $ sudo apt-get install -qy cloud-image-utils
  $ wget 
http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-disk1.img
  $ cp xenial-server-cloudimg-amd64-disk1.img disk.img
  $ sudo mount-image-callback xenial-server-cloudimg-amd64-disk1.img -v ls 
_MOUNTPOINT_
  replaced string _MOUNTPOINT_ in arguments arg 1
  waiting on pidfile for /dev/nbd0 in /sys/block/nbd0/pid
  connected xenial-server-cloudimg-amd64-disk1.img (qcow2) to /dev/nbd0. 
waiting for device.
  partitioned disk.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  gave up on waiting for /dev/nbd0p1
  $ echo $?
  1

  
  On an identical system other than 'apt-get install linux-virtual' to get the 
new kernel, you see:

  $ uname -r
  4.4.0-9136-generic

  $ sudo mount-image-callback disk.img -v ls _MOUNTPOINT_
  replaced string _MOUNTPOINT_ in arguments arg 1
  waiting on pidfile for /dev/nbd0 in /sys/block/nbd0/pid
  connected disk.img (qcow2) to /dev/nbd0. waiting for device.
  partitioned disk.
  mounted /dev/nbd0p1 via qemu-nbd /dev/nbd0
  invoking: MOUNTPOINT=/tmp/mount-image-callback.Y8D4lk/mp ls 
/tmp/mount-image-callback.Y8D4lk/mp
  bin   etc lib   media  proc  sbin  sys  var
  boot  homelib64   mntroot  snap  tmp  vmlinuz
  dev   initrd.img  lost+found  optrun   srv   usr
  cmd returned 0. unmounting /tmp/mount-image-callback.Y8D4lk/mp

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-generic 4.8.0-17.19
  ProcVersionSignature: User Name 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 27 19:04 seq
   crw-rw 1 root audio 116, 33 Sep 27 19:04 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.3-0ubuntu7
  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: Wed Sep 28 00:58:49 2016
  Ec2AMI: ami-0438
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=072136f3-5666-4381-83bd-8d7175059be3 ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1~cloud0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-vivid
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1~cloud0:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr12.0.3:cvnQEMU:ct1:cvrpc-i440fx-vivid:
  dmi.product.name: OpenStack Nova
  dmi.product.version: 12.0.3
  dmi.sys.vendor: OpenStack Foundation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628336/+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 1628336] [NEW] mount-image-callback cannot mount partitioned disk image

2016-09-27 Thread Scott Moser

Public bug reported:

This fails on 4.8.0-17-generic and passes on

$ sudo apt-get update
$ sudo apt-get install -qy cloud-image-utils
$ wget 
http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-disk1.img
$ cp xenial-server-cloudimg-amd64-disk1.img disk.img
$ sudo mount-image-callback xenial-server-cloudimg-amd64-disk1.img -v ls 
_MOUNTPOINT_
replaced string _MOUNTPOINT_ in arguments arg 1
waiting on pidfile for /dev/nbd0 in /sys/block/nbd0/pid
connected xenial-server-cloudimg-amd64-disk1.img (qcow2) to /dev/nbd0. waiting 
for device.
partitioned disk.
waiting for /dev/nbd0p1 part=1 to be ready.
waiting for /dev/nbd0p1 part=1 to be ready.
waiting for /dev/nbd0p1 part=1 to be ready.
waiting for /dev/nbd0p1 part=1 to be ready.
waiting for /dev/nbd0p1 part=1 to be ready.
waiting for /dev/nbd0p1 part=1 to be ready.
waiting for /dev/nbd0p1 part=1 to be ready.
waiting for /dev/nbd0p1 part=1 to be ready.
waiting for /dev/nbd0p1 part=1 to be ready.
gave up on waiting for /dev/nbd0p1
$ echo $?
1


On an identical system other than 'apt-get install linux-virtual' to get the 
new kernel, you see:

$ uname -r
4.4.0-9136-generic

$ sudo mount-image-callback disk.img -v ls _MOUNTPOINT_
replaced string _MOUNTPOINT_ in arguments arg 1
waiting on pidfile for /dev/nbd0 in /sys/block/nbd0/pid
connected disk.img (qcow2) to /dev/nbd0. waiting for device.
partitioned disk.
mounted /dev/nbd0p1 via qemu-nbd /dev/nbd0
invoking: MOUNTPOINT=/tmp/mount-image-callback.Y8D4lk/mp ls 
/tmp/mount-image-callback.Y8D4lk/mp
bin   etc lib   media  proc  sbin  sys  var
boot  homelib64   mntroot  snap  tmp  vmlinuz
dev   initrd.img  lost+found  optrun   srv   usr
cmd returned 0. unmounting /tmp/mount-image-callback.Y8D4lk/mp

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-17-generic 4.8.0-17.19
ProcVersionSignature: User Name 4.8.0-17.19-generic 4.8.0-rc7
Uname: Linux 4.8.0-17-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Sep 27 19:04 seq
 crw-rw 1 root audio 116, 33 Sep 27 19:04 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.3-0ubuntu7
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: Wed Sep 28 00:58:49 2016
Ec2AMI: ami-0438
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: OpenStack Foundation OpenStack Nova
PciMultimedia:
 
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=072136f3-5666-4381-83bd-8d7175059be3 ro console=tty1 console=ttyS0
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-17-generic N/A
 linux-backports-modules-4.8.0-17-generic  N/A
 linux-firmwareN/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: Ubuntu-1.8.2-1ubuntu1~cloud0
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-vivid
dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1~cloud0:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr12.0.3:cvnQEMU:ct1:cvrpc-i440fx-vivid:
dmi.product.name: OpenStack Nova
dmi.product.version: 12.0.3
dmi.sys.vendor: OpenStack Foundation

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


** Tags: amd64 apport-bug ec2-images yakkety

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

Title:
  mount-image-callback cannot mount partitioned disk image

Status in linux package in Ubuntu:
  New

Bug description:
  This fails on 4.8.0-17-generic and passes on

  $ sudo apt-get update
  $ sudo apt-get install -qy cloud-image-utils
  $ wget 
http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-disk1.img
  $ cp xenial-server-cloudimg-amd64-disk1.img disk.img
  $ sudo mount-image-callback xenial-server-cloudimg-amd64-disk1.img -v ls 
_MOUNTPOINT_
  replaced string _MOUNTPOINT_ in arguments arg 1
  waiting on pidfile for /dev/nbd0 in /sys/block/nbd0/pid
  connected xenial-server-cloudimg-amd64-disk1.img (qcow2) to /dev/nbd0. 
waiting for device.
  partitioned disk.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.

[Kernel-packages] [Bug 1628336] Re: mount-image-callback cannot mount partitioned disk image

2016-09-27 Thread Scott Moser

Attaching a script that shows the failure without downloading an image.


** Attachment added: "script to show failure"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628336/+attachment/4749866/+files/show-fail.sh

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

Title:
  mount-image-callback cannot mount partitioned disk image

Status in linux package in Ubuntu:
  New

Bug description:
  This fails on 4.8.0-17-generic and passes on

  $ sudo apt-get update
  $ sudo apt-get install -qy cloud-image-utils
  $ wget 
http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-disk1.img
  $ cp xenial-server-cloudimg-amd64-disk1.img disk.img
  $ sudo mount-image-callback xenial-server-cloudimg-amd64-disk1.img -v ls 
_MOUNTPOINT_
  replaced string _MOUNTPOINT_ in arguments arg 1
  waiting on pidfile for /dev/nbd0 in /sys/block/nbd0/pid
  connected xenial-server-cloudimg-amd64-disk1.img (qcow2) to /dev/nbd0. 
waiting for device.
  partitioned disk.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  gave up on waiting for /dev/nbd0p1
  $ echo $?
  1

  
  On an identical system other than 'apt-get install linux-virtual' to get the 
new kernel, you see:

  $ uname -r
  4.4.0-9136-generic

  $ sudo mount-image-callback disk.img -v ls _MOUNTPOINT_
  replaced string _MOUNTPOINT_ in arguments arg 1
  waiting on pidfile for /dev/nbd0 in /sys/block/nbd0/pid
  connected disk.img (qcow2) to /dev/nbd0. waiting for device.
  partitioned disk.
  mounted /dev/nbd0p1 via qemu-nbd /dev/nbd0
  invoking: MOUNTPOINT=/tmp/mount-image-callback.Y8D4lk/mp ls 
/tmp/mount-image-callback.Y8D4lk/mp
  bin   etc lib   media  proc  sbin  sys  var
  boot  homelib64   mntroot  snap  tmp  vmlinuz
  dev   initrd.img  lost+found  optrun   srv   usr
  cmd returned 0. unmounting /tmp/mount-image-callback.Y8D4lk/mp

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-generic 4.8.0-17.19
  ProcVersionSignature: User Name 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 27 19:04 seq
   crw-rw 1 root audio 116, 33 Sep 27 19:04 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.3-0ubuntu7
  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: Wed Sep 28 00:58:49 2016
  Ec2AMI: ami-0438
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=072136f3-5666-4381-83bd-8d7175059be3 ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1~cloud0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-vivid
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1~cloud0:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr12.0.3:cvnQEMU:ct1:cvrpc-i440fx-vivid:
  dmi.product.name: OpenStack Nova
  dmi.product.version: 12.0.3
  dmi.sys.vendor: OpenStack Foundation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628336/+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 1627074] dwalin (amd64) - tests ran: 35, failed: 0

2016-09-27 Thread Brad Figg

*** This bug is a duplicate of bug 1628204 ***
https://bugs.launchpad.net/bugs/1628204

tests ran:  35, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/dwalin__4.4.0-40.60__2016-09-27_23-36-00/results-index.html

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

Title:
  linux: 4.4.0-40.60 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-40.60 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/1627074/+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 1607920] Re: zfs services fail on firstboot if zfs-utils is integrated into the deployment image

2016-09-27 Thread Eric Desrochers

Thanks scotte for the feedbacks, I will now start the SRU process.

Eric

** Description changed:

  [Impact]
  
-  * zfs services fail on firstboot if zfs-utils is integrated into the
+  * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.
  
-  * Output from systemd - 
- sudo systemctl --failed 
- UNIT LOAD ACTIVE SUB DESCRIPTION 
- ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning 
- ● zfs-mount.service loaded failed failed Mount ZFS filesystems 
+  * Output from systemd -
+ sudo systemctl --failed
+ UNIT LOAD ACTIVE SUB DESCRIPTION
+ ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning
+ ● zfs-mount.service loaded failed failed Mount ZFS filesystems
  
-  * This is particularly frustrating for users who use automated
+  * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted before
  showing as clean.
  
-  * This failure is due to zfs services starting up before /etc/mtab has
+  * This failure is due to zfs services starting up before /etc/mtab has
  a chance to be symlinked to /proc/mounts.
  
  [Test Case]
  
-  1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it. 
-  2. Boot machine
-  3. Check systemctl --failed.
+  1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it.
+  2. Boot machine
+  3. Check systemctl --failed.
  
  [Regression Potential]
  
-  *
+  * none expected, patch has been merged upstream and ubuntu package has
+ been tested by people from the community.
+ 
+ [Other Info]
+ 
+  * Author: Eric Desrochers 
   
- [Other Info]
-  
-  * This can likely be resolved in the systemd init scripts, by modifying 
zfs-linux to depend on /proc/mounts instead, or inclusion of 
/lib/init/mount-functions.sh in initscripts (sysvinit).
+  * Origin: 
https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a
+ 
+  * Bug: https://github.com/zfsonlinux/zfs/issues/4680

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

Title:
  zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image

Status in sysvinit package in Ubuntu:
  Won't Fix
Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.

   * Output from systemd -
  sudo systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
  ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning
  ● zfs-mount.service loaded failed failed Mount ZFS filesystems

   * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted
  before showing as clean.

   * This failure is due to zfs services starting up before /etc/mtab
  has a chance to be symlinked to /proc/mounts.

  [Test Case]

   1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it.
   2. Boot machine
   3. Check systemctl --failed.

  [Regression Potential]

   * none expected, patch has been merged upstream and ubuntu package
  has been tested by people from the community.

  [Other Info]

   * Author: Eric Desrochers 
   
   * Origin: 
https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a

   * Bug: https://github.com/zfsonlinux/zfs/issues/4680

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1607920/+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 1607920] Re: zfs services fail on firstboot if zfs-utils is integrated into the deployment image

2016-09-27 Thread scotte

I tested this using my reproduction method in AWS EC2 with a test
package/PPA provided by Eric@Ubuntu (slashd) containing the commit
referenced in comment #6.

All looks good now - systemd units for ZFS no longer fail. Thanks for
moving this along!

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

Title:
  zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image

Status in sysvinit package in Ubuntu:
  Won't Fix
Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.

   * Output from systemd - 
  sudo systemctl --failed 
  UNIT LOAD ACTIVE SUB DESCRIPTION 
  ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning 
  ● zfs-mount.service loaded failed failed Mount ZFS filesystems 

   * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted
  before showing as clean.

   * This failure is due to zfs services starting up before /etc/mtab
  has a chance to be symlinked to /proc/mounts.

  [Test Case]

   1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it. 
   2. Boot machine
   3. Check systemctl --failed.

  [Regression Potential]

   *
   
  [Other Info]
   
   * This can likely be resolved in the systemd init scripts, by modifying 
zfs-linux to depend on /proc/mounts instead, or inclusion of 
/lib/init/mount-functions.sh in initscripts (sysvinit).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1607920/+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 1618151] Re: ISST-LTE: system dropped into xmon at pcibios_release_device+0x5c/0x80 during running dlpar test on monklp3

2016-09-27 Thread bugproxy

--- Comment From mauri...@br.ibm.com 2016-09-27 19:58 EDT---
This is verified successfully.
Updating tags.

The controller release function is only called when the last reference
to one of its devices (eg, disks) is dropped.

# echo 'func pcibios_free_controller_deferred +pf' >
/sys/kernel/debug/dynamic_debug/control

# lspci | grep Fibre
0021:01:00.0 Fibre Channel: Emulex Corporation Lancer-X: LightPulse Fibre 
Channel Host Adapter (rev 30)
0021:01:00.1 Fibre Channel: Emulex Corporation Lancer-X: LightPulse Fibre 
Channel Host Adapter (rev 30)

# ls -ld /sys/block/sd* | grep -m1 0021:01:00.0
<...> /sys/block/sdav -> ../devices/pci0021:01/0021:01:00.0/<...>

# ls -ld /sys/block/sd* | grep -m1 0021:01:00.1
<...> /sys/block/sdaa -> ../devices/pci0021:01/0021:01:00.1/<...>

# cat >/dev/sdav & pid1=$!
# cat >/dev/sdaa & pid2=$!

# dmesg -c >/dev/null

# drmgr -w 5 -d 1 -c phb -s 'PHB 33' -r
Validating PHB DLPAR capability...yes.

# dmesg -c | tail -n3
[11629.473248] iommu: Removing device 0021:01:00.0 from group 1
[11639.480792] pci_bus 0021:01: busn_res: [bus 01-ff] is released
[11639.480874] rpadlpar_io: slot PHB 33 removed

# kill -9 $pid1
# dmesg -c
[11682.255067] scsi 5:0:0:1: rdac: Detached

# kill -9 $pid2
# dmesg -c
[11695.380191] scsi 4:0:1:2: rdac: Detached
[11695.380359] pcibios_free_controller_deferred: domain 33, dynamic 1

** Tags removed: verification-needed-xenial
** Tags added: verification-done-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/1618151

Title:
  ISST-LTE: system dropped into xmon at pcibios_release_device+0x5c/0x80
  during running dlpar test on monklp3

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

Bug description:
  monklp3 is installed with ubuntu 14.04.4. System crashed and dropped
  into xmon at pcibios_release_device+0x5c/0x80 during running dlpar
  test(CPU, MEM and SLOT).

  The output from vterm:

  [ 1333.379900] lpfc 0005:a0:00.1: 2:1303 Link Up Event x1 received Data: x1 
x1 x20 x0 x0 x0 0
  [ 1334.522315] Unable to handle kernel paging request for instruction fetch
  [ 1334.522340] Faulting instruction address: 0x2f30613a35303030
  cpu 0x42: Vector: 400 (Instruction Access) at [c002b35fedd0]
  pc: 2f30613a35303030
  lr: c0047a9c: pcibios_release_device+0x5c/0x80
  sp: c002b35ff050
 msr: 800140009033
current = 0xc002b35290d0
paca= 0xc7b07300 softe: 0irq_happened: 0x01
  pid   = 5756, comm = multipathd
  enter ? for help
  [link register   ] c0047a9c pcibios_release_device+0x5c/0x80
  [c002b35ff050] c0047a78 pcibios_release_device+0x38/0x80 
(unreliable)
  [c002b35ff080] c0585ed4 pci_release_dev+0x84/0xd0
  [c002b35ff0b0] c066f210 device_release+0x60/0xf0
  [c002b35ff130] c0532a44 kobject_cleanup+0xd4/0x240
  [c002b35ff1b0] c066f8a4 put_device+0x34/0x50
  [c002b35ff1e0] c06f3f78 scsi_host_dev_release+0x118/0x180
  [c002b35ff220] c066f210 device_release+0x60/0xf0
  [c002b35ff2a0] c0532a44 kobject_cleanup+0xd4/0x240
  [c002b35ff320] c066f8a4 put_device+0x34/0x50
  [c002b35ff350] d533096c fc_rport_dev_release+0x2c/0x50 
[scsi_transport_fc]
  [c002b35ff380] c066f210 device_release+0x60/0xf0
  [c002b35ff400] c0532a44 kobject_cleanup+0xd4/0x240
  [c002b35ff480] c066f8a4 put_device+0x34/0x50
  [c002b35ff4b0] c0700550 scsi_target_dev_release+0x40/0x60
  [c002b35ff4e0] c066f210 device_release+0x60/0xf0
  [c002b35ff560] c0532a44 kobject_cleanup+0xd4/0x240
  [c002b35ff5e0] c066f8a4 put_device+0x34/0x50
  [c002b35ff610] c0704e68 
scsi_device_dev_release_usercontext+0x178/0x1b0
  [c002b35ff670] c00d69d4 execute_in_process_context+0xa4/0xd0
  [c002b35ff6a0] c0704cd4 scsi_device_dev_release+0x34/0x50
  [c002b35ff6d0] c066f210 device_release+0x60/0xf0
  [c002b35ff750] c0532a44 kobject_cleanup+0xd4/0x240
  [c002b35ff7d0] c066f8a4 put_device+0x34/0x50
  [c002b35ff800] c06f1a60 scsi_device_put+0x40/0x60
  [c002b35ff830] c0716568 scsi_disk_put+0x58/0x90
  [c002b35ff870] c0311398 __blkdev_put+0x278/0x2e0
  [c002b35ff8f0] c08861bc dm_put_table_device+0xcc/0x140
  [c002b35ff930] c088b12c dm_put_device+0x9c/0x130
  [c002b35ff9b0] d5f31864 free_priority_group+0xe4/0x140 
[dm_multipath]
  [c002b35ffa10] d5f31944 free_multipath+0x84/0xf0 [dm_multipath]
  [c002b35ffa60] c088c310 dm_table_destroy+0xb0/0x1a0
  [c002b35ffaf0] c0891b9c

[Kernel-packages] [Bug 1625794] modoc (ppc64el) - tests ran: 19, failed: 6

2016-09-27 Thread Brad Figg

tests ran:  19, failed: 6;
  
http://kernel.ubuntu.com/testing/3.19.0-70.78~14.04.1/modoc__3.19.0-70.78~14.04.1__2016-09-27_23-23-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-70.78~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-70.78~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1625788
  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/1625794/+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 1628284] Re: yakkety: daily powerpc server ISO fails to find cdrom during install in a VM

2016-09-27 Thread Nish Aravamudan

I'm not able to run apport-collect from the installer shell.

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

Title:
  yakkety: daily powerpc server ISO fails to find cdrom during install
  in a VM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  xenial daily ISO successfully installs using the same method on the
  same system, but yakkety reports:

  Sep 27 21:13:14 cdrom-detect: Searching for Ubuntu installation media...
  Sep 27 21:13:18 cdrom-detect: Devices: ''
  Sep 27 21:13:23 cdrom-detect: Devices: ''
  Sep 27 21:13:24 kernel: [  154.649279] random: crng init done
  Sep 27 21:13:28 cdrom-detect: Devices: ''
  Sep 27 21:13:33 cdrom-detect: Devices: ''
  Sep 27 21:13:38 cdrom-detect: Devices: ''
  Sep 27 21:13:43 cdrom-detect: Devices: ''
  Sep 27 21:13:48 cdrom-detect: Devices: ''
  Sep 27 21:13:53 cdrom-detect: Devices: ''
  Sep 27 21:13:58 cdrom-detect: Devices: ''
  Sep 27 21:14:06 cdrom-detect: CDROM-detect failed; unmounting CD just to be 
sure
  Sep 27 21:14:06 main-menu[267]: WARNING **: Configuring 'cdrom-detect' failed 
with error code 1
  Sep 27 21:14:06 main-menu[267]: WARNING **: Menu item 'cdrom-detect' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628284/+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 1626413] Re: My laptop doesn't resume when lid is opended

2016-09-27 Thread Alberto Salvia Novella

** Changed in: linux (Ubuntu)
   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/1626413

Title:
  My laptop doesn't resume when lid is opended

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have HP ProBook 440 G3.

  my cat > /proc/acpi/wakeup

  DeviceS-state   Status   Sysfs node
  PEG1S4*disabled
  PEGPS4*disabled
  PEG2S4*disabled
  PEGPS4*disabled
  PEG0S4*disabled
  PEGPS4*disabled
  GLANS4*disabled
  XHC S3*enabled   pci::00:14.0
  XDCIS4*disabled
  HDASS4*disabled  pci::00:1f.3
  RP01S4*disabled
  PXSXS4*disabled
  RP02S4*disabled
  PXSXS4*disabled
  RP03S4*disabled
  PXSXS4*disabled
  RP04S4*disabled
  PXSXS4*disabled
  RP05S4*disabled  pci::00:1c.0
  PXSXS4*disabled  pci::01:00.0
  RP06S4*disabled  pci::00:1c.5
  PXSXS4*disabled  pci::02:00.0
  RP07S4*disabled
  PXSXS4*disabled
  RP08S4*disabled
  PXSXS4*disabled
  RP09S4*disabled  pci::00:1d.0
  PXSXS4*disabled  pci::03:00.0
*disabled  platform:rtsx_pci_sdmmc.0
*disabled  platform:rtsx_pci_ms.0
  RP10S4*disabled
  PXSXS4*disabled
  RP11S4*disabled
  PXSXS4*disabled
  RP12S4*disabled
  PXSXS4*disabled
  RP13S4*disabled
  PXSXS4*disabled
  RP14S4*disabled
  PXSXS4*disabled
  RP15S4*disabled
  PXSXS4*disabled
  RP16S4*disabled
  PXSXS4*disabled
  RP17S4*disabled
  PXSXS4*disabled
  RP18S4*disabled
  PXSXS4*disabled
  RP19S4*disabled
  PXSXS4*disabled
  RP20S4*disabled
  PXSXS4*disabled

  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
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lyan   3843 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Sep 22 10:04:32 2016
  HibernationDevice: RESUME=UUID=fea7db5f-a686-450a-954f-0b89f08b946f
  InstallationDate: Installed on 2016-08-25 (28 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP ProBook 440 G3
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=eff3796a-2b2f-4f3a-8754-f446ddb32a9e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/10/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N78 Ver. 01.09
  dmi.board.name: 8100
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 40.03
  dmi.chassis.asset.tag: 5CD6228X27
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN78Ver.01.09:bd03/10/2016:svnHP:pnHPProBook440G3:pvr:rvnHP:rn8100:rvrKBCVersion40.03:cvnHP:ct10:cvr:
  dmi.product.name: HP ProBook 440 G3
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626413/+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 1626517] Re: Access to some folders hangs and in dmesg see kernel BUG report

2016-09-27 Thread Alberto Salvia Novella

** Changed in: linux (Ubuntu)
   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/1626517

Title:
  Access to some folders hangs and in dmesg see kernel BUG report

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Probably freeze during access to folder caused by 
  kernel BUG at /build/linux-BvkamA/linux-4.4.0/fs/namei.c:2562!

  Also segfault during collecting information with 'ubuntu-bug linux', but not 
sure it is related:
  [80059.937844] apport-kde[22602]: segfault at 7fdb0f1d4b00 ip 
7fdb44cd40f5 sp 7ffd35400828 error 4 in 
QtCore.cpython-35m-x86_64-linux-gnu.so[7fdb44ae4000+268000]
  [80099.437691] Qt bearer threa[23986]: segfault at 7f23b89942e9 ip 
7f23b3d41ccb sp 7f239fffce50 error 4 in 
libgcc_s.so.1[7f23b3d33000+16000]
  It is looks like separate issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vadim  4045 F pulseaudio
   /dev/snd/controlC0:  vadim  4045 F pulseaudio
  Date: Thu Sep 22 13:52:19 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=4ff5857a-eca8-4968-9e7d-16cb2b146f60
  InstallationDate: Installed on 2015-04-28 (512 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUS All Series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic 
root=UUID=f0d3e2ee-9f79-431c-9d8a-1079d7638279 ro quiet splash vt.handoff=7
  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.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (152 days ago)
  dmi.bios.date: 08/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1002
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1002:bd08/12/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626517/+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 1626679] Re: NVMe triggering kernel panic followed by "bad: scheduling from the idle thread!"

2016-09-27 Thread Alberto Salvia Novella

** Changed in: linux (Ubuntu)
   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/1626679

Title:
  NVMe triggering kernel panic followed by "bad: scheduling from the
  idle thread!"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On an NVMe system I'm using, Ubuntu 16.04.1 regularly seems to trigger
  off a kernel panic against somepart of the NVMe driver it looks like,
  after which the logs get filled with entries over and over again of:

  "bad: scheduling from the idle thread!"

  Here's the initial stack trace that seems to trigger off the bug:

  Sep 22 15:51:46 ubuntu kernel: [   97.478175] [ cut here 
]
  Sep 22 15:51:46 ubuntu kernel: [   97.478185] WARNING: CPU: 13 PID: 0 at 
/build/linux-dcxD3m/linux-4.4.0/kernel/irq/manage.c:1438 
__free_irq+0x1d2/0x280()
  Sep 22 15:51:46 ubuntu kernel: [   97.478188] Trying to free IRQ 38 from IRQ 
context!
  Sep 22 15:51:46 ubuntu kernel: [   97.478191] Modules linked in: 
nls_iso8859_1 ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel kvm irqbypass ioatdma me
  i_me sb_edac shpchp edac_core lpc_ich mei 8250_fintek ipmi_msghandler mac_hid 
ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr autofs4 btrfs 
iscsi_tcp libiscsi_tcp libiscsi
  scsi_transport_iscsi raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
crct10dif_pclmul ixgbe crc32_pclmu
  l dca vxlan aesni_intel ip6_udp_tunnel udp_tunnel aes_x86_64 lrw gf128mul ptp 
glue_helper ahci ablk_helper pps_core cryptd nvme libahci mdio wmi fjes
  Sep 22 15:51:46 ubuntu kernel: [   97.478257] CPU: 13 PID: 0 Comm: swapper/13 
Not tainted 4.4.0-31-generic #50-Ubuntu
  Sep 22 15:51:46 ubuntu kernel: [   97.478260] Hardware name: Oracle 
Corporation ORACLE SERVER X5-2/ASM,MOTHERBOARD,1U, BIOS 30080100 04/13/2016
  Sep 22 15:51:46 ubuntu kernel: [   97.478263]  0286 
4fea3140a01056a3 883f7f743b10 813f1143
  Sep 22 15:51:46 ubuntu kernel: [   97.478267]  883f7f743b58 
81cb61f8 883f7f743b48 81081102
  Sep 22 15:51:46 ubuntu kernel: [   97.478271]  0026 
883f5b2ea700 0026 
  Sep 22 15:51:46 ubuntu kernel: [   97.478275] Call Trace:
  Sep 22 15:51:46 ubuntu kernel: [   97.478277][] 
dump_stack+0x63/0x90
  Sep 22 15:51:46 ubuntu kernel: [   97.478290]  [] 
warn_slowpath_common+0x82/0xc0
  Sep 22 15:51:46 ubuntu kernel: [   97.478294]  [] 
warn_slowpath_fmt+0x5c/0x80
  Sep 22 15:51:46 ubuntu kernel: [   97.478299]  [] ? 
try_to_grab_pending+0xb3/0x160
  Sep 22 15:51:46 ubuntu kernel: [   97.478302]  [] 
__free_irq+0x1d2/0x280
  Sep 22 15:51:46 ubuntu kernel: [   97.478306]  [] 
free_irq+0x3c/0x90
  Sep 22 15:51:46 ubuntu kernel: [   97.478314]  [] 
nvme_suspend_queue+0x89/0xb0 [nvme]
  Sep 22 15:51:46 ubuntu kernel: [   97.478320]  [] 
nvme_disable_admin_queue+0x27/0x90 [nvme]
  Sep 22 15:51:46 ubuntu kernel: [   97.478325]  [] 
nvme_dev_disable+0x29e/0x2c0 [nvme]
  Sep 22 15:51:46 ubuntu kernel: [   97.478330]  [] ? 
__nvme_process_cq+0x210/0x210 [nvme]
  Sep 22 15:51:46 ubuntu kernel: [   97.478334]  [] ? 
dev_warn+0x6c/0x90
  Sep 22 15:51:46 ubuntu kernel: [   97.478340]  [] 
nvme_timeout+0x110/0x1d0 [nvme]
  Sep 22 15:51:46 ubuntu kernel: [   97.478344]  [] ? 
cpumask_next_and+0x2f/0x40
  Sep 22 15:51:46 ubuntu kernel: [   97.478348]  [] ? 
load_balance+0x18c/0x980
  Sep 22 15:51:46 ubuntu kernel: [   97.478354]  [] 
blk_mq_rq_timed_out+0x2f/0x70
  Sep 22 15:51:46 ubuntu kernel: [   97.478358]  [] 
blk_mq_check_expired+0x4e/0x80
  Sep 22 15:51:46 ubuntu kernel: [   97.478363]  [] 
bt_for_each+0xd8/0xe0
  Sep 22 15:51:46 ubuntu kernel: [   97.478367]  [] ? 
blk_mq_rq_timed_out+0x70/0x70
  Sep 22 15:51:46 ubuntu kernel: [   97.478370]  [] ? 
blk_mq_rq_timed_out+0x70/0x70
  Sep 22 15:51:46 ubuntu kernel: [   97.478375]  [] 
blk_mq_queue_tag_busy_iter+0x47/0xc0
  Sep 22 15:51:46 ubuntu kernel: [   97.478379]  [] ? 
blk_mq_attempt_merge+0xb0/0xb0
  Sep 22 15:51:46 ubuntu kernel: [   97.478383]  [] 
blk_mq_rq_timer+0x41/0xf0
  Sep 22 15:51:46 ubuntu kernel: [   97.478389]  [] 
call_timer_fn+0x35/0x120
  Sep 22 15:51:46 ubuntu kernel: [   97.478393]  [] ? 
blk_mq_attempt_merge+0xb0/0xb0
  Sep 22 15:51:46 ubuntu kernel: [   97.478397]  [] 
run_timer_softirq+0x23a/0x2f0
  Sep 22 15:51:46 ubuntu kernel: [   97.478403]  [] 
__do_softirq+0x101/0x290
  Sep 22 15:51:46 ubuntu kernel: [   97.478407]  [] 
irq_exit+0xa3/0xb0
  Sep 22 15:51:46 ubuntu kernel: [   97.478413]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Sep 22 15:51:46 ubuntu kernel: [   97.478417]  [] 
apic_timer_interrupt+0x82/0x90
  Sep 22 15:51:46 ubuntu kernel: [   97.478419][] ? 
cpuidle_enter_state+0x111/0x2b0
  Sep 22 15:51:46 ubuntu kernel: [   97.478428]  []

[Kernel-packages] [Bug 1626460] Re: usb-devices | awk '/13d3/' RS=

2016-09-27 Thread Alberto Salvia Novella

Please:

1. Edit the description so it explains the steps to reproduce the bug,
and what are the consequences of it.

2. Set status back to "confirmed".

Thank you.

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1626460

Title:
  usb-devices | awk '/13d3/' RS=

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  usb-devices | awk '/13d3/' RS=

  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 i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  studik 1697 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Sep 22 12:39:12 2016
  HibernationDevice: RESUME=UUID=56c1e43e-2a1f-4066-b572-bb690c40d0cd
  InstallationDate: Installed on 2016-09-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: Matsushita Electric Industrial Co.,Ltd. CF-19CHD07BE
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2007
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V1.00L14
  dmi.board.name: CF19-1
  dmi.board.vendor: Matsushita Electric Industrial Co.,Ltd.
  dmi.board.version: 001
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Matsushita Electric Industrial Co.,Ltd.
  dmi.chassis.version: 001
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV1.00L14:bd07/12/2007:svnMatsushitaElectricIndustrialCo.,Ltd.:pnCF-19CHD07BE:pvr001:rvnMatsushitaElectricIndustrialCo.,Ltd.:rnCF19-1:rvr001:cvnMatsushitaElectricIndustrialCo.,Ltd.:ct10:cvr001:
  dmi.product.name: CF-19CHD07BE
  dmi.product.version: 001
  dmi.sys.vendor: Matsushita Electric Industrial Co.,Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626460/+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 1626689] Re: During boot process, system goes to sleep

2016-09-27 Thread Alberto Salvia Novella

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

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

** Changed in: linux (Ubuntu)
   Importance: High => 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/1626689

Title:
  During boot process, system goes to sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.04, my computer goes to sleep during the boot process, 
shortly after I entered the passphrase to unlock my LVM. When I wake it up, I’m 
at the graphical login prompt. I type my user password, press enter and it goes 
to sleep again. When I wake it up, I’m in my working Lubuntu desktop. This 
happens every time I boot. And it’s quite annoying.
  Please tell me which additional information I can provide to help fix this 
bug.

  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 i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steffi 2155 F lxpanel
  CurrentDesktop: LXDE
  Date: Thu Sep 22 20:24:31 2016
  HibernationDevice: RESUME=UUID=9e305c00-cee8-4703-9352-abc5fb755282
  InstallationDate: Installed on 2016-09-21 (1 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  MachineType: Acer Aspire one
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic 
root=/dev/mapper/lubuntu--vg-root ro quiet splash vt.handoff=7
  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
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-09-22 (0 days ago)
  dmi.bios.date: 02/20/2009
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.05
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire one
  dmi.board.vendor: Acer
  dmi.board.version: V1.05
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.modalias: 
dmi:bvnAcer:bvrV1.05:bd02/20/2009:svnAcer:pnAspireone:pvrV1.05:rvnAcer:rnAspireone:rvrV1.05:cvnAcer:ct1:cvrV1.05:
  dmi.product.name: Aspire one
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626689/+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 1626998] Re: Unable to install wifi drivers on Ubuntu 16.04

2016-09-27 Thread Alberto Salvia Novella

** Changed in: linux (Ubuntu)
   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/1626998

Title:
  Unable to install wifi drivers on Ubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Unable to install wifi drivers on Ubuntu 16.04
  I have tried various options from the internet but in vain.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  manparvesh   1609 F pulseaudio
   /dev/snd/controlC0:  manparvesh   1609 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 23 17:31:56 2016
  HibernationDevice: RESUME=UUID=e32a9c2a-6ee4-477c-a51f-806ca999f29e
  InstallationDate: Installed on 2016-09-23 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enx7a2cb569331d  no wireless extensions.
   
   enp7s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. Vostro 3446
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/03/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 06XK30
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/03/2015:svnDellInc.:pnVostro3446:pvrNotSpecified:rvnDellInc.:rn06XK30:rvrA09:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Vostro 3446
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626998/+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 1626970] Re: Graphics not working after upgrade

2016-09-27 Thread Alberto Salvia Novella

** Changed in: linux (Ubuntu)
   Importance: Undecided => 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/1626970

Title:
  Graphics not working after upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I can't log-in in graphic mode after upgrading Ubuntu. I can only log-
  in via terminal.

  These are some errors reported after booting the vomputer, just before
  the login-screen.

  (45.185133) amdgpu :0a:00.0: couldn't schedule ib
  (45.185179) (drm:amdgpu_sched_run_job (amdgpu)) *ERROR* Error scheduling 
IBs (-22)
  (45.185221) (drm:amd_sched_main (amdgpu)) *ERROR* Faild to run job!

  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
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Sep 23 12:41:36 2016
  HibernationDevice: RESUME=UUID=9ae50736-ddfe-4650-9a8d-d0fa60d324cf
  InstallationDate: Installed on 2015-08-28 (391 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Hewlett-Packard HP ProBook 450 G2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  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
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-05-08 (137 days ago)
  dmi.bios.date: 11/27/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M73 Ver. 01.00
  dmi.board.name: 2248
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 59.19
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM73Ver.01.00:bd11/27/2014:svnHewlett-Packard:pnHPProBook450G2:pvrA3008DD10B03:rvnHewlett-Packard:rn2248:rvrKBCVersion59.19:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 450 G2
  dmi.product.version: A3008DD10B03
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

2016-09-27 Thread Joseph Salisbury

I built a mainline kenel with commit
2deb4be28077638591fe5fc593b7f8aabc140f42 reverted.

Can you test this kernel to see if it also has the new desktop issue?

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

Title:
  4.8.0 kernels do not complete boot process on VM

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

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

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

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

[Kernel-packages] [Bug 1627171] Re: Suspending Sony Vaio laptop results in system hang occasionally

2016-09-27 Thread Alberto Salvia Novella

** Changed in: linux (Ubuntu)
   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/1627171

Title:
  Suspending Sony Vaio laptop results in system hang occasionally

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sony Vaio VPCEA3C5E

  Normally suspending this laptop works fine, but if I have been using
  the system a lot (lots of applications open, etc.) there is a high
  likelihood that it will freeze when suspending.

  The screen goes black and all disk activity stops but the machine is
  still turned on and does not respond to any keypresses including
  trying Ctrl-Alt-F1 or the power button etc.

  The only way out is to turn off the power and boot again.

  As this happens mainly when programs are open (it doesn't seem to
  matter exactly what is open, just that the system isn't idle. Maybe
  when lots of memory is used?) it basically only happens at the worst
  possible times!

  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
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  josh   1976 F pulseaudio
   /dev/snd/controlC1:  josh   1976 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 23 20:36:19 2016
  HibernationDevice: RESUME=UUID=f474afa1-beb2-44eb-90f6-5e44a1ac1577
  InstallationDate: Installed on 2013-12-07 (1021 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Sony Corporation VPCEA3C5E
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=828ba2ee-5ee8-4211-9ff2-e65c3fcbc04f ro quiet splash vt.handoff=7
  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
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-07-29 (55 days ago)
  dmi.bios.date: 10/06/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R1140Y8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR1140Y8:bd10/06/2010:svnSonyCorporation:pnVPCEA3C5E:pvrC6082Y31:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCEA3C5E
  dmi.product.version: C6082Y31
  dmi.sys.vendor: Sony Corporation

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

2016-09-27 Thread Alberto Salvia Novella

** Changed in: linux (Ubuntu)
   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/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

[Kernel-packages] [Bug 1626299] Re: ACPI Errors in dmesg, battery monitor shows empty

2016-09-27 Thread Alberto Salvia Novella

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

** Changed in: linux (Ubuntu)
   Importance: Medium => 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/1626299

Title:
  ACPI Errors in dmesg, battery monitor shows empty

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using Xubuntu, and the power manager show an empty battery at all
  times, regardless of battery level. I essentially have no indicators
  of how much power my laptop has left. Once I run out of power, the
  laptop obviously shuts down causing data corruption.

  my dmesg shows:

  [   10.587295] ACPI Error: No handler for Region [PMRG] (88015a0c0090) 
[GenericSerialBus] (20150930/evregion-163)
  [   10.587303] ACPI Error: Region GenericSerialBus (ID=9) has no handler 
(20150930/exfldio-297)
  [   10.587309] ACPI Error: Method parse/execution failed [\_SB.TAMB._TMP] 
(Node 88015a0f7208), AE_NOT_EXIST (20150930/psparse-542)
  [   10.587325] thermal thermal_zone0: failed to read out thermal zone (-5)
  [   10.598876] ACPI Error: No handler for Region [PMRG] (88015a0c0090) 
[GenericSerialBus] (20150930/evregion-163)
  [   10.598882] ACPI Error: Region GenericSerialBus (ID=9) has no handler 
(20150930/exfldio-297)
  [   10.598886] ACPI Error: Method parse/execution failed [\_SB.TEFN._TMP] 
(Node 88015a0f76e0), AE_NOT_EXIST (20150930/psparse-542)
  [   10.598898] thermal thermal_zone1: failed to read out thermal zone (-5)
  [   10.600460] ACPI Error: No handler for Region [PMRG] (88015a0c0090) 
[GenericSerialBus] (20150930/evregion-163)
  [   10.600465] ACPI Error: Region GenericSerialBus (ID=9) has no handler 
(20150930/exfldio-297)
  [   10.600469] ACPI Error: Method parse/execution failed [\_SB.TSKN._TMP] 
(Node 88015a0f94b0), AE_NOT_EXIST (20150930/psparse-542)
  [   10.600479] thermal thermal_zone2: failed to read out thermal zone (-5)

  later it shows:

  [   11.235601] acer_wmi: Enabling Launch Manager failed: 0xe4 - 0x0

  
  It's unfortunate to never know how much power is left, as one might imagine.

  Thanks.

  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
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  coder  1607 F pulseaudio
   /dev/snd/controlC1:  coder  1607 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Sep 22 00:34:51 2016
  HibernationDevice: RESUME=UUID=c0846449-28bd-4d6a-9ccb-732cf1582f3a
  InstallationDate: Installed on 2016-09-08 (13 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Acer Aspire SW5-173
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/11/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Crepe
  dmi.board.vendor: Acer
  dmi.board.version: V1.08
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.08
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.08:bd04/11/2016:svnAcer:pnAspireSW5-173:pvrV1.08:rvnAcer:rnCrepe:rvrV1.08:cvnAcer:ct9:cvrV1.08:
  dmi.product.name: Aspire SW5-173
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626299/+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 1625794] modoc (ppc64el) - tests ran: 4, failed: 1

2016-09-27 Thread Brad Figg

tests ran:   4, failed: 1;
  
http://kernel.ubuntu.com/testing/3.19.0-70.78~14.04.1/modoc__3.19.0-70.78~14.04.1__2016-09-27_23-00-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-70.78~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-70.78~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1625788
  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/1625794/+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 1624765] Re: wifi broke after 16.04 upgrade

2016-09-27 Thread Alberto Salvia Novella

** Changed in: linux (Ubuntu)
   Importance: Undecided => 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/1624765

Title:
  wifi broke after 16.04 upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded from ubuntu 14.04 LTS to ubuntu 16.04 LTS. My wifi was working 
fine in previous version. But, after upgrade wifi broke. It won't show any wifi 
networks and I couldn't enable wifi from ubuntu panel on top right corner. 
  I tried almost all suggestions in this page and few other askubuntu pages 
with same problem: 
  
http://askubuntu.com/questions/62166/siocsifflags-operation-not-possible-due-to-rf-kill
  But, nothing worked. 

  Here is my console output: 
  ~$ sudo rfkill list
  0: dell-rbtn: Wireless LAN
Soft blocked: yes
Hard blocked: yes
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  7: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

  Then, I ran "sudo rfkill unblock wifi" but that didn't fix anything.

  Finally, the only thing that worked was: 
  sudo modprobe -r dell-rbtn

  I don't even know if this is the right way to fix it. Please fix the
  16.04 kernel and OS upgrade package so that other users don't face
  this problem that cost me 2 days. Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.14
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Sat Sep 17 15:13:39 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-19 (29 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  parag  3685 F pulseaudio
   /dev/snd/controlC1:  parag  3685 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=bad8d93e-83c4-40c0-aa97-00ac6c4e373e
  InstallationDate: Installed on 2016-08-19 (38 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 3542
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=206733db-103a-4078-847b-0a897121325e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/05/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 02RD2H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd08/05/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn02RD2H:rvrA04:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1624765/+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 1626283] Re: lenovo t420s very slow wifi after dist upgrade 14-16

2016-09-27 Thread Alberto Salvia Novella

** Changed in: linux (Ubuntu)
   Importance: Undecided => 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/1626283

Title:
  lenovo t420s very slow wifi after dist upgrade 14-16

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  it is not more than 2 mbit\s for the moment - before upgrade it works well - 
about 40-50 mbit\s.
  it is not ISP issue other devices works fast at my wifi network

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.16
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Thu Sep 22 00:29:18 2016
  InstallationDate: Installed on 2015-12-17 (279 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to xenial on 2016-08-17 (35 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626283/+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 1626749] Re: autofs set $USER to "root" instead of current user

2016-09-27 Thread Alberto Salvia Novella

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

Title:
  autofs set $USER to "root" instead of current user

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since last kernel upgrade from 4.4.0-36 to 4.4.0-38 automount failed to mount 
remote smb FS.
  The configuration file use $USER, $UID and $GID variables :
  i.e. :
  music 
-fstype=cifs,credentials=/home/$USER/.creds-file,user=$USER,uid=$UID,gid=$GID 
://192.168.1.9/music

  When a user account try to mount the FS, automount complain :

   >> error 2 (No such file or directory) opening credential file
  /home/root/.creds-file

  $USER, $UID and $GID are now sets with root variables instead of user
  account variables

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: autofs 5.1.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep 22 23:17:27 2016
  ExecutablePath: /usr/sbin/automount
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  SourcePackage: autofs
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1941 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=1ad9a17c-8b27-4436-a024-6c9ae99a5b87
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Sony Corporation SVS1511R9ES
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=df815dd3-2e1b-42d3-aef8-1823eb5d4f75 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  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-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0140C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0140C5:bd03/30/2012:svnSonyCorporation:pnSVS1511R9ES:pvrC60AGQAL:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVS1511R9ES
  dmi.product.version: C60AGQAL
  dmi.sys.vendor: Sony Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626749/+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 1626370] Re: Sound problems / slow performance /not responsive

2016-09-27 Thread Alberto Salvia Novella

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

** Changed in: linux (Ubuntu)
   Importance: High => 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/1626370

Title:
  Sound problems / slow performance /not responsive

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fan is always working very hard and system is hot. When I run windows
  8 on the same machine it is ok. New HD and fan too.

  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
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  peteruser   2757 F pulseaudio
   /dev/snd/controlC0:  peteruser   2757 F pulseaudio
  Date: Thu Sep 22 10:57:12 2016
  HibernationDevice: RESUME=UUID=def99bab-c578-4f83-b26e-3a1168b65b03
  MachineType: LENOVO 20193
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=b6bd5968-eb36-4de2-8e53-6906d540f6b6 ro quiet splash vt.handoff=7
  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.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6BCN44WW(V2.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y500
  dmi.modalias: 
dmi:bvnLENOVO:bvr6BCN44WW(V2.04):bd05/21/2013:svnLENOVO:pn20193:pvrLenovoIdeaPadY500:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY500:
  dmi.product.name: 20193
  dmi.product.version: Lenovo IdeaPad Y500
  dmi.sys.vendor: LENOVO

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

2016-09-27 Thread 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/1628309

Title:
  ENERGY_PERF_BIAS: Set to 'normal', was 'performance'

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [0.020580] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
  [0.020581] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
  ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
  Uname: Linux 4.8.0-17-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2141 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Sep 27 19:37:12 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (429 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-lowlatency N/A
   linux-backports-modules-4.8.0-17-lowlatency  N/A
   linux-firmware   1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628309/+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 1628061] Re: iwl4965 crashes randomly

2016-09-27 Thread Alberto Salvia Novella

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

** Changed in: linux (Ubuntu)
   Importance: High => 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/1628061

Title:
  iwl4965 crashes randomly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo X61s, WLAN randomly stops working, typically after a few hours 
of running time. I don't know any remedy but to reboot.
  This behavior started maybe 2 or 3 months ago. My maching is usually kept up 
to date, so the problem might be caused by some kernel update at that time.

  The relevant part in dmesg (attached) starts with
  [ 5812.412141] iwl4965 :03:00.0: Error sending C_POWER_TBL: time out 
after 500ms.
  [ 5812.412156] iwl4965 :03:00.0: set power fail, ret = -110
  [ 5813.424145] iwl4965 :03:00.0: Error sending C_ADD_STA: time out after 
500ms.
  [ 5813.424162] wls3: HW problem - can not stop rx aggregation for 
**:**:**:**:**:** tid 0
  [ 5813.924092] iwl4965 :03:00.0: Error sending C_ADD_STA: time out after 
500ms.
  [ 5813.924107] wls3: HW problem - can not stop rx aggregation for 
**:**:**:**:**:** tid 5
  [ 5814.052099] iwl4965 :03:00.0: Queue 4 stuck for 2500 ms.
  [ 5814.052124] iwl4965 :03:00.0: On demand firmware reload
  [ 5814.424142] iwl4965 :03:00.0: Error sending C_ADD_STA: time out after 
500ms.
  [ 5814.424168] wls3: HW problem - can not stop rx aggregation for 
**:**:**:**:**:** tid 6
  [ 5814.424421] iwl4965 :03:00.0: Master Disable Timed Out, 100 usec
  [ 5814.424468] ieee80211 phy0: Hardware restart was requested
  [ 5814.448160] iwl4965 :03:00.0: idx 0 not used in uCode key table.
  [ 5814.948182] iwl4965 :03:00.0: Error sending C_ADD_STA: time out after 
500ms.
  [ 5814.948201] wls3: failed to remove key (0, **:**:**:**:**:**) from 
hardware (-110)
  [ 5818.964158] iwl4965 :03:00.0: START_ALIVE timeout after 4000ms.

  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
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mki2093 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Sep 27 13:29:36 2016
  HibernationDevice: RESUME=/dev/mapper/vgubuntu-swap
  InstallationDate: Installed on 2016-06-05 (113 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  MachineType: LENOVO 76693JG
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic 
root=/dev/mapper/vgubuntu-system ro
  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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7NETC2WW (2.22 )
  dmi.board.name: 76693JG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7NETC2WW(2.22):bd03/22/2011:svnLENOVO:pn76693JG:pvrThinkPadX61s:rvnLENOVO:rn76693JG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 76693JG
  dmi.product.version: ThinkPad X61s
  dmi.sys.vendor: LENOVO

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

2016-09-27 Thread 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/1628311

Title:
  ACPI: 4 ACPI AML tables successfully acquired and loaded

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [0.011335] ACPI: 4 ACPI AML tables successfully acquired and
  loaded

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
  ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
  Uname: Linux 4.8.0-17-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2141 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Sep 27 19:39:45 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (429 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-lowlatency N/A
   linux-backports-modules-4.8.0-17-lowlatency  N/A
   linux-firmware   1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

2016-09-27 Thread 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/1628312

Title:
  ACPI: RSDP 0x000F0120 24 (v02 SECCSD)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [0.00] ACPI: RSDP 0x000F0120 24 (v02 SECCSD)
  [0.00] ACPI: XSDT 0xDAFFE170 94 (v01 SECCSD LH43STAR 
0002 PTL  0002)
  [0.00] ACPI: FACP 0xDAFEE000 00010C (v05 SECCSD LH43STAR 
0002 PTL  0002)
  [0.00] ACPI: DSDT 0xDAFF1000 0092DA (v02 SECCSD IVB-CPT  
 INTL 20061109)
  [0.00] ACPI: FACS 0xDAF7B000 40
  [0.00] ACPI: SLIC 0xDAFFD000 000176 (v01 SECCSD LH43STAR 
0002 PTL  0001)
  [0.00] ACPI: SSDT 0xDAFFB000 001068 (v01 SECCSD PtidDevc 
1000 INTL 20061109)
  [0.00] ACPI: ASF! 0xDAFF A5 (v32 SECCSD LH43STAR 
0002 PTL  0002)
  [0.00] ACPI: HPET 0xDAFED000 38 (v01 SECCSD LH43STAR 
0002 PTL  0002)
  [0.00] ACPI: APIC 0xDAFEC000 98 (v03 SECCSD LH43STAR 
0002 PTL  0002)
  [0.00] ACPI: MCFG 0xDAFEB000 3C (v01 SECCSD LH43STAR 
0002 PTL  0002)
  [0.00] ACPI: FPDT 0xDAFEA000 54 (v01 SECCSD LH43STAR 
0002 PTL  0002)
  [0.00] ACPI: SSDT 0xDAFE9000 0007D7 (v01 PmRef  Cpu0Ist  
3000 INTL 20061109)
  [0.00] ACPI: SSDT 0xDAFE8000 000AD0 (v01 PmRef  CpuPm
3000 INTL 20061109)
  [0.00] ACPI: UEFI 0xDAFE7000 3E (v01 SECCSD LH43STAR 
0002 PTL  0002)
  [0.00] ACPI: UEFI 0xDAFE6000 42 (v01 PTLCOMBUF   
0001 PTL  0001)
  [0.00] ACPI: POAT 0xDAF78000 55 (v03 SECCSD LH43STAR 
0002 PTL  0002)
  [0.00] ACPI: UEFI 0xDAFE5000 00022E (v01 SECCSD LH43STAR 
0002 PTL  0002)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
  ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
  Uname: Linux 4.8.0-17-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2141 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Sep 27 19:42:35 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (429 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-lowlatency N/A
   linux-backports-modules-4.8.0-17-lowlatency  N/A
   linux-firmware   1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628312/+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 1627321] Re: package linux-image-4.4.0-38-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2016-09-27 Thread Alberto Salvia Novella

** Changed in: linux (Ubuntu)
   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/1627321

Title:
  package linux-image-4.4.0-38-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm running this Ubuntu on VMware Fusion. It's my development machine.
  Host is OS X Yosemite.

  The machine has been in active use 2 years without problem.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  harri 36696 F pulseaudio
  Date: Tue Sep 20 14:03:23 2016
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=1d488a56-f4e9-4e2a-ae3c-133ac6d94606
  InstallationDate: Installed on 2014-03-18 (920 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  IwConfig:
   lono wireless extensions.
   
   docker0   no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 005: ID 0e0f:0008 VMware, Inc. 
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=24a8b3e3-6215-49ff-bb39-702c22ca263f ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
  RfKill:
   1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.4.0-38-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to xenial on 2016-08-09 (46 days ago)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

2016-09-27 Thread 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/1628307

Title:
  ACPI: Executed 1 blocks of module-level executable AML code

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [0.121702] ACPI: Executed 1 blocks of module-level executable AML
  code

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
  ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
  Uname: Linux 4.8.0-17-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2141 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Sep 27 19:32:02 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (429 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-lowlatency N/A
   linux-backports-modules-4.8.0-17-lowlatency  N/A
   linux-firmware   1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

2016-09-27 Thread 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/1628308

Title:
  PCCT header not found.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [0.114784] PCCT header not found.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
  ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
  Uname: Linux 4.8.0-17-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2141 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Sep 27 19:34:08 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (429 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-lowlatency N/A
   linux-backports-modules-4.8.0-17-lowlatency  N/A
   linux-firmware   1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

2016-09-27 Thread 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/1628305

Title:
  ACPI: Dynamic OEM Table Load:

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [0.128304] ACPI: Dynamic OEM Table Load:
  [0.128316] ACPI: SSDT 0x886FD09F2800 000784 (v01 PmRef  Cpu0Cst  
3001 INTL 20061109)
  [0.129166] ACPI: Dynamic OEM Table Load:
  [0.129174] ACPI: SSDT 0x886FD0A2B800 000303 (v01 PmRef  ApIst
3000 INTL 20061109)
  [0.129902] ACPI: Dynamic OEM Table Load:
  [0.129909] ACPI: SSDT 0x886FD0ABF000 000119 (v01 PmRef  ApCst
3000 INTL 20061109)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
  ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
  Uname: Linux 4.8.0-17-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2141 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Sep 27 19:29:22 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (429 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-lowlatency N/A
   linux-backports-modules-4.8.0-17-lowlatency  N/A
   linux-firmware   1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628305/+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 1628311] [NEW] ACPI: 4 ACPI AML tables successfully acquired and loaded

2016-09-27 Thread Cristian Aravena Romero

Public bug reported:

[0.011335] ACPI: 4 ACPI AML tables successfully acquired and loaded

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
Uname: Linux 4.8.0-17-lowlatency x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  caravena   2141 F pulseaudio
CurrentDesktop: GNOME
Date: Tue Sep 27 19:39:45 2016
HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
InstallationDate: Installed on 2015-07-26 (429 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-17-lowlatency N/A
 linux-backports-modules-4.8.0-17-lowlatency  N/A
 linux-firmware   1.161
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-bug yakkety

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

Title:
  ACPI: 4 ACPI AML tables successfully acquired and loaded

Status in linux package in Ubuntu:
  New

Bug description:
  [0.011335] ACPI: 4 ACPI AML tables successfully acquired and
  loaded

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
  ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
  Uname: Linux 4.8.0-17-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2141 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Sep 27 19:39:45 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (429 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-lowlatency N/A
   linux-backports-modules-4.8.0-17-lowlatency  N/A
   linux-firmware   1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628311/+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 1627074] dwalin (amd64) - tests ran: 30, failed: 0

2016-09-27 Thread Brad Figg

*** This bug is a duplicate of bug 1628204 ***
https://bugs.launchpad.net/bugs/1628204

tests ran:  30, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/dwalin__4.4.0-40.60__2016-09-27_21-43-00/results-index.html

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

Title:
  linux: 4.4.0-40.60 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-40.60 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/1627074/+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 1628312] [NEW] ACPI: RSDP 0x00000000000F0120 000024 (v02 SECCSD)

2016-09-27 Thread Cristian Aravena Romero

Public bug reported:

[0.00] ACPI: RSDP 0x000F0120 24 (v02 SECCSD)
[0.00] ACPI: XSDT 0xDAFFE170 94 (v01 SECCSD LH43STAR 
0002 PTL  0002)
[0.00] ACPI: FACP 0xDAFEE000 00010C (v05 SECCSD LH43STAR 
0002 PTL  0002)
[0.00] ACPI: DSDT 0xDAFF1000 0092DA (v02 SECCSD IVB-CPT  
 INTL 20061109)
[0.00] ACPI: FACS 0xDAF7B000 40
[0.00] ACPI: SLIC 0xDAFFD000 000176 (v01 SECCSD LH43STAR 
0002 PTL  0001)
[0.00] ACPI: SSDT 0xDAFFB000 001068 (v01 SECCSD PtidDevc 
1000 INTL 20061109)
[0.00] ACPI: ASF! 0xDAFF A5 (v32 SECCSD LH43STAR 
0002 PTL  0002)
[0.00] ACPI: HPET 0xDAFED000 38 (v01 SECCSD LH43STAR 
0002 PTL  0002)
[0.00] ACPI: APIC 0xDAFEC000 98 (v03 SECCSD LH43STAR 
0002 PTL  0002)
[0.00] ACPI: MCFG 0xDAFEB000 3C (v01 SECCSD LH43STAR 
0002 PTL  0002)
[0.00] ACPI: FPDT 0xDAFEA000 54 (v01 SECCSD LH43STAR 
0002 PTL  0002)
[0.00] ACPI: SSDT 0xDAFE9000 0007D7 (v01 PmRef  Cpu0Ist  
3000 INTL 20061109)
[0.00] ACPI: SSDT 0xDAFE8000 000AD0 (v01 PmRef  CpuPm
3000 INTL 20061109)
[0.00] ACPI: UEFI 0xDAFE7000 3E (v01 SECCSD LH43STAR 
0002 PTL  0002)
[0.00] ACPI: UEFI 0xDAFE6000 42 (v01 PTLCOMBUF   
0001 PTL  0001)
[0.00] ACPI: POAT 0xDAF78000 55 (v03 SECCSD LH43STAR 
0002 PTL  0002)
[0.00] ACPI: UEFI 0xDAFE5000 00022E (v01 SECCSD LH43STAR 
0002 PTL  0002)

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
Uname: Linux 4.8.0-17-lowlatency x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  caravena   2141 F pulseaudio
CurrentDesktop: GNOME
Date: Tue Sep 27 19:42:35 2016
HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
InstallationDate: Installed on 2015-07-26 (429 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-17-lowlatency N/A
 linux-backports-modules-4.8.0-17-lowlatency  N/A
 linux-firmware   1.161
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-bug yakkety

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

Title:
  ACPI: RSDP 0x000F0120 24 (v02 SECCSD)

Status in linux package in Ubuntu:
  New

Bug description:
  [0.00] ACPI: RSDP 0x000F0120 24 (v02 SECCSD)
  [0.00] ACPI: XSDT 0xDAFFE170 94 (v01 SECCSD LH43STAR 
0002 PTL  0002)
  [0.00] ACPI: FACP 0xDAFEE000 00010C (v05 SECCSD LH43STAR 
0002 PTL  0002)
  [0.00] ACPI: DSDT 0xDAFF1000 0092DA (v02 SECCSD IVB-CPT  
 INTL 20061109)
  [0.00] ACPI: FACS 0xDAF7B000 40
  [0.00] ACPI: SLIC 0xDAFFD000 000176 (v01 SECCSD LH43STAR 
0002 PTL  0001)
  [0.00] ACPI: SSDT 0xDAFFB000 001068 (v01 SECCSD PtidDevc 
1000 INTL 20061109)
  [0.00] ACPI: ASF! 0xDAFF A5 (v32 SECCSD LH43STAR 
0002 PTL  0002)
  [0.00] ACPI: HPET 0xDAFED000 38 (v01 SECCSD LH43STAR 
0002 PTL  0002)
  [0.00] ACPI: APIC 0xDAFEC000 98 (v03 SECCSD LH43STAR 
0002 PTL  0002)
  [0.00] ACPI: MCFG 0xDAFEB000 3C (v01 SECCSD LH43STAR 
0002 PTL  0002)
  [0.00] ACPI: FPDT 0xDAFEA000 54 (v01

[Kernel-packages] [Bug 1625794] modoc (ppc64el) - tests ran: 2, failed: 0

2016-09-27 Thread Brad Figg

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-70.78~14.04.1/modoc__3.19.0-70.78~14.04.1__2016-09-27_22-15-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-70.78~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-70.78~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1625788
  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/1625794/+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 1628308] [NEW] PCCT header not found.

2016-09-27 Thread Cristian Aravena Romero

Public bug reported:

[0.114784] PCCT header not found.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
Uname: Linux 4.8.0-17-lowlatency x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  caravena   2141 F pulseaudio
CurrentDesktop: GNOME
Date: Tue Sep 27 19:34:08 2016
HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
InstallationDate: Installed on 2015-07-26 (429 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-17-lowlatency N/A
 linux-backports-modules-4.8.0-17-lowlatency  N/A
 linux-firmware   1.161
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-bug yakkety

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

Title:
  PCCT header not found.

Status in linux package in Ubuntu:
  New

Bug description:
  [0.114784] PCCT header not found.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
  ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
  Uname: Linux 4.8.0-17-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2141 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Sep 27 19:34:08 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (429 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-lowlatency N/A
   linux-backports-modules-4.8.0-17-lowlatency  N/A
   linux-firmware   1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628308/+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 1628309] [NEW] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'

2016-09-27 Thread Cristian Aravena Romero

Public bug reported:

[0.020580] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[0.020581] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
Uname: Linux 4.8.0-17-lowlatency x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  caravena   2141 F pulseaudio
CurrentDesktop: GNOME
Date: Tue Sep 27 19:37:12 2016
HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
InstallationDate: Installed on 2015-07-26 (429 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-17-lowlatency N/A
 linux-backports-modules-4.8.0-17-lowlatency  N/A
 linux-firmware   1.161
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-bug yakkety

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

Title:
  ENERGY_PERF_BIAS: Set to 'normal', was 'performance'

Status in linux package in Ubuntu:
  New

Bug description:
  [0.020580] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
  [0.020581] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
  ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
  Uname: Linux 4.8.0-17-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2141 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Sep 27 19:37:12 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (429 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-lowlatency N/A
   linux-backports-modules-4.8.0-17-lowlatency  N/A
   linux-firmware   1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628309/+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 1628305] [NEW] ACPI: Dynamic OEM Table Load:

2016-09-27 Thread Cristian Aravena Romero

Public bug reported:

[0.128304] ACPI: Dynamic OEM Table Load:
[0.128316] ACPI: SSDT 0x886FD09F2800 000784 (v01 PmRef  Cpu0Cst  
3001 INTL 20061109)
[0.129166] ACPI: Dynamic OEM Table Load:
[0.129174] ACPI: SSDT 0x886FD0A2B800 000303 (v01 PmRef  ApIst
3000 INTL 20061109)
[0.129902] ACPI: Dynamic OEM Table Load:
[0.129909] ACPI: SSDT 0x886FD0ABF000 000119 (v01 PmRef  ApCst
3000 INTL 20061109)

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
Uname: Linux 4.8.0-17-lowlatency x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  caravena   2141 F pulseaudio
CurrentDesktop: GNOME
Date: Tue Sep 27 19:29:22 2016
HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
InstallationDate: Installed on 2015-07-26 (429 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-17-lowlatency N/A
 linux-backports-modules-4.8.0-17-lowlatency  N/A
 linux-firmware   1.161
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-bug yakkety

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

Title:
  ACPI: Dynamic OEM Table Load:

Status in linux package in Ubuntu:
  New

Bug description:
  [0.128304] ACPI: Dynamic OEM Table Load:
  [0.128316] ACPI: SSDT 0x886FD09F2800 000784 (v01 PmRef  Cpu0Cst  
3001 INTL 20061109)
  [0.129166] ACPI: Dynamic OEM Table Load:
  [0.129174] ACPI: SSDT 0x886FD0A2B800 000303 (v01 PmRef  ApIst
3000 INTL 20061109)
  [0.129902] ACPI: Dynamic OEM Table Load:
  [0.129909] ACPI: SSDT 0x886FD0ABF000 000119 (v01 PmRef  ApCst
3000 INTL 20061109)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
  ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
  Uname: Linux 4.8.0-17-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2141 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Sep 27 19:29:22 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (429 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-lowlatency N/A
   linux-backports-modules-4.8.0-17-lowlatency  N/A
   linux-firmware   1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications

[Kernel-packages] [Bug 1628307] [NEW] ACPI: Executed 1 blocks of module-level executable AML code

2016-09-27 Thread Cristian Aravena Romero

Public bug reported:

[0.121702] ACPI: Executed 1 blocks of module-level executable AML
code

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
Uname: Linux 4.8.0-17-lowlatency x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  caravena   2141 F pulseaudio
CurrentDesktop: GNOME
Date: Tue Sep 27 19:32:02 2016
HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
InstallationDate: Installed on 2015-07-26 (429 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-17-lowlatency N/A
 linux-backports-modules-4.8.0-17-lowlatency  N/A
 linux-firmware   1.161
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-bug yakkety

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

Title:
  ACPI: Executed 1 blocks of module-level executable AML code

Status in linux package in Ubuntu:
  New

Bug description:
  [0.121702] ACPI: Executed 1 blocks of module-level executable AML
  code

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
  ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
  Uname: Linux 4.8.0-17-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2141 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Sep 27 19:32:02 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (429 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-lowlatency N/A
   linux-backports-modules-4.8.0-17-lowlatency  N/A
   linux-firmware   1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628307/+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 1628279] Re: python utilities script suffix (.py) should be removed as per Policy 10.4

2016-09-27 Thread Eric Desrochers

** Changed in: zfs-linux (Ubuntu)
   Importance: Low => Medium

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

Title:
  python utilities script suffix (.py) should be removed as per Policy
  10.4

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  The zfs utilities scripts shipped with debian and ubuntu such as :

  * arc_summary.py : Provides a summary of the statistics
  https://github.com/zfsonlinux/zfs/blob/master/cmd/arc_summary

  * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1)
  https://github.com/zfsonlinux/zfs/tree/master/cmd/arcstat

  * dbufstat.py : Print out statistics for all cached dmu buffers
  https://github.com/zfsonlinux/zfs/blob/master/cmd/dbufstat

  should be renamed according to Policy 10.4 :

  [https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts]

  "When scripts are installed into a directory in the system PATH, the
  script name should not include an extension such as .sh or .pl that
  denotes the scripting language currently used to implement it."

  Ideally, this should be fixed and upstreamed to Debian (or to zfslinux
  upstream) as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/+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 1628279] Re: python utilities script suffix (.py) should be removed as per Policy 10.4

2016-09-27 Thread Eric Desrochers

** Changed in: zfs-linux (Ubuntu)
 Assignee: (unassigned) => Eric Desrochers (slashd)

** Changed in: zfs-linux (Ubuntu)
   Status: New => Confirmed

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

Title:
  python utilities script suffix (.py) should be removed as per Policy
  10.4

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  The zfs utilities scripts shipped with debian and ubuntu such as :

  * arc_summary.py : Provides a summary of the statistics
  https://github.com/zfsonlinux/zfs/blob/master/cmd/arc_summary

  * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1)
  https://github.com/zfsonlinux/zfs/tree/master/cmd/arcstat

  * dbufstat.py : Print out statistics for all cached dmu buffers
  https://github.com/zfsonlinux/zfs/blob/master/cmd/dbufstat

  should be renamed according to Policy 10.4 :

  [https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts]

  "When scripts are installed into a directory in the system PATH, the
  script name should not include an extension such as .sh or .pl that
  denotes the scripting language currently used to implement it."

  Ideally, this should be fixed and upstreamed to Debian (or to zfslinux
  upstream) as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/+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 1628284] Re: yakkety: daily powerpc server ISO fails to find cdrom during install in a VM

2016-09-27 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1628284

** Tags added: iso-testing

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

Title:
  yakkety: daily powerpc server ISO fails to find cdrom during install
  in a VM

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  xenial daily ISO successfully installs using the same method on the
  same system, but yakkety reports:

  Sep 27 21:13:14 cdrom-detect: Searching for Ubuntu installation media...
  Sep 27 21:13:18 cdrom-detect: Devices: ''
  Sep 27 21:13:23 cdrom-detect: Devices: ''
  Sep 27 21:13:24 kernel: [  154.649279] random: crng init done
  Sep 27 21:13:28 cdrom-detect: Devices: ''
  Sep 27 21:13:33 cdrom-detect: Devices: ''
  Sep 27 21:13:38 cdrom-detect: Devices: ''
  Sep 27 21:13:43 cdrom-detect: Devices: ''
  Sep 27 21:13:48 cdrom-detect: Devices: ''
  Sep 27 21:13:53 cdrom-detect: Devices: ''
  Sep 27 21:13:58 cdrom-detect: Devices: ''
  Sep 27 21:14:06 cdrom-detect: CDROM-detect failed; unmounting CD just to be 
sure
  Sep 27 21:14:06 main-menu[267]: WARNING **: Configuring 'cdrom-detect' failed 
with error code 1
  Sep 27 21:14:06 main-menu[267]: WARNING **: Menu item 'cdrom-detect' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628284/+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 1625794] modoc (ppc64el) - tests ran: 10, failed: 0

2016-09-27 Thread Brad Figg

tests ran:  10, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-70.78~14.04.1/modoc__3.19.0-70.78~14.04.1__2016-09-27_21-21-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-70.78~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-70.78~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1625788
  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/1625794/+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 1628279] Re: python utilities script suffix (.py) should be removed as per Policy 10.4

2016-09-27 Thread Eric Desrochers

rlaager, yes, this is reasonable.

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

Title:
  python utilities script suffix (.py) should be removed as per Policy
  10.4

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  The zfs utilities scripts shipped with debian and ubuntu such as :

  * arc_summary.py : Provides a summary of the statistics
  https://github.com/zfsonlinux/zfs/blob/master/cmd/arc_summary

  * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1)
  https://github.com/zfsonlinux/zfs/tree/master/cmd/arcstat

  * dbufstat.py : Print out statistics for all cached dmu buffers
  https://github.com/zfsonlinux/zfs/blob/master/cmd/dbufstat

  should be renamed according to Policy 10.4 :

  [https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts]

  "When scripts are installed into a directory in the system PATH, the
  script name should not include an extension such as .sh or .pl that
  denotes the scripting language currently used to implement it."

  Ideally, this should be fixed and upstreamed to Debian (or to zfslinux
  upstream) as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/+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 1626194] Re: Seccomp actions are not audited in the 4.8 kernel

2016-09-27 Thread Tyler Hicks

It looks like this was first fixed in 4.8.0-15.16 and I've verified that
it is fixed in 4.8.0-17.19.

** Changed in: linux (Ubuntu)
   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/1626194

Title:
  Seccomp actions are not audited in the 4.8 kernel

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  The following patch, released in v4.5, changed the auditing behavior of
  seccomp:

commit 96368701e1c89057bbf39222e965161c68a85b4b
Author: Paul Moore 
Date:   Wed Jan 13 09:18:55 2016 -0500

audit: force seccomp event logging to honor the audit_enabled
  flag

  In Ubuntu, where the audit subsystem is not enabled by default, it means that
  seccomp actions are not logged unless the user has installed auditd or added
  the audit=1 kernel command line parameter.

  This impacts snap confinement in Yakkety because seccomp actions are no longer
  audited which means that snap authors cannot easily know which restricted
  system calls they're using.

  To test, build the attached program:

   $ sudo apt-get install libseccomp-dev
   ...
   $ gcc -o test test.c -lseccomp

  Run the program. It should be killed when calling open().

   $ ./test
   Bad system call

  Now look in the syslog. In 4.4 kernels, there will be an audit record
  showing that the test program was killed because it called open()
  (syscall 2):

[15.055437] audit: type=1326 audit(1474477027.391:261):
  auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=12546 comm="test"
  exe="/tmp/seccomp-log/test" sig=31 arch=c03e syscall=2 compat=0
  ip=0x7fde77e45790 code=0x0

  This audit record is not present in 4.8 kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626194/+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 1627198] Re: 4.8.0 kernels do not complete boot process on VM

2016-09-27 Thread Barry Warsaw

On Sep 27, 2016, at 09:15 PM, Joseph Salisbury wrote:

>Can you see if this kernel resolves this bug?

Almost!  As mentioned in IRC, it boots but login doesn't give me a
desktop.

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

Title:
  4.8.0 kernels do not complete boot process on VM

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

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

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

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

[Kernel-packages] [Bug 1627074] onza (i386) - tests ran: 1, failed: 1

2016-09-27 Thread Brad Figg

*** This bug is a duplicate of bug 1628204 ***
https://bugs.launchpad.net/bugs/1628204

tests ran:   1, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/onza__4.4.0-40.60__2016-09-27_21-25-00/results-index.html

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

Title:
  linux: 4.4.0-40.60 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-40.60 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/1627074/+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 1628284] Missing required logs.

2016-09-27 Thread Brad Figg

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

apport-collect 1628284

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

Title:
  yakkety: daily powerpc server ISO fails to find cdrom during install
  in a VM

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  xenial daily ISO successfully installs using the same method on the
  same system, but yakkety reports:

  Sep 27 21:13:14 cdrom-detect: Searching for Ubuntu installation media...
  Sep 27 21:13:18 cdrom-detect: Devices: ''
  Sep 27 21:13:23 cdrom-detect: Devices: ''
  Sep 27 21:13:24 kernel: [  154.649279] random: crng init done
  Sep 27 21:13:28 cdrom-detect: Devices: ''
  Sep 27 21:13:33 cdrom-detect: Devices: ''
  Sep 27 21:13:38 cdrom-detect: Devices: ''
  Sep 27 21:13:43 cdrom-detect: Devices: ''
  Sep 27 21:13:48 cdrom-detect: Devices: ''
  Sep 27 21:13:53 cdrom-detect: Devices: ''
  Sep 27 21:13:58 cdrom-detect: Devices: ''
  Sep 27 21:14:06 cdrom-detect: CDROM-detect failed; unmounting CD just to be 
sure
  Sep 27 21:14:06 main-menu[267]: WARNING **: Configuring 'cdrom-detect' failed 
with error code 1
  Sep 27 21:14:06 main-menu[267]: WARNING **: Menu item 'cdrom-detect' failed.

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

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

[Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

2016-09-27 Thread Joseph Salisbury

I built a Yakkety test kernel with a revert of commit
2deb4be28077638591fe5fc593b7f8aabc140f42.

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

Can you see if this kernel resolves this bug?

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

Title:
  4.8.0 kernels do not complete boot process on VM

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

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

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

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

[Kernel-packages] [Bug 1628279] Re: python utilities script suffix (.py) should be removed as per Policy 10.4

2016-09-27 Thread Richard Laager

I just talked to Brian Behlendorf (since I'm sitting next to him at the
OpenZFS Developer Summit). He doesn't have strong feelings either way,
but is concerned about breaking people who are already relying on those
names.

My thought is we should just fix it in Debian/Ubuntu regardless of
whether it is fixed upstream.

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

Title:
  python utilities script suffix (.py) should be removed as per Policy
  10.4

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  The zfs utilities scripts shipped with debian and ubuntu such as :

  * arc_summary.py : Provides a summary of the statistics
  https://github.com/zfsonlinux/zfs/blob/master/cmd/arc_summary

  * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1)
  https://github.com/zfsonlinux/zfs/tree/master/cmd/arcstat

  * dbufstat.py : Print out statistics for all cached dmu buffers
  https://github.com/zfsonlinux/zfs/blob/master/cmd/dbufstat

  should be renamed according to Policy 10.4 :

  [https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts]

  "When scripts are installed into a directory in the system PATH, the
  script name should not include an extension such as .sh or .pl that
  denotes the scripting language currently used to implement it."

  Ideally, this should be fixed and upstreamed to Debian (or to zfslinux
  upstream) as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/+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 1628284] [NEW] yakkety: daily powerpc server ISO fails to find cdrom during install in a VM

2016-09-27 Thread Nish Aravamudan

Public bug reported:

xenial daily ISO successfully installs using the same method on the same
system, but yakkety reports:

Sep 27 21:13:14 cdrom-detect: Searching for Ubuntu installation media...
Sep 27 21:13:18 cdrom-detect: Devices: ''
Sep 27 21:13:23 cdrom-detect: Devices: ''
Sep 27 21:13:24 kernel: [  154.649279] random: crng init done
Sep 27 21:13:28 cdrom-detect: Devices: ''
Sep 27 21:13:33 cdrom-detect: Devices: ''
Sep 27 21:13:38 cdrom-detect: Devices: ''
Sep 27 21:13:43 cdrom-detect: Devices: ''
Sep 27 21:13:48 cdrom-detect: Devices: ''
Sep 27 21:13:53 cdrom-detect: Devices: ''
Sep 27 21:13:58 cdrom-detect: Devices: ''
Sep 27 21:14:06 cdrom-detect: CDROM-detect failed; unmounting CD just to be sure
Sep 27 21:14:06 main-menu[267]: WARNING **: Configuring 'cdrom-detect' failed 
with error code 1
Sep 27 21:14:06 main-menu[267]: WARNING **: Menu item 'cdrom-detect' failed.

** Affects: linux (Ubuntu)
 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/1628284

Title:
  yakkety: daily powerpc server ISO fails to find cdrom during install
  in a VM

Status in linux package in Ubuntu:
  New

Bug description:
  xenial daily ISO successfully installs using the same method on the
  same system, but yakkety reports:

  Sep 27 21:13:14 cdrom-detect: Searching for Ubuntu installation media...
  Sep 27 21:13:18 cdrom-detect: Devices: ''
  Sep 27 21:13:23 cdrom-detect: Devices: ''
  Sep 27 21:13:24 kernel: [  154.649279] random: crng init done
  Sep 27 21:13:28 cdrom-detect: Devices: ''
  Sep 27 21:13:33 cdrom-detect: Devices: ''
  Sep 27 21:13:38 cdrom-detect: Devices: ''
  Sep 27 21:13:43 cdrom-detect: Devices: ''
  Sep 27 21:13:48 cdrom-detect: Devices: ''
  Sep 27 21:13:53 cdrom-detect: Devices: ''
  Sep 27 21:13:58 cdrom-detect: Devices: ''
  Sep 27 21:14:06 cdrom-detect: CDROM-detect failed; unmounting CD just to be 
sure
  Sep 27 21:14:06 main-menu[267]: WARNING **: Configuring 'cdrom-detect' failed 
with error code 1
  Sep 27 21:14:06 main-menu[267]: WARNING **: Menu item 'cdrom-detect' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628284/+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 1627074] modoc (ppc64el) - tests ran: 64, failed: 0

2016-09-27 Thread Brad Figg

*** This bug is a duplicate of bug 1628204 ***
https://bugs.launchpad.net/bugs/1628204

tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/modoc__4.4.0-40.60__2016-09-27_20-46-00/results-index.html

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

Title:
  linux: 4.4.0-40.60 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-40.60 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/1627074/+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 1627074] onza (amd64) - tests ran: 1, failed: 1

2016-09-27 Thread Brad Figg

*** This bug is a duplicate of bug 1628204 ***
https://bugs.launchpad.net/bugs/1628204

tests ran:   1, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/onza__4.4.0-40.60__2016-09-27_21-02-00/results-index.html

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

Title:
  linux: 4.4.0-40.60 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-40.60 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/1627074/+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 1628279] Re: python utilities script suffix (.py) should be removed as per Policy 10.4

2016-09-27 Thread Eric Desrochers

It seems like "dh-exec" might do the trick.

http://manpages.ubuntu.com/manpages/xenial/man1/dh-exec-install.1.html

Example :
#! /usr/bin/dh-exec
debian/default.conf => /etc/my-package/start.conf

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

Title:
  python utilities script suffix (.py) should be removed as per Policy
  10.4

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  The zfs utilities scripts shipped with debian and ubuntu such as :

  * arc_summary.py : Provides a summary of the statistics
  https://github.com/zfsonlinux/zfs/blob/master/cmd/arc_summary

  * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1)
  https://github.com/zfsonlinux/zfs/tree/master/cmd/arcstat

  * dbufstat.py : Print out statistics for all cached dmu buffers
  https://github.com/zfsonlinux/zfs/blob/master/cmd/dbufstat

  should be renamed according to Policy 10.4 :

  [https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts]

  "When scripts are installed into a directory in the system PATH, the
  script name should not include an extension such as .sh or .pl that
  denotes the scripting language currently used to implement it."

  Ideally, this should be fixed and upstreamed to Debian (or to zfslinux
  upstream) as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/+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 1627074] dwalin (amd64) - tests ran: 10, failed: 0

2016-09-27 Thread Brad Figg

*** This bug is a duplicate of bug 1628204 ***
https://bugs.launchpad.net/bugs/1628204

tests ran:  10, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/dwalin__4.4.0-40.60__2016-09-27_19-42-00/results-index.html

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

Title:
  linux: 4.4.0-40.60 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-40.60 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/1627074/+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 1627198] Re: 4.8.0 kernels do not complete boot process on VM

2016-09-27 Thread Barry Warsaw

On Sep 27, 2016, at 08:28 PM, Joseph Salisbury wrote:

>The bisect reported the following as the first bad commit:
>
>commit 2deb4be28077638591fe5fc593b7f8aabc140f42
>Author: Andy Lutomirski 
>Date:   Thu Jul 14 13:22:55 2016 -0700
>
>x86/dumpstack: When OOPSing, rewind the stack before do_exit()

I should note that while I can't seem to capture it, the console does show
some stack track on boot.

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

Title:
  4.8.0 kernels do not complete boot process on VM

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

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

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

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

[Kernel-packages] [Bug 1628279] [NEW] python utilities script suffix (.py) should be removed as per Policy 10.4

2016-09-27 Thread Eric Desrochers

Public bug reported:

The zfs utilities scripts shipped with debian and ubuntu such as :

* arc_summary.py : Provides a summary of the statistics
https://github.com/zfsonlinux/zfs/blob/master/cmd/arc_summary

* arcstat.py : Print out ZFS ARC Statistics exported via kstat(1)
https://github.com/zfsonlinux/zfs/tree/master/cmd/arcstat

* dbufstat.py : Print out statistics for all cached dmu buffers
https://github.com/zfsonlinux/zfs/blob/master/cmd/dbufstat

should be renamed according to Policy 10.4 :

[https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts]

"When scripts are installed into a directory in the system PATH, the
script name should not include an extension such as .sh or .pl that
denotes the scripting language currently used to implement it."

Ideally, this should be fixed and upstreamed to Debian (or to zfslinux
upstream) as well.

** Affects: zfs-linux (Ubuntu)
 Importance: Low
 Status: New

** Changed in: zfs-linux (Ubuntu)
   Importance: Undecided => Low

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

Title:
  python utilities script suffix (.py) should be removed as per Policy
  10.4

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  The zfs utilities scripts shipped with debian and ubuntu such as :

  * arc_summary.py : Provides a summary of the statistics
  https://github.com/zfsonlinux/zfs/blob/master/cmd/arc_summary

  * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1)
  https://github.com/zfsonlinux/zfs/tree/master/cmd/arcstat

  * dbufstat.py : Print out statistics for all cached dmu buffers
  https://github.com/zfsonlinux/zfs/blob/master/cmd/dbufstat

  should be renamed according to Policy 10.4 :

  [https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts]

  "When scripts are installed into a directory in the system PATH, the
  script name should not include an extension such as .sh or .pl that
  denotes the scripting language currently used to implement it."

  Ideally, this should be fixed and upstreamed to Debian (or to zfslinux
  upstream) as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/+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 1625794] onza (i386) - tests ran: 1, failed: 1

2016-09-27 Thread Brad Figg

tests ran:   1, failed: 1;
  
http://kernel.ubuntu.com/testing/3.19.0-70.78~14.04.1/onza__3.19.0-70.78~14.04.1__2016-09-27_20-39-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-70.78~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-70.78~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1625788
  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/1625794/+subscriptions

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

[Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

2016-09-27 Thread Joseph Salisbury

The bisect reported the following as the first bad commit:

commit 2deb4be28077638591fe5fc593b7f8aabc140f42
Author: Andy Lutomirski 
Date:   Thu Jul 14 13:22:55 2016 -0700

x86/dumpstack: When OOPSing, rewind the stack before do_exit()

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

Title:
  4.8.0 kernels do not complete boot process on VM

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

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

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

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

[Kernel-packages] [Bug 1625794] onza (amd64) - tests ran: 1, failed: 1

2016-09-27 Thread Brad Figg

tests ran:   1, failed: 1;
  
http://kernel.ubuntu.com/testing/3.19.0-70.78~14.04.1/onza__3.19.0-70.78~14.04.1__2016-09-27_20-17-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-70.78~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-70.78~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1625788
  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/1625794/+subscriptions

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

[Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

2016-09-27 Thread Joseph Salisbury

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

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

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

Title:
  4.8.0 kernels do not complete boot process on VM

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

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

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

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

[Kernel-packages] [Bug 1627074] modoc (ppc64el) - tests ran: 2, failed: 0

2016-09-27 Thread Brad Figg

*** This bug is a duplicate of bug 1628204 ***
https://bugs.launchpad.net/bugs/1628204

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/modoc__4.4.0-40.60__2016-09-27_20-15-00/results-index.html

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

Title:
  linux: 4.4.0-40.60 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-40.60 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/1627074/+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 1628173] Re: ISST-LTE:pVM:roselp2:ubuntu 16.10: crash failed to check vmcore of 4.8 kernel

2016-09-27 Thread Chris J Arges

Uploaded fix into yakkety, pending approval in queue.

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

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

** Changed in: crash (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => Chris J Arges (arges)

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

Title:
  ISST-LTE:pVM:roselp2:ubuntu 16.10: crash failed to check vmcore of 4.8
  kernel

Status in crash package in Ubuntu:
  In Progress

Bug description:
  == Comment: #0 - Ping Tian Han  - 2016-09-22 03:05:36 ==
  ---Problem Description---
  crash cannot check vmcore of 4.8 kernel. 

  Then when trying to check the core with crash:

  % sudo crash /usr/lib/debug/boot/vmlinux-4.8.0-14-generic
  /var/crash/201609212349/vmcore.201609212349

  crash 7.1.5
  Copyright (C) 2002-2016  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering kmem slab cache data)
  crash: invalid kernel virtual address: 7aa9fe0100  type: "pmd page"

   
  ---uname output---
  Linux roselp2 4.8.0-14-generic #15-Ubuntu SMP Tue Sep 20 21:59:33 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = IBM,8286-42A, lpar 
   
  ---Steps to Reproduce---
   1. install 4.8 kernel
  2. trigger kdump to get vmcore
  3. check the vmcore with crash

  
  == Comment: #8 - Hari Krishna Bathini  - 2016-09-24 14:12:23 ==
  The below commit is needed for vtop address translation to succeed

commit 182914debbb9a2671ef644027fedd339aa9c80e0
Author: Dave Anderson 
Date:   Fri Sep 23 09:09:15 2016 -0400

  With the introduction of radix MMU in Power ISA 3.0, there are
  changes in kernel page table management accommodating it.  This patch
  series makes appropriate changes here to work for such kernels.
  Also, this series fixes a few bugs along the way:
  
ppc64: fix vtop page translation for 4K pages
ppc64: Use kernel terminology for each level in 4-level page table
ppc64/book3s: address changes in kernel v4.5
ppc64/book3s: address change in page flags for PowerISA v3.0
ppc64: use physical addresses and unfold pud for 64K page size
ppc64/book3s: support big endian Linux page tables
  
  The patches are needed for Linux v4.5 and later kernels on all
  ppc64 hardware.
  (hbath...@linux.vnet.ibm.com)
  --

  Also, the below commit is needed

commit 8ceb1ac628bf6a0a7f0bbfff030ec93081bca4cd
Author: Dave Anderson 
Date:   Mon May 23 11:23:01 2016 -0400

  Fix for Linux commit 0139aa7b7fa12ceef095d99dc36606a5b10ab83a, which
  renamed the page._count member to page._refcount.  Without the patch,
  certain "kmem" commands fail with the "kmem: invalid structure member
  offset: page_count".
  (ander...@redhat.com)

  Thanks
  Hari

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1628173/+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 1628187] Re: vNIC driver missing in 4.8 kernel package

2016-09-27 Thread Tim Gardner

** Also affects: linux (Ubuntu Yakkety)
   Importance: Critical
 Assignee: Leann Ogasawara (leannogasawara)
   Status: 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/1628187

Title:
  vNIC driver missing in 4.8 kernel package

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  == Comment: #0 - Ping Tian Han - 2016-09-22 01:20:10 ==
  ---Problem Description---
  There is on "ibmvnic" in 4.8.0-14-generic package:

  root@roselp2:~# uname -a
  Linux roselp2 4.8.0-14-generic #15-Ubuntu SMP Tue Sep 20 21:59:33 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  root@roselp2:~# modprobe ibmvnic
  modprobe: FATAL: Module ibmvnic not found in directory 
/lib/modules/4.8.0-14-generic
  root@roselp2:~# 

  so the vNIC device which  works well under 4.4 kernel doens't work
  now.

  == Comment: #6 - Kevin W. Rudd - 2016-09-27 11:49:32 ==
  From Bug 146781, this is still an issue with 4.8.0-17:

  ---
  Have installed lpar  using virtual  Ether adapter and after installation am 
not able to find vnic adapters 

  root@miglp2:~# modprobe ibmvnic
  modprobe: FATAL: Module ibmvnic not found in directory 
/lib/modules/4.8.0-17-generic
  root@miglp2:~#

  root@miglp2:~# ifconfig -a
  ibmveth2: flags=4163  mtu 1500
  inet 10.33.15.21  netmask 255.255.0.0  broadcast 10.33.255.255
  inet6 fe80::140f:bbff:fe6b:9502  prefixlen 64  scopeid 0x20
  inet6 2002:903:15f:1130:140f:bbff:fe6b:9502  prefixlen 64  scopeid 
0x0
  inet6 2002:926:3e2:1130:140f:bbff:fe6b:9502  prefixlen 64  scopeid 
0x0
  ether 16:0f:bb:6b:95:02  txqueuelen 1000  (Ethernet)
  RX packets 437923  bytes 29797431 (29.7 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 153  bytes 13014 (13.0 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  device interrupt 19

  lo: flags=73  mtu 65536
  inet 127.0.0.1  netmask 255.0.0.0
  inet6 ::1  prefixlen 128  scopeid 0x10
  loop  txqueuelen 1  (Local Loopback)
  RX packets 326  bytes 24184 (24.1 KB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 326  bytes 24184 (24.1 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  ---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628187/+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 1571535] Re: iwlwifi restarts randomly in xenial

2016-09-27 Thread Ekimia

Is there a master BUg for this ? this is a major problem even in 16.04.1
with latest updates.

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

Title:
  iwlwifi restarts randomly in xenial

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Recently installed xenial on a Lenovo Yoga 2-13 (Intel 7260 wifi
  card).  On wily it worked perfectly, on xenial it regularly appears to
  restart the wifi connection (the end result is that I lose any vpn
  connections, as they don't seem to notice the restart, but that's
  another issue).

  In general use, I get periodic "wlp1s0: WPA: Group rekeying completed"
  messages in syslog (and used to get these in wily, too), but now,
  after a random amount of time (over the weekend it was several hours,
  this morning it was about 10 minutes, so it might be related to the
  amount of network traffic) I get "kernel: [13983.248157] wlp1s0:
  authenticate with 00:8a:ae:c9:9a:d8" (presumably my wifi router) and
  the usual wifi startup stuff including frequency lists, etc.

  It also always logs "systemd-udevd[30319]: Process '/sbin/crda' failed
  with exit code 249." every time (I'm not sure if this is relevant)

  After reading old, but similar bug reports, I've tried changing some
  of the module options: "11n_disable=1" and "11n_disable=8", but these
  had no effect.  I've also tried the older firmware that wily used
  (/lib/firmware/iwlwifi-7260-13.ucode), but again, no improvement.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  7058 F pulseaudio
   /dev/snd/controlC1:  chris  7058 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Apr 18 09:01:26 2016
  HibernationDevice: RESUME=UUID=f92d915f-d552-4e5b-989d-70e936ce4f74
  InstallationDate: Installed on 2016-04-14 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  MachineType: LENOVO 20344
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-18-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-generic N/A
   linux-backports-modules-4.4.0-18-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN25WW(V1.11)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN25WW(V1.11):bd07/09/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

2016-09-27 Thread Joseph Salisbury

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

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

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

Title:
  4.8.0 kernels do not complete boot process on VM

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

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

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

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

[Kernel-packages] [Bug 1627074] modoc (ppc64el) - tests ran: 83, failed: 51

2016-09-27 Thread Brad Figg

*** This bug is a duplicate of bug 1628204 ***
https://bugs.launchpad.net/bugs/1628204

tests ran:  83, failed: 51;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/modoc__4.4.0-40.60__2016-09-27_17-26-00/results-index.html

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

Title:
  linux: 4.4.0-40.60 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-40.60 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/1627074/+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 1628241] Re: Enable switchdev config parameter for Yakkety

2016-09-27 Thread Tim Gardner

UBUNTU: [Config] CONFIG_NET_SWITCHDEV=y for amd64/arm64

** Changed in: linux (Ubuntu)
   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/1628241

Title:
  Enable switchdev config parameter for Yakkety

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Hi,

  To support switchdev as an inbox feature of Ubuntu Core, we would need
  the Ubuntu kernel to build with switchdev support, by setting
  NET_SWITCHDEV.

  Can we turn this on for Yakkety?  We have hardware that Luke Williams
  can use to verify working kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628241/+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 1625794] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 19, failed: 11

2016-09-27 Thread Brad Figg

tests ran:  19, failed: 11;
  
http://kernel.ubuntu.com/testing/3.19.0-70.78~14.04.1/ms10-35-mcdivittB0-kernel__3.19.0-70.78~14.04.1__2016-09-27_19-14-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-70.78~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-70.78~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1625788
  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/1625794/+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 1628009] Re: Ubuntu 16.10 kernel v4.8: Installation failing on Habanero with Shiner card

2016-09-27 Thread Tim Gardner

UBUNTU: firmware: Update bnx2x to 7.13.1.0

** Changed in: linux (Ubuntu Yakkety)
   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/1628009

Title:
  Ubuntu 16.10 kernel v4.8: Installation failing on Habanero with Shiner
  card

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  Problem Description
  
  Ubuntu 16.10 installer fails to configure network during installation. We are 
using Shiner adapter with bnx2x driver. looks like ubuntu installer does not 
have the firmware for it. Below is what I see in syslog:

  /var/log # cat syslog | grep -i bnx2x
  Sep 27 05:45:01 kernel: [   53.610983] bnx2x: QLogic 5771x/578xx 
10/20-Gigabit Ethernet Driver bnx2x 1.712.30-0 (2014/02/10)
  Sep 27 05:45:01 kernel: [   53.611167] bnx2x 0001:0c:00.0: msix capability 
found
  Sep 27 05:45:01 kernel: [   53.628231] bnx2x 0001:0c:00.0: Using 64-bit DMA 
iommu bypass
  Sep 27 05:45:01 kernel: [   53.628273] bnx2x 0001:0c:00.0: part number 0-0-0-0
  Sep 27 05:45:01 kernel: [   60.817161] bnx2x 0001:0c:00.1: msix capability 
found
  Sep 27 05:45:01 kernel: [   60.835940] bnx2x 0001:0c:00.1: Using 64-bit DMA 
iommu bypass
  Sep 27 05:45:01 kernel: [   60.835980] bnx2x 0001:0c:00.1: part number 0-0-0-0
  Sep 27 05:45:01 kernel: [   62.417124] bnx2x 0001:0c:00.2: msix capability 
found
  Sep 27 05:45:01 kernel: [   62.435935] bnx2x 0001:0c:00.2: Using 64-bit DMA 
iommu bypass
  Sep 27 05:45:01 kernel: [   62.435974] bnx2x 0001:0c:00.2: part number 0-0-0-0
  Sep 27 05:45:01 kernel: [   62.627147] bnx2x 0001:0c:00.3: msix capability 
found
  Sep 27 05:45:01 kernel: [   62.643972] bnx2x 0001:0c:00.3: Using 64-bit DMA 
iommu bypass
  Sep 27 05:45:01 kernel: [   62.644024] bnx2x 0001:0c:00.3: part number 0-0-0-0
  Sep 27 05:45:01 kernel: [   62.798136] bnx2x 0001:0c:00.0 enP1p12s0f0: 
renamed from eth0
  Sep 27 05:45:01 kernel: [   62.976102] bnx2x 0001:0c:00.1 enP1p12s0f1: 
renamed from eth1
  Sep 27 05:45:01 kernel: [   63.139992] bnx2x 0001:0c:00.2 enP1p12s0f2: 
renamed from eth2
  Sep 27 05:45:01 kernel: [   63.279984] bnx2x 0001:0c:00.3 enP1p12s0f3: 
renamed from eth3
  Sep 27 05:46:03 kernel: [  127.619915] bnx2x 0001:0c:00.0: Direct firmware 
load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2
  Sep 27 05:46:03 kernel: [  127.619917] bnx2x: 
[bnx2x_init_firmware:13427(enP1p12s0f0)]Can't load firmware file 
bnx2x/bnx2x-e2-7.13.1.0.fw
  Sep 27 05:46:03 kernel: [  127.619918] bnx2x: 
[bnx2x_func_hw_init:5785(enP1p12s0f0)]Error loading firmware
  Sep 27 05:46:03 kernel: [  127.619921] bnx2x: 
[bnx2x_nic_load:2727(enP1p12s0f0)]HW init failed, aborting
  Sep 27 05:46:03 kernel: [  128.051899] bnx2x 0001:0c:00.1: Direct firmware 
load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2
  Sep 27 05:46:03 kernel: [  128.051901] bnx2x: 
[bnx2x_init_firmware:13427(enP1p12s0f1)]Can't load firmware file 
bnx2x/bnx2x-e2-7.13.1.0.fw
  Sep 27 05:46:03 kernel: [  128.051902] bnx2x: 
[bnx2x_func_hw_init:5785(enP1p12s0f1)]Error loading firmware
  Sep 27 05:46:03 kernel: [  128.051904] bnx2x: 
[bnx2x_nic_load:2727(enP1p12s0f1)]HW init failed, aborting
  Sep 27 05:46:03 kernel: [  128.155912] bnx2x 0001:0c:00.2: Direct firmware 
load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2
  Sep 27 05:46:03 kernel: [  128.155915] bnx2x: 
[bnx2x_init_firmware:13427(enP1p12s0f2)]Can't load firmware file 
bnx2x/bnx2x-e2-7.13.1.0.fw
  Sep 27 05:46:03 kernel: [  128.155916] bnx2x: 
[bnx2x_func_hw_init:5785(enP1p12s0f2)]Error loading firmware
  Sep 27 05:46:03 kernel: [  128.155919] bnx2x: 
[bnx2x_nic_load:2727(enP1p12s0f2)]HW init failed, aborting
  Sep 27 05:46:03 kernel: [  128.279895] bnx2x 0001:0c:00.3: Direct firmware 
load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2
  Sep 27 05:46:03 kernel: [  128.279898] bnx2x: 
[bnx2x_init_firmware:13427(enP1p12s0f3)]Can't load firmware file 
bnx2x/bnx2x-e2-7.13.1.0.fw
  Sep 27 05:46:03 kernel: [  128.279899] bnx2x: 
[bnx2x_func_hw_init:5785(enP1p12s0f3)]Error loading firmware
  Sep 27 05:46:03 kernel: [  128.279902] bnx2x: 
[bnx2x_nic_load:2727(enP1p12s0f3)]HW init failed, aborting
  Sep 27 05:46:11 kernel: [  135.779921] bnx2x 0001:0c:00.2: Direct firmware 
load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2
  Sep 27 05:46:11 kernel: [  135.779924] bnx2x: 
[bnx2x_init_firmware:13427(enP1p12s0f2)]Can't load firmware file 
bnx2x/bnx2x-e2-7.13.1.0.fw
  Sep 27 05:46:11 kernel: [  135.779925] bnx2x: 
[bnx2x_func_hw_init:5785(enP1p12s0f2)]Error loading firmware
  Sep 27 05:46:11 kernel: [  135.779928] bnx2x: 
[bnx2x_nic_load:2727(enP1p12s0f2)]HW init failed, aborting

  
  This is blocking netboot installation of Ubuntu 16.10. This had worked when I 
tried installation when Ubuntu 16.10 had 4.4 kernel. This is regression issue

[Kernel-packages] [Bug 1628111] Re: [Yakkety] enable EDAC_GHES in kernel config

2016-09-27 Thread Tim Gardner

** Also affects: linux (Ubuntu Z-series)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Z-series)
 Assignee: (unassigned) => Manoj Iyer (manjo)

** Changed in: linux (Ubuntu Z-series)
Milestone: None => ubuntu-17.04

** Changed in: linux (Ubuntu Yakkety)
   Status: Incomplete => Won't Fix

** Changed in: linux (Ubuntu Z-series)
   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/1628111

Title:
  [Yakkety] enable EDAC_GHES in kernel config

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Yakkety:
  Won't Fix
Status in linux source package in z-series:
  In Progress

Bug description:
  EDAC_GHES is essential for ARMv8.0 Server systems, as it enables
  firmware-first error handling of memory and CPU errors. Due to a lack
  of standard RAS architecture (or machine check architecture
  equivalent) on ARMv8.0 systems, APEI/GHES is the only mechanism
  available for reporting hardware errors (e.g. memory and CPU errors).
  This enables reporting of hardware errors, and also helps enable
  memory fault recovery mechanisms to extend the life of the system by
  offlining pages when recoverable uncorrected errors are encountered.
  Note that other ARM vendors will be going in this direction for
  hardware error handling.

  Currently ACPI_APEI_GHES=n is in Ubuntu and CONFIG_EDAC_MM_EDAC=m for
  ARM64, but EDAC_GHES requires this to be =y therefore it is not
  selected.

  == SRU Request ==

  [Impact]
  * As a result of ACPI_APEI_GHES=n and CONFIG_EDAC_MM_EDAC=m for ARM64, 
EDAC_GHES is not selected on kernel build. This results in loss of 
functionality needed for firmware error handling of memory and CPU errors.

  [Test Case]
  * NA

  [Regression Potential]
  * None.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628111/+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 1628173] Re: ISST-LTE:pVM:roselp2:ubuntu 16.10: crash failed to check vmcore of 4.8 kernel

2016-09-27 Thread Leann Ogasawara

https://github.com/crash-
utility/crash/commit/182914debbb9a2671ef644027fedd339aa9c80e0

https://github.com/crash-
utility/crash/commit/8ceb1ac628bf6a0a7f0bbfff030ec93081bca4cd


** Tags added: kernel-4.8

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

Title:
  ISST-LTE:pVM:roselp2:ubuntu 16.10: crash failed to check vmcore of 4.8
  kernel

Status in crash package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Ping Tian Han  - 2016-09-22 03:05:36 ==
  ---Problem Description---
  crash cannot check vmcore of 4.8 kernel. 

  Then when trying to check the core with crash:

  % sudo crash /usr/lib/debug/boot/vmlinux-4.8.0-14-generic
  /var/crash/201609212349/vmcore.201609212349

  crash 7.1.5
  Copyright (C) 2002-2016  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering kmem slab cache data)
  crash: invalid kernel virtual address: 7aa9fe0100  type: "pmd page"

   
  ---uname output---
  Linux roselp2 4.8.0-14-generic #15-Ubuntu SMP Tue Sep 20 21:59:33 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = IBM,8286-42A, lpar 
   
  ---Steps to Reproduce---
   1. install 4.8 kernel
  2. trigger kdump to get vmcore
  3. check the vmcore with crash

  
  == Comment: #8 - Hari Krishna Bathini  - 2016-09-24 14:12:23 ==
  The below commit is needed for vtop address translation to succeed

commit 182914debbb9a2671ef644027fedd339aa9c80e0
Author: Dave Anderson 
Date:   Fri Sep 23 09:09:15 2016 -0400

  With the introduction of radix MMU in Power ISA 3.0, there are
  changes in kernel page table management accommodating it.  This patch
  series makes appropriate changes here to work for such kernels.
  Also, this series fixes a few bugs along the way:
  
ppc64: fix vtop page translation for 4K pages
ppc64: Use kernel terminology for each level in 4-level page table
ppc64/book3s: address changes in kernel v4.5
ppc64/book3s: address change in page flags for PowerISA v3.0
ppc64: use physical addresses and unfold pud for 64K page size
ppc64/book3s: support big endian Linux page tables
  
  The patches are needed for Linux v4.5 and later kernels on all
  ppc64 hardware.
  (hbath...@linux.vnet.ibm.com)
  --

  Also, the below commit is needed

commit 8ceb1ac628bf6a0a7f0bbfff030ec93081bca4cd
Author: Dave Anderson 
Date:   Mon May 23 11:23:01 2016 -0400

  Fix for Linux commit 0139aa7b7fa12ceef095d99dc36606a5b10ab83a, which
  renamed the page._count member to page._refcount.  Without the patch,
  certain "kmem" commands fail with the "kmem: invalid structure member
  offset: page_count".
  (ander...@redhat.com)

  Thanks
  Hari

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

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

[Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

2016-09-27 Thread Joseph Salisbury

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

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

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

Title:
  4.8.0 kernels do not complete boot process on VM

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

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

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

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

[Kernel-packages] [Bug 1628241] Re: Enable switchdev config parameter for Yakkety

2016-09-27 Thread Tim Gardner

** Package changed: linux-signed (Ubuntu) => linux (Ubuntu)

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  Enable switchdev config parameter for Yakkety

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Hi,

  To support switchdev as an inbox feature of Ubuntu Core, we would need
  the Ubuntu kernel to build with switchdev support, by setting
  NET_SWITCHDEV.

  Can we turn this on for Yakkety?  We have hardware that Luke Williams
  can use to verify working kernels.

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

2016-09-27 Thread bugproxy

--- Comment From ru...@us.ibm.com 2016-09-27 15:17 EDT---
*** Bug 146786 has been marked as a duplicate of this bug. ***

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

Title:
  Ubuntu 16.10 kernel v4.8: Installation failing on Habanero with Shiner
  card

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  Problem Description
  
  Ubuntu 16.10 installer fails to configure network during installation. We are 
using Shiner adapter with bnx2x driver. looks like ubuntu installer does not 
have the firmware for it. Below is what I see in syslog:

  /var/log # cat syslog | grep -i bnx2x
  Sep 27 05:45:01 kernel: [   53.610983] bnx2x: QLogic 5771x/578xx 
10/20-Gigabit Ethernet Driver bnx2x 1.712.30-0 (2014/02/10)
  Sep 27 05:45:01 kernel: [   53.611167] bnx2x 0001:0c:00.0: msix capability 
found
  Sep 27 05:45:01 kernel: [   53.628231] bnx2x 0001:0c:00.0: Using 64-bit DMA 
iommu bypass
  Sep 27 05:45:01 kernel: [   53.628273] bnx2x 0001:0c:00.0: part number 0-0-0-0
  Sep 27 05:45:01 kernel: [   60.817161] bnx2x 0001:0c:00.1: msix capability 
found
  Sep 27 05:45:01 kernel: [   60.835940] bnx2x 0001:0c:00.1: Using 64-bit DMA 
iommu bypass
  Sep 27 05:45:01 kernel: [   60.835980] bnx2x 0001:0c:00.1: part number 0-0-0-0
  Sep 27 05:45:01 kernel: [   62.417124] bnx2x 0001:0c:00.2: msix capability 
found
  Sep 27 05:45:01 kernel: [   62.435935] bnx2x 0001:0c:00.2: Using 64-bit DMA 
iommu bypass
  Sep 27 05:45:01 kernel: [   62.435974] bnx2x 0001:0c:00.2: part number 0-0-0-0
  Sep 27 05:45:01 kernel: [   62.627147] bnx2x 0001:0c:00.3: msix capability 
found
  Sep 27 05:45:01 kernel: [   62.643972] bnx2x 0001:0c:00.3: Using 64-bit DMA 
iommu bypass
  Sep 27 05:45:01 kernel: [   62.644024] bnx2x 0001:0c:00.3: part number 0-0-0-0
  Sep 27 05:45:01 kernel: [   62.798136] bnx2x 0001:0c:00.0 enP1p12s0f0: 
renamed from eth0
  Sep 27 05:45:01 kernel: [   62.976102] bnx2x 0001:0c:00.1 enP1p12s0f1: 
renamed from eth1
  Sep 27 05:45:01 kernel: [   63.139992] bnx2x 0001:0c:00.2 enP1p12s0f2: 
renamed from eth2
  Sep 27 05:45:01 kernel: [   63.279984] bnx2x 0001:0c:00.3 enP1p12s0f3: 
renamed from eth3
  Sep 27 05:46:03 kernel: [  127.619915] bnx2x 0001:0c:00.0: Direct firmware 
load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2
  Sep 27 05:46:03 kernel: [  127.619917] bnx2x: 
[bnx2x_init_firmware:13427(enP1p12s0f0)]Can't load firmware file 
bnx2x/bnx2x-e2-7.13.1.0.fw
  Sep 27 05:46:03 kernel: [  127.619918] bnx2x: 
[bnx2x_func_hw_init:5785(enP1p12s0f0)]Error loading firmware
  Sep 27 05:46:03 kernel: [  127.619921] bnx2x: 
[bnx2x_nic_load:2727(enP1p12s0f0)]HW init failed, aborting
  Sep 27 05:46:03 kernel: [  128.051899] bnx2x 0001:0c:00.1: Direct firmware 
load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2
  Sep 27 05:46:03 kernel: [  128.051901] bnx2x: 
[bnx2x_init_firmware:13427(enP1p12s0f1)]Can't load firmware file 
bnx2x/bnx2x-e2-7.13.1.0.fw
  Sep 27 05:46:03 kernel: [  128.051902] bnx2x: 
[bnx2x_func_hw_init:5785(enP1p12s0f1)]Error loading firmware
  Sep 27 05:46:03 kernel: [  128.051904] bnx2x: 
[bnx2x_nic_load:2727(enP1p12s0f1)]HW init failed, aborting
  Sep 27 05:46:03 kernel: [  128.155912] bnx2x 0001:0c:00.2: Direct firmware 
load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2
  Sep 27 05:46:03 kernel: [  128.155915] bnx2x: 
[bnx2x_init_firmware:13427(enP1p12s0f2)]Can't load firmware file 
bnx2x/bnx2x-e2-7.13.1.0.fw
  Sep 27 05:46:03 kernel: [  128.155916] bnx2x: 
[bnx2x_func_hw_init:5785(enP1p12s0f2)]Error loading firmware
  Sep 27 05:46:03 kernel: [  128.155919] bnx2x: 
[bnx2x_nic_load:2727(enP1p12s0f2)]HW init failed, aborting
  Sep 27 05:46:03 kernel: [  128.279895] bnx2x 0001:0c:00.3: Direct firmware 
load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2
  Sep 27 05:46:03 kernel: [  128.279898] bnx2x: 
[bnx2x_init_firmware:13427(enP1p12s0f3)]Can't load firmware file 
bnx2x/bnx2x-e2-7.13.1.0.fw
  Sep 27 05:46:03 kernel: [  128.279899] bnx2x: 
[bnx2x_func_hw_init:5785(enP1p12s0f3)]Error loading firmware
  Sep 27 05:46:03 kernel: [  128.279902] bnx2x: 
[bnx2x_nic_load:2727(enP1p12s0f3)]HW init failed, aborting
  Sep 27 05:46:11 kernel: [  135.779921] bnx2x 0001:0c:00.2: Direct firmware 
load for bnx2x/bnx2x-e2-7.13.1.0.fw failed with error -2
  Sep 27 05:46:11 kernel: [  135.779924] bnx2x: 
[bnx2x_init_firmware:13427(enP1p12s0f2)]Can't load firmware file 
bnx2x/bnx2x-e2-7.13.1.0.fw
  Sep 27 05:46:11 kernel: [  135.779925] bnx2x: 
[bnx2x_func_hw_init:5785(enP1p12s0f2)]Error loading firmware
  Sep 27 05:46:11 kernel: [  135.779928] bnx2x: 
[bnx2x_nic_load:2727(enP1p12s0f2)]HW init failed, aborting

  
  This is blocking netboot installation of Ubuntu 16.10. This had worked when I 
tried installation when Ubuntu 16.10 had 4.4 kernel. This is regression issue

[Kernel-packages] [Bug 1626564] Re: 4.8 regression: SLAB is being used instead of SLUB

2016-09-27 Thread Doug Smythies

I filed two bug reports upstream:

https://bugzilla.kernel.org/show_bug.cgi?id=172991
https://bugzilla.kernel.org/show_bug.cgi?id=172981

I also made a kernel 4.8-rc8 with 81ae6d03 reverted (because it is so trivial 
to revert) and no matter how hard I beat on it I can not get it to mess up.
 

** Bug watch added: Linux Kernel Bug Tracker #172991
   http://bugzilla.kernel.org/show_bug.cgi?id=172991

** Bug watch added: Linux Kernel Bug Tracker #172981
   http://bugzilla.kernel.org/show_bug.cgi?id=172981

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

Title:
  4.8 regression: SLAB is being used instead of SLUB

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

Bug description:
  We're seeing hundreds of kernel worker threads being spawned with some
  actions, for example, after booting the desktop and hutting the
  brightness keys causes this.  On investigation, this occurs when
  CONFIG_SLAB is being used.

  1. Ubuntu traditionally uses CONFIG_SLUB, so we should use that instead of 
CONFIG_SLAB (why was it changed for Yakkety?)
  2. With CONFIG_SLUB I cannot reproduce the issue of the hundreds for worker 
threads
  3 CONFIG_SLUB seems more performant on the boot too over SLAB.

  Please re-enable the CONFIG_SLUB allocator as per the 4.4. Xenial
  configs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626564/+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 1628187] Re: vNIC driver missing in 4.8 kernel package

2016-09-27 Thread Leann Ogasawara

I've pushed this fix to the tip of yakkety master-next.  I also added an
enforcement to our annotations file to ensure this doesn't get disabled
moving forward.  Thanks.

** Changed in: linux (Ubuntu)
   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/1628187

Title:
  vNIC driver missing in 4.8 kernel package

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  == Comment: #0 - Ping Tian Han - 2016-09-22 01:20:10 ==
  ---Problem Description---
  There is on "ibmvnic" in 4.8.0-14-generic package:

  root@roselp2:~# uname -a
  Linux roselp2 4.8.0-14-generic #15-Ubuntu SMP Tue Sep 20 21:59:33 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  root@roselp2:~# modprobe ibmvnic
  modprobe: FATAL: Module ibmvnic not found in directory 
/lib/modules/4.8.0-14-generic
  root@roselp2:~# 

  so the vNIC device which  works well under 4.4 kernel doens't work
  now.

  == Comment: #6 - Kevin W. Rudd - 2016-09-27 11:49:32 ==
  From Bug 146781, this is still an issue with 4.8.0-17:

  ---
  Have installed lpar  using virtual  Ether adapter and after installation am 
not able to find vnic adapters 

  root@miglp2:~# modprobe ibmvnic
  modprobe: FATAL: Module ibmvnic not found in directory 
/lib/modules/4.8.0-17-generic
  root@miglp2:~#

  root@miglp2:~# ifconfig -a
  ibmveth2: flags=4163  mtu 1500
  inet 10.33.15.21  netmask 255.255.0.0  broadcast 10.33.255.255
  inet6 fe80::140f:bbff:fe6b:9502  prefixlen 64  scopeid 0x20
  inet6 2002:903:15f:1130:140f:bbff:fe6b:9502  prefixlen 64  scopeid 
0x0
  inet6 2002:926:3e2:1130:140f:bbff:fe6b:9502  prefixlen 64  scopeid 
0x0
  ether 16:0f:bb:6b:95:02  txqueuelen 1000  (Ethernet)
  RX packets 437923  bytes 29797431 (29.7 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 153  bytes 13014 (13.0 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  device interrupt 19

  lo: flags=73  mtu 65536
  inet 127.0.0.1  netmask 255.0.0.0
  inet6 ::1  prefixlen 128  scopeid 0x10
  loop  txqueuelen 1  (Local Loopback)
  RX packets 326  bytes 24184 (24.1 KB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 326  bytes 24184 (24.1 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  ---

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

1 2 3 >

1 - 100 of 293 matches

Mail list logo