[Kernel-packages] [Bug 1566302] Re: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16

[Mingyang Li]

Using ASUS E200HA, same issue happened on kernel 4.4.0-35,
4.4.14-xenial, and 4.7.2, none of them have fixed the issue. For a quick
reference, this notebook's CPU is Intel Atom x5-Z8300, and it contains
Graphics Intel HD Graphics (Cherryview).

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

Title:
  Ubuntu 16.04: Suspend freezes the system after upgrade to linux image
  4.4.0-16

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  I'm using ubuntu 16.04 on a XPS 15 9550.

  Suspend/resume worked flawlessly with linux image 4.4.0-15, and after
  standard upgrade yesterday (5/04/2016) which installed image 4.4.0-16,
  the system freezes when attempting a suspend. I get  no response from
  the system (nor keyboard, nor screen, nor touchpad), but it gets very
  hot, so that it must be running something.

  Booting with 4.4.0-15 makes the suspend to work perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  macias 1770 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Tue Apr  5 14:56:17 2016
  HibernationDevice: RESUME=UUID=4180adfa-3852-4a96-86b4-f3696448c743
  InstallationDate: Installed on 2016-03-07 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed 
root=UUID=673f4658-75f8-4c01-bcd8-0af860269699 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566302/+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 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

[harry]

this one is broken. Same blackscreen.

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

Title:
  Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

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

Bug description:
  When I install Ubuntu 16.04 on my computer the screen goes blank at
  login. I can blindly login and it boots but I cannot use the display
  (external monitor through HDMI).

  I've looked online for an answer to this issue but could not find a
  solution.  However, many people report this issue in forums with the
  4.4x kernel.

  On my main computer, I upgraded from 14.04 to 16.04.1. On this
  computer I was able to switch back to the 3.13 kernel which *does
  work*.

  On the same computer, if I use a 16.04 live CD, it does the same
  thing.  The screen goes blank.

  UEFI may be part of the issue as well.  I have it disabled in bios
  (set to legacy mode) but when I first boot, it seems to go into UEFI
  mode first and then, after rebooting with  it shows
  me the list of kernels. I can select the kernel from there but if I
  use a 4.4x kernel, it blanks out at encryption passphrase screen.

  There are also people with similar issues on AskUbuntu.

  Here's some basic HW info.  If you require more, please ask.

  sudo lshw | head
  zbox
  description: Notebook
  product: ZBOX-ID18 (NA)
  vendor: ZOTAC
  version: XX
  serial: G211X
  width: 64 bits
  capabilities: smbios-2.7 dmi-2.7 vsyscall32
  configuration: boot=normal chassis=notebook family=NA sku=NA 
uuid=00020003-0004-0005-0006-000700080009
    *-core

  sudo lshw -C display
    *-display
     description: VGA compatible controller
     product: 3rd Gen Core processor Graphics Controller
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 09
     width: 64 bits
     clock: 33MHz
     capabilities: msi pm vga_controller bus_master cap_list rom
     configuration: driver=i915 latency=0
     resources: irq:45 memory:f780-f7bf memory:e000-efff 
ioport:f000(size=64)

  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user5536 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: #RESUME=UUID=edaa55c6-eb56-43fb-8004-495948b72b38
  InstallationDate: Installed on 2014-07-23 (743 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313)
  MachineType: ZOTAC ZBOX-ID18
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39
  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-3.13.0-92-generic N/A
   linux-backports-modules-3.13.0-92-generic  N/A
   linux-firmware 1.157.2
  RfKill:

  StagingDrivers: rts5139
  Tags:  xenial staging
  Uname: Linux 3.13.0-92-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-31 (3 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B211P011
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID18
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 10
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB211P011:bd03/13/2014:svnZOTAC:pnZBOX-ID18:pvrXX:rvnZOTAC:rnZBOX-ID18:rvrXX:cvnNA:ct10:cvrNA:
  dmi.product.name: ZBOX-ID18
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1609242/+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 1548850] Re: Suspend-Resume freezes the computer completely

[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/1548850

Title:
  Suspend-Resume freezes the computer completely

Status in linux package in Ubuntu:
  Expired

Bug description:
  I’m using HP 250 G3 notebook. When closing the screen and reopening it, the 
system should suspend and resume. However, when I reopen the computer, the 
system is completely frozen. I can’t move the mouse, keyboard strokes don’t get 
recongnized, not even Ctrl+Alt+F1 to get to the rescue terminal where I could 
at least reboot the computer. Instead, the only solution I found was to press 
the power button for several seconds.
  Being able to suspend the computer is very important for me. What can I do 
about this?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-headers-4.2.0-30 4.2.0-30.35
  ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  babbl  1584 F pulseaudio
   /dev/snd/controlC1:  babbl  1584 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Feb 23 15:28:30 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=34ce0104-ddbf-4b6e-8f5b-2012550d55ef
  InstallationDate: Installed on 2015-10-17 (129 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  Lsusb:
   Bus 003 Device 003: ID 064e:9320 Suyin Corp. 
   Bus 003 Device 002: ID 8087:8000 Intel Corp. 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP 250 G3 Notebook PC
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-30-generic.efi.signed 
root=UUID=ce32a0c7-c1c0-4a26-90c2-6466918c1e3d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.149.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2016-02-23 (0 days ago)
  dmi.bios.date: 10/23/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.31
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2212
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.44
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.31:bd10/23/2014:svnHewlett-Packard:pnHP250G3NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2212:rvr86.44:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 250 G3 Notebook PC
  dmi.product.version: 0991100600087
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1548850/+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 1577957] Re: Intel 7265D wifi firmware crashes on a Lenovo x1 carbon (3rd generation)

[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/1577957

Title:
  Intel 7265D wifi firmware crashes on a Lenovo x1 carbon (3rd
  generation)

Status in linux package in Ubuntu:
  Expired

Bug description:
  The stock firmware for this device /lib/firmware/iwlwifi-
  7265D-16.ucode is crashing.

  Downloading the latest firmware (/lib/firmware/iwlwifi-7265D-21.ucode)
  isn't supported by the existing iwlwifi driver, and so the driver
  likely needs to be upgraded (or downgraded as well
  (https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/backport-
  iwlwifi.git/?h=release/LinuxCore18).

  I can also confirm that wifi *did* work successfully on 15.10 before
  upgrading to 16.04, although the kernel module required frequent
  restarts due to this bug:
  https://bugs.launchpad.net/ubuntu/xenial/+source/linux/+bug/1570595

  
  A detailed message about the firmware crash is located in the attachment from 
dmesg output.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  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/pcmC1D0p:   mrhines2419 F...m pulseaudio
   /dev/snd/controlC1:  mrhines2419 F pulseaudio
   /dev/snd/controlC0:  mrhines2419 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue May  3 16:50:50 2016
  HibernationDevice: RESUME=UUID=1ac1f16c-161d-45c7-83b9-cecbbfdeee42
  InstallationDate: Installed on 2016-01-05 (119 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20BSCTO1WW
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (12 days ago)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577957/+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 1591631] Re: Atheros AR928X Wireless Network Adapter has poor range

[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/1591631

Title:
  Atheros AR928X Wireless Network Adapter has poor range

Status in linux package in Ubuntu:
  Expired

Bug description:
  My Atheros AR928X Wireless Network Adapter will only connect to my
  WiFi base station if it's very close to it.  When connected, if I move
  about 5 metres away, the connection drops.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-38-generic 4.2.0-38.45~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-38.45~14.04.1-generic 4.2.8-ckt10
  Uname: Linux 4.2.0-38-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jun 12 08:26:48 2016
  InstallationDate: Installed on 2016-06-01 (10 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jim2165 F pulseaudio
   /dev/snd/controlC1:  jim2165 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2016-06-01 (11 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Acer Aspire 5542
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-38-generic 
root=UUID=7d2bd334-80d7-4869-8ca2-849d7a1dcd3c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-38.45~14.04.1-generic 4.2.8-ckt10
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-38-generic N/A
   linux-backports-modules-4.2.0-38-generic  N/A
   linux-firmware1.127.22
  Tags:  trusty
  Uname: Linux 4.2.0-38-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/11/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.03
  dmi.board.name: JV50TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.03:bd08/11/2009:svnAcer:pnAspire5542:pvr0100:rvnAcer:rnJV50TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 5542
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1591631/+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 1615507] Re: package linux-image-extra-3.13.0-93-generic 3.13.0-93.140 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Conrad]

Hi Joseph,


Yes I can load previous kernel. I can't run any software update utility
either. i have had problems before with the boot partition being limited on
space but the error presented very differently.


Regards

Conrad

On 23/08/2016 2:41 am, "Joseph Salisbury" 
wrote:

> Are you able to boot the prior kernel version if you select it from the
> GRUB menu?
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => High
>
> ** Tags added: kernel-da-key
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1615507
>
> Title:
>   package linux-image-extra-3.13.0-93-generic 3.13.0-93.140 failed to
>   install/upgrade: subprocess installed post-installation script
>   returned error exit status 1
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   cant boot up latest kernal
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 14.04
>   Package: linux-image-extra-3.13.0-93-generic 3.13.0-93.140
>   ProcVersionSignature: Ubuntu 3.19.0-65.73~14.04.1-lowlatency
> 3.19.8-ckt22
>   Uname: Linux 3.19.0-65-lowlatency x86_64
>   NonfreeKernelModules: fglrx
>   ApportVersion: 2.14.1-0ubuntu3.21
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  conrad 2582 F pulseaudio
>/dev/snd/controlC0:  conrad 2582 F pulseaudio
>   Date: Fri Aug 19 20:30:14 2016
>   DpkgTerminalLog:
>Log started: 2016-08-05  23:30:50
>Log ended: 2016-08-05  23:31:28
>
>Log started: 2016-08-19  20:23:55
>   ErrorMessage: subprocess installed post-installation script returned
> error exit status 1
>   InstallationDate: Installed on 2015-12-24 (241 days ago)
>   InstallationMedia: Ubuntu-Studio 14.04.3 LTS "Trusty Tahr" - Beta amd64
> (20150805)
>   MachineType: Hewlett-Packard HP 15 Notebook PC
>   ProcFB: 0 radeondrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-65-lowlatency
> root=/dev/mapper/ubuntu--studio--vg-root ro nomdmonddf nomdmonisw
>   PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
> PulseAudio daemon running, or not running as session daemon.
>   RelatedPackageVersions: grub-pc N/A
>   SourcePackage: linux
>   Title: package linux-image-extra-3.13.0-93-generic 3.13.0-93.140 failed
> to install/upgrade: subprocess installed post-installation script returned
> error exit status 1
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 05/30/2014
>   dmi.bios.vendor: Insyde
>   dmi.bios.version: F.16
>   dmi.board.asset.tag: Base Board Asset Tag
>   dmi.board.name: 22CD
>   dmi.board.vendor: Hewlett-Packard
>   dmi.board.version: 93.15
>   dmi.chassis.asset.tag: Chassis Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Hewlett-Packard
>   dmi.chassis.version: Chassis Version
>   dmi.modalias: dmi:bvnInsyde:bvrF.16:bd05/30/
> 2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097510405F00
> 001620180:rvnHewlett-Packard:rn22CD:rvr93.15:cvnHewlett-Packard:ct10:
> cvrChassisVersion:
>   dmi.product.name: HP 15 Notebook PC
>   dmi.product.version: 097510405F1620180
>   dmi.sys.vendor: Hewlett-Packard
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1615507
> /+subscriptions
>

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

Title:
  package linux-image-extra-3.13.0-93-generic 3.13.0-93.140 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  cant boot up latest kernal

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.13.0-93-generic 3.13.0-93.140
  ProcVersionSignature: Ubuntu 3.19.0-65.73~14.04.1-lowlatency 3.19.8-ckt22
  Uname: Linux 3.19.0-65-lowlatency x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  conrad 2582 F pulseaudio
   /dev/snd/controlC0:  conrad 2582 F pulseaudio
  Date: Fri Aug 19 20:30:14 2016
  DpkgTerminalLog:
   Log started: 2016-08-05  23:30:50
   Log ended: 2016-08-05  23:31:28
   
   Log started: 2016-08-19  20:23:55
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-12-24 (241 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-65-lowlatency 
root=/dev/mapper/ubuntu--studio--vg-root ro nomdmonddf nomdmonisw
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running 

[Kernel-packages] [Bug 1615681] Re: BUG: unable to handle kernel paging request at ffff820504022108

[Neil]

Thanks for your suggestion.
This issue is not happened on any update/upgrade, and only happened once.
Because we cannot get any operation path to reproduce it, so test with the 
latest upstream kernel cannot help make it clear.
Anyway, I will try to share some more information on current kdump.

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

Title:
  BUG: unable to handle kernel paging request at 820504022108

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We get this kernel panic while running trusty with 3.19.0-26-generic. 
  It seems there is a bug in nf_nat module, I got kdump, if needed, I will 
upload.

  [702076.560806] BUG: unable to handle kernel paging request at 
820504022108
  [702076.564428] IP: [] nf_nat_setup_info+0x236/0x360 
[nf_nat]
  [702076.567971] PGD 0 
  [702076.571349] Oops: 0002 [#1] SMP 
  [702076.574656] Modules linked in: xt_nat iptable_nat nf_nat_ipv4 sch_sfq 
sch_htb xt_comment xt_iprange xt_physdev act_police cls_u32 sch_ingress 
ebt_dnat ebt_ip ebtable_nat ebt_arp veth xt_conntrack nbd nf_conntrack_netlink 
xt_TCPMSS xt_CT xt_set ip_set_hash_net ip_set nfnetlink iptable_raw 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter netconsole 
configfs xt_CHECKSUM xt_tcpudp iptable_mangle ip_tables x_tables bonding 
intel_rapl(E) iosf_mbi x86_pkg_temp_thermal(E) nf_nat intel_powerclamp(E) 
nf_conntrack_pptp nf_conntrack_proto_gre coretemp(E) br_netfilter 
crct10dif_pclmul ipmi_ssif(E) crc32_pclmul ghash_clmulni_intel aesni_intel 
bridge stp aes_x86_64 llc lrw ipmi_devintf(E) nf_conntrack_ipv4 gf128mul 
nf_defrag_ipv4 glue_helper ablk_helper cryptd mxm_wmi(E) dcdbas(E) sb_edac(E) 
mei_me(E)
  [702076.613908]  nf_conntrack mei(E) lpc_ich(E) edac_core(E) drbd(OE) 
ipmi_si(E) ipmi_msghandler 8250_fintek(E) shpchp(E) vhost_net vhost 
acpi_power_meter(E) macvtap wmi(E) macvlan mac_hid(E) kvm_intel kvm lp xfs 
parport libcrc32c ahci megaraid_sas(E) libahci tg3(E) ixgbe(OE) dca(E) vxlan 
ip6_udp_tunnel udp_tunnel ptp pps_core
  [702076.638776] CPU: 19 PID: 0 Comm: swapper/19 Tainted: G   OE  
3.19.0-26-generic #28~14.04.1
  [702076.649826] Hardware name: Dell Inc. PowerEdge R730/0WCJNT, BIOS 2.1.5 
04/11/2016
  [702076.66] task: 883011c49d70 ti: 881812224000 task.ti: 
881812224000
  [702076.672654] RIP: 0010:[]  [] 
nf_nat_setup_info+0x236/0x360 [nf_nat]
  [702076.684662] RSP: 0018:88301eb235b8  EFLAGS: 00010286
  [702076.690647] RAX: 882fbcd21700 RBX: 882f17b1bd40 RCX: 
820504022100
  [702076.702499] RDX: 88180fb7f038 RSI: 3637ced5 RDI: 
c04a04a0
  [702076.714455] RBP: 88301eb23668 R08:  R09: 
88301eb235b8
  [702076.726823] R10: 88301eb23560 R11: 88300eeb8000 R12: 
0006fe07
  [702076.739167] R13:  R14: 81cda040 R15: 
88301eb23678
  [702076.751481] FS:  () GS:88301eb2() 
knlGS:
  [702076.763823] CS:  0010 DS:  ES:  CR0: 80050033
  [702076.770007] CR2: 820504022108 CR3: 01c16000 CR4: 
001427e0
  [702076.782162] Stack:
  [702076.788035]  2755e673  a402c68b0002259b 

  [702076.799835]  00065000 2755e673  
a402c68b0002259b
  [702076.811642]   00065000 88300db05800 
8830001b0e70
  [702076.823573] Call Trace:
  [702076.829377]   
  [702076.829447] 
  [702076.835069]  [] __nf_nat_alloc_null_binding+0x52/0x80 
[nf_nat]
  [702076.846350]  [] nf_nat_alloc_null_binding+0x21/0x30 
[nf_nat]
  [702076.857721]  [] nf_nat_ipv4_fn+0x1dd/0x230 [nf_nat_ipv4]
  [702076.863548]  [] ? iptable_nat_ipv4_fn+0x20/0x20 
[iptable_nat]
  [702076.874933]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.886328]  [] nf_nat_ipv4_out+0x48/0xf0 [nf_nat_ipv4]
  [702076.892120]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.903384]  [] iptable_nat_ipv4_out+0x15/0x20 
[iptable_nat]
  [702076.914648]  [] nf_iterate+0x9a/0xb0
  [702076.920275]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.931324]  [] nf_hook_slow+0x74/0x130
  [702076.936913]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.947932]  [] br_nf_post_routing+0x283/0x370 
[br_netfilter]
  [702076.959286]  [] ? deliver_clone+0x60/0x60 [bridge]
  [702076.965049]  [] ? deliver_clone+0x60/0x60 [bridge]
  [702076.970612]  [] nf_iterate+0x9a/0xb0
  [702076.976050]  [] ? deliver_clone+0x60/0x60 [bridge]
  [702076.981437]  [] nf_hook_slow+0x74/0x130
  [702076.986715]  [] ? deliver_clone+0x60/0x60 [bridge]
  [702076.992071]  [] ? br_flood+0x160/0x160 [bridge]
  [702076.997487]  [] br_forward_finish+0x52/0x60 [bridge]
  [702077.002855]  [] br_nf_forward_finish+0xcb/0x1d0 
[br_netfilter]
  [702077.013278]  [] br_nf_forward_ip+0x22c/0x400 

[Kernel-packages] [Bug 1615593] Missing required logs.

[Brad Figg]

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

apport-collect 1615593

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

Title:
  Can not start unprivileged container on host with Xen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With a minimum server install of including (zfs, xen-hypervisor-amd64,
  nfs-common, and lxd).

  When I create a privileged container - it works fine.
  When I create an unprivileged container - it won't start with

  # lxc info --show-log test | grep ERROR
  lxc 20160822115926.073 ERRORlxc_utils - 
utils.c:safe_mount:1692 - Operation not permitted - Failed to mount proc onto 
/usr/lib/x86_64-linux-gnu/lxc/proc
  lxc 20160822115926.073 ERRORlxc_conf - 
conf.c:lxc_mount_auto_mounts:743 - Operation not permitted - error mounting 
proc on /usr/lib/x86_64-linux-gnu/lxc/proc flags 14
  lxc 20160822115926.073 ERRORlxc_conf - conf.c:lxc_setup:3721 
- failed to setup the automatic mounts for 'test'
  lxc 20160822115926.073 ERRORlxc_start - start.c:do_start:833 
- failed to setup the container
  lxc 20160822115926.073 ERRORlxc_sync - sync.c:__sync_wait:57 
- An error occurred in another process (expected sequence number 3)
  lxc 20160822115926.073 ERRORlxc_start - 
start.c:__lxc_start:1353 - failed to spawn 'test'

  # uname -a
  Linux xen 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux

  # lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  Tool versions
  # apt-cache policy zfsutils-linux
  zfsutils-linux:
Installed: 0.6.5.6-0ubuntu12
Candidate: 0.6.5.6-0ubuntu12
Version table:
   *** 0.6.5.6-0ubuntu12 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.6.5.6-0ubuntu8 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  # apt-cache policy xen-hypervisor-4.6-amd64
  xen-hypervisor-4.6-amd64:
Installed: 4.6.0-1ubuntu4.1
Candidate: 4.6.0-1ubuntu4.1
Version table:
   *** 4.6.0-1ubuntu4.1 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   4.6.0-1ubuntu4 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  # apt-cache policy nfs-common
  nfs-common:
Installed: 1:1.2.8-9ubuntu12
Candidate: 1:1.2.8-9ubuntu12
Version table:
   *** 1:1.2.8-9ubuntu12 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  # apt-cache policy lxd
  lxd:
Installed: 2.0.3-0ubuntu1~ubuntu16.04.2
Candidate: 2.0.3-0ubuntu1~ubuntu16.04.2
Version table:
   *** 2.0.3-0ubuntu1~ubuntu16.04.2 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.0.2-0ubuntu1~16.04.1 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   2.0.0-0ubuntu4 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  
  I've another system, which is very similar but without Xen installed, which 
doesn't have the same issue with creating unprivileged containers. It would 
seem that it is probably some clash between the two (also suggested in 
http://unix.stackexchange.com/questions/296998/create-lxd-containers-on-machine-with-no-internet-connection)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1615593/+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 1615593] Re: Can not start unprivileged container on host with Xen

[Stéphane Graber]

This is a kernel bug which sforshee has been working on. It should be
included in the next round of kernel updates.

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  Can not start unprivileged container on host with Xen

Status in linux package in Ubuntu:
  New

Bug description:
  With a minimum server install of including (zfs, xen-hypervisor-amd64,
  nfs-common, and lxd).

  When I create a privileged container - it works fine.
  When I create an unprivileged container - it won't start with

  # lxc info --show-log test | grep ERROR
  lxc 20160822115926.073 ERRORlxc_utils - 
utils.c:safe_mount:1692 - Operation not permitted - Failed to mount proc onto 
/usr/lib/x86_64-linux-gnu/lxc/proc
  lxc 20160822115926.073 ERRORlxc_conf - 
conf.c:lxc_mount_auto_mounts:743 - Operation not permitted - error mounting 
proc on /usr/lib/x86_64-linux-gnu/lxc/proc flags 14
  lxc 20160822115926.073 ERRORlxc_conf - conf.c:lxc_setup:3721 
- failed to setup the automatic mounts for 'test'
  lxc 20160822115926.073 ERRORlxc_start - start.c:do_start:833 
- failed to setup the container
  lxc 20160822115926.073 ERRORlxc_sync - sync.c:__sync_wait:57 
- An error occurred in another process (expected sequence number 3)
  lxc 20160822115926.073 ERRORlxc_start - 
start.c:__lxc_start:1353 - failed to spawn 'test'

  # uname -a
  Linux xen 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux

  # lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  Tool versions
  # apt-cache policy zfsutils-linux
  zfsutils-linux:
Installed: 0.6.5.6-0ubuntu12
Candidate: 0.6.5.6-0ubuntu12
Version table:
   *** 0.6.5.6-0ubuntu12 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.6.5.6-0ubuntu8 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  # apt-cache policy xen-hypervisor-4.6-amd64
  xen-hypervisor-4.6-amd64:
Installed: 4.6.0-1ubuntu4.1
Candidate: 4.6.0-1ubuntu4.1
Version table:
   *** 4.6.0-1ubuntu4.1 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   4.6.0-1ubuntu4 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  # apt-cache policy nfs-common
  nfs-common:
Installed: 1:1.2.8-9ubuntu12
Candidate: 1:1.2.8-9ubuntu12
Version table:
   *** 1:1.2.8-9ubuntu12 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  # apt-cache policy lxd
  lxd:
Installed: 2.0.3-0ubuntu1~ubuntu16.04.2
Candidate: 2.0.3-0ubuntu1~ubuntu16.04.2
Version table:
   *** 2.0.3-0ubuntu1~ubuntu16.04.2 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.0.2-0ubuntu1~16.04.1 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   2.0.0-0ubuntu4 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  
  I've another system, which is very similar but without Xen installed, which 
doesn't have the same issue with creating unprivileged containers. It would 
seem that it is probably some clash between the two (also suggested in 
http://unix.stackexchange.com/questions/296998/create-lxd-containers-on-machine-with-no-internet-connection)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1615593/+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 1615593] [NEW] Can not start unprivileged container on host with Xen

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

With a minimum server install of including (zfs, xen-hypervisor-amd64,
nfs-common, and lxd).

When I create a privileged container - it works fine.
When I create an unprivileged container - it won't start with

# lxc info --show-log test | grep ERROR
lxc 20160822115926.073 ERRORlxc_utils - utils.c:safe_mount:1692 
- Operation not permitted - Failed to mount proc onto 
/usr/lib/x86_64-linux-gnu/lxc/proc
lxc 20160822115926.073 ERRORlxc_conf - 
conf.c:lxc_mount_auto_mounts:743 - Operation not permitted - error mounting 
proc on /usr/lib/x86_64-linux-gnu/lxc/proc flags 14
lxc 20160822115926.073 ERRORlxc_conf - conf.c:lxc_setup:3721 - 
failed to setup the automatic mounts for 'test'
lxc 20160822115926.073 ERRORlxc_start - start.c:do_start:833 - 
failed to setup the container
lxc 20160822115926.073 ERRORlxc_sync - sync.c:__sync_wait:57 - 
An error occurred in another process (expected sequence number 3)
lxc 20160822115926.073 ERRORlxc_start - 
start.c:__lxc_start:1353 - failed to spawn 'test'

# uname -a
Linux xen 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux

# lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04

Tool versions
# apt-cache policy zfsutils-linux
zfsutils-linux:
  Installed: 0.6.5.6-0ubuntu12
  Candidate: 0.6.5.6-0ubuntu12
  Version table:
 *** 0.6.5.6-0ubuntu12 500
500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 0.6.5.6-0ubuntu8 500
500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

# apt-cache policy xen-hypervisor-4.6-amd64
xen-hypervisor-4.6-amd64:
  Installed: 4.6.0-1ubuntu4.1
  Candidate: 4.6.0-1ubuntu4.1
  Version table:
 *** 4.6.0-1ubuntu4.1 500
500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
100 /var/lib/dpkg/status
 4.6.0-1ubuntu4 500
500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

# apt-cache policy nfs-common
nfs-common:
  Installed: 1:1.2.8-9ubuntu12
  Candidate: 1:1.2.8-9ubuntu12
  Version table:
 *** 1:1.2.8-9ubuntu12 500
500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

# apt-cache policy lxd
lxd:
  Installed: 2.0.3-0ubuntu1~ubuntu16.04.2
  Candidate: 2.0.3-0ubuntu1~ubuntu16.04.2
  Version table:
 *** 2.0.3-0ubuntu1~ubuntu16.04.2 500
500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 2.0.2-0ubuntu1~16.04.1 500
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
 2.0.0-0ubuntu4 500
500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages


I've another system, which is very similar but without Xen installed, which 
doesn't have the same issue with creating unprivileged containers. It would 
seem that it is probably some clash between the two (also suggested in 
http://unix.stackexchange.com/questions/296998/create-lxd-containers-on-machine-with-no-internet-connection)

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Seth Forshee (sforshee)
 Status: New

-- 
Can not start unprivileged container on host with Xen
https://bugs.launchpad.net/bugs/1615593
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1251037] Re: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu1: bcmwl kernel module failed to build [Makefile: No such file or directory]

[buscoverdad]

I confirm this bug happens in Xubuntu 14.04. I noticed the problem after
upgrading my kernel to "4.4.0-34-generic".

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

Title:
  bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu1: bcmwl kernel module
  failed to build [Makefile: No such file or directory]

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  /

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu1
  Uname: Linux 3.12.0-031200-generic i686
  ApportVersion: 2.12.6-0ubuntu1
  Architecture: i386
  DKMSKernelVersion: 3.12.0-031200-generic
  Date: Wed Nov 13 23:02:12 2013
  InstallationDate: Installed on 2013-11-09 (4 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131108)
  MarkForUpload: True
  PackageVersion: 6.30.223.141+bdcom-0ubuntu1
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu1: bcmwl kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1251037/+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 1405742] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module failed to build

[Launchpad Bug Tracker]

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

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module
  failed to build

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  Testing Ubuntu v3.18.1 from Canonical kernel teams Ubuntu.com site.
  bcmwl failed to build.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 3.18.1-031801-generic
  Date: Fri Dec 26 00:11:59 2014
  InstallationDate: Installed on 2014-12-26 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141225)
  PackageVersion: 6.30.223.248+bdcom-0ubuntu2
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1405742/+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 1323426] Re: HP Z8000 bluetooth mouse

[Ismael]

I have found a solution here:

http://askubuntu.com/questions/636712/logitech-mx-anywhere-2-mouse-
pairs-but-doesnt-do-anything/660918#660918

It's is fine for me in Ubuntu 16.04

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

Title:
  HP Z8000 bluetooth mouse

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  This mouse is a HID over GAT recent HP low power mouse.

  It  is recognized as ALL types bluetooth peripherals not as a mouse!

  The mouse at the end of the installation process (automatic pin
  selection) results as PAIRED  but the connection option is not
  available in the bluetooth setting dialog.

  UBUNTU is last 14.04 full updated at filing bug time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1323426/+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 1615835] Re: CVE-2016-5696

[Steve Beattie]

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

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

** Changed in: linux-lts-trusty (Ubuntu)
   Status: New => Fix Committed

