date:20180124

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1745049

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

** Tags added: bionic

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

Title:
  Bumblebee crashes during boot with kernel 4.13.0.31 on Bionic

Status in bumblebee package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My laptop (Dell XPS 15 9560) fails to boot to the login screen when bumblebee 
is installed and running with the latest Bionic kernel 4.13.0.31.  I recently 
upgraded to Bionic using update-manager -d.
  My workaround is to use the old kernel 4.13.0.25.26 instead.  My laptop boots 
fine with the old kernel and bumblebee works.
  I suspect there is some problem with bumblebee's compatibility with the new 
kernel.

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

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

[Kernel-packages] [Bug 1730152] Re: Internal microsd card reader does not work in Ubuntu 17.10

2018-01-24 Thread sfc

@funicorn Yes. Put that dkms.conf in the same ampe_stor directory and
use "dkms add" to add it. Please refer to
https://help.ubuntu.com/community/DKMS and https://github.com/dell/dkms
for detailed instructions.

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

Title:
  Internal microsd card reader does not work in Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 x86_64 of Wayland-Session is running on a HP Envy
  13-ad1xx notbook with a internal microsd card reader. The system gives
  no response when inserting different micro sd cards, which work fine
  on Windows 10. I report this bug in hope that the upstream may notice
  and make some change on the suited driver or kernel module. I would
  provide more information under further direction.

  According to `lspci` output, the model name is 'Alcor Micro Device
  6625'.

  `udevadm monitor --env` gives no related events when inserting or
  pulling out the microsd card, in which only thermal_zone changes are
  recorded. No related events are recoded in /var/log/kern.log either.

  With sd card being inserted, `sudo fdisk -l` and `sudo blkid` gives no
  related information. The outputs are all about partitions on the local
  disk. No sdhc or mmc device is found in /dev/ either.

  The only implication now is the system notice the existence of the
  card reader, in terms of `lspci` outputs, the '01:00.0 Unassigned
  class [ff00]: Alcor Micro Device 6625', even when a sd card is
  inserted:

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   limorg 1514 F...m pulseaudio
   /dev/snd/controlC0:  limorg 1514 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  5 10:29:26 2017
  HibernationDevice: RESUME=UUID=8f370e7c-280d-4864-b687-a2c81ce87247
  InstallationDate: Installed on 2017-10-22 (13 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  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 0bda:5620 Realtek Semiconductor Corp.
   Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY Laptop 13-ad1xx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=67e321d1-4810-4157-8c29-09c51ea7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-29 (6 days ago)
  dmi.bios.date: 07/26/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.12
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83A8
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 39.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.12:bd07/26/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A8:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY Laptop 13-ad1xx
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1745049] Re: Bumblebee crashes during boot with kernel 4.13.0.31 on Bionic

2018-01-24 Thread walkerstreet

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

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

Title:
  Bumblebee crashes during boot with kernel 4.13.0.31 on Bionic

Status in bumblebee package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  My laptop (Dell XPS 15 9560) fails to boot to the login screen when bumblebee 
is installed and running with the latest Bionic kernel 4.13.0.31.  I recently 
upgraded to Bionic using update-manager -d.
  My workaround is to use the old kernel 4.13.0.25.26 instead.  My laptop boots 
fine with the old kernel and bumblebee works.
  I suspect there is some problem with bumblebee's compatibility with the new 
kernel.

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

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

[Kernel-packages] [Bug 1745119] Re: 4.13.0-31 hibernate doesn't work

2018-01-24 Thread Nicholas Taylor

I can confirm that hibernate works on 4.13.0-21 but is broken in
4.13.0-25 and 4.13.0-31.

I have reviewed syslog and kern.log but don't see any entries regarding
the failed resume attempt.

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

Title:
  4.13.0-31 hibernate doesn't work

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

Bug description:
  Hibernate process seems work and laptop (acer aspire v5-571G) shuts down
  But then laptop doesn't turn on. Blank screen and you must to force shut down 
with power button.
  You must start system with another kernel.

  I had the same problem with 4.13.0-26

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

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

[Kernel-packages] [Bug 1745054] Re: Xenial update to 4.4.108 stable release

drivers/misc/cxl/pci.c seems to have been heavily changed between Xenial
and 4.4-stable . This affects the following patch:

* cxl: Check if vphb exists before iterating over AFU devices


Though I think in the end I applied it correctly (still an additional pair of 
eyes would be appreciated).

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

Title:
  Xenial update to 4.4.108 stable release

Status in linux package in Ubuntu:
  New

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the 4.4.108 stable release shall be applied:
  * arm64: Initialise high_memory global variable earlier
  * cxl: Check if vphb exists before iterating over AFU devices
  * x86/mm: Add INVPCID helpers
  * x86/mm: Fix INVPCID asm constraint
  * x86/mm: Add a 'noinvpcid' boot option to turn off INVPCID
  * x86/mm: If INVPCID is available, use it to flush global mappings
  * mm/rmap: batched invalidations should use existing api
  * mm/mmu_context, sched/core: Fix mmu_context.h assumption
  * sched/core: Add switch_mm_irqs_off() and use it in the scheduler
  * x86/mm: Build arch/x86/mm/tlb.c even on !SMP
  * x86/mm, sched/core: Uninline switch_mm()
  * x86/mm, sched/core: Turn off IRQs in switch_mm()
  * ARM: Hide finish_arch_post_lock_switch() from modules
  * sched/core: Idle_task_exit() shouldn't use switch_mm_irqs_off()
  * x86/irq: Do not substract irq_tlb_count from irq_call_count
  * ALSA: hda - add support for docking station for HP 820 G2
  * ALSA: hda - add support for docking station for HP 840 G3
  * arm: kprobes: Fix the return address of multiple kretprobes
  * arm: kprobes: Align stack to 8-bytes in test code
  * cpuidle: Validate cpu_dev in cpuidle_add_sysfs()
  * r8152: fix the list rx_done may be used without initialization
  * crypto: deadlock between crypto_alg_sem/rtnl_mutex/genl_mutex
  * sch_dsmark: fix invalid skb_cow() usage
  * bna: integer overflow bug in debugfs
  * net: qmi_wwan: Add USB IDs for MDM6600 modem on Motorola Droid 4
  * usb: gadget: f_uvc: Sanity check wMaxPacketSize for SuperSpeed
  * usb: gadget: udc: remove pointer dereference after free
  * netfilter: nfnl_cthelper: fix runtime expectation policy updates
  * netfilter: nfnl_cthelper: Fix memory leak
  * inet: frag: release spinlock before calling icmp_send()
  * pinctrl: st: add irq_request/release_resources callbacks
  * scsi: lpfc: Fix PT2PT PRLI reject
  * KVM: x86: correct async page present tracepoint
  * KVM: VMX: Fix enable VPID conditions
  * ARM: dts: ti: fix PCI bus dtc warnings
  * hwmon: (asus_atk0110) fix uninitialized data access
  * HID: xinmo: fix for out of range for THT 2P arcade controller.
  * r8152: prevent the driver from transmitting packets with carrier off
  * s390/qeth: no ETH header for outbound AF_IUCV
  * bna: avoid writing uninitialized data into hw registers
  * net: Do not allow negative values for busy_read and busy_poll sysctl 
interfaces
  * i40e: Do not enable NAPI on q_vectors that have no rings
  * RDMA/iser: Fix possible mr leak on device removal event
  * irda: vlsi_ir: fix check for DMA mapping errors
  * netfilter: nfnl_cthelper: fix a race when walk the nf_ct_helper_hash table
  * netfilter: nf_nat_snmp: Fix panic when snmp_trap_helper fails to register
  * ARM: dts: am335x-evmsk: adjust mmc2 param to allow suspend
  * KVM: pci-assign: do not map smm memory slot pages in vt-d page tables
  * isdn: kcapi: avoid uninitialized data
  * xhci: plat: Register shutdown for xhci_plat
  * netfilter: nfnetlink_queue: fix secctx memory leak
  * ARM: dma-mapping: disallow dma_get_sgtable() for non-kernel managed memory
  * cpuidle: powernv: Pass correct drv->cpumask for registration
  * bnxt_en: Fix NULL pointer dereference in reopen failure path
  * backlight: pwm_bl: Fix overflow condition
  * crypto: crypto4xx - increase context and scatter ring buffer elements
  * rtc: pl031: make interrupt optional
  * net: phy: at803x: Change error to EINVAL for invalid MAC
  * PCI: Avoid bus reset if bridge itself is broken
  * scsi: cxgb4i: fix Tx skb leak
  * scsi: mpt3sas: Fix IO error occurs on pulling out a drive from RAID1 volume 
created on two SATA drive
  * PCI: Create SR-IOV virtfn/physfn links before attaching driver
  * igb: check memory allocation failure
  * ixgbe: fix use of uninitialized padding
  * PCI/AER: Report non-fatal errors only to

[Kernel-packages] [Bug 1727662] Re: [Lenovo ThinkPad T450s] Issues after docking and locking: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] ERROR CPU pipe A FIFO underrun

2018-01-24 Thread lanrat

I think I am having the same issue on my DELL XPS 13 with intel graphics
(no dock).

Is this what you are all seeing?
https://www.youtube.com/watch?v=2g2GRca3nik

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

Title:
  [Lenovo ThinkPad T450s] Issues after docking and locking:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  What happens is after I dock my laptop into a Lenovo ThinkPad Ultra Dock Type 
40A2 20V, lock it via clicking the lock icon, and wait ~30 minutes, one of the 
following three things happen ~50% of the time when I come back to unlock it:
  * Most of the time the computer is found shut down.
  * Sometimes the notebook screen flickers weirdly and one of the two external 
monitors show pixelation.
  * The notebook screen shows the lock screen but is completely frozen. 
Occasionally unlocking works.

  I have two external monitors attached to the docking station.

  When I dock my laptop, the battery indicator does recognize its
  charging.

  I've not seen this issue when:
  1) With the laptop in the dock, while actively using the laptop.
  2) With the laptop out of the dock and no external monitors present.

  This bug started after upgrading from Ubtuntu 17.04 to Ubuntu 17.10.

  Using or not using the following kernel parameter didn't change anything:
  i915.enable_rc6=0

  Updated docking station firmware to latest 2.33.00.

  PC temperatures are normal as per lm-sensors.

  20171109 - Not reproducible testing drm-tip for 1.5 days.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  akops  3337 F pulseaudio
   /dev/snd/controlC0:  akops  3337 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:44:11 2017
  HibernationDevice: RESUME=/dev/mapper/system-swap_1
  MachineType: LENOVO 20BWS2YL00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency 
root=/dev/mapper/system-root ro quiet splash i915.enable_rc6=0 
crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-lowlatency N/A
   linux-backports-modules-4.13.0-16-lowlatency  N/A
   linux-firmware1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago)
  dmi.bios.date: 07/08/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET51WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS2YL00
  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:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BWS2YL00:pvrThinkPadT450s:rvnLENOVO:rn20BWS2YL00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS2YL00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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

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

This change was made by a bot.

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

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

Title:
  Freezes XPS 13

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This kernel boots on the XPS 13 but in less than a minute it hard
  freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahron  2235 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 24 22:41:26 2018
  InstallationDate: Installed on 2018-01-04 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. XPS 13 9360
  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.13.0-25-generic.efi.signed 
root=UUID=5b8ac06d-8cf5-4417-85d2-df12f2d0dc30 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.0
  dmi.board.name: 0PVG6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.0:bd12/12/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PVG6D:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1745282] [NEW] Freezes XPS 13

2018-01-24 Thread AhronZombi

Public bug reported:

This kernel boots on the XPS 13 but in less than a minute it hard
freezes

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-31-generic 4.13.0-31.34
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ahron  2235 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 24 22:41:26 2018
InstallationDate: Installed on 2018-01-04 (20 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Dell Inc. XPS 13 9360
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.13.0-25-generic.efi.signed 
root=UUID=5b8ac06d-8cf5-4417-85d2-df12f2d0dc30 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-25-generic N/A
 linux-backports-modules-4.13.0-25-generic  N/A
 linux-firmware 1.169.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.5.0
dmi.board.name: 0PVG6D
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.0:bd12/12/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PVG6D:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  Freezes XPS 13

Status in linux package in Ubuntu:
  New

Bug description:
  This kernel boots on the XPS 13 but in less than a minute it hard
  freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahron  2235 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 24 22:41:26 2018
  InstallationDate: Installed on 2018-01-04 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. XPS 13 9360
  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.13.0-25-generic.efi.signed 
root=UUID=5b8ac06d-8cf5-4417-85d2-df12f2d0dc30 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.0
  dmi.board.name: 0PVG6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.0:bd12/12/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PVG6D:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1745282] Re: Freezes XPS 13

2018-01-24 Thread AhronZombi

Please fix before next kernel release

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

Title:
  Freezes XPS 13

Status in linux package in Ubuntu:
  New

Bug description:
  This kernel boots on the XPS 13 but in less than a minute it hard
  freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahron  2235 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 24 22:41:26 2018
  InstallationDate: Installed on 2018-01-04 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. XPS 13 9360
  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.13.0-25-generic.efi.signed 
root=UUID=5b8ac06d-8cf5-4417-85d2-df12f2d0dc30 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.0
  dmi.board.name: 0PVG6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.0:bd12/12/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PVG6D:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1745071] Re: Xenial update to 4.4.110 stable release

Note also that a few patches were referring to
arch/x86/include/asm/cpufeature.h , however, looking at the code it
appears the patches really should be applied (in our tree at least) to
arch/x86/include/asm/cpufeatures.h instead (has an extra 's' - plural).
Those patches basically had to be manually done

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

Title:
  Xenial update to 4.4.110 stable release

Status in linux package in Ubuntu:
  New

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the 4.4.110 stable release shall be applied:
  * x86/boot: Add early cmdline parsing for options with arguments
  * KAISER: Kernel Address Isolation
  * kaiser: merged update
  * kaiser: do not set _PAGE_NX on pgd_none
  * kaiser: stack map PAGE_SIZE at THREAD_SIZE-PAGE_SIZE
  * kaiser: fix build and FIXME in alloc_ldt_struct()
  * kaiser: KAISER depends on SMP
  * kaiser: fix regs to do_nmi() ifndef CONFIG_KAISER
  * kaiser: fix perf crashes
  * kaiser: ENOMEM if kaiser_pagetable_walk() NULL
  * kaiser: tidied up asm/kaiser.h somewhat
  * kaiser: tidied up kaiser_add/remove_mapping slightly
  * kaiser: kaiser_remove_mapping() move along the pgd
  * kaiser: cleanups while trying for gold link
  * kaiser: name that 0x1000 KAISER_SHADOW_PGD_OFFSET
  * kaiser: delete KAISER_REAL_SWITCH option
  * kaiser: vmstat show NR_KAISERTABLE as nr_overhead
  * kaiser: enhanced by kernel and user PCIDs
  * kaiser: load_new_mm_cr3() let SWITCH_USER_CR3 flush user
  * kaiser: PCID 0 for kernel and 128 for user
  * kaiser: x86_cr3_pcid_noflush and x86_cr3_pcid_user
  * kaiser: paranoid_entry pass cr3 need to paranoid_exit
  * kaiser: _pgd_alloc() without __GFP_REPEAT to avoid stalls
  * kaiser: fix unlikely error in alloc_ldt_struct()
  * kaiser: add "nokaiser" boot option, using ALTERNATIVE
  * x86/kaiser: Rename and simplify X86_FEATURE_KAISER handling
  * x86/kaiser: Check boottime cmdline params
  * kaiser: use ALTERNATIVE instead of x86_cr3_pcid_noflush
  * kaiser: drop is_atomic arg to kaiser_pagetable_walk()
  * kaiser: asm/tlbflush.h handle noPGE at lower level
  * kaiser: kaiser_flush_tlb_on_return_to_user() check PCID
  * x86/paravirt: Dont patch flush_tlb_single
  * x86/kaiser: Reenable PARAVIRT
  * kaiser: disabled on Xen PV
  * x86/kaiser: Move feature detection up
  * KPTI: Rename to PAGE_TABLE_ISOLATION
  * KPTI: Report when enabled
  * x86, vdso, pvclock: Simplify and speed up the vdso pvclock reader
  * x86/vdso: Get pvclock data from the vvar VMA instead of the fixmap
  * x86/kasan: Clear kasan_zero_page after TLB flush
  * kaiser: Set _PAGE_NX only if supported
  * Linux 4.4.110

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

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

[Kernel-packages] [Bug 1745071] Re: Xenial update to 4.4.110 stable release

Note also that the applied patch ("KPTI: Rename to ..") affects the file
"arch/x86/kernel/cpu/perf_event_intel_ds.c" which has been renamed in
our tree to "arch/x86/events/intel/ds.c". Therefore the patch had to be
modified slightly to change arch/x86/events/intel/ds.c instead of the
originally-intended file.

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

Title:
  Xenial update to 4.4.110 stable release

Status in linux package in Ubuntu:
  New

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the 4.4.110 stable release shall be applied:
  * x86/boot: Add early cmdline parsing for options with arguments
  * KAISER: Kernel Address Isolation
  * kaiser: merged update
  * kaiser: do not set _PAGE_NX on pgd_none
  * kaiser: stack map PAGE_SIZE at THREAD_SIZE-PAGE_SIZE
  * kaiser: fix build and FIXME in alloc_ldt_struct()
  * kaiser: KAISER depends on SMP
  * kaiser: fix regs to do_nmi() ifndef CONFIG_KAISER
  * kaiser: fix perf crashes
  * kaiser: ENOMEM if kaiser_pagetable_walk() NULL
  * kaiser: tidied up asm/kaiser.h somewhat
  * kaiser: tidied up kaiser_add/remove_mapping slightly
  * kaiser: kaiser_remove_mapping() move along the pgd
  * kaiser: cleanups while trying for gold link
  * kaiser: name that 0x1000 KAISER_SHADOW_PGD_OFFSET
  * kaiser: delete KAISER_REAL_SWITCH option
  * kaiser: vmstat show NR_KAISERTABLE as nr_overhead
  * kaiser: enhanced by kernel and user PCIDs
  * kaiser: load_new_mm_cr3() let SWITCH_USER_CR3 flush user
  * kaiser: PCID 0 for kernel and 128 for user
  * kaiser: x86_cr3_pcid_noflush and x86_cr3_pcid_user
  * kaiser: paranoid_entry pass cr3 need to paranoid_exit
  * kaiser: _pgd_alloc() without __GFP_REPEAT to avoid stalls
  * kaiser: fix unlikely error in alloc_ldt_struct()
  * kaiser: add "nokaiser" boot option, using ALTERNATIVE
  * x86/kaiser: Rename and simplify X86_FEATURE_KAISER handling
  * x86/kaiser: Check boottime cmdline params
  * kaiser: use ALTERNATIVE instead of x86_cr3_pcid_noflush
  * kaiser: drop is_atomic arg to kaiser_pagetable_walk()
  * kaiser: asm/tlbflush.h handle noPGE at lower level
  * kaiser: kaiser_flush_tlb_on_return_to_user() check PCID
  * x86/paravirt: Dont patch flush_tlb_single
  * x86/kaiser: Reenable PARAVIRT
  * kaiser: disabled on Xen PV
  * x86/kaiser: Move feature detection up
  * KPTI: Rename to PAGE_TABLE_ISOLATION
  * KPTI: Report when enabled
  * x86, vdso, pvclock: Simplify and speed up the vdso pvclock reader
  * x86/vdso: Get pvclock data from the vvar VMA instead of the fixmap
  * x86/kasan: Clear kasan_zero_page after TLB flush
  * kaiser: Set _PAGE_NX only if supported
  * Linux 4.4.110

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

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

[Kernel-packages] [Bug 1527727] Re: grub-probe for zfs assumes all devices prefix with /dev, ignoring /dev/disk/...

2018-01-24 Thread Scott Moser

I've marked this 'Fix Released' in xenial as Ubuntu's package in xenial
at 0.6.5.6-0ubuntu3 which has the fix at [1] as mentioned in comment 29.
Further, my experience with our zfs work in curtin indicates that it is
fixed.

--
https://github.com/zfsonlinux/zfs/commit/d2f3e292dccab23e47ade3c67677a10f353b9e85

** Changed in: zfs-linux (Ubuntu Xenial)
   Status: Confirmed => Fix Released

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

Title:
  grub-probe for zfs assumes all devices prefix with /dev, ignoring
  /dev/disk/...

Status in grub:
  Unknown
Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  In Progress
Status in grub2-signed source package in Xenial:
  In Progress
Status in zfs-linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Installs over ZFS where a ZFS disk is expected to be used as a root device.

  [Test case]
  - Run update-grub on a system with a ZFS root filesystem.

  [Regression Potential]
  Installs relying on the current broken behavior to avoid listing other 
operating systems in grub menu may find that new entries are added.

  ---

  update-grub runs /usr/sbin/grub-probe

  Without libzfslinux support compiled in, /usr/sbin/grub-probe runs
  ["zpool", "status", poolname] to find out ZFS info.

  zpool responds with device names as used at (I think!) pool creation
  time. Often, this is /dev/disk/by-id/... names, without the path.

  grub-probe then parses the output, and takes the names of devices, and
  if they do not start with a "/", it prepends "/dev/".

  It then tests the existence of the path name of the device. it fails.

  grub-probe then returns  something like

  /usr/sbin/grub-probe: error: failed to get canonical path of `/dev
  /ata-ST31000333AS_-part1'.

  The actual path is of course /dev/disk/by-
  id/ST31000333AS_-part1

  It can prepend smarter than "/dev" or it can understand ZFS natively,
  to fix the problem.

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

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

[Kernel-packages] [Bug 1745268] [NEW] Xenial update to 4.4.113 stable release

Public bug reported:

SRU Justification

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

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the 4.4.113 stable release shall be applied:
* gcov: disable for COMPILE_TEST
* x86/cpu/AMD: Make LFENCE a serializing instruction
* x86/cpu/AMD: Use LFENCE_RDTSC in preference to MFENCE_RDTSC
* x86/mm/32: Move setup_clear_cpu_cap(X86_FEATURE_PCID) earlier
* x86/asm: Use register variable to get stack pointer value
* x86/kbuild: enable modversions for symbols exported from asm
* x86/asm: Make asm/alternative.h safe from assembly
* EXPORT_SYMBOL() for asm
* kconfig.h: use __is_defined() to check if MODULE is defined
* x86/retpoline: Add initial retpoline support
* x86/spectre: Add boot time option to select Spectre v2 mitigation
* x86/retpoline/crypto: Convert crypto assembler indirect jumps
* x86/retpoline/entry: Convert entry assembler indirect jumps
* x86/retpoline/ftrace: Convert ftrace assembler indirect jumps
* x86/retpoline/hyperv: Convert assembler indirect jumps
* x86/retpoline/xen: Convert Xen hypercall indirect jumps
* x86/retpoline/checksum32: Convert assembler indirect jumps
* x86/retpoline/irq32: Convert assembler indirect jumps
* x86/retpoline: Fill return stack buffer on vmexit
* x86/retpoline: Remove compile time warning
* scsi: sg: disable SET_FORCE_LOW_DMA
* futex: Prevent overflow by strengthen input validation
* ALSA: pcm: Remove yet superfluous WARN_ON()
* ALSA: hda - Apply headphone noise quirk for another Dell XPS 13 variant
* ALSA: hda - Apply the existing quirk to iMac 14,1
* af_key: fix buffer overread in verify_address_len()
* af_key: fix buffer overread in parse_exthdrs()
* scsi: hpsa: fix volume offline state
* sched/deadline: Zero out positive runtime after throttling constrained tasks
* x86/retpoline: Add LFENCE to the retpoline/RSB filling RSB macros
* module: Add retpoline tag to VERMAGIC
* pipe: avoid round_pipe_size() nr_pages overflow on 32-bit
* x86/apic/vector: Fix off by one in error path
* Input: 88pm860x-ts - fix child-node lookup
* Input: twl6040-vibra - fix DT node memory management
* Input: twl6040-vibra - fix child-node lookup
* Input: twl4030-vibra - fix sibling-node lookup
* tracing: Fix converting enum's from the map in trace_event_eval_update()
* phy: work around 'phys' references to usb-nop-xceiv devices
* ARM: dts: kirkwood: fix pin-muxing of MPP7 on OpenBlocks A7
* can: peak: fix potential bug in packet fragmentation
* libata: apply MAX_SEC_1024 to all LITEON EP1 series devices
* dm btree: fix serious bug in btree_split_beneath()
* dm thin metadata: THIN_MAX_CONCURRENT_LOCKS should be 6
* arm64: KVM: Fix SMCCC handling of unimplemented SMC/HVC calls
* x86/cpu, x86/pti: Do not enable PTI on AMD processors
* kbuild: modversions for EXPORT_SYMBOL() for asm
* x86/mce: Make machine check speculation protected
* retpoline: Introduce start/end markers of indirect thunk
* kprobes/x86: Blacklist indirect thunk functions for kprobes
* kprobes/x86: Disable optimizing on the function jumps to indirect thunk
* x86/pti: Document fix wrong index
* x86/retpoline: Optimize inline assembler for vmexit_fill_RSB
* MIPS: AR7: ensure the port type's FCR value is used
* Linux 4.4.113

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


** Tags: kernel-stable-tracking-bug

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

** Description changed:

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

[Kernel-packages] [Bug 1745266] Re: Xenial update to 4.4.112 stable release

Note that a few patches were referring to
arch/x86/include/asm/cpufeature.h , however, looking at the code it
appears the patches really should be applied to
arch/x86/include/asm/cpufeatures.h instead (has an extra 's' - plural).
Those patches basically had to be manually done.

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

Title:
  Xenial update to 4.4.112 stable release

Status in linux package in Ubuntu:
  New

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the 4.4.112 stable release shall be applied:
  * dm bufio: fix shrinker scans when (nr_to_scan < retain_target)
  * KVM: Fix stack-out-of-bounds read in write_mmio
  * can: gs_usb: fix return value of the "set_bittiming" callback
  * IB/srpt: Disable RDMA access by the initiator
  * MIPS: Validate PR_SET_FP_MODE prctl(2) requests against the ABI of the task
  * MIPS: Factor out NT_PRFPREG regset access helpers
  * MIPS: Guard against any partial write attempt with PTRACE_SETREGSET
  * MIPS: Consistently handle buffer counter with PTRACE_SETREGSET
  * MIPS: Fix an FCSR access API regression with NT_PRFPREG and MSA
  * MIPS: Also verify sizeof `elf_fpreg_t' with PTRACE_SETREGSET
  * MIPS: Disallow outsized PTRACE_SETREGSET NT_PRFPREG regset accesses
  * net/mac80211/debugfs.c: prevent build failure with CONFIG_UBSAN=y
  * kvm: vmx: Scrub hardware GPRs at VM-exit
  * x86/vsdo: Fix build on PARAVIRT_CLOCK=y, KVM_GUEST=n
  * x86/acpi: Handle SCI interrupts above legacy space gracefully
  * iommu/arm-smmu-v3: Don't free page table ops twice
  * ALSA: pcm: Remove incorrect snd_BUG_ON() usages
  * ALSA: pcm: Add missing error checks in OSS emulation plugin builder
  * ALSA: pcm: Abort properly at pending signal in OSS read/write loops
  * ALSA: pcm: Allow aborting mutex lock at OSS read/write loops
  * ALSA: aloop: Release cable upon open error path
  * ALSA: aloop: Fix inconsistent format due to incomplete rule
  * ALSA: aloop: Fix racy hw constraints adjustment
  * x86/acpi: Reduce code duplication in mp_override_legacy_irq()
  * mm/compaction: fix invalid free_pfn and compact_cached_free_pfn
  * mm/compaction: pass only pageblock aligned range to pageblock_pfn_to_page
  * mm/page-writeback: fix dirty_ratelimit calculation
  * mm/zswap: use workqueue to destroy pool
  * zswap: don't param_set_charp while holding spinlock
  * locks: don't check for race with close when setting OFD lock
  * futex: Replace barrier() in unqueue_me() with READ_ONCE()
  * locking/mutex: Allow next waiter lockless wakeup
  * usbvision fix overflow of interfaces array
  * usb: musb: ux500: Fix NULL pointer dereference at system PM
  * r8152: fix the wake event
  * r8152: use test_and_clear_bit
  * r8152: adjust ALDPS function
  * lan78xx: use skb_cow_head() to deal with cloned skbs
  * sr9700: use skb_cow_head() to deal with cloned skbs
  * smsc75xx: use skb_cow_head() to deal with cloned skbs
  * cx82310_eth: use skb_cow_head() to deal with cloned skbs
  * x86/mm/pat, /dev/mem: Remove superfluous error message
  * hwrng: core - sleep interruptible in read
  * sysrq: Fix warning in sysrq generated crash.
  * xhci: Fix ring leak in failure path of xhci_alloc_virt_device()
  * Revert "userfaultfd: selftest: vm: allow to build in vm/ directory"
  * x86/pti/efi: broken conversion from efi to kernel page table
  * 8021q: fix a memory leak for VLAN 0 device
  * ip6_tunnel: disable dst caching if tunnel is dual-stack
  * net: core: fix module type in sock_diag_bind
  * RDS: Heap OOB write in rds_message_alloc_sgs()
  * RDS: null pointer dereference in rds_atomic_free_op
  * sh_eth: fix TSU resource handling
  * sh_eth: fix SH7757 GEther initialization
  * net: stmmac: enable EEE in MII, GMII or RGMII only
  * ipv6: fix possible mem leaks in ipv6_make_skb()
  * crypto: algapi - fix NULL dereference in crypto_remove_spawns()
  * rbd: set max_segments to USHRT_MAX
  * x86/microcode/intel: Extend BDW late-loading with a revision check
  * KVM: x86: Add memory barrier on vmcs field lookup
  * drm/vmwgfx: Potential off by one in vmw_view_add()
  * kaiser: Set _PAGE_NX only if supported
  * bpf: add bpf_patch_insn_single helper
  * bpf: don't (ab)use instructions to store state
  * bpf: move fixup_bpf_calls() function
  * bpf: refactor fixup_bpf_calls()
  * bpf: adjust insn_aux_data when patching insns
  * bpf: prevent

