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

[Brad Figg]

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-8.9/modoc__4.8.0-8.9__2016-09-14_05-05-00/results-index.html

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

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

[Kernel-packages] [Bug 1457472] Re: TPACKET_V3 in Linux before 3.19 causes packet loss in libpcap

[Bug Watch Updater]

** Changed in: nmap
   Status: Unknown => New

** Changed in: tcpdump
   Status: Unknown => New

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

Title:
  TPACKET_V3 in Linux before 3.19 causes packet loss in libpcap

Status in nmap:
  New
Status in tcpdump:
  New
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Observed packet loss and major slowdown in Nmap on Ubuntu 14.04:
  https://github.com/nmap/nmap/issues/34

  Traced to this bug report for libpcap 1.5.3: https://github.com/the-
  tcpdump-group/libpcap/issues/380

  Underlying issue is a bug in the Linux kernel which was fixed in 3.19:
  https://github.com/torvalds/linux/commit/da413ee

  Please backport this patch to Ubuntu 14.04 LTS kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-53-generic 3.13.0-53.89
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nmap  12401 F pulseaudio
   /dev/snd/pcmC0D0c:   nmap  12401 F...m pulseaudio
   /dev/snd/pcmC0D0p:   nmap  12401 F...m pulseaudio
   /dev/snd/timer:  nmap  12401 f pulseaudio
  CurrentDmesg: [   25.541696] init: plymouth-upstart-bridge main process 
ended, respawning
  Date: Thu May 21 07:42:08 2015
  HibernationDevice: RESUME=UUID=e4b6770e-dcc5-445d-a445-25d9a244e204
  InstallationDate: Installed on 2015-01-01 (139 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=032922f2-3fe1-4228-8c93-8c1e9afc4289 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-53-generic N/A
   linux-backports-modules-3.13.0-53-generic  N/A
   linux-firmware 1.127.12
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/nmap/+bug/1457472/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-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]

@jsalisbury How's it looking with this bug? Are we any closer to find
the root cause? Please let me know how I can help further. I'm ready to
test whatever you throw at me :)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1457472] Re: TPACKET_V3 in Linux before 3.19 causes packet loss in libpcap

[Mike Pontillo]

I have tested this on kernel 4.4.0 (in Xenial) and I don't think the fix
that went into 3.19 fixed the entire issue.

My understanding is that since nmap uses a relatively long pcap_select()
timeout, and the packet buffers in the kernel aren't filling up fast
enough, the packet loss can still be seen.

I see that you have worked around this in nmap by disabling TPACKET_v3:

https://github.com/nmap/nmap/commit/83b9c4c939094e673705b7c270533708853891f0

I noticed that another project (which I found linked to the libpcap bug)
worked around this issue by using libpcap's immediate_mode:

https://github.com/teclo/flow-
disruptor/commit/3376d049fc5280aedccc42fc6e090c32c0c4a128

Would you consider trying this same workaround in nmap, since it seems
more general than forcing TPACKET_V3 to be disabled? (That is, only
users who compile nmap from source and use  "./configure --with-
libpcap=included" can currently use the workaround.)

** Bug watch added: github.com/nmap/nmap/issues #34
   https://github.com/nmap/nmap/issues/34

** Also affects: linux via
   https://github.com/nmap/nmap/issues/34
   Importance: Unknown
   Status: Unknown

** Project changed: linux => nmap

** Bug watch added: github.com/the-tcpdump-group/libpcap/issues #380
   https://github.com/the-tcpdump-group/libpcap/issues/380

** Also affects: tcpdump via
   https://github.com/the-tcpdump-group/libpcap/issues/380
   Importance: Unknown
   Status: Unknown

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

Title:
  TPACKET_V3 in Linux before 3.19 causes packet loss in libpcap

Status in nmap:
  Unknown
Status in tcpdump:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Observed packet loss and major slowdown in Nmap on Ubuntu 14.04:
  https://github.com/nmap/nmap/issues/34

  Traced to this bug report for libpcap 1.5.3: https://github.com/the-
  tcpdump-group/libpcap/issues/380

  Underlying issue is a bug in the Linux kernel which was fixed in 3.19:
  https://github.com/torvalds/linux/commit/da413ee

  Please backport this patch to Ubuntu 14.04 LTS kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-53-generic 3.13.0-53.89
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nmap  12401 F pulseaudio
   /dev/snd/pcmC0D0c:   nmap  12401 F...m pulseaudio
   /dev/snd/pcmC0D0p:   nmap  12401 F...m pulseaudio
   /dev/snd/timer:  nmap  12401 f pulseaudio
  CurrentDmesg: [   25.541696] init: plymouth-upstart-bridge main process 
ended, respawning
  Date: Thu May 21 07:42:08 2015
  HibernationDevice: RESUME=UUID=e4b6770e-dcc5-445d-a445-25d9a244e204
  InstallationDate: Installed on 2015-01-01 (139 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=032922f2-3fe1-4228-8c93-8c1e9afc4289 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-53-generic N/A
   linux-backports-modules-3.13.0-53-generic  N/A
   linux-firmware 1.127.12
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/nmap/+bug/1457472/+subscriptions

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

[Kernel-packages] [Bug 1609913] onza (amd64) - tests ran: 5, failed: 3

[Brad Figg]

tests ran:   5, failed: 3;
  
http://kernel.ubuntu.com/testing/4.8.0-8.9/onza__4.8.0-8.9__2016-09-14_02-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/1609913

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

[Kernel-packages] [Bug 1609913] onibi (amd64) - tests ran: 5, failed: 3

[Brad Figg]

tests ran:   5, failed: 3;
  
http://kernel.ubuntu.com/testing/4.8.0-8.9/onibi__4.8.0-8.9__2016-09-14_03-01-00/results-index.html

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

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

[Kernel-packages] [Bug 1609913] s2lp6g002 (s390x.zKVM) - tests ran: 65, failed: 65

[Brad Figg]

tests ran:  65, failed: 65;
  
http://kernel.ubuntu.com/testing/4.8.0-8.9/s2lp6g002__4.8.0-8.9__2016-09-14_04-19-00/results-index.html

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

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

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

[mforonda]

My post is at https://www.spinics.net/lists/linux-acpi/msg69038.html
though bugzilla is currently getting more attention.

-- 
You 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:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  My HP ENVY m4-1015dx Notebook PC can't read the battery state. 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.

  This has been reproducible on kernel 3.19.

  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.

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   m  3446 F...m pulseaudio
   /dev/snd/controlC1:  m  3446 F pulseaudio
   /dev/snd/controlC0:  m  3446 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=bed51ac4-b6b1-43fc-8304-7b7b4a88b7bb
  InstallationDate: Installed on 2016-08-06 (26 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP ENVY m4 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=5a61dc86-7c12-4f8c-9f3c-717f399c2afc ro quiet splash 
acpi_backlight=vendor acpi_osi=Linux "acpi_osi=!Windows 2012" vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  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
  Tags:  xenial
  Uname: Linux 4.4.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/04/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.18
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 18EE
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 78.0D
  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.18:bd06/04/2014:svnHewlett-Packard:pnHPENVYm4NotebookPC:pvr0877100022345B10001620130:rvnHewlett-Packard:rn18EE:rvr78.0D:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY m4 Notebook PC
  dmi.product.version: 0877100022345B10001620130
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/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 1599110] Re: Blank screen 90 sec boot delay

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

Title:
  Blank screen 90 sec boot delay

Status in linux package in Ubuntu:
  Expired

Bug description:
  Tried to document this problem under bug 1559595 but have been
  requested to submit a new bug.

  Been having an intermittent problem booting (started on 16.04 and
  continues across multiple system rebuilds and 16.10) where just after
  entering my PW the screen goes blank for about 90 seconds.  After that
  interval the normal desktop appears and all is well.  Will supply a
  journal boot log of a failing boot (boot_0704.txt) and a normal boot
  log (boot_0704_good.txt).  Do see in the failing log and all others
  that I have looked at a gnome-session timeout (time 06:16:41).  Don't
  see this type of entry in the good log but haven't examined many non-
  failure logs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.4.0-30-generic 4.4.0-30.49
  ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
  Uname: Linux 4.4.0-30-generic x86_64
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  3761 F pulseaudio
   /dev/snd/controlC2:  cliff  3761 F pulseaudio
   /dev/snd/controlC1:  cliff  3761 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Jul  5 06:19:34 2016
  HibernationDevice: RESUME=UUID=51013622-8d36-45f8-89d8-8dc36d3b5ac5
  InstallationDate: Installed on 2016-05-30 (35 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160529)
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-30-generic 
root=UUID=375f8904-0bcb-4f0b-bd19-2a200ca1db5a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-30-generic N/A
   linux-backports-modules-4.4.0-30-generic  N/A
   linux-firmware1.158
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2012
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2012:bd09/30/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1602905] Re: non -working Elan Touchpad

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

Title:
  non -working Elan Touchpad

Status in linux package in Ubuntu:
  Expired

Bug description:
  After a direct install by USB, my Toshiba Satellite Radius P55W-B laptop runs 
ok except for the Elan Touchpad witch dosn't work in any way. I have a 
bluetooth mous workiing OK. I have bin unable to find a driver online.
  Release: 16.04
  Unable to locate package pkgname

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

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

[Kernel-packages] [Bug 1434136] Re: HP Pavilion 13-b208tu fails to boot with F.26 bios, PSOD

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

Title:
  HP Pavilion 13-b208tu fails to boot with F.26 bios, PSOD

Status in linux package in Ubuntu:
  Expired

Bug description:
  While trying to fix Bug #1432659, I updated the HP Pavilion 13-b208tu bios to 
the latest available on the HP website (F.26):
  
http://support.hp.com/us-en/drivers/selfservice/HP-Pavilion-13-b200-Notebook-PC-series/7527795/model/7597682

  After the update, the laptop no longer boots Ubuntu 14.10 or Ubuntu
  15.04 (Ubuntu 15.04 from the hard drive, Ubuntu 14.10 using a LiveCD).
  The grub menu is available and works, the kernel loads, the initrd
  step works, and then it hangs hard and requires power cycling.

  The required information for a kernel bug report can be found in Bug
  #1432659, from the original shipped F.23 bios. I obviously can't
  attach information with the F.26 bios loaded.

  I can confirm that the bios update worked, and I have repeated it
  twice. HP diagnostics give the system a green light, and I can boot to
  FreeDOS as normal. I'll leave the system unbootable with the F.26 bios
  for a while in case someone can help me diagnose further from grub.

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

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

[Kernel-packages] [Bug 1609913] s2lp6g002 (s390x.zKVM) - tests ran: 2, failed: 0

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-8.9/s2lp6g002__4.8.0-8.9__2016-09-14_04-16-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/1609913

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

[Kernel-packages] [Bug 1609913] s2lp6g002 (s390x.zKVM) - tests ran: 83, failed: 4

[Brad Figg]

tests ran:  83, failed: 4;
  
http://kernel.ubuntu.com/testing/4.8.0-8.9/s2lp6g002__4.8.0-8.9__2016-09-14_03-49-00/results-index.html

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

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

[Kernel-packages] [Bug 1609913] modoc (ppc64el) - tests ran: 35, failed: 4

[Brad Figg]

tests ran:  35, failed: 4;
  
http://kernel.ubuntu.com/testing/4.8.0-8.9/modoc__4.8.0-8.9__2016-09-14_03-23-00/results-index.html

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

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

[Kernel-packages] [Bug 1609913] s2lp6g002 (s390x.zKVM) - tests ran: 136, failed: 27

[Brad Figg]

tests ran: 136, failed: 27;
  
http://kernel.ubuntu.com/testing/4.8.0-8.9/s2lp6g002__4.8.0-8.9__2016-09-14_03-28-00/results-index.html

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

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

[Kernel-packages] [Bug 1609913] s2lp4 (s390x.LPAR) - tests ran: 65, failed: 65

[Brad Figg]

tests ran:  65, failed: 65;
  
http://kernel.ubuntu.com/testing/4.8.0-8.9/s2lp4__4.8.0-8.9__2016-09-14_03-40-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/1609913

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

[Kernel-packages] [Bug 1609606] Re: Mic mute hotkey does not work on usb keyboard [03f0:2f4a]

[AceLan Kao]

The hotkey works on 4.4.0-38.57

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

Title:
  Mic mute hotkey does not work on usb keyboard [03f0:2f4a]

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

Bug description:
  Press the MIC mute function key on the USB keyboard [03f0:2f4a]
  doesn't emit any keyevent nor acpi event.

  T:  Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 23 Spd=1.5 MxCh= 0
  D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
  P:  Vendor=03f0 ProdID=2f4a Rev=00.10
  S:  Manufacturer=Chicony
  S:  Product=HP Business Slim Keyboard
  C:  #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=100mA
  I:  If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=01 Driver=usbhid
  I:  If#= 1 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1609606/+subscriptions

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

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

[Brad Figg]

tests ran:  35, failed: 4;
  
http://kernel.ubuntu.com/testing/4.8.0-8.9/dwalin__4.8.0-8.9__2016-09-14_03-13-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/1609913

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

[Kernel-packages] [Bug 1609913] s2lp4 (s390x.LPAR) - tests ran: 2, failed: 0

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-8.9/s2lp4__4.8.0-8.9__2016-09-14_03-37-00/results-index.html

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

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

[Kernel-packages] [Bug 1609913] s2lp4 (s390x.LPAR) - tests ran: 83, failed: 5

[Brad Figg]

tests ran:  83, failed: 5;
  
http://kernel.ubuntu.com/testing/4.8.0-8.9/s2lp4__4.8.0-8.9__2016-09-14_03-11-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/1609913

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

[Kernel-packages] [Bug 1609913] s2lp6g002 (s390x.zKVM) - tests ran: 19, failed: 7

[Brad Figg]

tests ran:  19, failed: 7;
  
http://kernel.ubuntu.com/testing/4.8.0-8.9/s2lp6g002__4.8.0-8.9__2016-09-14_02-49-00/results-index.html

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

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

[Kernel-packages] [Bug 1609913] s2lp4 (s390x.LPAR) - tests ran: 136, failed: 27

[Brad Figg]

tests ran: 136, failed: 27;
  
http://kernel.ubuntu.com/testing/4.8.0-8.9/s2lp4__4.8.0-8.9__2016-09-14_02-51-00/results-index.html

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

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

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

[Brad Figg]

tests ran:   2, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-8.9/modoc__4.8.0-8.9__2016-09-14_02-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/1609913

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

[Kernel-packages] [Bug 1609913] s2lp4 (s390x.LPAR) - tests ran: 19, failed: 7

[Brad Figg]

tests ran:  19, failed: 7;
  
http://kernel.ubuntu.com/testing/4.8.0-8.9/s2lp4__4.8.0-8.9__2016-09-14_02-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/1609913

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

[Kernel-packages] [Bug 1609913] s2lp6g002 (s390x.zKVM) - tests ran: 32, failed: 1

[Brad Figg]

tests ran:  32, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-8.9/s2lp6g002__4.8.0-8.9__2016-09-14_02-15-00/results-index.html

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

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

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

[Jason Gambrel]

Still freezing after removing tlp.  Added "acpi_osi='!Windows 2013'
acpi_osi='!Windows 2012'" to grub configuration.

-- 
You 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 1609913] onibi (i386) - tests ran: 10, failed: 2

[Brad Figg]

tests ran:  10, failed: 2;
  
http://kernel.ubuntu.com/testing/4.8.0-8.9/onibi__4.8.0-8.9__2016-09-14_01-32-00/results-index.html

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

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

[Kernel-packages] [Bug 1617900] Re: Headset mic detection on some variants of Dell Inspiron 5468

[Shrirang Bagul]

Fixed in oem-audio-hda-daily-dkms_0.201608310502~ubuntu16.04.1_all.deb

** Attachment added: 
"oem-audio-hda-daily-dkms_0.201608310502-ubuntu16.04.1_all.deb"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1617900/+attachment/4740507/+files/oem-audio-hda-daily-dkms_0.201608310502-ubuntu16.04.1_all.deb

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

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

Title:
  Headset mic detection on some variants of Dell Inspiron 5468

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  On some Dell Inspiron 5468 variants, headset mic device is not
  detected.

  This bug is used for tracking purposes, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1617900/+subscriptions

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

[Kernel-packages] [Bug 1609913] onza (i386) - tests ran: 10, failed: 2

[Brad Figg]

tests ran:  10, failed: 2;
  
http://kernel.ubuntu.com/testing/4.8.0-8.9/onza__4.8.0-8.9__2016-09-14_01-04-00/results-index.html

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

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

[Kernel-packages] [Bug 1609913] s2lp4 (s390x.LPAR) - tests ran: 10, failed: 2

[Brad Figg]

tests ran:  10, failed: 2;
  
http://kernel.ubuntu.com/testing/4.8.0-8.9/s2lp4__4.8.0-8.9__2016-09-14_01-33-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/1609913

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

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

[Brad Figg]

tests ran:  10, failed: 2;
  
http://kernel.ubuntu.com/testing/4.8.0-8.9/modoc__4.8.0-8.9__2016-09-14_01-02-00/results-index.html

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

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

[Kernel-packages] [Bug 1389305] Re: sudo doesn't work on unprivileged lxc container on top of ecryptfs

[Jean-Pierre van Riel]

Update on the previous comment, I realised the issue was the the
partition where /var was mounted to hat nosuid set. Seems /var/lib/lxc
must allow for the suid bit to be set. The problem is that people often
have /home mounted with nosuid as a normal security precaution, so this
effects running unprivileged containers as well.

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

Title:
  sudo doesn't work on unprivileged lxc container on top of ecryptfs

Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in lxc package in Ubuntu:
  Triaged

Bug description:
  On Ubuntu 14.04 64 bit, after adding a user into an unprivileged
  container, the sudo complains that:

  $ sudo su
  sudo: effective uid is not 0, is /usr/bin/sudo on a file system with the 
'nosuid' option set or an NFS file system without root privileges?

  To reproduce:

  1. Download and install the Ubuntu amd64 minimalcd
  2. Install lxc on it and openssh for convenience.
  3. follow 