** Description changed:

  Description
  net/ipv4/tcp_input.c in the Linux kernel before 4.7 does not properly
  determine the rate of challenge ACK segments, which makes it easier for
  man-in-the-middle attackers to hijack TCP sessions via a blind in-window
  attack.
  
  Ubuntu-Description
  Yue Cao et al discovered a flaw in the TCP implementation's handling
  of challenge acks in the Linux kernel. A remote attacker could use
  this to cause a denial of service (reset connection) or inject
  content into an TCP stream.
  
  References
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5696
  https://www.mail-archive.com/netdev@vger.kernel.org/msg118677.html
  
http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=75ff39ccc1bd5d3c455b6822ab09e533c551f758
  https://lwn.net/Articles/696868/
+ https://people.canonical.com/~ubuntu-security/cve/2016/CVE-2016-5696.html

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

Title:
  CVE-2016-5696

Status in linux-lts-trusty package in Ubuntu:
  Fix Committed

Bug description:
  Description
  net/ipv4/tcp_input.c in the Linux kernel before 4.7 does not properly
  determine the rate of challenge ACK segments, which makes it easier for
  man-in-the-middle attackers to hijack TCP sessions via a blind in-window
  attack.

  Ubuntu-Description
  Yue Cao et al discovered a flaw in the TCP implementation's handling
  of challenge acks in the Linux kernel. A remote attacker could use
  this to cause a denial of service (reset connection) or inject
  content into an TCP stream.

  References
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5696
  https://www.mail-archive.com/netdev@vger.kernel.org/msg118677.html
  
http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=75ff39ccc1bd5d3c455b6822ab09e533c551f758
  https://lwn.net/Articles/696868/
  https://people.canonical.com/~ubuntu-security/cve/2016/CVE-2016-5696.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1615835/+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 1454717] Re: Weak wifi signal and frequency disconnects

[Theresa]

is this is bug fixed/addressed in 16.04 LTS?

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

Title:
  Weak wifi signal and frequency disconnects

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  This bug duplicate
  https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1379524 but it
  marked expired.

  Symptoms same - on my notebook HP Pavilion p170nr with BCM43142 chip
  has very low and unstable wi-fi signal. I even can't work from far
  room because of permanent disconnects and very low speed. Windows 8 in
  same place work fine also all phones.

  Also connection frequency disappear. Disconnects don't depend on
  signal level. Connection may break even near router and hi (relative)
  signal. I changed router but this didn't help.

  I don't know if it help, but I get this message in dmesg log

  [29218.308151] [ cut here ]
  [29218.308177] WARNING: CPU: 2 PID: 524 at 
/build/buildd/linux-3.19.0/net/wireless/sme.c:800 cfg80211_roamed+0x91/0xa0 
[cfg80211]()
  [29218.308179] Modules linked in: rfcomm bnep binfmt_misc bbswitch(OE) 
nls_iso8859_1 intel_rapl iosf_mbi hp_wmi sparse_keymap x86_pkg_temp_thermal 
intel_powerclamp snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic 
wl(POE) snd_hda_intel snd_hda_controller coretemp kvm_intel snd_hda_codec 
snd_hwdep btusb kvm snd_pcm uvcvideo crct10dif_pclmul snd_seq_midi 
snd_seq_midi_event bluetooth snd_rawmidi crc32_pclmul videobuf2_vmalloc snd_seq 
videobuf2_memops videobuf2_core ghash_clmulni_intel v4l2_common aesni_intel 
videodev media aes_x86_64 lrw gf128mul glue_helper snd_seq_device ablk_helper 
snd_timer dm_multipath cryptd scsi_dh i915 snd cfg80211 soundcore hp_accel 
joydev serio_raw lis3lv02d input_polldev shpchp drm_kms_helper hp_wireless 
mei_me wmi drm video i2c_algo_bit mei intel_smartconnect lpc_ich
  [29218.308208]  mac_hid ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt 
nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 
nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns 
nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack 
iptable_filter parport_pc ppdev ip_tables x_tables lp parport autofs4 
hid_generic usbhid hid psmouse ahci r8169 libahci mii
  [29218.308231] CPU: 2 PID: 524 Comm: wl_event_handle Tainted: PW  OE  
3.19.0-16-generic #16-Ubuntu
  [29218.308232] Hardware name: Hewlett-Packard HP Pavilion 15 Notebook PC 
/2281, BIOS F.12 08/18/2014
  [29218.308233]  c0478a78 8801d55c3da8 817c2235 
0007
  [29218.308236]   8801d55c3de8 8107595a 
8801d23c9078
  [29218.308238]  8801d26bb000 8801d4a52b40 009f 
8801c5b74b40
  [29218.308240] Call Trace:
  [29218.308246]  [] dump_stack+0x45/0x57
  [29218.308250]  [] warn_slowpath_common+0x8a/0xc0
  [29218.308252]  [] warn_slowpath_null+0x1a/0x20
  [29218.308260]  [] cfg80211_roamed+0x91/0xa0 [cfg80211]
  [29218.308290]  [] wl_notify_roaming_status+0xcb/0x150 [wl]
  [29218.308312]  [] wl_event_handler+0x6a/0x230 [wl]
  [29218.308333]  [] ? wl_free_wdev.isra.23+0x80/0x80 [wl]
  [29218.308336]  [] kthread+0xc9/0xe0
  [29218.308339]  [] ? kthread_create_on_node+0x1c0/0x1c0
  [29218.308342]  [] ret_from_fork+0x58/0x90
  [29218.308344]  [] ? kthread_create_on_node+0x1c0/0x1c0
  [29218.308346] ---[ end trace 0970ead2c419c952 ]---
  [29222.548357] cfg80211: Calling CRDA to update world regulatory domain
  [29222.575949] cfg80211: World regulatory domain updated:
  [29222.575952] cfg80211:  DFS Master region: unset
  [29222.575953] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp), (dfs_cac_time)
  [29222.575956] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2000 mBm), (N/A)
  [29222.575958] cfg80211:   (2457000 KHz - 2482000 KHz @ 4 KHz), (300 mBi, 
2000 mBm), (N/A)
  [29222.575959] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 
2000 mBm), (N/A)
  [29222.575961] cfg80211:   (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2000 mBm), (N/A)
  [29222.575962] cfg80211:   (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
2000 mBm), (N/A)
  [29228.744616] cfg80211: Calling CRDA to update world regulatory domain
  [29228.753685] cfg80211: World regulatory domain updated:
  [29228.753696] cfg80211:  DFS Master region: unset
  [29228.753701] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp), (dfs_cac_time)
  [29228.753711] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2000 mBm), (N/A)
  [29228.753718] cfg80211:   (2457000 KHz - 2482000 KHz @ 4 KHz), (300 mBi, 
2000 mBm), (N/A)
  [29228.753725] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 
2000 mBm), (N/A)
  [29228.753731] 

[Kernel-packages] [Bug 1615835] [NEW] CVE-2016-5696

[Leonardo Borda]

*** This bug is a security vulnerability ***

Public security bug reported:

Description
net/ipv4/tcp_input.c in the Linux kernel before 4.7 does not properly
determine the rate of challenge ACK segments, which makes it easier for
man-in-the-middle attackers to hijack TCP sessions via a blind in-window
attack.

Ubuntu-Description
Yue Cao et al discovered a flaw in the TCP implementation's handling
of challenge acks in the Linux kernel. A remote attacker could use
this to cause a denial of service (reset connection) or inject
content into an TCP stream.

References
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5696
https://www.mail-archive.com/netdev@vger.kernel.org/msg118677.html
http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=75ff39ccc1bd5d3c455b6822ab09e533c551f758
https://lwn.net/Articles/696868/

** Affects: linux-lts-trusty (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  CVE-2016-5696

Status in linux-lts-trusty package in Ubuntu:
  New

Bug description:
  Description
  net/ipv4/tcp_input.c in the Linux kernel before 4.7 does not properly
  determine the rate of challenge ACK segments, which makes it easier for
  man-in-the-middle attackers to hijack TCP sessions via a blind in-window
  attack.

  Ubuntu-Description
  Yue Cao et al discovered a flaw in the TCP implementation's handling
  of challenge acks in the Linux kernel. A remote attacker could use
  this to cause a denial of service (reset connection) or inject
  content into an TCP stream.

  References
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5696
  https://www.mail-archive.com/netdev@vger.kernel.org/msg118677.html
  
http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=75ff39ccc1bd5d3c455b6822ab09e533c551f758
  https://lwn.net/Articles/696868/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1615835/+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 1581594] Re: constantly shows wrong temperature (99°C )

[Phillip Susi]

** Bug watch added: freedesktop.org Bugzilla #97446
   https://bugs.freedesktop.org/show_bug.cgi?id=97446

** Also affects: libatasmart via
   https://bugs.freedesktop.org/show_bug.cgi?id=97446
   Importance: Unknown
   Status: Unknown

** Changed in: libatasmart (Ubuntu)
   Status: Incomplete => In Progress

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

Title:
  constantly shows wrong temperature (99°C )

Status in libatasmart:
  Unknown
Status in libatasmart package in Ubuntu:
  In Progress

Bug description:
  Hello, here's my system info

  ~$ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  ~$ apt-cache policy udisks2
  udisks2:
Installed: 2.1.7-1ubuntu1
Candidate: 2.1.7-1ubuntu1
Version table:
   *** 2.1.7-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Here's the problem: udisks2 constantly shows that my ssd temperature is 99°C 
(210°F), but in reality it's 30°C

  
  ~$ sudo smartctl -A /dev/sda
  smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-22-generic] (local build)
  Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

  === START OF READ SMART DATA SECTION ===
  SMART Attributes Data Structure revision number: 16
  Vendor Specific SMART Attributes with Thresholds:
  ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE  UPDATED  
WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b   100   100   050Pre-fail  Always  
 -   0
9 Power_On_Hours  0x0012   100   100   000Old_age   Always  
 -   24
   12 Power_Cycle_Count   0x0012   100   100   000Old_age   Always  
 -   51
  168 Unknown_Attribute   0x0012   100   100   000Old_age   Always  
 -   0
  170 Unknown_Attribute   0x0003   100   100   010Pre-fail  Always  
 -   231
  173 Unknown_Attribute   0x0012   100   100   000Old_age   Always  
 -   65539
  192 Power-Off_Retract_Count 0x0012   100   100   000Old_age   Always  
 -   23
  194 Temperature_Celsius 0x0023   070   070   030Pre-fail  Always  
 -   30 (Min/Max 30/30)
  218 Unknown_Attribute   0x000b   100   100   050Pre-fail  Always  
 -   0
  231 Temperature_Celsius 0x0013   100   100   000Pre-fail  Always  
 -   99
  241 Total_LBAs_Written  0x0012   100   100   000Old_age   Always  
 -   337


  in the GUI app ("Disks") it shows the wrong temperature too. hddtemp
  works well though:

  ~$ sudo hddtemp /dev/sda
  /dev/sda: PNY EU SSD CS1311 240GB: 30°C

To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1581594/+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 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

[Joseph Salisbury]

I built a v4.8-rc2 test kernel with the first patch Alex mentions in
comment #308.  Can this kernel be tested to see if it still exhibits the
bug?

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1470250/081816-Patch/

Alex, do you think we need the second patch for testing of this
particular 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/1470250

Title:
  [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
  Backups

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Customers have reported running various versions of Ubuntu 14.04.2 LTS
  on Generation 2 Hyper-V Hosts.On a random Basis, the file system
  will be mounted Read-Only due to a "disk error" (which really isn't
  the case here).As a result, they must reboot the Ubuntu guest to
  get the file system to mount RW again.

  The Error seen are the following:
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed. The Linux SCSI layer does not automatically adjust these 
parameters.
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc 
vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc 
vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed.  The Linux SCSI layer does not automatically adjust these 
parameters.

  This relates to the VSS "Windows Server Backup" process that kicks off at 
midnight on the host and finishes an hour and half later.   
  Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct 
kernel version we have.   We're currently running kernel version 
3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- 
We see the same errors on both.
  As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 
hyper-v system because of this.   We can stop the backup process and all is 
good, but we need nightly backups to image all of our VM's.   All the windows 
guests have no issues of course.   We also have some CentOS based guests 
running without issues from what we've seen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1470250/+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 1608236] Re: Regression: S-video output does not work

[Jarno Suni]

4.4.0-22 does not have the 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/1608236

Title:
  Regression: S-video output does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Regression. S-video output can not be used. It works by 4.4.0-22-generic.
  xrandr tells on 4.4.0-31-generic:

  TV1 unknown connection (normal left inverted right x axis y axis)
 848x480   50.00 +
 640x480   50.00 +
 1024x768  50.00  
 800x600   50.00

  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
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarnos 1573 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jul 31 17:15:16 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-28 (94 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 89224MG
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/06
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 63ET13WW
  dmi.board.name: CAPELL VALLEY(NAPA) CRB
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 89224MG
  dmi.product.version: 3000 C200
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608236/+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 1581594] Re: constantly shows wrong temperature (99°C )

[Phillip Susi]

Sorry for the late reply Martin... my bugs mailbox has gotten quite
backed up.  I emailed smartmontols-devel about the issue and their
response was:

There likely was some historic HDD which used attribute 231 for
temperature (same for 9 and 220).

And yes, there are devices which report temperature in more than one
attribute.

They went on to say they would probably change smartmontools to prefer
the more common attribute and I thought that libatasmart should follow
suit.


Will create the upstream bug report, though the last one or two I have created 
with patches attached have gone ignored there for years so...

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

Title:
  constantly shows wrong temperature (99°C )

Status in libatasmart package in Ubuntu:
  Incomplete

Bug description:
  Hello, here's my system info

  ~$ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  ~$ apt-cache policy udisks2
  udisks2:
Installed: 2.1.7-1ubuntu1
Candidate: 2.1.7-1ubuntu1
Version table:
   *** 2.1.7-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Here's the problem: udisks2 constantly shows that my ssd temperature is 99°C 
(210°F), but in reality it's 30°C

  
  ~$ sudo smartctl -A /dev/sda
  smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-22-generic] (local build)
  Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

  === START OF READ SMART DATA SECTION ===
  SMART Attributes Data Structure revision number: 16
  Vendor Specific SMART Attributes with Thresholds:
  ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE  UPDATED  
WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b   100   100   050Pre-fail  Always  
 -   0
9 Power_On_Hours  0x0012   100   100   000Old_age   Always  
 -   24
   12 Power_Cycle_Count   0x0012   100   100   000Old_age   Always  
 -   51
  168 Unknown_Attribute   0x0012   100   100   000Old_age   Always  
 -   0
  170 Unknown_Attribute   0x0003   100   100   010Pre-fail  Always  
 -   231
  173 Unknown_Attribute   0x0012   100   100   000Old_age   Always  
 -   65539
  192 Power-Off_Retract_Count 0x0012   100   100   000Old_age   Always  
 -   23
  194 Temperature_Celsius 0x0023   070   070   030Pre-fail  Always  
 -   30 (Min/Max 30/30)
  218 Unknown_Attribute   0x000b   100   100   050Pre-fail  Always  
 -   0
  231 Temperature_Celsius 0x0013   100   100   000Pre-fail  Always  
 -   99
  241 Total_LBAs_Written  0x0012   100   100   000Old_age   Always  
 -   337


  in the GUI app ("Disks") it shows the wrong temperature too. hddtemp
  works well though:

  ~$ sudo hddtemp /dev/sda
  /dev/sda: PNY EU SSD CS1311 240GB: 30°C

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/1581594/+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 1604314] Re: [Xenial] iommu/amd: Fix unity mapping initialization race

[Tim Gardner]

I've refreshed the kernel at http://people.canonical.com/~rtg/iommu-
lp1604314/. It contains upstream stable releases through v4.4.19 as well
as the IOMMU patches mentioned in the bug description.

git://kernel.ubuntu.com/rtg/ubuntu-xenial.git iommu-lp1604314

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

Title:
  [Xenial] iommu/amd: Fix unity mapping initialization race

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

Bug description:
  == Xenial SRU Justification ==
  HP Gen8 servers were having kernel panics with the 4.2 and 4.4 kernel which 
is apparently resolved with the following commits.  HP would like to see these 
SRU'd for Xenial.

  commit 0caa7616a6aca449dd68b58cb29bd491d296c2d5
  Author: Aaron Campbell 
  Date:   Sat Jul 2 21:23:24 2016 -0300

  iommu/vt-d: Fix infinite loop in free_all_cpu_cached_iovas

  commit 522e5cb76d0663c88f96b6a8301451c8efa37207
  Author: Joerg Roedel 
  Date:   Fri Jul 1 16:42:55 2016 +0200

  iommu/amd: Fix unity mapping initialization race

  == Testing ==
  HP confirms their testing shows these patches resolves the issue on several 
test machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1604314/+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 1611536] Re: Fan on full speed without noapic or nolapic on HP 6715s

[Carl Englund]

I made a mistake, 4.4.0-34 does not boot with normal fan speed without
noapic. Instead, it seems the change/break appears between 4.2.3 and
4.2.4. I will try to bisect there. Here is the updated list:

4.1.0: fan ok, 32-bit FADT
4.1.1: fan ok, 32-bit FADT
4.1.2: fan ok, 32-bit FADT
4.1.3: fan ok, 32-bit FADT
4.1.4: ?, boot freeze
4.1.5: ?, boot freeze
4.1.10: fan ok, 64-bit FADT. Freezes after a bit in Xorg.
4.1.11: fan ok, boot freeze
4.1.12: fan ok, boot freeze
4.1.13: fan ok, boot freeze
4.1.17: fan ok, boot freeze
4.1.23: fan ok, 64-bit FADT
4.1.24: fan ok, boot freeze
4.1.25: fan ok, boot freeze
4.1.26: fan ok, boot freeze
4.1.30: fan ok, X freeze, 64-bit fadt
4.2.0: fan ok, boot freeze
4.2.1: ??, boot freeze
4.2.2: fan ok, boot freeze
4.2.3: fan ok, boot freeze
4.2.4: fan full, boot freeze or dark screen (but working?)
4.2.7: fan full, 64-bit fadt
4.4.0-21: fan full, 32-bit fadt
4.4.0-34: fan full, 32-bit fadt
4.8.0-rc2: fan full, 32-bit fadt

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

Title:
  Fan on full speed without noapic or nolapic on HP 6715s

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Without adding noapic or nolapic to boot parameters the fan will run
  on full speed, the system is sluggish (can almost see windows
  redrawing on screen). On some kernel versions tested, rebooting also
  fails.

  The parameter(s) were not required in Trusty. I also tested some
  Mainline kernels and discovered 3.19.8 and 4.0.9 works without the
  parameters. At least 4.1.29 and onward requires noapic or nolapic for
  this machine to work properly but I have yet to investigate the
  versions between 4.0.9 and 4.1.29.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diskdoc2700 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Aug 10 01:15:07 2016
  HibernationDevice: RESUME=UUID=522810df-638a-412b-9aab-791e2e2bc545
  InstallationDate: Installed on 2016-06-07 (63 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Compaq 6715s (RU655ET#AK8)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=3a37ee65-4c02-4a95-b814-f4538a4a308d ro quiet splash noapic 
acpi_force_32bit_fadt_addr vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68YTT Ver. F.20
  dmi.board.name: 30C2
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.2D
  dmi.chassis.asset.tag: CNU7201T8J
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68YTTVer.F.20:bd12/01/2011:svnHewlett-Packard:pnHPCompaq6715s(RU655ET#AK8):pvrF.20:rvnHewlett-Packard:rn30C2:rvrKBCVersion71.2D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq 6715s (RU655ET#AK8)
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611536/+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 1602724] Re: Ubuntu 16.04 - Full EEH Recovery Support for NVMe devices

[Tim Gardner]

git://kernel.ubuntu.com/rtg/ubuntu-xenial.git eeh-lp1602724
commit fcb182b0c9d79b9dae70f2c9104997a0ec63f080 ('nvme: Suspend all queues 
before deletion')

The 6 patches mentioned in the bug description have already been merged
but not yet packaged in a released version, though they _are_ included
in this test kernel.

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

Title:
  Ubuntu 16.04 - Full EEH Recovery Support for NVMe devices

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

Bug description:
  == Comment: #0 - Heitor Ricardo Alves de Siqueira  - 
2016-07-12 12:54:27 ==
  Current nvme driver in Ubuntu 16.04 kernel does not handle error recovery; we 
are missing some patches from the upstream nvme driver.

  We would like to ask Canonical to cherry pick the following patches for the 
16.04 kernel, if possible:
  * 9396dec916c0 ("nvme: use a work item to submit async event requests")
  * 79f2b358c9ba ("nvme: don't poll the CQ from the kthread")
  * 2d55cd5f511d ("nvme: replace the kthread with a per-device watchdog 
timer")
  * 9bf2b972afea ("NVMe: Fix reset/remove race")
  * c875a7093f04 ("nvme: Avoid reset work on watchdog timer function during 
error recovery")
  * a5229050b69c ("NVMe: Always use MSI/MSI-x interrupts")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602724/+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 1612564] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 10, failed: 2

[Brad Figg]

tests ran:  10, failed: 2;
  
http://kernel.ubuntu.com/testing/3.19.0-68.76~14.04.1/ms10-34-mcdivittB0-kernel__3.19.0-68.76~14.04.1__2016-08-22_18-20-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/1612564

Title:
  linux-lts-vivid: 3.19.0-68.76~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:
  Fix Released
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:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.19.0-68.76~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 --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1612550
  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/1612564/+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 1612564] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 10, failed: 2

[Brad Figg]

tests ran:  10, failed: 2;
  
http://kernel.ubuntu.com/testing/3.19.0-68.76~14.04.1/ms10-35-mcdivittB0-kernel__3.19.0-68.76~14.04.1__2016-08-22_18-19-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/1612564

Title:
  linux-lts-vivid: 3.19.0-68.76~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:
  Fix Released
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:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.19.0-68.76~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 --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1612550
  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/1612564/+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 1615751] Re: kernel boot (not userspace) on azure takes > 5 minutes

[Scott Moser]

I just launched 1 instance of xenial and of trusty with the same user-
data, both of these were 'Standard_D1_v2' type.  They do not seem to
have such bad performance. trusty does not have systemd-analyze, but
i've included 'dmesg | grep sda1.*mounted' for each, which shows quite a
difference to the point where sda1 is mounted (and then re-mounted rw).

I've also included the initramfs-tools version as xenial and yakkety are
actually running the same kernel version.  So something else is at play
here.

# Trusty

uptime: 49.59 seconds
you launched me at: Mon, 22 Aug 2016 18:24:45 +
it is now : Mon, 22 Aug 2016 18:27:08 +
kernel booted : Mon, 22 Aug 2016 18:26:19 +
launch to kernel boot: 94 seconds
launch to user-data  : 143   seconds

$ dmesg | grep sda1.*mounted
[3.860600] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: 
(null)
[6.797368] EXT4-fs (sda1): re-mounted. Opts: discard

$ uname -r
4.4.0-34-generic

$ dpkg-query --show initramfs-tools
initramfs-tools   0.103ubuntu4.4


# xenial
uptime: 47.52 seconds
you launched me at: Mon, 22 Aug 2016 18:23:50 +
it is now : Mon, 22 Aug 2016 18:26:34 +
kernel booted : Mon, 22 Aug 2016 18:25:47 +
launch to kernel boot: 117 seconds
launch to user-data  : 164   seconds
$ systemd-analyze 
Startup finished in 7.597s (kernel) + 40.875s (userspace) = 48.472s

$ dmesg | grep sda1.*mounted
[5.795233] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: 
(null)
[   12.130461] EXT4-fs (sda1): re-mounted. Opts: discard

$ uname -r
4.4.0-34-generic
$ dpkg-query --show initramfs-tools
initramfs-tools   0.122ubuntu8.1


# yakkety
$ dmesg | grep sda1.*mounted[  305.882955] EXT4-fs (sda1): mounted filesystem 
with ordered data mode. Opts: (null)
[  306.921043] EXT4-fs (sda1): re-mounted. Opts: discard

$ uname -r
4.4.0-34-generic
$ dpkg-query --show initramfs-tools
initramfs-tools   0.125ubuntu2


** Also affects: initramfs-tools (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: initramfs-tools (Ubuntu Yakkety)
   Status: New => Confirmed

** Changed in: initramfs-tools (Ubuntu Yakkety)
   Importance: Undecided => High

** No longer affects: linux (Ubuntu)

** No longer affects: linux (Ubuntu 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/1615751

Title:
  ROOTDELAY= causes unnecessary delay in boot

Status in cloud-images:
  New
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools source package in Yakkety:
  Confirmed

Bug description:
  I launched 2 different yakkety systems on azure instance types:
    Basic_A0
    Standard_D1_v2
  More information what those things are at :
    https://azure.microsoft.com/en-us/pricing/details/virtual-machines/linux/

  systemd-analize says:

  ## Basic A0
  smoser@sm-y-d1v2-1:~$ systemd-analyze
  Startup finished in 5min 8.172s (kernel) + 42.670s (userspace) = 5min 50.842s

  ## Standard D1 v2
  $ systemd-analyze
  Startup finished in 5min 13.347s (kernel) + 1min 31.532s (userspace) = 6min 
44.879s

  Systemd thinks that more than 5 minutes passed between the kernel
  being loaded and /sbin/init being run.  I'm pretty sure this isn't
  just a bad clock, as the system actually is not reachable for
  something like 6 minutes after boot, so it seems sane.  Additionally,
  I have some scripts that compare launch time and code ran inside the
  vm via cloud-init and they agree.

  For example:
    starting at Mon, 22 Aug 2016 15:37:43 +
    uptime: 349.77 seconds
    you launched me at: Mon, 22 Aug 2016 15:30:11 +
    it is now : Mon, 22 Aug 2016 15:37:43 +
    kernel booted : Mon, 22 Aug 2016 15:31:54 +
    launch to kernel boot: 103 seconds
    launch to user-data  : 452   seconds

  The full dmesg is attached, but interesting bits are
  [0.815692] Trying to unpack rootfs image as initramfs...
  [1.289093] Freeing initrd memory: 35660K (88001d47d000 - 
88001f75)
  ...
  [7.820798] input: TPPS/2 IBM TrackPoint as 
/devices/platform/i8042/serio1/input/input3
  [7.834419] input: AT Translated Set 2 keyboard as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/VMBUS:01/vmbus_5/serio2/input/input5
  [   72.464227] random: nonblocking pool is initialized
  [  305.527657] Btrfs loaded
  [  305.628091] blk_update_request: I/O error, dev fd0, sector 0
  [  305.632007] floppy: error -5 while reading block 0
  [  306.027898] EXT4-fs (sda1): mounted filesystem with ordered data mode. 
Opts: (null)
  [  308.901437] systemd[1]: systemd 231 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
  [  308.925746] systemd[1]: Detected virtualization microsoft.
  [  308.933658] systemd[1]: Detected architecture x86-64.
  [  308.999041] 

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

[Brad Figg]

This change was made by a bot.

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

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

Title:
  iwlwifi queue stuck, Microcode SW error detected,  "ieee80211 phy0:
  Hardware restart was requested

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Recently (maybe since updating to linux-image-4.4.0-34-generic:amd64
  (4.4.0-34.53), i've not used this notebook to much lately), my wifi
  connection is unstable, often hangs and therefore spread a lot of bad
  karma to all networking applications. My log shows entries of the
  following pattern

  Aug 22 20:12:56 nb-voer kernel: [ 1792.518944] iwlwifi :02:00.0: Queue 2 
stuck for 1 ms.
  Aug 22 20:12:56 nb-voer kernel: [ 1792.518962] iwlwifi :02:00.0: Current 
SW read_ptr 86 write_ptr 124
  Aug 22 20:12:56 nb-voer kernel: [ 1792.518999] iwl data: : 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00  
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519024] iwlwifi :02:00.0: FH 
TRBs(0) = 0x
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519037] iwlwifi :02:00.0: FH 
TRBs(1) = 0x80102065
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519050] iwlwifi :02:00.0: FH 
TRBs(2) = 0x
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519062] iwlwifi :02:00.0: FH 
TRBs(3) = 0x8031
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519075] iwlwifi :02:00.0: FH 
TRBs(4) = 0x
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519088] iwlwifi :02:00.0: FH 
TRBs(5) = 0x
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519100] iwlwifi :02:00.0: FH 
TRBs(6) = 0x
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519113] iwlwifi :02:00.0: FH 
TRBs(7) = 0x00709052
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519163] iwlwifi :02:00.0: Q 0 is 
active and mapped to fifo 3 ra_tid 0x [2,2]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519213] iwlwifi :02:00.0: Q 1 is 
active and mapped to fifo 2 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519265] iwlwifi :02:00.0: Q 2 is 
active and mapped to fifo 1 ra_tid 0x [86,124]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519326] iwlwifi :02:00.0: Q 3 is 
active and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519376] iwlwifi :02:00.0: Q 4 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519426] iwlwifi :02:00.0: Q 5 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519476] iwlwifi :02:00.0: Q 6 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519526] iwlwifi :02:00.0: Q 7 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519576] iwlwifi :02:00.0: Q 8 is 
active and mapped to fifo 3 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519626] iwlwifi :02:00.0: Q 9 is 
active and mapped to fifo 7 ra_tid 0x [83,83]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519676] iwlwifi :02:00.0: Q 10 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519726] iwlwifi :02:00.0: Q 11 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519776] iwlwifi :02:00.0: Q 12 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519826] iwlwifi :02:00.0: Q 13 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519876] iwlwifi :02:00.0: Q 14 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519925] iwlwifi :02:00.0: Q 15 is 
active and mapped to fifo 5 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519975] iwlwifi :02:00.0: Q 16 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.520025] iwlwifi :02:00.0: Q 17 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.520075] iwlwifi :02:00.0: Q 18 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.520125] iwlwifi :02:00.0: Q 19 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.520175] iwlwifi :02:00.0: Q 20 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.520225] iwlwifi :02:00.0: Q 21 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.520275] iwlwifi :02:00.0: Q 22 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.520324] iwlwifi :02:00.0: Q 23 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 