[Kernel-packages] [Bug 1745266] Re: Xenial update to 4.4.112 stable release

The following patches were NOT applied as they had been applied
previously:

 * kvm: vmx: Scrub hardware GPRs at VM-exit
 * bpf: add bpf_patch_insn_single helper

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The 4.4.112 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The 4.4.112 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
- 
-The following patches from the 4.4.112 stable release shall be
- applied:
+    The following patches from the 4.4.112 stable release shall be applied:
+ * dm bufio: fix shrinker scans when (nr_to_scan < retain_target)
+ * KVM: Fix stack-out-of-bounds read in write_mmio
+ * can: gs_usb: fix return value of the "set_bittiming" callback
+ * IB/srpt: Disable RDMA access by the initiator
+ * MIPS: Validate PR_SET_FP_MODE prctl(2) requests against the ABI of the task
+ * MIPS: Factor out NT_PRFPREG regset access helpers
+ * MIPS: Guard against any partial write attempt with PTRACE_SETREGSET
+ * MIPS: Consistently handle buffer counter with PTRACE_SETREGSET
+ * MIPS: Fix an FCSR access API regression with NT_PRFPREG and MSA
+ * MIPS: Also verify sizeof `elf_fpreg_t' with PTRACE_SETREGSET
+ * MIPS: Disallow outsized PTRACE_SETREGSET NT_PRFPREG regset accesses
+ * net/mac80211/debugfs.c: prevent build failure with CONFIG_UBSAN=y
+ * kvm: vmx: Scrub hardware GPRs at VM-exit
+ * x86/vsdo: Fix build on PARAVIRT_CLOCK=y, KVM_GUEST=n
+ * x86/acpi: Handle SCI interrupts above legacy space gracefully
+ * iommu/arm-smmu-v3: Don't free page table ops twice
+ * ALSA: pcm: Remove incorrect snd_BUG_ON() usages
+ * ALSA: pcm: Add missing error checks in OSS emulation plugin builder
+ * ALSA: pcm: Abort properly at pending signal in OSS read/write loops
+ * ALSA: pcm: Allow aborting mutex lock at OSS read/write loops
+ * ALSA: aloop: Release cable upon open error path
+ * ALSA: aloop: Fix inconsistent format due to incomplete rule
+ * ALSA: aloop: Fix racy hw constraints adjustment
+ * x86/acpi: Reduce code duplication in mp_override_legacy_irq()
+ * mm/compaction: fix invalid free_pfn and compact_cached_free_pfn
+ * mm/compaction: pass only pageblock aligned range to pageblock_pfn_to_page
+ * mm/page-writeback: fix dirty_ratelimit calculation
+ * mm/zswap: use workqueue to destroy pool
+ * zswap: don't param_set_charp while holding spinlock
+ * locks: don't check for race with close when setting OFD lock
+ * futex: Replace barrier() in unqueue_me() with READ_ONCE()
+ * locking/mutex: Allow next waiter lockless wakeup
+ * usbvision fix overflow of interfaces array
+ * usb: musb: ux500: Fix NULL pointer dereference at system PM
+ * r8152: fix the wake event
+ * r8152: use test_and_clear_bit
+ * r8152: adjust ALDPS function
+ * lan78xx: use skb_cow_head() to deal with cloned skbs
+ * sr9700: use skb_cow_head() to deal with cloned skbs
+ * smsc75xx: use skb_cow_head() to deal with cloned skbs
+ * cx82310_eth: use skb_cow_head() to deal with cloned skbs
+ * x86/mm/pat, /dev/mem: Remove superfluous error message
+ * hwrng: core - sleep interruptible in read
+ * sysrq: Fix warning in sysrq generated crash.
+ * xhci: Fix ring leak in failure path of xhci_alloc_virt_device()
+ * Revert "userfaultfd: selftest: vm: allow to build in vm/ directory"
+ * x86/pti/efi: broken conversion from efi to kernel page table
+ * 8021q: fix a memory leak for VLAN 0 device
+ * ip6_tunnel: disable dst caching if tunnel is dual-stack
+ * net: core: fix module type in sock_diag_bind
+ * RDS: Heap OOB write in rds_message_alloc_sgs()
+ * RDS: null pointer dereference in rds_atomic_free_op
+ * sh_eth: fix TSU resource handling
+ * sh_eth: fix SH7757 GEther initialization
+ * net: stmmac: enable EEE in MII, GMII or RGMII only
+ * ipv6: fix possible mem leaks in ipv6_make_skb()
+ * crypto: algapi - fix NULL dereference in crypto_remove_spawns()
+ * rbd: set max_segments to USHRT_MAX
+ * x86/microcode/intel: Extend BDW late-loading with a revision check
+ * KVM: x86: Add memory barrier on vmcs field lookup
+ * drm/vmwgfx: Potential off by one in vmw_view_add()
+ *

[Kernel-packages] [Bug 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)

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

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

Title:
  Logitech G930 drops connection and reconnects in 17.10 (But not in
  17.04)

Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Every so many seconds / minutes the Wireless headset Logitech G930
  simply drops connection. It always reconnects but when doing a
  recording, a meeting, listening to music or a movie it simply drops
  the connection for 1 to 3 second. This happens several times an hour.
  If it helps, it was not happening in 17.04 (Never happened in more
  than 200+ hours of using the headset).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cyrex  1288 F pulseaudio
   /dev/snd/controlC2:  cyrex  1288 F pulseaudio
   /dev/snd/controlC0:  cyrex  1288 F pulseaudio
  Date: Sat Oct 21 17:55:42 2017
  InstallationDate: Installed on 2017-10-19 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  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.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3504
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  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/1725863/+subscriptions

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

[Kernel-packages] [Bug 1426228] Re: package bluez 4.101-0ubuntu13.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 [reload: Unknown instance: inv

See also: bug 1682731

** Summary changed:

- package bluez 4.101-0ubuntu13.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
+ package bluez 4.101-0ubuntu13.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1 [reload: 
Unknown instance: invoke-rc.d: initscript dbus, action "force-reload" failed.]

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

Title:
  package bluez 4.101-0ubuntu13.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1
  [reload: Unknown instance: invoke-rc.d: initscript dbus, action
  "force-reload" failed.]

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Balnk screen on start up, so I went to the fails safe boot followed by
  fixing broken packages option, and this is the message resulting.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: bluez 4.101-0ubuntu13.1
  ProcVersionSignature: Ubuntu 3.13.0-46.75-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  Date: Fri Feb 27 18:09:53 2015
  DuplicateSignature: package:bluez:4.101-0ubuntu13.1:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2012-05-05 (1028 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: TOSHIBA Satellite PRO C660
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic 
root=UUID=70e0e896-ab94-42e6-83d0-ff70ceeba57c ro recovery nomodeset
  SourcePackage: bluez
  Title: package bluez 4.101-0ubuntu13.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to trusty on 2014-09-06 (173 days ago)
  dmi.bios.date: 03/18/2011
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.00
  dmi.board.asset.tag: NULL
  dmi.board.name: PWWHA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.00:bd03/18/2011:svnTOSHIBA:pnSatellitePROC660:pvrPSC1RA-003001:rvnTOSHIBA:rnPWWHA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: Satellite PRO C660
  dmi.product.version: PSC1RA-003001
  dmi.sys.vendor: TOSHIBA
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 68:A3:C4:88:85:33  ACL MTU: 1022:8  SCO MTU: 121:3
UP RUNNING PSCAN 
RX bytes:1064 acl:0 sco:0 events:55 errors:0
TX bytes:1427 acl:0 sco:0 commands:53 errors:0

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

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

[Kernel-packages] [Bug 1729389] Re: [Intel 8260/8265] Bluetooth peripherals work for a few seconds, then don't react

2018-01-24 Thread Drew Rosoff

I had previously worked around this problem using the solution in
comment #17.  Now I just upgraded to linux-firmware 1.157.15, as I saw
it in my Ubuntu Xenial updates and it referenced fixing this bug.  I
therefore removed the workaround in comment #17 and rebooted.  The
problem returned immediately (I tried multiple reboots and reconnects).
Bluetooth still disconnects after a period of time if wifi is also
connected.  I had to reinstate the workaround in comment #17 again to
have a working mouse, even with the new linux-firmware update.  I am
using Ubuntu 16.04 kernel 4.13.0-31.

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

Title:
  [Intel 8260/8265] Bluetooth peripherals work for a few seconds, then
  don't react

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Confirmed
Status in linux-firmware source package in Artful:
  Fix Released

Bug description:
  SRU Justification

  Impact: Bluetooth peripherals work initially but stop working shortly
  with Linux 4.13.

  Fix: Updated firmware from Intel containing a fix for the issue.

  Regression Potential: Any firmware updates may bring regressions,
  however this is a bug fix update and therefore regression potential is
  expected to be minimal.

  ---

  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  ---
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp.
   Bus 001 Device 005: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 13d3:5664 IMC Networks
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
    UP RUNNING PSCAN ISCAN INQUIRY
    RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
    TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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

[Kernel-packages] [Bug 1682731] Re: package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 [invoke-rc.d: initscript bluetooth

See also: bug 1426228

** Summary changed:

- package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
+ package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1 [invoke-rc.d: initscript 
bluetooth, action "restart" failed.]

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

Title:
  package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1
  [invoke-rc.d: initscript bluetooth, action "restart" failed.]

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  passwd root

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bluez 5.43-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Apr 14 10:38:35 2017
  DpkgHistoryLog: Start-Date: 2017-04-14  10:35:52
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-04-02 (12 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Micro-Star International Co., Ltd. CR61 2M/CX61 2OC/CX61 2OD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=f5a8ba7b-5759-4d4c-99a4-6cad4db08728 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: bluez
  Title: package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16GDIMS.20G
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16GD
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: CR61 2M/CX61 2OC/CX61 2OD
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16GDIMS.20G:bd01/18/2014:svnMicro-StarInternationalCo.,Ltd.:pnCR612M/CX612OC/CX612OD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GD:rvrREV1.0:cvnCR612M/CX612OC/CX612OD:ct10:cvrN/A:
  dmi.product.name: CR61 2M/CX61 2OC/CX61 2OD
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 54:27:1E:9E:18:49  ACL MTU: 820:8  SCO MTU: 255:16
DOWN 
RX bytes:1274 acl:0 sco:0 events:129 errors:0
TX bytes:25311 acl:0 sco:0 commands:129 errors:0

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

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

[Kernel-packages] [Bug 1682751] Re: package bluez 5.37-0ubuntu5 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

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

** This bug has been marked a duplicate of bug 1682731
   package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1 [invoke-rc.d: initscript 
bluetooth, action "restart" failed.]

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

Title:
  package bluez 5.37-0ubuntu5 failed to install/upgrade: le sous-
  processus script post-installation installé a retourné une erreur de
  sortie d'état 1

Status in bluez package in Ubuntu:
  New

Bug description:
  Here is the terminal display for sudo apt install bluez:

  Lecture des listes de paquets... Fait
  Construction de l'arbre des dépendances   
  Lecture des informations d'état... Fait
  Les NOUVEAUX paquets suivants seront installés :
bluez
  0 mis à jour, 1 nouvellement installés, 0 à enlever et 0 non mis à jour.
  Il est nécessaire de prendre 0 o/899 ko dans les archives.
  Après cette opération, 4 218 ko d'espace disque supplémentaires seront 
utilisés.
  Sélection du paquet bluez précédemment désélectionné.
  (Lecture de la base de données... 205650 fichiers et répertoires déjà 
installés.)
  Préparation du dépaquetage de .../bluez_5.37-0ubuntu5_amd64.deb ...
  Dépaquetage de bluez (5.37-0ubuntu5) ...
  Traitement des actions différées (« triggers ») pour systemd (229-4ubuntu16) 
...
  Traitement des actions différées (« triggers ») pour ureadahead (0.100.0-19) 
...
  ureadahead will be reprofiled on next reboot
  Traitement des actions différées (« triggers ») pour dbus (1.10.6-1ubuntu3.3) 
...
  Traitement des actions différées (« triggers ») pour man-db (2.7.5-1) ...
  Paramétrage de bluez (5.37-0ubuntu5) ...
  Job for bluetooth.service failed because the control process exited with 
error code. See "systemctl status bluetooth.service" and "journalctl -xe" for 
details.
  invoke-rc.d: initscript bluetooth, action "restart" failed.
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since ven. 2017-04-14 09:59:14 CEST; 
6ms ago
   Docs: man:bluetoothd(8)
Process: 10540 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited, 
status=1/FAILURE)
   Main PID: 10540 (code=exited, status=1/FAILURE)
 Status: "Starting up"

  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: Starting 
Blueto...
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC bluetoothd[10540]: 
Bluetoot...
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC bluetoothd[10540]: D-Bus 
se...
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: 
bluetooth.servi...
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: Failed to 
start...
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: 
bluetooth.servi...
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: 
bluetooth.servi...
  Hint: Some lines were ellipsized, use -l to show in full.
  dpkg: erreur de traitement du paquet bluez (--configure) :
   le sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
-

  Here the terminal display for systemctl status bluetooth.service:

  bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: failed (Result: exit-code) since ven. 2017-04-14 09:59:14 CEST; 
5min 
   Docs: man:bluetoothd(8)
Process: 10540 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited, 
status=1/
   Main PID: 10540 (code=exited, status=1/FAILURE)
 Status: "Starting up"

  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: Starting 
Bluetooth service...
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC bluetoothd[10540]: 
Bluetooth daemon 5.37
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC bluetoothd[10540]: D-Bus 
setup failed: Connection ":1.112" is not allowed to own the service "org.bluez" 
due to own the service "org.bluez" due to security policies in the 
configuration file
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: 
bluetooth.service: Main process exited, code=exited, status=1/FAILURE
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: Failed to start 
Bluetooth service.
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: 
bluetooth.service: Unit entered failed state.
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: 
bluetooth.service: Failed with result 'exit-code'.

  
-

  Here details from

[Kernel-packages] [Bug 1717588] Re: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

** This bug is no longer a duplicate of bug 1717589
   package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
** This bug has been marked a duplicate of bug 1682731
   package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1 [invoke-rc.d: initscript 
bluetooth, action "restart" failed.]

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

Title:
  package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in bluez package in Ubuntu:
  New

Bug description:
  I was trying to perform the update on linux 16.04 LTE of my QNAP TS-
  253A NAS server when the error occurred.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.1
  Uname: Linux 4.2.8 x86_64
  NonfreeKernelModules: vfio_pci vfio_virqfd vfio_iommu_type1 vfio vhost_scsi 
target_core_mod vhost_net vhost macvtap macvlan tun vringh virtio_scsi 
virtio_pci virtio_net virtio_mmio virtio_console virtio_blk virtio_balloon 
virtio_rng virtio_ring virtio kvm_intel kvm xt_nat rfcomm iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi fbdisk cdc_ether ipt_MASQUERADE 
iptable_nat nf_nat_masquerade_ipv4 nf_nat_ipv4 nf_nat xt_policy xt_mark bonding 
br_netfilter bridge stp 8021q ipv6 uvcvideo videobuf2_vmalloc videobuf2_memops 
videobuf2_core snd_usb_caiaq snd_usb_audio snd_usbmidi_lib snd_seq_midi 
snd_rawmidi fnotify udf isofs sp5100_tco iTCO_wdt tbs_keys ufsd jnl pl2303 
usbserial qm2_i2c intel_ips drbd flashcache dm_tier_btier_algo dm_thin_pool 
dm_bio_prison dm_persistent_data hal_netlink k10temp coretemp r8152 usbnet mii 
igb e1000e mpt3sas mpt2sas scsi_transport_sas raid_class usb_storage xhci_pci 
xhci_hcd usblp uhci_hcd ehci_pci ehci_hcd
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Sep 15 21:39:42 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InterestingModules: rfcomm
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1005:b155 Apacer Technology, Inc. 
   Bus 001 Device 002: ID 045e:0800 Microsoft Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: consoleblank=0 console=ttyS0,115200n8 
video=HDMI-A-1:800x600@60 video=HDMI-A-2:800x600@60 i915.disable_dp_dual_mode=1 
i915.disable_power_well=0 memmap=2M$0x800 ramoops.mem_address=0x800 
ramoops.mem_size=0x20 ramoops.console_size=0x10 
BOOT_IMAGE=/boot/bzImage root=/dev/ram0 rw
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: bluez
  Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  getfacl: Error: command ['getfacl', '/dev/rfkill'] failed with exit code 1: 
getfacl: /dev/rfkill: No such file or directory
  hciconfig: Error: command hciconfig failed with exit code 1: Can't open HCI 
socket.: Address family not supported by protocol
  rfkill: Can't open RFKILL control device: No such file or directory
  upstart.bluetooth.override: manual

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

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

[Kernel-packages] [Bug 1717589] Re: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

** This bug has been marked a duplicate of bug 1682731
   package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1 [invoke-rc.d: initscript 
bluetooth, action "restart" failed.]

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

Title:
  package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I was trying to perform the update on linux 16.04 LTE of my QNAP TS-
  253A NAS server when the error occurred.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.1
  Uname: Linux 4.2.8 x86_64
  NonfreeKernelModules: vfio_pci vfio_virqfd vfio_iommu_type1 vfio vhost_scsi 
target_core_mod vhost_net vhost macvtap macvlan tun vringh virtio_scsi 
virtio_pci virtio_net virtio_mmio virtio_console virtio_blk virtio_balloon 
virtio_rng virtio_ring virtio kvm_intel kvm xt_nat rfcomm iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi fbdisk cdc_ether ipt_MASQUERADE 
iptable_nat nf_nat_masquerade_ipv4 nf_nat_ipv4 nf_nat xt_policy xt_mark bonding 
br_netfilter bridge stp 8021q ipv6 uvcvideo videobuf2_vmalloc videobuf2_memops 
videobuf2_core snd_usb_caiaq snd_usb_audio snd_usbmidi_lib snd_seq_midi 
snd_rawmidi fnotify udf isofs sp5100_tco iTCO_wdt tbs_keys ufsd jnl pl2303 
usbserial qm2_i2c intel_ips drbd flashcache dm_tier_btier_algo dm_thin_pool 
dm_bio_prison dm_persistent_data hal_netlink k10temp coretemp r8152 usbnet mii 
igb e1000e mpt3sas mpt2sas scsi_transport_sas raid_class usb_storage xhci_pci 
xhci_hcd usblp uhci_hcd ehci_pci ehci_hcd
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Sep 15 21:39:42 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InterestingModules: rfcomm
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1005:b155 Apacer Technology, Inc. 
   Bus 001 Device 002: ID 045e:0800 Microsoft Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: consoleblank=0 console=ttyS0,115200n8 
video=HDMI-A-1:800x600@60 video=HDMI-A-2:800x600@60 i915.disable_dp_dual_mode=1 
i915.disable_power_well=0 memmap=2M$0x800 ramoops.mem_address=0x800 
ramoops.mem_size=0x20 ramoops.console_size=0x10 
BOOT_IMAGE=/boot/bzImage root=/dev/ram0 rw
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: bluez
  Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  getfacl: Error: command ['getfacl', '/dev/rfkill'] failed with exit code 1: 
getfacl: /dev/rfkill: No such file or directory
  hciconfig: Error: command hciconfig failed with exit code 1: Can't open HCI 
socket.: Address family not supported by protocol
  rfkill: Can't open RFKILL control device: No such file or directory
  upstart.bluetooth.override: manual

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

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

[Kernel-packages] [Bug 1745239] Re: package bluez 5.37-0ubuntu5.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1682731, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1682731
   package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1 [invoke-rc.d: initscript 
bluetooth, action "restart" failed.]

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

Title:
  package bluez 5.37-0ubuntu5.2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in bluez package in Ubuntu:
  New

Bug description:
  bug

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.2
  ProcVersionSignature: Ubuntu 4.4.0-111.134-generic 4.4.98
  Uname: Linux 4.4.0-111-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Wed Jan 24 09:22:04 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-01-16 (739 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: bnep btusb bluetooth
  MachineType: TOSHIBA SATELLITE C875-14H
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-111-generic 
root=UUID=1bb1ab31-fec5-4cde-ac3f-1eed4203d409 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: bluez
  Title: package bluez 5.37-0ubuntu5.2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/01/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.80
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PLCSF8
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.80:bd10/01/2013:svnTOSHIBA:pnSATELLITEC875-14H:pvrPSCBCE-02L002FR:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: SATELLITE C875-14H
  dmi.product.version: PSCBCE-02L002FR
  dmi.sys.vendor: TOSHIBA
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 24:FD:52:15:9B:97  ACL MTU: 820:8  SCO MTU: 255:16
UP RUNNING PSCAN 
RX bytes:2526 acl:0 sco:0 events:181 errors:0
TX bytes:26261 acl:0 sco:0 commands:181 errors:0

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

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

[Kernel-packages] [Bug 1454297] Re: package bluez 4.101-0ubuntu13.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

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

** This bug has been marked a duplicate of bug 1426228
   package bluez 4.101-0ubuntu13.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1

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

Title:
  package bluez 4.101-0ubuntu13.1 failed to install/upgrade: sub-
  processo script post-installation instalado retornou estado de saída
  de erro 1

Status in bluez package in Ubuntu:
  New

Bug description:
  Reinstalando o sistema.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: bluez 4.101-0ubuntu13.1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.10
  AptOrdering:
   bluez: Configure
   bluez-alsa: Configure
  Architecture: amd64
  Date: Tue May 12 09:01:24 2015
  DuplicateSignature: package:bluez:4.101-0ubuntu13.1:sub-processo script 
post-installation instalado retornou estado de saída de erro 1
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  InstallationDate: Installed on 2015-05-12 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  InterestingModules: bnep rfcomm bluetooth
  MachineType: PCDIGIT OEM
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=UUID=7aa02f80-5352-4f4a-8952-776e18cc919d ro recovery nomodeset
  SourcePackage: bluez
  Title: package bluez 4.101-0ubuntu13.1 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/03/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: G31MXP
  dmi.board.vendor: Foxconn
  dmi.board.version: FAB:1.1
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd11/03/2009:svnPCDIGIT:pnOEM:pvrOEM:rvnFoxconn:rnG31MXP:rvrFAB1.1:cvnOEM:ct3:cvrOEM:
  dmi.product.name: OEM
  dmi.product.version: OEM
  dmi.sys.vendor: PCDIGIT
  hciconfig:
   
  rfkill:

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

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

[Kernel-packages] [Bug 1565240] Re: package bluez 4.101-0ubuntu13.1 failed to install/upgrade: podproces nainštalovaný skript post-installation vrátil chybový kód 1

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

** This bug has been marked a duplicate of bug 1426228
   package bluez 4.101-0ubuntu13.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1

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

Title:
  package bluez 4.101-0ubuntu13.1 failed to install/upgrade: podproces
  nainštalovaný skript post-installation vrátil chybový kód 1

Status in bluez package in Ubuntu:
  New

Bug description:
  problem in install

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: bluez 4.101-0ubuntu13.1
  ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
  Uname: Linux 3.13.0-83-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  AptOrdering: bluez: Configure
  Architecture: i386
  Date: Sat Apr  2 12:41:40 2016
  DuplicateSignature: package:bluez:4.101-0ubuntu13.1:podproces nainštalovaný 
skript post-installation vrátil chybový kód 1
  ErrorMessage: podproces nainštalovaný skript post-installation vrátil chybový 
kód 1
  InstallationDate: Installed on 2016-04-02 (0 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  InterestingModules: bnep rfcomm bluetooth
  MachineType: ASUSTeK Computer Inc. F3JC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-83-generic 
root=UUID=9638eded-ec1d-4d33-9ff1-a1853d4405d9 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.5
   apt  1.0.1ubuntu2.11
  SourcePackage: bluez
  Title: package bluez 4.101-0ubuntu13.1 failed to install/upgrade: podproces 
nainštalovaný skript post-installation vrátil chybový kód 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: F3JC
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr307:bd06/11/2008:svnASUSTeKComputerInc.:pnF3JC:pvr1.0:rvnASUSTeKComputerInc.:rnF3JC:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
  dmi.product.name: F3JC
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  hciconfig:
   
  rfkill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes

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

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

[Kernel-packages] [Bug 1745266] [NEW] Xenial update to 4.4.112 stable release

Public bug reported:


SRU Justification

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

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the 4.4.112 stable release shall be
applied:

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


** Tags: kernel-stable-tracking-bug

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

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

Title:
  Xenial update to 4.4.112 stable release

Status in linux package in Ubuntu:
  New

Bug description:
  
  SRU Justification

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

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.4.112 stable release shall be
  applied:

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

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

[Kernel-packages] [Bug 1745263] Re: Xenial update to 4.4.111 stable release

The following patches were NOT applied as they were already applied
previously:

 * x86/microcode/AMD: Add support for fam17h microcode loading
 * x86/tlb: Drop the _GPL from the cpu_tlbstate export
 * module: keep percpu symbols in module's symtab
 * Map the vsyscall page with _PAGE_USER

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

Title:
  Xenial update to 4.4.111 stable release

Status in linux package in Ubuntu:
  New

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the 4.4.111 stable release shall be applied:
  * x86/kasan: Write protect kasan zero shadow
  * kernel/acct.c: fix the acct->needcheck check in check_free_space()
  * crypto: n2 - cure use after free
  * crypto: chacha20poly1305 - validate the digest size
  * crypto: pcrypt - fix freeing pcrypt instances
  * sunxi-rsb: Include OF based modalias in device uevent
  * fscache: Fix the default for fscache_maybe_release_page()
  * kernel: make groups_sort calling a responsibility group_info allocators
  * kernel/signal.c: protect the traced SIGNAL_UNKILLABLE tasks from SIGKILL
  * kernel/signal.c: protect the SIGNAL_UNKILLABLE tasks from 
!sig_kernel_only() signals
  * kernel/signal.c: remove the no longer needed SIGNAL_UNKILLABLE check in 
complete_signal()
  * ARC: uaccess: dont use "l" gcc inline asm constraint modifier
  * Input: elantech - add new icbody type 15
  * x86/microcode/AMD: Add support for fam17h microcode loading
  * parisc: Fix alignment of pa_tlb_lock in assembly on 32-bit SMP kernel
  * x86/tlb: Drop the _GPL from the cpu_tlbstate export
  * genksyms: Handle string literals with spaces in reference files
  * module: keep percpu symbols in module's symtab
  * module: Issue warnings when tainting kernel
  * proc: much faster /proc/vmstat
  * Map the vsyscall page with _PAGE_USER
  * Fix build error in vma.c
  * Linux 4.4.111

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

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

[Kernel-packages] [Bug 1745071] Re: Xenial update to 4.4.110 stable release

Only one of the patches for this release actually needed to be applied,
as the rest had already been applied previously for spectre/meltdown
(CVE-2017-5754) though not necessarily in the same order.

The only patch that actually needed to be applied is:

 * KPTI: Rename to PAGE_TABLE_ISOLATION


Further, one additional patch was required in 
debian.master/config/config.common.ubuntu to change the config name from 
CONFIG_KAISER to CONFIG_PAGE_TABLE_ISOLATION.

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The 4.4.110 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The 4.4.110 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
- 
-The following patches from the 4.4.110 stable release shall be
- applied:
+    The following patches from the 4.4.110 stable release shall be applied:
+ * x86/boot: Add early cmdline parsing for options with arguments
+ * KAISER: Kernel Address Isolation
+ * kaiser: merged update
+ * kaiser: do not set _PAGE_NX on pgd_none
+ * kaiser: stack map PAGE_SIZE at THREAD_SIZE-PAGE_SIZE
+ * kaiser: fix build and FIXME in alloc_ldt_struct()
+ * kaiser: KAISER depends on SMP
+ * kaiser: fix regs to do_nmi() ifndef CONFIG_KAISER
+ * kaiser: fix perf crashes
+ * kaiser: ENOMEM if kaiser_pagetable_walk() NULL
+ * kaiser: tidied up asm/kaiser.h somewhat
+ * kaiser: tidied up kaiser_add/remove_mapping slightly
+ * kaiser: kaiser_remove_mapping() move along the pgd
+ * kaiser: cleanups while trying for gold link
+ * kaiser: name that 0x1000 KAISER_SHADOW_PGD_OFFSET
+ * kaiser: delete KAISER_REAL_SWITCH option
+ * kaiser: vmstat show NR_KAISERTABLE as nr_overhead
+ * kaiser: enhanced by kernel and user PCIDs
+ * kaiser: load_new_mm_cr3() let SWITCH_USER_CR3 flush user
+ * kaiser: PCID 0 for kernel and 128 for user
+ * kaiser: x86_cr3_pcid_noflush and x86_cr3_pcid_user
+ * kaiser: paranoid_entry pass cr3 need to paranoid_exit
+ * kaiser: _pgd_alloc() without __GFP_REPEAT to avoid stalls
+ * kaiser: fix unlikely error in alloc_ldt_struct()
+ * kaiser: add "nokaiser" boot option, using ALTERNATIVE
+ * x86/kaiser: Rename and simplify X86_FEATURE_KAISER handling
+ * x86/kaiser: Check boottime cmdline params
+ * kaiser: use ALTERNATIVE instead of x86_cr3_pcid_noflush
+ * kaiser: drop is_atomic arg to kaiser_pagetable_walk()
+ * kaiser: asm/tlbflush.h handle noPGE at lower level
+ * kaiser: kaiser_flush_tlb_on_return_to_user() check PCID
+ * x86/paravirt: Dont patch flush_tlb_single
+ * x86/kaiser: Reenable PARAVIRT
+ * kaiser: disabled on Xen PV
+ * x86/kaiser: Move feature detection up
+ * KPTI: Rename to PAGE_TABLE_ISOLATION
+ * KPTI: Report when enabled
+ * x86, vdso, pvclock: Simplify and speed up the vdso pvclock reader
+ * x86/vdso: Get pvclock data from the vvar VMA instead of the fixmap
+ * x86/kasan: Clear kasan_zero_page after TLB flush
+ * kaiser: Set _PAGE_NX only if supported
+ * Linux 4.4.110

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5754

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

Title:
  Xenial update to 4.4.110 stable release

Status in linux package in Ubuntu:
  New

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the 4.4.110 stable release shall be applied:
  * x86/boot: Add early cmdline parsing for options with arguments
  * KAISER: Kernel Address Isolation
  * kaiser: merged update
  * kaiser: do not set _PAGE_NX on

[Kernel-packages] [Bug 1745263] [NEW] Xenial update to 4.4.111 stable release

Public bug reported:

SRU Justification

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

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the 4.4.111 stable release shall be applied:
* x86/kasan: Write protect kasan zero shadow
* kernel/acct.c: fix the acct->needcheck check in check_free_space()
* crypto: n2 - cure use after free
* crypto: chacha20poly1305 - validate the digest size
* crypto: pcrypt - fix freeing pcrypt instances
* sunxi-rsb: Include OF based modalias in device uevent
* fscache: Fix the default for fscache_maybe_release_page()
* kernel: make groups_sort calling a responsibility group_info allocators
* kernel/signal.c: protect the traced SIGNAL_UNKILLABLE tasks from SIGKILL
* kernel/signal.c: protect the SIGNAL_UNKILLABLE tasks from !sig_kernel_only() 
signals
* kernel/signal.c: remove the no longer needed SIGNAL_UNKILLABLE check in 
complete_signal()
* ARC: uaccess: dont use "l" gcc inline asm constraint modifier
* Input: elantech - add new icbody type 15
* x86/microcode/AMD: Add support for fam17h microcode loading
* parisc: Fix alignment of pa_tlb_lock in assembly on 32-bit SMP kernel
* x86/tlb: Drop the _GPL from the cpu_tlbstate export
* genksyms: Handle string literals with spaces in reference files
* module: keep percpu symbols in module's symtab
* module: Issue warnings when tainting kernel
* proc: much faster /proc/vmstat
* Map the vsyscall page with _PAGE_USER
* Fix build error in vma.c
* Linux 4.4.111

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


** Tags: kernel-stable-tracking-bug

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

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The 4.4.111 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The 4.4.111 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
- 
-The following patches from the 4.4.111 stable release shall be
- applied:
+    The following patches from the 4.4.111 stable release shall be applied:
+ * x86/kasan: Write protect kasan zero shadow
+ * kernel/acct.c: fix the acct->needcheck check in check_free_space()
+ * crypto: n2 - cure use after free
+ * crypto: chacha20poly1305 - validate the digest size
+ * crypto: pcrypt - fix freeing pcrypt instances
+ * sunxi-rsb: Include OF based modalias in device uevent
+ * fscache: Fix the default for fscache_maybe_release_page()
+ * kernel: make groups_sort calling a responsibility group_info allocators
+ * kernel/signal.c: protect the traced SIGNAL_UNKILLABLE tasks from SIGKILL
+ * kernel/signal.c: protect the SIGNAL_UNKILLABLE tasks from 
!sig_kernel_only() signals
+ * kernel/signal.c: remove the no longer needed SIGNAL_UNKILLABLE check in 
complete_signal()
+ * ARC: uaccess: dont use "l" gcc inline asm constraint modifier
+ * Input: elantech - add new icbody type 15
+ * x86/microcode/AMD: Add support for fam17h microcode loading
+ * parisc: Fix alignment of pa_tlb_lock in assembly on 32-bit SMP kernel
+ * x86/tlb: Drop the _GPL from the cpu_tlbstate export
+ * genksyms: Handle string literals with spaces in reference files
+ * module: keep percpu symbols in module's symtab
+ * module: Issue warnings when tainting kernel
+ * proc: much faster /proc/vmstat
+ * Map the vsyscall page with _PAGE_USER
+ * Fix build error in vma.c
+ * Linux 4.4.111

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

Title:
  Xenial update to 4.4.111 stable release

Status in linux package in Ubuntu:
  New

Bug description:
  SRU Justification

  Impact:

[Kernel-packages] [Bug 1745260] [NEW] [Hyper-V] scsi: storvsc: Spread interrupts when picking a channel for I/O requests

2018-01-24 Thread Joshua R. Poulson

Public bug reported:

Update the algorithm in storvsc_do_io to look for a channel
starting with the current CPU + 1 and wrap around (within the
current NUMA node). This spreads VMbus interrupts more evenly
across CPUs. Previous code always started with first CPU in
the current NUMA node, skewing the interrupt load to that CPU.

This should be applied to the linux-azure kernel

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

** Attachment added: "Upstream submission to lkml"
   
https://bugs.launchpad.net/bugs/1745260/+attachment/5042532/+files/0001-scsi-storvsc-Spread-interrupts-when-picking-a-channe.patch

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

** Changed in: linux-azure (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/1745260

Title:
  [Hyper-V] scsi: storvsc: Spread interrupts when picking a channel for
  I/O requests

Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  Update the algorithm in storvsc_do_io to look for a channel
  starting with the current CPU + 1 and wrap around (within the
  current NUMA node). This spreads VMbus interrupts more evenly
  across CPUs. Previous code always started with first CPU in
  the current NUMA node, skewing the interrupt load to that CPU.

  This should be applied to the linux-azure kernel

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

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

[Kernel-packages] [Bug 1743027] Re: error loading realtime clock since upgrading to 17.10

2018-01-24 Thread Peter Milley

I've followed the instructions in the Wiki page and sent the email to
the maintainers.  I will update when I hear back from them.

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

Title:
  error loading realtime clock since upgrading to 17.10

Status in linux package in Ubuntu:
  Triaged

Bug description:
  (originally asked over at askubuntu.com, but is still unresolved:
  https://askubuntu.com/questions/971349/problem-with-real-time-clock-
  since-upgrading-to-ubuntu-17-10)

  I recently upgraded from Ubuntu 17.04 to Ubuntu 17.10 using the
  software update process. The update completed without any errors, and
  Ubuntu 17.10 is now running without any major issues.

  However, I was running a script previously that uses rtcwake which has
  since stopped working. The script automatically hibernates my laptop
  after a set period of time in sleep mode, and was working perfectly in
  Ubuntu 17.04.

  In the process of troubleshooting, I discovered that the problem was
  with rtcwake which is complaining about /dev/rtc0 missing.

  Here is output from a sample rtcwake command:

  peter@haven:~$ rtcwake -m no -s 1300
  rtcwake: assuming RTC uses UTC ...
  rtcwake: /dev/rtc0: unable to find device: No such file or directory

  I verified that in fact, that directory is missing. Since this was
  working prior to the upgrade, I have to assume that it was there
  previously, but I don't know for sure.

  In researching the error, I found some suggestions to get further
  information with timedatectl and hwclock, so here are the results from
  those commands as well.

  Output of timedatectl:

  peter@haven:~$ timedatectl
Local time: Fri 2017-10-27 19:06:26 EDT
Universal time: Fri 2017-10-27 23:06:26 UTC
  RTC time: n/a
 Time zone: America/New_York (EDT, -0400)
   Network time on: yes
  NTP synchronized: yes
   RTC in local TZ: no

  Output of hwclock --debug:

  peter@haven:~$ sudo hwclock --debug
  [sudo] password for peter: 
  hwclock from util-linux 2.30.1
  Trying to open: /dev/rtc0
  Trying to open: /dev/rtc
  Trying to open: /dev/misc/rtc
  No usable clock interface found.
  hwclock: Cannot access the Hardware Clock via any known method.

  UPDATE

  When I boot with my old kernel, 4.10.0-37-generic the real-time clock
  works fine.

  I get the following RTC messages in dmesg when I boot the
  4.13.0-16-generic kernel:

  peter@haven:~$ dmesg | grep -i rtc
  [0.089393] RTC time: 17:03:55, date: 11/01/17
  [1.238784] rtc_cmos 00:01: RTC can wake from S4
  [1.238794] rtc_cmos: probe of 00:01 failed with error -16
  [1.295459] hctosys: unable to open rtc device (rtc0)

  UPDATE #2

  Well, I was starting to believe that I had a hardware issue, since
  discovering I was unable to save changes to my BIOS and could not boot
  from USB. As it turns out, my laptop was bitten by this bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147 causing
  my BIOS to be locked in a read-only state.

  Once I resolved the BIOS issue, and fixed the USB boot problem, I did
  a live boot of Ubuntu 17.10. The issue with my real time clock still
  exists under this clean boot scenario, yet when I boot other distros,
  like Linux Mint 18.3 and the real time clock works fine. I feel this
  definitely has something to do with the Ubuntu install, perhaps even a
  kernel bug.

  UPDATE #3

  More evidence to suggest this is a kernel bug: I live-booted a copy of
  Antergos Linux, which was using the Arch kernel 4.14.12-1-ARCH and it
  exhibited the same problem with the real time clock as Ubuntu 17.10.
  In addition, I confirmed that the Linux Mint version I booted earlier
  (see Update #2) was on the Ubuntu kernel 4.10.0-38-generic.

  So, I suspect that sometime between kernels 4.10 and 4.13 this bug was 
introduced.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peter  1832 F pulseaudio
   /dev/snd/controlC1:  peter  1832 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=a602efe1-467d-4ac4-806f-1b931c91cdad
  InstallationDate: Installed on 2017-04-05 (292 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 20354
  Package: linux (not installed)
  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.13.0-25-generic.efi.signed 
root=UUID=fa5454aa-9072-475d-b515-acd51a6166cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware

[Kernel-packages] [Bug 1745256] [NEW] bcmwl: module cannot be inserted on Bionic: unknown symbol

2018-01-24 Thread Brenton Horne

Public bug reported:

On a Bionic Beaver system I installed via debootstrap I installed bcmwl-
kernel-source. The installation went largely well, except it seemed to
be experiencing a problem with loading the module. modprobe -a wl
returns:

modprobe: ERROR: could not insert 'wl': Unknown symbol in module, or
unknown parameter (see dmesg)

the lines in dmesg relating to wl are:

[   10.892819] wl: loading out-of-tree module taints kernel.
[   10.892822] wl: module license 'MIXED/Proprietary' taints kernel.
[   10.892823] Disabling lock debugging due to kernel taint
[   10.894423] wl: module verification failed: signature and/or required key 
missing - tainting kernel
[   10.894455] wl: Unknown symbol cfg80211_inform_bss_frame_data (err 0)
[   10.894470] wl: Unknown symbol cfg80211_scan_done (err 0)
[   10.894488] wl: Unknown symbol cfg80211_disconnected (err 0)
[   10.894506] wl: Unknown symbol wiphy_new_nm (err 0)
[   10.894510] wl: Unknown symbol wiphy_register (err 0)
[   10.894513] wl: Unknown symbol cfg80211_put_bss (err 0)
[   10.894514] wl: Unknown symbol cfg80211_roamed (err 0)
[   10.894517] wl: Unknown symbol cfg80211_gtk_rekey_notify (err 0)
[   10.894521] wl: Unknown symbol cfg80211_ibss_joined (err 0)
[   10.894526] wl: Unknown symbol cfg80211_michael_mic_failure (err 0)
[   10.894529] wl: Unknown symbol ieee80211_get_channel (err 0)
[   10.894533] wl: Unknown symbol wiphy_unregister (err 0)
[   10.894537] wl: Unknown symbol cfg80211_get_bss (err 0)
[   10.894549] wl: Unknown symbol ieee80211_channel_to_frequency (err 0)
[   10.894553] wl: Unknown symbol cfg80211_report_wowlan_wakeup (err 0)
[   10.894557] wl: Unknown symbol cfg80211_inform_bss_data (err 0)
[   10.894559] wl: Unknown symbol ieee80211_frequency_to_channel (err 0)
[   10.894563] wl: Unknown symbol cfg80211_connect_done (err 0)
[   10.894565] wl: Unknown symbol wiphy_free (err 0)

I have tried rebooting after I get this error, just in case the kernel
merely needed to be reloaded (doubted it would help but still worth a
try), but alas that didn't help. If relevant I am using a Btrfs file
system.

All the commands I have executed in it since the beginning of time
(which was only a few hours ago, at most, so there isn't much to it) can
be found here in its root bash_history file:

https://gist.github.com/22fdcbead4ce240230fa09f92a730a90

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

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

Title:
  bcmwl: module cannot be inserted on Bionic: unknown symbol

Status in bcmwl package in Ubuntu:
  New

Bug description:
  On a Bionic Beaver system I installed via debootstrap I installed
  bcmwl-kernel-source. The installation went largely well, except it
  seemed to be experiencing a problem with loading the module. modprobe
  -a wl returns:

  modprobe: ERROR: could not insert 'wl': Unknown symbol in module, or
  unknown parameter (see dmesg)

  the lines in dmesg relating to wl are:

  [   10.892819] wl: loading out-of-tree module taints kernel.
  [   10.892822] wl: module license 'MIXED/Proprietary' taints kernel.
  [   10.892823] Disabling lock debugging due to kernel taint
  [   10.894423] wl: module verification failed: signature and/or required key 
missing - tainting kernel
  [   10.894455] wl: Unknown symbol cfg80211_inform_bss_frame_data (err 0)
  [   10.894470] wl: Unknown symbol cfg80211_scan_done (err 0)
  [   10.894488] wl: Unknown symbol cfg80211_disconnected (err 0)
  [   10.894506] wl: Unknown symbol wiphy_new_nm (err 0)
  [   10.894510] wl: Unknown symbol wiphy_register (err 0)
  [   10.894513] wl: Unknown symbol cfg80211_put_bss (err 0)
  [   10.894514] wl: Unknown symbol cfg80211_roamed (err 0)
  [   10.894517] wl: Unknown symbol cfg80211_gtk_rekey_notify (err 0)
  [   10.894521] wl: Unknown symbol cfg80211_ibss_joined (err 0)
  [   10.894526] wl: Unknown symbol cfg80211_michael_mic_failure (err 0)
  [   10.894529] wl: Unknown symbol ieee80211_get_channel (err 0)
  [   10.894533] wl: Unknown symbol wiphy_unregister (err 0)
  [   10.894537] wl: Unknown symbol cfg80211_get_bss (err 0)
  [   10.894549] wl: Unknown symbol ieee80211_channel_to_frequency (err 0)
  [   10.894553] wl: Unknown symbol cfg80211_report_wowlan_wakeup (err 0)
  [   10.894557] wl: Unknown symbol cfg80211_inform_bss_data (err 0)
  [   10.894559] wl: Unknown symbol ieee80211_frequency_to_channel (err 0)
  [   10.894563] wl: Unknown symbol cfg80211_connect_done (err 0)
  [   10.894565] wl: Unknown symbol wiphy_free (err 0)

  I have tried rebooting after I get this error, just in case the kernel
  merely needed to be reloaded (doubted it would help but still worth a
  try), but alas that didn't help. If relevant I am using a Btrfs file
  system.

  All the commands I have executed in it since the beginning of time
  (which was only a few hours ago, at most, so there

[Kernel-packages] [Bug 1745123] Re: Elasticsearch 2.4.6 cause a Oops: 0010 [#37] SMP NOPTI

2018-01-24 Thread Marcos BL

Just confirming this bug with the same exact versions in Linux Mint:

Elasticsearch 2.4.6 + kernel 4.13.0-31-generic #34~16.04.1-Ubuntu


syslog


Jan 25 00:42:34 DevExMachina systemd[1]: Starting Elasticsearch...
Jan 25 00:42:34 DevExMachina systemd[1]: Started Elasticsearch.
Jan 25 00:42:35 DevExMachina kernel: [120549.349622] BUG: unable to handle 
kernel paging request at 06987877
Jan 25 00:42:35 DevExMachina kernel: [120549.350743] IP: 0x6987877
Jan 25 00:42:35 DevExMachina kernel: [120549.351867] PGD 8000b25e1067 
Jan 25 00:42:35 DevExMachina kernel: [120549.351867] P4D 8000b25e1067 
Jan 25 00:42:35 DevExMachina kernel: [120549.351867] PUD 789bc067 
Jan 25 00:42:35 DevExMachina kernel: [120549.351868] PMD 0 
Jan 25 00:42:35 DevExMachina kernel: [120549.351868] 
Jan 25 00:42:35 DevExMachina kernel: [120549.351869] Oops: 0010 [#12] SMP PTI
Jan 25 00:42:35 DevExMachina kernel: [120549.351871] Modules linked in: 
binfmt_misc snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic 
intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_hda_intel coretemp 
snd_hda_codec kvm_intel snd_hda_core kvm snd_hwdep irqbypass snd_pcm 
crct10dif_pclmul gpio_ich snd_seq_midi crc32_pclmul snd_seq_midi_event 
ghash_clmulni_intel snd_rawmidi pcbc snd_seq aesni_intel ipmi_si aes_x86_64 
crypto_simd glue_helper cryptd ipmi_devintf snd_seq_device snd_timer 
intel_cstate hp_wmi input_leds joydev ipmi_msghandler intel_rapl_perf serio_raw 
sparse_keymap wmi_bmof snd soundcore mei_me mei shpchp lpc_ich tpm_infineon 
mac_hid parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq hid_generic 
usbhid hid dm_mirror dm_region_hash dm_log i915 video i2c_algo_bit 
drm_kms_helper syscopyarea sysfillrect e1000e
Jan 25 00:42:35 DevExMachina kernel: [120549.351895]  sysimgblt ahci 
fb_sys_fops psmouse drm libahci ptp pps_core wmi
Jan 25 00:42:35 DevExMachina kernel: [120549.351899] CPU: 1 PID: 15290 Comm: 
java Tainted: G  D 4.13.0-31-generic #34~16.04.1-Ubuntu
Jan 25 00:42:35 DevExMachina kernel: [120549.351900] Hardware name: 
Hewlett-Packard HP Compaq 8200 Elite SFF PC/1495, BIOS J01 v02.15 11/10/2011
Jan 25 00:42:35 DevExMachina kernel: [120549.351900] task: 9d249c8bdd00 
task.stack: b51c04064000
Jan 25 00:42:35 DevExMachina kernel: [120549.351901] RIP: 0010:0x6987877
Jan 25 00:42:35 DevExMachina kernel: [120549.351902] RSP: 0018:b51c04067f50 
EFLAGS: 00010202
Jan 25 00:42:35 DevExMachina kernel: [120549.351902] RAX: 03e7 RBX: 
 RCX: 7fd744b314d9
Jan 25 00:42:35 DevExMachina kernel: [120549.351903] RDX: 7fd73c5e9830 RSI: 
4d73aa93 RDI: 
Jan 25 00:42:35 DevExMachina kernel: [120549.351903] RBP:  R08: 
7fd743f97b64 R09: 000c
Jan 25 00:42:35 DevExMachina kernel: [120549.351904] R10: 06987877 R11: 
9d249c8bdd00 R12: 
Jan 25 00:42:35 DevExMachina kernel: [120549.351904] R13:  R14: 
 R15: 
Jan 25 00:42:35 DevExMachina kernel: [120549.351905] FS:  
7fd74562c700() GS:9d256e24() knlGS:
Jan 25 00:42:35 DevExMachina kernel: [120549.351906] CS:  0010 DS:  ES: 
 CR0: 80050033
Jan 25 00:42:35 DevExMachina kernel: [120549.351906] CR2: 06987877 CR3: 
55dbe004 CR4: 000606e0
Jan 25 00:42:35 DevExMachina kernel: [120549.351907] Call Trace:
Jan 25 00:42:35 DevExMachina kernel: [120549.351913]  ? 
entry_SYSCALL_64_fastpath+0x33/0xa3
Jan 25 00:42:35 DevExMachina kernel: [120549.351914] Code:  Bad RIP value.
Jan 25 00:42:35 DevExMachina kernel: [120549.351915] RIP: 0x6987877 RSP: 
b51c04067f50
Jan 25 00:42:35 DevExMachina kernel: [120549.351915] CR2: 06987877
Jan 25 00:42:35 DevExMachina kernel: [120549.351934] ---[ end trace 
fc665251d9746e58 ]---


journalctl -xe


ene 25 00:44:51 DevExMachina systemd[1]: Starting Elasticsearch...
-- Subject: Unit elasticsearch.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit elasticsearch.service has begun starting up.
ene 25 00:44:51 DevExMachina systemd[1]: Started Elasticsearch.
-- Subject: Unit elasticsearch.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit elasticsearch.service has finished starting up.
-- 
-- The start-up result is done.
ene 25 00:44:51 DevExMachina kernel: BUG: unable to handle kernel paging 
request at 06987877
ene 25 00:44:51 DevExMachina kernel: IP: 0x6987877
ene 25 00:44:51 DevExMachina kernel: PGD 8000349a2067 
ene 25 00:44:51 DevExMachina kernel: P4D 8000349a2067 
ene 25 00:44:51 DevExMachina kernel: PUD b25ed067 
ene 25 00:44:51 DevExMachina kernel: PMD 0 
ene 25 00:44:51 DevExMachina kernel: 
ene 25

[Kernel-packages] [Bug 1744875] Re: Enable Qlogic network drivers for installer

2018-01-24 Thread dann frazier

> 1) Add all E4 FastLinQ qed* drivers (qed, qede, qedr, qedi, qedf)
> 2) Add all E3 FastLinQ bnx* drivers (bnx2, cnic, bnx2x, bnx2i, bnx2fc)

bnx2 and bnx2x are already enabled. As noted, qed/qede have already been
enabled in LP: #1743569.

qedr appears to be a ROCE driver. I don't have a lot of experience with
ROCE - is there a realistic need for that at install-time? (Note that
the driver is already present after install).

bnx2fc, bnx2i, qedf and qedi appear to be storage drivers (over
network). If added, would these actually be usable in an installer
environment?

According to Kconfig, cnic supports offload features. It looks like the
bnx2 driver actually runs the adapter - so it doesn't seem like
something that should go into the installer.



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

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

Title:
  Enable Qlogic network drivers for installer

Status in linux package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  New

Bug description:
  Not all Qlogic network drivers are enabled in the installer kernel (Ubuntu 
16.04) so detection
  of network interface fails during installer network dialog.

  Please enable this drivers:
  1) Add all E4 FastLinQ qed* drivers (qed, qede, qedr, qedi, qedf)
  2) Add all E3 FastLinQ bnx* drivers (bnx2, cnic, bnx2x, bnx2i, bnx2fc)

  qed and qede might already be enabled with a recent change:
  https://bugs.launchpad.net/yarmouth2/+bug/1743569

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

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

[Kernel-packages] [Bug 1744875] Re: Enable Qlogic network drivers for installer

2018-01-24 Thread dann frazier

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

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

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

Title:
  Enable Qlogic network drivers for installer

Status in linux package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  New

Bug description:
  Not all Qlogic network drivers are enabled in the installer kernel (Ubuntu 
16.04) so detection
  of network interface fails during installer network dialog.

  Please enable this drivers:
  1) Add all E4 FastLinQ qed* drivers (qed, qede, qedr, qedi, qedf)
  2) Add all E3 FastLinQ bnx* drivers (bnx2, cnic, bnx2x, bnx2i, bnx2fc)

  qed and qede might already be enabled with a recent change:
  https://bugs.launchpad.net/yarmouth2/+bug/1743569

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

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

[Kernel-packages] [Bug 1745247] Re: [Hyper-V] x86/hyperv: Stop suppressing X86_FEATURE_PCID

2018-01-24 Thread Joshua R. Poulson

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

** Also affects: linux
Importance: Undecided
Status: New

** Changed in: linux
Status: New => Confirmed

** Also affects: linux-lts-xenial (Ubuntu)
Importance: Undecided
Status: New

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

Title:
[Hyper-V] x86/hyperv: Stop suppressing X86_FEATURE_PCID

Status in Linux:
Confirmed
Status in linux-lts-vivid package in Ubuntu:
Confirmed
Status in linux-lts-xenial package in Ubuntu:
New

Bug description:
Anywhere where Meltdown fixes have gone in have likely also picked up
upstream work on TLB flushes. This is an important performance change.

x86/hyperv: Stop suppressing X86_FEATURE_PCIDx86/hyperv

When hypercall-based TLB flush was enabled for Hyper-V guests PCID feature
was deliberately suppressed as a precaution: back then PCID was never
exposed to Hyper-V guests and it wasn't clear what will happen if some day
it becomes available. The day came and PCID/INVPCID features are already
exposed on certain Hyper-V hosts.

From TLFS (as of 5.0b) it is unclear how TLB flush hypercalls combine with
PCID. In particular the usage of PCID is per-cpu based: the same mm gets
different CR3 values on different CPUs. If the hypercall does exact
matching this will fail. However, this is not the case. David Zhang
explains:

"In practice, the AddressSpace argument is ignored on any VM that supports
PCIDs.

Architecturally, the AddressSpace argument must match the CR3 with PCID
bits stripped out (i.e., the low 12 bits of AddressSpace should be 0 in
long mode). The flush hypercalls flush all PCIDs for the specified
AddressSpace."

With this, PCID can be enabled.

Upstream commit link:

https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=04651dd978a8749e59065df14b970a127f219ac2

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

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

[Kernel-packages] [Bug 1745246] [NEW] perf stat segfaults on uncore events w/o -a

2018-01-24 Thread dann frazier

Public bug reported:

[Impact]
perf crashes when monitoring an application for non-system-wide uncore events.

[Test Case]
Before fix:

ubuntu@starbuck:~$ sudo perf stat  -e l1d_cache_rd -- sleep 1
*** Error in `/usr/lib/linux-tools/4.13.0-31.34-generic/perf': free(): invalid 
next size (fast): 0x315f6e80 ***
Aborted