https://www.stgraber.org/2014/01/17/lxc-1-0-unprivileged-containers/ ; 
specifically do:
   a) sudo usermod --add-subuids 10-165536 $USER
   b) sudo usermod --add-subgids 10-165536 $USER
   c) sudo chmod +x $HOME
   d) create the file  ~/.config/lxc/default.conf with the following 
contents:
  lxc.include = /etc/lxc/default.conf
  lxc.id_map = u 0 10 65536
  lxc.id_map = g 0 10 65536
   e) echo "$USER veth lxcbr0 10" | sudo tee /etc/lxc/lxc-usernet
  (restart is not required)
  4. Create the container with
  lxc-create -t download -n p1 -- -d ubuntu -r trusty -a amd64
  5. Install openssh-server in the container:
  lxc-start -d -n p1
  lxc-attach -n p1 -- apt-get install openssh-server
  6. Add a user "adam" with the group sudo
  lxc-attach -n p1 -- adduser adam sudo
  7. Set a password for the user
  8. Log in via ssh (and provide the password from step 7)
  ssh p1@adam
  9. On the p1:
  adam@p1$ sudo su
  sudo: effective uid is not 0, is /usr/bin/sudo on a file system with the 
'nosuid' option set or an NFS file system without root privileges?

  I expected it to make change the user to root.

  lxc version: 1.0.3-0ubuntu3
  $cat ~/.cache/lxc/download/ubuntu/trusty/amd64/default/build_id
  20141101_03:49
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  DistroRelease: Ubuntu 14.04
  EcryptfsInUse: Yes
  Package: lxc
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Tags:  trusty
  Uname: Linux 3.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1389305/+subscriptions

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

[Kernel-packages] [Bug 1609913] s2lp4 (s390x.LPAR) - tests ran: 32, failed: 1

[Brad Figg]

tests ran:  32, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-8.9/s2lp4__4.8.0-8.9__2016-09-14_00-57-00/results-index.html

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

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

[Kernel-packages] [Bug 1609913] dwalin (amd64) - tests ran: 10, failed: 2

[Brad Figg]

tests ran:  10, failed: 2;
  
http://kernel.ubuntu.com/testing/4.8.0-8.9/dwalin__4.8.0-8.9__2016-09-14_00-45-00/results-index.html

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

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

[Kernel-packages] [Bug 1623194] Re: Permanent I/O from kworker and ecryptfs

[Sworddragon]

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

Title:
  Permanent I/O from kworker and ecryptfs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 16.10 dev and after upgrading from upstart to systemd
  (231-6) I'm noticing that if the system is on idle (even if only
  booted to the login screen) there are permanent I/O activities on my
  hard disk drive. On making a look with inotifywait this happens by
  permanently accessing files in /home/.ecryptfs/sworddragon/.Private
  (but no I/O appears at the transparent mountpoint at
  /home/sworddragon). On making a look with iotop the only I/O
  activities are comming from kworker (and sometimes jbd2) at this time.

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

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

[Kernel-packages] [Bug 1618678] Re: Disk Device Driver Reported Error: DID_ERROR ... DRIVER SENSE

[Raymond]

Christopher, we (Andrew and Raymond) just verified that this bug still
manifests itself in the 4.8-rc5 kernel (see below). Please let us know
if you need any further information.

Thanks!

---
Sep 13 18:09:59 penbrook2 kernel: [  670.050331] sd 4:0:0:0: [sdc] tag#0 FAILED 
Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE

Sep 13 18:09:59 penbrook2 kernel: [  670.050336] sd 4:0:0:0: [sdc] tag#0
Sense Key : Hardware Error [current] [descriptor]

Sep 13 18:09:59 penbrook2 kernel: [  670.050339] sd 4:0:0:0: [sdc] tag#0
Add. Sense: No additional sense information

Sep 13 18:09:59 penbrook2 kernel: [  670.050343] sd 4:0:0:0: [sdc] tag#0
CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00
00 e5 00

Sep 13 18:09:59 penbrook2 kernel: [  670.559187] sd 4:0:0:0: [sdc] tag#0
FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE

Sep 13 18:09:59 penbrook2 kernel: [  670.559194] sd 4:0:0:0: [sdc] tag#0
Sense Key : Hardware Error [current] [descriptor]

Sep 13 18:09:59 penbrook2 kernel: [  670.559196] sd 4:0:0:0: [sdc] tag#0
Add. Sense: No additional sense information

Sep 13 18:09:59 penbrook2 kernel: [  670.559201] sd 4:0:0:0: [sdc] tag#0 CDB: 
ATA command pass through(12)/Blank a1 06 20 da 00 00 4f c2 00 b0 00 00
...

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

Title:
  Disk Device Driver Reported Error: DID_ERROR ... DRIVER SENSE

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The Ubuntu 16.04.1 LTS upgrade from kernel 4.4.0-21 to 4.4.0-34
  introduced the following periodic error message sequence reported in
  dmesg/syslog:

  ...
  sd 4:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_SENSE
  sd 4:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current] [descriptor] 
  sd 4:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
  sd 4:0:0:0: [sdc] tag#0 CDB: ATA command pass through(16) 85 06 2c 00 da 00 
00 00 00 00 4f 00 c2 00 b0 00 
  sd 4:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_SENSE
  sd 4:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current] [descriptor] 
  sd 4:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
  sd 4:0:0:0: [sdc] tag#0 CDB: ATA command pass through(16) 85 06 20 00 00 00 
00 00 00 00 00 00 00 00 e5 00 
  sd 4:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_SENSE
  sd 4:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current] [descriptor] 
  sd 4:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
  sd 4:0:0:0: [sdc] tag#0 CDB: ATA command pass through(12)/Blank a1 06 20 da 
00 00 4f c2 00 b0 00 00 
  ...

  These repeat at precisely five and ten minute intervals but appear to
  result in no data corruption, nor performance degradation on the
  external USB drive.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   rap3412 F...m pulseaudio
   /dev/snd/pcmC1D0p:   rap3412 F...m pulseaudio
   /dev/snd/controlC1:  rap3412 F pulseaudio
   /dev/snd/controlC0:  rap3412 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug 30 19:48:43 2016
  HibernationDevice: RESUME=UUID=bb098361-baff-41e3-bf95-dad938b5d42c
  InstallationDate: Installed on 2016-08-10 (21 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s9no wireless extensions.
  MachineType: ECS K8M890M-M
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=d38a2b9b-2da3-48e2-b5f8-a464f49a5dc5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/29/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080013
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: K8M890M-M
  dmi.board.vendor: ECS
  dmi.board.version: 1.X
  dmi.chassis.asset.tag: 0123ABC
  dmi.chassis.type: 3
  dmi.chassis.vendor: ECS
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080013:bd12/29/2006:svnECS:pnK8M890M-M:pvr1.X:rvnECS:rnK8M890M-M:rvr1.X:cvnECS:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: K8M890M-M
  

[Kernel-packages] [Bug 1586195] Re: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug

[zwpwjwtz]

I tested following versions of Ubuntu Live ISOs:

- 15.10 (kernel 4.2.0-16-generic)
- 15.04 (kernel 3.19.0-15-generic)
- 14.10 (kernel 3.16.0-23-generic)
- 14.04.5 (kernel 4.4.0-31-generic)

Both 15.04 and 14.10 work fine. But I noticed some differences showed in
dmesg: "eth0" came up directly without being renamed to something like
"enp0s".

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

Title:
  Realtek 8153-based ethernet adapter on usb3 eventually stops working
  requiring unplug/replug

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

Bug description:
  Seems to be paired with dmesg entries like this on the trusty kernel:

  [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed.
  [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed.
  [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, 
RTL8153 ECM Device
  [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed.
  [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed.
  [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM
  [24763.809953] .
  [24763.810579] usb 4-4.2: USB disconnect, device number 7
  [24763.940765] userif-1: sent link down event.
  [24763.940769] userif-1: sent link up event.

  And like this on mainline:

  [  259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd
  [  259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153
  [  259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=6
  [  259.752920] usb 4-3: Product: USB 10/100/1000 LAN
  [  259.752921] usb 4-3: Manufacturer: Realtek
  [  259.752922] usb 4-3: SerialNumber: 0100
  [  259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd
  [  259.993254] r8152 4-3:1.0 eth0: v1.08.3
  [  260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [  296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  [  300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71
  [  302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM
  [  302.832697] .
  [  302.833086] usb 4-3: USB disconnect, device number 4

  Mainline version fyi:
  [0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc 
version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 
23:32:59 UTC 2016

  I also get a similar message about 'Failed to disable LTM' if I just
  unplug the device before the breakage occurs.

  I've attached lsusb before the breakage occurs (so you can see the
  device) from the mainline kernel.

  Interestingly it appears the drivers on trusty and wily/mainline are
  different (r815x vs r8152) yet still exhibit similar troubles. I'm
  still digging around to try and figure out why this doesn't seem to be
  working, but I was wondering if you all had any idea what might be
  going pear-shaped here.

  Thanks!

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

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

[Kernel-packages] [Bug 1616318] Re: System hang when plug/pull USB 3.1 key via thunderbolt port over 5 times

[AceLan Kao]

With kernel 4.4.0-38.57, I can't reproduce this issue.

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

Title:
   System hang when plug/pull USB 3.1 key via thunderbolt port over 5
  times

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

Bug description:
  Steps:
  1) Install Ubuntu 16.04
  2) Enter to Dekstop.
  3) Insert the USB 3.1 key in the thunderbolt port.
  4) Remove the USB 3.1 key from the thunderbolt port.
  5) Insert the USB 3.1 key in the thunderbolt port.

  Expected results: Can detect the USB 3.1 key and system will not hang.

  Actual results: System Hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1616318/+subscriptions

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

[Kernel-packages] [Bug 1623194] 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 1623194

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

Title:
  Permanent I/O from kworker and ecryptfs

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using Ubuntu 16.10 dev and after upgrading from upstart to systemd
  (231-6) I'm noticing that if the system is on idle (even if only
  booted to the login screen) there are permanent I/O activities on my
  hard disk drive. On making a look with inotifywait this happens by
  permanently accessing files in /home/.ecryptfs/sworddragon/.Private
  (but no I/O appears at the transparent mountpoint at
  /home/sworddragon). On making a look with iotop the only I/O
  activities are comming from kworker (and sometimes jbd2) at this time.

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

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

[Kernel-packages] [Bug 1623194] Re: Permanent I/O from kworker and ecryptfs

[Sworddragon]

Since this ticket got changed from systemd to linux it seems to be a
kernel bug. I wonder what the change from upstart to systemd caused to
reveal this issue. Anyways, in this case it could make more sense to
forward this to upstream so I have done this:
https://bugzilla.kernel.org/show_bug.cgi?id=156761

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

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

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

Title:
  Permanent I/O from kworker and ecryptfs

Status in linux package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 16.10 dev and after upgrading from upstart to systemd
  (231-6) I'm noticing that if the system is on idle (even if only
  booted to the login screen) there are permanent I/O activities on my
  hard disk drive. On making a look with inotifywait this happens by
  permanently accessing files in /home/.ecryptfs/sworddragon/.Private
  (but no I/O appears at the transparent mountpoint at
  /home/sworddragon). On making a look with iotop the only I/O
  activities are comming from kworker (and sometimes jbd2) at this time.

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

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

[Kernel-packages] [Bug 1623143] Re: Linux container does not take same cpu configuration as kernet's hosts

[Alberto Salvia Novella]

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

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

Title:
  Linux container does not take same cpu configuration as kernet's hosts

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I configured cpu affinity on a ubuntu 16.04 with kernel version 
"4.4.0-36-generic" on a host containing 3 cpus:
  on /etc/default/grub:
  GRUB_CMDLINE_LINUX_DEFAULT="isolcpus=0"

  update-grub

  reboot

  The output of "cat /proc/self/status" :
  ubuntu@ubuntu:~$ cat /proc/self/status
   .
   .
   .
  Cpus_allowed: 6
  Cpus_allowed_list:1-2
  Mems_allowed: ,0001
  Mems_allowed_list:0
  voluntary_ctxt_switches:  0
  nonvoluntary_ctxt_switches:   1

  When I create an lxd container in this host using these commands:

    lxc launch ubuntu:14.04 my-ubuntu

  And access to this container using:

    lxc exec my-ubuntu -- /bin/bash

  The output of "cat /proc/self/status" :
    .
    .
    .
  Cpus_allowed: 7
  Cpus_allowed_list:0-2
  Mems_allowed: ,0001
  Mems_allowed_list:0
  voluntary_ctxt_switches:  0
  nonvoluntary_ctxt_switches:   4

  Result: Container's process doesn't take same configuration as host's process.
  Host process use  2 cpus:  Cpus_allowed_list: 1-2
  Container process use 3 cpus: Cpus_allowed_list:  0-2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-36-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Tue Sep 13 18:36:29 2016
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-08-04 (40 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic 
root=/dev/mapper/username--vg-root ro isolcpus=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-wily
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-wily:cvnQEMU:ct1:cvrpc-i440fx-wily:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-wily
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1606030] Re: System reboots instead of shutting down if xhci is enabled in BIOS and USB hub is connected

[Hasan Mahmood]

As per Mathias's email, setting xhci_hcd.quirks=0x0004b810 solves this
problem. See message here: http://www.spinics.net/lists/linux-
usb/msg146618.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/1606030

Title:
  System reboots instead of shutting down if xhci is enabled in BIOS and
  USB hub is connected

Status in linux package in Ubuntu:
  Triaged

Bug description:
  When I connect the usb hub built into my monitor
  (http://www.samsung.com/uk/support/model/LS27D85KTSN/XU), the system
  will reboot instead of shutting down when I do a shut down. If I
  disable XCHI in the BIOS, the problem does not happen. If I disconnect
  the hub and enable XHCI, the problem does not occur.

  Release info:

  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  Outputs of various commands are attached.

  Possibly related bugs:
  https://bugzilla.kernel.org/show_bug.cgi?id=76291
  https://bugzilla.kernel.org/show_bug.cgi?id=66171

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50 [modified: 
boot/vmlinuz-4.4.0-31-generic]
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hmahmood   3688 F pulseaudio
   /dev/snd/controlC0:  hmahmood   3688 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Jul 24 11:18:09 2016
  HibernationDevice: RESUME=UUID=0477be12-31b0-423b-9277-22490ca71561
  InstallationDate: Installed on 2016-07-23 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=503e032f-c205-4594-a47f-cdc58ffa5dba ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/06/2016
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0358.2016.0606.1423
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-503
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0358.2016.0606.1423:bd06/06/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-503:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1562093] Re: [Dell Inc. XPS 13 9350] hibernate/resume failure

[s.illes79]

I can confirm it works fine on developer edition - this has the intel
wireless chip.

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

Title:
  [Dell Inc. XPS 13 9350] hibernate/resume failure

Status in linux package in Ubuntu:
  Expired

Bug description:
  sudo pm-hibernate failed.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-15-generic 4.4.0-15.31
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1491 F pulseaudio
johan  2042 F pulseaudio
  Date: Fri Mar 25 18:30:46 2016
  DuplicateSignature: hibernate/resume:Dell Inc. XPS 13 9350:1.2.3
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=d7490964-39a3-44ea-aded-1cceaead466d
  InstallationDate: Installed on 2016-01-10 (74 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterpreterPath: /usr/bin/python3.5
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia 
   Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   PATH=(custom, no user)
   LANG=sv_SE.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-15-generic 
root=/dev/mapper/lvm--vg-ubuntu--root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  Title: [Dell Inc. XPS 13 9350] hibernate/resume failure
  UpgradeStatus: Upgraded to xenial on 2016-02-09 (44 days ago)
  UserGroups:
   
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 0VM5NC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0VM5NC:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04

[Mike Rushton]

** Attachment added: "alpine.xml"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4740352/+files/alpine.xml

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

Title:
  memory_stress_ng failing for Power architecture for 16.04

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

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

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

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04

[Mike Rushton]

** Attachment added: "gulpin.xml"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4740353/+files/gulpin.xml

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

Title:
  memory_stress_ng failing for Power architecture for 16.04

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

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

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

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04

[Mike Rushton]

** Attachment added: "tuleta.xml"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4740354/+files/tuleta.xml

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

Title:
  memory_stress_ng failing for Power architecture for 16.04

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

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

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

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04

[Mike Rushton]

1. Can we get the configurations of the machines.

XML files for all 4 machines with hardware information from the
certification process will be attached in the next few comments


2. The first column is the number of times the test ran?

Yes


4. Did any of the tests result in system hang? Can we find out from the summary?

All failed tests failed with a complete system hang. The only way to
recover would be to reboot.

** Attachment added: "binacle.xml"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4740351/+files/binacle.xml

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

Title:
  memory_stress_ng failing for Power architecture for 16.04

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

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

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

[Kernel-packages] [Bug 1623187] Re: initramfs includes qle driver, but not firmware

[dann frazier]

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: linux (Ubuntu)
 Assignee: dann frazier (dannf) => (unassigned)

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

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

Title:
  initramfs includes qle driver, but not firmware

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

Bug description:
  [Impact]
  The qle driver for the Qlogic FastLinQ QL45000 Series 40GbE Adapter doesn't 
find devices. This is because the driver, by default, is loaded by the 
initramfs, and the initramfs does not contain the required firmware blob. The 
root cause is that the driver does not use implement the MODULE_FIRMWARE 
macro(), which is required for initramfs-tools to find and pre-load the 
required firmware.

  [Test Case]
  Install a system with a Qlogic FastLinQ QL45000 Series 40GbE Adapter. On 
failure, dmesg will show:

  [ 5.934190] qede 0009:90:00.0: Direct firmware load for 
qed/qed_init_values_zipped-8.4.2.0.bin failed with error -2
  [ 5.934208] [qed_slowpath_start:741()]Failed to find fw file - 
/lib/firmware/qed/qed_init_values_zipped-8.4.2.0.bin
  [ 5.934280] qede: probe of 0009:90:00.0 failed with error -2
  [ 5.934353] qede 0009:90:00.1: enabling device ( -> 0002)
  [ 5.935115] qede 0009:90:00.1: Direct firmware load for 
qed/qed_init_values_zipped-8.4.2.0.bin failed with error -2
  [ 5.935139] [qed_slowpath_start:741()]Failed to find fw file - 
/lib/firmware/qed/qed_init_values_zipped-8.4.2.0.bin
  [ 5.935236] qede: probe of 0009:90:00.1 failed with error -2

  [Regression Risk]
  Fix is upstream and the macro usage is well defined.

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

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

[Kernel-packages] [Bug 1623194] 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 1623194

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

Title:
  Permanent I/O from kworker and ecryptfs

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using Ubuntu 16.10 dev and after upgrading from upstart to systemd
  (231-6) I'm noticing that if the system is on idle (even if only
  booted to the login screen) there are permanent I/O activities on my
  hard disk drive. On making a look with inotifywait this happens by
  permanently accessing files in /home/.ecryptfs/sworddragon/.Private
  (but no I/O appears at the transparent mountpoint at
  /home/sworddragon). On making a look with iotop the only I/O
  activities are comming from kworker (and sometimes jbd2) at this time.

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

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

[Kernel-packages] [Bug 1623194] Re: Permanent I/O from kworker and ecryptfs

[Martin Pitt]

** Summary changed:

- Permanent I/O from kworker since migrated to systemd
+ Permanent I/O from kworker and ecryptfs

** Package changed: systemd (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/1623194

Title:
  Permanent I/O from kworker and ecryptfs

Status in linux package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 16.10 dev and after upgrading from upstart to systemd
  (231-6) I'm noticing that if the system is on idle (even if only
  booted to the login screen) there are permanent I/O activities on my
  hard disk drive. On making a look with inotifywait this happens by
  permanently accessing files in /home/.ecryptfs/sworddragon/.Private
  (but no I/O appears at the transparent mountpoint at
  /home/sworddragon). On making a look with iotop the only I/O
  activities are comming from kworker (and sometimes jbd2) at this time.

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

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

[Kernel-packages] [Bug 1623194] [NEW] Permanent I/O from kworker and ecryptfs

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I'm using Ubuntu 16.10 dev and after upgrading from upstart to systemd
(231-6) I'm noticing that if the system is on idle (even if only booted
to the login screen) there are permanent I/O activities on my hard disk
drive. On making a look with inotifywait this happens by permanently
accessing files in /home/.ecryptfs/sworddragon/.Private (but no I/O
appears at the transparent mountpoint at /home/sworddragon). On making a
look with iotop the only I/O activities are comming from kworker (and
sometimes jbd2) at this time.

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

-- 
Permanent I/O from kworker and ecryptfs
https://bugs.launchpad.net/bugs/1623194
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 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Eric Desrochers]

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

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

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Invalid
Status in linux-lts-xenial source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux-lts-xenial source package in Xenial:
  Invalid
Status in linux source package in Yakkety:
  Fix Released
Status in linux-lts-xenial source package in Yakkety:
  Invalid

Bug description:
  [Impact]

  At boot-time, the kernel will panic somewhere in
  'blk_mq_register_disk', a snippet of the track is below, and full
  panic dump is attached. The panic dump was collected via serial
  console, as the kernel panics so early that we cannot kdump it.

  [ 2.650512] [] blk_mq_register_disk+0xa6/0x160
  [ 2.656675] [] blk_register_queue+0xb4/0x160
  [ 2.662661] [] add_disk+0x1ce/0x490
  [ 2.667869] [] loop_add+0x1f0/0x270

  [Test Case]

  At boot-time, the kernel will panic somewhere in
  'blk_mq_register_disk', a snippet of the track is below, and full
  panic dump is attached.

  [Regression Potential]

   * Fix implemented upstream starting with v4.6-rc1

   * The fix is fairly straightfoward given the stack trace.

   * The fix is hard to verify, but user "Proton" was able to confirmed
  that upstream mainline 4.6-rc1 solve the situation and that the test
  kernel I have provided including the fix solves this particular
  problem as well.

  Confirmation by Proton :
  
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1572630/comments/23

  [Other Info]

   * https://lkml.org/lkml/2016/3/16/40
   * 
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=e0e827b9
   * 
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=897bb0c7

  [Original Description]
  We discovered a pretty serious regression introduced in 4.4.0-18.

  At boot-time, the kernel will panic somewhere in
  'blk_mq_register_disk', a snippet of the track is below, and full
  panic dump is attached. The panic dump was collected via serial
  console, as the kernel panics so early that we cannot kdump it.

  [2.650512]  [] blk_mq_register_disk+0xa6/0x160
  [2.656675]  [] blk_register_queue+0xb4/0x160
  [2.662661]  [] add_disk+0x1ce/0x490
  [2.667869]  [] loop_add+0x1f0/0x270

  This seems somewhat similar to https://lkml.org/lkml/2016/3/16/40, but
  the trace is not identical.

  We discovered this issue when we were experimenting with linux-
  generic-lts-xenial from trusty-updates on a 14.04 installation. When
  we installed it, 4.4.0-15 was the current package, and it worked fine
  and provided a large amount of improvements for us. Background
  security updates installed 4.4.0-18, and this updated and grub and
  became the default kernel. On a reboot, the node panics about 2
  seconds in, resulting in a machine in a dead state. We were able to
  boot a rescue image and roll bac kto 4.4.0-15, which works nicely. We
  currently have pinning on 4.4.0-15 to prevent this problem from coming
  back, but would prefer to see the problem fixed.

  I'll attach lspci, lshw, and dmidecode for our hardware as well, but
  this is happening on pretty vanilla supermicro nodes. We are able to
  consistently reproduce it on our hardware. It is not reproducible in
  EC2, only on metal.

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

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

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04

[Balbir Singh]

Can we please get answers to 1, 2 and 4 for comment #128. Also Kalpana
has a request for a new kernel build.

Thanks,

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

Title:
  memory_stress_ng failing for Power architecture for 16.04

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

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

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

[Kernel-packages] [Bug 1623187] [NEW] initramfs includes qle driver, but not firmware

[dann frazier]

Public bug reported:

[Impact]
The qle driver for the Qlogic FastLinQ QL45000 Series 40GbE Adapter doesn't 
find devices. This is because the driver, by default, is loaded by the 
initramfs, and the initramfs does not contain the required firmware blob. The 
root cause is that the driver does not use implement the MODULE_FIRMWARE 
macro(), which is required for initramfs-tools to find and pre-load the 
required firmware.

[Test Case]
Install a system with a Qlogic FastLinQ QL45000 Series 40GbE Adapter. On 
failure, dmesg will show:

[ 5.934190] qede 0009:90:00.0: Direct firmware load for 
qed/qed_init_values_zipped-8.4.2.0.bin failed with error -2
[ 5.934208] [qed_slowpath_start:741()]Failed to find fw file - 
/lib/firmware/qed/qed_init_values_zipped-8.4.2.0.bin
[ 5.934280] qede: probe of 0009:90:00.0 failed with error -2
[ 5.934353] qede 0009:90:00.1: enabling device ( -> 0002)
[ 5.935115] qede 0009:90:00.1: Direct firmware load for 
qed/qed_init_values_zipped-8.4.2.0.bin failed with error -2
[ 5.935139] [qed_slowpath_start:741()]Failed to find fw file - 
/lib/firmware/qed/qed_init_values_zipped-8.4.2.0.bin
[ 5.935236] qede: probe of 0009:90:00.1 failed with error -2

[Regression Risk]
Fix is upstream and the macro usage is well defined.

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: dann frazier (dannf)
 Status: In Progress

** Affects: linux (Ubuntu Xenial)
 Importance: Undecided
 Status: In Progress

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

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

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

Title:
  initramfs includes qle driver, but not firmware

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

Bug description:
  [Impact]
  The qle driver for the Qlogic FastLinQ QL45000 Series 40GbE Adapter doesn't 
find devices. This is because the driver, by default, is loaded by the 
initramfs, and the initramfs does not contain the required firmware blob. The 
root cause is that the driver does not use implement the MODULE_FIRMWARE 
macro(), which is required for initramfs-tools to find and pre-load the 
required firmware.

  [Test Case]
  Install a system with a Qlogic FastLinQ QL45000 Series 40GbE Adapter. On 
failure, dmesg will show:

  [ 5.934190] qede 0009:90:00.0: Direct firmware load for 
qed/qed_init_values_zipped-8.4.2.0.bin failed with error -2
  [ 5.934208] [qed_slowpath_start:741()]Failed to find fw file - 
/lib/firmware/qed/qed_init_values_zipped-8.4.2.0.bin
  [ 5.934280] qede: probe of 0009:90:00.0 failed with error -2
  [ 5.934353] qede 0009:90:00.1: enabling device ( -> 0002)
  [ 5.935115] qede 0009:90:00.1: Direct firmware load for 
qed/qed_init_values_zipped-8.4.2.0.bin failed with error -2
  [ 5.935139] [qed_slowpath_start:741()]Failed to find fw file - 
/lib/firmware/qed/qed_init_values_zipped-8.4.2.0.bin
  [ 5.935236] qede: probe of 0009:90:00.1 failed with error -2

  [Regression Risk]
  Fix is upstream and the macro usage is well defined.

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

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

[Kernel-packages] [Bug 1622005] Re: [Asus ZenBook UX501VW] Touchpad doesn't have multitouch support

[David DIDIER]

I gathered all the required informations but I can't subscribe to the list:
553 5.7.1 Hello [98.138.121.68], for your MAIL FROM address  
policy analysis reported: Your address is not liked source for email

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

Title:
  [Asus ZenBook UX501VW] Touchpad doesn't have multitouch support

Status in linux package in Ubuntu:
  Triaged

Bug description:
  The touchpad isn't recognized as such so there is no multitouch
  support. xinput displays "FTE1001:00 0B05:0101" instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.7.3-040703-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.44  Wed Aug 17 22:24:07 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Sep  9 22:27:19 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:1080]
     Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080]
  InstallationDate: Installed on 2016-06-01 (100 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp.
   Bus 001 Device 003: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500]
   Bus 001 Device 002: ID 04f2:b3fd Chicony Electronics Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. N501VW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.3-040703-generic 
root=UUID=ad612961-a4ae-4950-9d5a-20dcf8e56681 ro quiet splash acpi_osi= 
acpi_backlight=native nouveau.modeset=0 nvidia.nomodeset=0 i915.nomodeset=0 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.300:bd05/09/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Sep  9 22:26:55 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for (null): -22
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12876
   vendor SDC
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Kernel-packages] [Bug 1622005] Re: [Asus ZenBook UX501VW] Touchpad doesn't have multitouch support

[David DIDIER]

** Summary changed:

- [Asus ZenBook UX501] Touchpad doesn't have multitouch support
+ [Asus ZenBook UX501VW] Touchpad doesn't have multitouch support

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

Title:
  [Asus ZenBook UX501VW] Touchpad doesn't have multitouch support

Status in linux package in Ubuntu:
  Triaged

Bug description:
  The touchpad isn't recognized as such so there is no multitouch
  support. xinput displays "FTE1001:00 0B05:0101" instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.7.3-040703-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.44  Wed Aug 17 22:24:07 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Sep  9 22:27:19 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:1080]
     Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080]
  InstallationDate: Installed on 2016-06-01 (100 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp.
   Bus 001 Device 003: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500]
   Bus 001 Device 002: ID 04f2:b3fd Chicony Electronics Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. N501VW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.3-040703-generic 
root=UUID=ad612961-a4ae-4950-9d5a-20dcf8e56681 ro quiet splash acpi_osi= 
acpi_backlight=native nouveau.modeset=0 nvidia.nomodeset=0 i915.nomodeset=0 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.300:bd05/09/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Sep  9 22:26:55 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for (null): -22
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12876
   vendor SDC
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Kernel-packages] [Bug 1622293] Re: rtl8821ae WiFI does not work on Ubuntu 16.04