[Kernel-packages] [Bug 1615774] Re: iwlwifi queue stuck, Microcode SW error detected, "ieee80211 phy0: Hardware restart was requested

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc3

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

Title:
  iwlwifi queue stuck, Microcode SW error detected,  "ieee80211 phy0:
  Hardware restart was requested

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Recently (maybe since updating to linux-image-4.4.0-34-generic:amd64
  (4.4.0-34.53), i've not used this notebook to much lately), my wifi
  connection is unstable, often hangs and therefore spread a lot of bad
  karma to all networking applications. My log shows entries of the
  following pattern

  Aug 22 20:12:56 nb-voer kernel: [ 1792.518944] iwlwifi :02:00.0: Queue 2 
stuck for 1 ms.
  Aug 22 20:12:56 nb-voer kernel: [ 1792.518962] iwlwifi :02:00.0: Current 
SW read_ptr 86 write_ptr 124
  Aug 22 20:12:56 nb-voer kernel: [ 1792.518999] iwl data: : 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00  
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519024] iwlwifi :02:00.0: FH 
TRBs(0) = 0x
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519037] iwlwifi :02:00.0: FH 
TRBs(1) = 0x80102065
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519050] iwlwifi :02:00.0: FH 
TRBs(2) = 0x
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519062] iwlwifi :02:00.0: FH 
TRBs(3) = 0x8031
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519075] iwlwifi :02:00.0: FH 
TRBs(4) = 0x
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519088] iwlwifi :02:00.0: FH 
TRBs(5) = 0x
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519100] iwlwifi :02:00.0: FH 
TRBs(6) = 0x
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519113] iwlwifi :02:00.0: FH 
TRBs(7) = 0x00709052
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519163] iwlwifi :02:00.0: Q 0 is 
active and mapped to fifo 3 ra_tid 0x [2,2]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519213] iwlwifi :02:00.0: Q 1 is 
active and mapped to fifo 2 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519265] iwlwifi :02:00.0: Q 2 is 
active and mapped to fifo 1 ra_tid 0x [86,124]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519326] iwlwifi :02:00.0: Q 3 is 
active and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519376] iwlwifi :02:00.0: Q 4 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519426] iwlwifi :02:00.0: Q 5 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519476] iwlwifi :02:00.0: Q 6 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519526] iwlwifi :02:00.0: Q 7 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519576] iwlwifi :02:00.0: Q 8 is 
active and mapped to fifo 3 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519626] iwlwifi :02:00.0: Q 9 is 
active and mapped to fifo 7 ra_tid 0x [83,83]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519676] iwlwifi :02:00.0: Q 10 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519726] iwlwifi :02:00.0: Q 11 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519776] iwlwifi :02:00.0: Q 12 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519826] iwlwifi :02:00.0: Q 13 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519876] iwlwifi :02:00.0: Q 14 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519925] iwlwifi :02:00.0: Q 15 is 
active and mapped to fifo 5 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519975] iwlwifi :02:00.0: Q 16 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.520025] iwlwifi :02:00.0: Q 17 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.520075] iwlwifi :02:00.0: Q 18 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.520125] iwlwifi 

[Kernel-packages] [Bug 1608236] Re: Regression: S-video output does not work

[Joseph Salisbury]

So 4.4.0-22 has the bug, but 4.4.0-31 does have the bug?  From your
testing of upstream 4.4.17 in comment #4 this sounds like it is related
to an Ubuntu specific SAUCE patch.  This would be confirmed by your test
results of the -proposed kernel.

We can perform a kernel bisect to identify the commit that introduced
this regression.  We first need to identify the last good Ubuntu kernel
and the first bad one.  If -22 is good, we probably want to test
4.4.0-29 next.  It can be downloaded from:

https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/10184098

** Tags added: performing-bisect

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

Title:
  Regression: S-video output does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Regression. S-video output can not be used. It works by 4.4.0-22-generic.
  xrandr tells on 4.4.0-31-generic:

  TV1 unknown connection (normal left inverted right x axis y axis)
 848x480   50.00 +
 640x480   50.00 +
 1024x768  50.00  
 800x600   50.00

  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
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarnos 1573 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jul 31 17:15:16 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-28 (94 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 89224MG
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/06
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 63ET13WW
  dmi.board.name: CAPELL VALLEY(NAPA) CRB
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 89224MG
  dmi.product.version: 3000 C200
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608236/+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 1615774] [NEW] iwlwifi queue stuck, Microcode SW error detected, "ieee80211 phy0: Hardware restart was requested

[Christian Vorhauer]

Public bug reported:

Recently (maybe since updating to linux-image-4.4.0-34-generic:amd64
(4.4.0-34.53), i've not used this notebook to much lately), my wifi
connection is unstable, often hangs and therefore spread a lot of bad
karma to all networking applications. My log shows entries of the
following pattern

Aug 22 20:12:56 nb-voer kernel: [ 1792.518944] iwlwifi :02:00.0: Queue 2 
stuck for 1 ms.
Aug 22 20:12:56 nb-voer kernel: [ 1792.518962] iwlwifi :02:00.0: Current SW 
read_ptr 86 write_ptr 124
Aug 22 20:12:56 nb-voer kernel: [ 1792.518999] iwl data: : 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00  
Aug 22 20:12:56 nb-voer kernel: [ 1792.519024] iwlwifi :02:00.0: FH TRBs(0) 
= 0x
Aug 22 20:12:56 nb-voer kernel: [ 1792.519037] iwlwifi :02:00.0: FH TRBs(1) 
= 0x80102065
Aug 22 20:12:56 nb-voer kernel: [ 1792.519050] iwlwifi :02:00.0: FH TRBs(2) 
= 0x
Aug 22 20:12:56 nb-voer kernel: [ 1792.519062] iwlwifi :02:00.0: FH TRBs(3) 
= 0x8031
Aug 22 20:12:56 nb-voer kernel: [ 1792.519075] iwlwifi :02:00.0: FH TRBs(4) 
= 0x
Aug 22 20:12:56 nb-voer kernel: [ 1792.519088] iwlwifi :02:00.0: FH TRBs(5) 
= 0x
Aug 22 20:12:56 nb-voer kernel: [ 1792.519100] iwlwifi :02:00.0: FH TRBs(6) 
= 0x
Aug 22 20:12:56 nb-voer kernel: [ 1792.519113] iwlwifi :02:00.0: FH TRBs(7) 
= 0x00709052
Aug 22 20:12:56 nb-voer kernel: [ 1792.519163] iwlwifi :02:00.0: Q 0 is 
active and mapped to fifo 3 ra_tid 0x [2,2]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519213] iwlwifi :02:00.0: Q 1 is 
active and mapped to fifo 2 ra_tid 0x [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519265] iwlwifi :02:00.0: Q 2 is 
active and mapped to fifo 1 ra_tid 0x [86,124]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519326] iwlwifi :02:00.0: Q 3 is 
active and mapped to fifo 0 ra_tid 0x [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519376] iwlwifi :02:00.0: Q 4 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519426] iwlwifi :02:00.0: Q 5 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519476] iwlwifi :02:00.0: Q 6 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519526] iwlwifi :02:00.0: Q 7 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519576] iwlwifi :02:00.0: Q 8 is 
active and mapped to fifo 3 ra_tid 0x [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519626] iwlwifi :02:00.0: Q 9 is 
active and mapped to fifo 7 ra_tid 0x [83,83]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519676] iwlwifi :02:00.0: Q 10 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519726] iwlwifi :02:00.0: Q 11 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519776] iwlwifi :02:00.0: Q 12 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519826] iwlwifi :02:00.0: Q 13 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519876] iwlwifi :02:00.0: Q 14 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519925] iwlwifi :02:00.0: Q 15 is 
active and mapped to fifo 5 ra_tid 0x [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.519975] iwlwifi :02:00.0: Q 16 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.520025] iwlwifi :02:00.0: Q 17 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.520075] iwlwifi :02:00.0: Q 18 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.520125] iwlwifi :02:00.0: Q 19 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.520175] iwlwifi :02:00.0: Q 20 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.520225] iwlwifi :02:00.0: Q 21 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.520275] iwlwifi :02:00.0: Q 22 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.520324] iwlwifi :02:00.0: Q 23 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.520374] iwlwifi :02:00.0: Q 24 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.520424] iwlwifi :02:00.0: Q 25 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.520474] iwlwifi :02:00.0: Q 26 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
Aug 22 20:12:56 nb-voer kernel: [ 1792.520524] iwlwifi :02:00.0: Q 27 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
Aug 22 20:12:56 nb-voer 

[Kernel-packages] [Bug 1615751] Re: kernel boot (not userspace) on azure takes > 5 minutes

[Joseph Salisbury]

Does this issue also happen with Xenial or earlier kernels?

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

** Also affects: linux (Ubuntu Yakkety)
   Importance: High
   Status: Confirmed

** Tags added: kernel-da-key

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

Title:
  kernel boot (not userspace) on azure takes > 5 minutes

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

Bug description:
  I launched 2 different yakkety systems on azure instance types:
    Basic_A0
    Standard_D1_v2
  More information what those things are at :
    https://azure.microsoft.com/en-us/pricing/details/virtual-machines/linux/

  systemd-analize says:

  ## Basic A0
  smoser@sm-y-d1v2-1:~$ systemd-analyze
  Startup finished in 5min 8.172s (kernel) + 42.670s (userspace) = 5min 50.842s

  ## Standard D1 v2
  $ systemd-analyze
  Startup finished in 5min 13.347s (kernel) + 1min 31.532s (userspace) = 6min 
44.879s

  Systemd thinks that more than 5 minutes passed between the kernel
  being loaded and /sbin/init being run.  I'm pretty sure this isn't
  just a bad clock, as the system actually is not reachable for
  something like 6 minutes after boot, so it seems sane.  Additionally,
  I have some scripts that compare launch time and code ran inside the
  vm via cloud-init and they agree.

  For example:
    starting at Mon, 22 Aug 2016 15:37:43 +
    uptime: 349.77 seconds
    you launched me at: Mon, 22 Aug 2016 15:30:11 +
    it is now : Mon, 22 Aug 2016 15:37:43 +
    kernel booted : Mon, 22 Aug 2016 15:31:54 +
    launch to kernel boot: 103 seconds
    launch to user-data  : 452   seconds

  The full dmesg is attached, but interesting bits are
  [0.815692] Trying to unpack rootfs image as initramfs...
  [1.289093] Freeing initrd memory: 35660K (88001d47d000 - 
88001f75)
  ...
  [7.820798] input: TPPS/2 IBM TrackPoint as 
/devices/platform/i8042/serio1/input/input3
  [7.834419] input: AT Translated Set 2 keyboard as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/VMBUS:01/vmbus_5/serio2/input/input5
  [   72.464227] random: nonblocking pool is initialized
  [  305.527657] Btrfs loaded
  [  305.628091] blk_update_request: I/O error, dev fd0, sector 0
  [  305.632007] floppy: error -5 while reading block 0
  [  306.027898] EXT4-fs (sda1): mounted filesystem with ordered data mode. 
Opts: (null)
  [  308.901437] systemd[1]: systemd 231 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
  [  308.925746] systemd[1]: Detected virtualization microsoft.
  [  308.933658] systemd[1]: Detected architecture x86-64.
  [  308.999041] systemd[1]: Set hostname to .
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: User Name 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 22 15:37 seq
   crw-rw 1 root audio 116, 33 Aug 22 15:37 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:
  Date: Mon Aug 22 17:31:18 2016
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=314ea127-227e-4b64-b5b4-d70ab0fb7eb7 ro console=tty1 console=ttyS0 
earlyprintk=ttyS0 rootdelay=300
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.160
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090006
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 

[Kernel-packages] [Bug 1615681] Re: BUG: unable to handle kernel paging request at ffff820504022108

[Joseph Salisbury]

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc3


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

Title:
  BUG: unable to handle kernel paging request at 820504022108

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We get this kernel panic while running trusty with 3.19.0-26-generic. 
  It seems there is a bug in nf_nat module, I got kdump, if needed, I will 
upload.

  [702076.560806] BUG: unable to handle kernel paging request at 
820504022108
  [702076.564428] IP: [] nf_nat_setup_info+0x236/0x360 
[nf_nat]
  [702076.567971] PGD 0 
  [702076.571349] Oops: 0002 [#1] SMP 
  [702076.574656] Modules linked in: xt_nat iptable_nat nf_nat_ipv4 sch_sfq 
sch_htb xt_comment xt_iprange xt_physdev act_police cls_u32 sch_ingress 
ebt_dnat ebt_ip ebtable_nat ebt_arp veth xt_conntrack nbd nf_conntrack_netlink 
xt_TCPMSS xt_CT xt_set ip_set_hash_net ip_set nfnetlink iptable_raw 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter netconsole 
configfs xt_CHECKSUM xt_tcpudp iptable_mangle ip_tables x_tables bonding 
intel_rapl(E) iosf_mbi x86_pkg_temp_thermal(E) nf_nat intel_powerclamp(E) 
nf_conntrack_pptp nf_conntrack_proto_gre coretemp(E) br_netfilter 
crct10dif_pclmul ipmi_ssif(E) crc32_pclmul ghash_clmulni_intel aesni_intel 
bridge stp aes_x86_64 llc lrw ipmi_devintf(E) nf_conntrack_ipv4 gf128mul 
nf_defrag_ipv4 glue_helper ablk_helper cryptd mxm_wmi(E) dcdbas(E) sb_edac(E) 
mei_me(E)
  [702076.613908]  nf_conntrack mei(E) lpc_ich(E) edac_core(E) drbd(OE) 
ipmi_si(E) ipmi_msghandler 8250_fintek(E) shpchp(E) vhost_net vhost 
acpi_power_meter(E) macvtap wmi(E) macvlan mac_hid(E) kvm_intel kvm lp xfs 
parport libcrc32c ahci megaraid_sas(E) libahci tg3(E) ixgbe(OE) dca(E) vxlan 
ip6_udp_tunnel udp_tunnel ptp pps_core
  [702076.638776] CPU: 19 PID: 0 Comm: swapper/19 Tainted: G   OE  
3.19.0-26-generic #28~14.04.1
  [702076.649826] Hardware name: Dell Inc. PowerEdge R730/0WCJNT, BIOS 2.1.5 
04/11/2016
  [702076.66] task: 883011c49d70 ti: 881812224000 task.ti: 
881812224000
  [702076.672654] RIP: 0010:[]  [] 
nf_nat_setup_info+0x236/0x360 [nf_nat]
  [702076.684662] RSP: 0018:88301eb235b8  EFLAGS: 00010286
  [702076.690647] RAX: 882fbcd21700 RBX: 882f17b1bd40 RCX: 
820504022100
  [702076.702499] RDX: 88180fb7f038 RSI: 3637ced5 RDI: 
c04a04a0
  [702076.714455] RBP: 88301eb23668 R08:  R09: 
88301eb235b8
  [702076.726823] R10: 88301eb23560 R11: 88300eeb8000 R12: 
0006fe07
  [702076.739167] R13:  R14: 81cda040 R15: 
88301eb23678
  [702076.751481] FS:  () GS:88301eb2() 
knlGS:
  [702076.763823] CS:  0010 DS:  ES:  CR0: 80050033
  [702076.770007] CR2: 820504022108 CR3: 01c16000 CR4: 
001427e0
  [702076.782162] Stack:
  [702076.788035]  2755e673  a402c68b0002259b 

  [702076.799835]  00065000 2755e673  
a402c68b0002259b
  [702076.811642]   00065000 88300db05800 
8830001b0e70
  [702076.823573] Call Trace:
  [702076.829377]   
  [702076.829447] 
  [702076.835069]  [] __nf_nat_alloc_null_binding+0x52/0x80 
[nf_nat]
  [702076.846350]  [] nf_nat_alloc_null_binding+0x21/0x30 
[nf_nat]
  [702076.857721]  [] nf_nat_ipv4_fn+0x1dd/0x230 [nf_nat_ipv4]
  [702076.863548]  [] ? iptable_nat_ipv4_fn+0x20/0x20 
[iptable_nat]
  [702076.874933]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.886328]  [] nf_nat_ipv4_out+0x48/0xf0 [nf_nat_ipv4]
  [702076.892120]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.903384]  [] iptable_nat_ipv4_out+0x15/0x20 
[iptable_nat]
  [702076.914648]  [] nf_iterate+0x9a/0xb0
  [702076.920275]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.931324]  [] nf_hook_slow+0x74/0x130
  [702076.936913]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.947932]  [] br_nf_post_routing+0x283/0x370 
[br_netfilter]
  [702076.959286]  [] ? deliver_clone+0x60/0x60 [bridge]
  [702076.965049]  [] ? deliver_clone+0x60/0x60 [bridge]
  [702076.970612]  [] nf_iterate+0x9a/0xb0
  [702076.976050]  [] ? deliver_clone+0x60/0x60 [bridge]
  [702076.981437]  [] 

[Kernel-packages] [Bug 1615681] Re: BUG: unable to handle kernel paging request at ffff820504022108

[Joseph Salisbury]

Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of a
regression, and when this regression was introduced.   If this is a
regression, we can perform a kernel bisect to identify the commit that
introduced the problem.


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

Title:
  BUG: unable to handle kernel paging request at 820504022108

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We get this kernel panic while running trusty with 3.19.0-26-generic. 
  It seems there is a bug in nf_nat module, I got kdump, if needed, I will 
upload.

  [702076.560806] BUG: unable to handle kernel paging request at 
820504022108
  [702076.564428] IP: [] nf_nat_setup_info+0x236/0x360 
[nf_nat]
  [702076.567971] PGD 0 
  [702076.571349] Oops: 0002 [#1] SMP 
  [702076.574656] Modules linked in: xt_nat iptable_nat nf_nat_ipv4 sch_sfq 
sch_htb xt_comment xt_iprange xt_physdev act_police cls_u32 sch_ingress 
ebt_dnat ebt_ip ebtable_nat ebt_arp veth xt_conntrack nbd nf_conntrack_netlink 
xt_TCPMSS xt_CT xt_set ip_set_hash_net ip_set nfnetlink iptable_raw 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter netconsole 
configfs xt_CHECKSUM xt_tcpudp iptable_mangle ip_tables x_tables bonding 
intel_rapl(E) iosf_mbi x86_pkg_temp_thermal(E) nf_nat intel_powerclamp(E) 
nf_conntrack_pptp nf_conntrack_proto_gre coretemp(E) br_netfilter 
crct10dif_pclmul ipmi_ssif(E) crc32_pclmul ghash_clmulni_intel aesni_intel 
bridge stp aes_x86_64 llc lrw ipmi_devintf(E) nf_conntrack_ipv4 gf128mul 
nf_defrag_ipv4 glue_helper ablk_helper cryptd mxm_wmi(E) dcdbas(E) sb_edac(E) 
mei_me(E)
  [702076.613908]  nf_conntrack mei(E) lpc_ich(E) edac_core(E) drbd(OE) 
ipmi_si(E) ipmi_msghandler 8250_fintek(E) shpchp(E) vhost_net vhost 
acpi_power_meter(E) macvtap wmi(E) macvlan mac_hid(E) kvm_intel kvm lp xfs 
parport libcrc32c ahci megaraid_sas(E) libahci tg3(E) ixgbe(OE) dca(E) vxlan 
ip6_udp_tunnel udp_tunnel ptp pps_core
  [702076.638776] CPU: 19 PID: 0 Comm: swapper/19 Tainted: G   OE  
3.19.0-26-generic #28~14.04.1
  [702076.649826] Hardware name: Dell Inc. PowerEdge R730/0WCJNT, BIOS 2.1.5 
04/11/2016
  [702076.66] task: 883011c49d70 ti: 881812224000 task.ti: 
881812224000
  [702076.672654] RIP: 0010:[]  [] 
nf_nat_setup_info+0x236/0x360 [nf_nat]
  [702076.684662] RSP: 0018:88301eb235b8  EFLAGS: 00010286
  [702076.690647] RAX: 882fbcd21700 RBX: 882f17b1bd40 RCX: 
820504022100
  [702076.702499] RDX: 88180fb7f038 RSI: 3637ced5 RDI: 
c04a04a0
  [702076.714455] RBP: 88301eb23668 R08:  R09: 
88301eb235b8
  [702076.726823] R10: 88301eb23560 R11: 88300eeb8000 R12: 
0006fe07
  [702076.739167] R13:  R14: 81cda040 R15: 
88301eb23678
  [702076.751481] FS:  () GS:88301eb2() 
knlGS:
  [702076.763823] CS:  0010 DS:  ES:  CR0: 80050033
  [702076.770007] CR2: 820504022108 CR3: 01c16000 CR4: 
001427e0
  [702076.782162] Stack:
  [702076.788035]  2755e673  a402c68b0002259b 

  [702076.799835]  00065000 2755e673  
a402c68b0002259b
  [702076.811642]   00065000 88300db05800 
8830001b0e70
  [702076.823573] Call Trace:
  [702076.829377]   
  [702076.829447] 
  [702076.835069]  [] __nf_nat_alloc_null_binding+0x52/0x80 
[nf_nat]
  [702076.846350]  [] nf_nat_alloc_null_binding+0x21/0x30 
[nf_nat]
  [702076.857721]  [] nf_nat_ipv4_fn+0x1dd/0x230 [nf_nat_ipv4]
  [702076.863548]  [] ? iptable_nat_ipv4_fn+0x20/0x20 
[iptable_nat]
  [702076.874933]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.886328]  [] nf_nat_ipv4_out+0x48/0xf0 [nf_nat_ipv4]
  [702076.892120]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.903384]  [] iptable_nat_ipv4_out+0x15/0x20 
[iptable_nat]
  [702076.914648]  [] nf_iterate+0x9a/0xb0
  [702076.920275]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.931324]  [] nf_hook_slow+0x74/0x130
  [702076.936913]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.947932]  [] br_nf_post_routing+0x283/0x370 
[br_netfilter]
  [702076.959286]  [] ? deliver_clone+0x60/0x60 [bridge]
  [702076.965049]  [] ? deliver_clone+0x60/0x60 [bridge]
  [702076.970612]  [] nf_iterate+0x9a/0xb0
  [702076.976050]  [] ? deliver_clone+0x60/0x60 [bridge]
  [702076.981437]  [] nf_hook_slow+0x74/0x130
  [702076.986715]  [] ? deliver_clone+0x60/0x60 [bridge]
  [702076.992071]  [] ? br_flood+0x160/0x160 [bridge]
  [702076.997487]  [] 

[Kernel-packages] [Bug 1592443] Re: [Ubuntu 16.10] CAPI flash (cxlflash) driver and CXL kernel services to support driver event notification

[Tim Gardner]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
   Status: Triaged

** Changed in: linux (Ubuntu Yakkety)
   Status: Triaged => Fix Released

** Changed in: linux (Ubuntu Yakkety)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => (unassigned)

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

Title:
  [Ubuntu 16.10] CAPI flash (cxlflash) driver and CXL kernel services to
  support driver event notification

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

Bug description:
  This adds an afu_driver_ops structure with deliver_event callback. An
  AFU driver such as cxlflash can fill this out and associate it with a
  context to enable passing custom AFU specific events to userspace.

  This also adds a new kernel API function cxl_context_pending_events(),
  that the AFU driver can use to notify the cxl driver that new specific
  events are ready to be delivered, and wake up anyone waiting on the
  context wait queue.

  The current count of AFU driver specific events is stored in the field
  afu_driver_events of the context structure.

  The cxl driver will check the afu_driver_events count during poll,
  select, read, etc. calls to check if an AFU driver specific event is
  pending, and will call deliver_event() to deliver that event. This
  way, the cxl driver takes care of all the usual locking semantics
  around these calls and handles all the generic cxl events, so that the
  AFU driver only needs to worry about it's own events.

  This is a kernel feature for Ubuntu 16.10

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

[bugproxy]

--- Comment From bren...@br.ibm.com 2016-08-22 14:04 EDT---
Canonical,  all the patches seem to be integrated in kernel 4.8, so, there is 
no action at your side at this time.

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

Title:
  [Ubuntu 16.10] CAPI flash (cxlflash) driver and CXL kernel services to
  support driver event notification

Status in linux package in Ubuntu:
  Triaged

Bug description:
  This adds an afu_driver_ops structure with deliver_event callback. An
  AFU driver such as cxlflash can fill this out and associate it with a
  context to enable passing custom AFU specific events to userspace.

  This also adds a new kernel API function cxl_context_pending_events(),
  that the AFU driver can use to notify the cxl driver that new specific
  events are ready to be delivered, and wake up anyone waiting on the
  context wait queue.

  The current count of AFU driver specific events is stored in the field
  afu_driver_events of the context structure.

  The cxl driver will check the afu_driver_events count during poll,
  select, read, etc. calls to check if an AFU driver specific event is
  pending, and will call deliver_event() to deliver that event. This
  way, the cxl driver takes care of all the usual locking semantics
  around these calls and handles all the generic cxl events, so that the
  AFU driver only needs to worry about it's own events.

  This is a kernel feature for Ubuntu 16.10

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

[Brad Figg]

tests ran:  10, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-68.76~14.04.1/onza__3.19.0-68.76~14.04.1__2016-08-22_17-12-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/1612564

Title:
  linux-lts-vivid: 3.19.0-68.76~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:
  Fix Released
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:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.19.0-68.76~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 --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1612550
  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/1612564/+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 1615751] Status changed to Confirmed

[Brad Figg]

This change was made by a bot.

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

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

Title:
  kernel boot (not userspace) on azure takes > 5 minutes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I launched 2 different yakkety systems on azure instance types:
    Basic_A0
    Standard_D1_v2
  More information what those things are at :
    https://azure.microsoft.com/en-us/pricing/details/virtual-machines/linux/

  systemd-analize says:

  ## Basic A0
  smoser@sm-y-d1v2-1:~$ systemd-analyze
  Startup finished in 5min 8.172s (kernel) + 42.670s (userspace) = 5min 50.842s

  ## Standard D1 v2
  $ systemd-analyze
  Startup finished in 5min 13.347s (kernel) + 1min 31.532s (userspace) = 6min 
44.879s

  Systemd thinks that more than 5 minutes passed between the kernel
  being loaded and /sbin/init being run.  I'm pretty sure this isn't
  just a bad clock, as the system actually is not reachable for
  something like 6 minutes after boot, so it seems sane.  Additionally,
  I have some scripts that compare launch time and code ran inside the
  vm via cloud-init and they agree.

  For example:
    starting at Mon, 22 Aug 2016 15:37:43 +
    uptime: 349.77 seconds
    you launched me at: Mon, 22 Aug 2016 15:30:11 +
    it is now : Mon, 22 Aug 2016 15:37:43 +
    kernel booted : Mon, 22 Aug 2016 15:31:54 +
    launch to kernel boot: 103 seconds
    launch to user-data  : 452   seconds

  The full dmesg is attached, but interesting bits are
  [0.815692] Trying to unpack rootfs image as initramfs...
  [1.289093] Freeing initrd memory: 35660K (88001d47d000 - 
88001f75)
  ...
  [7.820798] input: TPPS/2 IBM TrackPoint as 
/devices/platform/i8042/serio1/input/input3
  [7.834419] input: AT Translated Set 2 keyboard as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/VMBUS:01/vmbus_5/serio2/input/input5
  [   72.464227] random: nonblocking pool is initialized
  [  305.527657] Btrfs loaded
  [  305.628091] blk_update_request: I/O error, dev fd0, sector 0
  [  305.632007] floppy: error -5 while reading block 0
  [  306.027898] EXT4-fs (sda1): mounted filesystem with ordered data mode. 
Opts: (null)
  [  308.901437] systemd[1]: systemd 231 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
  [  308.925746] systemd[1]: Detected virtualization microsoft.
  [  308.933658] systemd[1]: Detected architecture x86-64.
  [  308.999041] systemd[1]: Set hostname to .
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: User Name 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 22 15:37 seq
   crw-rw 1 root audio 116, 33 Aug 22 15:37 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:
  Date: Mon Aug 22 17:31:18 2016
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=314ea127-227e-4b64-b5b4-d70ab0fb7eb7 ro console=tty1 console=ttyS0 
earlyprintk=ttyS0 rootdelay=300
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.160
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090006
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1579374] Re: amdgpu causes NULL pointer dereference when trying to use Topaz (Radeon R7 M265) GPU

[Paulo Matias]

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