After fix:
ubuntu@starbuck:~$ sudo perf stat  -e l1d_cache_rd -- sleep 1

 Performance counter stats for 'sleep 1':

   159,004  l1d_cache_rd

   1.001223072 seconds time elapsed

[Regression Risk]
The fix involves 2 clean cherry picks from upstream to the perf utility, so any 
regressions introduced by them should have a straightforward support path w/ 
upstream.

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: dann frazier (dannf)
 Status: Fix Released

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

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

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

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

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

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

Title:
  perf stat segfaults on uncore events w/o -a

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

Bug description:
  [Impact]
  perf crashes when monitoring an application for non-system-wide uncore events.

  [Test Case]
  Before fix:

  ubuntu@starbuck:~$ sudo perf stat  -e l1d_cache_rd -- sleep 1
  *** Error in `/usr/lib/linux-tools/4.13.0-31.34-generic/perf': free(): 
invalid next size (fast): 0x315f6e80 ***
  Aborted

  After fix:
  ubuntu@starbuck:~$ sudo perf stat  -e l1d_cache_rd -- sleep 1

   Performance counter stats for 'sleep 1':

 159,004  l1d_cache_rd

 1.001223072 seconds time elapsed

  [Regression Risk]
  The fix involves 2 clean cherry picks from upstream to the perf utility, so 
any regressions introduced by them should have a straightforward support path 
w/ upstream.

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

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

[Kernel-packages] [Bug 1745247] [NEW] [Hyper-V] x86/hyperv: Stop suppressing X86_FEATURE_PCID

2018-01-24 Thread Joshua R. Poulson

Public bug reported:

Anywhere where Meltdown fixes have gone in have likely also picked up
upstream work on TLB flushes. This is an important performance change.

x86/hyperv: Stop suppressing X86_FEATURE_PCIDx86/hyperv

>From TLFS (as of 5.0b) it is unclear how TLB flush hypercalls combine with
PCID. In particular the usage of PCID is per-cpu based: the same mm gets
different CR3 values on different CPUs. If the hypercall does exact
matching this will fail. However, this is not the case. David Zhang
explains:

"In practice, the AddressSpace argument is ignored on any VM that supports
PCIDs.

With this, PCID can be enabled.

Upstream commit link:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=04651dd978a8749e59065df14b970a127f219ac2

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

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

Title:
[Hyper-V] x86/hyperv: Stop suppressing X86_FEATURE_PCID

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

Bug description:
Anywhere where Meltdown fixes have gone in have likely also picked up
upstream work on TLB flushes. This is an important performance change.

x86/hyperv: Stop suppressing X86_FEATURE_PCIDx86/hyperv

"In practice, the AddressSpace argument is ignored on any VM that supports
PCIDs.

With this, PCID can be enabled.

Upstream commit link:

https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=04651dd978a8749e59065df14b970a127f219ac2

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

[Kernel-packages] [Bug 1744214] Re: Boots into initramfs with an error stating that the UUID of the main partition cannot be found when it actually exists

I needed to reinstall Ubuntu and the problems I attached earlier no
longer apply.

** Tags added: kernel-fixed-upstream

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

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

Title:
  Boots into initramfs with an error stating that the UUID of the main
  partition cannot be found when it actually exists

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently updated Ubuntu 18.04 in a vm have a long dormancy and I
  found the issues I had after a reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-generic 4.13.0.17.18
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  reg1325 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 18 21:50:54 2018
  InstallationDate: Installed on 2017-11-27 (52 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.

   enp0s3no 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=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=d15b971c-a592-4259-b4fd-b74cf3c4d03c ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.170
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-11-27 (52 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1745239] [NEW] package bluez 5.37-0ubuntu5.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-01-24 Thread Hugo PAIVA RODRIGUES

Public bug reported:

bug

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bluez 5.37-0ubuntu5.2
ProcVersionSignature: Ubuntu 4.4.0-111.134-generic 4.4.98
Uname: Linux 4.4.0-111-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Wed Jan 24 09:22:04 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-01-16 (739 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
InterestingModules: bnep btusb bluetooth
MachineType: TOSHIBA SATELLITE C875-14H
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-111-generic 
root=UUID=1bb1ab31-fec5-4cde-ac3f-1eed4203d409 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.25
SourcePackage: bluez
Title: package bluez 5.37-0ubuntu5.2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/01/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.80
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: PLCSF8
dmi.board.vendor: Intel
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.80:bd10/01/2013:svnTOSHIBA:pnSATELLITEC875-14H:pvrPSCBCE-02L002FR:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: SATELLITE C875-14H
dmi.product.version: PSCBCE-02L002FR
dmi.sys.vendor: TOSHIBA
hciconfig:
 hci0:  Type: BR/EDR  Bus: USB
BD Address: 24:FD:52:15:9B:97  ACL MTU: 820:8  SCO MTU: 255:16
UP RUNNING PSCAN 
RX bytes:2526 acl:0 sco:0 events:181 errors:0
TX bytes:26261 acl:0 sco:0 commands:181 errors:0

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


** Tags: amd64 apport-package package-from-proposed third-party-packages xenial

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

Title:
  package bluez 5.37-0ubuntu5.2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in bluez package in Ubuntu:
  New

Bug description:
  bug

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.2
  ProcVersionSignature: Ubuntu 4.4.0-111.134-generic 4.4.98
  Uname: Linux 4.4.0-111-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Wed Jan 24 09:22:04 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-01-16 (739 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: bnep btusb bluetooth
  MachineType: TOSHIBA SATELLITE C875-14H
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-111-generic 
root=UUID=1bb1ab31-fec5-4cde-ac3f-1eed4203d409 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: bluez
  Title: package bluez 5.37-0ubuntu5.2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/01/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.80
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PLCSF8
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.80:bd10/01/2013:svnTOSHIBA:pnSATELLITEC875-14H:pvrPSCBCE-02L002FR:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: SATELLITE C875-14H
  dmi.product.version: PSCBCE-02L002FR
  dmi.sys.vendor: TOSHIBA
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 24:FD:52:15:9B:97  ACL MTU: 820:8  SCO MTU: 255:16
UP RUNNING PSCAN 
RX bytes:2526 acl:0 sco:0 events:181 errors:0
TX bytes:26261 acl:0 sco:0 commands:181 errors:0

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

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

[Kernel-packages] [Bug 1745239] Re: package bluez 5.37-0ubuntu5.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-01-24 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package bluez 5.37-0ubuntu5.2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in bluez package in Ubuntu:
  New

Bug description:
  bug

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.2
  ProcVersionSignature: Ubuntu 4.4.0-111.134-generic 4.4.98
  Uname: Linux 4.4.0-111-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Wed Jan 24 09:22:04 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-01-16 (739 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: bnep btusb bluetooth
  MachineType: TOSHIBA SATELLITE C875-14H
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-111-generic 
root=UUID=1bb1ab31-fec5-4cde-ac3f-1eed4203d409 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: bluez
  Title: package bluez 5.37-0ubuntu5.2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/01/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.80
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PLCSF8
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.80:bd10/01/2013:svnTOSHIBA:pnSATELLITEC875-14H:pvrPSCBCE-02L002FR:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: SATELLITE C875-14H
  dmi.product.version: PSCBCE-02L002FR
  dmi.sys.vendor: TOSHIBA
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 24:FD:52:15:9B:97  ACL MTU: 820:8  SCO MTU: 255:16
UP RUNNING PSCAN 
RX bytes:2526 acl:0 sco:0 events:181 errors:0
TX bytes:26261 acl:0 sco:0 commands:181 errors:0

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

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

[Kernel-packages] [Bug 1527727] Re: grub-probe for zfs assumes all devices prefix with /dev, ignoring /dev/disk/...

** Merge proposal linked:
   
https://code.launchpad.net/~smoser/ubuntu/+source/grub2/+git/grub2/+merge/336577

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

Title:
  grub-probe for zfs assumes all devices prefix with /dev, ignoring
  /dev/disk/...

Status in grub:
  Unknown
Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  In Progress
Status in grub2-signed source package in Xenial:
  In Progress
Status in zfs-linux source package in Xenial:
  Confirmed

Bug description:
  [Impact]
  Installs over ZFS where a ZFS disk is expected to be used as a root device.

  [Test case]
  - Run update-grub on a system with a ZFS root filesystem.

  [Regression Potential]
  Installs relying on the current broken behavior to avoid listing other 
operating systems in grub menu may find that new entries are added.

  ---

  update-grub runs /usr/sbin/grub-probe

  Without libzfslinux support compiled in, /usr/sbin/grub-probe runs
  ["zpool", "status", poolname] to find out ZFS info.

  zpool responds with device names as used at (I think!) pool creation
  time. Often, this is /dev/disk/by-id/... names, without the path.

  grub-probe then parses the output, and takes the names of devices, and
  if they do not start with a "/", it prepends "/dev/".

  It then tests the existence of the path name of the device. it fails.

  grub-probe then returns  something like

  /usr/sbin/grub-probe: error: failed to get canonical path of `/dev
  /ata-ST31000333AS_-part1'.

  The actual path is of course /dev/disk/by-
  id/ST31000333AS_-part1

  It can prepend smarter than "/dev" or it can understand ZFS natively,
  to fix the problem.

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

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