[Anton Polukhin]

I've changed the router to Netgear WNDR4000 and the problem still
exists. Previous router TP-LINK WR841N v9 was successfully used by 5
different devices, so the problem is not in the router's firmware. It's
in the rtl8821ae kernel module.

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

Title:
  rtl8821ae WiFI does not work on Ubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  rtl8821ae does not work out-of the box on Ubuntu 16.04. It does not
  detect any WIFi networks and laptop starts with Wifi disabled in
  NetworkManager. To make rtl8821ae work I have to do the following:

  echo "blacklist ideapad_laptop" | sudo tee /etc/modprobe.d/idepad.conf

  
  After that rtl8821ae loses connection occasionally. None of those helped:

  echo rtl8812ae  >>  /etc/modules
  echo "options rtl8821ae ips=0 fwlps=0" | sudo tee 
/etc/modprobe.d/rtl8821ae.conf
  sudo modprobe -r rtl8821ae && sudo modprobe rtl8821ae
  options rtl8821ae ips=0 swenc=1 debug=5 msi=0
  sudo iw dev wlp2s0 set power_save off

  Installing new driver from here
  https://github.com/lwfinger/rtlwifi_new did not help.

  
  Issue close to this one was reported here: 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1526683

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  antoshkka   3397 F pulseaudio
   /dev/snd/controlC0:  antoshkka   3397 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Sep 11 10:09:39 2016
  HibernationDevice: RESUME=UUID=de96877a-7ace-47cc-ac4c-b4662a72a1b7
  InstallationDate: Installed on 2016-09-10 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 80NY
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=d62213ac-da8e-417a-83fb-b8163b78199b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CECN43WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 5B
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-15ACZ
  dmi.modalias: 
dmi:bvnLENOVO:bvrCECN43WW:bd09/15/2015:svnLENOVO:pn80NY:pvrLenovoideapadY700-15ACZ:rvnLENOVO:rnAllsparks5B:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoideapadY700-15ACZ:
  dmi.product.name: 80NY
  dmi.product.version: Lenovo ideapad Y700-15ACZ
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1622763] Re: Sennheiser Officerunner - cannot get freq at ep 0x83

[David Britton]

** Description changed:

  This USB headset doesn't seem to support sample rate polling, similar to
  this issue:
  
  https://bugzilla.kernel.org/show_bug.cgi?id=95961
  
- The solution was simple, add this USB ID to the
+ == The problem ==
+ 
+ Every time something goes to interact with the device (playing a sound
+ file, opening the sound panel, opening web audio/video), a 10 second
+ pause is encountered, where dmesg prints out two messages:
+ 
+   usb 2-1.2: 2:1: cannot get freq at ep 0x83
+   usb 2-1.2: 2:1: cannot get freq at ep 0x83
+ 
+ Once the sound is playing, everything is fine.  These sample rate polls
+ don't seem to keep happening.  After waiting for maybe 30 seconds after
+ sound is playing, future interactions will again trigger the pause.
+ 
+ This 10 second pause can introduce other subtle problems.  For instance,
+ google hangouts will sometimes timeout waiting for the sound device to
+ respond, and the browser tab will crash or not fully load as a result.
+ The sound panel often also will not display the device in the list of
+ choices, and you will have to close it out.  Sometimes restart pulse
+ audio to get it to recognize the headset again.
+ 
+ == The solution ==
+ 
+ It is simple, add this USB ID to the
  sound/usb/quirks.c:snd_usb_get_sample_rate_quirk function.
  
  case USB_ID(0x1395, 0x740a): /* Sennheiser Officerunner */
- 
  
  version signature: Ubuntu 4.4.0-36.55-generic 4.4.16
  
  # lsusb |grep Senn
  Bus 002 Device 004: ID 1395:740a Sennheiser Communications
  
- 
  # zcat  /var/log/kern.log.2.gz | grep 'cannot get' | tail -4
  Sep  2 11:26:56 helo kernel: [908040.937098] usb 2-1.2: 2:1: cannot get freq 
at ep 0x4
  Sep  2 11:27:01 helo kernel: [908045.941168] usb 2-1.2: 2:1: cannot get freq 
at ep 0x4
  Sep  2 12:18:44 helo kernel: [911149.006318] usb 2-1.2: 3:1: cannot get freq 
at ep 0x83
  Sep  2 12:18:49 helo kernel: [911154.010268] usb 2-1.2: 3:1: cannot get freq 
at ep 0x83
- --- 
+ ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC3:  dpb   12893 F pulseaudio
-  /dev/snd/controlC2:  dpb   12893 F pulseaudio
-  /dev/snd/controlC1:  dpb   12893 F pulseaudio
-  /dev/snd/controlC0:  dpb   12893 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC3:  dpb   12893 F pulseaudio
+  /dev/snd/controlC2:  dpb   12893 F pulseaudio
+  /dev/snd/controlC1:  dpb   12893 F pulseaudio
+  /dev/snd/controlC0:  dpb   12893 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=a9a39ff3-c97d-471e-a0b3-518b4db8685c
  InstallationDate: Installed on 2015-03-18 (544 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150306)
  MachineType: Hewlett-Packard HP Z620 Workstation
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia zfs zunicode zcommon 
znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed 
root=/dev/mapper/vgroot-lvroot ro console=tty0 console=ttyS4,115200 nosplash 
nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  RelatedPackageVersions:
-  linux-restricted-modules-4.4.0-36-generic N/A
-  linux-backports-modules-4.4.0-36-generic  N/A
-  linux-firmware1.157.3
+  linux-restricted-modules-4.4.0-36-generic N/A
+  linux-backports-modules-4.4.0-36-generic  N/A
+  linux-firmware1.157.3
  RfKill:
-  0: hci0: Bluetooth
-   Soft blocked: no
-   Hard blocked: no
+  0: hci0: Bluetooth
+   Soft blocked: no
+   Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.4.0-36-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-02-16 (210 days ago)
  UserGroups: adm cdrom dip docker libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/27/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J61 v03.88
  dmi.board.asset.tag: 2UA41528ZC
  dmi.board.name: 158A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 0.00
  dmi.chassis.asset.tag: 2UA41528ZC
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ61v03.88:bd05/27/2015:svnHewlett-Packard:pnHPZ620Workstation:pvr:rvnHewlett-Packard:rn158A:rvr0.00:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Z620 Workstation
  dmi.sys.vendor: Hewlett-Packard

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