Title:
  amdgpu causes NULL pointer dereference when trying to use Topaz
  (Radeon R7 M265) GPU

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A Dell Inspiron 5448 / 0YDTG3 laptop (BIOS A06 10/12/2015), which used
  to work well with Ubuntu trusty and Ubuntu wily releases (using fglrx
  driver), presents multiple issues with Ubuntu xenial.

  When the amdgpu driver tries to activate the Radeon GPU, a NULL
  pointer dereference occurs, causing the caller process to hang. This
  practically causes the system to hang when trying a logoff or
  shutdown.

  The bug can be easily reproduced by calling:

  DRI_PRIME=1 glxgears

  Which hangs the glxgears process and causes the stacktrace attached
  below.

  The system also crashes with a kernel panic (capslock key blinking and
  system does not answer to magic SysRq keys) when coming back from a
  suspend.

  The bug reported in this forum post
  http://ubuntuforums.org/showthread.php?t=2318640 appears to be the
  same.

  Kernel 4.5.0-050400 from http://kernel.ubuntu.com/~kernel-
  ppa/mainline/v4.5-wily fixes the crashes and oopses, although the
  Radeon GPU still does not work (DRI_PRIME=1 glxgears opens a black
  window). However, at least the system can be used with the Intel GPU
  in a stable fashion.

  
  ---[cut]---

  $ lspci
  [...]
  04:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT 
[Radeon R7 M260/M265]
  $ dmesg
  [...]
  [  129.188685] [drm] PCIE GART of 2048M enabled (table at 0x0004).
  [  129.429667] [drm] ring test on 0 succeeded in 14 usecs
  [  131.087501] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp 
failed to lock ring 1 (-2).
  [  131.087520] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp 
failed to lock ring 2 (-2).
  [  131.087533] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp 
failed to lock ring 3 (-2).
  [  131.087547] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp 
failed to lock ring 4 (-2).
  [  131.087558] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp 
failed to lock ring 5 (-2).
  [  131.087571] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp 
failed to lock ring 6 (-2).
  [  131.087582] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp 
failed to lock ring 7 (-2).
  [  131.087595] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp 
failed to lock ring 8 (-2).
  [  131.191024] [drm:sdma_v2_4_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 9 
test failed (0xCAFEDEAD)
  [  131.191034] [drm:amdgpu_resume [amdgpu]] *ERROR* resume 5 failed -22
  [  131.191043] [drm:amdgpu_resume_kms [amdgpu]] *ERROR* amdgpu_resume failed 
(-22).
  [  131.191149] amdgpu :04:00.0: couldn't schedule ib
  [  131.191179] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [  131.191203] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [  131.201417] amdgpu :04:00.0: couldn't schedule ib
  [  131.201444] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [  131.201462] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [  131.201465] amdgpu :04:00.0: couldn't schedule ib
  [  131.201479] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [  131.201493] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [  131.201494] amdgpu :04:00.0: couldn't schedule ib
  [  131.201508] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [  131.201523] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [  131.201524] amdgpu :04:00.0: couldn't schedule ib
  [  131.201535] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [  131.201546] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [  131.201548] amdgpu :04:00.0: couldn't schedule ib
  [  131.201558] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [  131.201569] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [  131.201571] amdgpu :04:00.0: couldn't schedule ib
  [  131.201581] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling 
IBs (-22)
  [  131.201592] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [  131.201616] BUG: unable to handle kernel NULL pointer dereference at 
0248
  [  131.201648] IP: [] amdgpu_vm_grab_id+0x122/0x310 [amdgpu]
  [  131.201684] PGD 0 
  [  131.201693] Oops:  [#1] SMP 
  [  131.201707] Modules linked in: ctr ccm rfcomm pci_stub vboxpci(OE) 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep binfmt_misc rtsx_usb_ms memstick 
nls_iso8859_1 dell_wmi sparse_keymap dell_laptop intel_rapl 
x86_pkg_temp_thermal arc4 intel_powerclamp dcdbas dell_smm_hwmon coretemp 
dell_led 

[Kernel-packages] [Bug 1612564] onibi (amd64) - tests ran: 10, failed: 0

[Brad Figg]

tests ran:  10, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-68.76~14.04.1/onibi__3.19.0-68.76~14.04.1__2016-08-22_17-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/1612564

Title:
  linux-lts-vivid: 3.19.0-68.76~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:
  Fix Released
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:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.19.0-68.76~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 --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1612550
  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/1612564/+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 1615751] Re: kernel boot (not userspace) on azure takes > 5 minutes

[Scott Moser]

** Description changed:

  I launched 2 different yakkety systems on azure instance types:
    Basic_A0
    Standard_D1_v2
  More information what those things are at :
    https://azure.microsoft.com/en-us/pricing/details/virtual-machines/linux/
  
  systemd-analize says:
  
- ## Standard D1 v2
- $ systemd-analyze
+ ## Basic A0
+ smoser@sm-y-d1v2-1:~$ systemd-analyze
  Startup finished in 5min 8.172s (kernel) + 42.670s (userspace) = 5min 50.842s
  
- ## Basic A0
+ ## Standard D1 v2
  $ systemd-analyze
  Startup finished in 5min 13.347s (kernel) + 1min 31.532s (userspace) = 6min 
44.879s
  
  Systemd thinks that more than 5 minutes passed between the kernel being
  loaded and /sbin/init being run.  I'm pretty sure this isn't just a bad
  clock, as the system actually is not reachable for something like 6
  minutes after boot, so it seems sane.  Additionally, I have some scripts
  that compare launch time and code ran inside the vm via cloud-init and
  they agree.
  
  For example:
    starting at Mon, 22 Aug 2016 15:37:43 +
    uptime: 349.77 seconds
    you launched me at: Mon, 22 Aug 2016 15:30:11 +
    it is now : Mon, 22 Aug 2016 15:37:43 +
    kernel booted : Mon, 22 Aug 2016 15:31:54 +
    launch to kernel boot: 103 seconds
    launch to user-data  : 452   seconds
+ 
+ The full dmesg is attached, but interesting bits are
+ [0.815692] Trying to unpack rootfs image as initramfs...
+ [1.289093] Freeing initrd memory: 35660K (88001d47d000 - 
88001f75)
+ ...
+ [7.820798] input: TPPS/2 IBM TrackPoint as 
/devices/platform/i8042/serio1/input/input3
+ [7.834419] input: AT Translated Set 2 keyboard as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/VMBUS:01/vmbus_5/serio2/input/input5
+ [   72.464227] random: nonblocking pool is initialized
+ [  305.527657] Btrfs loaded
+ [  305.628091] blk_update_request: I/O error, dev fd0, sector 0
+ [  305.632007] floppy: error -5 while reading block 0
+ [  306.027898] EXT4-fs (sda1): mounted filesystem with ordered data mode. 
Opts: (null)
+ [  308.901437] systemd[1]: systemd 231 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
+ [  308.925746] systemd[1]: Detected virtualization microsoft.
+ [  308.933658] systemd[1]: Detected architecture x86-64.
+ [  308.999041] systemd[1]: Set hostname to .
+ ...
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: User Name 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 22 15:37 seq
   crw-rw 1 root audio 116, 33 Aug 22 15:37 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:
  Date: Mon Aug 22 17:31:18 2016
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  PciMultimedia:
  
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=314ea127-227e-4b64-b5b4-d70ab0fb7eb7 ro console=tty1 console=ttyS0 
earlyprintk=ttyS0 rootdelay=300
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.160
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090006
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

Title:
  kernel boot (not userspace) on azure takes > 5 minutes

Status in linux package in Ubuntu:
  New

Bug description:
  I launched 2 different yakkety systems on azure instance types:
    

[Kernel-packages] [Bug 1615751] [NEW] kernel boot (not userspace) on azure takes > 5 minutes

[Scott Moser]

Public bug reported:

I launched 2 different yakkety systems on azure instance types:
  Basic_A0
  Standard_D1_v2
More information what those things are at :
  https://azure.microsoft.com/en-us/pricing/details/virtual-machines/linux/

systemd-analize says:

## Basic A0
smoser@sm-y-d1v2-1:~$ systemd-analyze
Startup finished in 5min 8.172s (kernel) + 42.670s (userspace) = 5min 50.842s

## Standard D1 v2
$ systemd-analyze
Startup finished in 5min 13.347s (kernel) + 1min 31.532s (userspace) = 6min 
44.879s

Systemd thinks that more than 5 minutes passed between the kernel being
loaded and /sbin/init being run.  I'm pretty sure this isn't just a bad
clock, as the system actually is not reachable for something like 6
minutes after boot, so it seems sane.  Additionally, I have some scripts
that compare launch time and code ran inside the vm via cloud-init and
they agree.

For example:
  starting at Mon, 22 Aug 2016 15:37:43 +
  uptime: 349.77 seconds
  you launched me at: Mon, 22 Aug 2016 15:30:11 +
  it is now : Mon, 22 Aug 2016 15:37:43 +
  kernel booted : Mon, 22 Aug 2016 15:31:54 +
  launch to kernel boot: 103 seconds
  launch to user-data  : 452   seconds

The full dmesg is attached, but interesting bits are
[0.815692] Trying to unpack rootfs image as initramfs...
[1.289093] Freeing initrd memory: 35660K (88001d47d000 - 
88001f75)
...
[7.820798] input: TPPS/2 IBM TrackPoint as 
/devices/platform/i8042/serio1/input/input3
[7.834419] input: AT Translated Set 2 keyboard as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/VMBUS:01/vmbus_5/serio2/input/input5
[   72.464227] random: nonblocking pool is initialized
[  305.527657] Btrfs loaded
[  305.628091] blk_update_request: I/O error, dev fd0, sector 0
[  305.632007] floppy: error -5 while reading block 0
[  306.027898] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: 
(null)
[  308.901437] systemd[1]: systemd 231 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
[  308.925746] systemd[1]: Detected virtualization microsoft.
[  308.933658] systemd[1]: Detected architecture x86-64.
[  308.999041] systemd[1]: Set hostname to .
...

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.4.0-34-generic 4.4.0-34.53
ProcVersionSignature: User Name 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Aug 22 15:37 seq
 crw-rw 1 root audio 116, 33 Aug 22 15:37 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:
Date: Mon Aug 22 17:31:18 2016
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: Microsoft Corporation Virtual Machine
PciMultimedia:

ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=314ea127-227e-4b64-b5b4-d70ab0fb7eb7 ro console=tty1 console=ttyS0 
earlyprintk=ttyS0 rootdelay=300
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-34-generic N/A
 linux-backports-modules-4.4.0-34-generic  N/A
 linux-firmware1.160
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/23/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 090006
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: 7.0
dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: 7.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
dmi.product.name: Virtual Machine
dmi.product.version: 7.0
dmi.sys.vendor: Microsoft Corporation

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


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

** Description changed:

  I launched 2 different yakkety systems on azure instance types:
-   Basic_A0
-   Standard_D1_v2
+   Basic_A0
+   Standard_D1_v2
  More information what those things are at :
-   https://azure.microsoft.com/en-us/pricing/details/virtual-machines/linux/
+   https://azure.microsoft.com/en-us/pricing/details/virtual-machines/linux/
  
  systemd-analize says:
  
- ## Basic A0
- smoser@sm-y-d1v2-1:~$ systemd-analyze
+ ## Standard D1 v2
+ $ systemd-analyze
  Startup 

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

[bugproxy]

--- Comment From gbert...@br.ibm.com 2016-08-22 13:11 EDT---
(In reply to comment #16)
> Test kernel at http://people.canonical.com/~rtg/eeh-lp1602724/ with upstream
> commit c21377f8366c95440d533edbe47d070f662c62ef ('nvme: Suspend all queues
> before deletion') applied.

This test kernel is not ok, it stalls the wq:

[  540.097661] INFO: rcu_sched detected stalls on CPUs/tasks:
[  540.103320]  1-...: (1 GPs behind) idle=d35/140/0 
softirq=2385/2386 fqs=65
[  540.103411]  (detected by 11, t=5472 jiffies, g=1335, c=1334, q=793)
[  540.103492] Task dump for CPU 1:
[  540.103539] kworker/u32:1   D  0   101  0 0x0800
[  540.103656] Call Trace:
[  540.103692] [c0017bc539c0] [c0017bc53a00] 0xc0017bc53a00 
(unreliable)
[  540.103805] [c0017bc53a00] [d1614480] 
nvme_suspend_queue+0x30/0x150 [nvme]
[  540.103914] [c0017bc53a30] [d1616850] 
nvme_dev_disable+0x110/0x440 [nvme]
[  540.104022] [c0017bc53b10] [d1617e60] 
nvme_reset_work+0xe0/0x1120 [nvme]
[  540.104132] [c0017bc53c50] [c00dd630] 
process_one_work+0x1e0/0x5a0
[  540.104239] [c0017bc53ce0] [c00ddb84] worker_thread+0x194/0x680
[  540.104331] [c0017bc53d80] [c00e6680] kthread+0x110/0x130
[  540.104424] [c0017bc53e30] [c0009538] 
ret_from_kernel_thread+0x5c/0xa4
[  604.094501] INFO: rcu_sched detected stalls on CPUs/tasks:
[  604.094699]  1-...: (1 GPs behind) idle=d35/140/0 
softirq=2385/2386 fqs=82
[  604.094700]  (detected by 5, t=21472 jiffies, g=1335, c=1334, q=1283)
[  604.094705] Task dump for CPU 1:

Can you provide the backported patch for verification?

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

Title:
  Ubuntu 16.04 - Full EEH Recovery Support for NVMe devices

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

Bug description:
  == Comment: #0 - Heitor Ricardo Alves de Siqueira  - 
2016-07-12 12:54:27 ==
  Current nvme driver in Ubuntu 16.04 kernel does not handle error recovery; we 
are missing some patches from the upstream nvme driver.

  We would like to ask Canonical to cherry pick the following patches for the 
16.04 kernel, if possible:
  * 9396dec916c0 ("nvme: use a work item to submit async event requests")
  * 79f2b358c9ba ("nvme: don't poll the CQ from the kthread")
  * 2d55cd5f511d ("nvme: replace the kthread with a per-device watchdog 
timer")
  * 9bf2b972afea ("NVMe: Fix reset/remove race")
  * c875a7093f04 ("nvme: Avoid reset work on watchdog timer function during 
error recovery")
  * a5229050b69c ("NVMe: Always use MSI/MSI-x interrupts")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602724/+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 1612135] Re: CIFS client: access problems after updating to kernel 4.4.0-29-generic

[Joseph Salisbury]

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

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

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

Title:
  CIFS client: access problems after updating to kernel 4.4.0-29-generic

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

Bug description:
  Expected: being able to mount subfilesystems via cifs mount.
  What happens: permission denied even though there is permission

  I am denied access to the subfilesystems on a samba server. The top
  level filesystem itself is unaffected but dfs links seem to run into
  'Operation not permitted' problems. When accessing the subfilesystem
  on the mount as root it mounts correctly. The standard user is then
  also able to access the subfilesystem.

  This only happens when the client uses kernel 4.4.0-34 (#53). When I
  revert my client to an older kernel (4.4.0-21) everything works. Using
  the older kernel the normal user can directly ls into the
  subfilesystem.

  This is bug is very similar to bug #1603719
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603719).
  However, the released fix (in 4.4.0-33.52) does not seem to fix it for
  cifs.

  Extra info:
  Ubuntu 16.04.1 LTS
  cifs-utils version: 2:6.4-1ubuntu1
  Mount options are minimal: sec=krb5,uid=,cruid=XXX

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.15
  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
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Thu Aug 11 10:32:20 2016
  InstallationDate: Installed on 2016-04-28 (104 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.update-motd.d.91-release-upgrade: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1612135/+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 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

[Joseph Salisbury]

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

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

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.

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

Title:
  Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

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

Bug description:
  When I install Ubuntu 16.04 on my computer the screen goes blank at
  login. I can blindly login and it boots but I cannot use the display
  (external monitor through HDMI).

  I've looked online for an answer to this issue but could not find a
  solution.  However, many people report this issue in forums with the
  4.4x kernel.

  On my main computer, I upgraded from 14.04 to 16.04.1. On this
  computer I was able to switch back to the 3.13 kernel which *does
  work*.

  On the same computer, if I use a 16.04 live CD, it does the same
  thing.  The screen goes blank.

  UEFI may be part of the issue as well.  I have it disabled in bios
  (set to legacy mode) but when I first boot, it seems to go into UEFI
  mode first and then, after rebooting with  it shows
  me the list of kernels. I can select the kernel from there but if I
  use a 4.4x kernel, it blanks out at encryption passphrase screen.

  There are also people with similar issues on AskUbuntu.

  Here's some basic HW info.  If you require more, please ask.

  sudo lshw | head
  zbox
  description: Notebook
  product: ZBOX-ID18 (NA)
  vendor: ZOTAC
  version: XX
  serial: G211X
  width: 64 bits
  capabilities: smbios-2.7 dmi-2.7 vsyscall32
  configuration: boot=normal chassis=notebook family=NA sku=NA 
uuid=00020003-0004-0005-0006-000700080009
    *-core

  sudo lshw -C display
    *-display
     description: VGA compatible controller
     product: 3rd Gen Core processor Graphics Controller
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 09
     width: 64 bits
     clock: 33MHz
     capabilities: msi pm vga_controller bus_master cap_list rom
     configuration: driver=i915 latency=0
     resources: irq:45 memory:f780-f7bf memory:e000-efff 
ioport:f000(size=64)

  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user5536 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: #RESUME=UUID=edaa55c6-eb56-43fb-8004-495948b72b38
  InstallationDate: Installed on 2014-07-23 (743 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313)
  MachineType: ZOTAC ZBOX-ID18
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39
  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-3.13.0-92-generic N/A
   linux-backports-modules-3.13.0-92-generic  N/A
   linux-firmware 1.157.2
  RfKill:

  StagingDrivers: rts5139
  Tags:  xenial staging
  Uname: Linux 3.13.0-92-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-31 (3 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B211P011
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID18
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 10
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB211P011:bd03/13/2014:svnZOTAC:pnZBOX-ID18:pvrXX:rvnZOTAC:rnZBOX-ID18:rvrXX:cvnNA:ct10:cvrNA:
  dmi.product.name: ZBOX-ID18
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1609242/+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 1568729] Re: divide error: 0000 [#1] SMP in task_numa_migrate - handle_mm_fault

[Bert JW Regeer]

Just ran into this issue on Ubuntu 16.04:

Aug 21 02:49:14 doddering-fransisca kernel: [2532635.918673] divide error:  
[#1] SMP 
Aug 21 02:49:14 doddering-fransisca kernel: [2532635.935386] Modules linked in: 
bridge stp llc bonding nls_iso8859_1 ipmi_ssif ipmi_devintf dcdbas intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass sb_edac 
edac_core 8250_fintek ipmi_si ipmi_msghandler mei_me mei lpc_ich shpchp 
acpi_power_meter mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core 
ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid0 multipath linear raid1 crct10dif_pclmul crc32_pclmul 
mxm_wmi aesni_intel aes_x86_64 lrw ixgbe i40e gf128mul glue_helper igb 
ablk_helper vxlan cryptd ip6_udp_tunnel udp_tunnel dca mdio ahci ptp libahci 
pps_core i2c_algo_bit fjes wmi
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.036341] CPU: 20 PID: 95997 
Comm: jujud Not tainted 4.4.0-31-generic #50-Ubuntu
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.052997] Hardware name: 
Dell Inc. PowerEdge C6320/082F9M, BIOS 2.0.2 02/16/2016
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.069486] task: 
883f0cbd9b80 ti: 883f5ae5c000 task.ti: 883f5ae5c000
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.085837] RIP: 
0010:[]  [] task_numa_find_cpu+0x2cd/0x710
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.102963] RSP: 
:883f5ae5fbd8  EFLAGS: 00010257
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.118987] RAX: 
 RBX: 883f5ae5fc78 RCX: 0414
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.134881] RDX: 
 RSI:  RDI: 88547de36200
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.150581] RBP: 
883f5ae5fc40 R08: 012a R09: 00075d4a
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.166034] R10: 
0084 R11: 0003eab1 R12: 887c1fc6e040
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.181262] R13: 
001b R14: 88547de36200 R15: 007c
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.196284] FS:  
7f0888ff9700() GS:883f7e88() knlGS:
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.211275] CS:  0010 DS:  
ES:  CR0: 80050033
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.225943] CR2: 
00d884976e48 CR3: 003f56296000 CR4: 003406e0
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.240452] DR0: 
 DR1:  DR2: 
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.254703] DR3: 
 DR6: fffe0ff0 DR7: 0400
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.268649] Stack:
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.282271]  001d 
0100 012a 0414
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.295952]  0065 
00c3 00016d00 012a
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.309302]  883f0cbd9b80 
883f5ae5fc78 0192 01c1
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.322438] Call Trace:
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.335248]  
[] task_numa_migrate+0x43e/0x9b0
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.347983]  
[] ? native_flush_tlb_others+0x65/0x150
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.360511]  
[] numa_migrate_preferred+0x79/0x80
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.372777]  
[] task_numa_fault+0x7f4/0xd40
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.384811]  
[] ? should_numa_migrate_memory+0x55/0x130
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.396681]  
[] handle_mm_fault+0xbc0/0x1820
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.408285]  
[] ? find_vma+0x43/0x70
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.419617]  
[] __do_page_fault+0x197/0x400
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.430724]  
[] do_page_fault+0x22/0x30
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.441594]  
[] page_fault+0x28/0x30
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.452173] Code: d0 4c 89 f7 
e8 95 c7 ff ff 49 8b 84 24 d8 01 00 00 49 8b 76 78 31 d2 49 0f af 86 b0 00 00 
00 4c 8b 45 d0 48 8b 4d b0 48 83 c6 01 <48> f7 f6 4c 89 c6 48 89 da 48 8d 3c 01 
48 29 c6 e8 de c5 ff ff 
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.473627] RIP  
[] task_numa_find_cpu+0x2cd/0x710
Aug 21 02:49:14 doddering-fransisca kernel: [2532636.483974]  RSP 

Aug 21 02:49:14 doddering-fransisca kernel: [2532636.511555] ---[ end trace 
f9c3b1b52643e68b ]---

Reboot brought the machine back up with updated kernel version:

Linux doddering-fransisca 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27
16:06:39 UTC 2016 

[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

[Alex Ng]

Might be worth trying this patchset: https://lkml.org/lkml/2016/8/18/859

The first patch in the set addresses some issues with VSS that would
cause it to take a long time to initiate backup (and even may timeout).

The second patch is not necessary (but will need VSS daemon to be
replaced if you choose to apply it).

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

Title:
  [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
  Backups

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Customers have reported running various versions of Ubuntu 14.04.2 LTS
  on Generation 2 Hyper-V Hosts.On a random Basis, the file system
  will be mounted Read-Only due to a "disk error" (which really isn't
  the case here).As a result, they must reboot the Ubuntu guest to
  get the file system to mount RW again.

  The Error seen are the following:
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed. The Linux SCSI layer does not automatically adjust these 
parameters.
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc 
vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc 
vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed.  The Linux SCSI layer does not automatically adjust these 
parameters.

  This relates to the VSS "Windows Server Backup" process that kicks off at 
midnight on the host and finishes an hour and half later.   
  Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct 
kernel version we have.   We're currently running kernel version 
3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- 
We see the same errors on both.
  As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 
hyper-v system because of this.   We can stop the backup process and all is 
good, but we need nightly backups to image all of our VM's.   All the windows 
guests have no issues of course.   We also have some CentOS based guests 
running without issues from what we've seen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1470250/+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 1614953] Re: hw csum failure when IPv6 interfaces configured in netdev_rx_csum_fault+0x38/0x40

[Andrew McDermott]

Currently running:

$ uname -a
Linux spicy 4.8.0-040800rc3-generic #201608212032 SMP Mon Aug 22 00:34:39 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

Will report back tomorrow with a finding either way.

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

Title:
  hw csum failure when IPv6 interfaces configured in
  netdev_rx_csum_fault+0x38/0x40

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since I started using IPv6 I noticed the following kernel error:

  Thu Aug 18 15:05:01 2016] : hw csum failure
  [Thu Aug 18 15:05:01 2016] CPU: 5 PID: 11086 Comm: Chrome_IOThread Tainted: P 
  OE   4.4.0-34-generic #53-Ubuntu
  [Thu Aug 18 15:05:01 2016] Hardware name: Gigabyte Technology Co., Ltd. To be 
filled by O.E.M./Z77-D3H, BIOS F22 11/14/2013
  [Thu Aug 18 15:05:01 2016]  0286 c05989f2 
8807573dfcd0 813f11b3
  [Thu Aug 18 15:05:01 2016]   0008 
8807573dfce8 8171f6e8
  [Thu Aug 18 15:05:01 2016]  0074 8807573dfd30 
8171639b fe091360
  [Thu Aug 18 15:05:01 2016] Call Trace:
  [Thu Aug 18 15:05:01 2016]  [] dump_stack+0x63/0x90
  [Thu Aug 18 15:05:01 2016]  [] 
netdev_rx_csum_fault+0x38/0x40
  [Thu Aug 18 15:05:01 2016]  [] 
skb_copy_and_csum_datagram_msg+0xeb/0x100
  [Thu Aug 18 15:05:01 2016]  [] udpv6_recvmsg+0x233/0x670
  [Thu Aug 18 15:05:01 2016]  [] inet_recvmsg+0x7e/0xb0
  [Thu Aug 18 15:05:01 2016]  [] sock_recvmsg+0x3b/0x50
  [Thu Aug 18 15:05:01 2016]  [] SYSC_recvfrom+0xe1/0x160
  [Thu Aug 18 15:05:01 2016]  [] ? wake_up_q+0x70/0x70
  [Thu Aug 18 15:05:01 2016]  [] SyS_recvfrom+0xe/0x10
  [Thu Aug 18 15:05:01 2016]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71

  It repeats periodically:

  $ dmesg -T | grep 'hw csum failure' | wc -l
  201

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 19 13:47:54 2016
  HibernationDevice: RESUME=UUID=066c8903-7f5e-43d5-b48f-76d33c4558f2
  InstallationDate: Installed on 2016-04-24 (116 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/rootpool-rootvol ro intel_iommu=on
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF22:bd11/14/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

[Brad Figg]

tests ran:  20, failed: 1;
  
http://kernel.ubuntu.com/testing/3.19.0-68.76~14.04.1/onibi__3.19.0-68.76~14.04.1__2016-08-22_14-03-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/1612564

Title:
  linux-lts-vivid: 3.19.0-68.76~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:
  Fix Released
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:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.19.0-68.76~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 --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1612550
  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/1612564/+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 1615620] Re: Xenial update to v4.4.19 stable release

[Kamal Mostafa]

** Changed in: linux (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  Xenial update to v4.4.19 stable release

Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The v4.4.19 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the v4.4.19 stable release shall be
  applied:

  usb: gadget: avoid exposing kernel stack
  usb: f_fs: off by one bug in _ffs_func_bind()
  usb: renesas_usbhs: protect the CFIFOSEL setting in usbhsg_ep_enable()
  usb: dwc3: fix for the isoc transfer EP_BUSY flag
  USB: serial: option: add support for Telit LE910 PID 0x1206
  usb: renesas_usbhs: fix NULL pointer dereference in xfer_work()
  arm64: kernel: Save and restore UAO and addr_limit on exception entry
  arm64: debug: unmask PSTATE.D earlier
  arm64: Fix incorrect per-cpu usage for boot CPU
  tty: serial: msm: Don't read off end of tx fifo
  serial: samsung: Fix ERR pointer dereference on deferred probe
  tty/serial: atmel: fix RS485 half duplex with DMA
  gpio: pca953x: Fix NBANK calculation for PCA9536
  gpio: intel-mid: Remove potentially harmful code
  Bluetooth: hci_intel: Fix null gpio desc pointer dereference
  pinctrl: cherryview: prevent concurrent access to GPIO controllers
  arm64: dts: rockchip: fixes the gic400 2nd region size for rk3368
  arm64: mm: avoid fdt_check_header() before the FDT is fully mapped
  KVM: PPC: Book3S HV: Pull out TM state save/restore into separate procedures
  KVM: PPC: Book3S HV: Save/restore TM state in H_CEDE
  KVM: MTRR: fix kvm_mtrr_check_gfn_range_consistency page fault
  KVM: VMX: handle PML full VMEXIT that occurs during event delivery
  KVM: nVMX: Fix memory corruption when using VMCS shadowing
  intel_pstate: Fix MSR_CONFIG_TDP_x addressing in core_get_max_pstate()
  mfd: qcom_rpm: Fix offset error for msm8660
  mfd: qcom_rpm: Parametrize also ack selector size
  media: usbtv: prevent access to free'd resources
  media: dvb_ringbuffer: Add memory barriers
  vb2: core: Skip planes array verification if pb is NULL
  Fix RC5 decoding with Fintek CIR chipset
  sur40: lower poll interval to fix occasional FPS drops to ~56 FPS
  sur40: fix occasional oopses on device close
  dm: set DMF_SUSPENDED* _before_ clearing DMF_NOFLUSH_SUSPENDING
  hp-wmi: Fix wifi cannot be hard-unblocked
  s5p-mfc: Set device name for reserved memory region devs
  s5p-mfc: Add release callback for memory region devs
  i2c: efm32: fix a failure path in efm32_i2c_probe()
  spi: pxa2xx: Clear all RFT bits in reset_sccr1() on Intel Quark
  Bluetooth: Fix l2cap_sock_setsockopt() with optname BT_RCVMTU
  EDAC: Correct channel count limit
  HID: uhid: fix timeout when probe races with IO
  ovl: disallow overlayfs as upperdir
  remoteproc: Fix potential race condition in rproc_add
  ARC: mm: don't loose PTE_SPECIAL in pte_modify()
  jbd2: make journal y2038 safe
  fs/cifs: make share unaccessible at root level mountable
  cifs: Check for existing directory when opening file with O_CREAT
  cifs: fix crash due to race in hmac(md5) handling
  CIFS: Fix a possible invalid memory access in smb2_query_symlink()
  random: initialize the non-blocking pool via add_hwgenerator_randomness()
  random: print a warning for the first ten uninitialized random users
  random: add interrupt callback to VMBus IRQ handler
  MIPS: KVM: Fix mapped fault broken commpage handling
  MIPS: KVM: Add missing gfn range check
  MIPS: KVM: Fix gfn range check in kseg0 tlb faults
  MIPS: KVM: Propagate kseg0/mapped tlb fault errors
  nfs: don't create zero-length requests
  nfsd: Fix race between FREE_STATEID and LOCK
  nfsd: don't return an unhashed lock stateid after taking mutex
  drm/i915: Don't complain about lack of ACPI video bios
  iommu/exynos: Suppress unbinding to prevent system failure
  iommu/vt-d: Return error code in domain_context_mapping_one()
  iommu/amd: Handle IOMMU_DOMAIN_DMA in ops->domain_free call-back
  iommu/amd: Init unity mappings only for dma_ops domains
  iommu/amd: Update Alias-DTE in update_device_table()
  audit: fix a double fetch in audit_log_single_execve_arg()
  ARM: dts: sunxi: Add a startup delay for fixed regulator enabled phys
  netlabel: add address family checks to netlbl_{sock,req}_delattr()
  w1:omap_hdq: fix regression
  drm/amdgpu: add a delay 

[Kernel-packages] [Bug 1606786] Re: in Ubuntu16.10: Hit on Call traces and system goes down when transactional memory tests are running in 32TB Brazos system

[bugproxy]

** Tags removed: verification-needed-xenial
** Tags added: verification-done

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

Title:
  in Ubuntu16.10: Hit on Call traces  and system goes down when
  transactional memory  tests are running in 32TB Brazos system

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:
  == Comment: #0 - Praveen K. Pandey  - 2016-07-16 
14:21:39 ==
  ---Problem Description---
   In Ubuntu16.10 Call traces and unrecoverable exception occurs when 
Transactional memory tests are executed in 32TB system.

  Steps to reproduce:
   
  1- Download tm tests from the link - 
'http://ozlabs.au.ibm.com/~mikey/tm-test-le.tar.gz' 

  2- untar tm-test-le.tar.gz; make clean; make; ./runtests.sh

  The system gives below call traces and goes down. [Not able to do ssh
  and the console gets hung]

  LOG:

  Running ./htm_demo
  Starting 6144 worker threads, 5 loops
  --
  --
  [  438.064162] CFAR: c0008d18 SOFTE: 0

  
  PACATMSCRATCH: 80029033   

  
  GPR00: c0111028 c5f82e36f4b0 c15b5d00 

  
  GPR04: c0b28863 0001 c1755d00 00018748

  
  GPR08: 04f0 f5257d14 01fab980 0005

  
  GPR12: 0500 cbc9dd00 3ffcf5fa 0100

  
  GPR16:  c1faba7898e8 0001 c3f9865bf804

  
  GPR20: 0003 c01638b0 0001 00661a113a10

  
  GPR24:  c5f82e9f2060 01fab980 c15eaa60

  
  GPR28: c0f9e900 009e c15eaa60 c1faba79e900

  
  [  438.064303] NIP [c00a1ba4] kvmppc_interrupt_hv+0x28/0x15c  

  
  [  438.064315] LR [c0111028] trigger_load_balance+0x58/0x340  

  
  [  438.064323] Call Trace:

  
  [  438.064330] [c5f82e36f4b0] [c0111028] 
trigger_load_balance+0x58/0x340 (unreliable)
   
  [  438.064346] [c5f82e36f4f0] [c00f9ee4] 
scheduler_tick+0x104/0x180  
   
  [  438.064360] [c5f82e36f550] [c014c128] 
update_process_times+0x78/0xa0  
   
  [  438.064378] [c5f82e36f580] [c0163818] 
tick_sched_handle.isra.6+0x48/0xe0  
   
  [  438.064392] [c5f82e36f5c0] [c0163914] 
tick_sched_timer+0x64/0xd0  
   
  [  438.064404] [c5f82e36f600] [c014cbd4] 
__hrtimer_run_queues+0x124/0x450
   
  [  438.064418] [c5f82e36f690] [c014dbfc] 
hrtimer_interrupt+0xec/0x2c0
   
  [  438.064431] [c5f82e36f750] [c001f5bc] 
__timer_interrupt+0x8c/0x290
   

[Kernel-packages] [Bug 1615665] Re: Enable virtual scsi server driver for Power

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2016-August/079614.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/1615665

Title:
  Enable virtual scsi server driver for Power

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

Bug description:
  Once Canonical updates to the 4.8 kernel, the following kernel options
  need to be enabled for this feature:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1615665/+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 1615665] Re: Enable virtual scsi server driver for Power

[Tim Gardner]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
 Assignee: Taco Screen team (taco-screen-team)
   Status: New

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

** Changed in: linux (Ubuntu Yakkety)
   Status: New => Fix Released

** Changed in: linux (Ubuntu Yakkety)
 Assignee: Taco Screen team (taco-screen-team) => (unassigned)

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

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

Title:
  Enable virtual scsi server driver for Power

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

Bug description:
  Once Canonical updates to the 4.8 kernel, the following kernel options
  need to be enabled for this feature:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1615665/+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 1615681] Re: BUG: unable to handle kernel paging request at ffff820504022108