[Kernel-packages] [Bug 1744580] Re: 4.4.0-109 kernel panic upon boot with AMD Athlon II X3 455

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

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

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

Title:
  4.4.0-109 kernel panic upon boot with AMD Athlon II X3 455

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  After upgrade to 4.4.0-109, the system won't boot any more.

  At the first boot tentative, the following message is shown and the system 
freezes:
  "Failure reading sector 0xbbcfd0 from hd0"

  Upon retry, a kernel panic is shown (see attached screen hard copy)

  Going back to 4.4.0-104.127-generic solved the problem.

  I've been able to reproduce this bug in a consistent way: I tried
  several times to go boot into 4.0.0-109 and the system froze with the
  described behaviour, but booting into 4.0.0-104 always worked.

  I have checked the bug reports concerning kernel panic after upgrade
  to 4.4.0-108, but this problem seems to be different: I experience
  this problem after upgrading to 4.4.0-109, which presumably fixed the
  problem reported the other bug reports (I don't know if my
  configuration would've worked with 108, because I have not updated
  during a week)

  $ cat /proc/cpuinfo
  processor : 0
  vendor_id : AuthenticAMD
  cpu family: 16
  model : 5
  model name: AMD Athlon(tm) II X3 455 Processor
  stepping  : 3
  microcode : 0x1c8
  cpu MHz   : 800.000
  cache size: 512 KB
  physical id   : 0
  siblings  : 3
  core id   : 0
  cpu cores : 3
  apicid: 0
  initial apicid: 0
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 5
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid pni 
monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs skinit wdt nodeid_msr hw_pstate vmmcall npt 
lbrv svm_lock nrip_save
  bugs  : tlb_mmatch fxsave_leak sysret_ss_attrs
  bogomips  : 6629.24
  TLB size  : 1024 4K pages
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 48 bits physical, 48 bits virtual
  power management: ts ttp tm stc 100mhzsteps hwpstate
  [... and two more identical cpus]
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  administrator   1879 F pulseaudio
   /dev/snd/controlC2:  administrator   1879 F pulseaudio
   /dev/snd/controlC1:  administrator   1879 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=4483f480-1b20-4b71-8f19-8ae0b8239101
  InstallationDate: Installed on 2012-08-21 (1979 days ago)
  InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
root=UUID=765c1614-0bec-4d44-b970-139e13f9f135 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-104-generic N/A
   linux-backports-modules-4.4.0-104-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-104-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo vboxusers
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/20/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1002:bd02/20/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version

[Kernel-packages] [Bug 1743027] Re: error loading realtime clock since upgrading to 17.10

This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to
email the appropriate mailing list. If no response is received, then a
bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-
reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

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

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

Title:
  error loading realtime clock since upgrading to 17.10

Status in linux package in Ubuntu:
  Triaged

Bug description:
  (originally asked over at askubuntu.com, but is still unresolved:
  https://askubuntu.com/questions/971349/problem-with-real-time-clock-
  since-upgrading-to-ubuntu-17-10)

  I recently upgraded from Ubuntu 17.04 to Ubuntu 17.10 using the
  software update process. The update completed without any errors, and
  Ubuntu 17.10 is now running without any major issues.

  However, I was running a script previously that uses rtcwake which has
  since stopped working. The script automatically hibernates my laptop
  after a set period of time in sleep mode, and was working perfectly in
  Ubuntu 17.04.

  In the process of troubleshooting, I discovered that the problem was
  with rtcwake which is complaining about /dev/rtc0 missing.

  Here is output from a sample rtcwake command:

  peter@haven:~$ rtcwake -m no -s 1300
  rtcwake: assuming RTC uses UTC ...
  rtcwake: /dev/rtc0: unable to find device: No such file or directory

  I verified that in fact, that directory is missing. Since this was
  working prior to the upgrade, I have to assume that it was there
  previously, but I don't know for sure.

  In researching the error, I found some suggestions to get further
  information with timedatectl and hwclock, so here are the results from
  those commands as well.

  Output of timedatectl:

  peter@haven:~$ timedatectl