Title:
  Sennheiser Officerunner - cannot get freq at ep 0x83

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This USB headset doesn't seem to support sample rate polling, similar
  to this issue:

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

  == The problem ==

  Every time something goes to interact 

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

[Wolf]

Does anybody know, when kernel 4.6 will be released within an "official"
system update? -

Tried to install 4.8, or older versions still available on my computer,
but each of them made the X server (nvidia graphics) unusable.

-- 
You 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 1614309] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From gmgay...@us.ibm.com 2016-09-13 14:44 EDT---
(In reply to comment #35)
> I guess you'll have to wait until linux 4.4.0-38.57 has been promoted to
> updates since the net boot images are not updated until then. I won't revert
> this patch for lack of verification. It is obviously powerpc specific and
> should not cause regressions.

Hi Tim,
Please let us know when a netboot image containing a kernel with these patches 
is available, be it 4.4, 4.6, 4.7, or 4.8.
Thanks, Gary

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

Title:
  Ubuntu16.10:installation fails on Brazos system (31TB and 192 cores)
  No memory for flatten_device_tree (no room)

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:
  == Comment: #0 - Praveen K. Pandey - 2016-07-16 10:00:52 ==
  Hi , 

I tried  ubuntu16.10 Installation in brazos (configuration 31TB memory and 
192 cores) system . installation failing during prom_init when trying to 
allocate flatten_dt memory) System F/w is 
  FW860.00 (TC860_020).

  Reproducible Step :

  1- Configure Power VM  system having profile with  31TB memory and 1 92 Core
  2- Start Ubuntu16.10  Installation 

  Actual Result :

  Installation drop in F/w Console as failing during prom_init

  Expected Result :

  Installation Should went through

  Log:

   Booting a command list

  OF stdout device is: /vdevice/v...@3000nitrd.gz  34.84MiB  100%  
3.01MiB/s ]
  Preparing to boot Linux version 4.4.0-30-generic (buildd@bos01-ppc64el-023) 
(gcc version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2.1) ) #49-Ubuntu SMP Fri 
Jul 1 10:00:36 UTC 2016 (Ubuntu 4.4.0-30.49-generic 4.4.13)
  Detected machine type: 0101
  Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  command line: BOOT_IMAGE=/ubuntu-installer/ppc64el/yakkety/vmlinux 
tasks=standard pkgsel/language-pack-patterns= 
pkgsel/install-language-support=false DEBIAN_FRONTEND=text locale=en_US 
priority=low console-setup/ask_detect=false console-setup/layoutcode=us 
netcfg/disable_dhcp=true netcfg/confirm_static=true 
netcfg/choose_interface=6c:ae:8b:6a:81:98 netcfg/get_ipaddress=9.40.193.34/24 
netcfg/get_gateway=9.40.193.1 netcfg/get_nameservers=9.3.1.200 
netcfg/get_hostname=ltc-brazos1.aus.stglabs.ibm.com suite=yakkety 
scsi_mod.scan=sync sshd netcfg/get_domain=aus.stglabs.ibm.com unrestricted= 
url=tftp://9.3.80.16/tftpboot/ubuntu-installer/ppc64el/ubuntu-server.seed-01-6c-ae-8b-6a-81-98
 anna/choose_modules=network-console network-console/start=continue 
network-console/password=passw0rd network-console/password-again=passw0rd
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0e3e
alloc_top: 1000
alloc_top_hi : 1000
rmo_top  : 1000
ram_top  : 1000
  instantiating rtas at 0x0e9e... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  No memory for flatten_device_tree (no room)
  EXIT called ok
  0 > 

  
  Regards
  Praveen

  == Comment: #8 - Sukadev Bhattiprolu  - 2016-08-05 02:27:07 ==
  Posted a couple of patches to the community for review: 

  http://marc.info/?l=linux-kernel=147037748624043=2
  http://marc.info/?l=linux-kernel=147037768124064=2 

  == Comment: #12 - Sukadev Bhattiprolu - 2016-08-17 19:23:22 ==

  Temporary fix to address the issue while the above patches are being
  reviewed.

  ==

  Canonical,

  Please add the attached temporary fix to 16.10 to address the
  following issue while the upstream changes are being considered.

 When booting a very large system with a large initrd we run out of space
 for the flattened device tree (FDT). To fix this we must increase the
 space allocated for the RMA region.

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

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

[Kernel-packages] [Bug 1596216] Re: Black screen on boot; no modeset workaround broken by 16.04

[Joe Helfrifch]

4.8-rc6 does not resolve this issue.  Neither did the Oibaf driver PPA,
or the AMD Catalyst drivers for 16.04.

I have to question this process of just blindly testing the next RC each
time one comes out.  This problem is  related to the 8700P AMD processor
(and similar AMD chipsets) and/or the decision to disable the nomodeset
kernel option despite it being a long-term workaround for both AMD and
Nvidia graphics problems.  Unless there is explicit development to
address these issues, trying new RCs in the hopes that the issues have
been accidentally resolved is a waste of my time, your time as an Ubuntu
maintainer, and the time of all the other individuals that have reported
similar issues.

Is the Linux community really incapable of effectively communicating (or
tracking) work on issues reported inside one distro that relate to
upstream issues? As a software QA professional, I have to say that this
entire process has been disillusioning.  I purchased this laptop over a
year ago to give myself a dedicated development machine, but this is the
second bug I've encountered that makes the machine effectively useless.
Worse, this issue is a regression, since the chipset worked just fine
with the graphics drivers available in 14.04 through 15. I recognize
that sometimes hardware gets left behind by new development, but this is
not an old chip.

I really want Linux and Ubuntu to be an effective desktop environment.
But between poor communication and decisions like removing fglrx and
nomodeset that make modern, current hardware *less* effective than it
was on older versions, it doesn't seem to be there yet.  I'm currently
experimenting with using Windows and the Ubuntu bash subsystem as a
development environment, and if that proves effective (or at least
slightly productive) I'll likely be removing the Ubuntu partition. Until
I do that, I'll try to update this once a month or so.

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

Title:
  Black screen on boot; no modeset workaround broken by 16.04

Status in linux package in Ubuntu:
  Expired

Bug description:
  This bug appears to occur in several distros and architectures.  On
  this machine, it appeared somewhere in the last week of January, 2016,
  after a system update.

  On boot, the laptop monitor often flickers several times (signal
  connecting and disconnecting) and always settles onto a full backlight
  back screen.  The screen does not change after that.

  I found reports that adding nomodeset to the grub parameters would
  resolve the issue.  It does, but the workaround has significant issues
  in 16.04.  The nomodeset parameters conflict with both the amdgpu
  driver package and the radeon driver package.  When the machine boots,
  it is in 800x600 resolution.  While I can add new resolutions,
  attempting to switch to them with xrandr throws the error "configure
  crtc0 failed"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-24-generic 4.4.0-24.43
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jbhelfrich   2053 F pulseaudio
   /dev/snd/controlC0:  jbhelfrich   2053 F pulseaudio
  CurrentDesktop: MATE
  Date: Sat Jun 25 14:49:22 2016
  HibernationDevice: RESUME=UUID=51835e9e-6087-4108-af31-95e11fc3401c
  InstallationDate: Installed on 2015-10-30 (238 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: HP HP Pavilion Notebook
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed 
root=UUID=613f6223-b665-4289-9dfa-7b003124dfdf ro quiet splash nomodeset 
i8042.dumbkbd=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-24-generic N/A
   linux-backports-modules-4.4.0-24-generic  N/A
   linux-firmware1.157.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-24 (1 days ago)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80AF
  dmi.board.vendor: HP
  dmi.board.version: 81.28
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.13:bd08/06/2015:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80AF:rvr81.28:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1623143] Re: Linux container does not take same cpu configuration as kernet's hosts

[Stéphane Graber]

Seems correct to have this tracked as a kernel bug. Unless you set
limits.cpu in LXD, LXD will not alter the cpu pinning in any way. And
even if it did, it'd do so through the cpuset cgroup, which shouldn't
allow a sub-cgroup to be any more permissive than the root cgroup.

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

Title:
  Linux container does not take same cpu configuration as kernet's hosts

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I configured cpu affinity on a ubuntu 16.04 with kernel version 
"4.4.0-36-generic" on a host containing 3 cpus:
  on /etc/default/grub:
  GRUB_CMDLINE_LINUX_DEFAULT="isolcpus=0"

  update-grub

  reboot

  The output of "cat /proc/self/status" :
  ubuntu@ubuntu:~$ cat /proc/self/status
   .
   .
   .
  Cpus_allowed: 6
  Cpus_allowed_list:1-2
  Mems_allowed: ,0001
  Mems_allowed_list:0
  voluntary_ctxt_switches:  0
  nonvoluntary_ctxt_switches:   1

  When I create an lxd container in this host using these commands:

    lxc launch ubuntu:14.04 my-ubuntu

  And access to this container using:

    lxc exec my-ubuntu -- /bin/bash

  The output of "cat /proc/self/status" :
    .
    .
    .
  Cpus_allowed: 7
  Cpus_allowed_list:0-2
  Mems_allowed: ,0001
  Mems_allowed_list:0
  voluntary_ctxt_switches:  0
  nonvoluntary_ctxt_switches:   4

  Result: Container's process doesn't take same configuration as host's process.
  Host process use  2 cpus:  Cpus_allowed_list: 1-2
  Container process use 3 cpus: Cpus_allowed_list:  0-2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-36-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Tue Sep 13 18:36:29 2016
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-08-04 (40 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic 
root=/dev/mapper/username--vg-root ro isolcpus=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-wily
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-wily:cvnQEMU:ct1:cvrpc-i440fx-wily:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-wily
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1623143] Re: Linux container does not take same cpu configuration as kernet's hosts

[Stéphane Graber]

As a workaround, you could do "lxc profile set default limits.cpu 1-2"
which will have LXD setup the cpuset pinning for all containers to avoid
CPU 0.

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

Title:
  Linux container does not take same cpu configuration as kernet's hosts

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I configured cpu affinity on a ubuntu 16.04 with kernel version 
"4.4.0-36-generic" on a host containing 3 cpus:
  on /etc/default/grub:
  GRUB_CMDLINE_LINUX_DEFAULT="isolcpus=0"

  update-grub

  reboot

  The output of "cat /proc/self/status" :
  ubuntu@ubuntu:~$ cat /proc/self/status
   .
   .
   .
  Cpus_allowed: 6
  Cpus_allowed_list:1-2
  Mems_allowed: ,0001
  Mems_allowed_list:0
  voluntary_ctxt_switches:  0
  nonvoluntary_ctxt_switches:   1

  When I create an lxd container in this host using these commands:

    lxc launch ubuntu:14.04 my-ubuntu

  And access to this container using:

    lxc exec my-ubuntu -- /bin/bash

  The output of "cat /proc/self/status" :
    .
    .
    .
  Cpus_allowed: 7
  Cpus_allowed_list:0-2
  Mems_allowed: ,0001
  Mems_allowed_list:0
  voluntary_ctxt_switches:  0
  nonvoluntary_ctxt_switches:   4

  Result: Container's process doesn't take same configuration as host's process.
  Host process use  2 cpus:  Cpus_allowed_list: 1-2
  Container process use 3 cpus: Cpus_allowed_list:  0-2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-36-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Tue Sep 13 18:36:29 2016
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-08-04 (40 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic 
root=/dev/mapper/username--vg-root ro isolcpus=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-wily
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-wily:cvnQEMU:ct1:cvrpc-i440fx-wily:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-wily
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1623143] 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/1623143

Title:
  Linux container does not take same cpu configuration as kernet's hosts

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I configured cpu affinity on a ubuntu 16.04 with kernel version 
"4.4.0-36-generic" on a host containing 3 cpus:
  on /etc/default/grub:
  GRUB_CMDLINE_LINUX_DEFAULT="isolcpus=0"

  update-grub

  reboot

  The output of "cat /proc/self/status" :
  ubuntu@ubuntu:~$ cat /proc/self/status
   .
   .
   .
  Cpus_allowed: 6
  Cpus_allowed_list:1-2
  Mems_allowed: ,0001
  Mems_allowed_list:0
  voluntary_ctxt_switches:  0
  nonvoluntary_ctxt_switches:   1

  When I create an lxd container in this host using these commands:

    lxc launch ubuntu:14.04 my-ubuntu

  And access to this container using:

    lxc exec my-ubuntu -- /bin/bash

  The output of "cat /proc/self/status" :
    .
    .
    .
  Cpus_allowed: 7
  Cpus_allowed_list:0-2
  Mems_allowed: ,0001
  Mems_allowed_list:0
  voluntary_ctxt_switches:  0
  nonvoluntary_ctxt_switches:   4

  Result: Container's process doesn't take same configuration as host's process.
  Host process use  2 cpus:  Cpus_allowed_list: 1-2
  Container process use 3 cpus: Cpus_allowed_list:  0-2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-36-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Tue Sep 13 18:36:29 2016
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-08-04 (40 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic 
root=/dev/mapper/username--vg-root ro isolcpus=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-wily
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-wily:cvnQEMU:ct1:cvrpc-i440fx-wily:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-wily
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1623143] Re: Linux container does not take same cpu configuration as kernet's hosts

[Aymen Frikha]

** Summary changed:

- Linux container does not take same cpu affinity as kernet's hosts
+ Linux container does not take same cpu configuration as kernet's hosts

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

Title:
  Linux container does not take same cpu configuration as kernet's hosts

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I configured cpu affinity on a ubuntu 16.04 with kernel version 
"4.4.0-36-generic" on a host containing 3 cpus:
  on /etc/default/grub:
  GRUB_CMDLINE_LINUX_DEFAULT="isolcpus=0"

  update-grub

  reboot

  The output of "cat /proc/self/status" :
  ubuntu@ubuntu:~$ cat /proc/self/status
   .
   .
   .
  Cpus_allowed: 6
  Cpus_allowed_list:1-2
  Mems_allowed: ,0001
  Mems_allowed_list:0
  voluntary_ctxt_switches:  0
  nonvoluntary_ctxt_switches:   1

  When I create an lxd container in this host using these commands:

    lxc launch ubuntu:14.04 my-ubuntu

  And access to this container using:

    lxc exec my-ubuntu -- /bin/bash

  The output of "cat /proc/self/status" :
    .
    .
    .
  Cpus_allowed: 7
  Cpus_allowed_list:0-2
  Mems_allowed: ,0001
  Mems_allowed_list:0
  voluntary_ctxt_switches:  0
  nonvoluntary_ctxt_switches:   4

  Result: Container's process doesn't take same configuration as host's process.
  Host process use  2 cpus:  Cpus_allowed_list: 1-2
  Container process use 3 cpus: Cpus_allowed_list:  0-2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-36-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Tue Sep 13 18:36:29 2016
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-08-04 (40 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic 
root=/dev/mapper/username--vg-root ro isolcpus=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-wily
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-wily:cvnQEMU:ct1:cvrpc-i440fx-wily:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-wily
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1552551] Re: Dell CERC Adapter hangs temporarily until reset. REGRESSION

[Donc]

I believe I am having the same issue on a Dell PowerVault 745N. The
system worked fine on 14.04 but would not boot when upgraded to 16.04.
It does still boot with kernel 3.13.0-95-generic.

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

Title:
  Dell CERC Adapter hangs temporarily until reset.  REGRESSION

Status in linux package in Ubuntu:
  Triaged

Bug description:
  The HD CERC SATA 1.5 RAID controller (PCI-64 slot) hangs regularly for 10-60 
seconds until reset.
  The CERC card firmware is the newest I can find reference to: 4.1-0 [bld 
7419].  The Dell Poweredge 1800 has newest BIOS (A07).
  All hardware has been tested thoroughly OK except possibly the APIC component 
(Serverset Northbridge?).
  The 14.04LTS with all updates (or not) works fine with a perfectly consistent 
throughput of 77MB/s (slowest HD=66MB/s), RAID5.
  15.10 has the hangs of 10-60 seconds, AND with newest updates as of 
26-FEB-2016.
  I have changed PCI interrupts around and moved card slots to minimize sharing 
and removed cards - repeatedly.
  All hard drives and cables have been thoroughly tested, but the drives are 
mixed: 1 of 66MB/s, 1 of 125 MB/s, and 3 of 100MB/s.
  The drives not only work perfectly in 14.04LTS, but all Windows versions and 
DOS/BIOS-INT 19 as well (0x13).
  I have tried all combinations of card RAID options Read ahead, Write cache, 
and other BIOS options.
  Relevant dmesg lines (these were consecutive):
  [ 1046.808027] aacraid: Host adapter abort request (4,0,0,0)
  [ 1046.808123] aacraid: Host adapter reset request. SCSI hang ?
  [ 1297.828038] aacraid: Host adapter abort request (4,0,0,0)
  [ 1297.828168] aacraid: Host adapter reset request. SCSI hang ?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperVersion: 1.365
  CurrentDesktop: Unity
  Date: Thu Mar  3 05:08:57 2016
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Dell Computer Corporation PowerEdge 1800
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=u15.10-64/casper/vmlinuz.efi 
file=u15.10-64/preseed/username.seed boot=casper netboot=nfs 
nfsroot=10.100.1.86:/data2/tftpboot/u15.10-64 initrd=u15.10-64/casper/initrd.lz 
ipv6.disable=1 net.ifnames=0
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/29/2006
  dmi.bios.vendor: Dell Computer Corporation
  dmi.bios.version: A07
  dmi.board.name: 0P8611
  dmi.board.vendor: Dell Computer Corporation
  dmi.board.version: A04
  dmi.chassis.type: 17
  dmi.chassis.vendor: Dell Computer Corporation
  dmi.modalias: 