[Neil]

it was running on ubuntu server and cannot run apport-collect, I
attached the kernel log

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

Title:
  BUG: unable to handle kernel paging request at 820504022108

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We get this kernel panic while running trusty with 3.19.0-26-generic. 
  It seems there is a bug in nf_nat module, I got kdump, if needed, I will 
upload.

  [702076.560806] BUG: unable to handle kernel paging request at 
820504022108
  [702076.564428] IP: [] nf_nat_setup_info+0x236/0x360 
[nf_nat]
  [702076.567971] PGD 0 
  [702076.571349] Oops: 0002 [#1] SMP 
  [702076.574656] Modules linked in: xt_nat iptable_nat nf_nat_ipv4 sch_sfq 
sch_htb xt_comment xt_iprange xt_physdev act_police cls_u32 sch_ingress 
ebt_dnat ebt_ip ebtable_nat ebt_arp veth xt_conntrack nbd nf_conntrack_netlink 
xt_TCPMSS xt_CT xt_set ip_set_hash_net ip_set nfnetlink iptable_raw 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter netconsole 
configfs xt_CHECKSUM xt_tcpudp iptable_mangle ip_tables x_tables bonding 
intel_rapl(E) iosf_mbi x86_pkg_temp_thermal(E) nf_nat intel_powerclamp(E) 
nf_conntrack_pptp nf_conntrack_proto_gre coretemp(E) br_netfilter 
crct10dif_pclmul ipmi_ssif(E) crc32_pclmul ghash_clmulni_intel aesni_intel 
bridge stp aes_x86_64 llc lrw ipmi_devintf(E) nf_conntrack_ipv4 gf128mul 
nf_defrag_ipv4 glue_helper ablk_helper cryptd mxm_wmi(E) dcdbas(E) sb_edac(E) 
mei_me(E)
  [702076.613908]  nf_conntrack mei(E) lpc_ich(E) edac_core(E) drbd(OE) 
ipmi_si(E) ipmi_msghandler 8250_fintek(E) shpchp(E) vhost_net vhost 
acpi_power_meter(E) macvtap wmi(E) macvlan mac_hid(E) kvm_intel kvm lp xfs 
parport libcrc32c ahci megaraid_sas(E) libahci tg3(E) ixgbe(OE) dca(E) vxlan 
ip6_udp_tunnel udp_tunnel ptp pps_core
  [702076.638776] CPU: 19 PID: 0 Comm: swapper/19 Tainted: G   OE  
3.19.0-26-generic #28~14.04.1
  [702076.649826] Hardware name: Dell Inc. PowerEdge R730/0WCJNT, BIOS 2.1.5 
04/11/2016
  [702076.66] task: 883011c49d70 ti: 881812224000 task.ti: 
881812224000
  [702076.672654] RIP: 0010:[]  [] 
nf_nat_setup_info+0x236/0x360 [nf_nat]
  [702076.684662] RSP: 0018:88301eb235b8  EFLAGS: 00010286
  [702076.690647] RAX: 882fbcd21700 RBX: 882f17b1bd40 RCX: 
820504022100
  [702076.702499] RDX: 88180fb7f038 RSI: 3637ced5 RDI: 
c04a04a0
  [702076.714455] RBP: 88301eb23668 R08:  R09: 
88301eb235b8
  [702076.726823] R10: 88301eb23560 R11: 88300eeb8000 R12: 
0006fe07
  [702076.739167] R13:  R14: 81cda040 R15: 
88301eb23678
  [702076.751481] FS:  () GS:88301eb2() 
knlGS:
  [702076.763823] CS:  0010 DS:  ES:  CR0: 80050033
  [702076.770007] CR2: 820504022108 CR3: 01c16000 CR4: 
001427e0
  [702076.782162] Stack:
  [702076.788035]  2755e673  a402c68b0002259b 

  [702076.799835]  00065000 2755e673  
a402c68b0002259b
  [702076.811642]   00065000 88300db05800 
8830001b0e70
  [702076.823573] Call Trace:
  [702076.829377]   
  [702076.829447] 
  [702076.835069]  [] __nf_nat_alloc_null_binding+0x52/0x80 
[nf_nat]
  [702076.846350]  [] nf_nat_alloc_null_binding+0x21/0x30 
[nf_nat]
  [702076.857721]  [] nf_nat_ipv4_fn+0x1dd/0x230 [nf_nat_ipv4]
  [702076.863548]  [] ? iptable_nat_ipv4_fn+0x20/0x20 
[iptable_nat]
  [702076.874933]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.886328]  [] nf_nat_ipv4_out+0x48/0xf0 [nf_nat_ipv4]
  [702076.892120]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.903384]  [] iptable_nat_ipv4_out+0x15/0x20 
[iptable_nat]
  [702076.914648]  [] nf_iterate+0x9a/0xb0
  [702076.920275]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.931324]  [] nf_hook_slow+0x74/0x130
  [702076.936913]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.947932]  [] br_nf_post_routing+0x283/0x370 
[br_netfilter]
  [702076.959286]  [] ? deliver_clone+0x60/0x60 [bridge]
  [702076.965049]  [] ? deliver_clone+0x60/0x60 [bridge]
  [702076.970612]  [] nf_iterate+0x9a/0xb0
  [702076.976050]  [] ? deliver_clone+0x60/0x60 [bridge]
  [702076.981437]  [] nf_hook_slow+0x74/0x130
  [702076.986715]  [] ? deliver_clone+0x60/0x60 [bridge]
  [702076.992071]  [] ? br_flood+0x160/0x160 [bridge]
  [702076.997487]  [] br_forward_finish+0x52/0x60 [bridge]
  [702077.002855]  [] br_nf_forward_finish+0xcb/0x1d0 
[br_netfilter]
  [702077.013278]  [] br_nf_forward_ip+0x22c/0x400 
[br_netfilter]
  [702077.023700]  [] ? br_flood+0x160/0x160 [bridge]
  [702077.029033]  [] ? br_flood+0x160/0x160 [bridge]
  [702077.034166]  [] 

[Kernel-packages] [Bug 1614790] Re: Resume after suspend fails

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc3

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

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

Title:
  Resume after suspend fails

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Laptop suspends, but resume simply boots the computer from the start.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  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:  tehek  3193 F pulseaudio
   /dev/snd/controlC1:  tehek  3193 F pulseaudio
  CurrentDesktop: MATE
  Date: Thu Aug 18 18:21:06 2016
  HibernationDevice: RESUME=UUID=7b704486-5dd0-44b3-aebf-952c470c8917
  InstallationDate: Installed on 2016-07-15 (34 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: Sony Corporation VGN-NW130J
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=cac7c7ba-cd12-47de-abf6-bfe10f805a63 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 08/27/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0180Y4
  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.:bvrR0180Y4:bd08/27/2009:svnSonyCorporation:pnVGN-NW130J:pvrC601D1HP:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VGN-NW130J
  dmi.product.version: C601D1HP
  dmi.sys.vendor: Sony Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1614790/+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 1483343] Re: NMI watchdog: BUG: soft lockup errors when we execute lock_torture_wr tests

[Joseph Salisbury]

** Changed in: linux (Ubuntu Vivid)
   Status: In Progress => 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/1483343

Title:
  NMI watchdog: BUG: soft lockup errors when we execute lock_torture_wr
  tests

Status in linux package in Ubuntu:
  Triaged
Status in linux-lts-xenial package in Ubuntu:
  Triaged
Status in linux source package in Vivid:
  Incomplete

Bug description:
  ---Problem Description---
  NMI watchdog: BUG: soft lockup errors when we execute lock_torture_wr tests

  ---uname output---
  Linux alp15 3.19.0-18-generic #18~14.04.1-Ubuntu SMP Wed May 20 09:40:36 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P8 

  ---Steps to Reproduce---
  Install a P8 Power VM LPAR with Ubuntu 14.04.2 ISO.
  Then install the Ubuntu 14.04.3 kernel on the same and reboot.
  Then compile and build the LTP latest test suites on the same.

  root@alp15:~# tar -xvf ltp-full-20150420.tar.bz2
  root@alp15:~# cd ltp-full-20150420/
  root@alp15:~/ltp-full-20150420# ls
  aclocal.m4  configure execltp.in  install-sh  Makefile  
READMErunltplite.shtestcasesutils
  autom4te.cache  configure.ac  IDcheck.sh  lib Makefile.release  
README.kernel_config  runtest  testscripts  ver_linux
  config.guessCOPYING   include ltpmenu missing   
runalltests.shscenario_groups  TODO VERSION
  config.sub  doc   INSTALL m4  pan   
runltpscripts  tools
  root@alp15:~/ltp-full-20150420# ./configure
  root@alp15:~/ltp-full-20150420# make
  root@alp15:~/ltp-full-20150420# make install

  root@alp15:/opt/ltp/testcases/bin# ./lock_torture.sh
  lock_torture 1 TINFO : estimate time 6.00 min
  lock_torture 1 TINFO : spin_lock: running 60 sec...

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034386] NMI watchdog: BUG: soft lockup - CPU#10 stuck 
for 21s! [lock_torture_wr:2337]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034389] NMI watchdog: BUG: soft lockup - CPU#6 stuck for 
22s! [lock_torture_wr:2331]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034394] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 
22s! [lock_torture_wr:2339]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034396] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 
22s! [lock_torture_wr:2346]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034398] NMI watchdog: BUG: soft lockup - CPU#7 stuck for 
21s! [lock_torture_wr:2334]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034410] NMI watchdog: BUG: soft lockup - CPU#11 stuck 
for 22s! [lock_torture_wr:2321]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034412] NMI watchdog: BUG: soft lockup - CPU#9 stuck for 
22s! [lock_torture_wr:2333]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.038386] NMI watchdog: BUG: soft lockup - CPU#14 stuck 
for 22s! [lock_torture_wr:2327]

   
  Stack trace output:
   root@alp15:~# dmesg | more
  [ 1717.146881] lock_torture_wr R  running task
  [ 1717.146881]
  [ 1717.146885] 0  2555  2 0x0804
  [ 1717.146887] Call Trace:
  [ 1717.146894] [c00c7551b820] [c00c7551b860] 0xc00c7551b860 
(unreliable)
  [ 1717.146899] [c00c7551b860] [c00b4fb0] __do_softirq+0x220/0x3b0
  [ 1717.146904] [c00c7551b960] [c00b5478] irq_exit+0x98/0x100
  [ 1717.146909] [c00c7551b980] [c001fa54] timer_interrupt+0xa4/0xe0
  [ 1717.146913] [c00c7551b9b0] [c0002758] 
decrementer_common+0x158/0x180
  [ 1717.146922] --- interrupt: 901 at _raw_write_lock+0x68/0xc0
  [ 1717.146922] LR = torture_rwlock_write_lock+0x28/0x40 [locktorture]
  [ 1717.146927] [c00c7551bca0] [c00c7551bcd0] 0xc00c7551bcd0 
(unreliable)
  [ 1717.146934] [c00c7551bcd0] [dd4810b8] 
torture_rwlock_write_lock+0x28/0x40 [locktorture]
  [ 1717.146939] [c00c7551bcf0] [dd480578] 
lock_torture_writer+0x98/0x210 [locktorture]
  [ 1717.146944] [c00c7551bd80] [c00da4d4] kthread+0x114/0x140
  [ 1717.146948] [c00c7551be30] [c000956c] 
ret_from_kernel_thread+0x5c/0x70
  [ 1717.146951] Task dump for CPU 10:
  [ 1717.146953] lock_torture_wr R  running task0  2537  2 
0x0804
  [ 1717.146957] Call Trace:
  [ 1717.146961] [c00c7557b820] [c00c7557b860] 0xc00c7557b860 
(unreliable)
  [ 1717.146966] [c00c7557b860] [c00b4fb0] __do_softirq+0x220/0x3b0
  [ 1717.146970] [c00c7557b960] [c00b5478] irq_exit+0x98/0x100
  [ 1717.146975] [c00c7557b980] [c001fa54] timer_interrupt+0xa4/0xe0
  [ 

[Kernel-packages] [Bug 1614953] Re: hw csum failure when IPv6 interfaces configured in netdev_rx_csum_fault+0x38/0x40

[Andrew McDermott]

I only noticed because I had been experimenting with setting up IPv6
support for Juju. I enabled IPv6 on my router, then insisted that "eth0"
got an IP address in ENI and only then did I notice the messages. This
has only been a recent experiment so no evidence for whether this
happened as part of any upgrade.

I can try the latest upstream kernel but it won't be for a day or two.

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

Title:
  hw csum failure when IPv6 interfaces configured in
  netdev_rx_csum_fault+0x38/0x40

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since I started using IPv6 I noticed the following kernel error:

  Thu Aug 18 15:05:01 2016] : hw csum failure
  [Thu Aug 18 15:05:01 2016] CPU: 5 PID: 11086 Comm: Chrome_IOThread Tainted: P 
  OE   4.4.0-34-generic #53-Ubuntu
  [Thu Aug 18 15:05:01 2016] Hardware name: Gigabyte Technology Co., Ltd. To be 
filled by O.E.M./Z77-D3H, BIOS F22 11/14/2013
  [Thu Aug 18 15:05:01 2016]  0286 c05989f2 
8807573dfcd0 813f11b3
  [Thu Aug 18 15:05:01 2016]   0008 
8807573dfce8 8171f6e8
  [Thu Aug 18 15:05:01 2016]  0074 8807573dfd30 
8171639b fe091360
  [Thu Aug 18 15:05:01 2016] Call Trace:
  [Thu Aug 18 15:05:01 2016]  [] dump_stack+0x63/0x90
  [Thu Aug 18 15:05:01 2016]  [] 
netdev_rx_csum_fault+0x38/0x40
  [Thu Aug 18 15:05:01 2016]  [] 
skb_copy_and_csum_datagram_msg+0xeb/0x100
  [Thu Aug 18 15:05:01 2016]  [] udpv6_recvmsg+0x233/0x670
  [Thu Aug 18 15:05:01 2016]  [] inet_recvmsg+0x7e/0xb0
  [Thu Aug 18 15:05:01 2016]  [] sock_recvmsg+0x3b/0x50
  [Thu Aug 18 15:05:01 2016]  [] SYSC_recvfrom+0xe1/0x160
  [Thu Aug 18 15:05:01 2016]  [] ? wake_up_q+0x70/0x70
  [Thu Aug 18 15:05:01 2016]  [] SyS_recvfrom+0xe/0x10
  [Thu Aug 18 15:05:01 2016]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71

  It repeats periodically:

  $ dmesg -T | grep 'hw csum failure' | wc -l
  201

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 19 13:47:54 2016
  HibernationDevice: RESUME=UUID=066c8903-7f5e-43d5-b48f-76d33c4558f2
  InstallationDate: Installed on 2016-04-24 (116 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/rootpool-rootvol ro intel_iommu=on
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF22:bd11/14/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1614953/+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 1604995] Re: NVMe stress test fails after 12 hours on Ubuntu 16.04

[bugproxy]

--- Comment From gbert...@br.ibm.com 2016-08-22 10:51 EDT---
(In reply to comment #53)
> This bug is awaiting verification that the kernel in -proposed solves the
> problem. Please test the kernel and update this bug with the results. If the
> problem is solved, change the tag 'verification-needed-xenial' to
> 'verification-done-xenial'.
>
> If verification is not done by 5 working days from today, this fix will be
> dropped from the source code, and this bug will be closed.
>
> See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
> enable and use -proposed. Thank you!

I have verified that with -proposed kernel nvme disk will no longer be
identified as AHDI partition, preventing the bad request from being
sent.  Marking as verified and changing to accepted.

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

Title:
  NVMe stress test fails after 12 hours on Ubuntu 16.04

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

Bug description:
   State: Open by: mdate on 21 June 2016 10:22:28 

  Stress testing for perfromance is being done in preparation for the the 
Tencent PoC Sort Competition using the attached per scripts.  The system either 
hangs, or the NVMe goes offline after 12 hours or so.
  The nvme drives are set up in a RAID 0 config.  The script is run like this:

  ./perf_nvme_fio2.sh nvme_jobfile_raid0_huawei

  mdate (md...@pezman.austin.ibm.com) added native attachment 
/opt/IBM/WebSphere/AppServer/profiles/cqweb/temp/ausratsrv5Node01/server1/TeamEAR/cqweb.war/perf_nvme_fio2.sh
 on 2016-06-21 10:22:28
  mdate (md...@pezman.austin.ibm.com) added native attachment 
/opt/IBM/WebSphere/AppServer/profiles/cqweb/temp/ausratsrv5Node01/server1/TeamEAR/cqweb.war/nvme_jobfile_raid0_huawei
 on 2016-06-21 10:22:28

  == Comment: #48 - Gabriel Krisman Bertazi  - 2016-07-18 12:33:13 ==
  Hi, 

  We need to apply the following patch to the Ubuntu kernel to prevent
  wrongly identification of ATARI partitions, as mentioned in the commit
  log.

  It still didn't make to Linus tree, but Jens Axboe already approved it
  on linux-block.

  https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-
  block.git/commit/?h=for-4.8/core

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

[Brad Figg]

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

apport-collect 1615681

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

Title:
  BUG: unable to handle kernel paging request at 820504022108

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We get this kernel panic while running trusty with 3.19.0-26-generic. 
  It seems there is a bug in nf_nat module, I got kdump, if needed, I will 
upload.

  [702076.560806] BUG: unable to handle kernel paging request at 
820504022108
  [702076.564428] IP: [] nf_nat_setup_info+0x236/0x360 
[nf_nat]
  [702076.567971] PGD 0 
  [702076.571349] Oops: 0002 [#1] SMP 
  [702076.574656] Modules linked in: xt_nat iptable_nat nf_nat_ipv4 sch_sfq 
sch_htb xt_comment xt_iprange xt_physdev act_police cls_u32 sch_ingress 
ebt_dnat ebt_ip ebtable_nat ebt_arp veth xt_conntrack nbd nf_conntrack_netlink 
xt_TCPMSS xt_CT xt_set ip_set_hash_net ip_set nfnetlink iptable_raw 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter netconsole 
configfs xt_CHECKSUM xt_tcpudp iptable_mangle ip_tables x_tables bonding 
intel_rapl(E) iosf_mbi x86_pkg_temp_thermal(E) nf_nat intel_powerclamp(E) 
nf_conntrack_pptp nf_conntrack_proto_gre coretemp(E) br_netfilter 
crct10dif_pclmul ipmi_ssif(E) crc32_pclmul ghash_clmulni_intel aesni_intel 
bridge stp aes_x86_64 llc lrw ipmi_devintf(E) nf_conntrack_ipv4 gf128mul 
nf_defrag_ipv4 glue_helper ablk_helper cryptd mxm_wmi(E) dcdbas(E) sb_edac(E) 
mei_me(E)
  [702076.613908]  nf_conntrack mei(E) lpc_ich(E) edac_core(E) drbd(OE) 
ipmi_si(E) ipmi_msghandler 8250_fintek(E) shpchp(E) vhost_net vhost 
acpi_power_meter(E) macvtap wmi(E) macvlan mac_hid(E) kvm_intel kvm lp xfs 
parport libcrc32c ahci megaraid_sas(E) libahci tg3(E) ixgbe(OE) dca(E) vxlan 
ip6_udp_tunnel udp_tunnel ptp pps_core
  [702076.638776] CPU: 19 PID: 0 Comm: swapper/19 Tainted: G   OE  
3.19.0-26-generic #28~14.04.1
  [702076.649826] Hardware name: Dell Inc. PowerEdge R730/0WCJNT, BIOS 2.1.5 
04/11/2016
  [702076.66] task: 883011c49d70 ti: 881812224000 task.ti: 
881812224000
  [702076.672654] RIP: 0010:[]  [] 
nf_nat_setup_info+0x236/0x360 [nf_nat]
  [702076.684662] RSP: 0018:88301eb235b8  EFLAGS: 00010286
  [702076.690647] RAX: 882fbcd21700 RBX: 882f17b1bd40 RCX: 
820504022100
  [702076.702499] RDX: 88180fb7f038 RSI: 3637ced5 RDI: 
c04a04a0
  [702076.714455] RBP: 88301eb23668 R08:  R09: 
88301eb235b8
  [702076.726823] R10: 88301eb23560 R11: 88300eeb8000 R12: 
0006fe07
  [702076.739167] R13:  R14: 81cda040 R15: 
88301eb23678
  [702076.751481] FS:  () GS:88301eb2() 
knlGS:
  [702076.763823] CS:  0010 DS:  ES:  CR0: 80050033
  [702076.770007] CR2: 820504022108 CR3: 01c16000 CR4: 
001427e0
  [702076.782162] Stack:
  [702076.788035]  2755e673  a402c68b0002259b 

  [702076.799835]  00065000 2755e673  
a402c68b0002259b
  [702076.811642]   00065000 88300db05800 
8830001b0e70
  [702076.823573] Call Trace:
  [702076.829377]   
  [702076.829447] 
  [702076.835069]  [] __nf_nat_alloc_null_binding+0x52/0x80 
[nf_nat]
  [702076.846350]  [] nf_nat_alloc_null_binding+0x21/0x30 
[nf_nat]
  [702076.857721]  [] nf_nat_ipv4_fn+0x1dd/0x230 [nf_nat_ipv4]
  [702076.863548]  [] ? iptable_nat_ipv4_fn+0x20/0x20 
[iptable_nat]
  [702076.874933]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.886328]  [] nf_nat_ipv4_out+0x48/0xf0 [nf_nat_ipv4]
  [702076.892120]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.903384]  [] iptable_nat_ipv4_out+0x15/0x20 
[iptable_nat]
  [702076.914648]  [] nf_iterate+0x9a/0xb0
  [702076.920275]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.931324]  [] nf_hook_slow+0x74/0x130
  [702076.936913]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.947932]  [] br_nf_post_routing+0x283/0x370 
[br_netfilter]
  [702076.959286]  [] ? deliver_clone+0x60/0x60 [bridge]
  [702076.965049]  [] ? deliver_clone+0x60/0x60 [bridge]
  [702076.970612]  [] nf_iterate+0x9a/0xb0
  [702076.976050]  [] ? deliver_clone+0x60/0x60 [bridge]
  [702076.981437]  [] nf_hook_slow+0x74/0x130
  [702076.986715]  [] ? deliver_clone+0x60/0x60 [bridge]
  [702076.992071]  [] ? 

[Kernel-packages] [Bug 1615681] [NEW] BUG: unable to handle kernel paging request at ffff820504022108

[Neil]

Public bug reported:

We get this kernel panic while running trusty with 3.19.0-26-generic. 
It seems there is a bug in nf_nat module, I got kdump, if needed, I will upload.