Local time: Fri 2017-10-27 19:06:26 EDT
Universal time: Fri 2017-10-27 23:06:26 UTC
  RTC time: n/a
 Time zone: America/New_York (EDT, -0400)
   Network time on: yes
  NTP synchronized: yes
   RTC in local TZ: no

  Output of hwclock --debug:

  peter@haven:~$ sudo hwclock --debug
  [sudo] password for peter: 
  hwclock from util-linux 2.30.1
  Trying to open: /dev/rtc0
  Trying to open: /dev/rtc
  Trying to open: /dev/misc/rtc
  No usable clock interface found.
  hwclock: Cannot access the Hardware Clock via any known method.

  UPDATE

  When I boot with my old kernel, 4.10.0-37-generic the real-time clock
  works fine.

  I get the following RTC messages in dmesg when I boot the
  4.13.0-16-generic kernel:

  peter@haven:~$ dmesg | grep -i rtc
  [0.089393] RTC time: 17:03:55, date: 11/01/17
  [1.238784] rtc_cmos 00:01: RTC can wake from S4
  [1.238794] rtc_cmos: probe of 00:01 failed with error -16
  [1.295459] hctosys: unable to open rtc device (rtc0)

  UPDATE #2

  Well, I was starting to believe that I had a hardware issue, since
  discovering I was unable to save changes to my BIOS and could not boot
  from USB. As it turns out, my laptop was bitten by this bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147 causing
  my BIOS to be locked in a read-only state.

  Once I resolved the BIOS issue, and fixed the USB boot problem, I did
  a live boot of Ubuntu 17.10. The issue with my real time clock still
  exists under this clean boot scenario, yet when I boot other distros,
  like Linux Mint 18.3 and the real time clock works fine. I feel this
  definitely has something to do with the Ubuntu install, perhaps even a
  kernel bug.

  UPDATE #3

  More evidence to suggest this is a kernel bug: I live-booted a copy of
  Antergos Linux, which was using the Arch kernel 4.14.12-1-ARCH and it
  exhibited the same problem with the real time clock as Ubuntu 17.10.
  In addition, I confirmed that the Linux Mint version I booted earlier
  (see Update #2) was on the Ubuntu kernel 4.10.0-38-generic.

  So, I suspect that sometime between kernels 4.10 and 4.13 this bug was 
introduced.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peter  1832 F pulseaudio
   /dev/snd/controlC1:  peter  1832 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=a602efe1-467d-4ac4-806f-1b931c91cdad
  InstallationDate: Installed on 2017-04-05 (292 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 20354
  Package:

[Kernel-packages] [Bug 1745104] Re: ISST-LTE: KVM:UBUNTU1804: kdump is not working on UbuntuKVM guest

I see this in the trace in comment #2:
"The kernel version is not supported."

I wonder if makedumpfile is seeing the "lp1745104" tag I put in the test
kernel name.  I'll build another kernel without this tag to see if it
helps.

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

Title:
  ISST-LTE: KVM:UBUNTU1804: kdump is not working on UbuntuKVM  guest

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  == Comment: #0 - Chanh H. Nguyen  - 2018-01-23 14:55:05 
==
  root@boslcp4g5:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu Bionic Beaver (development branch)"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic
  root@boslcp4g5:~# uname -r
  4.13.0-25-generic
  root@boslcp4g5:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-25-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.13.0-25-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.13.0-25-generic 
root=UUID=8a776bc5-d9e0-4a1d-9218-135f9c702e11 ro splash quiet nr_cpus=1 
systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@boslcp4g5:~# kdump-config status
  current state   : ready to kdump
  root@boslcp4g5:~# echo c > /proc/sysrq-trigger
  [  176.911191] sysrq: SysRq : This sysrq operation is disabled.
  root@boslcp4g5:~# sysctl -w kernel.sysrq=1
  kernel.sysrq = 1
  root@boslcp4g5:~# echo c > /proc/sysrq-trigger
  [  240.304466] sysrq: SysRq : Trigger a crash
  [  240.304545] Unable to handle kernel paging request for data at address 
0x
  [  240.304656] Faulting instruction address: 0xc0792f88
  [  240.304771] Oops: Kernel access of bad area, sig: 11 [#1]
  [  240.304846] SMP NR_CPUS=2048
  [  240.304848] NUMA
  [  240.304903] pSeries
  [  240.305000] Modules linked in: sctp_diag sctp libcrc32c dccp_diag dccp 
tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag netlink_diag 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache dm_service_time 
vmx_crypto crct10dif_vpmsum binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc 
scsi_dh_alua sunrpc sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq 
crc32c_vpmsum virtio_net virtio_scsi
  [  240.305776] CPU: 12 PID: 1860 Comm: bash Not tainted 4.13.0-25-generic 
#29-Ubuntu
  [  240.305886] task: c000ff904500 task.stack: c001f2d7c000
  [  240.305979] NIP: c0792f88 LR: c0793eb8 CTR: 
c0792f60
  [  240.306087] REGS: c001f2d7f9f0 TRAP: 0300   Not tainted  
(4.13.0-25-generic)
  [  240.306195] MSR: 80009033 
  [  240.306207]   CR: 2842  XER: 2004
  [  240.306338] CFAR: c0793eb4 DAR:  DSISR: 4200 
SOFTE: 1
  [  240.306338] GPR00: c0793eb8 c001f2d7fc70 c15f6200 
0063
  [  240.306338] GPR04: c001feeeade8 c001fef02068 6967676572206120 
63726173680d0a72
  [  240.306338] GPR08: 0007 0001  

  [  240.306338] GPR12: c0792f60 c7ac7e00 10180df8 
10189e30
  [  240.306338] GPR16: 10189ea8 10151210 1018bd58 
1018de48
  [  240.306338] GPR20: 28bc0268 0001 10164590 
10163bb0
  [  240.306338] GPR24: 7fffdcb37d34 7fffdcb37d30 c14fa770 
0002
  [  240.306338] GPR28: 0063 0007 c14824f4 
c14fab10
  [  240.307346] NIP [c0792f88] sysrq_handle_crash+0x28/0x30
  [  240.307474] LR [c0793eb8] __handle_sysrq+0xf8/0x2b0
  [  240.307553] Call Trace:
  [  240.307594] [c001f2d7fc70] [c0793e98] 
__handle_sysrq+0xd8/0x2b0 (unreliable)
  [  240.307715] [c001f2d7fd10] [c07946b4] 
write_sysrq_trigger+0x64/0x90
  [  240.307850] [c001f2d7fd40] [c044fb28] proc_reg_write+0x88/0xd0
  [  240.307951] [c001f2d7fd70] [c03a160c] __vfs_write+0x3c/0x70
  [  240.308049] [c001f2d7fd90] [c03a3248] vfs_write+0xd8/0x220
  [  240.308149] [c001f2d7fde0] [c03a50c8] SyS_write+0x68/0x110
  [  240.308248] [c001f2d7fe30]

[Kernel-packages] [Bug 1510570] [bluez/xenial] possible regression found

2018-01-24 Thread Ubuntu Foundations Team Bug Bot

As a part of the Stable Release Updates quality process a search for
Launchpad bug reports using the version of bluez from xenial-proposed
was performed and bug 1744806 was found. Please investigate this bug
report to ensure that a regression will not be created by this SRU. In
the event that this is not a regression remove the "verification-failed"
tag from this bug report and add the tag "bot-stop-nagging" to bug
1744806 (not this bug). Thanks!

** Tags added: verification-failed

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

Title:
Bluetooth LE pairing fail

Status in OEM Priority Project:
Confirmed
Status in bluez package in Ubuntu:
Fix Released
Status in bluez source package in Xenial:
Fix Committed

Bug description:
[Impact]

When the Bluetooth adapter is not powered on it is not possible to use
it in normal way. We used to have a hack to force powering on by using
an udev rule but this doe snot work anymore. Luckily the BlueZ has
introduced "AutoEnable" option that makes the stack power on adapters by
itself.

Backporting this to xenial will improve life of the desktop users and
will not require them to hack the solution on their own. The fix itself
uses the well known solution to this problem that is floating around
there for a while.

The upload fixes the bug by enabling the 'AutoEnable' option in the
bluetoothd config file.

[Original Report]

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

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

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

here is a commit with this parameter:
http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138

[Test Case]

On xenial install from ppa:
https://launchpad.net/~bluetooth/+archive/ubuntu/bluez

Now reboot the machine. The BT adapter shall be
powered on.

[Regression Potential]

If things go wrong the adapter will not be powered on after the system
boots up. Therefore while testing please focus on the adapter state,
i.e. powered on or off.

[Other Info]

This fix is included in the development release, see:
http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22

[What to upload]

For xenial as in:

) https://launchpad.net/~bluetooth/+archive/ubuntu/bluez
)
https://launchpadlibrarian.net/347480725/bluez_5.37-0ubuntu5_5.37-0ubuntu5.2~build1.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

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

--- Comment From yasm...@br.ibm.com 2018-01-24 14:47 EDT---
Canonical Team,

Do we need to have these patches applied in Qemu for Ubuntu 16.04.3? If
so, could you tell me the repository/branch/mailing list to where I
should send the backport, please?

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

Title:
  spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe
  kernel

Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  New

Bug description:
  kernel: 4.10.0-33.37~16.04.1

  I think this issue was introduced by the old qemu version (similar
  issue was spotted on Xenial before), will need to investigate this
  further.

  
  qemu-system-ppc64 -machine pseries,accel=kvm -bios powerpc/boot_rom.bin 
-display none -serial stdio -kernel powerpc/spapr_hcall.elf -smp 1
  FAIL: hypercall: h_set_sprg0: sprg0 = 0xcafebabedeadbeef
  FAIL: hypercall: h_set_sprg0: sprg0 = 0x
  FAIL: hypercall: h_set_sprg0: sprg0 = 0x41a588
  FAIL: hypercall: h_page_init: h_zero_page
  FAIL: hypercall: h_page_init: h_copy_page
  FAIL: hypercall: h_page_init: h_copy_page+h_zero_page
  FAIL: hypercall: h_page_init: h_zero_page unaligned dst
  FAIL: hypercall: h_page_init: h_copy_page unaligned src
  XFAIL: hypercall: h_random: h-call available

  SUMMARY: 9 tests, 8 unexpected failures, 1 expected failures

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

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

[Kernel-packages] [Bug 1744379] Re: tcp_fastretrans_alert kernel warnings, possible system hardlock

2018-01-24 Thread Lastique

The errors in the kernel log don't appear with kernel version 4.10.17.
However, I still get lockups with that kernel as well.

At this point I think the lockups are probably not related to the
warnings and are possibly caused by a hardware failure. The errors in
the log are still a valid issue, IMHO.


** Summary changed:

- tcp_fastretrans_alert kernel warnings, possible system hardlock
+ tcp_fastretrans_alert kernel warnings

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

Title:
  tcp_fastretrans_alert kernel warnings

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have experienced a full system lockup, not even SysRq+REISUB could
  reboot the system. In the kernel logs I noticed multiple
  tcp_fastretrans_alert warnings and the upstream bug
  (https://bugzilla.kernel.org/show_bug.cgi?id=195835,
  https://bugzilla.kernel.org/show_bug.cgi?id=60779) seems to indicate
  this may be the reason.

  In the attached kernel log, the hang happened immediately before the
  last reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  lastique   3183 F pulseaudio
   /dev/snd/controlC1:  lastique   3183 F pulseaudio
   /dev/snd/controlC2:  lastique   3183 F pulseaudio
   /dev/snd/controlC0:  lastique   3183 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jan 19 22:26:36 2018
  InstallationDate: Installed on 2015-05-01 (993 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: System manufacturer System Product Name
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf 
nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-03 (76 days ago)
  dmi.bios.date: 11/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V 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.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  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/1744379/+subscriptions

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

[Kernel-packages] [Bug 1744214] Re: Boots into initramfs with an error stating that the UUID of the main partition cannot be found when it actually exists

** Attachment added: "This is the output of apt-get remove --purge 
linux-image-extra-4.13.0-25-generic"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744214/+attachment/5042466/+files/P0kVWunc.txt

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

Title:
  Boots into initramfs with an error stating that the UUID of the main
  partition cannot be found when it actually exists

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I recently updated Ubuntu 18.04 in a vm have a long dormancy and I
  found the issues I had after a reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-generic 4.13.0.17.18
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  reg1325 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 18 21:50:54 2018
  InstallationDate: Installed on 2017-11-27 (52 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.

   enp0s3no 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=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=d15b971c-a592-4259-b4fd-b74cf3c4d03c ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.170
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-11-27 (52 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

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

--- Comment From chngu...@us.ibm.com 2018-01-24 15:10 EDT---
(In reply to comment #6)
> I built a test kernel with commit 2621e945fbf1d6df5f3f0ba7be5bae3d2cf9b6a5.
> The test kernel can be downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1745104
>
> Can you test this kernel and see if it resolves this bug?
>
> Note, to test this kernel, you need to install both the linux-image and
> linux-image-extra .deb packages.
>
> Thanks in advance!

Thanks. It works but I see another error the "makedumpfile Failed".

root@boslcp4g5:~# echo c > /proc/sysrq-trigger
[   80.255377] sysrq: SysRq : Trigger a crash
[   80.255490] Unable to handle kernel paging request for data at address 
0x
[   80.255597] Faulting instruction address: 0xc078f608
[   80.255708] Oops: Kernel access of bad area, sig: 11 [#1]
[   80.255781] SMP NR_CPUS=2048
[   80.255782] NUMA
[   80.255837] pSeries
[   80.255930] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd 
grace fscache sctp_diag sctp libcrc32c dccp_diag dccp tcp_diag udp_diag 
raw_diag inet_diag unix_diag af_packet_diag netlink_diag binfmt_misc vmx_crypto 
crct10dif_vpmsum dm_service_time dm_multipath scsi_dh_rdac scsi_dh_emc 
scsi_dh_alua sch_fq_codel sunrpc ip_tables x_tables autofs4 btrfs xor raid6_pq 
crc32c_vpmsum virtio_net virtio_scsi
[   80.256798] CPU: 12 PID: 1928 Comm: bash Not tainted 4.13.0-17-generic 
#20~lp1745104
[   80.256907] task: c53c8a00 task.stack: c001ec3dc000
[   80.257010] NIP: c078f608 LR: c0790538 CTR: c078f5e0
[   80.257116] REGS: c001ec3df9f0 TRAP: 0300   Not tainted  
(4.13.0-17-generic)
[   80.257221] MSR: 80009033 
[   80.257232]   CR: 2842  XER: 2004
[   80.257355] CFAR: c0790534 DAR:  DSISR: 4200 
SOFTE: 1
[   80.257355] GPR00: c0790538 c001ec3dfc70 c1606000 
0063
[   80.257355] GPR04: c001feeeade8 c001fef02068 6967676572206120 
63726173680d0a72
[   80.257355] GPR08: 0007 0001  

[   80.257355] GPR12: c078f5e0 c7ac7e00 10180df8 
10189e30
[   80.257355] GPR16: 10189ea8 10151210 1018bd58 
1018de48
[   80.257355] GPR20: 121f0248 0001 10164590 
10163bb0
[   80.257355] GPR24: 7fffd06a0724 7fffd06a0720 c150a570 
0002
[   80.257355] GPR28: 0063 0004 c14922f4 
c150a910
[   80.258340] NIP [c078f608] sysrq_handle_crash+0x28/0x30
[   80.258433] LR [c0790538] __handle_sysrq+0xf8/0x2b0
[   80.258504] Call Trace:
[   80.258546] [c001ec3dfc70] [c0790518] __handle_sysrq+0xd8/0x2b0 
(unreliable)
[   80.258657] [c001ec3dfd10] [c0790d34] 
write_sysrq_trigger+0x64/0x90
[   80.258789] [c001ec3dfd40] [c044c0c8] proc_reg_write+0x88/0xd0
[   80.258883] [c001ec3dfd70] [c039db8c] __vfs_write+0x3c/0x70
[   80.258975] [c001ec3dfd90] [c039f7c8] vfs_write+0xd8/0x220
[   80.259067] [c001ec3dfde0] [c03a1648] SyS_write+0x68/0x110
[   80.259159] [c001ec3dfe30] [c000b184] system_call+0x58/0x6c
[   80.259248] Instruction dump:
[   80.259306] 4bfff9f1 4bfffe50 3c4c00e7 38426a20 7c0802a6 6000 3921 
3d42001d
[   80.259420] 394ad788 912a 7c0004ac 3940 <992a> 4e800020 3c4c00e7 
384269f0
[   80.259538] ---[ end trace 1a6f8bd87bc98f1a ]---
[   80.266608]
[   80.266754] Sending IPI to other CPUs
[   80.332950] IPI complete
[   80.343090] kexec: Starting switchover sequence.
I'm in purgatory
-> smp_release_cpus()
spinning_secondaries = 15
<- smp_release_cpus()
Linux ppc64le
#20~lp1745104 SM[0.964806] Unable to open file: /etc/keys/x509_ima.der (-2)
[0.964813] Unable to open file: /etc/keys/x509_evm.der (-2)
[1.129495] vio vio: uevent: failed to send synthetic uevent
/dev/sde2: recovering journal
/dev/sde2: clean, 87024/3932160 files, 1989241/15726336 blocks
[2.090741] nvram: Failed to find partition of-config, err 0
[3.200128] vio vio: uevent: failed to send synthetic uevent
[  OK  ] Started Show Plymouth Boot Screen.
plymouth-start.service
[  OK  ] Reached target Local Encrypted Volumes.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
systemd-tmpfiles-setup.service
[  OK  ] Started Create Volatile Files and Directories.
Starting Update UTMP about System Boot/Shutdown...
Starting Network Time Synchronization...
[  OK  ] Started Update UTMP about System Boot/Shutdown.
systemd-update-utmp.service
[  OK  ] Started Network Time Synchronization.
[  OK  ] Reached target System Time Synchronized.
systemd-timesyncd.service
apparmor.service
[  OK  ] Started AppArmor initialization.
[  OK  ] Reached target System Initialization.
[  OK  ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
[  OK  ] Started Wait for Network

[Kernel-packages] [Bug 1744214] Re: Boots into initramfs with an error stating that the UUID of the main partition cannot be found when it actually exists

** Attachment added: "This is the output I get when I try to install 
4.15.0-041500rc9-generic."
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744214/+attachment/5042464/+files/PiJFDc42.txt

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

Title:
  Boots into initramfs with an error stating that the UUID of the main
  partition cannot be found when it actually exists

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I recently updated Ubuntu 18.04 in a vm have a long dormancy and I
  found the issues I had after a reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-generic 4.13.0.17.18
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  reg1325 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 18 21:50:54 2018
  InstallationDate: Installed on 2017-11-27 (52 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.

   enp0s3no 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=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=d15b971c-a592-4259-b4fd-b74cf3c4d03c ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.170
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-11-27 (52 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1744214] Re: Boots into initramfs with an error stating that the UUID of the main partition cannot be found when it actually exists

** Attachment added: "This is the output when I run dpkg --configure -a"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744214/+attachment/5042465/+files/zMWvxbzf.txt

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

Title:
  Boots into initramfs with an error stating that the UUID of the main
  partition cannot be found when it actually exists

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I recently updated Ubuntu 18.04 in a vm have a long dormancy and I
  found the issues I had after a reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-generic 4.13.0.17.18
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  reg1325 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 18 21:50:54 2018
  InstallationDate: Installed on 2017-11-27 (52 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.

   enp0s3no 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=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=d15b971c-a592-4259-b4fd-b74cf3c4d03c ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.170
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-11-27 (52 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

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

--- Comment From yasm...@br.ibm.com 2018-01-24 14:13 EDT---
The reason for this bug is because the h_set_sprg0 and h_page_init hypervisor 
calls were not yet implemented in Qemu 2.5. The problem was solved by two 
patches. They implement one hypercall each.

https://github.com/qemu/qemu/commit/423576f771db8c6dbb944ddb8dc15b472f62de4a

This is a very simple hypercall that only sets up the SPRG0
register for the guest (since writing to SPRG0 was only permitted
to the hypervisor in older versions of the PowerISA).

https://github.com/qemu/qemu/commit/3240dd9a6924df18dfccb83defa0914065da076e

This hypercall either initializes a page with zeros, or copies
another page.
According to LoPAPR, the i-cache of the page should also be
flushed if using H_ICACHE_INVALIDATE or H_ICACHE_SYNCHRONIZE,
and the d-cache should be synchronized to the RAM if the
H_ICACHE_SYNCHRONIZE flag is used. For this, two new functions
are introduced, kvmppc_dcbst_range() and kvmppc_icbi()_range, which
use the corresponding assembler instructions to flush the caches
if running with KVM on Power. If the code runs with TCG instead,
the code only uses tb_flush(), assuming that this will be
enough for synchronization.

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

Title:
  spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe
  kernel

Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  New

Bug description:
  kernel: 4.10.0-33.37~16.04.1

  I think this issue was introduced by the old qemu version (similar
  issue was spotted on Xenial before), will need to investigate this
  further.

  
  qemu-system-ppc64 -machine pseries,accel=kvm -bios powerpc/boot_rom.bin 
-display none -serial stdio -kernel powerpc/spapr_hcall.elf -smp 1
  FAIL: hypercall: h_set_sprg0: sprg0 = 0xcafebabedeadbeef
  FAIL: hypercall: h_set_sprg0: sprg0 = 0x
  FAIL: hypercall: h_set_sprg0: sprg0 = 0x41a588
  FAIL: hypercall: h_page_init: h_zero_page
  FAIL: hypercall: h_page_init: h_copy_page
  FAIL: hypercall: h_page_init: h_copy_page+h_zero_page
  FAIL: hypercall: h_page_init: h_zero_page unaligned dst
  FAIL: hypercall: h_page_init: h_copy_page unaligned src
  XFAIL: hypercall: h_random: h-call available

  SUMMARY: 9 tests, 8 unexpected failures, 1 expected failures

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

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

[Kernel-packages] [Bug 1744214] Re: Boots into initramfs with an error stating that the UUID of the main partition cannot be found when it actually exists

I tried installing and testing the mainline kernel, but I encountered
issues with the linux-image not generating. I also tried to install
openssh-server and ssh while on 4.10.0-19-generic and I get errors that
dpkg failed processing 4.13.0-25 with the new modules. I have tried
uninstalling this same kernel and I encounter similar errors by dpkg.

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

Title:
  Boots into initramfs with an error stating that the UUID of the main
  partition cannot be found when it actually exists

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I recently updated Ubuntu 18.04 in a vm have a long dormancy and I
  found the issues I had after a reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-generic 4.13.0.17.18
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  reg1325 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 18 21:50:54 2018
  InstallationDate: Installed on 2017-11-27 (52 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.

   enp0s3no 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=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=d15b971c-a592-4259-b4fd-b74cf3c4d03c ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.170
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-11-27 (52 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1463120] Re: Failure to boot if fstab disk mounts fail

2018-01-24 Thread Dane Mutters

Could fstab default mount options be changed so that, unless otherwise
specified, failed mount attempts would skip that filesystem and keep
booting (logging an error), instead of dropping to an inaccessible
recovery console? This would let the fstab be fixed with minimal hassle
in a headless environment, so long as the broken mount isn't /boot or /.

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

Title:
  Failure to boot if fstab disk mounts fail

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I found this on my main 15.04 desktop but have reproduced it in a VM:
  1. Install Ubuntu 15.04 (I included updates and non-free but I doubt that 
matters).
  2. Add a bogus entry to /etc/fstab, eg:
/dev/sdd1 /mnt/sdd1 ext4 errors=remount-ro 0 0
  Note that /mnd/sdd1 exists but /dev/sdd1 does not
  3. Reboot

  Expected: Failure to mount /dev/sdd1 reported and option to boot without 
mounting it
  Actual: System appears to hang, although it will eventually present a root 
terminal (with no indication of the cause of the problem). It appears to hang 
prior to switching graphical mode, with the result that any warnings/errors 
that are present on all boots but invisible because the screen clears before 
they're seen become visible for the first time incorrectly suggesting they are 
the cause of the problem.

  Removing (or commenting out) the problematic entries and rebooting
  allows the system to boot.

  HOWEVER: The grub boot menu now appears and any pre-existing menu
  timeout and default action seems to have been lost; it's now necessary
  to select a boot option on each boot. This may be a separate bug (or
  feature?).

  My actual case: I have external drives permanently connected via USB, however 
the USB card appears to have failed hence the drives are not accessible. With 
no clues (and being unfamiliar to systemd) working out why the system wouldn't 
boot was a tough job.
  --- 
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mark   1382 F pulseaudio
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=76b7b79b-0cdd-4605-bc58-381fad8fa67f
  InstallationDate: Installed on 2015-06-08 (4 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  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
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic 
root=UUID=53f2fcea-e84c-4736-ac69-f34305a63432 ro quiet splash
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  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.19.0-20-generic N/A
   linux-backports-modules-3.19.0-20-generic  N/A
   linux-firmware 1.143.1
  RfKill:
   
  Tags:  vivid
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 3.19.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1745130] Re: Support rfkill-any led trigger for Fujitsu u727

2018-01-24 Thread Jan-Marek Glogowski

Thanks a lot. After apw's comment on IRC I expected something in the
next weeks :-)

I can just tell you it boots and seems to work. When I tried to manually
build my hw-support-dkms against the kernel I got:

LANG=C ./r 
+ pwd
+ make -C /usr/src/linux-headers-4.4.0-112-generic M=/home/glg/mod
make: Entering directory `/usr/src/linux-headers-4.4.0-112-generic'
Makefile:702: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: 
-fstack-protector-strong not supported by compiler
  CC [M]  /home/glg/mod/fujitsu-laptop.o
gcc: error: unrecognized command line option '-fstack-protector-strong'
make[1]: *** [/home/glg/mod/fujitsu-laptop.o] Error 1
make: *** [_module_/home/glg/mod] Error 2
make: Leaving directory `/usr/src/linux-headers-4.4.0-112-generic'

So I guess this kernel was build on Xenial, which I don't have
installed. I have Trusty and Bionic, which has the upstream patch
included.

But generally it looks ok'ish, as rfkill-any shows up:

$ cat /sys/class/leds/input2\:\:capslock/trigger 
none rfkill-any kbd-scrolllock kbd-numlock [kbd-capslock] kbd-kanalock 
kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock 
kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock AC-online CMB1-charging-or-full 
CMB1-charging CMB1-full CMB1-charging-blink-full-solid usb-gadget usb-host cpu0 
cpu1 cpu2 cpu3 cpu4 cpu5 cpu6 cpu7 mmc0 rfkill0 rfkill1 phy0rx phy0tx phy0assoc 
phy0radio

For a test I used the the caspslock led and manually set the soft
rfkill, which triggers the led correctly:

$ echo "rfkill-any" | sudo tee /sys/class/leds/input2\:\:capslock/trigger  
rfkill-any
$ cat /sys/class/leds/input2\:\:capslock/trigger 
none [rfkill-any] kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock 
kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock 
kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock AC-online CMB1-charging-or-full 
CMB1-charging CMB1-full CMB1-charging-blink-full-solid usb-gadget usb-host cpu0 
cpu1 cpu2 cpu3 cpu4 cpu5 cpu6 cpu7 mmc0 rfkill0 rfkill1 phy0rx phy0tx phy0assoc 
phy0radio 

=> capslock led is on

$ sudo rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

$ sudo rfkill block 0
$ sudo rfkill block 1

=> capslock led is off

I tried all combinations of block and unblock.
No stacks in the dmesg.

So I guess it works as expected.

If you can provide a Trusty based kernel, I'll test it tomorrow.

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

Title:
  Support rfkill-any led trigger for Fujitsu u727

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

Bug description:
  I got new HW from our supplier, which is the Fujitsu u7x7 laptop series based 
on Skylake hardware.
  It has a single rfkill button and a single LED for wlan and bluetooth. Both 
device driver currently provide a single rfkill trigger, so the led could just 
be assigned to one. As a result the upstream kernel got a new "rfkill-any" led 
trigger to correctly handle the led with multiple rfkill devices. That was 
added by one of the fujitsu-laptop maintainers and the driver sets it as the 
default trigger.

  commit 9b8e34e211b15af429b72388a8f2b3b1823d172e
  Author: Michał Kępień 
  Date:   Fri Jan 6 07:07:47 2017 +0100

  rfkill: Add rfkill-any LED trigger

  Normally I would simply patch the affected modules using DKMS, like the 
i915_bpo driver, fujitsu-laptop and snd_hda_codec_realtek to support the HW 
without messing with the kernel packages.
  I'm currently waiting for some reviews, like 
https://www.spinics.net/lists/platform-driver-x86/msg14606.html

  But the rfkill support is compiled in, so I can't patch it using DKMS.

  So my first proposed fix would be to include a backport of this patch.
  Alternatively rfkill can be compiled as a module, so I can patch it
  and provide an updated module.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.4.0-111-generic 4.4.0-111.134~14.04.1
  ProcVersionSignature: Ubuntu 4.4.0-111.134~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-111-generic i686
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: i386
  Date: Wed Jan 24 10:48:28 2018
  SourcePackage: linux-lts-xenial
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1745104] Re: ISST-LTE: KVM:UBUNTU1804: kdump is not working on UbuntuKVM guest

2018-01-24 Thread Frank Heimes

** Changed in: ubuntu-power-systems
   Status: Triaged => In Progress

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

Title:
  ISST-LTE: KVM:UBUNTU1804: kdump is not working on UbuntuKVM  guest

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  == Comment: #0 - Chanh H. Nguyen  - 2018-01-23 14:55:05 
==
  root@boslcp4g5:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu Bionic Beaver (development branch)"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic
  root@boslcp4g5:~# uname -r
  4.13.0-25-generic
  root@boslcp4g5:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-25-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.13.0-25-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.13.0-25-generic 
root=UUID=8a776bc5-d9e0-4a1d-9218-135f9c702e11 ro splash quiet nr_cpus=1 
systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@boslcp4g5:~# kdump-config status
  current state   : ready to kdump
  root@boslcp4g5:~# echo c > /proc/sysrq-trigger
  [  176.911191] sysrq: SysRq : This sysrq operation is disabled.
  root@boslcp4g5:~# sysctl -w kernel.sysrq=1
  kernel.sysrq = 1
  root@boslcp4g5:~# echo c > /proc/sysrq-trigger
  [  240.304466] sysrq: SysRq : Trigger a crash
  [  240.304545] Unable to handle kernel paging request for data at address 
0x
  [  240.304656] Faulting instruction address: 0xc0792f88
  [  240.304771] Oops: Kernel access of bad area, sig: 11 [#1]
  [  240.304846] SMP NR_CPUS=2048
  [  240.304848] NUMA
  [  240.304903] pSeries
  [  240.305000] Modules linked in: sctp_diag sctp libcrc32c dccp_diag dccp 
tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag netlink_diag 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache dm_service_time 
vmx_crypto crct10dif_vpmsum binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc 
scsi_dh_alua sunrpc sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq 
crc32c_vpmsum virtio_net virtio_scsi
  [  240.305776] CPU: 12 PID: 1860 Comm: bash Not tainted 4.13.0-25-generic 
#29-Ubuntu
  [  240.305886] task: c000ff904500 task.stack: c001f2d7c000
  [  240.305979] NIP: c0792f88 LR: c0793eb8 CTR: 
c0792f60
  [  240.306087] REGS: c001f2d7f9f0 TRAP: 0300   Not tainted  
(4.13.0-25-generic)
  [  240.306195] MSR: 80009033 
  [  240.306207]   CR: 2842  XER: 2004
  [  240.306338] CFAR: c0793eb4 DAR:  DSISR: 4200 
SOFTE: 1
  [  240.306338] GPR00: c0793eb8 c001f2d7fc70 c15f6200 
0063
  [  240.306338] GPR04: c001feeeade8 c001fef02068 6967676572206120 
63726173680d0a72
  [  240.306338] GPR08: 0007 0001  

  [  240.306338] GPR12: c0792f60 c7ac7e00 10180df8 
10189e30
  [  240.306338] GPR16: 10189ea8 10151210 1018bd58 
1018de48
  [  240.306338] GPR20: 28bc0268 0001 10164590 
10163bb0
  [  240.306338] GPR24: 7fffdcb37d34 7fffdcb37d30 c14fa770 
0002
  [  240.306338] GPR28: 0063 0007 c14824f4 
c14fab10
  [  240.307346] NIP [c0792f88] sysrq_handle_crash+0x28/0x30
  [  240.307474] LR [c0793eb8] __handle_sysrq+0xf8/0x2b0
  [  240.307553] Call Trace:
  [  240.307594] [c001f2d7fc70] [c0793e98] 
__handle_sysrq+0xd8/0x2b0 (unreliable)
  [  240.307715] [c001f2d7fd10] [c07946b4] 
write_sysrq_trigger+0x64/0x90
  [  240.307850] [c001f2d7fd40] [c044fb28] proc_reg_write+0x88/0xd0
  [  240.307951] [c001f2d7fd70] [c03a160c] __vfs_write+0x3c/0x70
  [  240.308049] [c001f2d7fd90] [c03a3248] vfs_write+0xd8/0x220
  [  240.308149] [c001f2d7fde0] [c03a50c8] SyS_write+0x68/0x110
  [  240.308248] [c001f2d7fe30] [c000b184] system_call+0x58/0x6c
  [  240.308340] Instruction dump:
  [  240.308400] 4bfff9f1 4bfffe50 3c4c00e6 384232a0 7c0802a6 6000 3921 
3d42001d
  [

[Kernel-packages] [Bug 1745104] Re: ISST-LTE: KVM:UBUNTU1804: kdump is not working on UbuntuKVM guest

I built a test kernel with commit 2621e945fbf1d6df5f3f0ba7be5bae3d2cf9b6a5.  
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1745104

Can you test this kernel and see if it resolves this bug?

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

Thanks in advance!

** Also affects: linux (Ubuntu Bionic)
   Importance: Critical
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
   Status: Triaged

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Joseph Salisbury (jsalisbury)

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

Title:
  ISST-LTE: KVM:UBUNTU1804: kdump is not working on UbuntuKVM  guest

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  == Comment: #0 - Chanh H. Nguyen  - 2018-01-23 14:55:05 
==
  root@boslcp4g5:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu Bionic Beaver (development branch)"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic
  root@boslcp4g5:~# uname -r
  4.13.0-25-generic
  root@boslcp4g5:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-25-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.13.0-25-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.13.0-25-generic 
root=UUID=8a776bc5-d9e0-4a1d-9218-135f9c702e11 ro splash quiet nr_cpus=1 
systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@boslcp4g5:~# kdump-config status
  current state   : ready to kdump
  root@boslcp4g5:~# echo c > /proc/sysrq-trigger
  [  176.911191] sysrq: SysRq : This sysrq operation is disabled.
  root@boslcp4g5:~# sysctl -w kernel.sysrq=1
  kernel.sysrq = 1
  root@boslcp4g5:~# echo c > /proc/sysrq-trigger
  [  240.304466] sysrq: SysRq : Trigger a crash
  [  240.304545] Unable to handle kernel paging request for data at address 
0x
  [  240.304656] Faulting instruction address: 0xc0792f88
  [  240.304771] Oops: Kernel access of bad area, sig: 11 [#1]
  [  240.304846] SMP NR_CPUS=2048
  [  240.304848] NUMA
  [  240.304903] pSeries
  [  240.305000] Modules linked in: sctp_diag sctp libcrc32c dccp_diag dccp 
tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag netlink_diag 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache dm_service_time 
vmx_crypto crct10dif_vpmsum binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc 
scsi_dh_alua sunrpc sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq 
crc32c_vpmsum virtio_net virtio_scsi
  [  240.305776] CPU: 12 PID: 1860 Comm: bash Not tainted 4.13.0-25-generic 
#29-Ubuntu
  [  240.305886] task: c000ff904500 task.stack: c001f2d7c000
  [  240.305979] NIP: c0792f88 LR: c0793eb8 CTR: 
c0792f60
  [  240.306087] REGS: c001f2d7f9f0 TRAP: 0300   Not tainted  
(4.13.0-25-generic)
  [  240.306195] MSR: 80009033 
  [  240.306207]   CR: 2842  XER: 2004
  [  240.306338] CFAR: c0793eb4 DAR:  DSISR: 4200 
SOFTE: 1
  [  240.306338] GPR00: c0793eb8 c001f2d7fc70 c15f6200 
0063
  [  240.306338] GPR04: c001feeeade8 c001fef02068 6967676572206120 
63726173680d0a72
  [  240.306338] GPR08: 0007 0001  

  [  240.306338] GPR12: c0792f60 c7ac7e00 10180df8 
10189e30
  [  240.306338] GPR16: 10189ea8 10151210 1018bd58 
1018de48
  [  240.306338] GPR20: 28bc0268 0001 10164590 
10163bb0
  [  240.306338] GPR24: 7fffdcb37d34 7fffdcb37d30 c14fa770 
0002
  [  240.306338] GPR28: 0063 0007 c14824f4 
c14fab10
  [  240.307346] NIP [c0792f88] sysrq_handle_crash+0x28/0x30
  [  240.307474] LR [c0793eb8] __handle_sysrq+0xf8/0x2b0
  [  240.307553] Call Trace:
  [  240.307594] [c001f2d7fc70]

[Kernel-packages] [Bug 1745123] Re: Elasticsearch 2.4.6 cause a Oops: 0010 [#37] SMP NOPTI

2018-01-24 Thread Jeffrey Bouter

ElasticSearch doens't log anything itself. There's just this in
journalctl -xe

-- Unit elasticsearch.service has begun starting up.
Jan 24 18:34:26 logness systemd[1]: Started Elasticsearch.
-- Subject: Unit elasticsearch.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit elasticsearch.service has finished starting up.
-- 
-- The start-up result is done.
Jan 24 18:34:27 logness kernel: kernel tried to execute NX-protected page - 
exploit attempt? (uid: 111)
Jan 24 18:34:27 logness kernel: BUG: unable to handle kernel paging request at 
7f8429f767a0
Jan 24 18:34:27 logness kernel: IP: 0x7f8429f767a0
Jan 24 18:34:27 logness kernel: PGD 800136028067 
Jan 24 18:34:27 logness kernel: P4D 800136028067 
Jan 24 18:34:27 logness kernel: PUD 139ea5067 
Jan 24 18:34:27 logness kernel: PMD 139f07067 
Jan 24 18:34:27 logness kernel: PTE 800109a6f867
Jan 24 18:34:27 logness kernel: 
Jan 24 18:34:27 logness kernel: Oops: 0011 [#9] SMP PTI
Jan 24 18:34:27 logness kernel: Modules linked in: ppdev snd_hda_codec_generic 
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep input_leds snd_pcm joydev 
serio_raw snd_timer snd i2c_piix4 soundcore
Jan 24 18:34:27 logness kernel:  linear hid_generic usbhid hid qxl ttm 
drm_kms_helper syscopyarea sysfillrect psmouse virtio_blk virtio_net sysimgblt 
fb_sys_fops drm pata_acpi floppy
Jan 24 18:34:27 logness kernel: CPU: 0 PID: 2305 Comm: java Tainted: G  D   
  4.13.0-31-generic #34~16.04.1-Ubuntu
Jan 24 18:34:27 logness kernel: Hardware name: QEMU Standard PC (i440FX + PIIX, 
1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014
Jan 24 18:34:27 logness kernel: task: 984ff604d800 task.stack: 
ac7b41dfc000
Jan 24 18:34:27 logness kernel: RIP: 0010:0x7f8429f767a0
Jan 24 18:34:27 logness kernel: RSP: 0018:ac7b41dfff50 EFLAGS: 00010202
Jan 24 18:34:27 logness kernel: RAX: 03e7 RBX:  
RCX: 7f84298884d9
Jan 24 18:34:27 logness kernel: RDX: 7f8429f76f50 RSI: 7f8429f77030 
RDI: 
Jan 24 18:34:27 logness kernel: RBP:  R08:  
R09: 000c
Jan 24 18:34:27 logness kernel: R10: 7f8429f767a0 R11: 984ff604d800 
R12: 
Jan 24 18:34:27 logness kernel: R13:  R14:  
R15: 
Jan 24 18:34:27 logness kernel: FS:  7f8429f78700() 
GS:984fffc0() knlGS:
Jan 24 18:34:27 logness kernel: CS:  0010 DS:  ES:  CR0: 
80050033
Jan 24 18:34:27 logness kernel: CR2: 7f8429f767a0 CR3: 000136022000 
CR4: 06f0
Jan 24 18:34:27 logness kernel: Call Trace:
Jan 24 18:34:27 logness kernel:  ? entry_SYSCALL_64_fastpath+0x33/0xa3
Jan 24 18:34:27 logness kernel: Code:  Bad RIP value.
Jan 24 18:34:27 logness kernel: RIP: 0x7f8429f767a0 RSP: ac7b41dfff50
Jan 24 18:34:27 logness kernel: CR2: 7f8429f767a0
Jan 24 18:34:27 logness kernel: ---[ end trace 2b5dfc9417bb8d5f ]---


** Also affects: elasticsearch (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Elasticsearch 2.4.6 cause a Oops: 0010 [#37] SMP NOPTI

Status in elasticsearch package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Triaged
Status in elasticsearch source package in Artful:
  New
Status in linux source package in Artful:
  Triaged

Bug description:
  Elasticsearch 2.4.6 can't start since new kernel upgrade
  (4.13.0-31-generic #34~16.04.1-Ubuntu)

  Kernel log contains :

  [ 4308.595429] Oops: 0010 [#37] SMP NOPTI
  [ 4308.595430] Modules linked in: btrfs xor raid6_pq ufs qnx4 hfsplus hfs 
minix ntfs msdos jfs xfs libcrc32c bnep pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) bluetooth ecdh_generic binfmt_misc nls_iso8859_1 
snd_hda_codec_hdmi edac_mce_amd snd_hda_codec_realtek snd_hda_codec_generic 
snd_hda_intel eeepc_wmi kvm_amd asus_wmi snd_hda_codec sparse_keymap 
snd_hda_core video wmi_bmof kvm input_leds joydev snd_hwdep snd_pcm irqbypass 
crct10dif_pclmul snd_seq_midi crc32_pclmul snd_seq_midi_event 
ghash_clmulni_intel snd_rawmidi pcbc nvidia_uvm(POE) snd_seq aesni_intel 
snd_seq_device snd_timer snd aes_x86_64 crypto_simd soundcore ccp glue_helper 
cryptd shpchp i2c_piix4 8250_dw wmi mac_hid parport_pc ppdev lp parport autofs4 
hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE)
  [ 4308.595462]  drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
drm r8169 ahci mii libahci gpio_amdpt gpio_generic
  [ 4308.595468] CPU: 0 PID: 9314 Comm: java Tainted: P  DOE   
4.13.0-31-generic #34~16.04.1-Ubuntu
  [ 4308.595470] Hardware name: System manufacturer System Product Name/PRIME 
B350M-A, BIOS 0502 02/24/2017
  [ 4308.595471] task: 8dfa07b945c0 task.stack: b2b6033f4000

[Kernel-packages] [Bug 1745130] Re: Support rfkill-any led trigger for Fujitsu u727

I built a test kernel with commit 9b8e34e211b15af429b72388a8f2b3b1823d172e.  
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1745130

Can you test this kernel and see if it resolves this bug?

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

Thanks in advance.

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

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

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

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

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

Title:
  Support rfkill-any led trigger for Fujitsu u727

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

Bug description:
  I got new HW from our supplier, which is the Fujitsu u7x7 laptop series based 
on Skylake hardware.
  It has a single rfkill button and a single LED for wlan and bluetooth. Both 
device driver currently provide a single rfkill trigger, so the led could just 
be assigned to one. As a result the upstream kernel got a new "rfkill-any" led 
trigger to correctly handle the led with multiple rfkill devices. That was 
added by one of the fujitsu-laptop maintainers and the driver sets it as the 
default trigger.

  commit 9b8e34e211b15af429b72388a8f2b3b1823d172e
  Author: Michał Kępień 
  Date:   Fri Jan 6 07:07:47 2017 +0100

  rfkill: Add rfkill-any LED trigger

  Normally I would simply patch the affected modules using DKMS, like the 
i915_bpo driver, fujitsu-laptop and snd_hda_codec_realtek to support the HW 
without messing with the kernel packages.
  I'm currently waiting for some reviews, like 
https://www.spinics.net/lists/platform-driver-x86/msg14606.html

  But the rfkill support is compiled in, so I can't patch it using DKMS.

  So my first proposed fix would be to include a backport of this patch.
  Alternatively rfkill can be compiled as a module, so I can patch it
  and provide an updated module.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.4.0-111-generic 4.4.0-111.134~14.04.1
  ProcVersionSignature: Ubuntu 4.4.0-111.134~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-111-generic i686
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: i386
  Date: Wed Jan 24 10:48:28 2018
  SourcePackage: linux-lts-xenial
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1742502] Re: 108 and 109 kernel hangs

2018-01-24 Thread Joey Stanford

112 kernel has the same issue.  Adding nopti allows it to boot.
What's different: It stops after zswap loading.

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

Title:
  108 and 109 kernel hangs

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

Bug description:
  Overnight I had 2 of 12  16.04 servers brick with the 108 kernel. They
  also do not work with 109.  They work fine with 104. The other 10
  worked fine on both 108 and 109.

  All are hosted on VMWARE. The two broken ones stop at the same place.
  I was able to go back to the 104 kernel to get them working and pin
  the kernel version.

  Just for fun, I set zswap.enabled=0 and they both crashed with kthread
  starved for jiffies. They are both multi-processor with lots of ram
  and disk.

  I have a task from the Ubuntu Kernel team to try this with 'nopti'.
  I'll report back.

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

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

[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

2018-01-24 Thread Kai-Heng Feng

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The AC adapter status is incorrectly reported when the battery is
  fully charged. It always shows as if the adapter is not plugged in. If
  the battery is drained for a while, the adapter status is shown
  correctly (both connects and disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1745104] Re: ISST-LTE: KVM:UBUNTU1804: kdump is not working on UbuntuKVM guest

2018-01-24 Thread Frank Heimes

** Changed in: ubuntu-power-systems
   Status: New => Triaged

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

Title:
  ISST-LTE: KVM:UBUNTU1804: kdump is not working on UbuntuKVM  guest

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Chanh H. Nguyen  - 2018-01-23 14:55:05 
==
  root@boslcp4g5:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu Bionic Beaver (development branch)"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic
  root@boslcp4g5:~# uname -r
  4.13.0-25-generic
  root@boslcp4g5:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-25-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.13.0-25-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.13.0-25-generic 
root=UUID=8a776bc5-d9e0-4a1d-9218-135f9c702e11 ro splash quiet nr_cpus=1 
systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@boslcp4g5:~# kdump-config status
  current state   : ready to kdump
  root@boslcp4g5:~# echo c > /proc/sysrq-trigger
  [  176.911191] sysrq: SysRq : This sysrq operation is disabled.
  root@boslcp4g5:~# sysctl -w kernel.sysrq=1
  kernel.sysrq = 1
  root@boslcp4g5:~# echo c > /proc/sysrq-trigger
  [  240.304466] sysrq: SysRq : Trigger a crash
  [  240.304545] Unable to handle kernel paging request for data at address 
0x
  [  240.304656] Faulting instruction address: 0xc0792f88
  [  240.304771] Oops: Kernel access of bad area, sig: 11 [#1]
  [  240.304846] SMP NR_CPUS=2048
  [  240.304848] NUMA
  [  240.304903] pSeries
  [  240.305000] Modules linked in: sctp_diag sctp libcrc32c dccp_diag dccp 
tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag netlink_diag 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache dm_service_time 
vmx_crypto crct10dif_vpmsum binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc 
scsi_dh_alua sunrpc sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq 
crc32c_vpmsum virtio_net virtio_scsi
  [  240.305776] CPU: 12 PID: 1860 Comm: bash Not tainted 4.13.0-25-generic 
#29-Ubuntu
  [  240.305886] task: c000ff904500 task.stack: c001f2d7c000
  [  240.305979] NIP: c0792f88 LR: c0793eb8 CTR: 
c0792f60
  [  240.306087] REGS: c001f2d7f9f0 TRAP: 0300   Not tainted  
(4.13.0-25-generic)
  [  240.306195] MSR: 80009033 
  [  240.306207]   CR: 2842  XER: 2004
  [  240.306338] CFAR: c0793eb4 DAR:  DSISR: 4200 
SOFTE: 1
  [  240.306338] GPR00: c0793eb8 c001f2d7fc70 c15f6200 
0063
  [  240.306338] GPR04: c001feeeade8 c001fef02068 6967676572206120 
63726173680d0a72
  [  240.306338] GPR08: 0007 0001  

  [  240.306338] GPR12: c0792f60 c7ac7e00 10180df8 
10189e30
  [  240.306338] GPR16: 10189ea8 10151210 1018bd58 
1018de48
  [  240.306338] GPR20: 28bc0268 0001 10164590 
10163bb0
  [  240.306338] GPR24: 7fffdcb37d34 7fffdcb37d30 c14fa770 
0002
  [  240.306338] GPR28: 0063 0007 c14824f4 
c14fab10
  [  240.307346] NIP [c0792f88] sysrq_handle_crash+0x28/0x30
  [  240.307474] LR [c0793eb8] __handle_sysrq+0xf8/0x2b0
  [  240.307553] Call Trace:
  [  240.307594] [c001f2d7fc70] [c0793e98] 
__handle_sysrq+0xd8/0x2b0 (unreliable)
  [  240.307715] [c001f2d7fd10] [c07946b4] 
write_sysrq_trigger+0x64/0x90
  [  240.307850] [c001f2d7fd40] [c044fb28] proc_reg_write+0x88/0xd0
  [  240.307951] [c001f2d7fd70] [c03a160c] __vfs_write+0x3c/0x70
  [  240.308049] [c001f2d7fd90] [c03a3248] vfs_write+0xd8/0x220
  [  240.308149] [c001f2d7fde0] [c03a50c8] SyS_write+0x68/0x110
  [  240.308248] [c001f2d7fe30] [c000b184] system_call+0x58/0x6c
  [  240.308340] Instruction dump:
  [  240.308400] 4bfff9f1 4bfffe50 3c4c00e6 384232a0 7c0802a6 6000 3921 
3d42001d
  [  240.308522] 394adab0 912a 7c0004ac 3940 <992a> 4e800020

[Kernel-packages] [Bug 1463120] Re: Failure to boot if fstab disk mounts fail

2018-01-24 Thread Hudson Kendall

This is a serious issue when there is no physical access to the machine.
I can confirm this issue on 16.04 happen after adding a new harddrive to
the fstab and subsequently reformatting the drive.  At reboot, I have to
options to resolve the situation.  All network requests are ignored,
because the boot sequence can not complete.

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

Title:
  Failure to boot if fstab disk mounts fail

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I found this on my main 15.04 desktop but have reproduced it in a VM:
  1. Install Ubuntu 15.04 (I included updates and non-free but I doubt that 
matters).
  2. Add a bogus entry to /etc/fstab, eg:
/dev/sdd1 /mnt/sdd1 ext4 errors=remount-ro 0 0
  Note that /mnd/sdd1 exists but /dev/sdd1 does not
  3. Reboot

  Expected: Failure to mount /dev/sdd1 reported and option to boot without 
mounting it
  Actual: System appears to hang, although it will eventually present a root 
terminal (with no indication of the cause of the problem). It appears to hang 
prior to switching graphical mode, with the result that any warnings/errors 
that are present on all boots but invisible because the screen clears before 
they're seen become visible for the first time incorrectly suggesting they are 
the cause of the problem.

  Removing (or commenting out) the problematic entries and rebooting
  allows the system to boot.

  HOWEVER: The grub boot menu now appears and any pre-existing menu
  timeout and default action seems to have been lost; it's now necessary
  to select a boot option on each boot. This may be a separate bug (or
  feature?).

  My actual case: I have external drives permanently connected via USB, however 
the USB card appears to have failed hence the drives are not accessible. With 
no clues (and being unfamiliar to systemd) working out why the system wouldn't 
boot was a tough job.
  --- 
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mark   1382 F pulseaudio
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=76b7b79b-0cdd-4605-bc58-381fad8fa67f
  InstallationDate: Installed on 2015-06-08 (4 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  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
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic 
root=UUID=53f2fcea-e84c-4736-ac69-f34305a63432 ro quiet splash
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  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.19.0-20-generic N/A
   linux-backports-modules-3.19.0-20-generic  N/A
   linux-firmware 1.143.1
  RfKill:
   
  Tags:  vivid
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 3.19.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

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

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

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The AC adapter status is incorrectly reported when the battery is
  fully charged. It always shows as if the adapter is not plugged in. If
  the battery is drained for a while, the adapter status is shown
  correctly (both connects and disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1745104] Re: ISST-LTE: KVM:UBUNTU1804: kdump is not working on UbuntuKVM guest

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

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

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

Title:
  ISST-LTE: KVM:UBUNTU1804: kdump is not working on UbuntuKVM  guest

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Chanh H. Nguyen  - 2018-01-23 14:55:05 
==
  root@boslcp4g5:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu Bionic Beaver (development branch)"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic
  root@boslcp4g5:~# uname -r
  4.13.0-25-generic
  root@boslcp4g5:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-25-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.13.0-25-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.13.0-25-generic 
root=UUID=8a776bc5-d9e0-4a1d-9218-135f9c702e11 ro splash quiet nr_cpus=1 
systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@boslcp4g5:~# kdump-config status
  current state   : ready to kdump
  root@boslcp4g5:~# echo c > /proc/sysrq-trigger
  [  176.911191] sysrq: SysRq : This sysrq operation is disabled.
  root@boslcp4g5:~# sysctl -w kernel.sysrq=1
  kernel.sysrq = 1
  root@boslcp4g5:~# echo c > /proc/sysrq-trigger
  [  240.304466] sysrq: SysRq : Trigger a crash
  [  240.304545] Unable to handle kernel paging request for data at address 
0x
  [  240.304656] Faulting instruction address: 0xc0792f88
  [  240.304771] Oops: Kernel access of bad area, sig: 11 [#1]
  [  240.304846] SMP NR_CPUS=2048
  [  240.304848] NUMA
  [  240.304903] pSeries
  [  240.305000] Modules linked in: sctp_diag sctp libcrc32c dccp_diag dccp 
tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag netlink_diag 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache dm_service_time 
vmx_crypto crct10dif_vpmsum binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc 
scsi_dh_alua sunrpc sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq 
crc32c_vpmsum virtio_net virtio_scsi
  [  240.305776] CPU: 12 PID: 1860 Comm: bash Not tainted 4.13.0-25-generic 
#29-Ubuntu
  [  240.305886] task: c000ff904500 task.stack: c001f2d7c000
  [  240.305979] NIP: c0792f88 LR: c0793eb8 CTR: 
c0792f60
  [  240.306087] REGS: c001f2d7f9f0 TRAP: 0300   Not tainted  
(4.13.0-25-generic)
  [  240.306195] MSR: 80009033 
  [  240.306207]   CR: 2842  XER: 2004
  [  240.306338] CFAR: c0793eb4 DAR:  DSISR: 4200 
SOFTE: 1
  [  240.306338] GPR00: c0793eb8 c001f2d7fc70 c15f6200 
0063
  [  240.306338] GPR04: c001feeeade8 c001fef02068 6967676572206120 
63726173680d0a72
  [  240.306338] GPR08: 0007 0001  

  [  240.306338] GPR12: c0792f60 c7ac7e00 10180df8 
10189e30
  [  240.306338] GPR16: 10189ea8 10151210 1018bd58 
1018de48
  [  240.306338] GPR20: 28bc0268 0001 10164590 
10163bb0
  [  240.306338] GPR24: 7fffdcb37d34 7fffdcb37d30 c14fa770 
0002
  [  240.306338] GPR28: 0063 0007 c14824f4 
c14fab10
  [  240.307346] NIP [c0792f88] sysrq_handle_crash+0x28/0x30
  [  240.307474] LR [c0793eb8] __handle_sysrq+0xf8/0x2b0
  [  240.307553] Call Trace:
  [  240.307594] [c001f2d7fc70] [c0793e98] 
__handle_sysrq+0xd8/0x2b0 (unreliable)
  [  240.307715] [c001f2d7fd10] [c07946b4] 
write_sysrq_trigger+0x64/0x90
  [  240.307850] [c001f2d7fd40] [c044fb28] proc_reg_write+0x88/0xd0
  [  240.307951] [c001f2d7fd70] [c03a160c] __vfs_write+0x3c/0x70
  [  240.308049] [c001f2d7fd90] [c03a3248] vfs_write+0xd8/0x220
  [  240.308149] [c001f2d7fde0] [c03a50c8] SyS_write+0x68/0x110
  [  240.308248] [c001f2d7fe30] [c000b184] system_call+0x58/0x6c
  [  240.308340] Instruction dump:
  [  240.308400] 4bfff9f1 4bfffe50 3c4c00e6 384232a0 7c0802a6 6000 3921 
3d42001d
  [  240.308522]

[Kernel-packages] [Bug 1745119] Re: 4.13.0-31 hibernate doesn't work

If you don't have 4.13.0-21 still installed, you can download it from:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/13870500

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

Title:
  4.13.0-31 hibernate doesn't work

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

Bug description:
  Hibernate process seems work and laptop (acer aspire v5-571G) shuts down
  But then laptop doesn't turn on. Blank screen and you must to force shut down 
with power button.
  You must start system with another kernel.

  I had the same problem with 4.13.0-26

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

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

[Kernel-packages] [Bug 1745119] Re: 4.13.0-31 hibernate doesn't work

Can you boot back into 4.13.0-21 and see if this bug still exists?

** Tags added: artful kernel-da-key pti

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

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

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

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

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

Title:
  4.13.0-31 hibernate doesn't work

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

Bug description:
  Hibernate process seems work and laptop (acer aspire v5-571G) shuts down
  But then laptop doesn't turn on. Blank screen and you must to force shut down 
with power button.
  You must start system with another kernel.

  I had the same problem with 4.13.0-26

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

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

[Kernel-packages] [Bug 1745123] Re: Elasticsearch 2.4.6 cause a Oops: 0010 [#37] SMP NOPTI

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

** Tags added: kernel-da-key pti

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

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

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

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

Title:
  Elasticsearch 2.4.6 cause a Oops: 0010 [#37] SMP NOPTI

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

Bug description:
  Elasticsearch 2.4.6 can't start since new kernel upgrade
  (4.13.0-31-generic #34~16.04.1-Ubuntu)

  Kernel log contains :

  [ 4308.595429] Oops: 0010 [#37] SMP NOPTI
  [ 4308.595430] Modules linked in: btrfs xor raid6_pq ufs qnx4 hfsplus hfs 
minix ntfs msdos jfs xfs libcrc32c bnep pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) bluetooth ecdh_generic binfmt_misc nls_iso8859_1 
snd_hda_codec_hdmi edac_mce_amd snd_hda_codec_realtek snd_hda_codec_generic 
snd_hda_intel eeepc_wmi kvm_amd asus_wmi snd_hda_codec sparse_keymap 
snd_hda_core video wmi_bmof kvm input_leds joydev snd_hwdep snd_pcm irqbypass 
crct10dif_pclmul snd_seq_midi crc32_pclmul snd_seq_midi_event 
ghash_clmulni_intel snd_rawmidi pcbc nvidia_uvm(POE) snd_seq aesni_intel 
snd_seq_device snd_timer snd aes_x86_64 crypto_simd soundcore ccp glue_helper 
cryptd shpchp i2c_piix4 8250_dw wmi mac_hid parport_pc ppdev lp parport autofs4 
hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE)
  [ 4308.595462]  drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
drm r8169 ahci mii libahci gpio_amdpt gpio_generic
  [ 4308.595468] CPU: 0 PID: 9314 Comm: java Tainted: P  DOE   
4.13.0-31-generic #34~16.04.1-Ubuntu
  [ 4308.595470] Hardware name: System manufacturer System Product Name/PRIME 
B350M-A, BIOS 0502 02/24/2017
  [ 4308.595471] task: 8dfa07b945c0 task.stack: b2b6033f4000
  [ 4308.595472] RIP: 0010:0x6987877
  [ 4308.595473] RSP: 0018:b2b6033f7f50 EFLAGS: 00010202
  [ 4308.595474] RAX: 03e7 RBX:  RCX: 
7f20e3d314d9
  [ 4308.595475] RDX: 7f20dc6686c0 RSI: 4d73aa93 RDI: 

  [ 4308.595476] RBP:  R08: 7f20e319caa4 R09: 
000c
  [ 4308.595477] R10: 06987877 R11: 8dfa07b945c0 R12: 

  [ 4308.595478] R13:  R14:  R15: 

  [ 4308.595479] FS:  7f20e4823700() GS:8dfac660() 
knlGS:
  [ 4308.595480] CS:  0010 DS:  ES:  CR0: 80050033
  [ 4308.595481] CR2: 06987877 CR3: 0003b723e000 CR4: 
003406f0
  [ 4308.595482] Call Trace:
  [ 4308.595487]  ? entry_SYSCALL_64_fastpath+0x33/0xa3
  [ 4308.595489] Code:  Bad RIP value.
  [ 4308.595490] RIP: 0x6987877 RSP: b2b6033f7f50
  [ 4308.595491] CR2: 06987877
  [ 4308.595493] ---[ end trace ba92d9f3b2090708 ]---

  
  It related to new kernel update, it work when starting with an older kernel.

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

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

[Kernel-packages] [Bug 1745130] Re: Support rfkill-any led trigger for Fujitsu u727

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

** Package changed: linux-lts-xenial (Ubuntu) => linux (Ubuntu)

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

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

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

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

Title:
  Support rfkill-any led trigger for Fujitsu u727

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

Bug description:
  I got new HW from our supplier, which is the Fujitsu u7x7 laptop series based 
on Skylake hardware.
  It has a single rfkill button and a single LED for wlan and bluetooth. Both 
device driver currently provide a single rfkill trigger, so the led could just 
be assigned to one. As a result the upstream kernel got a new "rfkill-any" led 
trigger to correctly handle the led with multiple rfkill devices. That was 
added by one of the fujitsu-laptop maintainers and the driver sets it as the 
default trigger.

  commit 9b8e34e211b15af429b72388a8f2b3b1823d172e
  Author: Michał Kępień 
  Date:   Fri Jan 6 07:07:47 2017 +0100

  rfkill: Add rfkill-any LED trigger

  Normally I would simply patch the affected modules using DKMS, like the 
i915_bpo driver, fujitsu-laptop and snd_hda_codec_realtek to support the HW 
without messing with the kernel packages.
  I'm currently waiting for some reviews, like 
https://www.spinics.net/lists/platform-driver-x86/msg14606.html

  But the rfkill support is compiled in, so I can't patch it using DKMS.

  So my first proposed fix would be to include a backport of this patch.
  Alternatively rfkill can be compiled as a module, so I can patch it
  and provide an updated module.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.4.0-111-generic 4.4.0-111.134~14.04.1
  ProcVersionSignature: Ubuntu 4.4.0-111.134~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-111-generic i686
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: i386
  Date: Wed Jan 24 10:48:28 2018
  SourcePackage: linux-lts-xenial
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1745167] Re: package linux-headers-3.13.0-141 (not installed) failed to install/upgrade: no se pudo crear `/usr/src/linux-headers-3.13.0-141/arch/score/include/asm/setup.h.dpkg-

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"


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

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

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

Title:
  package linux-headers-3.13.0-141 (not installed) failed to
  install/upgrade: no se pudo crear `/usr/src/linux-
  headers-3.13.0-141/arch/score/include/asm/setup.h.dpkg-new' (mientras
  se procesaba `./usr/src/linux-
  headers-3.13.0-141/arch/score/include/asm/setup.h'): No queda espacio
  en el dispositivo

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm not english and my write is so little bit, but my computer say
  about linux is no actualy

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-headers-3.13.0-141 (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-139.188-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-139-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vicente1622 F pulseaudio
   /dev/snd/controlC0:  vicente1622 F pulseaudio
  Date: Tue Jan 23 18:07:22 2018
  ErrorMessage: no se pudo crear 
`/usr/src/linux-headers-3.13.0-141/arch/score/include/asm/setup.h.dpkg-new' 
(mientras se procesaba 
`./usr/src/linux-headers-3.13.0-141/arch/score/include/asm/setup.h'): No queda 
espacio en el dispositivo
  HibernationDevice: RESUME=UUID=39e2d8b7-1cad-4a98-a894-b5325c0b3c17
  InstallationDate: Installed on 2014-05-28 (1337 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: TOSHIBA SATELLITE C50D-A-13P
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-139-generic 
root=UUID=886c5907-733f-48a7-9ace-24ddbc349eab 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: grub-pc 2.02~beta2-9ubuntu1.14
  SourcePackage: linux
  StagingDrivers: keucr
  Title: package linux-headers-3.13.0-141 (not installed) failed to 
install/upgrade: no se pudo crear 
`/usr/src/linux-headers-3.13.0-141/arch/score/include/asm/setup.h.dpkg-new' 
(mientras se procesaba 
`./usr/src/linux-headers-3.13.0-141/arch/score/include/asm/setup.h'): No queda 
espacio en el dispositivo
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: PT10AN
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.20:bd08/30/2013:svnTOSHIBA:pnSATELLITEC50D-A-13P:pvrPSCGWE-02T014CE:rvnAMD:rnPT10AN:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: SATELLITE C50D-A-13P
  dmi.product.version: PSCGWE-02T014CE
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1745151] Re: R9 270

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

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.15 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.15-rc9


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

Title:
  R9 270

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  this VGA is not being recognized by the kernel.

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

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

[Kernel-packages] [Bug 1724120] Re: Ubuntu 16.04.3 - call traces occurs when memory-hotplug test is run with 16Gb hugepages configured

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

Thanks for the update.  I'll mark this bug as a duplicate of bug
1706247, since the fixes for that bug are the same for this bug.

We can look at the traces for the new bug in that bug report.

** This bug has been marked a duplicate of bug 1706247
   Add support for 16g huge pages on Ubuntu 16.04.2 PowerNV

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

Title:
  Ubuntu 16.04.3 - call traces occurs when memory-hotplug test is run
  with 16Gb hugepages configured

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress

Bug description:
  Issue:

  Call traces occurs when memory-hotplug script is run with 16Gb
  hugepages configured.

  Environment:
  ppc64le PowerVM Lpar

  root@ltctuleta-lp1:~# uname -r
  4.4.0-34-generic

  root@ltctuleta-lp1:~# cat /proc/meminfo | grep -i huge
  AnonHugePages: 0 kB
  HugePages_Total:   2
  HugePages_Free:2
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   16777216 kB

  root@ltctuleta-lp1:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:85G 32G 52G 16M193M 
52G
  Swap:   43G  0B 43G

  Steps to reproduce:
  1 - Download kernel source and enter to the directory- 
tools/testing/selftests/memory-hotplug/
  2 - Run  mem-on-off-test.sh script in it.

  System gives call traces like:

  offline_memory_expect_success 639: unexpected fail
  online-offline 668
  [   57.552964] Unable to handle kernel paging request for data at address 
0x0028
  [   57.552977] Faulting instruction address: 0xc029bc04
  [   57.552987] Oops: Kernel access of bad area, sig: 11 [#1]
  [   57.552992] SMP NR_CPUS=2048 NUMA pSeries
  [   57.553002] Modules linked in: btrfs xor raid6_pq pseries_rng sunrpc 
autofs4 ses enclosure nouveau bnx2x i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops drm vxlan ip6_udp_tunnel ipr udp_tunnel 
rtc_generic mdio libcrc32c
  [   57.553050] CPU: 44 PID: 6518 Comm: mem-on-off-test Not tainted 
4.4.0-34-generic #53-Ubuntu
  [   57.553059] task: c0072773c8e0 ti: c0072778 task.ti: 
c0072778
  [   57.553067] NIP: c029bc04 LR: c029bbdc CTR: 
c01107f0
  [   57.553076] REGS: c00727783770 TRAP: 0300   Not tainted  
(4.4.0-34-generic)
  [   57.553083] MSR: 80019033   CR: 24242882  
XER: 0002
  [   57.553104] CFAR: c0008468 DAR: 0028 DSISR: 4000 
SOFTE: 1 
  GPR00: c029bbdc c007277839f0 c15b5d00  
  GPR04: 0029d000 0800  fa01 
  GPR08: fa700020 0008 c185e270 c00e7e50 
  GPR12: 2200 ce6ea200 0029d000 2200 
  GPR16: 1000 c15e2200 0a70  
  GPR20: 0001 0100 0200 c15f16d0 
  GPR24: c1876510  0001 c1872a00 
  GPR28: 0029d000 f000 fa70 0029c000 
  [   57.553211] NIP [c029bc04] dissolve_free_huge_pages+0x154/0x220
  [   57.553219] LR [c029bbdc] dissolve_free_huge_pages+0x12c/0x220
  [   57.553226] Call Trace:
  [   57.553231] [c007277839f0] [c029bbdc] 
dissolve_free_huge_pages+0x12c/0x220 (unreliable)
  [   57.553244] [c00727783a80] [c02dcbc8] 
__offline_pages.constprop.6+0x3f8/0x900
  [   57.553254] [c00727783bd0] [c06fbb38] 
memory_subsys_offline+0xa8/0x110
  [   57.553265] [c00727783c00] [c06d6424] 
device_offline+0x104/0x140
  [   57.553274] [c00727783c40] [c06fba80] 
store_mem_state+0x180/0x190
  [   57.553283] [c00727783c80] [c06d1e58] dev_attr_store+0x68/0xa0
  [   57.553293] [c00727783cc0] [c0398110] sysfs_kf_write+0x80/0xb0
  [   57.553302] [c00727783d00] [c0397028] 
kernfs_fop_write+0x188/0x200
  [   57.553312] [c00727783d50] [c02e190c] __vfs_write+0x6c/0xe0
  [   57.553321] [c00727783d90] [c02e2640] vfs_write+0xc0/0x230
  [   57.553329] [c00727783de0] [c02e367c] SyS_write+0x6c/0x110
  [   57.553339] [c00727783e30] [c0009204] system_call+0x38/0xb4
  [   57.553346] Instruction dump:
  [   57.553351] 7e831836 4bfff991 e91e0028 e8fe0020 7d32e82a f9070008 f8e8 
fabe0020 
  [   57.553366] fade0028 79294620 79291764 7d234a14  3908 
f9030028 81091458 
  [   57.553383] ---[ end trace 617f7bdd75bcfc10 ]---
  [   57.557133] 
  Segmentation fault

  The following commit IDs

[Kernel-packages] [Bug 1729391] Re: Trackpad stops responding after suspend

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

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

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

Title:
  Trackpad stops responding after suspend

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

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, the trackpad
  stops working after suspend (it actually works for a few seconds, then
  doesn't react). I can still use the touch screen.

  Please tell me which log-files to upload.

  Thanks

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

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

[Kernel-packages] [Bug 1257547] [NEW] [bcm5974] Apple touchpad fails to respond, dmesg contains multiple mesages of form: bcm5974: bad trackpad package, length: 8

You have been subscribed to a public bug:

Have Apple Macbook pro 8,1. With Trusty devel, occasionally (i.e. twice in the 
last 3 weeks) my trackpad completely stopped functioning. From then on, dmesg 
is full of these messages:
bcm5974: bad trackpad package, length: 8

WORKAROUND: Remove and re-load bcm5974.

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


** Tags: apport-collected artful ubuntu
-- 
[bcm5974] Apple touchpad fails to respond, dmesg contains multiple mesages of 
form: bcm5974: bad trackpad package, length: 8
https://bugs.launchpad.net/bugs/1257547
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 1745130] [NEW] Support rfkill-any led trigger for Fujitsu u727

You have been subscribed to a public bug:

I got new HW from our supplier, which is the Fujitsu u7x7 laptop series based 
on Skylake hardware.
It has a single rfkill button and a single LED for wlan and bluetooth. Both 
device driver currently provide a single rfkill trigger, so the led could just 
be assigned to one. As a result the upstream kernel got a new "rfkill-any" led 
trigger to correctly handle the led with multiple rfkill devices. That was 
added by one of the fujitsu-laptop maintainers and the driver sets it as the 
default trigger.

commit 9b8e34e211b15af429b72388a8f2b3b1823d172e
Author: Michał Kępień 
Date:   Fri Jan 6 07:07:47 2017 +0100

rfkill: Add rfkill-any LED trigger

Normally I would simply patch the affected modules using DKMS, like the 
i915_bpo driver, fujitsu-laptop and snd_hda_codec_realtek to support the HW 
without messing with the kernel packages.
I'm currently waiting for some reviews, like 
https://www.spinics.net/lists/platform-driver-x86/msg14606.html

But the rfkill support is compiled in, so I can't patch it using DKMS.

So my first proposed fix would be to include a backport of this patch.
Alternatively rfkill can be compiled as a module, so I can patch it and
provide an updated module.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-4.4.0-111-generic 4.4.0-111.134~14.04.1
ProcVersionSignature: Ubuntu 4.4.0-111.134~14.04.1-generic 4.4.98
Uname: Linux 4.4.0-111-generic i686
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: i386
Date: Wed Jan 24 10:48:28 2018
SourcePackage: linux-lts-xenial
UpgradeStatus: No upgrade log present (probably fresh install)

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

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


** Tags: apport-bug i386 patch third-party-packages trusty
-- 
Support rfkill-any led trigger for Fujitsu u727
https://bugs.launchpad.net/bugs/1745130
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 1742626] Re: Unstable LTS kernel 4.13

2018-01-24 Thread Josep Pujadas-Jubany

It seems to be related with
https://bugzilla.kernel.org/show_bug.cgi?id=194945#c73

I can see also bad interrupts for chv-gpio

No more IRQ errors with kernel 4.14.15-041415-generic

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14.15/


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

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

Title:
  Unstable LTS kernel 4.13

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  At job, after upgrading many Lubuntu 16.04 LTS 64 bit systems from
  4.10 to 4.13 they are (most of them) unstable.

  Acer TravelMate B117-M (SSD disk) freeze at boot or show errors at
  startup such:

  unexpected irq trap at vector

  similar to https://forum.manjaro.org/t/manjaro-kernel-4-13-unexpected-
  irq-trap-at-vector-e3-error/30942

  At home (no signed kernel, old machine) my VirtualBox freezes also the
  machine, as explained at
  https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1736116/comments/14

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

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

[Kernel-packages] [Bug 1743027] Re: error loading realtime clock since upgrading to 17.10

2018-01-24 Thread Peter Milley

Hi Joseph,

As requested, I booted and tested the 4.15.0-041500rc9-generic kernel,
and the problem still exists.  Let me know if you have any other
questions.

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

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

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

Title:
  error loading realtime clock since upgrading to 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (originally asked over at askubuntu.com, but is still unresolved:
  https://askubuntu.com/questions/971349/problem-with-real-time-clock-
  since-upgrading-to-ubuntu-17-10)

  I recently upgraded from Ubuntu 17.04 to Ubuntu 17.10 using the
  software update process. The update completed without any errors, and
  Ubuntu 17.10 is now running without any major issues.

  However, I was running a script previously that uses rtcwake which has
  since stopped working. The script automatically hibernates my laptop
  after a set period of time in sleep mode, and was working perfectly in
  Ubuntu 17.04.

  In the process of troubleshooting, I discovered that the problem was
  with rtcwake which is complaining about /dev/rtc0 missing.

  Here is output from a sample rtcwake command:

  peter@haven:~$ rtcwake -m no -s 1300
  rtcwake: assuming RTC uses UTC ...
  rtcwake: /dev/rtc0: unable to find device: No such file or directory

  I verified that in fact, that directory is missing. Since this was
  working prior to the upgrade, I have to assume that it was there
  previously, but I don't know for sure.

  In researching the error, I found some suggestions to get further
  information with timedatectl and hwclock, so here are the results from
  those commands as well.

  Output of timedatectl:

  peter@haven:~$ timedatectl
Local time: Fri 2017-10-27 19:06:26 EDT
Universal time: Fri 2017-10-27 23:06:26 UTC
  RTC time: n/a
 Time zone: America/New_York (EDT, -0400)
   Network time on: yes
  NTP synchronized: yes
   RTC in local TZ: no

  Output of hwclock --debug:

  peter@haven:~$ sudo hwclock --debug
  [sudo] password for peter: 
  hwclock from util-linux 2.30.1
  Trying to open: /dev/rtc0
  Trying to open: /dev/rtc
  Trying to open: /dev/misc/rtc
  No usable clock interface found.
  hwclock: Cannot access the Hardware Clock via any known method.

  UPDATE

  When I boot with my old kernel, 4.10.0-37-generic the real-time clock
  works fine.

  I get the following RTC messages in dmesg when I boot the
  4.13.0-16-generic kernel:

  peter@haven:~$ dmesg | grep -i rtc
  [0.089393] RTC time: 17:03:55, date: 11/01/17
  [1.238784] rtc_cmos 00:01: RTC can wake from S4
  [1.238794] rtc_cmos: probe of 00:01 failed with error -16
  [1.295459] hctosys: unable to open rtc device (rtc0)

  UPDATE #2

  Well, I was starting to believe that I had a hardware issue, since
  discovering I was unable to save changes to my BIOS and could not boot
  from USB. As it turns out, my laptop was bitten by this bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147 causing
  my BIOS to be locked in a read-only state.

  Once I resolved the BIOS issue, and fixed the USB boot problem, I did
  a live boot of Ubuntu 17.10. The issue with my real time clock still
  exists under this clean boot scenario, yet when I boot other distros,
  like Linux Mint 18.3 and the real time clock works fine. I feel this
  definitely has something to do with the Ubuntu install, perhaps even a
  kernel bug.

  UPDATE #3

  More evidence to suggest this is a kernel bug: I live-booted a copy of
  Antergos Linux, which was using the Arch kernel 4.14.12-1-ARCH and it
  exhibited the same problem with the real time clock as Ubuntu 17.10.
  In addition, I confirmed that the Linux Mint version I booted earlier
  (see Update #2) was on the Ubuntu kernel 4.10.0-38-generic.

  So, I suspect that sometime between kernels 4.10 and 4.13 this bug was 
introduced.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peter  1832 F pulseaudio
   /dev/snd/controlC1:  peter  1832 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=a602efe1-467d-4ac4-806f-1b931c91cdad
  InstallationDate: Installed on 2017-04-05 (292 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 20354
  Package: linux (not installed)
  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.13.0-25-generic.efi.signed 
root=UUID=fa5454aa-9072-475d-b515-acd51a6166cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13

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

This change was made by a bot.

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

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

Title:
  package linux-headers-3.13.0-141 (not installed) failed to
  install/upgrade: no se pudo crear `/usr/src/linux-
  headers-3.13.0-141/arch/score/include/asm/setup.h.dpkg-new' (mientras
  se procesaba `./usr/src/linux-
  headers-3.13.0-141/arch/score/include/asm/setup.h'): No queda espacio
  en el dispositivo

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm not english and my write is so little bit, but my computer say
  about linux is no actualy

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-headers-3.13.0-141 (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-139.188-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-139-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vicente1622 F pulseaudio
   /dev/snd/controlC0:  vicente1622 F pulseaudio
  Date: Tue Jan 23 18:07:22 2018
  ErrorMessage: no se pudo crear 
`/usr/src/linux-headers-3.13.0-141/arch/score/include/asm/setup.h.dpkg-new' 
(mientras se procesaba 
`./usr/src/linux-headers-3.13.0-141/arch/score/include/asm/setup.h'): No queda 
espacio en el dispositivo
  HibernationDevice: RESUME=UUID=39e2d8b7-1cad-4a98-a894-b5325c0b3c17
  InstallationDate: Installed on 2014-05-28 (1337 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: TOSHIBA SATELLITE C50D-A-13P
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-139-generic 
root=UUID=886c5907-733f-48a7-9ace-24ddbc349eab 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: grub-pc 2.02~beta2-9ubuntu1.14
  SourcePackage: linux
  StagingDrivers: keucr
  Title: package linux-headers-3.13.0-141 (not installed) failed to 
install/upgrade: no se pudo crear 
`/usr/src/linux-headers-3.13.0-141/arch/score/include/asm/setup.h.dpkg-new' 
(mientras se procesaba 
`./usr/src/linux-headers-3.13.0-141/arch/score/include/asm/setup.h'): No queda 
espacio en el dispositivo
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: PT10AN
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.20:bd08/30/2013:svnTOSHIBA:pnSATELLITEC50D-A-13P:pvrPSCGWE-02T014CE:rvnAMD:rnPT10AN:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: SATELLITE C50D-A-13P
  dmi.product.version: PSCGWE-02T014CE
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1745167] [NEW] package linux-headers-3.13.0-141 (not installed) failed to install/upgrade: no se pudo crear `/usr/src/linux-headers-3.13.0-141/arch/score/include/asm/setup.h.dpk

2018-01-24 Thread vicente juan

Public bug reported:

I'm not english and my write is so little bit, but my computer say about
linux is no actualy

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-headers-3.13.0-141 (not installed)
ProcVersionSignature: Ubuntu 3.13.0-139.188-generic 3.13.11-ckt39
Uname: Linux 3.13.0-139-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  vicente1622 F pulseaudio
 /dev/snd/controlC0:  vicente1622 F pulseaudio
Date: Tue Jan 23 18:07:22 2018
ErrorMessage: no se pudo crear 
`/usr/src/linux-headers-3.13.0-141/arch/score/include/asm/setup.h.dpkg-new' 
(mientras se procesaba 
`./usr/src/linux-headers-3.13.0-141/arch/score/include/asm/setup.h'): No queda 
espacio en el dispositivo
HibernationDevice: RESUME=UUID=39e2d8b7-1cad-4a98-a894-b5325c0b3c17
InstallationDate: Installed on 2014-05-28 (1337 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: TOSHIBA SATELLITE C50D-A-13P
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-139-generic 
root=UUID=886c5907-733f-48a7-9ace-24ddbc349eab 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: grub-pc 2.02~beta2-9ubuntu1.14
SourcePackage: linux
StagingDrivers: keucr
Title: package linux-headers-3.13.0-141 (not installed) failed to 
install/upgrade: no se pudo crear 
`/usr/src/linux-headers-3.13.0-141/arch/score/include/asm/setup.h.dpkg-new' 
(mientras se procesaba 
`./usr/src/linux-headers-3.13.0-141/arch/score/include/asm/setup.h'): No queda 
espacio en el dispositivo
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/30/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.20
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: PT10AN
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.20:bd08/30/2013:svnTOSHIBA:pnSATELLITEC50D-A-13P:pvrPSCGWE-02T014CE:rvnAMD:rnPT10AN:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: SATELLITE C50D-A-13P
dmi.product.version: PSCGWE-02T014CE
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-package staging trusty

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

Title:
  package linux-headers-3.13.0-141 (not installed) failed to
  install/upgrade: no se pudo crear `/usr/src/linux-
  headers-3.13.0-141/arch/score/include/asm/setup.h.dpkg-new' (mientras
  se procesaba `./usr/src/linux-
  headers-3.13.0-141/arch/score/include/asm/setup.h'): No queda espacio
  en el dispositivo

Status in linux package in Ubuntu:
  New

Bug description:
  I'm not english and my write is so little bit, but my computer say
  about linux is no actualy

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-headers-3.13.0-141 (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-139.188-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-139-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vicente1622 F pulseaudio
   /dev/snd/controlC0:  vicente1622 F pulseaudio
  Date: Tue Jan 23 18:07:22 2018
  ErrorMessage: no se pudo crear 
`/usr/src/linux-headers-3.13.0-141/arch/score/include/asm/setup.h.dpkg-new' 
(mientras se procesaba 
`./usr/src/linux-headers-3.13.0-141/arch/score/include/asm/setup.h'): No queda 
espacio en el dispositivo
  HibernationDevice: RESUME=UUID=39e2d8b7-1cad-4a98-a894-b5325c0b3c17
  InstallationDate: Installed on 2014-05-28 (1337 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: TOSHIBA SATELLITE C50D-A-13P
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-139-generic 
root=UUID=886c5907-733f-48a7-9ace-24ddbc349eab 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: grub-pc 2.02~beta2-9ubuntu1.14
  SourcePackage: linux
  StagingDrivers: keucr
  Title: package linux-headers-3.13.0-141 (not installed) failed to 
install/upgrade: no se pudo crear 
`/usr/src/linux-headers-3.13.0-141/arch/score/include/asm/setup.h.dpkg-new' 
(mientras se procesaba 
`./usr/src/linux-headers-3.13.0-141/arch/score/include/asm/setup.h'): No queda 
espacio en el dispositivo
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date:

[Kernel-packages] [Bug 1743279] Re: QCA6174 stops working on newer kernels after second group rekeying

2018-01-24 Thread Seth Forshee

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

** Changed in: linux-firmware (Ubuntu Artful)
   Status: Confirmed => Fix Committed

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

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

Title:
  QCA6174 stops working on newer kernels after second group rekeying

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Artful:
  Fix Committed

Bug description:
  After upgrading to the 4.13 kernel on Ubuntu 16.04.3, I've noticed my
  WiFi would stop working after every 20 minutes or so. The problem
  initially seems related to some DNS services crashing because of what
  happend in browsers and other software that usually rely on DNS but
  I've noticed I couldn't ping my router and other local devices for
  which I knew the IP addresses. The connection is still presented as
  being connected, but it just doesn't work.

  After googling a lot, I came across this question on askubuntu.com

  https://askubuntu.com/questions/967355/wifi-unstable-
  after-17-10-update

  Which led me to this bug report on Debian's bug tracker:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879184

  Which led me to this bug in upstream:

  http://lists.infradead.org/pipermail/ath10k/2017-September/010088.html

  I've tested the proposed fixes myself and I can confirm they work.

  What causes the WiFi to stop working is a bug related to the group
  rekeying routines.

  It seems it only happens in >4.12 kernels, hence why I've only had
  problems after 4.13 was pushed as the current rolling HWE kernel for
  16.04.3.

  kvalo made the fix available in version WLAN.RM.4.4.1-00051-QCARMSWP-1
  of the firmware-6.bin file, which is the current one present in
  upstream.

  Updating the firmware-6.bin (and board-2.bin, optionally) to any
  version equal or later than that fixes the issue completely.

  -

  SRU Justification:
  [Impact]
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter, available in 
numerous laptops, including ones that ship with Ubuntu 16.04 pre-installed, 
silently stops working after the second group rekeying, which is usually few 
minutes after the user has connected to a WiFi network. The connection status 
remains unchanged but there's no connectivity at all. This effectively 
disconnects the user without notifying it of what's occurred.

  Additionally, this happens for the only HWE kernel that's been patched
  against the recent Meltdown vulnerability, leaving the user without
  the option of using a recent kernel and a secure kernel at the same
  time.

  [Test Case]
  After applying the required firmwares, check if the connectivity is 
unaffected after the second group rekeying, which can be checked with

  $ cat /var/log/syslog | grep wpa_.*rekeying

  [How to fix it]

  Update the firmware-6.bin file to version
  WLAN.RM.4.4.1-00051-QCARMSWP-1 or later.

  [Regression Potential]
  The new firmware overwrites the old one, but since it's been in upstream 
since October 2017, it should be good.

  -

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  linux-firmware:
    Instalado: 1.157.14
    Candidato: 1.157.14
    Tabela de versão:
   *** 1.157.14 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   1.157 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages

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

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

[Kernel-packages] [Bug 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)

2018-01-24 Thread Luis Alvarado

Hi Daniel, thank you. How can I mark this ticket as fixed. It has been
about 10 days. No problems whatsoever. I actually lost connection
yesterday but then noticed it was because I did not charge the headset
for the last 2 days. Even with very low power, I was still able to
finish a conversation. Thank you for the help and if you would like as a
gift, I could buy one of this in Amazon and send it to you buddy. They
are pretty awesome. Big hugs friend and think positive.

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

Title:
Logitech G930 drops connection and reconnects in 17.10 (But not in
17.04)

Status in linux package in Ubuntu:
Incomplete
Status in pulseaudio package in Ubuntu:
Incomplete

Bug description:
Every so many seconds / minutes the Wireless headset Logitech G930
simply drops connection. It always reconnects but when doing a
recording, a meeting, listening to music or a movie it simply drops
the connection for 1 to 3 second. This happens several times an hour.
If it helps, it was not happening in 17.04 (Never happened in more
than 200+ hours of using the headset).

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: cyrex 1288 F pulseaudio
/dev/snd/controlC2: cyrex 1288 F pulseaudio
/dev/snd/controlC0: cyrex 1288 F pulseaudio
Date: Sat Oct 21 17:55:42 2017
InstallationDate: Installed on 2017-10-19 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
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.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/30/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3504
dmi.board.asset.tag: Default string
dmi.board.name: MAXIMUS VIII HERO ALPHA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
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/1725863/+subscriptions

[Kernel-packages] [Bug 1742764] Re: 4.13.0-26-generic touchpad two finger scroll & tap to click doesn't work after upgrade

2018-01-24 Thread Rubén

Fixed on 4.15-rc9

** Tags added: kernel-fixed-upstream

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

Title:
   4.13.0-26-generic touchpad two finger scroll & tap to click doesn't
  work after upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  when I use kernel version 4.10.0-42-generic touchpad work as requested
  (two finger scroll & tap to click activated).

  When I use Kernel 4.13.0-26-generic which system ask me to upgrade on,
  two finger scroll & tap to click activated but touchpad doesn't work
  with.

  GOOD:
  4.10.0-42-generic
  xinput
  kam@kam-Flex-3-1580:~$ xinput 
  ⎡ Virtual core pointerid=2[master 
pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  
pointer  (2)]
  ⎜   ↳ AlpsPS/2 ALPS GlidePointid=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master 
keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7
[slave  keyboard (3)]
  ↳ Video Bus   id=8
[slave  keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Lenovo EasyCamera   id=10   [slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  kam@kam-Flex-3-1580:~$ 

  
  ===
  BAD:
  4.13.0-26-generic
  xinput

  xxx@xxx-Flex-3-1580:~$ xinput 
  ⎡ Virtual core pointerid=2[master 
pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  
pointer  (2)]
  ⎜   ↳ AlpsPS/2 ALPS GlidePointid=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master 
keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7
[slave  keyboard (3)]
  ↳ Video Bus   id=8
[slave  keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Lenovo EasyCamera: Lenovo EasyC id=10   [slave  keyboard (3)]
  ↳ Ideapad extra buttons   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ PEAQ WMI hotkeysid=15   [slave  
keyboard (3)]
  xxx@xxx-Flex-3-1580:~$
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kam2605 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0ab1aa77-c4e5-44b4-8551-2cb8303dd3f2
  InstallationDate: Installed on 2017-06-21 (204 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: LENOVO 80R4
  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.13.0-26-generic.efi.signed 
root=UUID=5a4a3b87-22ad-46cb-b313-e45f053e558e ro
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  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.13.0-26-generic N/A
   linux-backports-modules-4.13.0-26-generic  N/A
   linux-firmware 1.157.14
  Tags:  xenial
  Uname: Linux 4.13.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/10/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: D3CN25WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Flex 3-1580
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset

[Kernel-packages] [Bug 1724614] Re: [KVM] Lower the default for halt_poll_ns to 200000 ns

2018-01-24 Thread Victor Tapia

** Description changed:

  [Environment]
- 
- Reproducible <= 4.12 that means all our supported series + HWE
- (including edge).
  
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  
- Linux 4.10.0-33-generic #37~16.04.1-Ubuntu SMP Fri Aug 11 14:07:24 UTC
- 2017 x86_64 x86_64 x86_64 GNU/Linux
+ Linux porygon 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36 UTC
+ 2018 x86_64 x86_64 x86_64 GNU/Linux
  
  [Description]
  
  We've identified a constant high (~90%) system time load at the host level
  when a VCPU in a KVM guest remains or switches/resumes in/from halt/idle state
  in a constant frequency, usually for a slightly smaller time than the default 
polling
- period. 
+ period.
  
- The halt polling mechanism has the intention to reduce latency in the cases 
- on which the guest is quickly resumed saving a call to the scheduler. 
+ The halt polling mechanism has the intention to reduce latency in the cases
+ on which the guest is quickly resumed saving a call to the scheduler.
  
- We've performed some testing by adjusting the 
/sys/module/kvm/parameters/halt_poll_ns 
- value which defines the max time that should be spend polling before calling 
the 
- scheduler to allow it to run other tasks (which defaults to 40 ns in 
Ubuntu). 
+ We've performed some testing by adjusting the 
/sys/module/kvm/parameters/halt_poll_ns
+ value which defines the max time that should be spend polling before calling 
the
+ scheduler to allow it to run other tasks (which defaults to 40 ns in 
Ubuntu).
  
  With the default value the tests shows that the load remains nearly on 90% on 
a
- VCPU that has a single task in the run queue. 
+ VCPU that has a single task in the run queue.
  
  We've also tested altering the halt_poll_ns value to 20 ns and the results
  seems to drop the system time usage from 90% to ~25%.
  
- root@buneary:/home/ubuntu/trace# echo 20 > 
/sys/module/kvm/parameters/halt_poll_ns
- root@buneary:/home/ubuntu/trace# sudo mpstat 1 -P 6 5
- Linux 4.10.0-33-generic (buneary) 10/16/2017 _x86_64_ (56 CPU)
+ root@porygon:/home/ubuntu# echo 20 > 
/sys/module/kvm/parameters/halt_poll_ns
+ root@porygon:/home/ubuntu# mpstat 1 -P 6 5
+ Linux 4.4.0-112-generic (porygon) 01/24/2018  _x86_64_(64 CPU)
  
- 02:33:59 PM CPU %usr %nice %sys %iowait %irq %soft %steal %guest %gnice %idle
+ 02:06:08 PM  CPU  %usr  %nice  %sys %iowait  %irq   %soft  %steal  %guest  
%gnice   %idle
+ 02:06:09 PM6  0.00  0.00   4.85  0.000.000.000.00   16.50
0.00   78.64
  [...]
- 02:34:03 PM 6 4.04 0.00 24.24 0.00 0.00 0.00 0.00 12.12 0.00 59.60
- 02:34:04 PM 6 2.97 0.00 27.72 0.00 0.00 0.00 0.00 11.88 0.00 57.43
- Average: 6 2.45 0.00 25.97 0.00 0.00 0.00 0.00 12.07 0.00 59.51
+ Average:   6  0.00  0.00   4.26  0.000.000.000.00   17.83
0.00   77.91
  
- root@buneary:/home/ubuntu/trace# echo 40 > 
/sys/module/kvm/parameters/halt_poll_ns
- root@buneary:/home/ubuntu/trace# sudo mpstat 1 -P 6 5
- Linux 4.10.0-33-generic (buneary) 10/16/2017 _x86_64_ (56 CPU)
  
- 02:34:08 PM CPU %usr %nice %sys %iowait %irq %soft %steal %guest %gnice %idle
- 02:34:09 PM 6 1.94 0.00 92.23 0.00 0.00 0.00 0.00 3.88 0.00 1.94
+ root@porygon:/home/ubuntu# echo 40 > 
/sys/module/kvm/parameters/halt_poll_ns
+ root@porygon:/home/ubuntu# mpstat 1 -P 6 5
+ Linux 4.4.0-112-generic (porygon) 01/24/2018  _x86_64_(64 CPU)
+ 
+ 02:06:20 PM  CPU  %usr  %nice  %sys %iowait   %irq   %soft  %steal  %guest  
%gnice   %idle
+ 02:06:21 PM6  0.00  0.00   87.13  0.000.000.000.00   11.88
0.000.99
  [...]
- Average: 6 1.38 0.00 89.74 0.00 0.00 0.00 0.00 7.30 0.00 1.58
+ Average:   6  0.00  0.00   89.59  0.000.000.000.008.45
0.001.96
  
  [Reproducer]
  
  1) Configure a KVM guest with a single pinned VCPU.
  2) Run the following program (http://pastebin.ubuntu.com/25731919/) at the 
KVM guest.
  $ gcc test.c -lpthread -o test && ./test 250 0
  3) Run mpstat at the host on the pinned CPU and compare the stats
  $ sudo mpstat 1 -P 6 5
  
  [Fix]
  
  Change the halt polling max time to half of the current value.
  
  In some fio benchmarks, halt_poll_ns=40 caused CPU utilization to
  increase heavily even in cases where the performance improvement was
  small.  In particular, bandwidth divided by CPU usage was as much as
  60% lower.
  
  To some extent this is the expected effect of the patch, and the
  additional CPU utilization is only visible when running the
  benchmarks.  However, halving the threshold also halves the extra
  CPU utilization (from +30-130% to +20-70%) and has no negative
  effect on performance.
  
  Signed-off-by: Paolo Bonzini 
  
  *
  
https://github.com/torvalds/linux/commit/b401ee0b85a53e89739ff68a5b1a0667d664afc9

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

[Kernel-packages] [Bug 1744979] Re: grub_efi_secure_boot signal at the beginning of the boot process

2018-01-24 Thread csola48

How much should GRUB_DEFAULT be set to for example start 4.4.0-112 kernel 
automatically when booting?
Different descriptions do not give a clear answer to which "menuentry" counts 
and which one does not ...
https://pastebin.com/G23aHrMn and
https://pastebin.com/g4hr6Ltf

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

Title:
  grub_efi_secure_boot signal at the beginning of the boot process

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The previous kernel (4.4.0-109) was running without any problems, without 
triggering an error.
  After today's kernel update, the machine can not be started unless you select 
"run" the selected kernel from the advanced settings menu item.
  The first message always: grub_efi_secure_boot

  Ubuntu 4.4.0-112.135-generic 4.4.98
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  Intel® Core™ i5-3330 CPU @ 3.00GHz × 4 
  GeForce GT 630/PCIe/SSE2
  system 32 bit

  Please help... 
  I chose 16.04 LTS because I wanted to have a long, calm and safe use ...
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  csola481454 F pulseaudio
   /dev/snd/controlC2:  csola481454 F pulseaudio
   /dev/snd/controlC0:  csola481454 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=6c8c77a4-d4d3-4e31-a038-13930e1abfd0
  InstallationDate: Installed on 2016-11-08 (441 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=4cbb9ed4-c9ab-4ee3-8eb5-2473af0d2ae7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-112-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77-DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1738178] Re: ubuntu_ecryptfs tests failed on Xenial s390x instances

2018-01-24 Thread Colin Ian King

Fix sent to autotest tools, "[PATCH] UBUNTU: SAUCE: ubuntu_ecryptfs:
ensure mkfs.xfs works for all releases (LP:#1738178)".  Sam, do you mind
testing this for me?

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

Title:
  ubuntu_ecryptfs tests failed on Xenial s390x instances

Status in ecryptfs-utils package in Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  In the ubuntu_ecryptfs test suite, it constantly fail with 28 test
  cases on all s390x instances (zVM / zKVM / Ubuntu on LPAR) with Xenial
  kernel.

   miscdev-bad-count.sh.xfs 3 sec   Failed
    extend-file-random.sh.xfs   5 sec   Failed
    trunc-file.sh.xfs   3 sec   Failed
    directory-concurrent.sh.xfs 2 sec   Failed
    file-concurrent.sh.xfs  5 sec   Failed
    lp-994247.sh.xfs3 sec   Failed
    llseek.sh.xfs   4 sec   Failed
    lp-469664.sh.xfs5 sec   Failed
    lp-524919.sh.xfs5 sec   Failed
    lp-509180.sh.xfs6 sec   Failed
    lp-613873.sh.xfs11 sec  Failed
    lp-745836.sh.xfs10 sec  Failed
    lp-870326.sh.xfs6 sec   Failed
    lp-885744.sh.xfs9 sec   Failed
    lp-926292.sh.xfs9 sec   Failed
    inotify.sh.xfs  10 sec  Failed
    mmap-bmap.sh.xfs9 sec   Failed
    mmap-close.sh.xfs   10 sec  Failed
    mmap-dir.sh.xfs 9 sec   Failed
    read-dir.sh.xfs 6 sec   Failed
    setattr-flush-dirty.sh.xfs  5 sec   Failed
    inode-race-stat.sh.xfs  5 sec   Failed
    lp-911507.sh.xfs5 sec   Failed
    lp-561129.sh.xfs5 sec   Failed
    mknod.sh.xfs7 sec   Failed
    link.sh.xfs 3 sec   Failed
    xattr.sh.xfs5 sec   Failed
    namelen.sh.xfs  4 sec   Failed

  Tested with the upstream repo from lp:ecryptfs (revno 894)
  There is not much error message to see, these test cases just exit with 1

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-104-generic 4.4.0-104.127
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   [104616.551505] EXT4-fs (loop0): mounting ext3 file system using the ext4 
subsystem
   [104616.574291] EXT4-fs (loop0): mounted filesystem with ordered data mode. 
Opts: user_xattr,acl,commit=600,barrier=1,data=ordered
  Date: Thu Dec 14 05:33:55 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-104-generic N/A
   linux-backports-modules-4.4.0-104-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1745151

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

Title:
  R9 270

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  this VGA is not being recognized by the kernel.

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

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

[Kernel-packages] [Bug 1745151] [NEW] R9 270

2018-01-24 Thread BetoMaldonado

Public bug reported:

this VGA is not being recognized by the kernel.

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

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

Title:
  R9 270

Status in linux package in Ubuntu:
  New

Bug description:
  this VGA is not being recognized by the kernel.

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

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

[Kernel-packages] [Bug 1742474] Re: Bad return status for module build on kernel: 4.13.0-26-generic (i686)

2018-01-24 Thread Julian Andres Klode

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

** This bug has been marked a duplicate of bug 1724869
   ndiswrapper 1.60-3~ubuntu16.04.1 ADT test failure with linux-hwe-edge 
4.13.0-16.19~16.04.3

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

Title:
  Bad return status for module build on kernel: 4.13.0-26-generic (i686)

Status in linux package in Ubuntu:
  Confirmed
Status in ndiswrapper package in Ubuntu:
  New

Bug description:
  Distributor ID: LinuxMint
  Description: Linux Mint 18.3 Sylvia
  Release: 18.3
  Codename: sylvia
  Linux Asus-1000HE 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 
UTC 2017 i686 i686 i686 GNU/Linux

  Linux Mint 18.3 with HWE Kernel (sudo apt install --install-recommends
  linux-generic-hwe-16.04 xserver-xorg-hwe-16.04)

  I've upgraded linux kernel from 4.10.0-4.10.0-42.46~16.04.1 to 
4.13.0-26.29~16.04.2.
  I've got errors while upgrade kernel.
  And, After rebooting, my linux login screen has been broken.
  I cannot log in and my linux screen has gone black.
  Restroing kernel 4.10, then works well.

  run-parts: executing /etc/kernel/postinst.d/dkms 4.13.0-26-generic 
/boot/vmlinuz-4.13.0-26-generic
  Error! Bad return status for module build on kernel: 4.13.0-26-generic (i686)
  Consult /var/lib/dkms/ndiswrapper/1.60/build/make.log for more information.

  Belows are /var/lib/dkms/ndiswrapper/1.60/build/make.log.

  DKMS make.log for ndiswrapper-1.60 for kernel 4.13.0-26-generic (i686)
  2018. 01. 11. (목) 00:16:20 KST
  make: 디렉터리 '/usr/src/linux-headers-4.13.0-26-generic' 들어감
AR /var/lib/dkms/ndiswrapper/1.60/build/built-in.o
MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/crt_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/hal_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ndis_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/rtl_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/usb_exports.h
CC [M] /var/lib/dkms/ndiswrapper/1.60/build/crt.o
CC [M] /var/lib/dkms/ndiswrapper/1.60/build/hal.o
CC [M] /var/lib/dkms/ndiswrapper/1.60/build/iw_ndis.o
CC [M] /var/lib/dkms/ndiswrapper/1.60/build/loader.o
CC [M] /var/lib/dkms/ndiswrapper/1.60/build/ndis.o
  In file included from /var/lib/dkms/ndiswrapper/1.60/build/ndis.h:19:0,
   from /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:16:
  /var/lib/dkms/ndiswrapper/1.60/build/ndis.c: In function 
‘NdisMAllocateSharedMemory’:
  /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.h:122:20: error: 
‘__GFP_REPEAT’ undeclared (first use in this function)
 GFP_KERNEL | __GFP_REPEAT)
  ^
  /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:1095:10: note: in expansion of 
macro ‘PCI_DMA_ALLOC_COHERENT’
*virt = PCI_DMA_ALLOC_COHERENT(wd->pci.pdev, size, _addr);
^
  /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.h:122:20: note: each 
undeclared identifier is reported only once for each function it appears in
 GFP_KERNEL | __GFP_REPEAT)
  ^
  /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:1095:10: note: in expansion of 
macro ‘PCI_DMA_ALLOC_COHERENT’
*virt = PCI_DMA_ALLOC_COHERENT(wd->pci.pdev, size, _addr);
^
  /var/lib/dkms/ndiswrapper/1.60/build/ndis.c: In function 
‘NdisMIndicateReceivePacket’:
  /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:2261:15: error: ‘struct 
net_device’ has no member named ‘last_rx’
 wnd->net_dev->last_rx = jiffies;
 ^
  /var/lib/dkms/ndiswrapper/1.60/build/ndis.c: In function 
‘EthRxIndicateHandler’:
  /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:2349:14: error: ‘struct 
net_device’ has no member named ‘last_rx’
wnd->net_dev->last_rx = jiffies;
^
  /var/lib/dkms/ndiswrapper/1.60/build/ndis.c: In function 
‘NdisMTransferDataComplete’:
  /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:2464:14: error: ‘struct 
net_device’ has no member named ‘last_rx’
wnd->net_dev->last_rx = jiffies;
^
  scripts/Makefile.build:308: '/var/lib/dkms/ndiswrapper/1.60/build/ndis.o' 타겟에 
대한 명령이 실패했습니다
  make[1]: *** [/var/lib/dkms/ndiswrapper/1.60/build/ndis.o] 오류 1
  Makefile:1550: '_module_/var/lib/dkms/ndiswrapper/1.60/build' 타겟에 대한 명령이 
실패했습니다
  make: *** [_module_/var/lib/dkms/ndiswrapper/1.60/build] 오류 2
  make: 디렉터리 '/usr/src/linux-headers-4.13.0-26-generic' 나감

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

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

[Kernel-packages] [Bug 1736774] Re: arm64/thunderx: Unhandled context faults in ACPI mode

2018-01-24 Thread Stefan Bader

** Changed in: linux (Ubuntu Zesty)
   Status: New => Won't Fix

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

Title:
  arm64/thunderx: Unhandled context faults in ACPI mode

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  In Progress

Bug description:
  [Impact]
  Booting a Cavium ThunderX node in ACPI mode results in constant messages like 
this to the console:
    arm-smmu arm-smmu.1.auto: Unhandled context fault: fsr=0x8402, 
iova=0x0fffc000, fsynr=0x10081, cb=1

  In some configurations, this causes the SATA controller to fail to
  initialize, making the system unbootable. (Note to self: this occurs
  on our internal system known as "alekhin").

  [Test Case]
  Boot a Cavium ThunderX node w/ the kernel parameter "acpi=on" and watch the 
console.

  [Regression Risk]
  The fixes are restricted to quirks for Cavium ThunderX hardware, which is 
hardware we've tested directly.

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

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

[Kernel-packages] [Bug 1738497] Re: Falkor erratum 1041 needs workaround

2018-01-24 Thread Stefan Bader

** Changed in: linux (Ubuntu Zesty)
   Status: In Progress => Won't Fix

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

Title:
  Falkor erratum 1041 needs workaround

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  In Progress

Bug description:
  [Impact]
  A hardware issue can lead to a kernel crash or unexpected behavior.

  [Test Case]
  The issue presents itself most commonly as a boot-time crash. It doesn't 
effect all Falkor CPUs, and only rarely occurs on CPUs that are effected.

  [Regression Risk]
  The fix is entirely in arm64 code, mitigating the risk to other 
architectures. The biggest regression risk is performance, as the workaround 
involves adding an instruction barrier prior to disabling the MMU.

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

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

[Kernel-packages] [Bug 1728523] Update Released

2018-01-24 Thread Chris J Arges

The verification of the Stable Release Update for linux-firmware has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  QCA6174A XR cannot find any WiFi AP

Status in HWE Next:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Released

Bug description:
  SRU Justification
  [Impact]
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e]
  Atheros QCA6174 can't find any WiFi APs and got below message in dmesg

  [   16.158772] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   22.162575] ath10k_pci :02:00.0: could not suspend target (-11)
  [   27.533002] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   33.535958] ath10k_pci :02:00.0: could not suspend target (-11)
  [   38.890790] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   44.893968] ath10k_pci :02:00.0: could not suspend target (-11)
  [   46.358194] i2c_designware i2c_designware.0: controller timed out
  [   47.358231] i2c_designware i2c_designware.0: controller timed out
  [   48.358506] i2c_designware i2c_designware.0: controller timed out
  [   49.566240] i2c_designware i2c_designware.2: controller timed out
  [   50.566862] i2c_designware i2c_designware.2: controller timed out
  [   51.566307] i2c_designware i2c_designware.2: controller timed out
  [   52.670330] i2c_designware i2c_designware.3: controller timed out
  [   53.670775] i2c_designware i2c_designware.3: controller timed out
  [   54.670427] i2c_designware i2c_designware.3: controller timed out
  [   60.326619] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   66.327117] ath10k_pci :02:00.0: could not suspend target (-11)
  [   71.678943] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   77.679084] ath10k_pci :02:00.0: could not suspend target (-11)

  It requires updated firmwares to enable it.

  [Test Case]
  After applying the required firmwares, it can search APs and connect to the 
network.

  [Regression Potential]
  Although the new firmware overwrite the old one, considering it exists in 
linux-firmware git tree and didn't get any update for 3 month, it should be 
good with no regression.

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

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

[Kernel-packages] [Bug 1728523] Re: QCA6174A XR cannot find any WiFi AP

This bug was fixed in the package linux-firmware - 1.157.15

---
linux-firmware (1.157.15) xenial; urgency=medium

  * QCA6174A XR cannot find any WiFi AP (LP: #1728523)
- ath10k: QCA6174 hw3.0: update board-2.bin
- ath10k: QCA6174 hw3.0: update board-2.bin
- ath10k: QCA6174 hw3.0: update board-2.bin

  * Intel 9260/9462/9560 firmware support (LP: #1734243)
- iwlwifi: add firmware version 33 for new 9000 series
- linux-firmware: Add firmware file for Intel Bluetooth 9560
- linux-firmware: Add firmware file for Intel Bluetooth 9260

  * Bluetooth mouse and keyboard connects, works for a few seconds, then
doesn't react (LP: #1729389)
- linux-firmware: Update firmware patch for Intel Bluetooth,8260
- linux-firmware: Update firmware file for Intel Bluetooth 8265
- linux-firmware: Update firmware patch for Intel Bluetooth 8260

 -- Seth Forshee   Tue, 12 Dec 2017 08:26:17
-0600

** Changed in: linux-firmware (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  QCA6174A XR cannot find any WiFi AP

Status in HWE Next:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Released

Bug description:
  SRU Justification
  [Impact]
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e]
  Atheros QCA6174 can't find any WiFi APs and got below message in dmesg

  [   16.158772] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   22.162575] ath10k_pci :02:00.0: could not suspend target (-11)
  [   27.533002] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   33.535958] ath10k_pci :02:00.0: could not suspend target (-11)
  [   38.890790] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   44.893968] ath10k_pci :02:00.0: could not suspend target (-11)
  [   46.358194] i2c_designware i2c_designware.0: controller timed out
  [   47.358231] i2c_designware i2c_designware.0: controller timed out
  [   48.358506] i2c_designware i2c_designware.0: controller timed out
  [   49.566240] i2c_designware i2c_designware.2: controller timed out
  [   50.566862] i2c_designware i2c_designware.2: controller timed out
  [   51.566307] i2c_designware i2c_designware.2: controller timed out
  [   52.670330] i2c_designware i2c_designware.3: controller timed out
  [   53.670775] i2c_designware i2c_designware.3: controller timed out
  [   54.670427] i2c_designware i2c_designware.3: controller timed out
  [   60.326619] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   66.327117] ath10k_pci :02:00.0: could not suspend target (-11)
  [   71.678943] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   77.679084] ath10k_pci :02:00.0: could not suspend target (-11)

  It requires updated firmwares to enable it.

  [Test Case]
  After applying the required firmwares, it can search APs and connect to the 
network.

  [Regression Potential]
  Although the new firmware overwrite the old one, considering it exists in 
linux-firmware git tree and didn't get any update for 3 month, it should be 
good with no regression.

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

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

[Kernel-packages] [Bug 1729389] Re: [Intel 8260/8265] Bluetooth peripherals work for a few seconds, then don't react

This bug was fixed in the package linux-firmware - 1.157.15

---
linux-firmware (1.157.15) xenial; urgency=medium

  * QCA6174A XR cannot find any WiFi AP (LP: #1728523)
- ath10k: QCA6174 hw3.0: update board-2.bin
- ath10k: QCA6174 hw3.0: update board-2.bin
- ath10k: QCA6174 hw3.0: update board-2.bin

  * Intel 9260/9462/9560 firmware support (LP: #1734243)
- iwlwifi: add firmware version 33 for new 9000 series
- linux-firmware: Add firmware file for Intel Bluetooth 9560
- linux-firmware: Add firmware file for Intel Bluetooth 9260

  * Bluetooth mouse and keyboard connects, works for a few seconds, then
doesn't react (LP: #1729389)
- linux-firmware: Update firmware patch for Intel Bluetooth,8260
- linux-firmware: Update firmware file for Intel Bluetooth 8265
- linux-firmware: Update firmware patch for Intel Bluetooth 8260

 -- Seth Forshee   Tue, 12 Dec 2017 08:26:17
-0600

** Changed in: linux-firmware (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  [Intel 8260/8265] Bluetooth peripherals work for a few seconds, then
  don't react

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Confirmed
Status in linux-firmware source package in Artful:
  Fix Released

Bug description:
  SRU Justification

  Impact: Bluetooth peripherals work initially but stop working shortly
  with Linux 4.13.

  Fix: Updated firmware from Intel containing a fix for the issue.

  Regression Potential: Any firmware updates may bring regressions,
  however this is a bug fix update and therefore regression potential is
  expected to be minimal.

  ---

  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  ---
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp.
   Bus 001 Device 005: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 13d3:5664 IMC Networks
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
    UP RUNNING PSCAN ISCAN INQUIRY
    RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
    TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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

[Kernel-packages] [Bug 1729389] Re: [Intel 8260/8265] Bluetooth peripherals work for a few seconds, then don't react

2018-01-24 Thread Chris J Arges

** Changed in: linux-firmware (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [Intel 8260/8265] Bluetooth peripherals work for a few seconds, then
  don't react

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Confirmed
Status in linux-firmware source package in Artful:
  Fix Released

Bug description:
  SRU Justification

  Impact: Bluetooth peripherals work initially but stop working shortly
  with Linux 4.13.

  Fix: Updated firmware from Intel containing a fix for the issue.

  Regression Potential: Any firmware updates may bring regressions,
  however this is a bug fix update and therefore regression potential is
  expected to be minimal.

  ---

  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  ---
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp.
   Bus 001 Device 005: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 13d3:5664 IMC Networks
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
    UP RUNNING PSCAN ISCAN INQUIRY
    RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
    TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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

[Kernel-packages] [Bug 1734243] Re: Intel 9260/9462/9560 firmware support

This bug was fixed in the package linux-firmware - 1.157.15

---
linux-firmware (1.157.15) xenial; urgency=medium

  * QCA6174A XR cannot find any WiFi AP (LP: #1728523)
- ath10k: QCA6174 hw3.0: update board-2.bin
- ath10k: QCA6174 hw3.0: update board-2.bin
- ath10k: QCA6174 hw3.0: update board-2.bin

  * Intel 9260/9462/9560 firmware support (LP: #1734243)
- iwlwifi: add firmware version 33 for new 9000 series
- linux-firmware: Add firmware file for Intel Bluetooth 9560
- linux-firmware: Add firmware file for Intel Bluetooth 9260

  * Bluetooth mouse and keyboard connects, works for a few seconds, then
doesn't react (LP: #1729389)
- linux-firmware: Update firmware patch for Intel Bluetooth,8260
- linux-firmware: Update firmware file for Intel Bluetooth 8265
- linux-firmware: Update firmware patch for Intel Bluetooth 8260

 -- Seth Forshee   Tue, 12 Dec 2017 08:26:17
-0600

** Changed in: linux-firmware (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Intel 9260/9462/9560 firmware support

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux-firmware source package in Zesty:
  Fix Committed
Status in linux-firmware source package in Artful:
  Fix Released

Bug description:
  SRU Justification
  [Impact]
  Intel 9260/9462/9560 require new firmwares to enable them.

  [ 7.492326] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-33.ucode failed with error -2
  [ 7.492349] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-32.ucode failed with error -2
  [ 7.492362] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-31.ucode failed with error -2
  [ 7.492375] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-30.ucode failed with error -2
  [ 7.492378] iwlwifi :00:0c.0: no suitable firmware found!

  For v4.13 kernel, it uses firmware version 33, so we only need this.

  commit c4276b65390d32d33c8263a7e3c8be0db8cccad4 (tag: 
refs/tags/iwlwifi-fw-2017-11-03)
  Author: Luca Coelho 
  Date:   Fri Oct 13 14:22:26 2017 +0300

  iwlwifi: add firmware version 33 for new 9000 series

  Build number: WFFW53774_R30_FW610294

  Revision number: 610294

  Signed-off-by: Luca Coelho 

  [Test Case]
  After applying the firmwares, confirm the 9260/9560 can connect to 6 
different APs(bg/n/ac * open/wap)

  [Regression Potential]
  There is no regression for the new devices and new firmwares.

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

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

[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

2018-01-24 Thread Agustin Barto

It works. 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/1745032

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The AC adapter status is incorrectly reported when the battery is
  fully charged. It always shows as if the adapter is not plugged in. If
  the battery is drained for a while, the adapter status is shown
  correctly (both connects and disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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