dmi:bvnDellComputerCorporation:bvrA07:bd09/29/2006:svnDellComputerCorporation:pnPowerEdge1800:pvr:rvnDellComputerCorporation:rn0P8611:rvrA04:cvnDellComputerCorporation:ct17:cvr:
  dmi.product.name: PowerEdge 1800
  dmi.sys.vendor: Dell Computer Corporation

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

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

[Kernel-packages] [Bug 1623143] [NEW] Linux container does not take same cpu configuration as kernet's hosts

[Aymen Frikha]

Public bug reported:

When I configured cpu affinity on a ubuntu 16.04 with kernel version 
"4.4.0-36-generic" on a host containing 3 cpus:
on /etc/default/grub:
GRUB_CMDLINE_LINUX_DEFAULT="isolcpus=0"

update-grub

reboot

The output of "cat /proc/self/status" :
ubuntu@ubuntu:~$ cat /proc/self/status
 .
 .
 .
Cpus_allowed:   6
Cpus_allowed_list:  1-2
Mems_allowed:   ,0001
Mems_allowed_list:  0
voluntary_ctxt_switches:0
nonvoluntary_ctxt_switches: 1

When I create an lxd container in this host using these commands:

  lxc launch ubuntu:14.04 my-ubuntu

And access to this container using:

  lxc exec my-ubuntu -- /bin/bash

The output of "cat /proc/self/status" :
  .
  .
  .
Cpus_allowed:   7
Cpus_allowed_list:  0-2
Mems_allowed:   ,0001
Mems_allowed_list:  0
voluntary_ctxt_switches:0
nonvoluntary_ctxt_switches: 4