[702076.560806] BUG: unable to handle kernel paging request at 820504022108
[702076.564428] IP: [] nf_nat_setup_info+0x236/0x360 [nf_nat]
[702076.567971] PGD 0 
[702076.571349] Oops: 0002 [#1] SMP 
[702076.574656] Modules linked in: xt_nat iptable_nat nf_nat_ipv4 sch_sfq 
sch_htb xt_comment xt_iprange xt_physdev act_police cls_u32 sch_ingress 
ebt_dnat ebt_ip ebtable_nat ebt_arp veth xt_conntrack nbd nf_conntrack_netlink 
xt_TCPMSS xt_CT xt_set ip_set_hash_net ip_set nfnetlink iptable_raw 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter netconsole 
configfs xt_CHECKSUM xt_tcpudp iptable_mangle ip_tables x_tables bonding 
intel_rapl(E) iosf_mbi x86_pkg_temp_thermal(E) nf_nat intel_powerclamp(E) 
nf_conntrack_pptp nf_conntrack_proto_gre coretemp(E) br_netfilter 
crct10dif_pclmul ipmi_ssif(E) crc32_pclmul ghash_clmulni_intel aesni_intel 
bridge stp aes_x86_64 llc lrw ipmi_devintf(E) nf_conntrack_ipv4 gf128mul 
nf_defrag_ipv4 glue_helper ablk_helper cryptd mxm_wmi(E) dcdbas(E) sb_edac(E) 
mei_me(E)
[702076.613908]  nf_conntrack mei(E) lpc_ich(E) edac_core(E) drbd(OE) 
ipmi_si(E) ipmi_msghandler 8250_fintek(E) shpchp(E) vhost_net vhost 
acpi_power_meter(E) macvtap wmi(E) macvlan mac_hid(E) kvm_intel kvm lp xfs 
parport libcrc32c ahci megaraid_sas(E) libahci tg3(E) ixgbe(OE) dca(E) vxlan 
ip6_udp_tunnel udp_tunnel ptp pps_core
[702076.638776] CPU: 19 PID: 0 Comm: swapper/19 Tainted: G   OE  
3.19.0-26-generic #28~14.04.1
[702076.649826] Hardware name: Dell Inc. PowerEdge R730/0WCJNT, BIOS 2.1.5 
04/11/2016
[702076.66] task: 883011c49d70 ti: 881812224000 task.ti: 
881812224000
[702076.672654] RIP: 0010:[]  [] 
nf_nat_setup_info+0x236/0x360 [nf_nat]
[702076.684662] RSP: 0018:88301eb235b8  EFLAGS: 00010286
[702076.690647] RAX: 882fbcd21700 RBX: 882f17b1bd40 RCX: 
820504022100
[702076.702499] RDX: 88180fb7f038 RSI: 3637ced5 RDI: 
c04a04a0
[702076.714455] RBP: 88301eb23668 R08:  R09: 
88301eb235b8
[702076.726823] R10: 88301eb23560 R11: 88300eeb8000 R12: 
0006fe07
[702076.739167] R13:  R14: 81cda040 R15: 
88301eb23678
[702076.751481] FS:  () GS:88301eb2() 
knlGS:
[702076.763823] CS:  0010 DS:  ES:  CR0: 80050033
[702076.770007] CR2: 820504022108 CR3: 01c16000 CR4: 
001427e0
[702076.782162] Stack:
[702076.788035]  2755e673  a402c68b0002259b 

[702076.799835]  00065000 2755e673  
a402c68b0002259b
[702076.811642]   00065000 88300db05800 
8830001b0e70
[702076.823573] Call Trace:
[702076.829377]   
[702076.829447] 
[702076.835069]  [] __nf_nat_alloc_null_binding+0x52/0x80 
[nf_nat]
[702076.846350]  [] nf_nat_alloc_null_binding+0x21/0x30 
[nf_nat]
[702076.857721]  [] nf_nat_ipv4_fn+0x1dd/0x230 [nf_nat_ipv4]
[702076.863548]  [] ? iptable_nat_ipv4_fn+0x20/0x20 
[iptable_nat]
[702076.874933]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
[702076.886328]  [] nf_nat_ipv4_out+0x48/0xf0 [nf_nat_ipv4]
[702076.892120]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
[702076.903384]  [] iptable_nat_ipv4_out+0x15/0x20 
[iptable_nat]
[702076.914648]  [] nf_iterate+0x9a/0xb0
[702076.920275]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
[702076.931324]  [] nf_hook_slow+0x74/0x130
[702076.936913]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
[702076.947932]  [] br_nf_post_routing+0x283/0x370 
[br_netfilter]
[702076.959286]  [] ? deliver_clone+0x60/0x60 [bridge]
[702076.965049]  [] ? deliver_clone+0x60/0x60 [bridge]
[702076.970612]  [] nf_iterate+0x9a/0xb0
[702076.976050]  [] ? deliver_clone+0x60/0x60 [bridge]
[702076.981437]  [] nf_hook_slow+0x74/0x130
[702076.986715]  [] ? deliver_clone+0x60/0x60 [bridge]
[702076.992071]  [] ? br_flood+0x160/0x160 [bridge]
[702076.997487]  [] br_forward_finish+0x52/0x60 [bridge]
[702077.002855]  [] br_nf_forward_finish+0xcb/0x1d0 
[br_netfilter]
[702077.013278]  [] br_nf_forward_ip+0x22c/0x400 
[br_netfilter]
[702077.023700]  [] ? br_flood+0x160/0x160 [bridge]
[702077.029033]  [] ? br_flood+0x160/0x160 [bridge]
[702077.034166]  [] nf_iterate+0x9a/0xb0
[702077.039182]  [] ? br_flood+0x160/0x160 [bridge]
[702077.044116]  [] nf_hook_slow+0x74/0x130
[702077.048952]  [] ? br_flood+0x160/0x160 [bridge]
[702077.053787]  [] __br_forward+0xb0/0xf0 [bridge]
[702077.058482]  [] br_forward+0x93/0xb0 [bridge]
[702077.063064]  [] br_handle_frame_finish+0x13b/0x540 
[bridge]
[702077.071975]  [] br_nf_pre_routing_finish+0x138/0x3e0 
[br_netfilter]
[702077.081089]  [] br_nf_pre_routing+0x2b3/0x67d 
[br_netfilter]
[702077.090349]  [] ? br_handle_local_finish+0x90/0x90 
[bridge]

[Kernel-packages] [Bug 1615681] Re: BUG: unable to handle kernel paging request at ffff820504022108

[Neil]

I attached the kernel log

** Attachment added: "kernel.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1615681/+attachment/4725785/+files/dmesg.201608220924

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

Title:
  BUG: unable to handle kernel paging request at 820504022108

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We get this kernel panic while running trusty with 3.19.0-26-generic. 
  It seems there is a bug in nf_nat module, I got kdump, if needed, I will 
upload.

  [702076.560806] BUG: unable to handle kernel paging request at 
820504022108
  [702076.564428] IP: [] nf_nat_setup_info+0x236/0x360 
[nf_nat]
  [702076.567971] PGD 0 
  [702076.571349] Oops: 0002 [#1] SMP 
  [702076.574656] Modules linked in: xt_nat iptable_nat nf_nat_ipv4 sch_sfq 
sch_htb xt_comment xt_iprange xt_physdev act_police cls_u32 sch_ingress 
ebt_dnat ebt_ip ebtable_nat ebt_arp veth xt_conntrack nbd nf_conntrack_netlink 
xt_TCPMSS xt_CT xt_set ip_set_hash_net ip_set nfnetlink iptable_raw 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter netconsole 
configfs xt_CHECKSUM xt_tcpudp iptable_mangle ip_tables x_tables bonding 
intel_rapl(E) iosf_mbi x86_pkg_temp_thermal(E) nf_nat intel_powerclamp(E) 
nf_conntrack_pptp nf_conntrack_proto_gre coretemp(E) br_netfilter 
crct10dif_pclmul ipmi_ssif(E) crc32_pclmul ghash_clmulni_intel aesni_intel 
bridge stp aes_x86_64 llc lrw ipmi_devintf(E) nf_conntrack_ipv4 gf128mul 
nf_defrag_ipv4 glue_helper ablk_helper cryptd mxm_wmi(E) dcdbas(E) sb_edac(E) 
mei_me(E)
  [702076.613908]  nf_conntrack mei(E) lpc_ich(E) edac_core(E) drbd(OE) 
ipmi_si(E) ipmi_msghandler 8250_fintek(E) shpchp(E) vhost_net vhost 
acpi_power_meter(E) macvtap wmi(E) macvlan mac_hid(E) kvm_intel kvm lp xfs 
parport libcrc32c ahci megaraid_sas(E) libahci tg3(E) ixgbe(OE) dca(E) vxlan 
ip6_udp_tunnel udp_tunnel ptp pps_core
  [702076.638776] CPU: 19 PID: 0 Comm: swapper/19 Tainted: G   OE  
3.19.0-26-generic #28~14.04.1
  [702076.649826] Hardware name: Dell Inc. PowerEdge R730/0WCJNT, BIOS 2.1.5 
04/11/2016
  [702076.66] task: 883011c49d70 ti: 881812224000 task.ti: 
881812224000
  [702076.672654] RIP: 0010:[]  [] 
nf_nat_setup_info+0x236/0x360 [nf_nat]
  [702076.684662] RSP: 0018:88301eb235b8  EFLAGS: 00010286
  [702076.690647] RAX: 882fbcd21700 RBX: 882f17b1bd40 RCX: 
820504022100
  [702076.702499] RDX: 88180fb7f038 RSI: 3637ced5 RDI: 
c04a04a0
  [702076.714455] RBP: 88301eb23668 R08:  R09: 
88301eb235b8
  [702076.726823] R10: 88301eb23560 R11: 88300eeb8000 R12: 
0006fe07
  [702076.739167] R13:  R14: 81cda040 R15: 
88301eb23678
  [702076.751481] FS:  () GS:88301eb2() 
knlGS:
  [702076.763823] CS:  0010 DS:  ES:  CR0: 80050033
  [702076.770007] CR2: 820504022108 CR3: 01c16000 CR4: 
001427e0
  [702076.782162] Stack:
  [702076.788035]  2755e673  a402c68b0002259b 

  [702076.799835]  00065000 2755e673  
a402c68b0002259b
  [702076.811642]   00065000 88300db05800 
8830001b0e70
  [702076.823573] Call Trace:
  [702076.829377]   
  [702076.829447] 
  [702076.835069]  [] __nf_nat_alloc_null_binding+0x52/0x80 
[nf_nat]
  [702076.846350]  [] nf_nat_alloc_null_binding+0x21/0x30 
[nf_nat]
  [702076.857721]  [] nf_nat_ipv4_fn+0x1dd/0x230 [nf_nat_ipv4]
  [702076.863548]  [] ? iptable_nat_ipv4_fn+0x20/0x20 
[iptable_nat]
  [702076.874933]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.886328]  [] nf_nat_ipv4_out+0x48/0xf0 [nf_nat_ipv4]
  [702076.892120]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.903384]  [] iptable_nat_ipv4_out+0x15/0x20 
[iptable_nat]
  [702076.914648]  [] nf_iterate+0x9a/0xb0
  [702076.920275]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.931324]  [] nf_hook_slow+0x74/0x130
  [702076.936913]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.947932]  [] br_nf_post_routing+0x283/0x370 
[br_netfilter]
  [702076.959286]  [] ? deliver_clone+0x60/0x60 [bridge]
  [702076.965049]  [] ? deliver_clone+0x60/0x60 [bridge]
  [702076.970612]  [] nf_iterate+0x9a/0xb0
  [702076.976050]  [] ? deliver_clone+0x60/0x60 [bridge]
  [702076.981437]  [] nf_hook_slow+0x74/0x130
  [702076.986715]  [] ? deliver_clone+0x60/0x60 [bridge]
  [702076.992071]  [] ? br_flood+0x160/0x160 [bridge]
  [702076.997487]  [] br_forward_finish+0x52/0x60 [bridge]
  [702077.002855]  [] br_nf_forward_finish+0xcb/0x1d0 
[br_netfilter]
  [702077.013278]  [] br_nf_forward_ip+0x22c/0x400 
[br_netfilter]
  [702077.023700]  [] ? br_flood+0x160/0x160 [bridge]
  [702077.029033]  [] ? br_flood+0x160/0x160 [bridge]
  

[Kernel-packages] [Bug 1614887] Re: Lage samba file transfers block btrfs to hung task

[Joseph Salisbury]

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc3


** Tags added: kernel-da-key needs-bisect

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

Title:
  Lage samba file transfers block btrfs to hung task

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  this bug occurs when user transfer big files ~1gb to the samba server
  on xenial/wily

  on wily this problem was NOT showing with samba 4.2 (i guess) until
  samba was also upgraded to 4.3.

  the samba runs on a KVM VM

  samba version: 4.3.9+dfsg-0ubuntu0.16.04.

  
  [   30.171211] zram: Added device: zram0
  [   30.356301] zram0: detected capacity change from 0 to 1518252032
  [   30.668855] Adding 1482664k swap on /dev/zram0.  Priority:5 extents:1 
across:1482664k SSFS
  [   35.608271] [drm:qxl_enc_commit [qxl]] *ERROR* head number too large or 
missing monitors config: c9e3, 0
  [   45.008364] Non-volatile memory driver v1.3
  [65636.820111] INFO: task btrfs-cleaner:631 blocked for more than 120 seconds.
  [65636.820128]   Not tainted 4.4.0-36-generic #55-Ubuntu
  [65636.820129] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [65636.820131] btrfs-cleaner   D 88005ae93ce8 0   631  2 
0x
  [65636.820137]  88005ae93ce8 8800bbb86400 8801b0dc3e80 
8801b0dc2580
  [65636.820139]  88005ae94000 8801851971f0 880185197000 
8801851971f0
  [65636.820141]  0001 88005ae93d00 81829ec5 
8801b7fc4000
  [65636.820143] Call Trace:
  [65636.820182]  [] schedule+0x35/0x80
  [65636.820360]  [] wait_current_trans.isra.21+0xd3/0x120 
[btrfs]
  [65636.820395]  [] ? wake_atomic_t_function+0x60/0x60
  [65636.820409]  [] start_transaction+0x2c5/0x4b0 [btrfs]
  [65636.820434]  [] btrfs_start_transaction+0x18/0x20 [btrfs]
  [65636.820452]  [] btrfs_drop_snapshot+0x7f/0x830 [btrfs]
  [65636.820454]  [] ? __schedule+0x3b6/0xa30
  [65636.820467]  [] 
btrfs_clean_one_deleted_snapshot+0xb2/0x100 [btrfs]
  [65636.820480]  [] cleaner_kthread+0xcf/0x220 [btrfs]
  [65636.820493]  [] ? check_leaf+0x360/0x360 [btrfs]
  [65636.820497]  [] kthread+0xd8/0xf0
  [65636.820499]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [65636.820505]  [] ret_from_fork+0x3f/0x70
  [65636.820507]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [65636.820550] INFO: task kworker/u4:1:7760 blocked for more than 120 seconds.
  [65636.820551]   Not tainted 4.4.0-36-generic #55-Ubuntu
  [65636.820558] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [65636.820559] kworker/u4:1D 880008433c48 0  7760  2 
0x
  [65636.820579] Workqueue: btrfs-endio-write btrfs_endio_write_helper [btrfs]
  [65636.820581]  880008433c48 0040 8800b9d98c80 
8801b51a9900
  [65636.820582]  880008434000 8801851941f0 880185194000 
8801851941f0
  [65636.820584]  0001 880008433c60 81829ec5 
8801b7fc4000
  [65636.820586] Call Trace:
  [65636.820588]  [] schedule+0x35/0x80
  [65636.820602]  [] wait_current_trans.isra.21+0xd3/0x120 
[btrfs]
  [65636.820604]  [] ? wake_atomic_t_function+0x60/0x60
  [65636.820620]  [] start_transaction+0x275/0x4b0 [btrfs]
  [65636.820650]  [] btrfs_join_transaction+0x17/0x20 [btrfs]
  [65636.820667]  [] btrfs_finish_ordered_io+0x435/0x650 
[btrfs]
  [65636.820692]  [] finish_ordered_fn+0x15/0x20 [btrfs]
  [65636.820718]  [] btrfs_scrubparity_helper+0xca/0x2f0 
[btrfs]
  [65636.820723]  [] ? try_to_wake_up+0x47/0x3b0
  [65636.820741]  [] btrfs_endio_write_helper+0xe/0x10 [btrfs]
  [65636.820753]  [] process_one_work+0x165/0x480
  [65636.820755]  [] worker_thread+0x4b/0x4c0
  [65636.820757]  [] ? process_one_work+0x480/0x480
  [65636.820758]  [] kthread+0xd8/0xf0
  [65636.820760]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [65636.820761]  [] ret_from_fork+0x3f/0x70
  [65636.820763]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [65636.820770] INFO: task kworker/u4:2:7814 blocked for more than 120 seconds.
  [65636.820771]   Not tainted 4.4.0-36-generic #55-Ubuntu
  [65636.820772] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [65636.820773] kworker/u4:2D 880102027c48 0  7814  2 
0x
  [65636.820848] Workqueue: btrfs-endio-write btrfs_endio_write_helper [btrfs]
  [65636.820850]  880102027c48 0040 8801b51ae400 

[Kernel-packages] [Bug 1614953] Re: hw csum failure when IPv6 interfaces configured in netdev_rx_csum_fault+0x38/0x40

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc3


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

** Tags added: kernel-da-key

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

Title:
  hw csum failure when IPv6 interfaces configured in
  netdev_rx_csum_fault+0x38/0x40

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since I started using IPv6 I noticed the following kernel error:

  Thu Aug 18 15:05:01 2016] : hw csum failure
  [Thu Aug 18 15:05:01 2016] CPU: 5 PID: 11086 Comm: Chrome_IOThread Tainted: P 
  OE   4.4.0-34-generic #53-Ubuntu
  [Thu Aug 18 15:05:01 2016] Hardware name: Gigabyte Technology Co., Ltd. To be 
filled by O.E.M./Z77-D3H, BIOS F22 11/14/2013
  [Thu Aug 18 15:05:01 2016]  0286 c05989f2 
8807573dfcd0 813f11b3
  [Thu Aug 18 15:05:01 2016]   0008 
8807573dfce8 8171f6e8
  [Thu Aug 18 15:05:01 2016]  0074 8807573dfd30 
8171639b fe091360
  [Thu Aug 18 15:05:01 2016] Call Trace:
  [Thu Aug 18 15:05:01 2016]  [] dump_stack+0x63/0x90
  [Thu Aug 18 15:05:01 2016]  [] 
netdev_rx_csum_fault+0x38/0x40
  [Thu Aug 18 15:05:01 2016]  [] 
skb_copy_and_csum_datagram_msg+0xeb/0x100
  [Thu Aug 18 15:05:01 2016]  [] udpv6_recvmsg+0x233/0x670
  [Thu Aug 18 15:05:01 2016]  [] inet_recvmsg+0x7e/0xb0
  [Thu Aug 18 15:05:01 2016]  [] sock_recvmsg+0x3b/0x50
  [Thu Aug 18 15:05:01 2016]  [] SYSC_recvfrom+0xe1/0x160
  [Thu Aug 18 15:05:01 2016]  [] ? wake_up_q+0x70/0x70
  [Thu Aug 18 15:05:01 2016]  [] SyS_recvfrom+0xe/0x10
  [Thu Aug 18 15:05:01 2016]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71

  It repeats periodically:

  $ dmesg -T | grep 'hw csum failure' | wc -l
  201

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 19 13:47:54 2016
  HibernationDevice: RESUME=UUID=066c8903-7f5e-43d5-b48f-76d33c4558f2
  InstallationDate: Installed on 2016-04-24 (116 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/rootpool-rootvol ro intel_iommu=on
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF22:bd11/14/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1614953/+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 1614887] Re: Lage samba file transfers block btrfs to hung task

[Joseph Salisbury]

Also, does the bug go away if you boot back into prior kernel versions?

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

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

Title:
  Lage samba file transfers block btrfs to hung task

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  this bug occurs when user transfer big files ~1gb to the samba server
  on xenial/wily

  on wily this problem was NOT showing with samba 4.2 (i guess) until
  samba was also upgraded to 4.3.

  the samba runs on a KVM VM

  samba version: 4.3.9+dfsg-0ubuntu0.16.04.

  
  [   30.171211] zram: Added device: zram0
  [   30.356301] zram0: detected capacity change from 0 to 1518252032
  [   30.668855] Adding 1482664k swap on /dev/zram0.  Priority:5 extents:1 
across:1482664k SSFS
  [   35.608271] [drm:qxl_enc_commit [qxl]] *ERROR* head number too large or 
missing monitors config: c9e3, 0
  [   45.008364] Non-volatile memory driver v1.3
  [65636.820111] INFO: task btrfs-cleaner:631 blocked for more than 120 seconds.
  [65636.820128]   Not tainted 4.4.0-36-generic #55-Ubuntu
  [65636.820129] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [65636.820131] btrfs-cleaner   D 88005ae93ce8 0   631  2 
0x
  [65636.820137]  88005ae93ce8 8800bbb86400 8801b0dc3e80 
8801b0dc2580
  [65636.820139]  88005ae94000 8801851971f0 880185197000 
8801851971f0
  [65636.820141]  0001 88005ae93d00 81829ec5 
8801b7fc4000
  [65636.820143] Call Trace:
  [65636.820182]  [] schedule+0x35/0x80
  [65636.820360]  [] wait_current_trans.isra.21+0xd3/0x120 
[btrfs]
  [65636.820395]  [] ? wake_atomic_t_function+0x60/0x60
  [65636.820409]  [] start_transaction+0x2c5/0x4b0 [btrfs]
  [65636.820434]  [] btrfs_start_transaction+0x18/0x20 [btrfs]
  [65636.820452]  [] btrfs_drop_snapshot+0x7f/0x830 [btrfs]
  [65636.820454]  [] ? __schedule+0x3b6/0xa30
  [65636.820467]  [] 
btrfs_clean_one_deleted_snapshot+0xb2/0x100 [btrfs]
  [65636.820480]  [] cleaner_kthread+0xcf/0x220 [btrfs]
  [65636.820493]  [] ? check_leaf+0x360/0x360 [btrfs]
  [65636.820497]  [] kthread+0xd8/0xf0
  [65636.820499]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [65636.820505]  [] ret_from_fork+0x3f/0x70
  [65636.820507]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [65636.820550] INFO: task kworker/u4:1:7760 blocked for more than 120 seconds.
  [65636.820551]   Not tainted 4.4.0-36-generic #55-Ubuntu
  [65636.820558] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [65636.820559] kworker/u4:1D 880008433c48 0  7760  2 
0x
  [65636.820579] Workqueue: btrfs-endio-write btrfs_endio_write_helper [btrfs]
  [65636.820581]  880008433c48 0040 8800b9d98c80 
8801b51a9900
  [65636.820582]  880008434000 8801851941f0 880185194000 
8801851941f0
  [65636.820584]  0001 880008433c60 81829ec5 
8801b7fc4000
  [65636.820586] Call Trace:
  [65636.820588]  [] schedule+0x35/0x80
  [65636.820602]  [] wait_current_trans.isra.21+0xd3/0x120 
[btrfs]
  [65636.820604]  [] ? wake_atomic_t_function+0x60/0x60
  [65636.820620]  [] start_transaction+0x275/0x4b0 [btrfs]
  [65636.820650]  [] btrfs_join_transaction+0x17/0x20 [btrfs]
  [65636.820667]  [] btrfs_finish_ordered_io+0x435/0x650 
[btrfs]
  [65636.820692]  [] finish_ordered_fn+0x15/0x20 [btrfs]
  [65636.820718]  [] btrfs_scrubparity_helper+0xca/0x2f0 
[btrfs]
  [65636.820723]  [] ? try_to_wake_up+0x47/0x3b0
  [65636.820741]  [] btrfs_endio_write_helper+0xe/0x10 [btrfs]
  [65636.820753]  [] process_one_work+0x165/0x480
  [65636.820755]  [] worker_thread+0x4b/0x4c0
  [65636.820757]  [] ? process_one_work+0x480/0x480
  [65636.820758]  [] kthread+0xd8/0xf0
  [65636.820760]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [65636.820761]  [] ret_from_fork+0x3f/0x70
  [65636.820763]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [65636.820770] INFO: task kworker/u4:2:7814 blocked for more than 120 seconds.
  [65636.820771]   Not tainted 4.4.0-36-generic #55-Ubuntu
  [65636.820772] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [65636.820773] kworker/u4:2D 880102027c48 0  7814  2 
0x
  [65636.820848] Workqueue: btrfs-endio-write btrfs_endio_write_helper [btrfs]
  [65636.820850]  880102027c48 0040 8801b51ae400 
8801b51a8c80
  [65636.820852]  880102028000 8801851941f0 880185194000 
8801851941f0
  [65636.820853]  0001 880102027c60 81829ec5 
8801b7fc4000
  [65636.820855] Call Trace:
  [65636.820857]  [] schedule+0x35/0x80
  [65636.820877]  [] wait_current_trans.isra.21+0xd3/0x120 
[btrfs]
  [65636.820879]  [] ? 

[Kernel-packages] [Bug 1615200] Re: Can't read battery state

[Joseph Salisbury]

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc3


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

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

Title:
  Can't read battery state

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The laptop's model is HP ENVY m4 Notebook, featuring the latest BIOS
  (F.18)

  This happens roughly once every three sessions, with no obvious
  trigger, thus no way to reproduce but to boot and wait, usually a
  couple of hours. The error displayed on dmesg is the following:

  ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.EC0.MMRD] (Node 
8802468b4f50), AE_AML_INFINITE_LOOP (20150930/psparse-542)
  ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.EC0.RDMB] (Node 
8802468b5938), AE_AML_INFINITE_LOOP (20150930/psparse-542)
  ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.EC0.RDMW] (Node 
8802468b5960), AE_AML_INFINITE_LOOP (20150930/psparse-542)
  ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.EC0.BAT0._BST] 
(Node 8802468b54d8), AE_AML_INFINITE_LOOP (20150930/psparse-542)

  This makes every process that depends on reading battery state hang
  indefinitely, including suspend and shutdown. It is my understanding
  that \_SB.PCI0.LPCB.EC0.MMRD is the PCI Node of Memory Read 32-bit
  double word, and that these other nodes reference it in their
  definitions. In the session I share (dmesg), no event gets registered
  in dmesg for several minutes before these errors. As I said, no
  obvious trigger.

  Also, perhaps related, I find two other ACPI parsing/execution errors
  that repeat on every boot and frequently show on dmesg without any
  visible effect:

  ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.EC0.ACCR] (Node 
8802b68b4ed8), AE_AML_INFINITE_LOOP (20150930/psparse-542)
  ACPI Error: Method parse/execution failed [\_SB.PCI0.ACEL._STA] (Node 
8802b68b90a0), AE_AML_INFINITE_LOOP (20150930/psparse-542)

  I haven't been able to find anything on the first node.

  I have had the same situation on every kernel I've tried on this
  machine, which goes from 3.19 to 4.7. Currently I'm using the
  supported 4.4.0-34 kernel on Ubuntu 16.10.1 LTS.

  Maybe worth mentioning. When disassembling DSDT from IASL I get a
  warning:

  iASL Warning: There were 6 external control methods found during
  disassembly, but additional ACPI tables to resolve these externals
  were not specified. The resulting disassembler output file may not
  compile because the disassembler did not know how many arguments to
  assign to these methods.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1615200/+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 1602724] Re: Ubuntu 16.04 - Full EEH Recovery Support for NVMe devices

[Tim Gardner]