Result: Container's process doesn't take same configuration as host's process.
Host process use  2 cpus:  Cpus_allowed_list:   1-2
Container process use 3 cpus: Cpus_allowed_list:0-2

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-36-generic 4.4.0-36.55
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-36-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
Date: Tue Sep 13 18:36:29 2016
HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
InstallationDate: Installed on 2016-08-04 (40 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic 
root=/dev/mapper/username--vg-root ro isolcpus=0
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-36-generic N/A
 linux-backports-modules-4.4.0-36-generic  N/A
 linux-firmware1.157
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-wily
dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-wily:cvnQEMU:ct1:cvrpc-i440fx-wily:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-wily
dmi.sys.vendor: QEMU

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


** Tags: amd64 apport-bug xenial

** Description changed:

  When I configured cpu affinity on a ubuntu 16.04 with kernel version 
"4.4.0-36-generic" on a host containing 3 cpus:
  on /etc/default/grub:
- GRUB_CMDLINE_LINUX_DEFAULT="isolcpus=0"
+ GRUB_CMDLINE_LINUX_DEFAULT="isolcpus=0"
  
  update-grub
  
  reboot
  
  The output of "cat /proc/self/status" :
  ubuntu@ubuntu:~$ cat /proc/self/status
-  .
-  .
-  .
+  .
+  .
+  .
  Cpus_allowed: 6
  Cpus_allowed_list:1-2
  Mems_allowed: ,0001
  Mems_allowed_list:0
  voluntary_ctxt_switches:  0
  nonvoluntary_ctxt_switches:   1
  
- 
  When I create an lxd container in this host using these commands:
  
-   lxc launch ubuntu:14.04 my-ubuntu
+   lxc launch ubuntu:14.04 my-ubuntu
  
  And access to this container using:
-   
-   lxc exec my-ubuntu -- /bin/bash
+ 
+   lxc exec my-ubuntu -- /bin/bash
  
  The output of "cat /proc/self/status" :
-   .
-   .
-   .
+   .
+   .
+   .
  Cpus_allowed: 7
  Cpus_allowed_list:0-2
  Mems_allowed: ,0001
  Mems_allowed_list:0
  voluntary_ctxt_switches:  0
  nonvoluntary_ctxt_switches:   4
  
- 
- Result: Container's process doesn't take same configuration as host's
- process.
+ Result: Container's process doesn't take same configuration as host's process.
+ Host 

[Kernel-packages] [Bug 1618083] Re: linux: 3.13.0-96.143 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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/1618083

Title:
  linux: 3.13.0-96.143 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-96.143 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/1618083/+subscriptions

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

[Kernel-packages] [Bug 1575467] Re: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-utopic-vy2yyy/linux-lts-utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_rea

[Chris]

I fixed one of the issues I described above by reinstalling Ubuntu with
a swap. Originally I installed it without a swap, with the rationale
that this tiny laptop has only 32GB SSD, which is very little. I
determined that vswapd was killing the CPU, that's why the mouse cursor
was moving so slowly.

I reinstalled with full swap support. On top of that I installed zram-
config and also reduced vm.swappiness to 10, which arguably seems more
snappy.

So far it works like a charm. If I have other similar problems, I will
report them here.

Note: I am still using intel_idle.cstate_max=1 in order to avoid random
hangs. It would be nice if Intel got around to fixing this bug in their
firmware...

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1575467

Title:
  [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-
  utopic-vy2yyy/linux-lts-
  utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743
  vlv_wait_port_ready+0x126/0x170 [i915]()

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

Bug description:
  After upgrading from stock Ubuntu 14.04 to 16.04 my laptop
  consistently freezes up and is unresponsive to keyboard or mouse. The
  only way is to do a hard shutdown. I'm usually in a browser when this
  happens, and often watching a video or two. It seems to happen more
  often in Google Chrome than Firefox, but it happens with both. It has
  happened at least once with no videos loaded. I haven’t observed it
  freeze / hang when I’m not in a browser, but that's mainly what i use
  my laptop for, so that's where most of my time is spent.

  Call trace:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+attachment/4648682/+files/kern.log.2.gz

  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrew 1949 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=e8aaee7c-d956-4519-94f0-cf7aad745020
  InstallationDate: Installed on 2015-08-08 (263 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Dell Inc. Inspiron 3451
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=d01f07be-c906-4024-8eef-a58ba3935298 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (4 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 12/05/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0H4MK6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd12/05/2014:svnDellInc.:pnInspiron3451:pvrA00:rvnDellInc.:rn0H4MK6:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3451
  dmi.product.version: A00
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1619679] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1: bcmwl kernel module failed to build [error: ‘STATION_INFO_TX_BITRATE’ undeclared]

[Guy Begin]

Naturally, after the failed build, Wifi does not work. Rebooting with
the previous kernel (3.19.0-68-generic #76~14.04.1-Ubuntu) restores
Wifi.

After a bit of googling, I found someone suggesting that kernel build
errors may be due to using an old version of gcc. This sounded good, so
I installed gcc-4.9 as per

http://askubuntu.com/questions/466651/how-do-i-use-the-latest-gcc-on-
ubuntu

Next I uninstalled and re-installed bcmwl-kernel-source. It took a while
to build the module, but after that booting using kernel 4.4 brought
back Wifi.

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

Title:
  bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1: bcmwl kernel module
  failed to build [error: ‘STATION_INFO_TX_BITRATE’ undeclared]

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  DKMS 4.4.0-36_generic
  Latest kernel 4.4,
  Ubuntu was Launched with kernel 3.19.066 when bug was occurred.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.19.0-66.74~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-66-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-36-generic
  Date: Fri Sep  2 10:13:50 2016
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu0.1:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:1444:20:
 error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this function)
  InstallationDate: Installed on 2015-11-07 (299 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageVersion: 6.30.223.248+bdcom-0ubuntu0.1
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1: 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/1619679/+subscriptions

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

[Kernel-packages] [Bug 1616677] Re: [Hyper-V] Rebase Hyper-V to 4.7.2 (stable)

[Joshua R. Poulson]

SR-IOV test still pending, we're on 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/1616677

Title:
  [Hyper-V] Rebase Hyper-V to 4.7.2 (stable)

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:
  Please rebase the Hyper-V drivers and tools in lts-xenial (and
  yakkity) to the final v4.7.2 stable upstream kernel.

  The following files comprise Hyper-V support in the upstream kernel:
  arch/x86/kernel/cpu/mshyperv.c
  arch/x86/include/asm/mshyperv.h
  arch/x86/include/uapi/asm/hyperv.h
  include/linux/hyperv.h
  drivers/hv/channel.c
  drivers/hv/channel_mgmt.c
  drivers/hv/connection.c
  drivers/hv/hv_balloon.c
  drivers/hv/hv.c
  drivers/hv/hv_fcopy.c
  drivers/hv/hv_kvp.c
  drivers/hv/hv_snapshot.c
  drivers/hv/hv_util.c
  drivers/hv/hv_utils_transport.c
  drivers/hv/hv_utils_transport.h
  drivers/hv/hyperv_vmbus.h
  drivers/hv/ring_buffer.c
  drivers/hv/vmbus_drv.c
  tools/hv/hv_fcopy_daemon.c
  tools/hv/hv_get_dhcp_info.sh
  tools/hv/hv_get_dns_info.sh
  tools/hv/hv_kvp_daemon.c
  tools/hv/hv_set_ifconfig.sh
  tools/hv/hv_vss_daemon.c
  tools/hv/lsvmbus
  drivers/input/serio/hyperv-keyboard.c
  drivers/net/hyperv/hyperv_net.h
  drivers/net/hyperv/netvsc.c
  drivers/net/hyperv/netvsc_drv.c
  drivers/net/hyperv/rndis_filter.c
  drivers/scsi/storvsc_drv.c
  drivers/hid/hid-hyperv.c
  drivers/pci/host/pci-hyperv.c
  drivers/video/fbdev/hyperv_fb.c

  While I know a number of post-4.6 commits are already included, I am
  including all of the commits from 4.6 to 4.7.2 for reference:

  channel_mgmt.c : commit cd95aad5579371ac332507fc946008217fc37e6c : 
Drivers: hv: vmbus: handle various crash scenarios
  connection.c : commit 5cc472477f928fb8584eb8e08245c9cf9002d74a : Drivers: 
hv: vmbus: Export the vmbus_set_event() API
  hv_balloon.c : commit 77c0c9735bc0ba5898e637a3a20d6bcb50e3f67d : Drivers: 
hv: balloon: don't crash when memory is added in non-sorted order
  hv_balloon.c : commit d19a55d6ed5bf0ffe553df2d8bf91d054ddf2d76 : Drivers: 
hv: balloon: reset host_specified_ha_region
  hv_kvp.c : commit 4dbfc2e68004c60edab7e8fd26784383dd3ee9bc : Drivers: hv: 
kvp: fix IP Failover
  hyperv_fb.c : commit 696ca5e82c057a272381ae6064d59eb97a578397 : 
drivers:hv: Use new vmbus_mmio_free() from client drivers.
  hyperv.h : commit 97fb77dc87582300fa3c141b63699f853576cab1 : drivers:hv: 
Make a function to free mmio regions through vmbus
  hyperv.h : commit a6341f24cdf1ec14dc26743a409a17378db5 : Drivers: hv: 
vmbus: Introduce functions for estimating room in the ring buffer
  hyperv.h : commit ab028db41ca9174caab7f9e3fc0a2e7f4a418410 : Drivers: hv: 
vmbus: Implement APIs to support "in place" consumption of vmbus packets
  hyperv_net.h : commit 10082f98878a9dff1563745f9f1dd9d1ff142700 : 
hv_netvsc: Eliminate status from struct hv_netvsc_packet
  hyperv_net.h : commit 3d541ac5a92af708d0085925d136f875f3a58d57 : 
hv_netvsc: untangle the pointer mess
  hyperv_net.h : commit c85e4924452ae8225c8829f3fa8a2f7baa34bc5c : 
hv_netvsc: Fix book keeping of skb during batching process
  hyperv_vmbus.h : commit 4dbfc2e68004c60edab7e8fd26784383dd3ee9bc : 
Drivers: hv: kvp: fix IP Failover
  hyperv_vmbus.h : commit 5cc472477f928fb8584eb8e08245c9cf9002d74a : 
Drivers: hv: vmbus: Export the vmbus_set_event() API
  hyperv_vmbus.h : commit cd95aad5579371ac332507fc946008217fc37e6c : 
Drivers: hv: vmbus: handle various crash scenarios
  lsvmbus : commit 552beb4930ef3889d42a049eb9ba3533b4cbe0f6 : tools: hv: 
lsvmbus: add pci pass-through UUID
  netvsc_drv.c : commit 15cfd40771e18a4e9b788c64c9db2606f958b93d : 
hv_netvsc: Fix the list processing for network change event
  netvsc_drv.c : commit 1bdcec8a5f05445752a0639edd603ac09ae6c553 : 
hv_netvsc: use start_remove flag to protect netvsc_link_change()
  netvsc_drv.c : commit 84bf9cefb162b197da20a0f4388929f4b5ba5db4 : 
hv_netvsc: Implement support for VF drivers on Hyper-V
  pci-hyperv.c : commit 696ca5e82c057a272381ae6064d59eb97a578397 : 
drivers:hv: Use new vmbus_mmio_free() from client drivers.
  pci-hyperv.c : commit bdd74440d9e887b1fa648eefa17421def5f5243c : PCI: hv: 
Add explicit barriers to config space access
  pci-hyperv.c : commit deb22e5c84c884a129d801cf3bfde7411536998d : PCI: hv: 
Report resources release after stopping the bus
  ring_buffer.c : commit a6341f24cdf1ec14dc26743a409a17378db5 : 
Drivers: hv: vmbus: Introduce functions for estimating room in the ring buffer
  rndis_filter.c : commit 0a1275ca5128b84c149960969ed351ae00eb : 
hv_netvsc: get rid of struct net_device pointer in struct netvsc_device
  rndis_filter.c : commit 10082f98878a9dff1563745f9f1dd9d1ff142700 : 
hv_netvsc: Eliminate status from struct hv_netvsc_packet
  

Re: [Kernel-packages] [Bug 1616677] Re: [Hyper-V] Rebase Hyper-V to 4.7.2 (stable)

[Joshua R. Poulson]

The SR-IOV test is still pending. In progress.

Thanks, --jrp

-Original Message-
From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Tim 
Gardner
Sent: Tuesday, September 13, 2016 08:41
To: Josh Poulson 
Subject: [Bug 1616677] Re: [Hyper-V] Rebase Hyper-V to 4.7.2 (stable)

Joshua - are y'all ever gonna retest this ?

--
You received this bug notification because you are subscribed to the bug report.
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fbugs.launchpad.net%2fbugs%2f1616677=02%7c01%7cjopoulso%40microsoft.com%7ca03647aed6164c1b8f1b08d3dbeddcfa%7c72f988bf86f141af91ab2d7cd011db47%7c1%7c0%7c636093787054915770=LQE2jeOCNxemBwzTe5t5eZdmBx7dgl3UhWA9olw8KZ8%3d

Title:
  [Hyper-V] Rebase Hyper-V to 4.7.2 (stable)

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:
  Please rebase the Hyper-V drivers and tools in lts-xenial (and
  yakkity) to the final v4.7.2 stable upstream kernel.

  The following files comprise Hyper-V support in the upstream kernel:
  arch/x86/kernel/cpu/mshyperv.c
  arch/x86/include/asm/mshyperv.h
  arch/x86/include/uapi/asm/hyperv.h
  include/linux/hyperv.h
  drivers/hv/channel.c
  drivers/hv/channel_mgmt.c
  drivers/hv/connection.c
  drivers/hv/hv_balloon.c
  drivers/hv/hv.c
  drivers/hv/hv_fcopy.c
  drivers/hv/hv_kvp.c
  drivers/hv/hv_snapshot.c
  drivers/hv/hv_util.c
  drivers/hv/hv_utils_transport.c
  drivers/hv/hv_utils_transport.h
  drivers/hv/hyperv_vmbus.h
  drivers/hv/ring_buffer.c
  drivers/hv/vmbus_drv.c
  tools/hv/hv_fcopy_daemon.c
  tools/hv/hv_get_dhcp_info.sh
  tools/hv/hv_get_dns_info.sh
  tools/hv/hv_kvp_daemon.c
  tools/hv/hv_set_ifconfig.sh
  tools/hv/hv_vss_daemon.c
  tools/hv/lsvmbus
  drivers/input/serio/hyperv-keyboard.c
  drivers/net/hyperv/hyperv_net.h
  drivers/net/hyperv/netvsc.c
  drivers/net/hyperv/netvsc_drv.c
  drivers/net/hyperv/rndis_filter.c
  drivers/scsi/storvsc_drv.c
  drivers/hid/hid-hyperv.c
  drivers/pci/host/pci-hyperv.c
  drivers/video/fbdev/hyperv_fb.c

  While I know a number of post-4.6 commits are already included, I am
  including all of the commits from 4.6 to 4.7.2 for reference:

  channel_mgmt.c : commit cd95aad5579371ac332507fc946008217fc37e6c : 
Drivers: hv: vmbus: handle various crash scenarios
  connection.c : commit 5cc472477f928fb8584eb8e08245c9cf9002d74a : Drivers: 
hv: vmbus: Export the vmbus_set_event() API
  hv_balloon.c : commit 77c0c9735bc0ba5898e637a3a20d6bcb50e3f67d : Drivers: 
hv: balloon: don't crash when memory is added in non-sorted order
  hv_balloon.c : commit d19a55d6ed5bf0ffe553df2d8bf91d054ddf2d76 : Drivers: 
hv: balloon: reset host_specified_ha_region
  hv_kvp.c : commit 4dbfc2e68004c60edab7e8fd26784383dd3ee9bc : Drivers: hv: 
kvp: fix IP Failover
  hyperv_fb.c : commit 696ca5e82c057a272381ae6064d59eb97a578397 : 
drivers:hv: Use new vmbus_mmio_free() from client drivers.
  hyperv.h : commit 97fb77dc87582300fa3c141b63699f853576cab1 : drivers:hv: 
Make a function to free mmio regions through vmbus
  hyperv.h : commit a6341f24cdf1ec14dc26743a409a17378db5 : Drivers: hv: 
vmbus: Introduce functions for estimating room in the ring buffer
  hyperv.h : commit ab028db41ca9174caab7f9e3fc0a2e7f4a418410 : Drivers: hv: 
vmbus: Implement APIs to support "in place" consumption of vmbus packets
  hyperv_net.h : commit 10082f98878a9dff1563745f9f1dd9d1ff142700 : 
hv_netvsc: Eliminate status from struct hv_netvsc_packet
  hyperv_net.h : commit 3d541ac5a92af708d0085925d136f875f3a58d57 : 
hv_netvsc: untangle the pointer mess
  hyperv_net.h : commit c85e4924452ae8225c8829f3fa8a2f7baa34bc5c : 
hv_netvsc: Fix book keeping of skb during batching process
  hyperv_vmbus.h : commit 4dbfc2e68004c60edab7e8fd26784383dd3ee9bc : 
Drivers: hv: kvp: fix IP Failover
  hyperv_vmbus.h : commit 5cc472477f928fb8584eb8e08245c9cf9002d74a : 
Drivers: hv: vmbus: Export the vmbus_set_event() API
  hyperv_vmbus.h : commit cd95aad5579371ac332507fc946008217fc37e6c : 
Drivers: hv: vmbus: handle various crash scenarios
  lsvmbus : commit 552beb4930ef3889d42a049eb9ba3533b4cbe0f6 : tools: hv: 
lsvmbus: add pci pass-through UUID
  netvsc_drv.c : commit 15cfd40771e18a4e9b788c64c9db2606f958b93d : 
hv_netvsc: Fix the list processing for network change event
  netvsc_drv.c : commit 1bdcec8a5f05445752a0639edd603ac09ae6c553 : 
hv_netvsc: use start_remove flag to protect netvsc_link_change()
  netvsc_drv.c : commit 84bf9cefb162b197da20a0f4388929f4b5ba5db4 : 
hv_netvsc: Implement support for VF drivers on Hyper-V
  pci-hyperv.c : commit 696ca5e82c057a272381ae6064d59eb97a578397 : 
drivers:hv: Use new vmbus_mmio_free() from client drivers.
  pci-hyperv.c : commit bdd74440d9e887b1fa648eefa17421def5f5243c : PCI: hv: 
Add explicit barriers to config space access
  pci-hyperv.c : commit 

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

[Jarno Suni]

I tested the kernel in lp1608236. S-video works.

-- 
You 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 1589997] Re: The device on /dev/sdx is not created when inserting new devices

[Joan]

Hello again, it seems that the issue arose again, I don't know at what
point but it's still present. Apparently the kernel upgrade didn't fix
the issue, because when it appeared back on the new install I upgraded
the kernel again to current version, and it's still happening

$ uname -r
4.7.0-040700rc6-generic


About the bios upgrade, I updated it to the current version 1.25, so it 
shouldn't be a problem.
What could I provide to help with the diagnostic of the issue.

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

Title:
  The device on /dev/sdx is not created when inserting new devices

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am on kubuntu xenial (upgraded from 15.10), from a couple of weeks I 
noticed that the pendrives i insert to my computer are detected but the devices 
under /dev are no longer created.
  I if reboot the pc with the pendrive already plugged in it works without 
issues. I'm suspecting from udev because of this text in syslog (full output in 
the summary)

  Jun  7 15:02:55 pc systemd-udevd[24747]: inotify_add_watch(9,
  /dev/sdb, 10) failed: No such file or directory

  I'm up to date on all the packages
  - linux-image-4.4.0-22-generic
  - udev - 229-4ubuntu6
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jjuvanteny   2047 F pulseaudio
   /dev/snd/pcmC1D0p:   jjuvanteny   2047 F...m pulseaudio
   /dev/snd/controlC1:  jjuvanteny   2047 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=120e7a9e-4193-4d2d-a46e-6fdf0fa5b16c
  InstallationDate: Installed on 2015-03-27 (439 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  MachineType: LENOVO 20DF004USP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=c62be6bc-f11b-4970-8ee1-976bf2e7fb9d ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (47 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/08/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J5ET41WW (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20DF004USP
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ5ET41WW(1.12):bd12/08/2014:svnLENOVO:pn20DF004USP:pvrThinkPadE550:rvnLENOVO:rn20DF004USP:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20DF004USP
  dmi.product.version: ThinkPad E550
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1589997] Re: The device on /dev/sdx is not created when inserting new devices

[Joan]

I changed the status into confirmed (didn't see how to reopen the
issue), if I have to open a new bug referring this one, just tell me.

Thanks

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

Title:
  The device on /dev/sdx is not created when inserting new devices

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am on kubuntu xenial (upgraded from 15.10), from a couple of weeks I 
noticed that the pendrives i insert to my computer are detected but the devices 
under /dev are no longer created.
  I if reboot the pc with the pendrive already plugged in it works without 
issues. I'm suspecting from udev because of this text in syslog (full output in 
the summary)

  Jun  7 15:02:55 pc systemd-udevd[24747]: inotify_add_watch(9,
  /dev/sdb, 10) failed: No such file or directory

  I'm up to date on all the packages
  - linux-image-4.4.0-22-generic
  - udev - 229-4ubuntu6
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jjuvanteny   2047 F pulseaudio
   /dev/snd/pcmC1D0p:   jjuvanteny   2047 F...m pulseaudio
   /dev/snd/controlC1:  jjuvanteny   2047 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=120e7a9e-4193-4d2d-a46e-6fdf0fa5b16c
  InstallationDate: Installed on 2015-03-27 (439 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  MachineType: LENOVO 20DF004USP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=c62be6bc-f11b-4970-8ee1-976bf2e7fb9d ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (47 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/08/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J5ET41WW (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20DF004USP
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ5ET41WW(1.12):bd12/08/2014:svnLENOVO:pn20DF004USP:pvrThinkPadE550:rvnLENOVO:rn20DF004USP:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20DF004USP
  dmi.product.version: ThinkPad E550
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1619679] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1: bcmwl kernel module failed to build [error: ‘STATION_INFO_TX_BITRATE’ undeclared]

[Guy Begin]

Naturally, after the failed build, Wifi does not work. Rebooting with
the previous kernel (3.19.0-68-generic #76~14.04.1-Ubuntu) restores Wifi

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

Title:
  bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1: bcmwl kernel module
  failed to build [error: ‘STATION_INFO_TX_BITRATE’ undeclared]

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  DKMS 4.4.0-36_generic
  Latest kernel 4.4,
  Ubuntu was Launched with kernel 3.19.066 when bug was occurred.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.19.0-66.74~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-66-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-36-generic
  Date: Fri Sep  2 10:13:50 2016
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu0.1:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:1444:20:
 error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this function)
  InstallationDate: Installed on 2015-11-07 (299 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageVersion: 6.30.223.248+bdcom-0ubuntu0.1
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1: 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/1619679/+subscriptions

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

[Kernel-packages] [Bug 1619679] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1: bcmwl kernel module failed to build [error: ‘STATION_INFO_TX_BITRATE’ undeclared]

[Launchpad Bug Tracker]

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

Title:
  bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1: bcmwl kernel module
  failed to build [error: ‘STATION_INFO_TX_BITRATE’ undeclared]

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  DKMS 4.4.0-36_generic
  Latest kernel 4.4,
  Ubuntu was Launched with kernel 3.19.066 when bug was occurred.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.19.0-66.74~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-66-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-36-generic
  Date: Fri Sep  2 10:13:50 2016
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu0.1:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:1444:20:
 error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this function)
  InstallationDate: Installed on 2015-11-07 (299 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageVersion: 6.30.223.248+bdcom-0ubuntu0.1
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1: 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/1619679/+subscriptions

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

[Kernel-packages] [Bug 1616677] Re: [Hyper-V] Rebase Hyper-V to 4.7.2 (stable)

[Tim Gardner]

Joshua - are y'all ever gonna retest this ?

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

Title:
  [Hyper-V] Rebase Hyper-V to 4.7.2 (stable)

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:
  Please rebase the Hyper-V drivers and tools in lts-xenial (and
  yakkity) to the final v4.7.2 stable upstream kernel.

  The following files comprise Hyper-V support in the upstream kernel:
  arch/x86/kernel/cpu/mshyperv.c
  arch/x86/include/asm/mshyperv.h
  arch/x86/include/uapi/asm/hyperv.h
  include/linux/hyperv.h
  drivers/hv/channel.c
  drivers/hv/channel_mgmt.c
  drivers/hv/connection.c
  drivers/hv/hv_balloon.c
  drivers/hv/hv.c
  drivers/hv/hv_fcopy.c
  drivers/hv/hv_kvp.c
  drivers/hv/hv_snapshot.c
  drivers/hv/hv_util.c
  drivers/hv/hv_utils_transport.c
  drivers/hv/hv_utils_transport.h
  drivers/hv/hyperv_vmbus.h
  drivers/hv/ring_buffer.c
  drivers/hv/vmbus_drv.c
  tools/hv/hv_fcopy_daemon.c
  tools/hv/hv_get_dhcp_info.sh
  tools/hv/hv_get_dns_info.sh
  tools/hv/hv_kvp_daemon.c
  tools/hv/hv_set_ifconfig.sh
  tools/hv/hv_vss_daemon.c
  tools/hv/lsvmbus
  drivers/input/serio/hyperv-keyboard.c
  drivers/net/hyperv/hyperv_net.h
  drivers/net/hyperv/netvsc.c
  drivers/net/hyperv/netvsc_drv.c
  drivers/net/hyperv/rndis_filter.c
  drivers/scsi/storvsc_drv.c
  drivers/hid/hid-hyperv.c
  drivers/pci/host/pci-hyperv.c
  drivers/video/fbdev/hyperv_fb.c

  While I know a number of post-4.6 commits are already included, I am
  including all of the commits from 4.6 to 4.7.2 for reference:

  channel_mgmt.c : commit cd95aad5579371ac332507fc946008217fc37e6c : 
Drivers: hv: vmbus: handle various crash scenarios
  connection.c : commit 5cc472477f928fb8584eb8e08245c9cf9002d74a : Drivers: 
hv: vmbus: Export the vmbus_set_event() API
  hv_balloon.c : commit 77c0c9735bc0ba5898e637a3a20d6bcb50e3f67d : Drivers: 
hv: balloon: don't crash when memory is added in non-sorted order
  hv_balloon.c : commit d19a55d6ed5bf0ffe553df2d8bf91d054ddf2d76 : Drivers: 
hv: balloon: reset host_specified_ha_region
  hv_kvp.c : commit 4dbfc2e68004c60edab7e8fd26784383dd3ee9bc : Drivers: hv: 
kvp: fix IP Failover
  hyperv_fb.c : commit 696ca5e82c057a272381ae6064d59eb97a578397 : 
drivers:hv: Use new vmbus_mmio_free() from client drivers.
  hyperv.h : commit 97fb77dc87582300fa3c141b63699f853576cab1 : drivers:hv: 
Make a function to free mmio regions through vmbus
  hyperv.h : commit a6341f24cdf1ec14dc26743a409a17378db5 : Drivers: hv: 
vmbus: Introduce functions for estimating room in the ring buffer
  hyperv.h : commit ab028db41ca9174caab7f9e3fc0a2e7f4a418410 : Drivers: hv: 
vmbus: Implement APIs to support "in place" consumption of vmbus packets
  hyperv_net.h : commit 10082f98878a9dff1563745f9f1dd9d1ff142700 : 
hv_netvsc: Eliminate status from struct hv_netvsc_packet
  hyperv_net.h : commit 3d541ac5a92af708d0085925d136f875f3a58d57 : 
hv_netvsc: untangle the pointer mess
  hyperv_net.h : commit c85e4924452ae8225c8829f3fa8a2f7baa34bc5c : 
hv_netvsc: Fix book keeping of skb during batching process
  hyperv_vmbus.h : commit 4dbfc2e68004c60edab7e8fd26784383dd3ee9bc : 
Drivers: hv: kvp: fix IP Failover
  hyperv_vmbus.h : commit 5cc472477f928fb8584eb8e08245c9cf9002d74a : 
Drivers: hv: vmbus: Export the vmbus_set_event() API
  hyperv_vmbus.h : commit cd95aad5579371ac332507fc946008217fc37e6c : 
Drivers: hv: vmbus: handle various crash scenarios
  lsvmbus : commit 552beb4930ef3889d42a049eb9ba3533b4cbe0f6 : tools: hv: 
lsvmbus: add pci pass-through UUID
  netvsc_drv.c : commit 15cfd40771e18a4e9b788c64c9db2606f958b93d : 
hv_netvsc: Fix the list processing for network change event
  netvsc_drv.c : commit 1bdcec8a5f05445752a0639edd603ac09ae6c553 : 
hv_netvsc: use start_remove flag to protect netvsc_link_change()
  netvsc_drv.c : commit 84bf9cefb162b197da20a0f4388929f4b5ba5db4 : 
hv_netvsc: Implement support for VF drivers on Hyper-V
  pci-hyperv.c : commit 696ca5e82c057a272381ae6064d59eb97a578397 : 
drivers:hv: Use new vmbus_mmio_free() from client drivers.
  pci-hyperv.c : commit bdd74440d9e887b1fa648eefa17421def5f5243c : PCI: hv: 
Add explicit barriers to config space access
  pci-hyperv.c : commit deb22e5c84c884a129d801cf3bfde7411536998d : PCI: hv: 
Report resources release after stopping the bus
  ring_buffer.c : commit a6341f24cdf1ec14dc26743a409a17378db5 : 
Drivers: hv: vmbus: Introduce functions for estimating room in the ring buffer
  rndis_filter.c : commit 0a1275ca5128b84c149960969ed351ae00eb : 
hv_netvsc: get rid of struct net_device pointer in struct netvsc_device
  rndis_filter.c : commit 10082f98878a9dff1563745f9f1dd9d1ff142700 : 
hv_netvsc: Eliminate status from struct hv_netvsc_packet
  

[Kernel-packages] [Bug 1623092] Re: Computer crashes on shutdown

[Antonios Hadjigeorgalis]

This is the section of the kern.log that was showing on the screen at
the time of the crash.

** Attachment added: "kern.log crash report section"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1623092/+attachment/4740140/+files/kern.log

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

Title:
  Computer crashes on shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug has occurred twice in the past week.  My motherboard is set
  up to turn on at 6am in the morning.  The morning after this bug
  occurs it does not automatically start up.  The bug occurs on shutdown
  and leaves the computer unresponsive with the text of the kernel log
  bug report on the screen.  I've had to do a hard shutdown at this
  point, holding the power button until the machine powers down fully.

  I am happy to do whatever troubleshooting you suggest.  I used
  `ubuntu-bug linux` to file this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  antonios   4898 F pulseaudio
   /dev/snd/controlC0:  antonios   4898 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Sep 13 11:09:38 2016
  HibernationDevice: RESUME=UUID=d39f2337-8ee7-4d9d-9202-41a04c955dfd
  InstallationDate: Installed on 2012-09-14 (1459 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  IwConfig:
   lono wireless extensions.
   
   docker0   no wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=50ef8abe-641b-49fd-8a81-60aca8cd440f ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-08-08 (35 days ago)
  dmi.bios.date: 09/06/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2105
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2105:bd09/06/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1623092] [NEW] Computer crashes on shutdown

[Antonios Hadjigeorgalis]

Public bug reported:

This bug has occurred twice in the past week.  My motherboard is set up
to turn on at 6am in the morning.  The morning after this bug occurs it
does not automatically start up.  The bug occurs on shutdown and leaves
the computer unresponsive with the text of the kernel log bug report on
the screen.  I've had to do a hard shutdown at this point, holding the
power button until the machine powers down fully.

I am happy to do whatever troubleshooting you suggest.  I used `ubuntu-
bug linux` to file this report.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-36-generic 4.4.0-36.55
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  antonios   4898 F pulseaudio
 /dev/snd/controlC0:  antonios   4898 F pulseaudio
CurrentDesktop: Unity
Date: Tue Sep 13 11:09:38 2016
HibernationDevice: RESUME=UUID=d39f2337-8ee7-4d9d-9202-41a04c955dfd
InstallationDate: Installed on 2012-09-14 (1459 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
IwConfig:
 lono wireless extensions.
 
 docker0   no wireless extensions.
 
 eth0  no wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=50ef8abe-641b-49fd-8a81-60aca8cd440f ro
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-36-generic N/A
 linux-backports-modules-4.4.0-36-generic  N/A
 linux-firmware1.157.3
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-08-08 (35 days ago)
dmi.bios.date: 09/06/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2105
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z77-M PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2105:bd09/06/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug 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/1623092

Title:
  Computer crashes on shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug has occurred twice in the past week.  My motherboard is set
  up to turn on at 6am in the morning.  The morning after this bug
  occurs it does not automatically start up.  The bug occurs on shutdown
  and leaves the computer unresponsive with the text of the kernel log
  bug report on the screen.  I've had to do a hard shutdown at this
  point, holding the power button until the machine powers down fully.

  I am happy to do whatever troubleshooting you suggest.  I used
  `ubuntu-bug linux` to file this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  antonios   4898 F pulseaudio
   /dev/snd/controlC0:  antonios   4898 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Sep 13 11:09:38 2016
  HibernationDevice: RESUME=UUID=d39f2337-8ee7-4d9d-9202-41a04c955dfd
  InstallationDate: Installed on 2012-09-14 (1459 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  IwConfig:
   lono wireless extensions.
   
   docker0   no wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=50ef8abe-641b-49fd-8a81-60aca8cd440f ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-08-08 (35 days ago)
  dmi.bios.date: 09/06/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2105
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  

[Kernel-packages] [Bug 1609913] s2lp6g002 (s390x.zKVM) - tests ran: 65, failed: 65

[Brad Figg]

tests ran:  65, failed: 65;
  
http://kernel.ubuntu.com/testing/4.6.0-12.14/s2lp6g002__4.6.0-12.14__2016-09-13_15-08-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/1609913

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

[Kernel-packages] [Bug 1609913] s2lp6g002 (s390x.zKVM) - tests ran: 136, failed: 27

[Brad Figg]

tests ran: 136, failed: 27;
  
http://kernel.ubuntu.com/testing/4.6.0-12.14/s2lp6g002__4.6.0-12.14__2016-09-13_14-20-00/results-index.html

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

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-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]

For what it is worth, S-video works by v4.8-rc5

-- 
You 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 1623092] 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/1623092

Title:
  Computer crashes on shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug has occurred twice in the past week.  My motherboard is set
  up to turn on at 6am in the morning.  The morning after this bug
  occurs it does not automatically start up.  The bug occurs on shutdown
  and leaves the computer unresponsive with the text of the kernel log
  bug report on the screen.  I've had to do a hard shutdown at this
  point, holding the power button until the machine powers down fully.

  I am happy to do whatever troubleshooting you suggest.  I used
  `ubuntu-bug linux` to file this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  antonios   4898 F pulseaudio
   /dev/snd/controlC0:  antonios   4898 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Sep 13 11:09:38 2016
  HibernationDevice: RESUME=UUID=d39f2337-8ee7-4d9d-9202-41a04c955dfd
  InstallationDate: Installed on 2012-09-14 (1459 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  IwConfig:
   lono wireless extensions.
   
   docker0   no wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=50ef8abe-641b-49fd-8a81-60aca8cd440f ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-08-08 (35 days ago)
  dmi.bios.date: 09/06/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2105
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2105:bd09/06/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

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

[bugproxy]

--- Comment From gmgay...@us.ibm.com 2016-09-13 10:45 EDT---
(In reply to comment #31)
> (In reply to comment #30)
> > You should be testing at least linux 4.4.0-38.57 in proposed.
>
> Hi Tim.
>
> Do you have specific instructions on how to do so for the *install*?  Since
> the netboot image is not using that kernel, the system doesn't make it far
> enough into the install process to pick up a non-install kernel like
> mentioned above.
>
> Thanks

Hi Tim at Canonical,
I'd like to clarify.
This install bug occurs very early in the boot of the install image.  We will 
need a netboot install image with the 4.4.0-38-57, or later, in order to test 
this fix.
Thanks, Gary

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

Title:
  Ubuntu16.10:installation fails on Brazos system (31TB and 192 cores)
  No memory for flatten_device_tree (no room)

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:
  == Comment: #0 - Praveen K. Pandey - 2016-07-16 10:00:52 ==
  Hi , 

I tried  ubuntu16.10 Installation in brazos (configuration 31TB memory and 
192 cores) system . installation failing during prom_init when trying to 
allocate flatten_dt memory) System F/w is 
  FW860.00 (TC860_020).

  Reproducible Step :

  1- Configure Power VM  system having profile with  31TB memory and 1 92 Core
  2- Start Ubuntu16.10  Installation 

  Actual Result :

  Installation drop in F/w Console as failing during prom_init

  Expected Result :

  Installation Should went through

  Log:

   Booting a command list

  OF stdout device is: /vdevice/v...@3000nitrd.gz  34.84MiB  100%  
3.01MiB/s ]
  Preparing to boot Linux version 4.4.0-30-generic (buildd@bos01-ppc64el-023) 
(gcc version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2.1) ) #49-Ubuntu SMP Fri 
Jul 1 10:00:36 UTC 2016 (Ubuntu 4.4.0-30.49-generic 4.4.13)
  Detected machine type: 0101
  Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  command line: BOOT_IMAGE=/ubuntu-installer/ppc64el/yakkety/vmlinux 
tasks=standard pkgsel/language-pack-patterns= 
pkgsel/install-language-support=false DEBIAN_FRONTEND=text locale=en_US 
priority=low console-setup/ask_detect=false console-setup/layoutcode=us 
netcfg/disable_dhcp=true netcfg/confirm_static=true 
netcfg/choose_interface=6c:ae:8b:6a:81:98 netcfg/get_ipaddress=9.40.193.34/24 
netcfg/get_gateway=9.40.193.1 netcfg/get_nameservers=9.3.1.200 
netcfg/get_hostname=ltc-brazos1.aus.stglabs.ibm.com suite=yakkety 
scsi_mod.scan=sync sshd netcfg/get_domain=aus.stglabs.ibm.com unrestricted= 
url=tftp://9.3.80.16/tftpboot/ubuntu-installer/ppc64el/ubuntu-server.seed-01-6c-ae-8b-6a-81-98
 anna/choose_modules=network-console network-console/start=continue 
network-console/password=passw0rd network-console/password-again=passw0rd
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0e3e
alloc_top: 1000
alloc_top_hi : 1000
rmo_top  : 1000
ram_top  : 1000
  instantiating rtas at 0x0e9e... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  No memory for flatten_device_tree (no room)
  EXIT called ok
  0 > 

  
  Regards
  Praveen

  == Comment: #8 - Sukadev Bhattiprolu  - 2016-08-05 02:27:07 ==
  Posted a couple of patches to the community for review: 

  http://marc.info/?l=linux-kernel=147037748624043=2
  http://marc.info/?l=linux-kernel=147037768124064=2 

  == Comment: #12 - Sukadev Bhattiprolu - 2016-08-17 19:23:22 ==

  Temporary fix to address the issue while the above patches are being
  reviewed.

  ==

  Canonical,

  Please add the attached temporary fix to 16.10 to address the
  following issue while the upstream changes are being considered.

 When booting a very large system with a large initrd we run out of space
 for the flattened device tree (FDT). To fix this we must increase the
 space allocated for the RMA region.

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

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

[Kernel-packages] [Bug 1614309] Re: Ubuntu16.10:installation fails on Brazos system (31TB and 192 cores) No memory for flatten_device_tree (no room)

[Tim Gardner]

I guess you'll have to wait until linux 4.4.0-38.57 has been promoted to
updates since the net boot images are not updated until then. I won't
revert this patch for lack of verification. It is obviously powerpc
specific and should not cause regressions.

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

Title:
  Ubuntu16.10:installation fails on Brazos system (31TB and 192 cores)
  No memory for flatten_device_tree (no room)

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:
  == Comment: #0 - Praveen K. Pandey - 2016-07-16 10:00:52 ==
  Hi , 

I tried  ubuntu16.10 Installation in brazos (configuration 31TB memory and 
192 cores) system . installation failing during prom_init when trying to 
allocate flatten_dt memory) System F/w is 
  FW860.00 (TC860_020).

  Reproducible Step :

  1- Configure Power VM  system having profile with  31TB memory and 1 92 Core
  2- Start Ubuntu16.10  Installation 

  Actual Result :

  Installation drop in F/w Console as failing during prom_init

  Expected Result :

  Installation Should went through

  Log:

   Booting a command list

  OF stdout device is: /vdevice/v...@3000nitrd.gz  34.84MiB  100%  
3.01MiB/s ]
  Preparing to boot Linux version 4.4.0-30-generic (buildd@bos01-ppc64el-023) 
(gcc version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2.1) ) #49-Ubuntu SMP Fri 
Jul 1 10:00:36 UTC 2016 (Ubuntu 4.4.0-30.49-generic 4.4.13)
  Detected machine type: 0101
  Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  command line: BOOT_IMAGE=/ubuntu-installer/ppc64el/yakkety/vmlinux 
tasks=standard pkgsel/language-pack-patterns= 
pkgsel/install-language-support=false DEBIAN_FRONTEND=text locale=en_US 
priority=low console-setup/ask_detect=false console-setup/layoutcode=us 
netcfg/disable_dhcp=true netcfg/confirm_static=true 
netcfg/choose_interface=6c:ae:8b:6a:81:98 netcfg/get_ipaddress=9.40.193.34/24 
netcfg/get_gateway=9.40.193.1 netcfg/get_nameservers=9.3.1.200 
netcfg/get_hostname=ltc-brazos1.aus.stglabs.ibm.com suite=yakkety 
scsi_mod.scan=sync sshd netcfg/get_domain=aus.stglabs.ibm.com unrestricted= 
url=tftp://9.3.80.16/tftpboot/ubuntu-installer/ppc64el/ubuntu-server.seed-01-6c-ae-8b-6a-81-98
 anna/choose_modules=network-console network-console/start=continue 
network-console/password=passw0rd network-console/password-again=passw0rd
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0e3e
alloc_top: 1000
alloc_top_hi : 1000
rmo_top  : 1000
ram_top  : 1000
  instantiating rtas at 0x0e9e... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  No memory for flatten_device_tree (no room)
  EXIT called ok
  0 > 

  
  Regards
  Praveen

  == Comment: #8 - Sukadev Bhattiprolu  - 2016-08-05 02:27:07 ==
  Posted a couple of patches to the community for review: 

  http://marc.info/?l=linux-kernel=147037748624043=2
  http://marc.info/?l=linux-kernel=147037768124064=2 

  == Comment: #12 - Sukadev Bhattiprolu - 2016-08-17 19:23:22 ==

  Temporary fix to address the issue while the above patches are being
  reviewed.

  ==

  Canonical,

  Please add the attached temporary fix to 16.10 to address the
  following issue while the upstream changes are being considered.

 When booting a very large system with a large initrd we run out of space
 for the flattened device tree (FDT). To fix this we must increase the
 space allocated for the RMA region.

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

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

[Kernel-packages] [Bug 1609913] s2lp6g002 (s390x.zKVM) - tests ran: 83, failed: 2

[Brad Figg]

tests ran:  83, failed: 2;
  
http://kernel.ubuntu.com/testing/4.6.0-12.14/s2lp6g002__4.6.0-12.14__2016-09-13_14-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/1609913

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

[Kernel-packages] [Bug 1622894] Re: sg devices are not being created for SCSI storage controller devices starting from v4.4.0-30

[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-rc6


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

Title:
  sg devices are not being created for SCSI storage controller devices
  starting from v4.4.0-30

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Most storage array expose a store controller device to logical unit 0.
  Following LP #1567602, when this happens and the alua driver is loaded, 
Ubuntu doesn't create the sg device for it, and linux fails to discover the 
disks that are attached to higher logical unit numbers.

  With kernel version 4.4.0-31, we tried a number of things:
  - With a disk mapped to LUN0, everything is working.
  - Without a disk mapped to LUN0, nothing works - linux doesn't see disks 
mapped to higher LUNs, calling rescan_scsi_bus throws a stack trace to syslog: 
https://gist.github.com/grzn/20c05ce3fc96062ec9572fd5b8093b55
  - When turning on SCSI logging to the maximum 
(https://access.redhat.com/articles/337903 - 0xfff), we see that after ALUA 
driver rejected the SCSI controller nothing happens (look for 18:0:0:0 which is 
a controller here 
(https://gist.github.com/grzn/f8b65dd07b2df5f3f72ca8121d8c93ad) vs 19:0:00 
which is a disk here 
(https://gist.github.com/grzn/48da86b7f7390dab2983927862cda949).
  - When removing the scsi_dh_alua driver and then reloading the lpfc driver, 
everything is working as expected when no disk is mapped to LUN0.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 12 18:00 seq
   crw-rw 1 root audio 116, 33 Sep 12 18:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=1b089ce2-057f-44d6-9e53-5ee1b7fb5be9
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=6738fbd7-7243-4860-949f-717dfd084c43 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.3
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 09/17/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/17/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/1622894/+subscriptions

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

[Kernel-packages] [Bug 1618572] Re: apt-key add fails in overlayfs

[Scott Moser]

trusty + linux-virtual-lts-xenial looks good also.

ubuntu@sm-y1:~$ uname -r
4.4.0-38-generic
ubuntu@sm-y1:~$ dpkg -S /boot/vmlinuz-$(uname -r)
linux-image-4.4.0-38-generic: /boot/vmlinuz-4.4.0-38-generic
ubuntu@sm-y1:~$ grep overlay /proc/mounts 
overlayroot / overlayfs rw,relatime,lowerdir=/media/root-ro,upperdir=/media/root
-rw//overlay,workdir=/media/root-rw//overlay-workdir 0 0
ubuntu@sm-y1:~$ lsb_release -sc 
trusty

$ dpkg-query --show | grep linux- | grep -v headers
linux-image-3.13.0-95-generic   3.13.0-95.142
linux-image-3.13.0-96-generic   3.13.0-96.143
linux-image-4.4.0-36-generic4.4.0-36.55~14.04.1
linux-image-4.4.0-38-generic4.4.0-38.57~14.04.1
linux-image-virtual 3.13.0.96.104
linux-image-virtual-lts-xenial  4.4.0.38.28
linux-virtual   3.13.0.96.104
linux-virtual-lts-xenial4.4.0.38.28

$ sudo apt-key add my.pubkey
OK

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

Title:
  apt-key add fails in overlayfs

Status in cloud-init:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Sending a custom APT config to cloud-init fails to:
  1. add keys
  2. configure sources
  3. configura additional repository.

  The same config is being sent to curtin, and curtin doesn't seem to
  fail (curtin install log http://paste.ubuntu.com/23112826/ just in
  case).

  config sent by maas = http://pastebin.ubuntu.com/23112834/
  cloud-init.log = http://paste.ubuntu.com/23112820/
  cloud-init-output.log = http://paste.ubuntu.com/23112822/
  sources.list = http://paste.ubuntu.com/23112824/
  ubuntu@node03:/var/log$ ls -l /etc/apt/sources.list.d/
  total 0

  
  ubuntu@node03:/var/log$ sudo apt-get update
  Hit:2 http://us.archive.ubuntu.com/ubuntu yakkety-updates InRelease
  Get:3 http://us.archive.ubuntu.com/ubuntu yakkety-backports InRelease [92.2 
kB]
  Err:2 http://us.archive.ubuntu.com/ubuntu yakkety-updates InRelease
The following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  Ign:3 http://us.archive.ubuntu.com/ubuntu yakkety-backports InRelease
  Hit:4 http://us.archive.ubuntu.com/ubuntu yakkety-security InRelease
  Get:1 http://us.archive.ubuntu.com/ubuntu yakkety InRelease [247 kB]
  Err:4 http://us.archive.ubuntu.com/ubuntu yakkety-security InRelease
The following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  Err:1 http://us.archive.ubuntu.com/ubuntu yakkety InRelease
The following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  Fetched 339 kB in 0s (388 kB/s)
  Reading package lists... Error!
  W: An error occurred during the signature verification. The repository is not 
updated and the previous index files will be used. GPG error: 
http://us.archive.ubuntu.com/ubuntu yakkety-updates InRelease: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: GPG error: http://us.archive.ubuntu.com/ubuntu yakkety-backports 
InRelease: The following signatures couldn't be verified because the public key 
is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: The repository 'http://us.archive.ubuntu.com/ubuntu yakkety-backports 
InRelease' is not signed.
  N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: An error occurred during the signature verification. The repository is not 
updated and the previous index files will be used. GPG error: 
http://us.archive.ubuntu.com/ubuntu yakkety-security InRelease: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: An error occurred during the signature verification. The repository is not 
updated and the previous index files will be used. GPG error: 
http://us.archive.ubuntu.com/ubuntu yakkety InRelease: The following signatures 
couldn't be verified because the public key is not available: NO_PUBKEY 
40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: Failed to fetch 
http://us.archive.ubuntu.com/ubuntu/dists/yakkety/InRelease  The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: Failed to fetch 
http://us.archive.ubuntu.com/ubuntu/dists/yakkety-updates/InRelease  The 
following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: Failed to fetch 

[Kernel-packages] [Bug 1609913] s2lp6g002 (s390x.zKVM) - tests ran: 2, failed: 0

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.6.0-12.14/s2lp6g002__4.6.0-12.14__2016-09-13_15-06-00/results-index.html

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

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

[Kernel-packages] [Bug 1550779] Re: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

[Alan Robertson]

I just took some updates to a number of graphic libraries on 16.04, and
now I can't login to kubuntu. The symptom is that it takes my password
on the greeter screen, but never updates the screen after that.

The messages include these apparently related kernel messages:
kernel: [  701.564034] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] 
*ERROR* uncleared fifo underrun on pipe B
kernel: [  701.564054] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* 
CPU pipe B FIFO underrun

It is, of course, unclear whether these libraries triggered the kernel
bug or if this is unrelated to the kernel bug. I attached it here
because this is what I noticed first.

I'm currently running kernel 4.4.0-36.

Here are my most recent updates. The problem started after I rebooted.
Of course that was the next time I logged in too...

Start-Date: 2016-09-07  08:46:04
Commandline: /usr/bin/unattended-upgrade
Remove: libcdaudio1:amd64 (0.99.12p2-14), 
linux-image-extra-4.2.0-36-generic:amd64 (4.2.0-36.42), 
linux-image-extra-4.4.0-22-generic:amd64 (4.4.0-22.40), 
gtk2-engines-murrine:amd64 (0.98.2-0ubuntu2.1), 
linux-image-extra-4.4.0-24-generic:amd64 (4.4.0-24.43), libslv2-9:amd64 
(0.6.6+dfsg1-3build1), linux-image-extra-4.4.0-28-generic:amd64 (4.4.0-28.47), 
linux-image-extra-4.4.0-31-generic:amd64 (4.4.0-31.50), libfaac0:amd64 
(1.28+cvs20151130-1)
End-Date: 2016-09-07  08:48:13

Start-Date: 2016-09-07  16:42:27
Install: libgnome-keyring-common:amd64 (3.12.0-1build1, automatic), 
libgnome-keyring0:amd64 (3.12.0-1build1, automatic)
Upgrade: libgles2-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgles1-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libglapi-mesa:amd64 
(11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libglapi-mesa:i386 (11.2.0-1ubuntu2.1, 
11.2.0-1ubuntu2.2), p11-kit:amd64 (0.23.2-3, 0.23.2-5~ubuntu16.04.1), 
libxatracker2:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libegl1-mesa-drivers:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libegl1-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libegl1-mesa:i386 
(11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), p11-kit-modules:amd64 (0.23.2-3, 
0.23.2-5~ubuntu16.04.1), libgbm1:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgbm1:i386 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), cups-filters:amd64 
(1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), chromium-browser:amd64 
(51.0.2704.79-0ubuntu0.16.04.1.1242, 52.0.2743.116-0ubuntu0.16.04.1.1250), 
libcupsfilters1:amd64 (1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), 
chromium-codecs-ffmpeg-extra:amd64 (51.0.2704.79-0ubuntu0.16.04.1.1242, 52.0.274
 3.116-0ubuntu0.16.04.1.1250), libwayland-egl1-mesa:amd64 (11.2.0-1ubuntu2.1, 
11.2.0-1ubuntu2.2), libfontembed1:amd64 (1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), 
libgl1-mesa-dri:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgl1-mesa-dri:i386 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
cups-filters-core-drivers:amd64 (1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), 
libgl1-mesa-glx:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgl1-mesa-glx:i386 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libp11-kit0:amd64 
(0.23.2-3, 0.23.2-5~ubuntu16.04.1), libp11-kit0:i386 (0.23.2-3, 
0.23.2-5~ubuntu16.04.1), mesa-vdpau-drivers:amd64 (11.2.0-1ubuntu2.1, 
11.2.0-1ubuntu2.2), chromium-browser-l10n:amd64 
(51.0.2704.79-0ubuntu0.16.04.1.1242, 52.0.2743.116-0ubuntu0.16.04.1.1250), 
ubuntu-mono:amd64 (14.04+16.04.20160621-0ubuntu1, 
14.04+16.04.20160804-0ubuntu1), cups-browsed:amd64 (1.8.3-2ubuntu3, 
1.8.3-2ubuntu3.1)
End-Date: 2016-09-07  16:44:34

Start-Date: 2016-09-12  14:31:39
Commandline: /usr/sbin/synaptic
Requested-By: alanr (1000)
Upgrade: snapd:amd64 (2.13, 2.14.2~16.04), libappstream-glib8:amd64 
(0.5.13-1ubuntu2, 0.5.13-1ubuntu3), neo4j:amd64 (3.0.4, 3.0.5), 
accountsservice:amd64 (0.6.40-2ubuntu11.1, 0.6.40-2ubuntu11.2), 
libaccountsservice0:amd64 (0.6.40-2ubuntu11.1, 0.6.40-2ubuntu11.2)
End-Date: 2016-09-12  14:32:17


** Attachment added: "Syslog from my failed attempt to log in."
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779/+attachment/4740111/+files/syslog.error

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

Title:
  [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches,
  looks like the graphic buffer gets screwed up

  - funny repetition's patterns  (back in time glitches)
  - black screen (<1sec)
  - graphic errors  

  I can influence the severity of the issue with switching windows and
  using certain programs, e.g. Google Maps in chrome causes this issue
  reproducibly

  dmesg  | grep i915
  [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on 
minor 0
  [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit 
banging on pin 5
  [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device
  [ 

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

[bugproxy]

--- Comment From ru...@us.ibm.com 2016-09-13 10:16 EDT---
(In reply to comment #30)
> You should be testing at least linux 4.4.0-38.57 in proposed.

Hi Tim.

Do you have specific instructions on how to do so for the *install*?
Since the netboot image is not using that kernel, the system doesn't
make it far enough into the install process to pick up a non-install
kernel like mentioned above.

Thanks

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

Title:
  Ubuntu16.10:installation fails on Brazos system (31TB and 192 cores)
  No memory for flatten_device_tree (no room)

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:
  == Comment: #0 - Praveen K. Pandey - 2016-07-16 10:00:52 ==
  Hi , 

I tried  ubuntu16.10 Installation in brazos (configuration 31TB memory and 
192 cores) system . installation failing during prom_init when trying to 
allocate flatten_dt memory) System F/w is 
  FW860.00 (TC860_020).

  Reproducible Step :

  1- Configure Power VM  system having profile with  31TB memory and 1 92 Core
  2- Start Ubuntu16.10  Installation 

  Actual Result :

  Installation drop in F/w Console as failing during prom_init

  Expected Result :

  Installation Should went through

  Log:

   Booting a command list

  OF stdout device is: /vdevice/v...@3000nitrd.gz  34.84MiB  100%  
3.01MiB/s ]
  Preparing to boot Linux version 4.4.0-30-generic (buildd@bos01-ppc64el-023) 
(gcc version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2.1) ) #49-Ubuntu SMP Fri 
Jul 1 10:00:36 UTC 2016 (Ubuntu 4.4.0-30.49-generic 4.4.13)
  Detected machine type: 0101
  Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  command line: BOOT_IMAGE=/ubuntu-installer/ppc64el/yakkety/vmlinux 
tasks=standard pkgsel/language-pack-patterns= 
pkgsel/install-language-support=false DEBIAN_FRONTEND=text locale=en_US 
priority=low console-setup/ask_detect=false console-setup/layoutcode=us 
netcfg/disable_dhcp=true netcfg/confirm_static=true 
netcfg/choose_interface=6c:ae:8b:6a:81:98 netcfg/get_ipaddress=9.40.193.34/24 
netcfg/get_gateway=9.40.193.1 netcfg/get_nameservers=9.3.1.200 
netcfg/get_hostname=ltc-brazos1.aus.stglabs.ibm.com suite=yakkety 
scsi_mod.scan=sync sshd netcfg/get_domain=aus.stglabs.ibm.com unrestricted= 
url=tftp://9.3.80.16/tftpboot/ubuntu-installer/ppc64el/ubuntu-server.seed-01-6c-ae-8b-6a-81-98
 anna/choose_modules=network-console network-console/start=continue 
network-console/password=passw0rd network-console/password-again=passw0rd
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0e3e
alloc_top: 1000
alloc_top_hi : 1000
rmo_top  : 1000
ram_top  : 1000
  instantiating rtas at 0x0e9e... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  No memory for flatten_device_tree (no room)
  EXIT called ok
  0 > 

  
  Regards
  Praveen

  == Comment: #8 - Sukadev Bhattiprolu  - 2016-08-05 02:27:07 ==
  Posted a couple of patches to the community for review: 

  http://marc.info/?l=linux-kernel=147037748624043=2
  http://marc.info/?l=linux-kernel=147037768124064=2 

  == Comment: #12 - Sukadev Bhattiprolu - 2016-08-17 19:23:22 ==

  Temporary fix to address the issue while the above patches are being
  reviewed.

  ==

  Canonical,

  Please add the attached temporary fix to 16.10 to address the
  following issue while the upstream changes are being considered.

 When booting a very large system with a large initrd we run out of space
 for the flattened device tree (FDT). To fix this we must increase the
 space allocated for the RMA region.

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

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

[Kernel-packages] [Bug 1242321] Re: USB 3.0 Harddrive not recognised

[Dr. Karl-Heinz Ziessow]

Hi,
the same problem her with Asus E200HA, 64bit, Ubuntu Gnome 16.04 LTS.
The harddisk at USB3 works once when connected at startup, but never again when 
disconnected.

SYSTEM INFO
   system E200HA (ASUS-NotebookSKU)
/0 busE200HA
/0/0   memory 64KiB BIOS
/0/a   memory 2GiB Systemspeicher
/0/a/0 memory 2GiB DIMM DDR3 1600 MHz (0,6 ns)
/0/a/1 memory DIMMProject-Id-Version: lshwReport-Msgid-B
/0/11  memory 224KiB L1 Cache
/0/12  memory 2MiB L2 Cache
/0/13  processor  Intel(R) Atom(TM) x5-Z8300  CPU @ 1.44GHz
/0/100 bridge Intel Corporation
/0/100/2   displayIntel Corporation
/0/100/b   genericIntel Corporation
/0/100/14  busIntel Corporation
/0/100/14/0usb1busxHCI Host Controller
/0/100/14/0/1  multimedia USB2.0 VGA UVC WebCam
/0/100/14/0/3  communication  Bluetooth-Schnittstelle
/0/100/14/0/4  input  U+P Mouse
/0/100/14/1usb2busxHCI Host Controller
/0/100/14/1/1  storageExternal USB 3.0
/0/100/1a  genericIntel Corporation
/0/100/1c  bridge Intel Corporation
/0/100/1c/0wlp1s0  networkQualcomm Atheros
/0/100/1f  bridge Intel Corporation


CONNECTION MESSAGES
[  231.291890] usb 2-1: new SuperSpeed USB device number 3 using xhci_hcd
[  231.310300] usb 2-1: New USB device found, idVendor=0480, idProduct=a202
[  231.310324] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  231.310338] usb 2-1: Product: External USB 3.0
[  231.310350] usb 2-1: Manufacturer: TOSHIBA
[  231.310362] usb 2-1: SerialNumber: 20151231001889C
[  231.312379] usb-storage 2-1:1.0: USB Mass Storage device detected
[  231.316046] scsi host0: usb-storage 2-1:1.0
[  253.805170] usb 2-1: Disable of device-initiated U1 failed.
[  258.800433] usb 2-1: Disable of device-initiated U2 failed.
[  258.968598] usb 2-1: reset SuperSpeed USB device number 3 using xhci_hcd

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

Title:
  USB 3.0 Harddrive not recognised

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is not recognising any device plugged into any USB 3.0 ports.
  Sometimes Ubuntu will freeze for a few seconds when you plug something
  into a USB 3.0 port; when Ubuntu comes out of the freeze, the device
  is still NOT recognised.

  No problems with USB 2.0 ports and devices.

  The USB 3.0 on this computer only works in Windows 7 (I'm dual booting
  Ubuntu 13.10 and Windows 7, both are 64-bit).

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

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

[Kernel-packages] [Bug 1609913] s2lp6g002 (s390x.zKVM) - tests ran: 32, failed: 32

[Brad Figg]

tests ran:  32, failed: 32;
  
http://kernel.ubuntu.com/testing/4.6.0-12.14/s2lp6g002__4.6.0-12.14__2016-09-13_14-01-00/results-index.html

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

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

[Kernel-packages] [Bug 1609913] s2lp6g002 (s390x.zKVM) - tests ran: 4, failed: 4

[Brad Figg]

tests ran:   4, failed: 4;
  
http://kernel.ubuntu.com/testing/4.6.0-10.12/s2lp6g002__4.6.0-10.12__2016-09-13_13-52-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/1609913

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

[Kernel-packages] [Bug 1609913] s2lp6g002 (s390x.zKVM) - tests ran: 10, failed: 10

[Brad Figg]

tests ran:  10, failed: 10;
  
http://kernel.ubuntu.com/testing/4.6.0-10.12/s2lp6g002__4.6.0-10.12__2016-09-13_13-43-00/results-index.html

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

Title:
  linux: 4.6.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.6.0-10.12 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-development-workflow/+bug/1609913/+subscriptions

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

[Kernel-packages] [Bug 1614309] Re: Ubuntu16.10:installation fails on Brazos system (31TB and 192 cores) No memory for flatten_device_tree (no room)

[Tim Gardner]

You should be testing at least linux 4.4.0-38.57 in proposed.

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

Title:
  Ubuntu16.10:installation fails on Brazos system (31TB and 192 cores)
  No memory for flatten_device_tree (no room)

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:
  == Comment: #0 - Praveen K. Pandey - 2016-07-16 10:00:52 ==
  Hi , 

I tried  ubuntu16.10 Installation in brazos (configuration 31TB memory and 
192 cores) system . installation failing during prom_init when trying to 
allocate flatten_dt memory) System F/w is 
  FW860.00 (TC860_020).

  Reproducible Step :

  1- Configure Power VM  system having profile with  31TB memory and 1 92 Core
  2- Start Ubuntu16.10  Installation 

  Actual Result :

  Installation drop in F/w Console as failing during prom_init

  Expected Result :

  Installation Should went through

  Log:

   Booting a command list

  OF stdout device is: /vdevice/v...@3000nitrd.gz  34.84MiB  100%  
3.01MiB/s ]
  Preparing to boot Linux version 4.4.0-30-generic (buildd@bos01-ppc64el-023) 
(gcc version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2.1) ) #49-Ubuntu SMP Fri 
Jul 1 10:00:36 UTC 2016 (Ubuntu 4.4.0-30.49-generic 4.4.13)
  Detected machine type: 0101
  Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  command line: BOOT_IMAGE=/ubuntu-installer/ppc64el/yakkety/vmlinux 
tasks=standard pkgsel/language-pack-patterns= 
pkgsel/install-language-support=false DEBIAN_FRONTEND=text locale=en_US 
priority=low console-setup/ask_detect=false console-setup/layoutcode=us 
netcfg/disable_dhcp=true netcfg/confirm_static=true 
netcfg/choose_interface=6c:ae:8b:6a:81:98 netcfg/get_ipaddress=9.40.193.34/24 
netcfg/get_gateway=9.40.193.1 netcfg/get_nameservers=9.3.1.200 
netcfg/get_hostname=ltc-brazos1.aus.stglabs.ibm.com suite=yakkety 
scsi_mod.scan=sync sshd netcfg/get_domain=aus.stglabs.ibm.com unrestricted= 
url=tftp://9.3.80.16/tftpboot/ubuntu-installer/ppc64el/ubuntu-server.seed-01-6c-ae-8b-6a-81-98
 anna/choose_modules=network-console network-console/start=continue 
network-console/password=passw0rd network-console/password-again=passw0rd
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0e3e
alloc_top: 1000
alloc_top_hi : 1000
rmo_top  : 1000
ram_top  : 1000
  instantiating rtas at 0x0e9e... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  No memory for flatten_device_tree (no room)
  EXIT called ok
  0 > 

  
  Regards
  Praveen

  == Comment: #8 - Sukadev Bhattiprolu  - 2016-08-05 02:27:07 ==
  Posted a couple of patches to the community for review: 

  http://marc.info/?l=linux-kernel=147037748624043=2
  http://marc.info/?l=linux-kernel=147037768124064=2 

  == Comment: #12 - Sukadev Bhattiprolu - 2016-08-17 19:23:22 ==

  Temporary fix to address the issue while the above patches are being
  reviewed.

  ==

  Canonical,

  Please add the attached temporary fix to 16.10 to address the
  following issue while the upstream changes are being considered.

 When booting a very large system with a large initrd we run out of space
 for the flattened device tree (FDT). To fix this we must increase the
 space allocated for the RMA region.

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

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

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

[Eric Desrochers]

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

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

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

** Tags added: sts

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

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

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

Bug description:
  [Impact]

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

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

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

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

  [Test Case]

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

  [Regression Potential]

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

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

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

[Kernel-packages] [Bug 1618572] Re: apt-key add fails in overlayfs

[Scott Moser]

I booted a xenial guest as shown in my comment 10, added -proposed and
rebooted into overlayfs

ubuntu@sm-y1:~$ uname -r
4.4.0-38-generic
ubuntu@sm-y1:~$ dpkg -S /boot/vmlinuz-4.4.0-38-generic 
linux-image-4.4.0-38-generic: /boot/vmlinuz-4.4.0-38-generic

$ grep overlayroot /proc/mounts 
overlayroot / overlayfs 
rw,relatime,lowerdir=/media/root-ro,upperdir=/media/root-rw//overlay,workdir=/media/root-rw//overlay-workdir
 0 0

$ sudo apt-key add my.pubkey
OK


So xenial looks good to me.

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

Title:
  apt-key add fails in overlayfs

Status in cloud-init:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Sending a custom APT config to cloud-init fails to:
  1. add keys
  2. configure sources
  3. configura additional repository.

  The same config is being sent to curtin, and curtin doesn't seem to
  fail (curtin install log http://paste.ubuntu.com/23112826/ just in
  case).

  config sent by maas = http://pastebin.ubuntu.com/23112834/
  cloud-init.log = http://paste.ubuntu.com/23112820/
  cloud-init-output.log = http://paste.ubuntu.com/23112822/
  sources.list = http://paste.ubuntu.com/23112824/
  ubuntu@node03:/var/log$ ls -l /etc/apt/sources.list.d/
  total 0

  
  ubuntu@node03:/var/log$ sudo apt-get update
  Hit:2 http://us.archive.ubuntu.com/ubuntu yakkety-updates InRelease
  Get:3 http://us.archive.ubuntu.com/ubuntu yakkety-backports InRelease [92.2 
kB]
  Err:2 http://us.archive.ubuntu.com/ubuntu yakkety-updates InRelease
The following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  Ign:3 http://us.archive.ubuntu.com/ubuntu yakkety-backports InRelease
  Hit:4 http://us.archive.ubuntu.com/ubuntu yakkety-security InRelease
  Get:1 http://us.archive.ubuntu.com/ubuntu yakkety InRelease [247 kB]
  Err:4 http://us.archive.ubuntu.com/ubuntu yakkety-security InRelease
The following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  Err:1 http://us.archive.ubuntu.com/ubuntu yakkety InRelease
The following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  Fetched 339 kB in 0s (388 kB/s)
  Reading package lists... Error!
  W: An error occurred during the signature verification. The repository is not 
updated and the previous index files will be used. GPG error: 
http://us.archive.ubuntu.com/ubuntu yakkety-updates InRelease: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: GPG error: http://us.archive.ubuntu.com/ubuntu yakkety-backports 
InRelease: The following signatures couldn't be verified because the public key 
is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: The repository 'http://us.archive.ubuntu.com/ubuntu yakkety-backports 
InRelease' is not signed.
  N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: An error occurred during the signature verification. The repository is not 
updated and the previous index files will be used. GPG error: 
http://us.archive.ubuntu.com/ubuntu yakkety-security InRelease: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: An error occurred during the signature verification. The repository is not 
updated and the previous index files will be used. GPG error: 
http://us.archive.ubuntu.com/ubuntu yakkety InRelease: The following signatures 
couldn't be verified because the public key is not available: NO_PUBKEY 
40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: Failed to fetch 
http://us.archive.ubuntu.com/ubuntu/dists/yakkety/InRelease  The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: Failed to fetch 
http://us.archive.ubuntu.com/ubuntu/dists/yakkety-updates/InRelease  The 
following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: Failed to fetch 
http://us.archive.ubuntu.com/ubuntu/dists/yakkety-security/InRelease  The 
following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.
  E: Problem renaming the file /var/cache/apt/srcpkgcache.bin.3HKvbX to 

[Kernel-packages] [Bug 1602724] Re: Ubuntu 16.04 - Full EEH Recovery Support for NVMe devices

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2016-September/079944.html

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