Test kernel at http://people.canonical.com/~rtg/eeh-lp1602724/ with
upstream commit c21377f8366c95440d533edbe47d070f662c62ef ('nvme: Suspend
all queues before deletion') applied.

** Changed in: linux (Ubuntu Xenial)
   Status: Fix Committed => 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/1602724

Title:
  Ubuntu 16.04 - Full EEH Recovery Support for NVMe devices

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

Bug description:
  == Comment: #0 - Heitor Ricardo Alves de Siqueira  - 
2016-07-12 12:54:27 ==
  Current nvme driver in Ubuntu 16.04 kernel does not handle error recovery; we 
are missing some patches from the upstream nvme driver.

  We would like to ask Canonical to cherry pick the following patches for the 
16.04 kernel, if possible:
  * 9396dec916c0 ("nvme: use a work item to submit async event requests")
  * 79f2b358c9ba ("nvme: don't poll the CQ from the kthread")
  * 2d55cd5f511d ("nvme: replace the kthread with a per-device watchdog 
timer")
  * 9bf2b972afea ("NVMe: Fix reset/remove race")
  * c875a7093f04 ("nvme: Avoid reset work on watchdog timer function during 
error recovery")
  * a5229050b69c ("NVMe: Always use MSI/MSI-x interrupts")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602724/+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 1615082] Re: kernel NULL pointer dereference on apparmor profile update

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc3


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

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

Title:
  kernel NULL pointer dereference on apparmor profile update

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've used aa-logprof to find more things out to be added to my custom
  apache2 apparmor file. Since PHP created tons of files in /tmp in the
  form of /tmp/php* I've decided to add this:

  /tmp/php* rw,

  I'm not sure if it caused the problem, but after this
  /etc/init.d/apparmor reload froze and there was the following in the
  output of dmesg command:

  
  [13838.909880] audit: type=1400 audit(1471631019.426:1488): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/apache2" 
pid=23590 comm="apparmor_parser"
  [13838.920067] [ cut here ]
  [13838.920079] WARNING: CPU: 0 PID: 23590 at 
/build/linux-5vkMGy/linux-4.4.0/security/apparmor/label.c:142 
profile_cmp+0xed/0x180()
  [13838.920083] AppArmor WARN profile_cmp: ((!b)): 
  [13838.920085] Modules linked in:
  [13838.920088]  binfmt_misc nf_conntrack_ftp nf_conntrack_irc ip6t_REJECT 
nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables 
ipt_REJECT nf_reject_ipv4 xt_NFLOG nfnetlink_log nfnetlink xt_tcpudp xt_pkttype 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter 
ip_tables x_tables gpio_ich ipmi_devintf coretemp ipmi_ssif kvm dcdbas 
irqbypass i5000_edac serio_raw edac_core lpc_ich joydev input_leds i5k_amb 
ipmi_si 8250_fintek ipmi_msghandler shpchp mac_hid ib_iser rdma_cm iw_cm ib_cm 
ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear ses enclosure amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm 
drm_kms_helper
  [13838.920166]  syscopyarea sysfillrect sysimgblt hid_generic fb_sys_fops 
usbhid uas e1000e ptp hid usb_storage psmouse drm megaraid_sas bnx2 pps_core 
pata_acpi fjes
  [13838.920188] CPU: 0 PID: 23590 Comm: apparmor_parser Not tainted 
4.4.0-34-generic #53-Ubuntu
  [13838.920192] Hardware name: Dell Inc. PowerEdge 1950/0DT097, BIOS 2.7.0 
10/30/2010
  [13838.920195]  0086 88f44738 880128bffc00 
813f11b3
  [13838.920199]  880128bffc48 81cf08e8 880128bffc38 
81081102
  [13838.920204]  8800c8d7d400  000a 

  [13838.920208] Call Trace:
  [13838.920218]  [] dump_stack+0x63/0x90
  [13838.920224]  [] warn_slowpath_common+0x82/0xc0
  [13838.920228]  [] warn_slowpath_fmt+0x5c/0x80
  [13838.920232]  [] ? u32_swap+0x10/0x10
  [13838.920236]  [] profile_cmp+0xed/0x180
  [13838.920239]  [] aa_vec_unique+0x163/0x240
  [13838.920244]  [] __aa_labelset_update_subtree+0x687/0x820
  [13838.920249]  [] ? kzfree+0x2d/0x40
  [13838.920254]  [] aa_replace_profiles+0x59b/0xb70
  [13838.920259]  [] ? __kmalloc+0x22e/0x250
  [13838.920263]  [] policy_update+0x9f/0x1f0
  [13838.920267]  [] profile_replace+0x13/0x20
  [13838.920272]  [] __vfs_write+0x18/0x40
  [13838.920275]  [] vfs_write+0xa9/0x1a0
  [13838.920279]  [] ? do_sys_open+0x1bf/0x2a0
  [13838.920282]  [] SyS_write+0x55/0xc0
  [13838.920288]  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [13838.920291] ---[ end trace a19473a0fd8d9556 ]---
  [13838.920305] BUG: unable to handle kernel NULL pointer dereference at 
0038
  [13838.920475] IP: [] profile_cmp+0x2f/0x180
  [13838.920582] PGD 128a7d067 PUD 12a6be067 PMD 0 
  [13838.920684] Oops:  [#1] SMP 
  [13838.920755] Modules linked in: binfmt_misc nf_conntrack_ftp 
nf_conntrack_irc ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 
ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_NFLOG nfnetlink_log 
nfnetlink xt_tcpudp xt_pkttype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
nf_conntrack iptable_filter ip_tables x_tables gpio_ich ipmi_devintf coretemp 
ipmi_ssif kvm dcdbas irqbypass i5000_edac serio_raw edac_core lpc_ich joydev 
input_leds i5k_amb ipmi_si 8250_fintek 

[Kernel-packages] [Bug 1615507] Re: package linux-image-extra-3.13.0-93-generic 3.13.0-93.140 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Joseph Salisbury]

Are you able to boot the prior kernel version if you select it from the
GRUB menu?

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

** Tags added: kernel-da-key

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

Title:
  package linux-image-extra-3.13.0-93-generic 3.13.0-93.140 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  cant boot up latest kernal

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.13.0-93-generic 3.13.0-93.140
  ProcVersionSignature: Ubuntu 3.19.0-65.73~14.04.1-lowlatency 3.19.8-ckt22
  Uname: Linux 3.19.0-65-lowlatency x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  conrad 2582 F pulseaudio
   /dev/snd/controlC0:  conrad 2582 F pulseaudio
  Date: Fri Aug 19 20:30:14 2016
  DpkgTerminalLog:
   Log started: 2016-08-05  23:30:50
   Log ended: 2016-08-05  23:31:28
   
   Log started: 2016-08-19  20:23:55
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-12-24 (241 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-65-lowlatency 
root=/dev/mapper/ubuntu--studio--vg-root ro nomdmonddf nomdmonisw
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-image-extra-3.13.0-93-generic 3.13.0-93.140 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 22CD
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 93.15
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd05/30/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097510405F1620180:rvnHewlett-Packard:rn22CD:rvr93.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 097510405F1620180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1615507/+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 1615333] Re: S3/resume -> Memory corruption detected in low memory

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc3


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

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

Title:
  S3/resume -> Memory corruption detected in low memory

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Every time, I resume from S3 I get a Memory corruption detected in low
  memory. it's supposed to be a BIOS issue (Bios has been updated to
  latest version)

  Dmesg :

   482.012031] Corrupted low memory at 880067f0 (67f0 phys) = 
2001
  [  482.012041] [ cut here ]
  [  482.012046] WARNING: CPU: 0 PID: 61 at 
/build/linux-5vkMGy/linux-4.4.0/arch/x86/kernel/check.c:141 
check_for_bios_corruption.part.1+0xaf/0x100()
  [  482.012047] Memory corruption detected in low memory
  [  482.012049] Modules linked in: drbg ansi_cprng ctr ccm pci_stub 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) nvidia_uvm(POE) 
nvidia(POE) binfmt_misc arc4 mxm_wmi kvm_amd ath9k kvm ath9k_common ath9k_hw 
joydev input_leds ath snd_hda_codec_realtek mac80211 snd_hda_codec_generic 
snd_hda_intel irqbypass snd_hda_codec cfg80211 crct10dif_pclmul crc32_pclmul 
snd_hda_core aesni_intel snd_hwdep aes_x86_64 lrw gf128mul glue_helper 
ablk_helper cryptd drm snd_pcm serio_raw snd_seq_midi snd_seq_midi_event 
fam15h_power snd_rawmidi snd_seq snd_seq_device snd_timer snd edac_mce_amd 
k10temp edac_core soundcore i2c_piix4 shpchp 8250_fintek tpm_infineon mac_hid 
wmi f71882fg adt7475 hwmon_vid parport_pc ppdev lp parport autofs4 raid10 raid1 
raid0 multipath linear raid456 async_raid6_recov async_memcpy async_pq
  [  482.012083]  async_xor async_tx xor raid6_pq libcrc32c hid_logitech_hidpp 
hid_logitech_dj usbhid hid psmouse r8169 mii ahci libahci fjes
  [  482.012091] CPU: 0 PID: 61 Comm: kworker/0:1 Tainted: P   OE   
4.4.0-34-generic #53-Ubuntu
  [  482.012092] Hardware name: MSI MS-7640/990FXA-GD65 (MS-7640), BIOS V20.5 
06/01/2015
  [  482.012095] Workqueue: events check_corruption
  [  482.012097]  0286 8eb30a27 88041bbefd20 
813f11b3
  [  482.012099]  88041bbefd68 81ca9938 88041bbefd58 
81081102
  [  482.012101]   8801 820fc730 
0001
  [  482.012103] Call Trace:
  [  482.012107]  [] dump_stack+0x63/0x90
  [  482.012110]  [] warn_slowpath_common+0x82/0xc0
  [  482.012112]  [] warn_slowpath_fmt+0x5c/0x80
  [  482.012115]  [] 
check_for_bios_corruption.part.1+0xaf/0x100
  [  482.012117]  [] check_corruption+0x18/0x50
  [  482.012119]  [] process_one_work+0x165/0x480
  [  482.012121]  [] worker_thread+0x4b/0x4c0
  [  482.012123]  [] ? process_one_work+0x480/0x480
  [  482.012125]  [] ? process_one_work+0x480/0x480
  [  482.012127]  [] kthread+0xd8/0xf0
  [  482.012129]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [  482.012131]  [] ret_from_fork+0x3f/0x70
  [  482.012133]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [  482.012134] ---[ end trace e749f67fe945b9d2 ]---

  ---

  System:Host: j-quadcore Kernel: 4.4.0-34-generic x86_64 (64 bit gcc: 
5.3.1)
     Desktop: Gnome 3.18.5 (Gtk 3.18.9-1ubuntu3.1) Distro: Ubuntu 16.04 
xenial
  Machine:   Mobo: MSI model: 990FXA-GD65 (MS-7640) v: 3.0 Bios: American 
Megatrends v: V20.5 date: 06/01/2015
  CPU:   Octa core AMD FX-8320E Eight-Core (-MCP-) cache: 16384 KB
     flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 
55049
     clock speeds: max: 3440 MHz 1: 3440 MHz 2: 3440 MHz 3: 3440 MHz 4: 
3440 MHz 5: 3440 MHz 6: 3440 MHz
     7: 3440 MHz 8: 3440 MHz
  Graphics:  Card: NVIDIA GT200 [GeForce GTX 260] bus-ID: 01:00.0
     Display Server: X.Org 1.18.3 drivers: nvidia (unloaded: 
fbdev,vesa,nouveau)
     Resolution: 1920x1080@60.00hz
     GLX Renderer: GeForce GTX 260/PCIe/SSE2 GLX Version: 3.3.0 NVIDIA 
340.96 Direct Rendering: Yes
  Info:  Processes: 329 Uptime: 1:06 Memory: 4118.7/15997.4MB Init: systemd 
runlevel: 5 Gcc sys: 5.4.0
     Client: Shell (bash 4.3.461) inxi: 2.2.35
  --- 
  ApportVersion: 

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

[bugproxy]

--- Comment From bren...@br.ibm.com 2016-08-22 10:09 EDT---
This is a feature request to enable the IBM VSCSI server for PowerVM. This is a 
new device driver recently accepted upstream and queued for the 4.8 kernel. It 
enables Linux to act as a virtual scsi *server*, allowing other Linux LPARs on 
the same machine to access shared storage via the VSCSI protocol.

** Changed in: ubuntu
 Assignee: (unassigned) => Taco Screen team (taco-screen-team)

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

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

Title:
  Enable virtual scsi server driver for Power

Status in linux package in Ubuntu:
  New

Bug description:
  Once Canonical updates to the 4.8 kernel, the following kernel options
  need to be enabled for this feature:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1615665/+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 1615665] Re: Enable virtual scsi server driver for Power

[Joseph Salisbury]

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

** Tags added: kernel-da-key

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

Title:
  Enable virtual scsi server driver for Power

Status in linux package in Ubuntu:
  New

Bug description:
  Once Canonical updates to the 4.8 kernel, the following kernel options
  need to be enabled for this feature:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1615665/+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 344878] Re: file name too long when creating new file (ecryptfs_lookup: lookup_one_len() returned [-36] on lower_dentry)

[Ronald]

Long Path Tool worked wonders for me, it helped me a lot.

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

Title:
  file name too long when creating new file (ecryptfs_lookup:
  lookup_one_len() returned [-36] on lower_dentry)

Status in eCryptfs:
  Fix Released
Status in ecryptfs-utils package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in ecryptfs-utils source package in Natty:
  Won't Fix
Status in linux source package in Natty:
  Won't Fix
Status in ecryptfs-utils source package in Oneiric:
  Won't Fix
Status in linux source package in Oneiric:
  Won't Fix
Status in ecryptfs-utils source package in Precise:
  Invalid
Status in linux source package in Precise:
  Fix Released

Bug description:
  ===
  IMPORTANT: eCryptfs can only store filenames of up to 143 characters when 
filename encryption is enabled. The remaining 112 characters are used for 
storing metadata such as the encrypted filename prefix, the signature of the 
filename encryption key, and an identifier for the cipher used, as well as 
random bytes to make /foo/file and /bar/file encrypt to different ciphertext 
and padding bytes to achieve proper cipher block size alignment.

  This bug is considered 'fixed' by the upstream maintainers. The
  eCryptfs kernel error message has been reduced to a debug level log
  message and eCryptfs now correctly reports its maximum supported
  filename length through the statfs() syscall. This is all that can be
  done without implementing a completely new encrypted filename design.
  A design that allows 255 character filenames without introducing other
  design limitations has not been identified and no one is currently
  working to come up with such a design.

  Please do not add comments or create new bugs saying that mv reports
  'File name too long' or that you can't create a long filename in your
  eCryptfs mounts. It is an unfortunate design limitation that cannot be
  avoided at this time.

  Please do create new bugs when an application generates filenames that are 
too long to be stored in an eCryptfs mount. The application may be able to use 
the statfs() syscall to check the filename length limits of eCryptfs. Note that 
this does not include something like a torrent or ftp client trying to download 
a file with a long filename. The application is not generating the filename in 
those cases, it is just downloading the file that the user told it to download.
  ===

  When trying to create a new file with a relatively long filename (f. ex. 
dfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqb.txt)
  I get an error: file name to long, when in fact the file name is not to long, 
but the encrypted name created for this file is to long, so, the file was not 
created.

  this is no problem when I try to create a file, but when I'm copying a
  lot of files to my home folder I get some: filename to long error's
  and it's hard to fix (first locate the file, create shorter name, move
  again)

  so, maybe you could create a check for to long filenames?

  I'm using ext4 here...

  mv 
dfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqb.txt
 /home/jens/
  mv: cannot stat 
`/home/jens/dfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqb.txt':
 File name too long

  libecryptfs0:
    Installed: 71-0ubuntu2
    Candidate: 71-0ubuntu2
    Version table:
   *** 71-0ubuntu2 0
  500 http://be.archive.ubuntu.com jaunty/main Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ecryptfs/+bug/344878/+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 1615663] [NEW] package linux-firmware 1.157.3 failed to install/upgrade: package linux-firmware is not ready for configuration cannot configure (current status 'half-installed')

[Anupam Sobti]

Public bug reported:

The error came when I booted the PC after a shutdown.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-firmware 1.157.3
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Aug 21 16:31:21 2016
Dependencies:
 
DpkgHistoryLog:
 Start-Date: 2016-08-21  16:31:18
 Commandline: apt-get install python3-tk
 Requested-By: anupam (1000)
 Install: blt:amd64 (2.5.3+dfsg-3, automatic), tk8.6-blt2.5:amd64 
(2.5.3+dfsg-3, automatic), python3-tk:amd64 (3.5.1-1)
DuplicateSignature:
 package:linux-firmware:1.157.3
 Processing triggers for libc-bin (2.23-0ubuntu3) ...
 dpkg: error processing package linux-firmware (--configure):
  package linux-firmware is not ready for configuration
ErrorMessage: package linux-firmware is not ready for configuration  cannot 
configure (current status 'half-installed')
InstallationDate: Installed on 2016-04-30 (114 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: linux-firmware
Title: package linux-firmware 1.157.3 failed to install/upgrade: package 
linux-firmware is not ready for configuration  cannot configure (current status 
'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package linux-firmware 1.157.3 failed to install/upgrade: package
  linux-firmware is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  The error came when I booted the PC after a shutdown.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Aug 21 16:31:21 2016
  Dependencies:
   
  DpkgHistoryLog:
   Start-Date: 2016-08-21  16:31:18
   Commandline: apt-get install python3-tk
   Requested-By: anupam (1000)
   Install: blt:amd64 (2.5.3+dfsg-3, automatic), tk8.6-blt2.5:amd64 
(2.5.3+dfsg-3, automatic), python3-tk:amd64 (3.5.1-1)
  DuplicateSignature:
   package:linux-firmware:1.157.3
   Processing triggers for libc-bin (2.23-0ubuntu3) ...
   dpkg: error processing package linux-firmware (--configure):
package linux-firmware is not ready for configuration
  ErrorMessage: package linux-firmware is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2016-04-30 (114 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.157.3 failed to install/upgrade: package 
linux-firmware is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1615663/+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 1615663] Re: package linux-firmware 1.157.3 failed to install/upgrade: package linux-firmware is not ready for configuration cannot configure (current status 'half-installed')

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-firmware 1.157.3 failed to install/upgrade: package
  linux-firmware is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  The error came when I booted the PC after a shutdown.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Aug 21 16:31:21 2016
  Dependencies:
   
  DpkgHistoryLog:
   Start-Date: 2016-08-21  16:31:18
   Commandline: apt-get install python3-tk
   Requested-By: anupam (1000)
   Install: blt:amd64 (2.5.3+dfsg-3, automatic), tk8.6-blt2.5:amd64 
(2.5.3+dfsg-3, automatic), python3-tk:amd64 (3.5.1-1)
  DuplicateSignature:
   package:linux-firmware:1.157.3
   Processing triggers for libc-bin (2.23-0ubuntu3) ...
   dpkg: error processing package linux-firmware (--configure):
package linux-firmware is not ready for configuration
  ErrorMessage: package linux-firmware is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2016-04-30 (114 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.157.3 failed to install/upgrade: package 
linux-firmware is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1615663/+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 1615665] [NEW] Enable virtual scsi server driver for Power

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Once Canonical updates to the 4.8 kernel, the following kernel options
need to be enabled for this feature:

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64le bugnameltc-144007 severity-high 
targetmilestone-inin1610
-- 
Enable virtual scsi server driver for Power
https://bugs.launchpad.net/bugs/1615665
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1612732] onza (amd64) - tests ran: 10, failed: 10

[Brad Figg]

tests ran:  10, failed: 10;
  
http://kernel.ubuntu.com/testing/3.2.0-109.150/onza__3.2.0-109.150__2016-08-22_13-18-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/1612732

Title:
  linux: 3.2.0-109.150 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New

Bug description:
  This bug is for tracking the 3.2.0-109.150 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: 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/1612732/+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 1615620] [NEW] Xenial update to v4.4.19 stable release

[Tim Gardner]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The v4.4.19 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the v4.4.19 stable release shall be
applied:

usb: gadget: avoid exposing kernel stack
usb: f_fs: off by one bug in _ffs_func_bind()
usb: renesas_usbhs: protect the CFIFOSEL setting in usbhsg_ep_enable()
usb: dwc3: fix for the isoc transfer EP_BUSY flag
USB: serial: option: add support for Telit LE910 PID 0x1206
usb: renesas_usbhs: fix NULL pointer dereference in xfer_work()
arm64: kernel: Save and restore UAO and addr_limit on exception entry
arm64: debug: unmask PSTATE.D earlier
arm64: Fix incorrect per-cpu usage for boot CPU
tty: serial: msm: Don't read off end of tx fifo
serial: samsung: Fix ERR pointer dereference on deferred probe
tty/serial: atmel: fix RS485 half duplex with DMA
gpio: pca953x: Fix NBANK calculation for PCA9536
gpio: intel-mid: Remove potentially harmful code
Bluetooth: hci_intel: Fix null gpio desc pointer dereference
pinctrl: cherryview: prevent concurrent access to GPIO controllers
arm64: dts: rockchip: fixes the gic400 2nd region size for rk3368
arm64: mm: avoid fdt_check_header() before the FDT is fully mapped
KVM: PPC: Book3S HV: Pull out TM state save/restore into separate procedures
KVM: PPC: Book3S HV: Save/restore TM state in H_CEDE
KVM: MTRR: fix kvm_mtrr_check_gfn_range_consistency page fault
KVM: VMX: handle PML full VMEXIT that occurs during event delivery
KVM: nVMX: Fix memory corruption when using VMCS shadowing
intel_pstate: Fix MSR_CONFIG_TDP_x addressing in core_get_max_pstate()
mfd: qcom_rpm: Fix offset error for msm8660
mfd: qcom_rpm: Parametrize also ack selector size
media: usbtv: prevent access to free'd resources
media: dvb_ringbuffer: Add memory barriers
vb2: core: Skip planes array verification if pb is NULL
Fix RC5 decoding with Fintek CIR chipset
sur40: lower poll interval to fix occasional FPS drops to ~56 FPS
sur40: fix occasional oopses on device close
dm: set DMF_SUSPENDED* _before_ clearing DMF_NOFLUSH_SUSPENDING
hp-wmi: Fix wifi cannot be hard-unblocked
s5p-mfc: Set device name for reserved memory region devs
s5p-mfc: Add release callback for memory region devs
i2c: efm32: fix a failure path in efm32_i2c_probe()
spi: pxa2xx: Clear all RFT bits in reset_sccr1() on Intel Quark
Bluetooth: Fix l2cap_sock_setsockopt() with optname BT_RCVMTU
EDAC: Correct channel count limit
HID: uhid: fix timeout when probe races with IO
ovl: disallow overlayfs as upperdir
remoteproc: Fix potential race condition in rproc_add
ARC: mm: don't loose PTE_SPECIAL in pte_modify()
jbd2: make journal y2038 safe
fs/cifs: make share unaccessible at root level mountable
cifs: Check for existing directory when opening file with O_CREAT
cifs: fix crash due to race in hmac(md5) handling
CIFS: Fix a possible invalid memory access in smb2_query_symlink()
random: initialize the non-blocking pool via add_hwgenerator_randomness()
random: print a warning for the first ten uninitialized random users
random: add interrupt callback to VMBus IRQ handler
MIPS: KVM: Fix mapped fault broken commpage handling
MIPS: KVM: Add missing gfn range check
MIPS: KVM: Fix gfn range check in kseg0 tlb faults
MIPS: KVM: Propagate kseg0/mapped tlb fault errors
nfs: don't create zero-length requests
nfsd: Fix race between FREE_STATEID and LOCK
nfsd: don't return an unhashed lock stateid after taking mutex
drm/i915: Don't complain about lack of ACPI video bios
iommu/exynos: Suppress unbinding to prevent system failure
iommu/vt-d: Return error code in domain_context_mapping_one()
iommu/amd: Handle IOMMU_DOMAIN_DMA in ops->domain_free call-back
iommu/amd: Init unity mappings only for dma_ops domains
iommu/amd: Update Alias-DTE in update_device_table()
audit: fix a double fetch in audit_log_single_execve_arg()
ARM: dts: sunxi: Add a startup delay for fixed regulator enabled phys
netlabel: add address family checks to netlbl_{sock,req}_delattr()
w1:omap_hdq: fix regression
drm/amdgpu: add a delay after ATPX dGPU power off
drm/amdgpu: Poll for both connect/disconnect on analog connectors
drm/amdgpu: support backlight control for UNIPHY3
drm/amdgpu: Disable RPM helpers while reprobing connectors on resume
drm/amdgpu: fix firmware info version checks
drm/amdgpu/gmc7: add missing mullins case
drm/radeon: add a delay after ATPX dGPU power off
drm/radeon: Poll for both connect/disconnect on analog connectors
drm/radeon: fix firmware info version checks
drm/radeon: support backlight control for UNIPHY3
drm/nouveau/gr/nv3x: fix instobj write 

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

[Brad Figg]

tests ran:   4, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-95.142/dwalin__3.13.0-95.142__2016-08-22_12-41-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/1612715

Title:
  linux: 3.13.0-95.142 -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:
  Fix Released
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:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.13.0-95.142 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: 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/1612715/+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 1615585] Re: Perl warnings when using linuxdoc

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Perl warnings when using linuxdoc

Status in linuxdoc-tools package in Ubuntu:
  New

Bug description:
  Starting with Ubuntu 16.04 running linuxdoc produces a number of Perl
  warnings:

  
  linuxdoc -B html -s 1 manual.sgml
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/\\nameurl{ <-- HERE (.*)}{(.*)}/ at 
/usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl line 287.
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/\\nameurl{(.*)}{ <-- HERE (.*)}/ at 
/usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl line 287.
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/\\nameurl{ <-- HERE .*}{.*}/ at 
/usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl line 291.
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/\\nameurl{.*}{ <-- HERE .*}/ at 
/usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl line 291.
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/^\\usepackage{ <-- HERE \@LINUXDOC_DTD\@-sgml}/ at 
/usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl line 370.
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/^\\usepackage\[\@BABELOPTIONS\@\]{ <-- HERE babel}/ at 
/usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl line 375.
  Processing file manual.sgml

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linuxdoc-tools 0.9.71-2 [modified: 
usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl]
  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
  CurrentDesktop: Unity
  Date: Mon Aug 22 12:43:20 2016
  InstallationDate: Installed on 2015-02-24 (544 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: linuxdoc-tools
  UpgradeStatus: Upgraded to xenial on 2016-08-20 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linuxdoc-tools/+bug/1615585/+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 1611536] Re: Fan on full speed without noapic or nolapic on HP 6715s

[Carl Englund]

I have done some testing of different kernels from the mainline
repository, omitting the noapic parameter to see if they start and how
the fan behaves. This is the result. Kernels using 64-bit FADT cause the
machine to malfunction, as per:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590154

4.1.0: fan ok, 32-bit FADT
4.1.10: fan ok, 64-bit FADT. X.org freeze.
4.1.11: fan ok, boot freeze
4.1.12: fan ok, boot freeze
4.1.13: fan ok, boot freeze
4.1.17: fan ok, boot freeze
4.1.23: fan ok, 64-bit FADT
4.1.24: fan ok, boot freeze
4.1.25: fan ok, boot freeze
4.1.26: fan ok, boot freeze
4.1.30: fan ok, 64-bit FADT, X.org freeze.
4.2.0: fan ok, boot freeze
4.2.4: fan full, very dark screen (but working?)
4.2.7: fan full, 64-bit FADT
(U) 4.4.0-21: fan full, 32-bit FADT
(U) 4.4.0-34: fan ok, 32-bit FADT
4.8.0-rc2: fan full, 32-bit FADT

The kernels marked (U) are downloaded from the normal repositories. This
machine is currently running Mint 18 but I understand Mint uses Ubuntu
kernels so I hope it's alright testing in Mint.

I'm thinking it could be interesting to bisect 4.4.0-21 to 4.4.0-34 and
see what causes the fan to start behaving normally.

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

Title:
  Fan on full speed without noapic or nolapic on HP 6715s

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Without adding noapic or nolapic to boot parameters the fan will run
  on full speed, the system is sluggish (can almost see windows
  redrawing on screen). On some kernel versions tested, rebooting also
  fails.

  The parameter(s) were not required in Trusty. I also tested some
  Mainline kernels and discovered 3.19.8 and 4.0.9 works without the
  parameters. At least 4.1.29 and onward requires noapic or nolapic for
  this machine to work properly but I have yet to investigate the
  versions between 4.0.9 and 4.1.29.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diskdoc2700 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Aug 10 01:15:07 2016
  HibernationDevice: RESUME=UUID=522810df-638a-412b-9aab-791e2e2bc545
  InstallationDate: Installed on 2016-06-07 (63 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Compaq 6715s (RU655ET#AK8)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=3a37ee65-4c02-4a95-b814-f4538a4a308d ro quiet splash noapic 
acpi_force_32bit_fadt_addr vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68YTT Ver. F.20
  dmi.board.name: 30C2
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.2D
  dmi.chassis.asset.tag: CNU7201T8J
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68YTTVer.F.20:bd12/01/2011:svnHewlett-Packard:pnHPCompaq6715s(RU655ET#AK8):pvrF.20:rvnHewlett-Packard:rn30C2:rvrKBCVersion71.2D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq 6715s (RU655ET#AK8)
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard

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

[Brad Figg]

tests ran:  20, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-68.76~14.04.1/onibi__3.19.0-68.76~14.04.1__2016-08-22_10-38-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/1612564

Title:
  linux-lts-vivid: 3.19.0-68.76~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:
  Fix Released
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:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.19.0-68.76~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 --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1612550
  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/1612564/+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 1612715] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 3, failed: 1

[Brad Figg]

tests ran:   3, failed: 1;
  
http://kernel.ubuntu.com/testing/3.13.0-95.142/ms10-34-mcdivittB0-kernel__3.13.0-95.142__2016-08-22_11-12-00/results-index.html

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

Title:
  linux: 3.13.0-95.142 -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:
  Fix Released
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:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.13.0-95.142 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: 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/1612715/+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 1612715] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 3, failed: 1

[Brad Figg]

tests ran:   3, failed: 1;
  
http://kernel.ubuntu.com/testing/3.13.0-95.142/ms10-35-mcdivittB0-kernel__3.13.0-95.142__2016-08-22_11-12-00/results-index.html

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

Title:
  linux: 3.13.0-95.142 -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:
  Fix Released
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:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.13.0-95.142 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: 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/1612715/+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 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

[Keith Burns]

Found that root cause on my rig was low end GPU and nouveau driver. Vendor
upgraded my GPU and put on Nvidia driver and its been perfect ever since.
NOTE: nothing in logs indicates a video issue.

On Mon, Aug 22, 2016, 3:45 AM Jimmy Pan  wrote:

> This problem is driving me crazy. Looks like this is related to the
> nvidia driver. You can shut down the system with 3rd party nvidia driver
> installed in recovery x mode. However, you cannot enter normal mode at
> all.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1530405
>
> Title:
>   NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
>
> Status in linux package in Ubuntu:
>   Triaged
>
> Bug description:
>   I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
>   randomly freeze up, sometimes before the login screen, sometimes while
>   I'm in the middle of using a program. This sometimes happens on the
>   Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
>   4.2.0-22.
>
>   Important part of log:
>
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG:
> soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in:
> rfcomm bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul
> sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul
> rtl8821ae glue_helper snd_hda_codec_realtek ablk_helper
> snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel btcoexist
> snd_hda_codec rtl_pci snd_hda_core joydev input_leds snd_hwdep rtlwifi
> snd_pcm fam15h_power cryptd snd_seq_midi serio_raw snd_seq_midi_event
> snd_rawmidi mac80211 snd_seq snd_seq_device snd_timer cfg80211 btusb btrtl
> btbcm btintel bluetooth snd soundcore edac_mce_amd k10temp edac_core
> i2c_piix4 shpchp mac_hid parport_pc ppdev lp parport autofs4
> hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid amdkfd
> amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect
> sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes video
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814
> Comm: kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name:
> ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS
> 0501 07/09/2015
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task:
> 88031146d400 ti: 88030e838000 task.ti: 88030e838000
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP:
> 0010:[]  [] __do_softirq+0x76/0x250
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP:
> 0018:88031fc03f30  EFLAGS: 0202
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX:
> 88030e83c000 RBX:  RCX: 40400040
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:
>  RSI: 613e RDI: 0380
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP:
> 88031fc03f80 R08: 0029f8fa1411 R09: 88031fc169f0
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10:
> 0020 R11: 0004 R12: 88031fc169c0
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13:
> 88030df8e200 R14:  R15: 0001
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112202] FS:
> 7f6c266ac880() GS:88031fc0() knlGS:
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112203] CS:  0010 DS: 
> ES:  CR0: 80050033
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112205] CR2:
> 7ffef000bff8 CR3: 00030f368000 CR4: 000406f0
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112206] Stack:
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112207]  404000401fc03f78
> 88030e83c000 0121 8803000a
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112209]  00021fc0d640
>  88031fc169c0 88030df8e200
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112211]  
> 0001 88031fc03f90 81081d23
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112213] Call Trace:
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112215]  
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112219]
> [] irq_exit+0xa3/0xb0
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.11]
> [] smp_apic_timer_interrupt+0x42/0x50
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112225]
> [] apic_timer_interrupt+0x82/0x90
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112226]  
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112230]
> [] ? finish_task_switch+0x67/0x1c0
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112232]
> [] __schedule+0x36c/0x980
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112234]
> [] schedule+0x33/0x80
>   Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112236]
> [] 

[Kernel-packages] [Bug 1584456] Re: apparmor denial using ptmx char device

[Zygmunt Krynicki]

** Changed in: snap-confine
   Status: Fix Committed => 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/1584456

Title:
  apparmor denial using ptmx char device

Status in Snappy Launcher:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  - Finding issues running snaps (hello-world). 
  - Same issue even installing with --devmode. Even running the snap binary as 
root
  - Using a custom kernel, this is on an Nvidia Tegra X1 custom board.

  =

  ubuntu@localhost:~$ hello-world.echo plop
  unable to mount '/dev/pts/ptmx'->'/dev/ptmx'. errmsg: Permission denied
  ubuntu@localhost:~$ sudo hello-world.echo plop
  unable to mount '/dev/pts/ptmx'->'/dev/ptmx'. errmsg: Permission denied

  dmesg shows:
  =

  [  302.838046] type=1400 audit(1455208371.989:16): apparmor="DENIED"
  operation="mount" info="failed mntpnt match" error=-13 parent=911
  profile="/usr/bin/ubuntu-core-launcher" name="/dev/ptmx/" pid=912
  comm="ubuntu-core-lau" srcname="/dev/pts/ptmx/" flags="rw, bind"
  [  308.080449] type=1400 audit(1455208377.229:17): apparmor="DENIED"
  operation="mount" info="failed mntpnt match" error=-13 parent=914
  profile="/usr/bin/ubuntu-core-launcher" name="/dev/ptmx/" pid=915
  comm="ubuntu-core-lau" srcname="/dev/pts/ptmx/" flags="rw, bind"

  This is with the "hello-world" snap installed with "snap install"

  Output of an ls over the device file:
  =

  ubuntu@localhost:~$ ls -lR /dev/ptmx /dev/pts
  crw-rw-rw- 1 root tty  5, 2 Feb 11 16:28 /dev/ptmx

  /dev/pts:
  total 0
  c- 1 root root 5, 2 Jan  1  1970 ptmx

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-confine/+bug/1584456/+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 1605494] Re: vmxnet3 LRO IPv6 performance issues (stalling TCP)

[Floris Mouwen]

Hi Stefan and Tim,

Is this patch also available for Ubuntu 12.04 LTS and 14.04 LTS?
The fix in -proposed works in Ubuntu 16.04.1.

Kind Regards,
Floris Mouwen

** Tags added: verification-done-xenial

** Tags removed: verification-needed-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/1605494

Title:
  vmxnet3 LRO IPv6 performance issues (stalling TCP)

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:
  We have performance problems with TCP over IPv6 with SSH/SCP and HTTP traffic 
on Linux guest virtual machines running on VMware ESXi (6.0u2). We are running 
Ubuntu 12.04.5 LTS, 14.04.3 LTS and soon 16.04.1 LTS.
  If we upload (large) files with these protocols the performance go's down to 
200kb/s.
  With IPv4, we have a much higher performance.

  This is a known issue in the vmxnet3 driver that is fixed upstream on the 
21th of April:
  "This is due to check sum handling issue in the vmxnet3 driver. Fix is on 
  the kernel tree." http://comments.gmane.org/gmane.linux.network/401727

  Kernel Patch:
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f0d437809d23999cb25207cfbe80c61e5703fdc1

  Another example of someone who has this problem:
  https://lists.debian.org/debian-kernel/2016/03/msg1.html
  https://lists.debian.org/debian-kernel/2016/03/msg2.html

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-61-generic 3.13.0-61.100
  ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-61-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 12 14:04 seq
   crw-rw 1 root audio 116, 33 Jul 12 14:04 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'
  Date: Fri Jul 22 08:05:09 2016
  HibernationDevice: RESUME=UUID=4b881d72-9266-45cd-a12f-f21b55fe1ae7
  InstallationDate: Installed on 2014-05-08 (805 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: VMware, Inc. VMware Virtual Platform
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-61-generic 
root=/dev/mapper/system-root ro
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-61-generic N/A
   linux-backports-modules-3.13.0-61-generic  N/A
   linux-firmware 1.127.22
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 09/21/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:bd09/21/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/1605494/+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 1615585] [NEW] Perl warnings when using linuxdoc

[Jan Willamowius]

Public bug reported:

Starting with Ubuntu 16.04 running linuxdoc produces a number of Perl
warnings:


linuxdoc -B html -s 1 manual.sgml
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/\\nameurl{ <-- HERE (.*)}{(.*)}/ at 
/usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl line 287.
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/\\nameurl{(.*)}{ <-- HERE (.*)}/ at 
/usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl line 287.
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/\\nameurl{ <-- HERE .*}{.*}/ at 
/usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl line 291.
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/\\nameurl{.*}{ <-- HERE .*}/ at 
/usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl line 291.
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/^\\usepackage{ <-- HERE \@LINUXDOC_DTD\@-sgml}/ at 
/usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl line 370.
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/^\\usepackage\[\@BABELOPTIONS\@\]{ <-- HERE babel}/ at 
/usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl line 375.
Processing file manual.sgml

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linuxdoc-tools 0.9.71-2 [modified: 
usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl]
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
CurrentDesktop: Unity
Date: Mon Aug 22 12:43:20 2016
InstallationDate: Installed on 2015-02-24 (544 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
SourcePackage: linuxdoc-tools
UpgradeStatus: Upgraded to xenial on 2016-08-20 (1 days ago)

** Affects: linuxdoc-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  Perl warnings when using linuxdoc

Status in linuxdoc-tools package in Ubuntu:
  New

Bug description:
  Starting with Ubuntu 16.04 running linuxdoc produces a number of Perl
  warnings:

  
  linuxdoc -B html -s 1 manual.sgml
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/\\nameurl{ <-- HERE (.*)}{(.*)}/ at 
/usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl line 287.
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/\\nameurl{(.*)}{ <-- HERE (.*)}/ at 
/usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl line 287.
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/\\nameurl{ <-- HERE .*}{.*}/ at 
/usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl line 291.
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/\\nameurl{.*}{ <-- HERE .*}/ at 
/usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl line 291.
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/^\\usepackage{ <-- HERE \@LINUXDOC_DTD\@-sgml}/ at 
/usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl line 370.
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/^\\usepackage\[\@BABELOPTIONS\@\]{ <-- HERE babel}/ at 
/usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl line 375.
  Processing file manual.sgml

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linuxdoc-tools 0.9.71-2 [modified: 
usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl]
  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
  CurrentDesktop: Unity
  Date: Mon Aug 22 12:43:20 2016
  InstallationDate: Installed on 2015-02-24 (544 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: linuxdoc-tools
  UpgradeStatus: Upgraded to xenial on 2016-08-20 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linuxdoc-tools/+bug/1615585/+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 1615585] Re: Perl warnings when using linuxdoc

[Jan Willamowius]

Here is a diff to fix the Perl code of /usr/share/linuxdoc-
tools/fmt/fmt_latex2e.pl

** Patch added: "fmt_latex2e.pl.diff"
   
https://bugs.launchpad.net/ubuntu/+source/linuxdoc-tools/+bug/1615585/+attachment/4725602/+files/fmt_latex2e.pl.diff

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

Title:
  Perl warnings when using linuxdoc

Status in linuxdoc-tools package in Ubuntu:
  New

Bug description:
  Starting with Ubuntu 16.04 running linuxdoc produces a number of Perl
  warnings:

  
  linuxdoc -B html -s 1 manual.sgml
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/\\nameurl{ <-- HERE (.*)}{(.*)}/ at 
/usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl line 287.
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/\\nameurl{(.*)}{ <-- HERE (.*)}/ at 
/usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl line 287.
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/\\nameurl{ <-- HERE .*}{.*}/ at 
/usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl line 291.
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/\\nameurl{.*}{ <-- HERE .*}/ at 
/usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl line 291.
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/^\\usepackage{ <-- HERE \@LINUXDOC_DTD\@-sgml}/ at 
/usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl line 370.
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/^\\usepackage\[\@BABELOPTIONS\@\]{ <-- HERE babel}/ at 
/usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl line 375.
  Processing file manual.sgml

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linuxdoc-tools 0.9.71-2 [modified: 
usr/share/linuxdoc-tools/fmt/fmt_latex2e.pl]
  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
  CurrentDesktop: Unity
  Date: Mon Aug 22 12:43:20 2016
  InstallationDate: Installed on 2015-02-24 (544 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: linuxdoc-tools
  UpgradeStatus: Upgraded to xenial on 2016-08-20 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linuxdoc-tools/+bug/1615585/+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 1576909] Re: [Acer Aspire V3-472G] Suspend not working on Ubuntu 16.04

[saguti]

I couldn't continue the testing in 16.04 thus I had to rollback to
14.04, where suspend works flawlessly

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

Title:
  [Acer Aspire V3-472G] Suspend not working on Ubuntu 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 16.04 on an Acer Aspire V3-472G with Nvidia
  Geforce 840M graphic cards, proprietary driver.

  None of the options for suspend are working. The process of suspend
  works fine but when the computer is waken, screen stays black and
  computer becomes unresponsive.

  Installation of packets such as uswsusp create a bigger problem as the
  computer freezes during boot process.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  saguti 2907 F pulseaudio
   /dev/snd/pcmC1D0p:   saguti 2907 F...m pulseaudio
   /dev/snd/controlC1:  saguti 2907 F pulseaudio
  Date: Fri Apr 29 21:42:27 2016
  HibernationDevice: RESUME=UUID=93ec1eec-dc0c-4ac4-9b06-b2d3cca2a8da
  InstallationDate: Installed on 2015-01-01 (484 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 004: ID 04f2:b469 Chicony Electronics Co., Ltd
   Bus 002 Device 005: ID 0489:e04e Foxconn / Hon Hai
   Bus 002 Device 002: ID 3938:1031
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire V3-472G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/ubuntu--vg-root ro acpi_sleep=nonvs resume=/dev/dm-1
  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-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (4 days ago)
  dmi.bios.date: 09/24/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA40_HB
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.21:bd09/24/2014:svnAcer:pnAspireV3-472G:pvrTBDbyOEM:rvnAcer:rnEA40_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire V3-472G
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576909/+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 1584597] Re: Hyper-V Memory Ballooning re-broken in 16.04

[erty]

I had same issue because my memory parameters didn't divide by 128mb
see official Hyper-V documentation Note 8 and 9: 
https://technet.microsoft.com/ru-ru/windows-server-docs/compute/hyper-v/supported-ubuntu-virtual-machines-on-hyper-v

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

Title:
  Hyper-V Memory Ballooning re-broken in 16.04

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

Bug description:
  Regression: #1294283 fixed memory ballooning in Hyper-V in 14.04, but
  the bug has returned in 16.04.

  
  Steps to reproduce:

  1. Create Gen2 Hyper-V VM
  2. Install Ubuntu 16.04
  3. modprobe hv_balloon
  Memory usage according to Hyper-V Manager will not change

  
  This has been reproduced on 2 fresh Ubuntu Server 16.04 instances.

  I installed linux-generic-xenial on a 14.04 instance, rebooted,
  modprobe'd hv_balloon and memory usage in Hyper-V Manager reduced to
  the correct level.

  Environment:
  Host: Windows NanoServer 2016

  Ubuntu Server 16.04 version_signature: `Ubuntu 4.4.0-21.37-generic 4.4.6`
  Ubuntu Server 14.04 version_signature: `Ubuntu 4.4.0-22.40~14.04.1-generic 
4.4.8`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584597/+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 1612550] Re: linux: 3.19.0-68.76 -proposed tracker

[Yung Shen]

Hardware Certification have begun testing this -proposed kernel.

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => Yung 
Shen (kaxing)

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

Title:
  linux: 3.19.0-68.76 -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:
  In Progress
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:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: 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/1612550/+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 1611283] Re: entering crypto passphrase while notebook is mounted to docking station results in sleep state

[Hauke Bruno]

So sadly neither 4.8.0-040800rc1.201608072231 nor
4.8.0-040800rc2.201608142332 resolves the problem. Is there any kind of
log or debugging output I can send you?

** Tags added: kernel-bug-exists-upstream

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

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

Title:
  entering crypto passphrase while notebook is mounted to docking
  station results in sleep state

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to the current kernel (4.4.0-34-generic) I am not able
  to log in to my Kubuntu 16.04 at a Lenovo T430 while it is mounted to
  a docking station.

  Ubuntu boots until I need to enter the passphrase for my crypted disk,
  but anyhow the system then enters a sleep state (small moon icon is
  blinking). Inside the docking station I am not able to leave that
  state.

  Outside the docking station the problem doesn't occur.

  While using the 4.4.0-31-generic kernel, everything works fine.

  I am not sure how to debug that behavior, so if some more information
  is needed please leave me a note.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  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
  CurrentDesktop: KDE
  Date: Tue Aug  9 10:31:09 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-12 (88 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611283/+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 1612715] onibi (i386) - tests ran: 3, failed: 0

[Brad Figg]

tests ran:   3, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-95.142/onibi__3.13.0-95.142__2016-08-22_07-35-00/results-index.html

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

Title:
  linux: 3.13.0-95.142 -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:
  Fix Released
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:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.13.0-95.142 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: 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/1612715/+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 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

[Jimmy Pan]

This problem is driving me crazy. Looks like this is related to the
nvidia driver. You can shut down the system with 3rd party nvidia driver
installed in recovery x mode. However, you cannot enter normal mode at
all.

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
  randomly freeze up, sometimes before the login screen, sometimes while
  I'm in the middle of using a program. This sometimes happens on the
  Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
  4.2.0-22.

  Important part of log:

  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 22s! [kerneloops:814]
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in: rfcomm 
bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul 
sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae 
glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic 
snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core 
joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi 
serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device 
snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore 
edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp 
parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid 
amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes 
video
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814 Comm: 
kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name: ASUSTeK 
COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 
07/09/2015
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task: 88031146d400 
ti: 88030e838000 task.ti: 88030e838000
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP: 
0010:[]  [] __do_softirq+0x76/0x250
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP: 
0018:88031fc03f30  EFLAGS: 0202
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX: 88030e83c000 
RBX:  RCX: 40400040
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:  
RSI: 613e RDI: 0380
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP: 88031fc03f80 
R08: 0029f8fa1411 R09: 88031fc169f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10: 0020 
R11: 0004 R12: 88031fc169c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13: 88030df8e200 
R14:  R15: 0001
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112202] FS:  
7f6c266ac880() GS:88031fc0() knlGS:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112203] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112205] CR2: 7ffef000bff8 
CR3: 00030f368000 CR4: 000406f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112206] Stack:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112207]  404000401fc03f78 
88030e83c000 0121 8803000a
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112209]  00021fc0d640 
 88031fc169c0 88030df8e200
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112211]   
0001 88031fc03f90 81081d23
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112213] Call Trace:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112215]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112219]  [] 
irq_exit+0xa3/0xb0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.11]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112225]  [] 
apic_timer_interrupt+0x82/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112226]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112230]  [] ? 
finish_task_switch+0x67/0x1c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112232]  [] 
__schedule+0x36c/0x980
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112234]  [] 
schedule+0x33/0x80
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112236]  [] 
do_nanosleep+0x6f/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112239]  [] 
hrtimer_nanosleep+0xdc/0x1f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112241]  [] ? 
__hrtimer_init+0x90/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112243]  [] ? 
do_nanosleep+0x5a/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112245]  [] 

[Kernel-packages] [Bug 1606786] dmesg output

[bugproxy]

--- Comment (attachment only) From santh...@in.ibm.com 2016-08-22 03:16 
EDT---


** Attachment added: "dmesg output"
   
https://bugs.launchpad.net/bugs/1606786/+attachment/4725421/+files/dmesg31Tb.out

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

Title:
  in Ubuntu16.10: Hit on Call traces  and system goes down when
  transactional memory  tests are running in 32TB Brazos system

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:
  == Comment: #0 - Praveen K. Pandey  - 2016-07-16 
14:21:39 ==
  ---Problem Description---
   In Ubuntu16.10 Call traces and unrecoverable exception occurs when 
Transactional memory tests are executed in 32TB system.

  Steps to reproduce:
   
  1- Download tm tests from the link - 
'http://ozlabs.au.ibm.com/~mikey/tm-test-le.tar.gz' 

  2- untar tm-test-le.tar.gz; make clean; make; ./runtests.sh

  The system gives below call traces and goes down. [Not able to do ssh
  and the console gets hung]

  LOG:

  Running ./htm_demo
  Starting 6144 worker threads, 5 loops
  --
  --
  [  438.064162] CFAR: c0008d18 SOFTE: 0

  
  PACATMSCRATCH: 80029033   

  
  GPR00: c0111028 c5f82e36f4b0 c15b5d00 

  
  GPR04: c0b28863 0001 c1755d00 00018748

  
  GPR08: 04f0 f5257d14 01fab980 0005

  
  GPR12: 0500 cbc9dd00 3ffcf5fa 0100

  
  GPR16:  c1faba7898e8 0001 c3f9865bf804

  
  GPR20: 0003 c01638b0 0001 00661a113a10

  
  GPR24:  c5f82e9f2060 01fab980 c15eaa60

  
  GPR28: c0f9e900 009e c15eaa60 c1faba79e900

  
  [  438.064303] NIP [c00a1ba4] kvmppc_interrupt_hv+0x28/0x15c  

  
  [  438.064315] LR [c0111028] trigger_load_balance+0x58/0x340  

  
  [  438.064323] Call Trace:

  
  [  438.064330] [c5f82e36f4b0] [c0111028] 
trigger_load_balance+0x58/0x340 (unreliable)
   
  [  438.064346] [c5f82e36f4f0] [c00f9ee4] 
scheduler_tick+0x104/0x180  
   
  [  438.064360] [c5f82e36f550] [c014c128] 
update_process_times+0x78/0xa0  
   
  [  438.064378] [c5f82e36f580] [c0163818] 
tick_sched_handle.isra.6+0x48/0xe0  
   
  [  438.064392] [c5f82e36f5c0] [c0163914] 
tick_sched_timer+0x64/0xd0  
   
  [  438.064404] [c5f82e36f600] [c014cbd4] 
__hrtimer_run_queues+0x124/0x450
   
  [  438.064418] [c5f82e36f690] [c014dbfc] 
hrtimer_interrupt+0xec/0x2c0
   
  [  438.064431] [c5f82e36f750] 

[Kernel-packages] [Bug 1615506] [NEW] package linux-image-3.19.0-66-lowlatency 3.19.0-66.74~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status

[Conrad]

Public bug reported:

gets haung up on start-up. i have to roll back to previous kernal
constantly

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-3.19.0-66-lowlatency 3.19.0-66.74~14.04.1
ProcVersionSignature: Ubuntu 3.19.0-65.73~14.04.1-lowlatency 3.19.8-ckt22
Uname: Linux 3.19.0-65-lowlatency x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Fri Aug 19 20:28:53 2016
DpkgTerminalLog:
 Log started: 2016-08-05  23:30:50
 Log ended: 2016-08-05  23:31:28
 
 Log started: 2016-08-19  20:23:55
ErrorMessage: subprocess installed post-installation script returned error exit 
status 2
InstallationDate: Installed on 2015-12-24 (241 days ago)
InstallationMedia: Ubuntu-Studio 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.14
SourcePackage: linux-lts-vivid
Title: package linux-image-3.19.0-66-lowlatency 3.19.0-66.74~14.04.1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-lts-vivid (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  package linux-image-3.19.0-66-lowlatency 3.19.0-66.74~14.04.1 failed
  to install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux-lts-vivid package in Ubuntu:
  New

Bug description:
  gets haung up on start-up. i have to roll back to previous kernal
  constantly

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-66-lowlatency 3.19.0-66.74~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-65.73~14.04.1-lowlatency 3.19.8-ckt22
  Uname: Linux 3.19.0-65-lowlatency x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Aug 19 20:28:53 2016
  DpkgTerminalLog:
   Log started: 2016-08-05  23:30:50
   Log ended: 2016-08-05  23:31:28
   
   Log started: 2016-08-19  20:23:55
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2015-12-24 (241 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: linux-lts-vivid
  Title: package linux-image-3.19.0-66-lowlatency 3.19.0-66.74~14.04.1 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Brad Figg]

This change was made by a bot.

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

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

Title:
  package linux-image-extra-3.13.0-93-generic 3.13.0-93.140 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  cant boot up latest kernal

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.13.0-93-generic 3.13.0-93.140
  ProcVersionSignature: Ubuntu 3.19.0-65.73~14.04.1-lowlatency 3.19.8-ckt22
  Uname: Linux 3.19.0-65-lowlatency x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  conrad 2582 F pulseaudio
   /dev/snd/controlC0:  conrad 2582 F pulseaudio
  Date: Fri Aug 19 20:30:14 2016
  DpkgTerminalLog:
   Log started: 2016-08-05  23:30:50
   Log ended: 2016-08-05  23:31:28
   
   Log started: 2016-08-19  20:23:55
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-12-24 (241 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-65-lowlatency 
root=/dev/mapper/ubuntu--studio--vg-root ro nomdmonddf nomdmonisw
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-image-extra-3.13.0-93-generic 3.13.0-93.140 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 22CD
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 93.15
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd05/30/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097510405F1620180:rvnHewlett-Packard:rn22CD:rvr93.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 097510405F1620180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1615507/+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 1615507] [NEW] package linux-image-extra-3.13.0-93-generic 3.13.0-93.140 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Conrad]

Public bug reported:

cant boot up latest kernal

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.13.0-93-generic 3.13.0-93.140
ProcVersionSignature: Ubuntu 3.19.0-65.73~14.04.1-lowlatency 3.19.8-ckt22
Uname: Linux 3.19.0-65-lowlatency x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  conrad 2582 F pulseaudio
 /dev/snd/controlC0:  conrad 2582 F pulseaudio
Date: Fri Aug 19 20:30:14 2016
DpkgTerminalLog:
 Log started: 2016-08-05  23:30:50
 Log ended: 2016-08-05  23:31:28
 
 Log started: 2016-08-19  20:23:55
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2015-12-24 (241 days ago)
InstallationMedia: Ubuntu-Studio 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
MachineType: Hewlett-Packard HP 15 Notebook PC
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-65-lowlatency 
root=/dev/mapper/ubuntu--studio--vg-root ro nomdmonddf nomdmonisw
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-image-extra-3.13.0-93-generic 3.13.0-93.140 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/30/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.16
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 22CD
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 93.15
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd05/30/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097510405F1620180:rvnHewlett-Packard:rn22CD:rvr93.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP 15 Notebook PC
dmi.product.version: 097510405F1620180
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-package trusty

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

Title:
  package linux-image-extra-3.13.0-93-generic 3.13.0-93.140 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  cant boot up latest kernal

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.13.0-93-generic 3.13.0-93.140
  ProcVersionSignature: Ubuntu 3.19.0-65.73~14.04.1-lowlatency 3.19.8-ckt22
  Uname: Linux 3.19.0-65-lowlatency x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  conrad 2582 F pulseaudio
   /dev/snd/controlC0:  conrad 2582 F pulseaudio
  Date: Fri Aug 19 20:30:14 2016
  DpkgTerminalLog:
   Log started: 2016-08-05  23:30:50
   Log ended: 2016-08-05  23:31:28
   
   Log started: 2016-08-19  20:23:55
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-12-24 (241 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-65-lowlatency 
root=/dev/mapper/ubuntu--studio--vg-root ro nomdmonddf nomdmonisw
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-image-extra-3.13.0-93-generic 3.13.0-93.140 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 22CD
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 93.15
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd05/30/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097510405F1620180:rvnHewlett-Packard:rn22CD:rvr93.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 097510405F1620180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1504909] Re: blk_update_request: I/O error when accessing a disk that is spun down

[Felix Matouschek]

Hello Ant,

I'm not quite sure what you mean?

I'm currently using Debian Jessie with Kernel 4.6.3, the problem is
still there. So it is not limited to Ubuntu... it probably also exists
in more recent releases like 16.04...

Greetings,
Felix

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

Title:
  blk_update_request: I/O error when accessing a disk that is spun down

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have 6 3TB SATA disks that are attached via a IBM M1015 in IT mode
  and the mpt2sas driver. The filesystem is zfsonlinux.

  I can't name the exact 3.19 kernel version when this error began, but
  it was not the inital 3.19 Vivid LTS Kernel because after initally
  upgrading to 3.19 everything still worked.

  After a recent update I have the following problem:

  When disks are spun down and then accessed an error occurs which corrupts 
data.
  When the disks are finally spun up everything works as expected, also 
preventing them from spinning down works as a workaround.

  Could this be a NCQ bug?

  Drives are 5x Seagate ST3000DM001 and 1x HGST HDN724030ALE640.

  [59526.359997] sd 0:0:1:0: [sdc] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [59526.360003] sd 0:0:1:0: [sdc] CDB:
  [59526.360006] Read(16): 88 00 00 00 00 00 31 28 fd 58 00 00 00 08 00 00
  [59526.360022] blk_update_request: I/O error, dev sdc, sector 824769880
  [59544.111090] sd 0:0:0:0: [sdb] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [59544.111097] sd 0:0:0:0: [sdb] CDB:
  [59544.00] Read(16): 88 00 00 00 00 00 31 28 fd 50 00 00 00 08 00 00
  [59544.15] blk_update_request: I/O error, dev sdb, sector 824769872
  [59544.114465] sd 0:0:4:0: [sdf] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [59544.114468] sd 0:0:4:0: [sdf] CDB:
  [59544.114469] Read(16): 88 00 00 00 00 00 31 28 fd 58 00 00 00 08 00 00
  [59544.114483] blk_update_request: I/O error, dev sdf, sector 824769880
  [59552.117436] sd 0:0:3:0: [sde] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [59552.117443] sd 0:0:3:0: [sde] CDB:
  [59552.117446] Read(16): 88 00 00 00 00 00 31 28 fd b0 00 00 00 08 00 00
  [59552.117462] blk_update_request: I/O error, dev sde, sector 824769968
  [59572.951158] sd 0:0:2:0: [sdd] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [59572.951167] sd 0:0:2:0: [sdd] CDB:
  [59572.951170] Read(16): 88 00 00 00 00 00 31 28 fd b0 00 00 00 08 00 00
  [59572.951192] blk_update_request: I/O error, dev sdd, sector 824769968
  [59572.955679] sd 0:0:5:0: [sdg] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [59572.955695] sd 0:0:5:0: [sdg] CDB:
  [59572.955701] Read(16): 88 00 00 00 00 00 31 28 fd b0 00 00 00 08 00 00
  [59572.955720] blk_update_request: I/O error, dev sdg, sector 824769968
  [70357.782677] sd 0:0:4:0: [sdf] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [70357.782686] sd 0:0:4:0: [sdf] CDB:
  [70357.782690] Read(16): 88 00 00 00 00 00 85 c1 c9 08 00 00 00 08 00 00
  [70357.782712] blk_update_request: I/O error, dev sdf, sector 2244069640
  [70368.087947] sd 0:0:0:0: [sdb] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [70368.087953] sd 0:0:0:0: [sdb] CDB:
  [70368.087955] Read(16): 88 00 00 00 00 00 85 c1 c9 00 00 00 00 08 00 00
  [70368.087969] blk_update_request: I/O error, dev sdb, sector 2244069632

  lsb_release -rd:
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  Kernel Version: 3.19.0-30-generic
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Okt  8 18:46 seq
   crw-rw 1 root audio 116, 33 Okt  8 18:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/eternity--vg-swap_1
  InstallationDate: Installed on 2014-09-25 (380 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   lono wireless extensions.
   
   em1   no wireless extensions.
  MachineType: Dell Inc. PowerEdge T20
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-30-generic 
root=/dev/mapper/hostname--vg-root ro console=tty0 console=ttyS4,115200 
intel_pstate=enable cgroup_enable=memory swapaccount=1 intel_iommu=on 
enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=16M mtrr_chunk_size=64M 
i915.enable_rc6=0 nmi_watchdog=0
  ProcVersionSignature: