[Kernel-packages] [Bug 1559308] Re: Plugging HDMI screen in causes system hang

[Kai-Heng Feng]

@johnnynobody,

Please file a new bug.
Also, I don't think all DC codes are in the mainline yet. The easiest way to 
"solve" the issue is use AMDGPU-Pro from AMD.

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

Title:
  Plugging HDMI screen in causes system hang

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I have a 4K UHD laptop screen and am running Ubuntu Gnome 16.04 Beta1
  using 4.4.0-13-generic and the Nouveau drivers.

  If I plug in an external HDMI monitor (FHD) either into either HDMI
  port (there's one on the machine and there's one available via a usb
  3.1 extra adaptor) then the whole system hangs, completely
  unresponsive and needing a hard reboot. Before hanging the 2nd display
  gets an image as expected, but the laptop's screen flashes randomly,
  sometimes you see weird artifacts. Then the hang comes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar 18 20:43:42 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06e4]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4]
  InstallationDate: Installed on 2016-03-15 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160225.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed 
root=UUID=b026feed-8801-44f4-9f3f-c245f4a1f25e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Mar 18 17:28:07 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   Unknown chipset: NV117
   SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5182 
   vendor SHP
  xserver.version: 2:1.18.1-1ubuntu4

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

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

[Kernel-packages] [Bug 1704469] Re: r8169 0000:02:00.0: invalid large VPD tag 7f at offset 0

[Launchpad Bug Tracker]

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

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

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

Title:
  r8169 :02:00.0: invalid large VPD tag 7f at offset 0

Status in linux package in Ubuntu:
  Expired

Bug description:
  dmesg:
  [ 1025.813826] r8169 :02:00.0: invalid large VPD tag 7f at offset 0

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-10-generic 4.11.0-10.15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1801 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Jul 14 15:30:03 2017
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2017-07-05 (9 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic 
root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-10-generic N/A
   linux-backports-modules-4.11.0-10-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-07-05 (8 days ago)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1704764] Re: NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [chromium-browse:23224]

[Launchpad Bug Tracker]

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

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

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [chromium-
  browse:23224]

Status in linux package in Ubuntu:
  Expired

Bug description:
  IT SUDDENLY APPEARED AND I HONESTLY HAVE NO IDEA WHAT TO DO WITH
  THESE.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-11-generic 4.11.0-11.16
  ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10
  Uname: Linux 4.11.0-11-generic i686
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm4852 F pulseaudio
yoogeun8331 F pulseaudio
  Date: Mon Jul 17 16:32:29 2017
  Failure: oops
  HibernationDevice: RESUME=UUID=4959b0ef-4074-4fad-a92e-aa2dbedbcc41
  InstallationDate: Installed on 2016-10-06 (283 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: LG Electronics 15ZD960-GX36K
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-11-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! 
[chromium-browse:23224]
  UpgradeStatus: Upgraded to artful on 2017-06-02 (45 days ago)
  dmi.bios.date: 02/17/2016
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 15ZA1570 X64
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 15Z960
  dmi.board.vendor: LG Electronics
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: LG Electronics
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr15ZA1570X64:bd02/17/2016:svnLGElectronics:pn15ZD960-GX36K:pvr0.1:rvnLGElectronics:rn15Z960:rvrFAB1:cvnLGElectronics:ct9:cvr0.1:
  dmi.product.name: 15ZD960-GX36K
  dmi.product.version: 0.1
  dmi.sys.vendor: LG Electronics

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

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

[Kernel-packages] [Bug 1704763] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [systemd:1]

[Launchpad Bug Tracker]

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

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

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [systemd:1]

Status in linux package in Ubuntu:
  Expired

Bug description:
  IT JUST APPEARED

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-11-generic 4.11.0-11.16
  ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10
  Uname: Linux 4.11.0-11-generic i686
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm4852 F pulseaudio
yoogeun8331 F pulseaudio
  Date: Mon Jul 17 16:28:25 2017
  Failure: oops
  HibernationDevice: RESUME=UUID=4959b0ef-4074-4fad-a92e-aa2dbedbcc41
  InstallationDate: Installed on 2016-10-06 (283 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: LG Electronics 15ZD960-GX36K
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-11-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [systemd:1]
  UpgradeStatus: Upgraded to artful on 2017-06-02 (45 days ago)
  dmi.bios.date: 02/17/2016
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 15ZA1570 X64
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 15Z960
  dmi.board.vendor: LG Electronics
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: LG Electronics
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr15ZA1570X64:bd02/17/2016:svnLGElectronics:pn15ZD960-GX36K:pvr0.1:rvnLGElectronics:rn15Z960:rvrFAB1:cvnLGElectronics:ct9:cvr0.1:
  dmi.product.name: 15ZD960-GX36K
  dmi.product.version: 0.1
  dmi.sys.vendor: LG Electronics

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

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

[Kernel-packages] [Bug 1686837] Re: ubuntu fails to boot with btrfs root (unable to mount root)

[Launchpad Bug Tracker]

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

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

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

Title:
  ubuntu fails to boot with btrfs root (unable to mount root)

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hello,

  Failing to mount / as btrfs has been haunting btrfs users on ubuntu
  for some time. Coming and going with kernel updates.

  After I upgraded to 17.04, it seems that the problem is back.

  It seems that a non-clean umount reboot always leads to a non-bootable 
system. If I boot into rescue (selecting in grub, not a livecd), kernel can 
find the root partition. I can also boot normally if root=... kernel parameter 
is set with the device name (/dev/sda6) instead of UUID=.
  So, there might be a bug in kernel that does not allow linux to identify the 
boot partition using UUID in some circumstances (probably after a dirt reboot).

  Maybe other distros do some magic at initrd that cleans the btrfs
  problem because some, like opensuse, do uses btrfs as default root fs.
  Anyway, even ubuntu own rescue can boot normally.

  This is a tricky bug to debug as I get no logs written and no
  emergency shell. Just an ugly kernel error and a backstack.

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

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

[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

[Seth Arnold]

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

** This bug has been marked 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

** Information type changed from Private Security to Public

-- 
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 1712867] Re: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

[Marcelo Cerri]

I have verified kexec-tools and crash with the 4.4 kernel in a ppc64el
machine and both packages are working as expected.

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

Title:
  [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

Status in crash package in Ubuntu:
  Fix Released
Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in crash source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Xenial:
  Fix Committed
Status in linux-azure source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  Currently it's not possible to use the kdump functionality in xenial
  when running the linux-azure kernel. The problem is actually caused by
  several factors:

  1. kexec fails to parse /proc/kcore and thus fails to load the crash
  kernel. That's similar to bug #1713940 and it's related to 4.10+
  kernels.

  2. When the crash kernel boots, a bug in KASLR causes it to crash in a
  very early stage. For the user, it seems the system just rebooted
  after the crash.

  3. Currently in azure, crashkernel=128G is not enough to boot and run
  the dump procedure with 4.11+ kernels. That value needs to be
  increased in order to kdump to succeed.

  4. After the vmcore is dumped, the current version of crash in xenial
  is not able to parse it. All the necessary fixes are already upstream
  and can be backported.

  [Test Case]

  1. Install the linux-azure kernel in an azure instance (although it's
  possible to run linux-azure in bare metal or kvm, the KASLR issue only
  is triggered in azure).

  2. Follow the instructions in https://help.ubuntu.com/lts/serverguide
  /kernel-crash-dump.html to setup kdump and manually trigger a crash
  using /proc/sysrq-trigger.

  The vmcore must be generated and it should be possible to inspect it
  using crash.

  3. Perform these same tests for the linux-generic kernel, on each
  supported architecture.

  [Regression Potential]

  Since both kexec-tools and crash are being changed to support 4.10+
  kernels, it's very important that they continue to handle 4.4 kernels
  properly.

  The same steps above can be used to test linux-generic for
  regressions.

  [Other Info]

  Original description:

  --8<--
  Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the 
following error:
  kdump-tools[1436]: ELF core (kcore) parse failed

  Perhaps the artful kexec-tools should be backported?
  --8<--

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

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

[Steve Beattie]

Not quite sure what's gone wrong, but these are the relevant messages
from the journal log:

sep 15 21:39:42 hostname bluetoothd[22727]: Failed to access management 
interface
sep 15 21:39:42 hostname bluetoothd[22727]: Adapter handling initialization 
failed
sep 15 21:39:42 hostname pulseaudio[5571]: [pulseaudio] bluez5-util.c: 
GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Message 
recipient disconnected from message bus without replying
sep 15 21:39:42 hostname systemd[1]: Failed to start Bluetooth service.
sep 15 21:39:42 hostname systemd[1]: bluetooth.service: Failed with result 
'exit-code'.
sep 15 21:39:42 hostname AptDaemon.Worker[21499]: CRITICAL: bluez: 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/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:
  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/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 1712867] Re: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

[Launchpad Bug Tracker]

This bug was fixed in the package crash - 7.1.4-1ubuntu4.2

---
crash (7.1.4-1ubuntu4.2) xenial; urgency=medium

  [ Marcelo Henrique Cerri ]
  * [Hyper-V] 16.04 kexec-tools doesn't match linux-azure (LP: #1712867)
d/p/0011-Fix-for-Linux-commit-0100301bfdf56a2a370c7157b5ab0fb.patch
d/p/0012-Fix-for-the-ps-t-option-in-3.17-and-later-kernels-th.patch
d/p/0013-Fix-for-the-irq-s-option-for-Linux-4.2-and-later-ker.patch
d/p/0014-Improvement-of-the-accuracy-of-the-allocated-objects.patch
d/p/0015-When-reading-a-task-s-task_struct.flags-field-check-.patch
d/p/0016-Fix-for-Linux-4.8-rc1-commit-500462a9de657f86edaa102.patch
d/p/0017-Improvement-of-the-dev-d-option-to-display-I-O-stati.patch
d/p/0018-Introduction-of-a-new-bt-v-option-that-checks-the-ke.patch
d/p/0019-Fix-for-Linux-4.9-rc1-commits-15f4eae70d365bba26854c.patch
d/p/0020-Fix-for-Linux-4.10-commit-7fd8329ba502ef76dd91db561c.patch
d/p/0021-Prepare-for-the-kernel-s-taint_flag.true-and-taint_f.patch
d/p/0022-Prevent-the-livepatch-taint-flag-check-during-the-sy.patch

 -- Stefan Bader   Tue, 12 Sep 2017 09:15:25
+0200

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

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

Title:
  [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

Status in crash package in Ubuntu:
  Fix Released
Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in crash source package in Xenial:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  Currently it's not possible to use the kdump functionality in xenial
  when running the linux-azure kernel. The problem is actually caused by
  several factors:

  1. kexec fails to parse /proc/kcore and thus fails to load the crash
  kernel. That's similar to bug #1713940 and it's related to 4.10+
  kernels.

  2. When the crash kernel boots, a bug in KASLR causes it to crash in a
  very early stage. For the user, it seems the system just rebooted
  after the crash.

  3. Currently in azure, crashkernel=128G is not enough to boot and run
  the dump procedure with 4.11+ kernels. That value needs to be
  increased in order to kdump to succeed.

  4. After the vmcore is dumped, the current version of crash in xenial
  is not able to parse it. All the necessary fixes are already upstream
  and can be backported.

  [Test Case]

  1. Install the linux-azure kernel in an azure instance (although it's
  possible to run linux-azure in bare metal or kvm, the KASLR issue only
  is triggered in azure).

  2. Follow the instructions in https://help.ubuntu.com/lts/serverguide
  /kernel-crash-dump.html to setup kdump and manually trigger a crash
  using /proc/sysrq-trigger.

  The vmcore must be generated and it should be possible to inspect it
  using crash.

  3. Perform these same tests for the linux-generic kernel, on each
  supported architecture.

  [Regression Potential]

  Since both kexec-tools and crash are being changed to support 4.10+
  kernels, it's very important that they continue to handle 4.4 kernels
  properly.

  The same steps above can be used to test linux-generic for
  regressions.

  [Other Info]

  Original description:

  --8<--
  Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the 
following error:
  kdump-tools[1436]: ELF core (kcore) parse failed

  Perhaps the artful kexec-tools should be backported?
  --8<--

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

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

[Kernel-packages] [Bug 1712867] Update Released

[Steve Langasek]

The verification of the Stable Release Update for kexec-tools 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 crash in Ubuntu.
https://bugs.launchpad.net/bugs/1712867

Title:
  [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

Status in crash package in Ubuntu:
  Fix Released
Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in crash source package in Xenial:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  Currently it's not possible to use the kdump functionality in xenial
  when running the linux-azure kernel. The problem is actually caused by
  several factors:

  1. kexec fails to parse /proc/kcore and thus fails to load the crash
  kernel. That's similar to bug #1713940 and it's related to 4.10+
  kernels.

  2. When the crash kernel boots, a bug in KASLR causes it to crash in a
  very early stage. For the user, it seems the system just rebooted
  after the crash.

  3. Currently in azure, crashkernel=128G is not enough to boot and run
  the dump procedure with 4.11+ kernels. That value needs to be
  increased in order to kdump to succeed.

  4. After the vmcore is dumped, the current version of crash in xenial
  is not able to parse it. All the necessary fixes are already upstream
  and can be backported.

  [Test Case]

  1. Install the linux-azure kernel in an azure instance (although it's
  possible to run linux-azure in bare metal or kvm, the KASLR issue only
  is triggered in azure).

  2. Follow the instructions in https://help.ubuntu.com/lts/serverguide
  /kernel-crash-dump.html to setup kdump and manually trigger a crash
  using /proc/sysrq-trigger.

  The vmcore must be generated and it should be possible to inspect it
  using crash.

  3. Perform these same tests for the linux-generic kernel, on each
  supported architecture.

  [Regression Potential]

  Since both kexec-tools and crash are being changed to support 4.10+
  kernels, it's very important that they continue to handle 4.4 kernels
  properly.

  The same steps above can be used to test linux-generic for
  regressions.

  [Other Info]

  Original description:

  --8<--
  Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the 
following error:
  kdump-tools[1436]: ELF core (kcore) parse failed

  Perhaps the artful kexec-tools should be backported?
  --8<--

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

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

[Kernel-packages] [Bug 1712867] Re: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

[Launchpad Bug Tracker]

This bug was fixed in the package kexec-tools - 1:2.0.10-1ubuntu2.4

---
kexec-tools (1:2.0.10-1ubuntu2.4) xenial; urgency=medium

  [Marcelo Henrique Cerri]
  * [Hyper-V] 16.04 kexec-tools doesn't match linux-azure (LP: #1712867)
- [PATCH] build_mem_phdrs(): check if p_paddr is invalid
- [PATCH] kexec-tools/x86: get_kernel_vaddr_and_size off-by-one fix
- Increase crashkernel size to 256M for machines with 2G or more of memory.

 -- Stefan Bader   Tue, 12 Sep 2017 09:12:32
+0200

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

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

Title:
  [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

Status in crash package in Ubuntu:
  Fix Released
Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in crash source package in Xenial:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  Currently it's not possible to use the kdump functionality in xenial
  when running the linux-azure kernel. The problem is actually caused by
  several factors:

  1. kexec fails to parse /proc/kcore and thus fails to load the crash
  kernel. That's similar to bug #1713940 and it's related to 4.10+
  kernels.

  2. When the crash kernel boots, a bug in KASLR causes it to crash in a
  very early stage. For the user, it seems the system just rebooted
  after the crash.

  3. Currently in azure, crashkernel=128G is not enough to boot and run
  the dump procedure with 4.11+ kernels. That value needs to be
  increased in order to kdump to succeed.

  4. After the vmcore is dumped, the current version of crash in xenial
  is not able to parse it. All the necessary fixes are already upstream
  and can be backported.

  [Test Case]

  1. Install the linux-azure kernel in an azure instance (although it's
  possible to run linux-azure in bare metal or kvm, the KASLR issue only
  is triggered in azure).

  2. Follow the instructions in https://help.ubuntu.com/lts/serverguide
  /kernel-crash-dump.html to setup kdump and manually trigger a crash
  using /proc/sysrq-trigger.

  The vmcore must be generated and it should be possible to inspect it
  using crash.

  3. Perform these same tests for the linux-generic kernel, on each
  supported architecture.

  [Regression Potential]

  Since both kexec-tools and crash are being changed to support 4.10+
  kernels, it's very important that they continue to handle 4.4 kernels
  properly.

  The same steps above can be used to test linux-generic for
  regressions.

  [Other Info]

  Original description:

  --8<--
  Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the 
following error:
  kdump-tools[1436]: ELF core (kcore) parse failed

  Perhaps the artful kexec-tools should be backported?
  --8<--

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

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

[Kernel-packages] [Bug 1712867] Re: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

[Marcelo Cerri]

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

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

Title:
  [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

Status in crash package in Ubuntu:
  Fix Released
Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in crash source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Xenial:
  Fix Committed
Status in linux-azure source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  Currently it's not possible to use the kdump functionality in xenial
  when running the linux-azure kernel. The problem is actually caused by
  several factors:

  1. kexec fails to parse /proc/kcore and thus fails to load the crash
  kernel. That's similar to bug #1713940 and it's related to 4.10+
  kernels.

  2. When the crash kernel boots, a bug in KASLR causes it to crash in a
  very early stage. For the user, it seems the system just rebooted
  after the crash.

  3. Currently in azure, crashkernel=128G is not enough to boot and run
  the dump procedure with 4.11+ kernels. That value needs to be
  increased in order to kdump to succeed.

  4. After the vmcore is dumped, the current version of crash in xenial
  is not able to parse it. All the necessary fixes are already upstream
  and can be backported.

  [Test Case]

  1. Install the linux-azure kernel in an azure instance (although it's
  possible to run linux-azure in bare metal or kvm, the KASLR issue only
  is triggered in azure).

  2. Follow the instructions in https://help.ubuntu.com/lts/serverguide
  /kernel-crash-dump.html to setup kdump and manually trigger a crash
  using /proc/sysrq-trigger.

  The vmcore must be generated and it should be possible to inspect it
  using crash.

  3. Perform these same tests for the linux-generic kernel, on each
  supported architecture.

  [Regression Potential]

  Since both kexec-tools and crash are being changed to support 4.10+
  kernels, it's very important that they continue to handle 4.4 kernels
  properly.

  The same steps above can be used to test linux-generic for
  regressions.

  [Other Info]

  Original description:

  --8<--
  Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the 
following error:
  kdump-tools[1436]: ELF core (kcore) parse failed

  Perhaps the artful kexec-tools should be backported?
  --8<--

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

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

[Kernel-packages] [Bug 1712867] Re: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

[Steve Langasek]

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

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

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

Title:
  [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

Status in crash package in Ubuntu:
  Fix Released
Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in crash source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Xenial:
  Fix Committed
Status in linux-azure source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  Currently it's not possible to use the kdump functionality in xenial
  when running the linux-azure kernel. The problem is actually caused by
  several factors:

  1. kexec fails to parse /proc/kcore and thus fails to load the crash
  kernel. That's similar to bug #1713940 and it's related to 4.10+
  kernels.

  2. When the crash kernel boots, a bug in KASLR causes it to crash in a
  very early stage. For the user, it seems the system just rebooted
  after the crash.

  3. Currently in azure, crashkernel=128G is not enough to boot and run
  the dump procedure with 4.11+ kernels. That value needs to be
  increased in order to kdump to succeed.

  4. After the vmcore is dumped, the current version of crash in xenial
  is not able to parse it. All the necessary fixes are already upstream
  and can be backported.

  [Test Case]

  1. Install the linux-azure kernel in an azure instance (although it's
  possible to run linux-azure in bare metal or kvm, the KASLR issue only
  is triggered in azure).

  2. Follow the instructions in https://help.ubuntu.com/lts/serverguide
  /kernel-crash-dump.html to setup kdump and manually trigger a crash
  using /proc/sysrq-trigger.

  The vmcore must be generated and it should be possible to inspect it
  using crash.

  3. Perform these same tests for the linux-generic kernel, on each
  supported architecture.

  [Regression Potential]

  Since both kexec-tools and crash are being changed to support 4.10+
  kernels, it's very important that they continue to handle 4.4 kernels
  properly.

  The same steps above can be used to test linux-generic for
  regressions.

  [Other Info]

  Original description:

  --8<--
  Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the 
following error:
  kdump-tools[1436]: ELF core (kcore) parse failed

  Perhaps the artful kexec-tools should be backported?
  --8<--

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

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

[Kernel-packages] [Bug 1717581] Re: linux 4.13.0-11.12 ADT test failure with linux 4.13.0-11.12

[Seth Forshee]

Reproduced in a VM.

[   48.361847] BUG: unable to handle kernel paging request at d000
[   48.362522] IP: wp_page_copy+0xa5/0x650
[   48.362899] *pdpt = 15d85001 *pde = 15f0d067 
[   48.362900] *pte =  
[   48.363458] 
[   48.363974] Oops: 0002 [#1] SMP
[   48.364285] Modules linked in: ppdev input_leds i2c_piix4 joydev serio_raw 
mac_hid parport_pc parport qemu_fw_cfg ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 
btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx 
xor raid6_pq libcrc32c raid1 raid0 multipath linear psmouse virtio_blk 
virtio_net floppy pata_acpi
[   48.367731] CPU: 0 PID: 372 Comm: systemd-udevd Tainted: GW   
4.13.0-10-generic #11-Ubuntu
[   48.368608] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
[   48.369503] task: d3dc57c0 task.stack: d392c000
[   48.369966] EIP: wp_page_copy+0xa5/0x650
[   48.370361] EFLAGS: 00010282 CPU: 0
[   48.370714] EAX: d000 EBX: d11a4000 ECX: d000 EDX: bf991ff0
[   48.371295] ESI: d11a4000 EDI: d004 EBP: d392dea0 ESP: d392de64
[   48.371890]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[   48.372573] CR0: 80050033 CR2: d000 CR3: 1ed26e60 CR4: 06f0
[   48.375056] Call Trace:
[   48.376155]  do_wp_page+0x83/0x4f0
[   48.377090]  ? kmap_atomic_prot+0x3c/0x100
[   48.377632]  handle_mm_fault+0x94b/0xe70
[   48.377965]  __do_page_fault+0x209/0x500
[   48.378290]  ? kvm_async_pf_task_wake+0x100/0x100
[   48.378679]  trace_do_page_fault+0x3f/0xe0
[   48.379048]  ? kvm_async_pf_task_wake+0x100/0x100
[   48.379424]  do_async_page_fault+0x55/0x70
[   48.379764]  common_exception+0x6c/0x72
[   48.380070] EIP: 0xb7e1c76a
[   48.380296] EFLAGS: 00010286 CPU: 0
[   48.380574] EAX: bf9927f0 EBX: 01200011 ECX:  EDX: 
[   48.381066] ESI:  EDI: 03ad EBP: bf992838 ESP: bf9927f0
[   48.381558]  DS: 007b ES: 007b FS:  GS: 0033 SS: 007b
[   48.381985] Code: 00 00 8b 4d e8 85 c9 0f 84 11 05 00 00 8b 45 e8 e8 61 80 
ea ff 89 c3 8b 45 e0 89 de e8 55 80 ea ff 8b 13 8d 78 04 89 c1 83 e7 fc <89> 10 
8b 93 fc 0f 00 00 29 f9 29 ce 81 c1 00 10 00 00 c1 e9 02
[   48.383453] EIP: wp_page_copy+0xa5/0x650 SS:ESP: 0068:d392de64
[   48.383921] CR2: d000
[   48.384188] ---[ end trace a95cd1e3637ee3ef ]---
[   48.385163] BUG: unable to handle kernel paging request at dfffeaed
[   48.385680] IP: ext4_block_write_begin+0x435/0x470
[   48.386062] *pdpt = 15d85001 *pde = 15f0d067 
[   48.386063] *pte =  
[   48.386516] 
[   48.386930] Oops: 0002 [#2] SMP
[   48.387185] Modules linked in: ppdev input_leds i2c_piix4 joydev serio_raw 
mac_hid parport_pc parport qemu_fw_cfg ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 
btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx 
xor raid6_pq libcrc32c raid1 raid0 multipath linear psmouse virtio_blk 
virtio_net floppy pata_acpi
[   48.390027] CPU: 0 PID: 525 Comm: rs:main Q:Reg Tainted: G  D W   
4.13.0-10-generic #11-Ubuntu
[   48.390759] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
[   48.391462] task: d754f500 task.stack: d7552000
[   48.391833] EIP: ext4_block_write_begin+0x435/0x470
[   48.392219] EFLAGS: 00010216 CPU: 0
[   48.392499] EAX: 0513 EBX: 00e5 ECX: dfffeaed EDX: de637000
[   48.392992] ESI:  EDI: dfffeaf1 EBP: d7553d9c ESP: d7553d4c
[   48.393487]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[   48.393915] CR0: 80050033 CR2: dfffeaed CR3: 1423c860 CR4: 06f0
[   48.394412] Call Trace:
[   48.394614]  ? ext4_inode_attach_jinode.part.63+0x90/0x90
[   48.395044]  ext4_da_write_begin+0x13b/0x380
[   48.395388]  ? ext4_inode_attach_jinode.part.63+0x90/0x90
[   48.395882]  generic_perform_write+0x95/0x180
[   48.396410]  __generic_file_write_iter+0x183/0x1b0
[   48.396878]  ext4_file_write_iter+0x2f0/0x4b0
[   48.397307]  new_sync_write+0xcb/0x130
[   48.397737]  ? ext4_llseek+0x500/0x500
[   48.398237]  __vfs_write+0x37/0x50
[   48.398691]  vfs_write+0x94/0x1a0
[   48.399134]  SyS_write+0x47/0xb0
[   48.399571]  do_fast_syscall_32+0x71/0x150
[   48.400152]  entry_SYSENTER_32+0x4e/0x7c
[   48.400684] EIP: 0xb7f11cf9
[   48.401060] EFLAGS: 0293 CPU: 0
[   48.401546] EAX: ffda EBX: 0005 ECX: b61059b0 EDX: 0e39
[   48.402435] ESI: b61059b0 EDI: 0e39 EBP: b6105800 ESP: b6c25b14
[   48.403240]  DS: 007b ES: 007b FS:  GS: 0033 SS: 007b
[   48.404266] Code: 72 a5 f9 ff e9 0b fe ff ff 90 8d 74 26 00 0f 0b 8d b6 00 
00 00 00 0f 0b 8d b6 00 00 00 00 0f 0b 8d b6 00 00 00 00 0f 0b 8d 79 04  01 
00 00 00 00 c7 44 01 fc 00 00 00 00 83 e7 fc 29 f9 01 c1
[   48.408331] EIP: ext4_block_write_begin+0x435/0x470 SS:ESP: 0068:d7553d4c
[   48.409282] CR2: dfffeaed
[   48.409793] ---[ end 

[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

[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/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:
  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/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 1717589] Re: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Seth Arnold]

** Information type changed from Private Security to Public

-- 
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:
  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/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 1712867] Re: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

[Marcelo Cerri]

** Changed in: kexec-tools (Ubuntu)
   Status: In Progress => Fix Committed

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

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

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

Title:
  [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

Status in crash package in Ubuntu:
  In Progress
Status in kexec-tools package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in crash source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Xenial:
  Fix Committed
Status in linux-azure source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  Currently it's not possible to use the kdump functionality in xenial
  when running the linux-azure kernel. The problem is actually caused by
  several factors:

  1. kexec fails to parse /proc/kcore and thus fails to load the crash
  kernel. That's similar to bug #1713940 and it's related to 4.10+
  kernels.

  2. When the crash kernel boots, a bug in KASLR causes it to crash in a
  very early stage. For the user, it seems the system just rebooted
  after the crash.

  3. Currently in azure, crashkernel=128G is not enough to boot and run
  the dump procedure with 4.11+ kernels. That value needs to be
  increased in order to kdump to succeed.

  4. After the vmcore is dumped, the current version of crash in xenial
  is not able to parse it. All the necessary fixes are already upstream
  and can be backported.

  [Test Case]

  1. Install the linux-azure kernel in an azure instance (although it's
  possible to run linux-azure in bare metal or kvm, the KASLR issue only
  is triggered in azure).

  2. Follow the instructions in https://help.ubuntu.com/lts/serverguide
  /kernel-crash-dump.html to setup kdump and manually trigger a crash
  using /proc/sysrq-trigger.

  The vmcore must be generated and it should be possible to inspect it
  using crash.

  3. Perform these same tests for the linux-generic kernel, on each
  supported architecture.

  [Regression Potential]

  Since both kexec-tools and crash are being changed to support 4.10+
  kernels, it's very important that they continue to handle 4.4 kernels
  properly.

  The same steps above can be used to test linux-generic for
  regressions.

  [Other Info]

  Original description:

  --8<--
  Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the 
following error:
  kdump-tools[1436]: ELF core (kcore) parse failed

  Perhaps the artful kexec-tools should be backported?
  --8<--

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

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

[Kernel-packages] [Bug 1702910] Re: System freeze after in6_dev_finish_destroy errors

[Victor Palma]

Here is additional debug information:


  KERNEL: /usr/lib/debug/boot/vmlinux-4.4.0-87-generic
DUMPFILE: dump.201709151609  [PARTIAL DUMP]
CPUS: 12
DATE: Fri Sep 15 16:05:34 2017
  UPTIME: 1 days, 17:34:46
LOAD AVERAGE: 4.17, 5.02, 4.48
   TASKS: 2572
NODENAME: 543231-infra02
 RELEASE: 4.4.0-87-generic
 VERSION: #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 2017
 MACHINE: x86_64  (3000 Mhz)
  MEMORY: 32 GB
   PANIC: "BUG: unable to handle kernel paging request at 0040"
 PID: 4189
 COMMAND: "dnsmasq"
TASK: 8808299dd400  [THREAD_INFO: 88042502c000]
 CPU: 11
   STATE: TASK_RUNNING (PANIC)


[149668.845048] WARNING: CPU: 0 PID: 11227 at 
/build/linux-5EyXrQ/linux-4.4.0/net/ipv6/addrconf_core.c:159 
in6_dev_finish_destroy+0x6b/0xc0()
[149668.845050] Modules linked in: nf_conntrack_netlink ebt_arp ebt_among xt_CT 
xt_mac xt_physdev xt_set ip_set_hash_net ip_set nfnetlink xt_REDIRECT 
nf_nat_redirect nf_conntrack_ipv6 nf_defrag_ipv6 xt_nat xt_conntrack xt_mark 
xt_connmark tcp_diag udp_diag inet_diag unix_diag ebtable_filter xt_comment 
ip6table_raw ip6table_mangle sunrpc binfmt_misc veth xt_CHECKSUM xt_tcpudp 
iptable_raw ipmi_ssif kvm_amd ib_iser kvm amd64_edac_mod rdma_cm iw_cm 
8250_fintek edac_mce_amd irqbypass ib_cm fam15h_power edac_core ib_sa serio_raw 
ib_mad i2c_piix4 ipmi_si ipmi_msghandler k10temp hpilo ib_core shpchp ib_addr 
vhost_net vhost macvtap macvlan nbd mac_hid iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_vs iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 iptable_mangle iptable_filter ipt_REJECT nf_reject_ipv4
[149668.845092]  ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_nat nf_conntrack 
ip_tables ip6table_filter ip6_tables ebtables x_tables dm_snapshot dm_bufio 
dm_multipath br_netfilter bridge 8021q garp mrp stp llc ixgbe mdio tg3 bonding 
autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx4_en vxlan 
ip6_udp_tunnel udp_tunnel crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ttm 
aesni_intel drm_kms_helper aes_x86_64 lrw gf128mul syscopyarea glue_helper 
sysfillrect ablk_helper sysimgblt fb_sys_fops cryptd drm psmouse pata_acpi igb 
pata_atiixp hpsa dca ahci mlx4_core ptp libahci scsi_transport_sas pps_core 
i2c_algo_bit fjes
[149668.845132] CPU: 0 PID: 11227 Comm: kworker/u24:1 Not tainted 
4.4.0-87-generic #110-Ubuntu
[149668.845134] Hardware name: HP ProLiant SE4255e  /, BIOS A31 01/05/2013
[149668.845138] Workqueue: netns cleanup_net
[149668.845139]  0286 e218996f8a60a1fa 8802f3637ba0 
813f9903
[149668.845142]   81d75978 8802f3637bd8 
81081332
[149668.845144]  8806dd999400 8806dd99e800 0006 
8802f3637ca8
[149668.845146] Call Trace:
[149668.845151]  [] dump_stack+0x63/0x90
[149668.845154]  [] warn_slowpath_common+0x82/0xc0
[149668.845156]  [] warn_slowpath_null+0x1a/0x20
[149668.845158]  [] in6_dev_finish_destroy+0x6b/0xc0
[149668.845161]  [] ip6_route_dev_notify+0x116/0x130
[149668.845163]  [] notifier_call_chain+0x4a/0x70
[149668.845165]  [] raw_notifier_call_chain+0x16/0x20
[149668.845168]  [] call_netdevice_notifiers_info+0x35/0x60
[149668.845170]  [] netdev_run_todo+0x16d/0x320
[149668.845173]  [] rtnl_unlock+0xe/0x10
[149668.845175]  [] default_device_exit_batch+0x147/0x170
[149668.845179]  [] ? __wake_up_sync+0x20/0x20
[149668.845181]  [] ops_exit_list.isra.4+0x52/0x60
[149668.845183]  [] cleanup_net+0x1c2/0x2a0
[149668.845185]  [] process_one_work+0x165/0x480
[149668.845188]  [] worker_thread+0x4b/0x4c0
[149668.845190]  [] ? process_one_work+0x480/0x480
[149668.845192]  [] kthread+0xe5/0x100
[149668.845194]  [] ? kthread_create_on_node+0x1e0/0x1e0
[149668.845197]  [] ret_from_fork+0x3f/0x70
[149668.845199]  [] ? kthread_create_on_node+0x1e0/0x1e0
[149668.845200] ---[ end trace a70573408f354326 ]---

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

Title:
  System freeze after in6_dev_finish_destroy errors

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After the upgrade to the `4.4.0-83-generic #106~14.04.1-Ubuntu` kernel
  we are seeing system hangs with the following logs.  Prior to this
  upgrade there were no crashes or kernel traces of this sort.  We have
  ruled out physical hardware issues by moving the VM to another
  physical host.

  In the logs there's reference to docker instances on the host.  This
  results in veth devices being brought up and torn down frequently,
  which is likely related.

  As a possible workaround we have disabled IPv6 for now.

  ```
  kernel: [337352.274907] vethf317e0d: renamed from eth0
  kernel: [337352.386446] docker0: port 1(veth160ed4a) entered disabled state
  kernel: [337352.393444] docker0: port 

[Kernel-packages] [Bug 1701499] Re: System often freezes or panics if I log in with Dell Dock WD15 connected

[Mario Limonciello]

>From what I can tell you're on BIOS 1.3.3.  Please upgrade to 1.5.0.
It's available both for Ubuntu through fwupd
(https://fwupd.org/lvfs/device/34578c72-11dc-4378-bc7f-b643866f598c) or
can be updated from the F12 post menu by downloading from
support.dell.com
(https://www.dell.com/support/article/us/en/19/sln171755/updating-the-
dell-bios-in-linux-and-ubuntu-environments?lang=en#updatebios2015)

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

Title:
  System often freezes or panics if I log in with Dell Dock WD15
  connected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Dell Precision 5520 with Ubuntu 17.04.

  If I first start a Unity session and then connect Dell WD15 USB-C dock
  with an external diplay plugged in, the system detects it properly and
  all the things work flawlessly (ethernet, external keyboard, external
  display, external storage connected to USB on the dock). I can plug-in
  and plug-out the dock multiple times and it just works.

  However if I boot the laptop with the dock already plugged in, first I
  get to the login screen and initially all is ok. Both screens are
  activated, and I can log in using the keyboard connected to the dock.

  When I hit "Enter", both screens go blank for a while, then they turn
  back on and I can see the desktop. A second or maybe two seconds later
  things start falling apart. When I move the mouse pointer a second
  after logging, it is kinda "jumpy", the movement is not smooth. The
  move freezes for a few times. I observed this behaviour only when
  moving the wireless mouse connected to the USB of the laptop. The
  builtin touchpad works smoothly.

  If it was the only issue, this would be a very minor annoyance.
  Sometimes, after a few short mouse pointer freezes the system starts
  working smoothly and all is rock stable from that point. However quite
  often I noticed much worse things happen:

  1. The mouse pointer and everything freezes totally after a few
  seconds from displaying the desktop. It is not possible to switch to
  the console with Ctrl-Alt-F1. This happens in >50% of logins.

  2. Kernel panic.

  I observed this behavior with stable Ubuntu kernel 4.10.0-20, as well
  as 4.11.0 - 4.11.8 (which I'm using now, because 4.11.x seems more
  stable than 4.10.0-x) and also 4.12.rc5 which I tried once.

  Even if everything goes fine, I noticed the following errors printed
  in syslog. I'm not sure if they are related, but they look very iffy
  to me:

  Jun 30 10:46:23 p5520 kernel: [   38.391971] DMAR: DRHD: handling fault 
status reg 2
  Jun 30 10:46:23 p5520 kernel: [   38.391977] DMAR: [INTR-REMAP] Request 
device [3e:00.0] fault index 1e [fault reason 38] Blocked an interrupt request 
due to source-id verification failure
  Jun 30 10:46:23 p5520 kernel: [   38.472490] xhci_hcd :0a:00.0: remove, 
state 1
  Jun 30 10:46:23 p5520 kernel: [   38.472496] usb usb4: USB disconnect, device 
number 1
  Jun 30 10:46:23 p5520 kernel: [   38.472497] usb 4-1: USB disconnect, device 
number 2
  Jun 30 10:46:23 p5520 kernel: [   38.472498] usb 4-1.2: USB disconnect, 
device number 3
  Jun 30 10:46:23 p5520 NetworkManager[1129]:   [1498812383.7510] device 
(eth0): state change: disconnected -> unmanaged (reason 'removed') [30 10 36]
  Jun 30 10:46:23 p5520 ModemManager[1076]:   (net/eth0): released by 
modem 
/sys/devices/pci:00/:00:1d.6/:06:00.0/:07:02.0/:0a:00.0/usb4/4-1/4-1.2
  Jun 30 10:46:23 p5520 NetworkManager[1129]:   [1498812383.7537] devices 
removed (path: 
/sys/devices/pci:00/:00:1d.6/:06:00.0/:07:02.0/:0a:00.0/usb4/4-1/4-1.2/4-1.2:1.0/net/eth0,
 iface: eth0)
  Jun 30 10:46:23 p5520 kernel: [   38.552718] xhci_hcd :0a:00.0: Host halt 
failed, -19
  Jun 30 10:46:23 p5520 kernel: [   38.552721] xhci_hcd :0a:00.0: Host not 
accessible, reset failed.
  Jun 30 10:46:23 p5520 kernel: [   38.552722] xhci_hcd :0a:00.0: USB bus 4 
deregistered
  Jun 30 10:46:23 p5520 kernel: [   38.552728] xhci_hcd :0a:00.0: remove, 
state 1
  Jun 30 10:46:23 p5520 kernel: [   38.552731] usb usb3: USB disconnect, device 
number 1
  Jun 30 10:46:23 p5520 kernel: [   38.552732] usb 3-1: USB disconnect, device 
number 2
  Jun 30 10:46:23 p5520 kernel: [   38.552732] usb 3-1.5: USB disconnect, 
device number 3
  Jun 30 10:46:23 p5520 kernel: [   38.553322] usb 3-1.7: USB disconnect, 
device number 4
  Jun 30 10:46:23 p5520 kernel: [   38.556064] BUG: unable to handle kernel 
paging request at 002018387ad8
  Jun 30 10:46:23 p5520 kernel: [   38.556173] IP: __radix_tree_lookup+0x10/0xf0
  Jun 30 10:46:23 p5520 kernel: [   38.556230] PGD 0 
  Jun 30 10:46:23 p5520 kernel: [   38.556232] 
  Jun 30 10:46:24 p5520 kernel: [   38.556280] Oops:  [#1] SMP
  Jun 30 10:46:24 p5520 kernel: [   38.556320] Modules linked in: ccm rfcomm 
cdc_ether usbnet 

[Kernel-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[Brian Murray]

** Tags added: full-boot

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[Brian Murray]

** Changed in: dkms (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1559308] Re: Plugging HDMI screen in causes system hang

[johnnynobody]

I have this problem running 16.04.3 with the kernel package and drivers
from https://github.com/M-Bab/linux-kernel-amdgpu-binaries. Those
binaries are the only solution that I've found to fixing the problem of
the display going to a blank screen and won't "wake up". But when I try
to use the HDMI port the screen goes blank and won't wake up and nothing
gets displayed on the TV - I'm still able to ssh in from another PC and
reboot the PC that's "frozen" but I don't get a login screen if I leave
the HDMI cable plugged in. I have tried the oibaf and padoka
repositories, also, but that hasn't solved the problem either.

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

Title:
  Plugging HDMI screen in causes system hang

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I have a 4K UHD laptop screen and am running Ubuntu Gnome 16.04 Beta1
  using 4.4.0-13-generic and the Nouveau drivers.

  If I plug in an external HDMI monitor (FHD) either into either HDMI
  port (there's one on the machine and there's one available via a usb
  3.1 extra adaptor) then the whole system hangs, completely
  unresponsive and needing a hard reboot. Before hanging the 2nd display
  gets an image as expected, but the laptop's screen flashes randomly,
  sometimes you see weird artifacts. Then the hang comes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar 18 20:43:42 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06e4]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4]
  InstallationDate: Installed on 2016-03-15 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160225.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed 
root=UUID=b026feed-8801-44f4-9f3f-c245f4a1f25e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Mar 18 17:28:07 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   Unknown chipset: NV117
   SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5182 
   vendor SHP
  xserver.version: 2:1.18.1-1ubuntu4

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

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

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

[Ubuntu Kernel Bot]

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

Title:
  Bluetooth

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It seems that there is an issue with the Bluetooth connection for the
  linux system.. if i connect it starts off fine... but after a little
  bit it begins to slow my computer... specifically when watching
  youtube or streaming any video... at one point it actually crashed the
  OS... and i had to reboot from the repair options..

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50 [modified: 
boot/vmlinuz-4.4.0-31-generic]
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darkpirate   1946 F pulseaudio
   /dev/snd/controlC1:  darkpirate   1946 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 15 16:31:13 2017
  HibernationDevice: RESUME=UUID=4a471530-5e9d-4eb5-9272-a9630d8acccb
  InstallationDate: Installed on 2017-09-08 (6 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. Q302LAB
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=24233149-7a11-4b65-9166-1fe8959e4dc7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Q302LAB.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Q302LAB
  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.:bvrQ302LAB.203:bd11/27/2014:svnASUSTeKCOMPUTERINC.:pnQ302LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ302LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: Q302LAB
  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/1717607/+subscriptions

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

[Kernel-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[Brian Murray]

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

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

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1717607] [NEW] Bluetooth

[MIchael Galindo]

Public bug reported:

It seems that there is an issue with the Bluetooth connection for the
linux system.. if i connect it starts off fine... but after a little bit
it begins to slow my computer... specifically when watching youtube or
streaming any video... at one point it actually crashed the OS... and i
had to reboot from the repair options..

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-31-generic 4.4.0-31.50 [modified: 
boot/vmlinuz-4.4.0-31-generic]
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  darkpirate   1946 F pulseaudio
 /dev/snd/controlC1:  darkpirate   1946 F pulseaudio
CurrentDesktop: Unity
Date: Fri Sep 15 16:31:13 2017
HibernationDevice: RESUME=UUID=4a471530-5e9d-4eb5-9272-a9630d8acccb
InstallationDate: Installed on 2017-09-08 (6 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: ASUSTeK COMPUTER INC. Q302LAB
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=24233149-7a11-4b65-9166-1fe8959e4dc7 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-31-generic N/A
 linux-backports-modules-4.4.0-31-generic  N/A
 linux-firmware1.157.12
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/27/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: Q302LAB.203
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: Q302LAB
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.:bvrQ302LAB.203:bd11/27/2014:svnASUSTeKCOMPUTERINC.:pnQ302LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ302LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: Q302LAB
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug xenial

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

Title:
  Bluetooth

Status in linux package in Ubuntu:
  New

Bug description:
  It seems that there is an issue with the Bluetooth connection for the
  linux system.. if i connect it starts off fine... but after a little
  bit it begins to slow my computer... specifically when watching
  youtube or streaming any video... at one point it actually crashed the
  OS... and i had to reboot from the repair options..

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50 [modified: 
boot/vmlinuz-4.4.0-31-generic]
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darkpirate   1946 F pulseaudio
   /dev/snd/controlC1:  darkpirate   1946 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 15 16:31:13 2017
  HibernationDevice: RESUME=UUID=4a471530-5e9d-4eb5-9272-a9630d8acccb
  InstallationDate: Installed on 2017-09-08 (6 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. Q302LAB
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=24233149-7a11-4b65-9166-1fe8959e4dc7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Q302LAB.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Q302LAB
  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.:bvrQ302LAB.203:bd11/27/2014:svnASUSTeKCOMPUTERINC.:pnQ302LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ302LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: Q302LAB
  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/1717607/+subscriptions

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

[Kernel-packages] [Bug 1702910] Re: System freeze after in6_dev_finish_destroy errors

[Victor Palma]

I can confirm that this also happens with 4.4.0-87-generic.

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

Title:
  System freeze after in6_dev_finish_destroy errors

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After the upgrade to the `4.4.0-83-generic #106~14.04.1-Ubuntu` kernel
  we are seeing system hangs with the following logs.  Prior to this
  upgrade there were no crashes or kernel traces of this sort.  We have
  ruled out physical hardware issues by moving the VM to another
  physical host.

  In the logs there's reference to docker instances on the host.  This
  results in veth devices being brought up and torn down frequently,
  which is likely related.

  As a possible workaround we have disabled IPv6 for now.

  ```
  kernel: [337352.274907] vethf317e0d: renamed from eth0
  kernel: [337352.386446] docker0: port 1(veth160ed4a) entered disabled state
  kernel: [337352.393444] docker0: port 1(veth160ed4a) entered disabled state
  kernel: [337352.395408] device veth160ed4a left promiscuous mode
  kernel: [337352.395417] docker0: port 1(veth160ed4a) entered disabled state
  kernel: [337359.301576] vethee2599d: renamed from eth0
  kernel: [337359.339582] docker0: port 2(veth3100aab) entered disabled state
  kernel: [337359.343059] docker0: port 2(veth3100aab) entered disabled state
  kernel: [337359.344987] device veth3100aab left promiscuous mode
  kernel: [337359.344997] docker0: port 2(veth3100aab) entered disabled state
  kernel: [337475.398358] [ cut here ]
  kernel: [337475.398370] WARNING: CPU: 3 PID: 23671 at 
/build/linux-lts-xenial-ep3zLI/linux-lts-xenial-4.4.0/net/ipv6/addrconf_core.c:159
 in6_dev_f

  kernel: [337475.398372] Modules linked in: btrfs xor raid6_pq ufs qnx4 
hfsplus hfs minix ntfs msdos jfs xfs libcrc32c veth ip6table_filter ip6_tab
  comment ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_fil
  filter bridge stp llc aufs tcp_diag inet_diag coretemp crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel ppdev aes_x86_64 lrw gf128mul
  input_leds serio_raw drm_kms_helper parport_pc drm lp fb_sys_fops syscopyarea 
sysfillrect sysimgblt vmw_vmci parport shpchp 8250_fintek i2c_piix4

  kernel: [337475.398416] CPU: 3 PID: 23671 Comm: kworker/u8:0 Not tainted 
4.4.0-83-generic #106~14.04.1-Ubuntu
  kernel: [337475.398418] Hardware name: VMware, Inc. VMware Virtual 
Platform/440BX Desktop Reference Platform, BIOS 6.00 09/17/2015
  kernel: [337475.398423] Workqueue: netns cleanup_net
  kernel: [337475.398424]   8801b197fbb8 813ddefc 

  kernel: [337475.398427]  81d7aa10 8801b197fbf0 8107ea36 
88016f97d400
  kernel: [337475.398428]  88016f97e800 0006 8801b197fcc0 

  kernel: [337475.398430] Call Trace:
  kernel: [337475.398435]  [] dump_stack+0x63/0x87
  kernel: [337475.398440]  [] warn_slowpath_common+0x86/0xc0
  kernel: [337475.398442]  [] warn_slowpath_null+0x1a/0x20
  kernel: [337475.398444]  [] in6_dev_finish_destroy+0x6b/0xb0
  kernel: [337475.398447]  [] ip6_route_dev_notify+0x110/0x130
  kernel: [337475.398450]  [] notifier_call_chain+0x49/0x70
  kernel: [337475.398452]  [] 
raw_notifier_call_chain+0x16/0x20
  kernel: [337475.398455]  [] 
call_netdevice_notifiers_info+0x35/0x60
  kernel: [337475.398458]  [] netdev_run_todo+0x157/0x300
  kernel: [337475.398461]  [] ? 
rollback_registered_many+0x22e/0x2e0
  kernel: [337475.398463]  [] rtnl_unlock+0xe/0x10
  kernel: [337475.398464]  [] 
default_device_exit_batch+0x138/0x150
  kernel: [337475.398468]  [] ? __wake_up_sync+0x20/0x20
  kernel: [337475.398470]  [] ops_exit_list.isra.4+0x52/0x60
  kernel: [337475.398472]  [] cleanup_net+0x1b3/0x280
  kernel: [337475.398476]  [] process_one_work+0x150/0x3f0
  kernel: [337475.398478]  [] worker_thread+0x11a/0x470
  kernel: [337475.398481]  [] ? __schedule+0x359/0x980
  kernel: [337475.398483]  [] ? rescuer_thread+0x310/0x310
  kernel: [337475.398484]  [] kthread+0xd6/0xf0
  kernel: [337475.398486]  [] ? kthread_park+0x60/0x60
  kernel: [337475.398488]  [] ret_from_fork+0x3f/0x70
  kernel: [337475.398490]  [] ? kthread_park+0x60/0x60
  kernel: [337475.398491] ---[ end trace 6d63274dc9a3dbec ]---
  kernel: [337475.398492] [ cut here ]

  ```

  ProblemType: Bug
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: amd64
  Date: Fri Jul  7 13:59:36 2017
  Dependencies:
   adduser 3.113+nmu3ubuntu3
   apt-utils 1.0.1ubuntu2.17
   base-passwd 3.5.33
   busybox-initramfs 1:1.21.0-1ubuntu1
   coreutils 8.21-1ubuntu5.4
   cpio 2.11+dfsg-1ubuntu1.2
   dbus 1.6.18-0ubuntu4.5
   debconf 1.5.51ubuntu2
   debconf-i18n 1.5.51ubuntu2
   debianutils 4.4
   dmsetup 2:1.02.77-6ubuntu2
   dpkg 1.17.5ubuntu5.7
   e2fslibs 

[Kernel-packages] [Bug 1716033] Re: [SRU][Zesty] enable TPM CRB driver on ARM64 for Qualcomm Centriq 2400

[Jeffrey Hugo]

Validated.

root@ubuntu:/home/ubuntu/andy/ibmtss930/utils# ./reg.sh -1
init tpm done

Initialize Regression Test Keys

Create a platform primary storage key
 INFO:
Create a storage key under the primary key
 INFO:
Create an unrestricted RSA signing key under the primary key
 INFO:
Create an unrestricted ECC signing key under the primary key
 INFO:
Create a restricted signing key under the primary key
 INFO:
Create an RSA decryption key under the primary key
 INFO:
Create a symmetric cipher key under the primary key
 INFO:
Create a sha1 keyed hash key under the primary key
 INFO:
Create a sha256 keyed hash key under the primary key
 INFO:

Random Number Generator

Stir Random
 INFO:
Get Random
 INFO:

Success - 1 Tests 0 Warnings

root@ubuntu:/home/ubuntu/andy/ibmtss930/utils#

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

Title:
  [SRU][Zesty]  enable TPM CRB driver on ARM64 for Qualcomm Centriq 2400

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Enable TPM CRB driver on ARM64 for Qualcomm Centriq 2400. Where, control area 
buffer address is greater than 32-bit.

  [Test]
  Currently only built for X64 & ACPI. 

  [Fix]
  This is upstream:
  19b7bf51fc3d tpm, tpm_crb: Handle 64-bit resource in crb_check_resource()
  08eff49d63ca tpm/tpm_crb: Enable TPM CRB interface for ARM64

  [Regression Potential]
  None.

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

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

[Kernel-packages] [Bug 1679208] Re: Zesty (4.10.0-14) won't boot on HP ProLiant DL360 Gen9 with intel_iommu=on

[Narinder Gupta]

I have subscribed to HPE Eddie and Ganesh to this bug whether they have
tested this with old kernel or some parameter needs to be added.

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

Title:
  Zesty (4.10.0-14) won't boot on HP ProLiant DL360 Gen9 with
  intel_iommu=on

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  TL;DR
  - one of our HP ProLiant DL360 Gen9 fails to boot with intel_iommu=on
  - the Disk controller fails
  - Xenial seems to work for a while but then fails
  - Zesty 100% crashes on boot
  - An identical system seems to work, so need HW replace to finally confirm

  After reboot one sees a HW report like this:
  After the boot I see the HW telling me this on boot:
  Embedded RAID : Smart HBA H240ar Controller - Operation Failed
   - 1719-Slot 0 Drive Array  - A controller failure event occurred prior
 to this power-up. (Previous lock up code = 0x13)

  
  I tried several things (In between always redeploy zesty with MAAS).
  I think my debugging might be helpful, but I wanted to keep the documentation 
in the bug in case you'd go another route or that others find useful 
information in here.

  0. I retried what I did twice, fully reproducible
 That is:
 0.1 install zesty 
 0.2 change grub default cmdline in /etc/default/grub.d/50- to add 
intel_iommu=on
 0.3 sudo update-grub
 0.4 reboot


  1. I tried a Recovery boot from the boot options in gub.
 => Failed as well


  2. iLO rebooted vis "request reboot" and as well via "full system reset"
 => both Failed


  3. Reboot the system as deployed by MAAS
 # /proc/cmdline before that
 BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=2137c19a-d441-43fa-82e2-f2b7e3b2727b ro
 The orig grub.cfg is like http://paste.ubuntu.com/24305945/
 It reboots as-is.
 => Reboot worked


  4. without a change to anything in /etc run update-grub
 $ sudo update-grub
 Generating grub configuration file ...
 Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT 
is set is no longer supported.
 Found linux image: /boot/vmlinuz-4.10.0-14-generic
 Found initrd image: /boot/initrd.img-4.10.0-14-generic
 Adding boot menu entry for EFI firmware configuration
 done

 There was no diff between the new grub.cfg and the one I saved.
 => Reboot worked


  5. add the intel_iommu=on arg
$ sudo sed -i 
's/GRUB_CMDLINE_LINUX_DEFAULT=""/GRUB_CMDLINE_LINUX_DEFAULT="intel_iommu=on"/' 
/etc/default/grub.d/50-curtin-settings.cfg
$ sudo update-grub
# Diff in grub.cfg really only is the iommu setting
=> Reboot Failed
So this doesn't seem so much of a cloud-init/curtin/maas bug anymore to me 
- maybe intel_iommu bheaves different?
  - Check grub cfg pre/post - not change but the expected?


  6. Install Xenial and do the same
 => Reboot working


  7. Upgrade to Z
 Since the Xenial system just worked and one can assume that almost only 
kernel is working so early in the boot process I upgraded the working system 
with intel_iommu=on to Zesty.
 That would be 4.4.0-71-generic to 4.10.0-1
 On this upgrade I finally saw my I/O errors again :-/
 Note: these issues are hard to miss as they mount root as read-only.
 I wonder if they only ever appear with intel_iommu=on as this is the only 
combo I ever saw them,


  8. Redeploy and upgrade to Z without intel_iommu=on enabled
 Then enable intel_iommu=on and reboot
 => Reboot Fail
 From here I rebooted into the Xenial kerenl (that since this is an update 
was still there)
 Here I saw:
  Loading Linux 4.4.0-71-generic ...
  Loading initial ramdisk ...
  error: invalid video mode specification `text'.
  Booting in blind mode
 Hrm, as outlined above the "blind mode" might be a red herring, but since 
this kernel worked before it might still be a red herring that swims in the 
initrd that got regenerated on the upgrade.
 => Xenial Kernel Reboot - works !!
 So "blind mode" is a red herring of some sort.
 
 But this might allow to find some logs
 => No
 This appears as if the Failing boot has never made it to the point to 
actually write anything.
 I see:
  1. the original xenial
  2. the upgraded zesty
  3. NOT THE zesty+iommu
  4. the xenial+iommu

  $ egrep 'kernel:.*(Linux version|Command line)' /var/log/syslog 
  Apr  3 12:15:20 node-horsea kernel: [0.00] Linux version 
4.4.0-71-generic (buildd@lcy01-05) (gcc version 5.4.0 20160609 (Ubuntu 
5.4.0-6ubuntu1~16.04.4) ) #92-Ubuntu SMP Fri Mar 24 12:59:01 UTC 2017 (Ubuntu 
4.4.0-71.92-generic 4.4.49)
  Apr  3 12:15:20 node-horsea kernel: [0.00] Command line: 
BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic 
root=UUID=2137c19a-d441-43fa-82e2-f2b7e3b2727b ro
  Apr  3 12:47:45 node-horsea kernel: [0.00] Linux version 

[Kernel-packages] [Bug 1716626] Re: linux: 3.19.0-93.101 -proposed tracker

[Brad Figg]

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

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

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

** Tags removed: block-proposed-vivid

** Tags removed: block-proposed

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

Title:
  linux: 3.19.0-93.101 -proposed tracker

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

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

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

  backports: 1716628
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1716626/+subscriptions

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

[Kernel-packages] [Bug 1717581] Re: linux 4.13.0-11.12 ADT test failure with linux 4.13.0-11.12

[Seth Forshee]

memory-hotplug kselftest is failing. A bug in the test means it wasn't
actually doing anything before, so possibly this doesn't represent an
actual regression vs. previous artful kernels. However the test does
pass in xenial so it warrants investigation.

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

Title:
  linux 4.13.0-11.12 ADT test failure with linux 4.13.0-11.12

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Testing failed on:
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/i386/l/linux/20170914_153408_2e966@/log.gz

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

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

[Kernel-packages] [Bug 1717581] [NEW] linux 4.13.0-11.12 ADT test failure with linux 4.13.0-11.12

[Seth Forshee]

Public bug reported:

Testing failed on:
i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/i386/l/linux/20170914_153408_2e966@/log.gz

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

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

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

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

Title:
  linux 4.13.0-11.12 ADT test failure with linux 4.13.0-11.12

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Testing failed on:
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/i386/l/linux/20170914_153408_2e966@/log.gz

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

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

[Kernel-packages] [Bug 1482390] UdevDb.txt

[Tiago Ramos]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1482390/+attachment/4950805/+files/UdevDb.txt

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

Title:
  ASUS UX305LA - Battery state not detected correctly

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Whether the AC adapter is connected or not, the battery is always
  detected as discharging:

  When AC adapter is present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%
    AC adapter : online

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54027 mWh, 100.0%
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 0 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  When AC adapter is not present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%, 04:19:49
    AC adapter : off-line

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54005 mWh, 100.0%, 04:28:31
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 12067 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  System information:

  $ sudo dmidecode
  # dmidecode 2.12
  # SMBIOS entry point at 0xace2a898
  SMBIOS 2.8 present.
  27 structures occupying 2154 bytes.
  Table at 0xAC7C6000.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
   Vendor: American Megatrends Inc.
   Version: UX305LA.202
   Release Date: 04/16/2015
   Address: 0xF
   Runtime Size: 64 kB
   ROM Size: 6464 kB
   Characteristics:
    PCI is supported
    BIOS is upgradeable
    BIOS shadowing is allowed
    Boot from CD is supported
    Selectable boot is supported
    BIOS ROM is socketed
    EDD is supported
    5.25"/1.2 MB floppy services are supported (int 13h)
    3.5"/720 kB floppy services are supported (int 13h)
    3.5"/2.88 MB floppy services are supported (int 13h)
    Print screen service is supported (int 5h)
    8042 keyboard services are supported (int 9h)
    Serial services are supported (int 14h)
    Printer services are supported (int 17h)
    ACPI is supported
    USB legacy is supported
    Smart battery is supported
    BIOS boot specification is supported
    Targeted content distribution is supported
    UEFI is supported
   BIOS Revision: 5.6

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   UUID: xxx
   Wake-up Type: Power Switch
   SKU Number: ASUS-NotebookSKU
   Family: UX

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Features:
    Board is a hosting board
    Board is replaceable
   Location In Chassis: MIDDLE
   Chassis Handle: 0x0003
   Type: Motherboard
   Contained Object Handles: 0

  Handle 0x0003, DMI type 3, 25 bytes
  Chassis Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Type: Notebook
   Lock: Not Present
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Boot-up State: Safe
   Power Supply State: Safe
   Thermal State: Safe
   Security Status: None
   OEM Information: 0x
   Height: Unspecified
   Number Of Power Cords: 1
   Contained Elements: 1
     (0)
   SKU Number: To be filled by O.E.M.

  Handle 0x0004, DMI type 10, 26 bytes
  On Board Device 1 Information
   Type: Video
   Status: Enabled
   Description:  VGA
  On Board Device 2 Information
   Type: Ethernet
   Status: Enabled
   Description:  GLAN
  On Board Device 3 Information
   Type: Ethernet
   Status: Enabled
   Description:  WLAN
  On Board Device 4 Information
   Type: Sound
   Status: Enabled
   Description:  Audio CODEC
  On Board Device 5 Information
   Type: SATA Controller
   Status: Enabled
   Description:  SATA Controller
  On Board Device 6 Information
   Type: Other
   Status: Enabled
   Description:  USB 2.0 Controller
  On Board Device 7 Information
   Type: Other
   Status: Enabled
   Description:  USB 3.0 Controller
  On Board Device 8 Information
   Type: Other
   Status: Enabled
   Description:  SMBus Controller
  On Board Device 9 Information
   Type: Other
   Status: Enabled
   Description:  Card Reader
  On Board Device 10 Information
   Type: Other
   Status: Enabled
   Description:  Cmos Camera
  On Board Device 11 Information
   Type: Other
   Status: Enabled
   Description:  Bluetooth

  Handle 0x0005, DMI type 11, 5 bytes
  OEM Strings
   String 1:
   String 2:
   String 3:
   String 4: 90NB08T5-M00230
   String 5:
  

[Kernel-packages] [Bug 1482390] RfKill.txt

[Tiago Ramos]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1482390/+attachment/4950804/+files/RfKill.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/1482390

Title:
  ASUS UX305LA - Battery state not detected correctly

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Whether the AC adapter is connected or not, the battery is always
  detected as discharging:

  When AC adapter is present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%
    AC adapter : online

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54027 mWh, 100.0%
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 0 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  When AC adapter is not present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%, 04:19:49
    AC adapter : off-line

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54005 mWh, 100.0%, 04:28:31
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 12067 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  System information:

  $ sudo dmidecode
  # dmidecode 2.12
  # SMBIOS entry point at 0xace2a898
  SMBIOS 2.8 present.
  27 structures occupying 2154 bytes.
  Table at 0xAC7C6000.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
   Vendor: American Megatrends Inc.
   Version: UX305LA.202
   Release Date: 04/16/2015
   Address: 0xF
   Runtime Size: 64 kB
   ROM Size: 6464 kB
   Characteristics:
    PCI is supported
    BIOS is upgradeable
    BIOS shadowing is allowed
    Boot from CD is supported
    Selectable boot is supported
    BIOS ROM is socketed
    EDD is supported
    5.25"/1.2 MB floppy services are supported (int 13h)
    3.5"/720 kB floppy services are supported (int 13h)
    3.5"/2.88 MB floppy services are supported (int 13h)
    Print screen service is supported (int 5h)
    8042 keyboard services are supported (int 9h)
    Serial services are supported (int 14h)
    Printer services are supported (int 17h)
    ACPI is supported
    USB legacy is supported
    Smart battery is supported
    BIOS boot specification is supported
    Targeted content distribution is supported
    UEFI is supported
   BIOS Revision: 5.6

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   UUID: xxx
   Wake-up Type: Power Switch
   SKU Number: ASUS-NotebookSKU
   Family: UX

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Features:
    Board is a hosting board
    Board is replaceable
   Location In Chassis: MIDDLE
   Chassis Handle: 0x0003
   Type: Motherboard
   Contained Object Handles: 0

  Handle 0x0003, DMI type 3, 25 bytes
  Chassis Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Type: Notebook
   Lock: Not Present
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Boot-up State: Safe
   Power Supply State: Safe
   Thermal State: Safe
   Security Status: None
   OEM Information: 0x
   Height: Unspecified
   Number Of Power Cords: 1
   Contained Elements: 1
     (0)
   SKU Number: To be filled by O.E.M.

  Handle 0x0004, DMI type 10, 26 bytes
  On Board Device 1 Information
   Type: Video
   Status: Enabled
   Description:  VGA
  On Board Device 2 Information
   Type: Ethernet
   Status: Enabled
   Description:  GLAN
  On Board Device 3 Information
   Type: Ethernet
   Status: Enabled
   Description:  WLAN
  On Board Device 4 Information
   Type: Sound
   Status: Enabled
   Description:  Audio CODEC
  On Board Device 5 Information
   Type: SATA Controller
   Status: Enabled
   Description:  SATA Controller
  On Board Device 6 Information
   Type: Other
   Status: Enabled
   Description:  USB 2.0 Controller
  On Board Device 7 Information
   Type: Other
   Status: Enabled
   Description:  USB 3.0 Controller
  On Board Device 8 Information
   Type: Other
   Status: Enabled
   Description:  SMBus Controller
  On Board Device 9 Information
   Type: Other
   Status: Enabled
   Description:  Card Reader
  On Board Device 10 Information
   Type: Other
   Status: Enabled
   Description:  Cmos Camera
  On Board Device 11 Information
   Type: Other
   Status: Enabled
   Description:  Bluetooth

  Handle 0x0005, DMI type 11, 5 bytes
  OEM Strings
   String 1:
   String 2:
   String 3:
   String 4: 90NB08T5-M00230
   String 5:
  

[Kernel-packages] [Bug 1482390] WifiSyslog.txt

[Tiago Ramos]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1482390/+attachment/4950806/+files/WifiSyslog.txt

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

Title:
  ASUS UX305LA - Battery state not detected correctly

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Whether the AC adapter is connected or not, the battery is always
  detected as discharging:

  When AC adapter is present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%
    AC adapter : online

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54027 mWh, 100.0%
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 0 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  When AC adapter is not present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%, 04:19:49
    AC adapter : off-line

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54005 mWh, 100.0%, 04:28:31
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 12067 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  System information:

  $ sudo dmidecode
  # dmidecode 2.12
  # SMBIOS entry point at 0xace2a898
  SMBIOS 2.8 present.
  27 structures occupying 2154 bytes.
  Table at 0xAC7C6000.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
   Vendor: American Megatrends Inc.
   Version: UX305LA.202
   Release Date: 04/16/2015
   Address: 0xF
   Runtime Size: 64 kB
   ROM Size: 6464 kB
   Characteristics:
    PCI is supported
    BIOS is upgradeable
    BIOS shadowing is allowed
    Boot from CD is supported
    Selectable boot is supported
    BIOS ROM is socketed
    EDD is supported
    5.25"/1.2 MB floppy services are supported (int 13h)
    3.5"/720 kB floppy services are supported (int 13h)
    3.5"/2.88 MB floppy services are supported (int 13h)
    Print screen service is supported (int 5h)
    8042 keyboard services are supported (int 9h)
    Serial services are supported (int 14h)
    Printer services are supported (int 17h)
    ACPI is supported
    USB legacy is supported
    Smart battery is supported
    BIOS boot specification is supported
    Targeted content distribution is supported
    UEFI is supported
   BIOS Revision: 5.6

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   UUID: xxx
   Wake-up Type: Power Switch
   SKU Number: ASUS-NotebookSKU
   Family: UX

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Features:
    Board is a hosting board
    Board is replaceable
   Location In Chassis: MIDDLE
   Chassis Handle: 0x0003
   Type: Motherboard
   Contained Object Handles: 0

  Handle 0x0003, DMI type 3, 25 bytes
  Chassis Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Type: Notebook
   Lock: Not Present
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Boot-up State: Safe
   Power Supply State: Safe
   Thermal State: Safe
   Security Status: None
   OEM Information: 0x
   Height: Unspecified
   Number Of Power Cords: 1
   Contained Elements: 1
     (0)
   SKU Number: To be filled by O.E.M.

  Handle 0x0004, DMI type 10, 26 bytes
  On Board Device 1 Information
   Type: Video
   Status: Enabled
   Description:  VGA
  On Board Device 2 Information
   Type: Ethernet
   Status: Enabled
   Description:  GLAN
  On Board Device 3 Information
   Type: Ethernet
   Status: Enabled
   Description:  WLAN
  On Board Device 4 Information
   Type: Sound
   Status: Enabled
   Description:  Audio CODEC
  On Board Device 5 Information
   Type: SATA Controller
   Status: Enabled
   Description:  SATA Controller
  On Board Device 6 Information
   Type: Other
   Status: Enabled
   Description:  USB 2.0 Controller
  On Board Device 7 Information
   Type: Other
   Status: Enabled
   Description:  USB 3.0 Controller
  On Board Device 8 Information
   Type: Other
   Status: Enabled
   Description:  SMBus Controller
  On Board Device 9 Information
   Type: Other
   Status: Enabled
   Description:  Card Reader
  On Board Device 10 Information
   Type: Other
   Status: Enabled
   Description:  Cmos Camera
  On Board Device 11 Information
   Type: Other
   Status: Enabled
   Description:  Bluetooth

  Handle 0x0005, DMI type 11, 5 bytes
  OEM Strings
   String 1:
   String 2:
   String 3:
   String 4: 90NB08T5-M00230
   

[Kernel-packages] [Bug 1482390] ProcEnviron.txt

[Tiago Ramos]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1482390/+attachment/4950800/+files/ProcEnviron.txt

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

Title:
  ASUS UX305LA - Battery state not detected correctly

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Whether the AC adapter is connected or not, the battery is always
  detected as discharging:

  When AC adapter is present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%
    AC adapter : online

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54027 mWh, 100.0%
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 0 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  When AC adapter is not present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%, 04:19:49
    AC adapter : off-line

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54005 mWh, 100.0%, 04:28:31
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 12067 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  System information:

  $ sudo dmidecode
  # dmidecode 2.12
  # SMBIOS entry point at 0xace2a898
  SMBIOS 2.8 present.
  27 structures occupying 2154 bytes.
  Table at 0xAC7C6000.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
   Vendor: American Megatrends Inc.
   Version: UX305LA.202
   Release Date: 04/16/2015
   Address: 0xF
   Runtime Size: 64 kB
   ROM Size: 6464 kB
   Characteristics:
    PCI is supported
    BIOS is upgradeable
    BIOS shadowing is allowed
    Boot from CD is supported
    Selectable boot is supported
    BIOS ROM is socketed
    EDD is supported
    5.25"/1.2 MB floppy services are supported (int 13h)
    3.5"/720 kB floppy services are supported (int 13h)
    3.5"/2.88 MB floppy services are supported (int 13h)
    Print screen service is supported (int 5h)
    8042 keyboard services are supported (int 9h)
    Serial services are supported (int 14h)
    Printer services are supported (int 17h)
    ACPI is supported
    USB legacy is supported
    Smart battery is supported
    BIOS boot specification is supported
    Targeted content distribution is supported
    UEFI is supported
   BIOS Revision: 5.6

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   UUID: xxx
   Wake-up Type: Power Switch
   SKU Number: ASUS-NotebookSKU
   Family: UX

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Features:
    Board is a hosting board
    Board is replaceable
   Location In Chassis: MIDDLE
   Chassis Handle: 0x0003
   Type: Motherboard
   Contained Object Handles: 0

  Handle 0x0003, DMI type 3, 25 bytes
  Chassis Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Type: Notebook
   Lock: Not Present
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Boot-up State: Safe
   Power Supply State: Safe
   Thermal State: Safe
   Security Status: None
   OEM Information: 0x
   Height: Unspecified
   Number Of Power Cords: 1
   Contained Elements: 1
     (0)
   SKU Number: To be filled by O.E.M.

  Handle 0x0004, DMI type 10, 26 bytes
  On Board Device 1 Information
   Type: Video
   Status: Enabled
   Description:  VGA
  On Board Device 2 Information
   Type: Ethernet
   Status: Enabled
   Description:  GLAN
  On Board Device 3 Information
   Type: Ethernet
   Status: Enabled
   Description:  WLAN
  On Board Device 4 Information
   Type: Sound
   Status: Enabled
   Description:  Audio CODEC
  On Board Device 5 Information
   Type: SATA Controller
   Status: Enabled
   Description:  SATA Controller
  On Board Device 6 Information
   Type: Other
   Status: Enabled
   Description:  USB 2.0 Controller
  On Board Device 7 Information
   Type: Other
   Status: Enabled
   Description:  USB 3.0 Controller
  On Board Device 8 Information
   Type: Other
   Status: Enabled
   Description:  SMBus Controller
  On Board Device 9 Information
   Type: Other
   Status: Enabled
   Description:  Card Reader
  On Board Device 10 Information
   Type: Other
   Status: Enabled
   Description:  Cmos Camera
  On Board Device 11 Information
   Type: Other
   Status: Enabled
   Description:  Bluetooth

  Handle 0x0005, DMI type 11, 5 bytes
  OEM Strings
   String 1:
   String 2:
   String 3:
   String 4: 90NB08T5-M00230
   

[Kernel-packages] [Bug 1482390] ProcInterrupts.txt

[Tiago Ramos]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1482390/+attachment/4950801/+files/ProcInterrupts.txt

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

Title:
  ASUS UX305LA - Battery state not detected correctly

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Whether the AC adapter is connected or not, the battery is always
  detected as discharging:

  When AC adapter is present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%
    AC adapter : online

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54027 mWh, 100.0%
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 0 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  When AC adapter is not present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%, 04:19:49
    AC adapter : off-line

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54005 mWh, 100.0%, 04:28:31
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 12067 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  System information:

  $ sudo dmidecode
  # dmidecode 2.12
  # SMBIOS entry point at 0xace2a898
  SMBIOS 2.8 present.
  27 structures occupying 2154 bytes.
  Table at 0xAC7C6000.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
   Vendor: American Megatrends Inc.
   Version: UX305LA.202
   Release Date: 04/16/2015
   Address: 0xF
   Runtime Size: 64 kB
   ROM Size: 6464 kB
   Characteristics:
    PCI is supported
    BIOS is upgradeable
    BIOS shadowing is allowed
    Boot from CD is supported
    Selectable boot is supported
    BIOS ROM is socketed
    EDD is supported
    5.25"/1.2 MB floppy services are supported (int 13h)
    3.5"/720 kB floppy services are supported (int 13h)
    3.5"/2.88 MB floppy services are supported (int 13h)
    Print screen service is supported (int 5h)
    8042 keyboard services are supported (int 9h)
    Serial services are supported (int 14h)
    Printer services are supported (int 17h)
    ACPI is supported
    USB legacy is supported
    Smart battery is supported
    BIOS boot specification is supported
    Targeted content distribution is supported
    UEFI is supported
   BIOS Revision: 5.6

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   UUID: xxx
   Wake-up Type: Power Switch
   SKU Number: ASUS-NotebookSKU
   Family: UX

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Features:
    Board is a hosting board
    Board is replaceable
   Location In Chassis: MIDDLE
   Chassis Handle: 0x0003
   Type: Motherboard
   Contained Object Handles: 0

  Handle 0x0003, DMI type 3, 25 bytes
  Chassis Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Type: Notebook
   Lock: Not Present
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Boot-up State: Safe
   Power Supply State: Safe
   Thermal State: Safe
   Security Status: None
   OEM Information: 0x
   Height: Unspecified
   Number Of Power Cords: 1
   Contained Elements: 1
     (0)
   SKU Number: To be filled by O.E.M.

  Handle 0x0004, DMI type 10, 26 bytes
  On Board Device 1 Information
   Type: Video
   Status: Enabled
   Description:  VGA
  On Board Device 2 Information
   Type: Ethernet
   Status: Enabled
   Description:  GLAN
  On Board Device 3 Information
   Type: Ethernet
   Status: Enabled
   Description:  WLAN
  On Board Device 4 Information
   Type: Sound
   Status: Enabled
   Description:  Audio CODEC
  On Board Device 5 Information
   Type: SATA Controller
   Status: Enabled
   Description:  SATA Controller
  On Board Device 6 Information
   Type: Other
   Status: Enabled
   Description:  USB 2.0 Controller
  On Board Device 7 Information
   Type: Other
   Status: Enabled
   Description:  USB 3.0 Controller
  On Board Device 8 Information
   Type: Other
   Status: Enabled
   Description:  SMBus Controller
  On Board Device 9 Information
   Type: Other
   Status: Enabled
   Description:  Card Reader
  On Board Device 10 Information
   Type: Other
   Status: Enabled
   Description:  Cmos Camera
  On Board Device 11 Information
   Type: Other
   Status: Enabled
   Description:  Bluetooth

  Handle 0x0005, DMI type 11, 5 bytes
  OEM Strings
   String 1:
   String 2:
   String 3:
   String 4: 

[Kernel-packages] [Bug 1482390] ProcCpuinfoMinimal.txt

[Tiago Ramos]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1482390/+attachment/4950799/+files/ProcCpuinfoMinimal.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/1482390

Title:
  ASUS UX305LA - Battery state not detected correctly

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Whether the AC adapter is connected or not, the battery is always
  detected as discharging:

  When AC adapter is present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%
    AC adapter : online

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54027 mWh, 100.0%
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 0 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  When AC adapter is not present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%, 04:19:49
    AC adapter : off-line

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54005 mWh, 100.0%, 04:28:31
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 12067 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  System information:

  $ sudo dmidecode
  # dmidecode 2.12
  # SMBIOS entry point at 0xace2a898
  SMBIOS 2.8 present.
  27 structures occupying 2154 bytes.
  Table at 0xAC7C6000.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
   Vendor: American Megatrends Inc.
   Version: UX305LA.202
   Release Date: 04/16/2015
   Address: 0xF
   Runtime Size: 64 kB
   ROM Size: 6464 kB
   Characteristics:
    PCI is supported
    BIOS is upgradeable
    BIOS shadowing is allowed
    Boot from CD is supported
    Selectable boot is supported
    BIOS ROM is socketed
    EDD is supported
    5.25"/1.2 MB floppy services are supported (int 13h)
    3.5"/720 kB floppy services are supported (int 13h)
    3.5"/2.88 MB floppy services are supported (int 13h)
    Print screen service is supported (int 5h)
    8042 keyboard services are supported (int 9h)
    Serial services are supported (int 14h)
    Printer services are supported (int 17h)
    ACPI is supported
    USB legacy is supported
    Smart battery is supported
    BIOS boot specification is supported
    Targeted content distribution is supported
    UEFI is supported
   BIOS Revision: 5.6

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   UUID: xxx
   Wake-up Type: Power Switch
   SKU Number: ASUS-NotebookSKU
   Family: UX

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Features:
    Board is a hosting board
    Board is replaceable
   Location In Chassis: MIDDLE
   Chassis Handle: 0x0003
   Type: Motherboard
   Contained Object Handles: 0

  Handle 0x0003, DMI type 3, 25 bytes
  Chassis Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Type: Notebook
   Lock: Not Present
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Boot-up State: Safe
   Power Supply State: Safe
   Thermal State: Safe
   Security Status: None
   OEM Information: 0x
   Height: Unspecified
   Number Of Power Cords: 1
   Contained Elements: 1
     (0)
   SKU Number: To be filled by O.E.M.

  Handle 0x0004, DMI type 10, 26 bytes
  On Board Device 1 Information
   Type: Video
   Status: Enabled
   Description:  VGA
  On Board Device 2 Information
   Type: Ethernet
   Status: Enabled
   Description:  GLAN
  On Board Device 3 Information
   Type: Ethernet
   Status: Enabled
   Description:  WLAN
  On Board Device 4 Information
   Type: Sound
   Status: Enabled
   Description:  Audio CODEC
  On Board Device 5 Information
   Type: SATA Controller
   Status: Enabled
   Description:  SATA Controller
  On Board Device 6 Information
   Type: Other
   Status: Enabled
   Description:  USB 2.0 Controller
  On Board Device 7 Information
   Type: Other
   Status: Enabled
   Description:  USB 3.0 Controller
  On Board Device 8 Information
   Type: Other
   Status: Enabled
   Description:  SMBus Controller
  On Board Device 9 Information
   Type: Other
   Status: Enabled
   Description:  Card Reader
  On Board Device 10 Information
   Type: Other
   Status: Enabled
   Description:  Cmos Camera
  On Board Device 11 Information
   Type: Other
   Status: Enabled
   Description:  Bluetooth

  Handle 0x0005, DMI type 11, 5 bytes
  OEM Strings
   String 1:
   String 2:
   String 3:
   String 4: 

[Kernel-packages] [Bug 1482390] PulseList.txt

[Tiago Ramos]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1482390/+attachment/4950803/+files/PulseList.txt

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

Title:
  ASUS UX305LA - Battery state not detected correctly

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Whether the AC adapter is connected or not, the battery is always
  detected as discharging:

  When AC adapter is present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%
    AC adapter : online

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54027 mWh, 100.0%
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 0 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  When AC adapter is not present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%, 04:19:49
    AC adapter : off-line

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54005 mWh, 100.0%, 04:28:31
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 12067 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  System information:

  $ sudo dmidecode
  # dmidecode 2.12
  # SMBIOS entry point at 0xace2a898
  SMBIOS 2.8 present.
  27 structures occupying 2154 bytes.
  Table at 0xAC7C6000.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
   Vendor: American Megatrends Inc.
   Version: UX305LA.202
   Release Date: 04/16/2015
   Address: 0xF
   Runtime Size: 64 kB
   ROM Size: 6464 kB
   Characteristics:
    PCI is supported
    BIOS is upgradeable
    BIOS shadowing is allowed
    Boot from CD is supported
    Selectable boot is supported
    BIOS ROM is socketed
    EDD is supported
    5.25"/1.2 MB floppy services are supported (int 13h)
    3.5"/720 kB floppy services are supported (int 13h)
    3.5"/2.88 MB floppy services are supported (int 13h)
    Print screen service is supported (int 5h)
    8042 keyboard services are supported (int 9h)
    Serial services are supported (int 14h)
    Printer services are supported (int 17h)
    ACPI is supported
    USB legacy is supported
    Smart battery is supported
    BIOS boot specification is supported
    Targeted content distribution is supported
    UEFI is supported
   BIOS Revision: 5.6

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   UUID: xxx
   Wake-up Type: Power Switch
   SKU Number: ASUS-NotebookSKU
   Family: UX

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Features:
    Board is a hosting board
    Board is replaceable
   Location In Chassis: MIDDLE
   Chassis Handle: 0x0003
   Type: Motherboard
   Contained Object Handles: 0

  Handle 0x0003, DMI type 3, 25 bytes
  Chassis Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Type: Notebook
   Lock: Not Present
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Boot-up State: Safe
   Power Supply State: Safe
   Thermal State: Safe
   Security Status: None
   OEM Information: 0x
   Height: Unspecified
   Number Of Power Cords: 1
   Contained Elements: 1
     (0)
   SKU Number: To be filled by O.E.M.

  Handle 0x0004, DMI type 10, 26 bytes
  On Board Device 1 Information
   Type: Video
   Status: Enabled
   Description:  VGA
  On Board Device 2 Information
   Type: Ethernet
   Status: Enabled
   Description:  GLAN
  On Board Device 3 Information
   Type: Ethernet
   Status: Enabled
   Description:  WLAN
  On Board Device 4 Information
   Type: Sound
   Status: Enabled
   Description:  Audio CODEC
  On Board Device 5 Information
   Type: SATA Controller
   Status: Enabled
   Description:  SATA Controller
  On Board Device 6 Information
   Type: Other
   Status: Enabled
   Description:  USB 2.0 Controller
  On Board Device 7 Information
   Type: Other
   Status: Enabled
   Description:  USB 3.0 Controller
  On Board Device 8 Information
   Type: Other
   Status: Enabled
   Description:  SMBus Controller
  On Board Device 9 Information
   Type: Other
   Status: Enabled
   Description:  Card Reader
  On Board Device 10 Information
   Type: Other
   Status: Enabled
   Description:  Cmos Camera
  On Board Device 11 Information
   Type: Other
   Status: Enabled
   Description:  Bluetooth

  Handle 0x0005, DMI type 11, 5 bytes
  OEM Strings
   String 1:
   String 2:
   String 3:
   String 4: 90NB08T5-M00230
   

[Kernel-packages] [Bug 1482390] ProcModules.txt

[Tiago Ramos]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1482390/+attachment/4950802/+files/ProcModules.txt

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

Title:
  ASUS UX305LA - Battery state not detected correctly

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Whether the AC adapter is connected or not, the battery is always
  detected as discharging:

  When AC adapter is present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%
    AC adapter : online

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54027 mWh, 100.0%
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 0 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  When AC adapter is not present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%, 04:19:49
    AC adapter : off-line

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54005 mWh, 100.0%, 04:28:31
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 12067 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  System information:

  $ sudo dmidecode
  # dmidecode 2.12
  # SMBIOS entry point at 0xace2a898
  SMBIOS 2.8 present.
  27 structures occupying 2154 bytes.
  Table at 0xAC7C6000.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
   Vendor: American Megatrends Inc.
   Version: UX305LA.202
   Release Date: 04/16/2015
   Address: 0xF
   Runtime Size: 64 kB
   ROM Size: 6464 kB
   Characteristics:
    PCI is supported
    BIOS is upgradeable
    BIOS shadowing is allowed
    Boot from CD is supported
    Selectable boot is supported
    BIOS ROM is socketed
    EDD is supported
    5.25"/1.2 MB floppy services are supported (int 13h)
    3.5"/720 kB floppy services are supported (int 13h)
    3.5"/2.88 MB floppy services are supported (int 13h)
    Print screen service is supported (int 5h)
    8042 keyboard services are supported (int 9h)
    Serial services are supported (int 14h)
    Printer services are supported (int 17h)
    ACPI is supported
    USB legacy is supported
    Smart battery is supported
    BIOS boot specification is supported
    Targeted content distribution is supported
    UEFI is supported
   BIOS Revision: 5.6

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   UUID: xxx
   Wake-up Type: Power Switch
   SKU Number: ASUS-NotebookSKU
   Family: UX

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Features:
    Board is a hosting board
    Board is replaceable
   Location In Chassis: MIDDLE
   Chassis Handle: 0x0003
   Type: Motherboard
   Contained Object Handles: 0

  Handle 0x0003, DMI type 3, 25 bytes
  Chassis Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Type: Notebook
   Lock: Not Present
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Boot-up State: Safe
   Power Supply State: Safe
   Thermal State: Safe
   Security Status: None
   OEM Information: 0x
   Height: Unspecified
   Number Of Power Cords: 1
   Contained Elements: 1
     (0)
   SKU Number: To be filled by O.E.M.

  Handle 0x0004, DMI type 10, 26 bytes
  On Board Device 1 Information
   Type: Video
   Status: Enabled
   Description:  VGA
  On Board Device 2 Information
   Type: Ethernet
   Status: Enabled
   Description:  GLAN
  On Board Device 3 Information
   Type: Ethernet
   Status: Enabled
   Description:  WLAN
  On Board Device 4 Information
   Type: Sound
   Status: Enabled
   Description:  Audio CODEC
  On Board Device 5 Information
   Type: SATA Controller
   Status: Enabled
   Description:  SATA Controller
  On Board Device 6 Information
   Type: Other
   Status: Enabled
   Description:  USB 2.0 Controller
  On Board Device 7 Information
   Type: Other
   Status: Enabled
   Description:  USB 3.0 Controller
  On Board Device 8 Information
   Type: Other
   Status: Enabled
   Description:  SMBus Controller
  On Board Device 9 Information
   Type: Other
   Status: Enabled
   Description:  Card Reader
  On Board Device 10 Information
   Type: Other
   Status: Enabled
   Description:  Cmos Camera
  On Board Device 11 Information
   Type: Other
   Status: Enabled
   Description:  Bluetooth

  Handle 0x0005, DMI type 11, 5 bytes
  OEM Strings
   String 1:
   String 2:
   String 3:
   String 4: 90NB08T5-M00230
   

[Kernel-packages] [Bug 1482390] Lspci.txt

[Tiago Ramos]

apport information

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

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

Title:
  ASUS UX305LA - Battery state not detected correctly

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Whether the AC adapter is connected or not, the battery is always
  detected as discharging:

  When AC adapter is present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%
    AC adapter : online

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54027 mWh, 100.0%
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 0 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  When AC adapter is not present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%, 04:19:49
    AC adapter : off-line

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54005 mWh, 100.0%, 04:28:31
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 12067 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  System information:

  $ sudo dmidecode
  # dmidecode 2.12
  # SMBIOS entry point at 0xace2a898
  SMBIOS 2.8 present.
  27 structures occupying 2154 bytes.
  Table at 0xAC7C6000.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
   Vendor: American Megatrends Inc.
   Version: UX305LA.202
   Release Date: 04/16/2015
   Address: 0xF
   Runtime Size: 64 kB
   ROM Size: 6464 kB
   Characteristics:
    PCI is supported
    BIOS is upgradeable
    BIOS shadowing is allowed
    Boot from CD is supported
    Selectable boot is supported
    BIOS ROM is socketed
    EDD is supported
    5.25"/1.2 MB floppy services are supported (int 13h)
    3.5"/720 kB floppy services are supported (int 13h)
    3.5"/2.88 MB floppy services are supported (int 13h)
    Print screen service is supported (int 5h)
    8042 keyboard services are supported (int 9h)
    Serial services are supported (int 14h)
    Printer services are supported (int 17h)
    ACPI is supported
    USB legacy is supported
    Smart battery is supported
    BIOS boot specification is supported
    Targeted content distribution is supported
    UEFI is supported
   BIOS Revision: 5.6

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   UUID: xxx
   Wake-up Type: Power Switch
   SKU Number: ASUS-NotebookSKU
   Family: UX

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Features:
    Board is a hosting board
    Board is replaceable
   Location In Chassis: MIDDLE
   Chassis Handle: 0x0003
   Type: Motherboard
   Contained Object Handles: 0

  Handle 0x0003, DMI type 3, 25 bytes
  Chassis Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Type: Notebook
   Lock: Not Present
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Boot-up State: Safe
   Power Supply State: Safe
   Thermal State: Safe
   Security Status: None
   OEM Information: 0x
   Height: Unspecified
   Number Of Power Cords: 1
   Contained Elements: 1
     (0)
   SKU Number: To be filled by O.E.M.

  Handle 0x0004, DMI type 10, 26 bytes
  On Board Device 1 Information
   Type: Video
   Status: Enabled
   Description:  VGA
  On Board Device 2 Information
   Type: Ethernet
   Status: Enabled
   Description:  GLAN
  On Board Device 3 Information
   Type: Ethernet
   Status: Enabled
   Description:  WLAN
  On Board Device 4 Information
   Type: Sound
   Status: Enabled
   Description:  Audio CODEC
  On Board Device 5 Information
   Type: SATA Controller
   Status: Enabled
   Description:  SATA Controller
  On Board Device 6 Information
   Type: Other
   Status: Enabled
   Description:  USB 2.0 Controller
  On Board Device 7 Information
   Type: Other
   Status: Enabled
   Description:  USB 3.0 Controller
  On Board Device 8 Information
   Type: Other
   Status: Enabled
   Description:  SMBus Controller
  On Board Device 9 Information
   Type: Other
   Status: Enabled
   Description:  Card Reader
  On Board Device 10 Information
   Type: Other
   Status: Enabled
   Description:  Cmos Camera
  On Board Device 11 Information
   Type: Other
   Status: Enabled
   Description:  Bluetooth

  Handle 0x0005, DMI type 11, 5 bytes
  OEM Strings
   String 1:
   String 2:
   String 3:
   String 4: 90NB08T5-M00230
   String 5:
   

[Kernel-packages] [Bug 1482390] Lsusb.txt

[Tiago Ramos]

apport information

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

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

Title:
  ASUS UX305LA - Battery state not detected correctly

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Whether the AC adapter is connected or not, the battery is always
  detected as discharging:

  When AC adapter is present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%
    AC adapter : online

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54027 mWh, 100.0%
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 0 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  When AC adapter is not present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%, 04:19:49
    AC adapter : off-line

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54005 mWh, 100.0%, 04:28:31
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 12067 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  System information:

  $ sudo dmidecode
  # dmidecode 2.12
  # SMBIOS entry point at 0xace2a898
  SMBIOS 2.8 present.
  27 structures occupying 2154 bytes.
  Table at 0xAC7C6000.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
   Vendor: American Megatrends Inc.
   Version: UX305LA.202
   Release Date: 04/16/2015
   Address: 0xF
   Runtime Size: 64 kB
   ROM Size: 6464 kB
   Characteristics:
    PCI is supported
    BIOS is upgradeable
    BIOS shadowing is allowed
    Boot from CD is supported
    Selectable boot is supported
    BIOS ROM is socketed
    EDD is supported
    5.25"/1.2 MB floppy services are supported (int 13h)
    3.5"/720 kB floppy services are supported (int 13h)
    3.5"/2.88 MB floppy services are supported (int 13h)
    Print screen service is supported (int 5h)
    8042 keyboard services are supported (int 9h)
    Serial services are supported (int 14h)
    Printer services are supported (int 17h)
    ACPI is supported
    USB legacy is supported
    Smart battery is supported
    BIOS boot specification is supported
    Targeted content distribution is supported
    UEFI is supported
   BIOS Revision: 5.6

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   UUID: xxx
   Wake-up Type: Power Switch
   SKU Number: ASUS-NotebookSKU
   Family: UX

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Features:
    Board is a hosting board
    Board is replaceable
   Location In Chassis: MIDDLE
   Chassis Handle: 0x0003
   Type: Motherboard
   Contained Object Handles: 0

  Handle 0x0003, DMI type 3, 25 bytes
  Chassis Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Type: Notebook
   Lock: Not Present
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Boot-up State: Safe
   Power Supply State: Safe
   Thermal State: Safe
   Security Status: None
   OEM Information: 0x
   Height: Unspecified
   Number Of Power Cords: 1
   Contained Elements: 1
     (0)
   SKU Number: To be filled by O.E.M.

  Handle 0x0004, DMI type 10, 26 bytes
  On Board Device 1 Information
   Type: Video
   Status: Enabled
   Description:  VGA
  On Board Device 2 Information
   Type: Ethernet
   Status: Enabled
   Description:  GLAN
  On Board Device 3 Information
   Type: Ethernet
   Status: Enabled
   Description:  WLAN
  On Board Device 4 Information
   Type: Sound
   Status: Enabled
   Description:  Audio CODEC
  On Board Device 5 Information
   Type: SATA Controller
   Status: Enabled
   Description:  SATA Controller
  On Board Device 6 Information
   Type: Other
   Status: Enabled
   Description:  USB 2.0 Controller
  On Board Device 7 Information
   Type: Other
   Status: Enabled
   Description:  USB 3.0 Controller
  On Board Device 8 Information
   Type: Other
   Status: Enabled
   Description:  SMBus Controller
  On Board Device 9 Information
   Type: Other
   Status: Enabled
   Description:  Card Reader
  On Board Device 10 Information
   Type: Other
   Status: Enabled
   Description:  Cmos Camera
  On Board Device 11 Information
   Type: Other
   Status: Enabled
   Description:  Bluetooth

  Handle 0x0005, DMI type 11, 5 bytes
  OEM Strings
   String 1:
   String 2:
   String 3:
   String 4: 90NB08T5-M00230
   String 5:
   

[Kernel-packages] [Bug 1482390] apport information

[Tiago Ramos]

ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tramos 2378 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=a701a1fd-79c3-4dbc-be06-b8c9ed40829d
InstallationDate: Installed on 2017-08-23 (23 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: ASUSTeK COMPUTER INC. GL502VSK
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-33-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_rev_override=1 
vt.handoff=7
ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-33-generic N/A
 linux-backports-modules-4.10.0-33-generic  N/A
 linux-firmware 1.157.12
Tags:  xenial
Uname: Linux 4.10.0-33-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/10/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL502VSK.301
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GL502VSK
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.:bvrGL502VSK.301:bd01/10/2017:svnASUSTeKCOMPUTERINC.:pnGL502VSK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VSK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: GL502VSK
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

Title:
  ASUS UX305LA - Battery state not detected correctly

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Whether the AC adapter is connected or not, the battery is always
  detected as discharging:

  When AC adapter is present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%
    AC adapter : online

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54027 mWh, 100.0%
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 0 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  When AC adapter is not present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%, 04:19:49
    AC adapter : off-line

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54005 mWh, 100.0%, 04:28:31
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 12067 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  System information:

  $ sudo dmidecode
  # dmidecode 2.12
  # SMBIOS entry point at 0xace2a898
  SMBIOS 2.8 present.
  27 structures occupying 2154 bytes.
  Table at 0xAC7C6000.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
   Vendor: American Megatrends Inc.
   Version: UX305LA.202
   Release Date: 04/16/2015
   Address: 0xF
   Runtime Size: 64 kB
   ROM Size: 6464 kB
   Characteristics:
    PCI is supported
    BIOS is upgradeable
    BIOS shadowing is allowed
    Boot from CD is supported
    Selectable boot is supported
    BIOS ROM is socketed
    EDD is supported
    5.25"/1.2 MB floppy services are supported (int 13h)
    3.5"/720 kB floppy services are supported (int 13h)
    3.5"/2.88 MB floppy services are supported (int 13h)
    Print screen service is supported (int 5h)
    8042 keyboard services are supported (int 9h)
    Serial services are supported (int 14h)
    Printer services are supported (int 17h)
    ACPI is supported
    USB legacy is supported
    Smart battery is supported
    BIOS boot specification is supported
    Targeted content distribution is supported
    UEFI is supported
   BIOS Revision: 5.6

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   UUID: xxx
   Wake-up Type: Power Switch
   SKU Number: ASUS-NotebookSKU
   Family: UX

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Features:
    Board is a hosting board
    Board is replaceable
   Location In Chassis: MIDDLE
   Chassis Handle: 0x0003
   Type: Motherboard
   Contained Object Handles: 0

  

[Kernel-packages] [Bug 1482390] ProcCpuinfo.txt

[Tiago Ramos]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1482390/+attachment/4950798/+files/ProcCpuinfo.txt

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

Title:
  ASUS UX305LA - Battery state not detected correctly

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Whether the AC adapter is connected or not, the battery is always
  detected as discharging:

  When AC adapter is present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%
    AC adapter : online

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54027 mWh, 100.0%
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 0 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  When AC adapter is not present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%, 04:19:49
    AC adapter : off-line

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54005 mWh, 100.0%, 04:28:31
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 12067 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  System information:

  $ sudo dmidecode
  # dmidecode 2.12
  # SMBIOS entry point at 0xace2a898
  SMBIOS 2.8 present.
  27 structures occupying 2154 bytes.
  Table at 0xAC7C6000.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
   Vendor: American Megatrends Inc.
   Version: UX305LA.202
   Release Date: 04/16/2015
   Address: 0xF
   Runtime Size: 64 kB
   ROM Size: 6464 kB
   Characteristics:
    PCI is supported
    BIOS is upgradeable
    BIOS shadowing is allowed
    Boot from CD is supported
    Selectable boot is supported
    BIOS ROM is socketed
    EDD is supported
    5.25"/1.2 MB floppy services are supported (int 13h)
    3.5"/720 kB floppy services are supported (int 13h)
    3.5"/2.88 MB floppy services are supported (int 13h)
    Print screen service is supported (int 5h)
    8042 keyboard services are supported (int 9h)
    Serial services are supported (int 14h)
    Printer services are supported (int 17h)
    ACPI is supported
    USB legacy is supported
    Smart battery is supported
    BIOS boot specification is supported
    Targeted content distribution is supported
    UEFI is supported
   BIOS Revision: 5.6

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   UUID: xxx
   Wake-up Type: Power Switch
   SKU Number: ASUS-NotebookSKU
   Family: UX

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Features:
    Board is a hosting board
    Board is replaceable
   Location In Chassis: MIDDLE
   Chassis Handle: 0x0003
   Type: Motherboard
   Contained Object Handles: 0

  Handle 0x0003, DMI type 3, 25 bytes
  Chassis Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Type: Notebook
   Lock: Not Present
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Boot-up State: Safe
   Power Supply State: Safe
   Thermal State: Safe
   Security Status: None
   OEM Information: 0x
   Height: Unspecified
   Number Of Power Cords: 1
   Contained Elements: 1
     (0)
   SKU Number: To be filled by O.E.M.

  Handle 0x0004, DMI type 10, 26 bytes
  On Board Device 1 Information
   Type: Video
   Status: Enabled
   Description:  VGA
  On Board Device 2 Information
   Type: Ethernet
   Status: Enabled
   Description:  GLAN
  On Board Device 3 Information
   Type: Ethernet
   Status: Enabled
   Description:  WLAN
  On Board Device 4 Information
   Type: Sound
   Status: Enabled
   Description:  Audio CODEC
  On Board Device 5 Information
   Type: SATA Controller
   Status: Enabled
   Description:  SATA Controller
  On Board Device 6 Information
   Type: Other
   Status: Enabled
   Description:  USB 2.0 Controller
  On Board Device 7 Information
   Type: Other
   Status: Enabled
   Description:  USB 3.0 Controller
  On Board Device 8 Information
   Type: Other
   Status: Enabled
   Description:  SMBus Controller
  On Board Device 9 Information
   Type: Other
   Status: Enabled
   Description:  Card Reader
  On Board Device 10 Information
   Type: Other
   Status: Enabled
   Description:  Cmos Camera
  On Board Device 11 Information
   Type: Other
   Status: Enabled
   Description:  Bluetooth

  Handle 0x0005, DMI type 11, 5 bytes
  OEM Strings
   String 1:
   String 2:
   String 3:
   String 4: 90NB08T5-M00230
   

[Kernel-packages] [Bug 1482390] CurrentDmesg.txt

[Tiago Ramos]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1482390/+attachment/4950793/+files/CurrentDmesg.txt

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

Title:
  ASUS UX305LA - Battery state not detected correctly

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Whether the AC adapter is connected or not, the battery is always
  detected as discharging:

  When AC adapter is present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%
    AC adapter : online

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54027 mWh, 100.0%
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 0 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  When AC adapter is not present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%, 04:19:49
    AC adapter : off-line

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54005 mWh, 100.0%, 04:28:31
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 12067 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  System information:

  $ sudo dmidecode
  # dmidecode 2.12
  # SMBIOS entry point at 0xace2a898
  SMBIOS 2.8 present.
  27 structures occupying 2154 bytes.
  Table at 0xAC7C6000.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
   Vendor: American Megatrends Inc.
   Version: UX305LA.202
   Release Date: 04/16/2015
   Address: 0xF
   Runtime Size: 64 kB
   ROM Size: 6464 kB
   Characteristics:
    PCI is supported
    BIOS is upgradeable
    BIOS shadowing is allowed
    Boot from CD is supported
    Selectable boot is supported
    BIOS ROM is socketed
    EDD is supported
    5.25"/1.2 MB floppy services are supported (int 13h)
    3.5"/720 kB floppy services are supported (int 13h)
    3.5"/2.88 MB floppy services are supported (int 13h)
    Print screen service is supported (int 5h)
    8042 keyboard services are supported (int 9h)
    Serial services are supported (int 14h)
    Printer services are supported (int 17h)
    ACPI is supported
    USB legacy is supported
    Smart battery is supported
    BIOS boot specification is supported
    Targeted content distribution is supported
    UEFI is supported
   BIOS Revision: 5.6

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   UUID: xxx
   Wake-up Type: Power Switch
   SKU Number: ASUS-NotebookSKU
   Family: UX

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Features:
    Board is a hosting board
    Board is replaceable
   Location In Chassis: MIDDLE
   Chassis Handle: 0x0003
   Type: Motherboard
   Contained Object Handles: 0

  Handle 0x0003, DMI type 3, 25 bytes
  Chassis Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Type: Notebook
   Lock: Not Present
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Boot-up State: Safe
   Power Supply State: Safe
   Thermal State: Safe
   Security Status: None
   OEM Information: 0x
   Height: Unspecified
   Number Of Power Cords: 1
   Contained Elements: 1
     (0)
   SKU Number: To be filled by O.E.M.

  Handle 0x0004, DMI type 10, 26 bytes
  On Board Device 1 Information
   Type: Video
   Status: Enabled
   Description:  VGA
  On Board Device 2 Information
   Type: Ethernet
   Status: Enabled
   Description:  GLAN
  On Board Device 3 Information
   Type: Ethernet
   Status: Enabled
   Description:  WLAN
  On Board Device 4 Information
   Type: Sound
   Status: Enabled
   Description:  Audio CODEC
  On Board Device 5 Information
   Type: SATA Controller
   Status: Enabled
   Description:  SATA Controller
  On Board Device 6 Information
   Type: Other
   Status: Enabled
   Description:  USB 2.0 Controller
  On Board Device 7 Information
   Type: Other
   Status: Enabled
   Description:  USB 3.0 Controller
  On Board Device 8 Information
   Type: Other
   Status: Enabled
   Description:  SMBus Controller
  On Board Device 9 Information
   Type: Other
   Status: Enabled
   Description:  Card Reader
  On Board Device 10 Information
   Type: Other
   Status: Enabled
   Description:  Cmos Camera
  On Board Device 11 Information
   Type: Other
   Status: Enabled
   Description:  Bluetooth

  Handle 0x0005, DMI type 11, 5 bytes
  OEM Strings
   String 1:
   String 2:
   String 3:
   String 4: 90NB08T5-M00230
  

[Kernel-packages] [Bug 1482390] AlsaInfo.txt

[Tiago Ramos]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1482390/+attachment/4950791/+files/AlsaInfo.txt

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

Title:
  ASUS UX305LA - Battery state not detected correctly

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Whether the AC adapter is connected or not, the battery is always
  detected as discharging:

  When AC adapter is present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%
    AC adapter : online

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54027 mWh, 100.0%
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 0 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  When AC adapter is not present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%, 04:19:49
    AC adapter : off-line

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54005 mWh, 100.0%, 04:28:31
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 12067 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  System information:

  $ sudo dmidecode
  # dmidecode 2.12
  # SMBIOS entry point at 0xace2a898
  SMBIOS 2.8 present.
  27 structures occupying 2154 bytes.
  Table at 0xAC7C6000.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
   Vendor: American Megatrends Inc.
   Version: UX305LA.202
   Release Date: 04/16/2015
   Address: 0xF
   Runtime Size: 64 kB
   ROM Size: 6464 kB
   Characteristics:
    PCI is supported
    BIOS is upgradeable
    BIOS shadowing is allowed
    Boot from CD is supported
    Selectable boot is supported
    BIOS ROM is socketed
    EDD is supported
    5.25"/1.2 MB floppy services are supported (int 13h)
    3.5"/720 kB floppy services are supported (int 13h)
    3.5"/2.88 MB floppy services are supported (int 13h)
    Print screen service is supported (int 5h)
    8042 keyboard services are supported (int 9h)
    Serial services are supported (int 14h)
    Printer services are supported (int 17h)
    ACPI is supported
    USB legacy is supported
    Smart battery is supported
    BIOS boot specification is supported
    Targeted content distribution is supported
    UEFI is supported
   BIOS Revision: 5.6

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   UUID: xxx
   Wake-up Type: Power Switch
   SKU Number: ASUS-NotebookSKU
   Family: UX

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Features:
    Board is a hosting board
    Board is replaceable
   Location In Chassis: MIDDLE
   Chassis Handle: 0x0003
   Type: Motherboard
   Contained Object Handles: 0

  Handle 0x0003, DMI type 3, 25 bytes
  Chassis Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Type: Notebook
   Lock: Not Present
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Boot-up State: Safe
   Power Supply State: Safe
   Thermal State: Safe
   Security Status: None
   OEM Information: 0x
   Height: Unspecified
   Number Of Power Cords: 1
   Contained Elements: 1
     (0)
   SKU Number: To be filled by O.E.M.

  Handle 0x0004, DMI type 10, 26 bytes
  On Board Device 1 Information
   Type: Video
   Status: Enabled
   Description:  VGA
  On Board Device 2 Information
   Type: Ethernet
   Status: Enabled
   Description:  GLAN
  On Board Device 3 Information
   Type: Ethernet
   Status: Enabled
   Description:  WLAN
  On Board Device 4 Information
   Type: Sound
   Status: Enabled
   Description:  Audio CODEC
  On Board Device 5 Information
   Type: SATA Controller
   Status: Enabled
   Description:  SATA Controller
  On Board Device 6 Information
   Type: Other
   Status: Enabled
   Description:  USB 2.0 Controller
  On Board Device 7 Information
   Type: Other
   Status: Enabled
   Description:  USB 3.0 Controller
  On Board Device 8 Information
   Type: Other
   Status: Enabled
   Description:  SMBus Controller
  On Board Device 9 Information
   Type: Other
   Status: Enabled
   Description:  Card Reader
  On Board Device 10 Information
   Type: Other
   Status: Enabled
   Description:  Cmos Camera
  On Board Device 11 Information
   Type: Other
   Status: Enabled
   Description:  Bluetooth

  Handle 0x0005, DMI type 11, 5 bytes
  OEM Strings
   String 1:
   String 2:
   String 3:
   String 4: 90NB08T5-M00230
   String 

[Kernel-packages] [Bug 1482390] IwConfig.txt

[Tiago Ramos]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1482390/+attachment/4950794/+files/IwConfig.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/1482390

Title:
  ASUS UX305LA - Battery state not detected correctly

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Whether the AC adapter is connected or not, the battery is always
  detected as discharging:

  When AC adapter is present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%
    AC adapter : online

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54027 mWh, 100.0%
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 0 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  When AC adapter is not present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%, 04:19:49
    AC adapter : off-line

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54005 mWh, 100.0%, 04:28:31
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 12067 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  System information:

  $ sudo dmidecode
  # dmidecode 2.12
  # SMBIOS entry point at 0xace2a898
  SMBIOS 2.8 present.
  27 structures occupying 2154 bytes.
  Table at 0xAC7C6000.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
   Vendor: American Megatrends Inc.
   Version: UX305LA.202
   Release Date: 04/16/2015
   Address: 0xF
   Runtime Size: 64 kB
   ROM Size: 6464 kB
   Characteristics:
    PCI is supported
    BIOS is upgradeable
    BIOS shadowing is allowed
    Boot from CD is supported
    Selectable boot is supported
    BIOS ROM is socketed
    EDD is supported
    5.25"/1.2 MB floppy services are supported (int 13h)
    3.5"/720 kB floppy services are supported (int 13h)
    3.5"/2.88 MB floppy services are supported (int 13h)
    Print screen service is supported (int 5h)
    8042 keyboard services are supported (int 9h)
    Serial services are supported (int 14h)
    Printer services are supported (int 17h)
    ACPI is supported
    USB legacy is supported
    Smart battery is supported
    BIOS boot specification is supported
    Targeted content distribution is supported
    UEFI is supported
   BIOS Revision: 5.6

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   UUID: xxx
   Wake-up Type: Power Switch
   SKU Number: ASUS-NotebookSKU
   Family: UX

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Features:
    Board is a hosting board
    Board is replaceable
   Location In Chassis: MIDDLE
   Chassis Handle: 0x0003
   Type: Motherboard
   Contained Object Handles: 0

  Handle 0x0003, DMI type 3, 25 bytes
  Chassis Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Type: Notebook
   Lock: Not Present
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Boot-up State: Safe
   Power Supply State: Safe
   Thermal State: Safe
   Security Status: None
   OEM Information: 0x
   Height: Unspecified
   Number Of Power Cords: 1
   Contained Elements: 1
     (0)
   SKU Number: To be filled by O.E.M.

  Handle 0x0004, DMI type 10, 26 bytes
  On Board Device 1 Information
   Type: Video
   Status: Enabled
   Description:  VGA
  On Board Device 2 Information
   Type: Ethernet
   Status: Enabled
   Description:  GLAN
  On Board Device 3 Information
   Type: Ethernet
   Status: Enabled
   Description:  WLAN
  On Board Device 4 Information
   Type: Sound
   Status: Enabled
   Description:  Audio CODEC
  On Board Device 5 Information
   Type: SATA Controller
   Status: Enabled
   Description:  SATA Controller
  On Board Device 6 Information
   Type: Other
   Status: Enabled
   Description:  USB 2.0 Controller
  On Board Device 7 Information
   Type: Other
   Status: Enabled
   Description:  USB 3.0 Controller
  On Board Device 8 Information
   Type: Other
   Status: Enabled
   Description:  SMBus Controller
  On Board Device 9 Information
   Type: Other
   Status: Enabled
   Description:  Card Reader
  On Board Device 10 Information
   Type: Other
   Status: Enabled
   Description:  Cmos Camera
  On Board Device 11 Information
   Type: Other
   Status: Enabled
   Description:  Bluetooth

  Handle 0x0005, DMI type 11, 5 bytes
  OEM Strings
   String 1:
   String 2:
   String 3:
   String 4: 90NB08T5-M00230
   String 

[Kernel-packages] [Bug 1482390] JournalErrors.txt

[Tiago Ramos]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1482390/+attachment/4950795/+files/JournalErrors.txt

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

Title:
  ASUS UX305LA - Battery state not detected correctly

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Whether the AC adapter is connected or not, the battery is always
  detected as discharging:

  When AC adapter is present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%
    AC adapter : online

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54027 mWh, 100.0%
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 0 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  When AC adapter is not present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%, 04:19:49
    AC adapter : off-line

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54005 mWh, 100.0%, 04:28:31
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 12067 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  System information:

  $ sudo dmidecode
  # dmidecode 2.12
  # SMBIOS entry point at 0xace2a898
  SMBIOS 2.8 present.
  27 structures occupying 2154 bytes.
  Table at 0xAC7C6000.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
   Vendor: American Megatrends Inc.
   Version: UX305LA.202
   Release Date: 04/16/2015
   Address: 0xF
   Runtime Size: 64 kB
   ROM Size: 6464 kB
   Characteristics:
    PCI is supported
    BIOS is upgradeable
    BIOS shadowing is allowed
    Boot from CD is supported
    Selectable boot is supported
    BIOS ROM is socketed
    EDD is supported
    5.25"/1.2 MB floppy services are supported (int 13h)
    3.5"/720 kB floppy services are supported (int 13h)
    3.5"/2.88 MB floppy services are supported (int 13h)
    Print screen service is supported (int 5h)
    8042 keyboard services are supported (int 9h)
    Serial services are supported (int 14h)
    Printer services are supported (int 17h)
    ACPI is supported
    USB legacy is supported
    Smart battery is supported
    BIOS boot specification is supported
    Targeted content distribution is supported
    UEFI is supported
   BIOS Revision: 5.6

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   UUID: xxx
   Wake-up Type: Power Switch
   SKU Number: ASUS-NotebookSKU
   Family: UX

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Features:
    Board is a hosting board
    Board is replaceable
   Location In Chassis: MIDDLE
   Chassis Handle: 0x0003
   Type: Motherboard
   Contained Object Handles: 0

  Handle 0x0003, DMI type 3, 25 bytes
  Chassis Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Type: Notebook
   Lock: Not Present
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Boot-up State: Safe
   Power Supply State: Safe
   Thermal State: Safe
   Security Status: None
   OEM Information: 0x
   Height: Unspecified
   Number Of Power Cords: 1
   Contained Elements: 1
     (0)
   SKU Number: To be filled by O.E.M.

  Handle 0x0004, DMI type 10, 26 bytes
  On Board Device 1 Information
   Type: Video
   Status: Enabled
   Description:  VGA
  On Board Device 2 Information
   Type: Ethernet
   Status: Enabled
   Description:  GLAN
  On Board Device 3 Information
   Type: Ethernet
   Status: Enabled
   Description:  WLAN
  On Board Device 4 Information
   Type: Sound
   Status: Enabled
   Description:  Audio CODEC
  On Board Device 5 Information
   Type: SATA Controller
   Status: Enabled
   Description:  SATA Controller
  On Board Device 6 Information
   Type: Other
   Status: Enabled
   Description:  USB 2.0 Controller
  On Board Device 7 Information
   Type: Other
   Status: Enabled
   Description:  USB 3.0 Controller
  On Board Device 8 Information
   Type: Other
   Status: Enabled
   Description:  SMBus Controller
  On Board Device 9 Information
   Type: Other
   Status: Enabled
   Description:  Card Reader
  On Board Device 10 Information
   Type: Other
   Status: Enabled
   Description:  Cmos Camera
  On Board Device 11 Information
   Type: Other
   Status: Enabled
   Description:  Bluetooth

  Handle 0x0005, DMI type 11, 5 bytes
  OEM Strings
   String 1:
   String 2:
   String 3:
   String 4: 90NB08T5-M00230

[Kernel-packages] [Bug 1482390] CRDA.txt

[Tiago Ramos]

apport information

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

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

Title:
  ASUS UX305LA - Battery state not detected correctly

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Whether the AC adapter is connected or not, the battery is always
  detected as discharging:

  When AC adapter is present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%
    AC adapter : online

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54027 mWh, 100.0%
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 0 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  When AC adapter is not present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%, 04:19:49
    AC adapter : off-line

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54005 mWh, 100.0%, 04:28:31
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 12067 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  System information:

  $ sudo dmidecode
  # dmidecode 2.12
  # SMBIOS entry point at 0xace2a898
  SMBIOS 2.8 present.
  27 structures occupying 2154 bytes.
  Table at 0xAC7C6000.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
   Vendor: American Megatrends Inc.
   Version: UX305LA.202
   Release Date: 04/16/2015
   Address: 0xF
   Runtime Size: 64 kB
   ROM Size: 6464 kB
   Characteristics:
    PCI is supported
    BIOS is upgradeable
    BIOS shadowing is allowed
    Boot from CD is supported
    Selectable boot is supported
    BIOS ROM is socketed
    EDD is supported
    5.25"/1.2 MB floppy services are supported (int 13h)
    3.5"/720 kB floppy services are supported (int 13h)
    3.5"/2.88 MB floppy services are supported (int 13h)
    Print screen service is supported (int 5h)
    8042 keyboard services are supported (int 9h)
    Serial services are supported (int 14h)
    Printer services are supported (int 17h)
    ACPI is supported
    USB legacy is supported
    Smart battery is supported
    BIOS boot specification is supported
    Targeted content distribution is supported
    UEFI is supported
   BIOS Revision: 5.6

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   UUID: xxx
   Wake-up Type: Power Switch
   SKU Number: ASUS-NotebookSKU
   Family: UX

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Features:
    Board is a hosting board
    Board is replaceable
   Location In Chassis: MIDDLE
   Chassis Handle: 0x0003
   Type: Motherboard
   Contained Object Handles: 0

  Handle 0x0003, DMI type 3, 25 bytes
  Chassis Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Type: Notebook
   Lock: Not Present
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Boot-up State: Safe
   Power Supply State: Safe
   Thermal State: Safe
   Security Status: None
   OEM Information: 0x
   Height: Unspecified
   Number Of Power Cords: 1
   Contained Elements: 1
     (0)
   SKU Number: To be filled by O.E.M.

  Handle 0x0004, DMI type 10, 26 bytes
  On Board Device 1 Information
   Type: Video
   Status: Enabled
   Description:  VGA
  On Board Device 2 Information
   Type: Ethernet
   Status: Enabled
   Description:  GLAN
  On Board Device 3 Information
   Type: Ethernet
   Status: Enabled
   Description:  WLAN
  On Board Device 4 Information
   Type: Sound
   Status: Enabled
   Description:  Audio CODEC
  On Board Device 5 Information
   Type: SATA Controller
   Status: Enabled
   Description:  SATA Controller
  On Board Device 6 Information
   Type: Other
   Status: Enabled
   Description:  USB 2.0 Controller
  On Board Device 7 Information
   Type: Other
   Status: Enabled
   Description:  USB 3.0 Controller
  On Board Device 8 Information
   Type: Other
   Status: Enabled
   Description:  SMBus Controller
  On Board Device 9 Information
   Type: Other
   Status: Enabled
   Description:  Card Reader
  On Board Device 10 Information
   Type: Other
   Status: Enabled
   Description:  Cmos Camera
  On Board Device 11 Information
   Type: Other
   Status: Enabled
   Description:  Bluetooth

  Handle 0x0005, DMI type 11, 5 bytes
  OEM Strings
   String 1:
   String 2:
   String 3:
   String 4: 90NB08T5-M00230
   String 5:
   

[Kernel-packages] [Bug 1482390] Re: ASUS UX305LA - Battery state not detected correctly

[Tiago Ramos]

i am using a asus gl502vm and i am also afected.

ubuntu 16.04

Linux nubium-pc01 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

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_rev_override=1"

upower --dump

Device: /org/freedesktop/UPower/devices/line_power_AC0
  native-path:  AC0
  power supply: yes
  updated:  Sex 15 Set 2017 14:43:55 BRT (306 seconds ago)
  has history:  no
  has statistics:   no
  line-power
warning-level:   none
online:  yes
icon-name:  'ac-adapter-symbolic'

Device: /org/freedesktop/UPower/devices/battery_BAT0
  native-path:  BAT0
  vendor:   ASUSTeK
  model:ASUS Battery
  power supply: yes
  updated:  Sex 15 Set 2017 14:47:55 BRT (66 seconds ago)
  has history:  yes
  has statistics:   yes
  battery
present: yes
rechargeable:yes
state:   discharging
warning-level:   none
energy:  59,614 Wh
energy-empty:0 Wh
energy-full: 60,404 Wh
energy-full-design:  62,624 Wh
energy-rate: 0 W
voltage: 15,2 V
percentage:  98%
capacity:96,455%
technology:  lithium-ion
icon-name:  'battery-full-symbolic'

Device: /org/freedesktop/UPower/devices/DisplayDevice
  power supply: yes
  updated:  Sex 15 Set 2017 14:45:55 BRT (186 seconds ago)
  has history:  no
  has statistics:   no
  battery
present: yes
state:   discharging
warning-level:   none
energy:  59,614 Wh
energy-full: 60,404 Wh
energy-rate: 0 W
percentage:  98%
icon-name:  'battery-full-symbolic'

Daemon:
  daemon-version:  0.99.4
  on-battery:  no
  lid-is-closed:   no
  lid-is-present:  yes
  critical-action: HybridSleep

acpitool -a -b
  Battery #1 : Discharging, 98.69%
  AC adapter : online 


** Tags added: xenial

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

Title:
  ASUS UX305LA - Battery state not detected correctly

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Whether the AC adapter is connected or not, the battery is always
  detected as discharging:

  When AC adapter is present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%
    AC adapter : online

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54027 mWh, 100.0%
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 0 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  When AC adapter is not present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%, 04:19:49
    AC adapter : off-line

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54005 mWh, 100.0%, 04:28:31
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 12067 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  System information:

  $ sudo dmidecode
  # dmidecode 2.12
  # SMBIOS entry point at 0xace2a898
  SMBIOS 2.8 present.
  27 structures occupying 2154 bytes.
  Table at 0xAC7C6000.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
   Vendor: American Megatrends Inc.
   Version: UX305LA.202
   Release Date: 04/16/2015
   Address: 0xF
   Runtime Size: 64 kB
   ROM Size: 6464 kB
   Characteristics:
    PCI is supported
    BIOS is upgradeable
    BIOS shadowing is allowed
    Boot from CD is supported
    Selectable boot is supported
    BIOS ROM is socketed
    EDD is supported
    5.25"/1.2 MB floppy services are supported (int 13h)
    3.5"/720 kB floppy services are supported (int 13h)
    3.5"/2.88 MB floppy services are supported (int 13h)
    Print screen service is supported (int 5h)
    8042 keyboard services are supported (int 9h)
    Serial services are supported (int 14h)
    Printer services are supported (int 17h)
    ACPI is supported
    USB legacy is supported
    Smart battery is supported
    BIOS boot specification is supported
    Targeted content distribution is supported
    UEFI is supported
   BIOS Revision: 5.6

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   UUID: xxx
   Wake-up Type: Power Switch
   SKU Number: ASUS-NotebookSKU
   Family: UX

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board 

[Kernel-packages] [Bug 1676678] Re: ISST-LTE:dotg6:Kernel access of bad area, sig: 11 - during stress tests

[Frank Heimes]

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

** Changed in: ubuntu-power-systems
   Status: Incomplete => Invalid

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

Title:
  ISST-LTE:dotg6:Kernel access of bad area, sig: 11 - during stress
  tests

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

Bug description:
  ---Problem Description---
  After running stress tests (IO, TCP, BASE) for a few hours, Ubuntu 17.04 KVM 
guest dotg6 crashed, produced a kdump, and rebooted.
   
  ---uname output---
  Linux dotg6 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:27:28 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = KVM guest on a 8247-22L (host also running Ubuntu 17.04) 
   
   Stack trace output:
   [ 1909.621800] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 1909.621870] SMP NR_CPUS=2048
  [ 1909.621871] NUMA
  [ 1909.621925] pSeries
  [ 1909.622016] Modules linked in: minix nls_iso8859_1 rpcsec_gss_krb5 
auth_rpcgss nfsv4 nfs lockd grace fscache binfmt_misc xfs libcrc32c vmx_crypto 
sunrpc ip_tables x_tables autofs4 btrfs xor raid6_pq dm_service_time 
crc32c_vpmsum virtio_scsi virtio_net scsi_dh_emc scsi_dh_rdac scsi_dh_alua 
dm_multipath
  [ 1909.622401] CPU: 2 PID: 27704 Comm: ppc64_cpu Not tainted 
4.10.0-13-generic #15-Ubuntu
  [ 1909.622536] task: c00042a64200 task.stack: c0003423c000
  [ 1909.622627] NIP: d16a14f4 LR: d16a14a0 CTR: 
c0609d00
  [ 1909.622737] REGS: c0003423f7f0 TRAP: 0380   Not tainted  
(4.10.0-13-generic)
  [ 1909.622850] MSR: 8280b033 
  [ 1909.622860]   CR: 24002428  XER: 2000
  [ 1909.623016] CFAR: c061a238 SOFTE: 1
  [ 1909.623016] GPR00: d16a14a0 c0003423fa70 d16ab8cc 
c00170fd5000
  [ 1909.623016] GPR04:    
7530
  [ 1909.623016] GPR08: c146c700 757465736d642f6e c146dbe0 
d16a2ef8
  [ 1909.623016] GPR12: c0609d00 c1b81200 0008 
0001
  [ 1909.623016] GPR16:    
46f05f80
  [ 1909.623016] GPR20: 46f061f8  46f05f58 
c0017fd4a808
  [ 1909.623016] GPR24: 0001 c00170fc7a30 c1326eb0 
d16a1648
  [ 1909.623016] GPR28: c1471c28 c00170fc7860 71ae4a20 
0058
  [ 1909.623990] NIP [d16a14f4] __virtscsi_set_affinity+0xac/0x200 
[virtio_scsi]
  [ 1909.624114] LR [d16a14a0] __virtscsi_set_affinity+0x58/0x200 
[virtio_scsi]
  [ 1909.624235] Call Trace:
  [ 1909.624278] [c0003423fa70] [d16a14a0] 
__virtscsi_set_affinity+0x58/0x200 [virtio_scsi] (unreliable)
  [ 1909.624445] [c0003423fac0] [d16a1678] 
virtscsi_cpu_online+0x30/0x70 [virtio_scsi]
  [ 1909.624746] [c0003423fae0] [c00db73c] 
cpuhp_invoke_callback+0x3ec/0x5a0
  [ 1909.624887] [c0003423fb50] [c00dba88] 
cpuhp_down_callbacks+0x78/0xf0
  [ 1909.625037] [c0003423fba0] [c0268bb0] _cpu_down+0x150/0x1b0
  [ 1909.625174] [c0003423fc00] [c00de1b4] do_cpu_down+0x64/0xb0
  [ 1909.625330] [c0003423fc40] [c074b834] 
cpu_subsys_offline+0x24/0x40
  [ 1909.625485] [c0003423fc60] [c0743284] device_offline+0xf4/0x130
  [ 1909.625610] [c0003423fca0] [c0743434] online_store+0x64/0xb0
  [ 1909.625736] [c0003423fce0] [c073e37c] dev_attr_store+0x3c/0x60
  [ 1909.625862] [c0003423fd00] [c03faa18] sysfs_kf_write+0x68/0xa0
  [ 1909.625984] [c0003423fd20] [c03f98bc] 
kernfs_fop_write+0x17c/0x250
  [ 1909.626132] [c0003423fd70] [c033c98c] __vfs_write+0x3c/0x70
  [ 1909.626253] [c0003423fd90] [c033e414] vfs_write+0xd4/0x240
  [ 1909.626374] [c0003423fde0] [c033ffc8] SyS_write+0x68/0x110
  [ 1909.626501] [c0003423fe30] [c000b184] system_call+0x38/0xe0
  [ 1909.626624] Instruction dump:
  [ 1909.626691] 2f89 419e0064 3be0 393f0021 3880 792926e4 7d3d4a14 
e9290010
  [ 1909.626835] 2fa9 7d234b78 419e002c e9290020  e9290058 
2fa9 7d2c4b78
  [ 1909.627003] ---[ end trace ecc8a323beb021a2 ]---

   
  crash>  bt
  PID: 27704  TASK: c00042a64200  CPU: 2   COMMAND: "ppc64_cpu"
   #0 [c0003423f630] crash_kexec at c01a04c4
   #1 [c0003423f670] oops_end at c0024da8
   #2 [c0003423f6f0] bad_page_fault at c00627b0
   #3 [c0003423f760] slb_miss_bad_addr at c0026828
   #4 [c0003423f780] bad_addr_slb at c0008acc
   Data SLB Access [380] exception frame:
   R0:  d16a14a0R1:  c0003423fa70R2:  d16ab8cc   
   R3:  c00170fd5000R4:  R5:    

Re: [Kernel-packages] [Bug 1701499] Re: System often freezes or panics if I log in with Dell Dock WD15 connected

[Mario Limonciello]

Can you please check if you're on the latest firmware for the 5520? There
was a recent issue on many laptops that was leading to instability
specifically with USB. BIOS has been released for many of them already.

On Fri, Sep 15, 2017, 10:36 Piotr Kołaczkowski 
wrote:

> Also, I've read this on another USB ticket in bugzilla:
> All USB bugs should be sent to the linux-...@vger.kernel.org mailing
> list, and not entered into bugzilla.  Please bring this issue up there,
> if it is still a problem in the latest kernel release.
>
>
> So it looks like the mailing list is the only way.
> Is it normal that I post something to the mailing list and get no answer
> back?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1701499
>
> Title:
>   System often freezes or panics if I log in with Dell Dock WD15
>   connected
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701499/+subscriptions
>

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

Title:
  System often freezes or panics if I log in with Dell Dock WD15
  connected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Dell Precision 5520 with Ubuntu 17.04.

  If I first start a Unity session and then connect Dell WD15 USB-C dock
  with an external diplay plugged in, the system detects it properly and
  all the things work flawlessly (ethernet, external keyboard, external
  display, external storage connected to USB on the dock). I can plug-in
  and plug-out the dock multiple times and it just works.

  However if I boot the laptop with the dock already plugged in, first I
  get to the login screen and initially all is ok. Both screens are
  activated, and I can log in using the keyboard connected to the dock.

  When I hit "Enter", both screens go blank for a while, then they turn
  back on and I can see the desktop. A second or maybe two seconds later
  things start falling apart. When I move the mouse pointer a second
  after logging, it is kinda "jumpy", the movement is not smooth. The
  move freezes for a few times. I observed this behaviour only when
  moving the wireless mouse connected to the USB of the laptop. The
  builtin touchpad works smoothly.

  If it was the only issue, this would be a very minor annoyance.
  Sometimes, after a few short mouse pointer freezes the system starts
  working smoothly and all is rock stable from that point. However quite
  often I noticed much worse things happen:

  1. The mouse pointer and everything freezes totally after a few
  seconds from displaying the desktop. It is not possible to switch to
  the console with Ctrl-Alt-F1. This happens in >50% of logins.

  2. Kernel panic.

  I observed this behavior with stable Ubuntu kernel 4.10.0-20, as well
  as 4.11.0 - 4.11.8 (which I'm using now, because 4.11.x seems more
  stable than 4.10.0-x) and also 4.12.rc5 which I tried once.

  Even if everything goes fine, I noticed the following errors printed
  in syslog. I'm not sure if they are related, but they look very iffy
  to me:

  Jun 30 10:46:23 p5520 kernel: [   38.391971] DMAR: DRHD: handling fault 
status reg 2
  Jun 30 10:46:23 p5520 kernel: [   38.391977] DMAR: [INTR-REMAP] Request 
device [3e:00.0] fault index 1e [fault reason 38] Blocked an interrupt request 
due to source-id verification failure
  Jun 30 10:46:23 p5520 kernel: [   38.472490] xhci_hcd :0a:00.0: remove, 
state 1
  Jun 30 10:46:23 p5520 kernel: [   38.472496] usb usb4: USB disconnect, device 
number 1
  Jun 30 10:46:23 p5520 kernel: [   38.472497] usb 4-1: USB disconnect, device 
number 2
  Jun 30 10:46:23 p5520 kernel: [   38.472498] usb 4-1.2: USB disconnect, 
device number 3
  Jun 30 10:46:23 p5520 NetworkManager[1129]:   [1498812383.7510] device 
(eth0): state change: disconnected -> unmanaged (reason 'removed') [30 10 36]
  Jun 30 10:46:23 p5520 ModemManager[1076]:   (net/eth0): released by 
modem 
/sys/devices/pci:00/:00:1d.6/:06:00.0/:07:02.0/:0a:00.0/usb4/4-1/4-1.2
  Jun 30 10:46:23 p5520 NetworkManager[1129]:   [1498812383.7537] devices 
removed (path: 
/sys/devices/pci:00/:00:1d.6/:06:00.0/:07:02.0/:0a:00.0/usb4/4-1/4-1.2/4-1.2:1.0/net/eth0,
 iface: eth0)
  Jun 30 10:46:23 p5520 kernel: [   38.552718] xhci_hcd :0a:00.0: Host halt 
failed, -19
  Jun 30 10:46:23 p5520 kernel: [   38.552721] xhci_hcd :0a:00.0: Host not 
accessible, reset failed.
  Jun 30 10:46:23 p5520 kernel: [   38.552722] xhci_hcd :0a:00.0: USB bus 4 
deregistered
  Jun 30 10:46:23 p5520 kernel: [   38.552728] xhci_hcd :0a:00.0: remove, 
state 1
  Jun 30 10:46:23 p5520 kernel: [   38.552731] usb usb3: USB disconnect, device 
number 1
  Jun 30 10:46:23 p5520 kernel: [   38.552732] usb 3-1: USB disconnect, device 
number 

[Kernel-packages] [Bug 1701499] Re: System often freezes or panics if I log in with Dell Dock WD15 connected

[Piotr Kołaczkowski]

Also, I've read this on another USB ticket in bugzilla: 
All USB bugs should be sent to the linux-...@vger.kernel.org mailing
list, and not entered into bugzilla.  Please bring this issue up there,
if it is still a problem in the latest kernel release.


So it looks like the mailing list is the only way.
Is it normal that I post something to the mailing list and get no answer back?

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

Title:
  System often freezes or panics if I log in with Dell Dock WD15
  connected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Dell Precision 5520 with Ubuntu 17.04.

  If I first start a Unity session and then connect Dell WD15 USB-C dock
  with an external diplay plugged in, the system detects it properly and
  all the things work flawlessly (ethernet, external keyboard, external
  display, external storage connected to USB on the dock). I can plug-in
  and plug-out the dock multiple times and it just works.

  However if I boot the laptop with the dock already plugged in, first I
  get to the login screen and initially all is ok. Both screens are
  activated, and I can log in using the keyboard connected to the dock.

  When I hit "Enter", both screens go blank for a while, then they turn
  back on and I can see the desktop. A second or maybe two seconds later
  things start falling apart. When I move the mouse pointer a second
  after logging, it is kinda "jumpy", the movement is not smooth. The
  move freezes for a few times. I observed this behaviour only when
  moving the wireless mouse connected to the USB of the laptop. The
  builtin touchpad works smoothly.

  If it was the only issue, this would be a very minor annoyance.
  Sometimes, after a few short mouse pointer freezes the system starts
  working smoothly and all is rock stable from that point. However quite
  often I noticed much worse things happen:

  1. The mouse pointer and everything freezes totally after a few
  seconds from displaying the desktop. It is not possible to switch to
  the console with Ctrl-Alt-F1. This happens in >50% of logins.

  2. Kernel panic.

  I observed this behavior with stable Ubuntu kernel 4.10.0-20, as well
  as 4.11.0 - 4.11.8 (which I'm using now, because 4.11.x seems more
  stable than 4.10.0-x) and also 4.12.rc5 which I tried once.

  Even if everything goes fine, I noticed the following errors printed
  in syslog. I'm not sure if they are related, but they look very iffy
  to me:

  Jun 30 10:46:23 p5520 kernel: [   38.391971] DMAR: DRHD: handling fault 
status reg 2
  Jun 30 10:46:23 p5520 kernel: [   38.391977] DMAR: [INTR-REMAP] Request 
device [3e:00.0] fault index 1e [fault reason 38] Blocked an interrupt request 
due to source-id verification failure
  Jun 30 10:46:23 p5520 kernel: [   38.472490] xhci_hcd :0a:00.0: remove, 
state 1
  Jun 30 10:46:23 p5520 kernel: [   38.472496] usb usb4: USB disconnect, device 
number 1
  Jun 30 10:46:23 p5520 kernel: [   38.472497] usb 4-1: USB disconnect, device 
number 2
  Jun 30 10:46:23 p5520 kernel: [   38.472498] usb 4-1.2: USB disconnect, 
device number 3
  Jun 30 10:46:23 p5520 NetworkManager[1129]:   [1498812383.7510] device 
(eth0): state change: disconnected -> unmanaged (reason 'removed') [30 10 36]
  Jun 30 10:46:23 p5520 ModemManager[1076]:   (net/eth0): released by 
modem 
/sys/devices/pci:00/:00:1d.6/:06:00.0/:07:02.0/:0a:00.0/usb4/4-1/4-1.2
  Jun 30 10:46:23 p5520 NetworkManager[1129]:   [1498812383.7537] devices 
removed (path: 
/sys/devices/pci:00/:00:1d.6/:06:00.0/:07:02.0/:0a:00.0/usb4/4-1/4-1.2/4-1.2:1.0/net/eth0,
 iface: eth0)
  Jun 30 10:46:23 p5520 kernel: [   38.552718] xhci_hcd :0a:00.0: Host halt 
failed, -19
  Jun 30 10:46:23 p5520 kernel: [   38.552721] xhci_hcd :0a:00.0: Host not 
accessible, reset failed.
  Jun 30 10:46:23 p5520 kernel: [   38.552722] xhci_hcd :0a:00.0: USB bus 4 
deregistered
  Jun 30 10:46:23 p5520 kernel: [   38.552728] xhci_hcd :0a:00.0: remove, 
state 1
  Jun 30 10:46:23 p5520 kernel: [   38.552731] usb usb3: USB disconnect, device 
number 1
  Jun 30 10:46:23 p5520 kernel: [   38.552732] usb 3-1: USB disconnect, device 
number 2
  Jun 30 10:46:23 p5520 kernel: [   38.552732] usb 3-1.5: USB disconnect, 
device number 3
  Jun 30 10:46:23 p5520 kernel: [   38.553322] usb 3-1.7: USB disconnect, 
device number 4
  Jun 30 10:46:23 p5520 kernel: [   38.556064] BUG: unable to handle kernel 
paging request at 002018387ad8
  Jun 30 10:46:23 p5520 kernel: [   38.556173] IP: __radix_tree_lookup+0x10/0xf0
  Jun 30 10:46:23 p5520 kernel: [   38.556230] PGD 0 
  Jun 30 10:46:23 p5520 kernel: [   38.556232] 
  Jun 30 10:46:24 p5520 kernel: [   38.556280] Oops:  [#1] SMP
  Jun 30 10:46:24 p5520 kernel: [   38.556320] Modules linked in: ccm rfcomm 
cdc_ether usbnet snd_usb_audio 

[Kernel-packages] [Bug 1701499] Re: System often freezes or panics if I log in with Dell Dock WD15 connected

[Piotr Kołaczkowski]

Tried posting to linux-usb mailing list but I got no answer back. Any
other ways to report this problem?

The problem still exists with kernels 4.13.2 and 4.12.13.
I updated BIOS to 1.5.0 released today and also applied a fresh firmware update 
to WD15 from Dell (using Windows, because Linux can't do it yet) - and also no 
visible improvement.

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

Title:
  System often freezes or panics if I log in with Dell Dock WD15
  connected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Dell Precision 5520 with Ubuntu 17.04.

  If I first start a Unity session and then connect Dell WD15 USB-C dock
  with an external diplay plugged in, the system detects it properly and
  all the things work flawlessly (ethernet, external keyboard, external
  display, external storage connected to USB on the dock). I can plug-in
  and plug-out the dock multiple times and it just works.

  However if I boot the laptop with the dock already plugged in, first I
  get to the login screen and initially all is ok. Both screens are
  activated, and I can log in using the keyboard connected to the dock.

  When I hit "Enter", both screens go blank for a while, then they turn
  back on and I can see the desktop. A second or maybe two seconds later
  things start falling apart. When I move the mouse pointer a second
  after logging, it is kinda "jumpy", the movement is not smooth. The
  move freezes for a few times. I observed this behaviour only when
  moving the wireless mouse connected to the USB of the laptop. The
  builtin touchpad works smoothly.

  If it was the only issue, this would be a very minor annoyance.
  Sometimes, after a few short mouse pointer freezes the system starts
  working smoothly and all is rock stable from that point. However quite
  often I noticed much worse things happen:

  1. The mouse pointer and everything freezes totally after a few
  seconds from displaying the desktop. It is not possible to switch to
  the console with Ctrl-Alt-F1. This happens in >50% of logins.

  2. Kernel panic.

  I observed this behavior with stable Ubuntu kernel 4.10.0-20, as well
  as 4.11.0 - 4.11.8 (which I'm using now, because 4.11.x seems more
  stable than 4.10.0-x) and also 4.12.rc5 which I tried once.

  Even if everything goes fine, I noticed the following errors printed
  in syslog. I'm not sure if they are related, but they look very iffy
  to me:

  Jun 30 10:46:23 p5520 kernel: [   38.391971] DMAR: DRHD: handling fault 
status reg 2
  Jun 30 10:46:23 p5520 kernel: [   38.391977] DMAR: [INTR-REMAP] Request 
device [3e:00.0] fault index 1e [fault reason 38] Blocked an interrupt request 
due to source-id verification failure
  Jun 30 10:46:23 p5520 kernel: [   38.472490] xhci_hcd :0a:00.0: remove, 
state 1
  Jun 30 10:46:23 p5520 kernel: [   38.472496] usb usb4: USB disconnect, device 
number 1
  Jun 30 10:46:23 p5520 kernel: [   38.472497] usb 4-1: USB disconnect, device 
number 2
  Jun 30 10:46:23 p5520 kernel: [   38.472498] usb 4-1.2: USB disconnect, 
device number 3
  Jun 30 10:46:23 p5520 NetworkManager[1129]:   [1498812383.7510] device 
(eth0): state change: disconnected -> unmanaged (reason 'removed') [30 10 36]
  Jun 30 10:46:23 p5520 ModemManager[1076]:   (net/eth0): released by 
modem 
/sys/devices/pci:00/:00:1d.6/:06:00.0/:07:02.0/:0a:00.0/usb4/4-1/4-1.2
  Jun 30 10:46:23 p5520 NetworkManager[1129]:   [1498812383.7537] devices 
removed (path: 
/sys/devices/pci:00/:00:1d.6/:06:00.0/:07:02.0/:0a:00.0/usb4/4-1/4-1.2/4-1.2:1.0/net/eth0,
 iface: eth0)
  Jun 30 10:46:23 p5520 kernel: [   38.552718] xhci_hcd :0a:00.0: Host halt 
failed, -19
  Jun 30 10:46:23 p5520 kernel: [   38.552721] xhci_hcd :0a:00.0: Host not 
accessible, reset failed.
  Jun 30 10:46:23 p5520 kernel: [   38.552722] xhci_hcd :0a:00.0: USB bus 4 
deregistered
  Jun 30 10:46:23 p5520 kernel: [   38.552728] xhci_hcd :0a:00.0: remove, 
state 1
  Jun 30 10:46:23 p5520 kernel: [   38.552731] usb usb3: USB disconnect, device 
number 1
  Jun 30 10:46:23 p5520 kernel: [   38.552732] usb 3-1: USB disconnect, device 
number 2
  Jun 30 10:46:23 p5520 kernel: [   38.552732] usb 3-1.5: USB disconnect, 
device number 3
  Jun 30 10:46:23 p5520 kernel: [   38.553322] usb 3-1.7: USB disconnect, 
device number 4
  Jun 30 10:46:23 p5520 kernel: [   38.556064] BUG: unable to handle kernel 
paging request at 002018387ad8
  Jun 30 10:46:23 p5520 kernel: [   38.556173] IP: __radix_tree_lookup+0x10/0xf0
  Jun 30 10:46:23 p5520 kernel: [   38.556230] PGD 0 
  Jun 30 10:46:23 p5520 kernel: [   38.556232] 
  Jun 30 10:46:24 p5520 kernel: [   38.556280] Oops:  [#1] SMP
  Jun 30 10:46:24 p5520 kernel: [   38.556320] Modules linked in: ccm rfcomm 
cdc_ether usbnet snd_usb_audio snd_usbmidi_lib r8152 mii snd_hda_codec_hdmi 

[Kernel-packages] [Bug 1712867] Re: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

[Stefan Bader]

Additionally took the new crash version and installed it on s390x. I can
still load dumps produced before and also dumps done after updating
crash (just in case crash is in any way used to produce the dumps, which
I do not think is true).

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

Title:
  [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

Status in crash package in Ubuntu:
  In Progress
Status in kexec-tools package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  In Progress
Status in crash source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Xenial:
  Fix Committed
Status in linux-azure source package in Xenial:
  In Progress

Bug description:
  [Impact]

  Currently it's not possible to use the kdump functionality in xenial
  when running the linux-azure kernel. The problem is actually caused by
  several factors:

  1. kexec fails to parse /proc/kcore and thus fails to load the crash
  kernel. That's similar to bug #1713940 and it's related to 4.10+
  kernels.

  2. When the crash kernel boots, a bug in KASLR causes it to crash in a
  very early stage. For the user, it seems the system just rebooted
  after the crash.

  3. Currently in azure, crashkernel=128G is not enough to boot and run
  the dump procedure with 4.11+ kernels. That value needs to be
  increased in order to kdump to succeed.

  4. After the vmcore is dumped, the current version of crash in xenial
  is not able to parse it. All the necessary fixes are already upstream
  and can be backported.

  [Test Case]

  1. Install the linux-azure kernel in an azure instance (although it's
  possible to run linux-azure in bare metal or kvm, the KASLR issue only
  is triggered in azure).

  2. Follow the instructions in https://help.ubuntu.com/lts/serverguide
  /kernel-crash-dump.html to setup kdump and manually trigger a crash
  using /proc/sysrq-trigger.

  The vmcore must be generated and it should be possible to inspect it
  using crash.

  3. Perform these same tests for the linux-generic kernel, on each
  supported architecture.

  [Regression Potential]

  Since both kexec-tools and crash are being changed to support 4.10+
  kernels, it's very important that they continue to handle 4.4 kernels
  properly.

  The same steps above can be used to test linux-generic for
  regressions.

  [Other Info]

  Original description:

  --8<--
  Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the 
following error:
  kdump-tools[1436]: ELF core (kcore) parse failed

  Perhaps the artful kexec-tools should be backported?
  --8<--

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

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

[Kernel-packages] [Bug 1712867] Re: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

[Marcelo Cerri]

I also verified that the current version fails to load the kdump kernel
with linux-azure (4.11.0-1009.9) and that the version in -proposed fixes
the problem. The version in -proposed also works as expected with the
4.4 xenial kernel running in azure and in kvm.

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

Title:
  [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

Status in crash package in Ubuntu:
  In Progress
Status in kexec-tools package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  In Progress
Status in crash source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Xenial:
  Fix Committed
Status in linux-azure source package in Xenial:
  In Progress

Bug description:
  [Impact]

  Currently it's not possible to use the kdump functionality in xenial
  when running the linux-azure kernel. The problem is actually caused by
  several factors:

  1. kexec fails to parse /proc/kcore and thus fails to load the crash
  kernel. That's similar to bug #1713940 and it's related to 4.10+
  kernels.

  2. When the crash kernel boots, a bug in KASLR causes it to crash in a
  very early stage. For the user, it seems the system just rebooted
  after the crash.

  3. Currently in azure, crashkernel=128G is not enough to boot and run
  the dump procedure with 4.11+ kernels. That value needs to be
  increased in order to kdump to succeed.

  4. After the vmcore is dumped, the current version of crash in xenial
  is not able to parse it. All the necessary fixes are already upstream
  and can be backported.

  [Test Case]

  1. Install the linux-azure kernel in an azure instance (although it's
  possible to run linux-azure in bare metal or kvm, the KASLR issue only
  is triggered in azure).

  2. Follow the instructions in https://help.ubuntu.com/lts/serverguide
  /kernel-crash-dump.html to setup kdump and manually trigger a crash
  using /proc/sysrq-trigger.

  The vmcore must be generated and it should be possible to inspect it
  using crash.

  3. Perform these same tests for the linux-generic kernel, on each
  supported architecture.

  [Regression Potential]

  Since both kexec-tools and crash are being changed to support 4.10+
  kernels, it's very important that they continue to handle 4.4 kernels
  properly.

  The same steps above can be used to test linux-generic for
  regressions.

  [Other Info]

  Original description:

  --8<--
  Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the 
following error:
  kdump-tools[1436]: ELF core (kcore) parse failed

  Perhaps the artful kexec-tools should be backported?
  --8<--

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

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

[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

[gcchen]

My laptop runs ubuntu 16.04. Linux: 4.4.0-93-generic
I tried to debug this issue by compiling bluetoothd from source code.
Surprisingly, this issue is fixed after executing newly compiled bluetoothd 
instead of /usr/lib/bluetooth/bluetoothd.
Steps to build and run newly compiled bluetoothd is listed below.

sudo systemctl disable bluetooth.service 
sudo systemctl stop bluetooth.service 
* make sure bluetoothd started by systemd is stopped.
sudo systemctl status bluetooth.service 

* build bluetoothd
mkdir test
cd test/
apt-get source bluez
cd bluez-5.37/
sudo apt-get install libglib2.0-dev
sudo apt-get install libdbus-1-dev
sudo apt-get install libudev-dev
sudo apt-get install libical-dev
sudo apt-get install lib64readline-dev
sudo apt-get install libreadline-dev
./configure 
make
cd src/
ls
sudo ./bluetoothd -n
bluetooth may work now.

The drawback is that you have to start bluetoothd manually after reboot.
Good luck.

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

Title:
  15:10 and 16.04: bluetoothd "Failed to start discovery:
  org.bluez.Error.NotReady" after bluetoothd restarted

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  On 15:10 after the bluetooth service has been stopped and restarted it
  is not possible to scan or connect to devices:

  $ sudo systemctl restart bluetooth

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady

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

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

[Kernel-packages] [Bug 1712867] Re: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

[Stefan Bader]

Verified on Azure with 4.11 kernel that the current version (updates)
fails to load the kdump kernel and the new one from proposed succeeds to
load.

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

Title:
  [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

Status in crash package in Ubuntu:
  In Progress
Status in kexec-tools package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  In Progress
Status in crash source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Xenial:
  Fix Committed
Status in linux-azure source package in Xenial:
  In Progress

Bug description:
  [Impact]

  Currently it's not possible to use the kdump functionality in xenial
  when running the linux-azure kernel. The problem is actually caused by
  several factors:

  1. kexec fails to parse /proc/kcore and thus fails to load the crash
  kernel. That's similar to bug #1713940 and it's related to 4.10+
  kernels.

  2. When the crash kernel boots, a bug in KASLR causes it to crash in a
  very early stage. For the user, it seems the system just rebooted
  after the crash.

  3. Currently in azure, crashkernel=128G is not enough to boot and run
  the dump procedure with 4.11+ kernels. That value needs to be
  increased in order to kdump to succeed.

  4. After the vmcore is dumped, the current version of crash in xenial
  is not able to parse it. All the necessary fixes are already upstream
  and can be backported.

  [Test Case]

  1. Install the linux-azure kernel in an azure instance (although it's
  possible to run linux-azure in bare metal or kvm, the KASLR issue only
  is triggered in azure).

  2. Follow the instructions in https://help.ubuntu.com/lts/serverguide
  /kernel-crash-dump.html to setup kdump and manually trigger a crash
  using /proc/sysrq-trigger.

  The vmcore must be generated and it should be possible to inspect it
  using crash.

  3. Perform these same tests for the linux-generic kernel, on each
  supported architecture.

  [Regression Potential]

  Since both kexec-tools and crash are being changed to support 4.10+
  kernels, it's very important that they continue to handle 4.4 kernels
  properly.

  The same steps above can be used to test linux-generic for
  regressions.

  [Other Info]

  Original description:

  --8<--
  Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the 
following error:
  kdump-tools[1436]: ELF core (kcore) parse failed

  Perhaps the artful kexec-tools should be backported?
  --8<--

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

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

[Kernel-packages] [Bug 1717549] [NEW] Artful update to v4.13.2 stable release

[Seth Forshee]

Public bug reported:

SRU Justification

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

   git://git.kernel.org/

TEST CASE: TBD

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

mtd: nand: make Samsung SLC NAND usable again
mtd: nand: hynix: add support for 20nm NAND chips
mtd: nand: mxc: Fix mxc_v1 ooblayout
mtd: nand: qcom: fix read failure without complete bootchain
mtd: nand: qcom: fix config error for BCH
nvme-fabrics: generate spec-compliant UUID NQNs
btrfs: resume qgroup rescan on rw remount
rtlwifi: btcoexist: Fix breakage of ant_sel for rtl8723be
rtlwifi: btcoexist: Fix antenna selection code
radix-tree: must check __radix_tree_preload() return value
brcmfmac: feature check for multi-scheduled scan fails on bcm4345 devices
kselftests: timers: leap-a-day: Change default arguments to help test runs
selftests: timers: Fix run_destructive_tests target to handle skipped tests
selftests/x86/fsgsbase: Test selectors 1, 2, and 3
mm: kvfree the swap cluster info if the swap file is unsatisfactory
mm/swapfile.c: fix swapon frontswap_map memory leak on error
mm/sparse.c: fix typo in online_mem_sections
mm/memory.c: fix mem_cgroup_oom_disable() call missing
KVM: SVM: Limit PFERR_NESTED_GUEST_PAGE error_code check to L1 guest
Revert "firmware: add sanity check on shutdown/suspend"
rt2800: fix TX_PIN_CFG setting for non MT7620 chips
ARM64: dts: marvell: armada-37xx: Fix GIC maintenance interrupt
ARM: 8692/1: mm: abort uaccess retries upon fatal signal
NFS: Fix 2 use after free issues in the I/O code
NFS: Sync the correct byte range during synchronous writes
NFSv4: Fix up mirror allocation
xfs: XFS_IS_REALTIME_INODE() should be false if no rt device present
Linux 4.13.2

   The following patches from the v4.13.2 stable release had already
been applied:

Bluetooth: Properly check L2CAP config option output buffer length

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: Fix Committed

** Affects: linux (Ubuntu Artful)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: Fix Committed


** Tags: kernel-stable-tracking-bug

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

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

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

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

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

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The v4.13.2 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The v4.13.2 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
+    The following patches from the v4.13.2 stable release shall be
+ applied:
  
-The following patches from the v4.13.2 stable release shall be
- applied:
+ mtd: nand: make Samsung SLC NAND usable again
+ mtd: nand: hynix: add support for 20nm NAND chips
+ mtd: nand: mxc: Fix mxc_v1 ooblayout
+ mtd: nand: qcom: fix read failure without complete bootchain
+ mtd: nand: qcom: fix config error for BCH
+ nvme-fabrics: generate spec-compliant UUID NQNs
+ btrfs: resume qgroup rescan on rw remount
+ rtlwifi: btcoexist: Fix breakage of ant_sel for rtl8723be
+ rtlwifi: btcoexist: Fix antenna selection code
+ radix-tree: must check __radix_tree_preload() return value
+ brcmfmac: feature check for multi-scheduled scan fails on bcm4345 devices
+ kselftests: timers: leap-a-day: Change default arguments to help test runs
+ selftests: timers: Fix run_destructive_tests target to 

[Kernel-packages] [Bug 1717430] Re: [Bug] Thunderbolt-patches: Related to the way the key for secure connection is handled

[Seth Forshee]

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

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

Title:
  [Bug] Thunderbolt-patches: Related to the way the key for secure
  connection is handled

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  . These patches allow security-related (preventing non-root users from 
reading the key) and functional capability (not blocking “connect once” flow).
  Merged in kernel v 4.14
  8fdd6ab36197 thunderbolt: Remove superfluous check – Needed to enable Allow 
clearing key 
  e545f0d8a54a thunderbolt: Allow clearing the key – user cannot reset the 
device key, without disconnecting device
  0956e4116922 thunderbolt: Make key root-only accessible – security, non-root 
users can read the key, possible security breach

  
  Target Release: 17.10

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

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

[Kernel-packages] [Bug 1717431] Re: [Bug] Thunderbolt-patches: Fixes the issue regarding the order of ACPI calls w.r.t. PCI enumeration

[Seth Forshee]

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

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

Title:
  [Bug] Thunderbolt-patches: Fixes the issue regarding the order of ACPI
  calls w.r.t. PCI enumeration

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  Description:

  Without these patches, TBT device that is connected on boot is usually not 
functional. Only reconnecting after OS up works. This is a serious usability 
issue.
  Merged in kernel v 4.14
  ecc1165b8b74 ACPICA: Dispatch active GPEs at init time 
  1312b7e0caca ACPICA: Make it possible to enable runtime GPEs earlier
  eb7f43c4adb4 ACPI / scan: Enable GPEs before scanning the namespace

  
  Target Release: 17.10

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

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

[Kernel-packages] [Bug 1712867] Re: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

[Steve Langasek]

Hello Joshua, or anyone else affected,

Accepted crash into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/crash/7.1.4-1ubuntu4.2
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

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

Title:
  [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

Status in crash package in Ubuntu:
  In Progress
Status in kexec-tools package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  In Progress
Status in crash source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Xenial:
  Fix Committed
Status in linux-azure source package in Xenial:
  In Progress

Bug description:
  [Impact]

  Currently it's not possible to use the kdump functionality in xenial
  when running the linux-azure kernel. The problem is actually caused by
  several factors:

  1. kexec fails to parse /proc/kcore and thus fails to load the crash
  kernel. That's similar to bug #1713940 and it's related to 4.10+
  kernels.

  2. When the crash kernel boots, a bug in KASLR causes it to crash in a
  very early stage. For the user, it seems the system just rebooted
  after the crash.

  3. Currently in azure, crashkernel=128G is not enough to boot and run
  the dump procedure with 4.11+ kernels. That value needs to be
  increased in order to kdump to succeed.

  4. After the vmcore is dumped, the current version of crash in xenial
  is not able to parse it. All the necessary fixes are already upstream
  and can be backported.

  [Test Case]

  1. Install the linux-azure kernel in an azure instance (although it's
  possible to run linux-azure in bare metal or kvm, the KASLR issue only
  is triggered in azure).

  2. Follow the instructions in https://help.ubuntu.com/lts/serverguide
  /kernel-crash-dump.html to setup kdump and manually trigger a crash
  using /proc/sysrq-trigger.

  The vmcore must be generated and it should be possible to inspect it
  using crash.

  3. Perform these same tests for the linux-generic kernel, on each
  supported architecture.

  [Regression Potential]

  Since both kexec-tools and crash are being changed to support 4.10+
  kernels, it's very important that they continue to handle 4.4 kernels
  properly.

  The same steps above can be used to test linux-generic for
  regressions.

  [Other Info]

  Original description:

  --8<--
  Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the 
following error:
  kdump-tools[1436]: ELF core (kcore) parse failed

  Perhaps the artful kexec-tools should be backported?
  --8<--

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

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

[Kernel-packages] [Bug 1712867] Re: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

[Stefan Bader]

Verified that kexec-tools 1:2.0.10-1ubuntu2.4 on s390x still works (with
4.4 kernel).

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

Title:
  [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

Status in crash package in Ubuntu:
  In Progress
Status in kexec-tools package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  In Progress
Status in kexec-tools source package in Xenial:
  Fix Committed
Status in linux-azure source package in Xenial:
  In Progress

Bug description:
  [Impact]

  Currently it's not possible to use the kdump functionality in xenial
  when running the linux-azure kernel. The problem is actually caused by
  several factors:

  1. kexec fails to parse /proc/kcore and thus fails to load the crash
  kernel. That's similar to bug #1713940 and it's related to 4.10+
  kernels.

  2. When the crash kernel boots, a bug in KASLR causes it to crash in a
  very early stage. For the user, it seems the system just rebooted
  after the crash.

  3. Currently in azure, crashkernel=128G is not enough to boot and run
  the dump procedure with 4.11+ kernels. That value needs to be
  increased in order to kdump to succeed.

  4. After the vmcore is dumped, the current version of crash in xenial
  is not able to parse it. All the necessary fixes are already upstream
  and can be backported.

  [Test Case]

  1. Install the linux-azure kernel in an azure instance (although it's
  possible to run linux-azure in bare metal or kvm, the KASLR issue only
  is triggered in azure).

  2. Follow the instructions in https://help.ubuntu.com/lts/serverguide
  /kernel-crash-dump.html to setup kdump and manually trigger a crash
  using /proc/sysrq-trigger.

  The vmcore must be generated and it should be possible to inspect it
  using crash.

  3. Perform these same tests for the linux-generic kernel, on each
  supported architecture.

  [Regression Potential]

  Since both kexec-tools and crash are being changed to support 4.10+
  kernels, it's very important that they continue to handle 4.4 kernels
  properly.

  The same steps above can be used to test linux-generic for
  regressions.

  [Other Info]

  Original description:

  --8<--
  Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the 
following error:
  kdump-tools[1436]: ELF core (kcore) parse failed

  Perhaps the artful kexec-tools should be backported?
  --8<--

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

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

[Kernel-packages] [Bug 1646277] Re: Xenial server 16.04.x will have a black screen after PXE installation

[Joseph Salisbury]

Thanks for testing.  Can you test this 3.19 kernel:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/13366909

This may not be a regression afterall, so we should figure that out.

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

Title:
  Xenial server 16.04.x will have a black screen after PXE installation

Status in debian-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in debian-installer source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  The display will keep black screen after install 16.04.x via PXE(need
  use "Ctrl+Alt+F1" to change to terminal 1, then can see text mode
  screen)

  Quanta team is installing Xenial server using PXE boot.   After the
  installation, the console will show a black screen.   Hitting ctl-
  alt-f1 displays the text mode screen OK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1646277/+subscriptions

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

[Kernel-packages] [Bug 1416277] Re: toshiba_acpi: Unknown key 158

[Joseph Salisbury]

I guess it's been a while since I last posted.  Can those affected by
this bug test the latest 4.13 kernel to see if the fix ever made it
upstream?  The kernel can be downloaded from:

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

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

Title:
  toshiba_acpi: Unknown key 158

Status in linux package in Ubuntu:
  In Progress

Bug description:
  If I press the wireless key (see attached image) on my Toshiba P50W I
  get the following error in dmesg:

  toshiba_acpi: Unknown key 158

  I'd expect this key to toggle flight mode.
  --- 
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bob2980 F pulseaudio
   /dev/snd/controlC1:  bob2980 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=5033984a-21af-482d-a1fd-c075e818cd12
  InstallationDate: Installed on 2013-12-26 (400 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: TOSHIBA Satellite P50W-B
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=885f0f10-b818-4eb4-8ff4-d067e16bef2f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-11-generic N/A
   linux-backports-modules-3.18.0-11-generic  N/A
   linux-firmware 1.141
  Tags:  vivid
  Uname: Linux 3.18.0-11-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2013-12-26 (400 days ago)
  UserGroups: adm autopilot cdrom dip libvirtd lpadmin netdev plugdev 
sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 08/08/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  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.:bvr1.40:bd08/08/2014:svnTOSHIBA:pnSatelliteP50W-B:pvrPSVP2A-00F002:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite P50W-B
  dmi.product.version: PSVP2A-00F002
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1716620] Re: linux-aws: 4.4.0-1035.44 -proposed tracker

[Stefan Bader]

Manual override, ignoring regression of snapd test (>=2.27.5) which
looks to fail with some ALSA subtest (not sure this ever was supposed to
work on AWS).

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

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

Title:
  linux-aws: 4.4.0-1035.44 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1716613
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1716620/+subscriptions

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

[Kernel-packages] [Bug 1716644] Re: linux: 3.2.0-131.177 -proposed tracker

[Stefan Bader]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Invalid

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

Title:
  linux: 3.2.0-131.177 -proposed tracker

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

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

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

  backports: 
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1716644/+subscriptions

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

[Kernel-packages] [Bug 1716635] Re: linux-lts-trusty: 3.13.0-132.181~precise1 -proposed tracker

[Stefan Bader]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Invalid

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

Title:
  linux-lts-trusty: 3.13.0-132.181~precise1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1716634
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1716635/+subscriptions

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

[Kernel-packages] [Bug 1713553] Re: Intel i40e PF reset due to incorrect MDD detection

[Stefan Bader]

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

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

Title:
  Intel i40e PF reset due to incorrect MDD detection

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

Bug description:
  [Impact]

  Using an Intel i40e network device, under heavy traffic load with
  TSO enabled, the device will spontaneously reset itself and issue errors
  similar to the following:

  Jun 14 14:09:51 hostname kernel: [4253913.851053] i40e :05:00.1: TX 
driver issue detected, PF reset issued
  Jun 14 14:09:53 hostname kernel: [4253915.476283] i40e :05:00.1: TX 
driver issue detected, PF reset issued
  Jun 14 14:09:54 hostname kernel: [4253917.411264] i40e :05:00.1: TX 
driver issue detected, PF reset issued

   This causes a full reset of the PF, which causes an interruption
  in traffic flow.

  This was partially fixed by Xenial commit
  12f8cc59d5886b86372f45290166deca57a60d7a, however there is one
  additional upstream commit required to fully fix the issue:

  commit 841493a3f64395b60554afbcaa17f4350f90e764
  Author: Alexander Duyck 
  Date:   Tue Sep 6 18:05:04 2016 -0700

  i40e: Limit TX descriptor count in cases where frag size is
  greater than 16K

   This fix was never backported into the Xenial 4.4 kernel series, but
  is already present in the Xenial HWE (and Zesty) 4.10 kernel.

  [Testcase]

   In this case, the issue occurs at a customer site using i40e based
  Intel network cards with SR-IOV enabled. Under heavy load, the card will
  reset itself as described.

  [Regression Potential]

  As with any change to a network card driver, this may cause
  regressions with network I/O through i40e card(s).  However, this
  specific change only increases the likelyhood that any specific large
  TSO tx will need to be linearized, which will avoid the PF reset.
  Linearizing a TSO tx that did not need to be linearized will not cause
  any failures, it may only decrease performance slightly.  However this
  patch should only cause linearization when required to avoid the MDD
  detection and PF reset.

  [Other Info]

  The previous bug for this issue is bug 1700834.

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

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

[Kernel-packages] [Bug 1716644] Re: linux: 3.2.0-131.177 -proposed tracker

[Stefan Bader]

** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Invalid

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

Title:
  linux: 3.2.0-131.177 -proposed tracker

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

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

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

  backports: 
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1716644/+subscriptions

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

[Kernel-packages] [Bug 1715812] Re: Neighbour confirmation broken, breaks ARP cache aging

[Stefan Bader]

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

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

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

Title:
  Neighbour confirmation broken, breaks ARP cache aging

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]
  A host can lose access to another host whose MAC address changes if they have 
active connections to other hosts that share a route. The ARP cache does not 
time out as expected - instead the old MAC address is continuously reconfirmed.

  [Fix]
  Apply series [1], which changes the algorithm for neighbour confirmation.
  That is, from upstream:
  51ce8bd4d17a net: pending_confirm is not used anymore 
  0dec879f636f net: use dst_confirm_neigh for UDP, RAW, ICMP, L2TP 
  63fca65d0863 net: add confirm_neigh method to dst_ops 
  c3a2e8370534 tcp: replace dst_confirm with sk_dst_confirm 
  c86a773c7802 sctp: add dst_pending_confirm flag 
  4ff0620354f2 net: add dst_pending_confirm flag to skbuff 
  9b8805a32559 sock: add sk_dst_pending_confirm flag 

  [Test case]
  Create 3 real or virtual systems, all hooked up to a switch.
  One system needs an active-backup bond with fail_over_mac=1 num_grat_arp=0.

  Put all the systems in the same subnet, e.g. 192.168.200.0/24

  Call the system with the bond A, and the other two systems B and C.

  On B, run in 3 shells:
   - netperf -t TCP_RR to C
   - ping -f A
   - watch 'ip -s neigh show 192.168.200.0/24'

  On A, cause the bond to fail over.

  Observe that:

   - without the patches, B intermittently fails to notice the change in
  A's MAC address. This presents as the ping failing and not recovering,
  and the arp table showing the old mac address never timing out and
  never being replace with a new mac address.

   - with the patches, the arp cache times out and B sends another mac
  probe and detects A's new address.

  It helps to use taskset to put ping and netperf on the same CPU, or
  use single-CPU vms.

  See [2] for more details.

  [References]
  [2] Original report: 
https://www.mail-archive.com/netdev@vger.kernel.org/msg138762.html
  [1]: https://www.spinics.net/lists/linux-rdma/msg45907.html

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

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

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

[bugproxy]

--- Comment From cha...@us.ibm.com 2017-09-15 09:43 EDT---
Closing as insufficient data as the requested information has not been provided 
in some time.

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

Title:
  ISST-LTE:dotg6:Kernel access of bad area, sig: 11 - during stress
  tests

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

Bug description:
  ---Problem Description---
  After running stress tests (IO, TCP, BASE) for a few hours, Ubuntu 17.04 KVM 
guest dotg6 crashed, produced a kdump, and rebooted.
   
  ---uname output---
  Linux dotg6 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:27:28 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = KVM guest on a 8247-22L (host also running Ubuntu 17.04) 
   
   Stack trace output:
   [ 1909.621800] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 1909.621870] SMP NR_CPUS=2048
  [ 1909.621871] NUMA
  [ 1909.621925] pSeries
  [ 1909.622016] Modules linked in: minix nls_iso8859_1 rpcsec_gss_krb5 
auth_rpcgss nfsv4 nfs lockd grace fscache binfmt_misc xfs libcrc32c vmx_crypto 
sunrpc ip_tables x_tables autofs4 btrfs xor raid6_pq dm_service_time 
crc32c_vpmsum virtio_scsi virtio_net scsi_dh_emc scsi_dh_rdac scsi_dh_alua 
dm_multipath
  [ 1909.622401] CPU: 2 PID: 27704 Comm: ppc64_cpu Not tainted 
4.10.0-13-generic #15-Ubuntu
  [ 1909.622536] task: c00042a64200 task.stack: c0003423c000
  [ 1909.622627] NIP: d16a14f4 LR: d16a14a0 CTR: 
c0609d00
  [ 1909.622737] REGS: c0003423f7f0 TRAP: 0380   Not tainted  
(4.10.0-13-generic)
  [ 1909.622850] MSR: 8280b033 
  [ 1909.622860]   CR: 24002428  XER: 2000
  [ 1909.623016] CFAR: c061a238 SOFTE: 1
  [ 1909.623016] GPR00: d16a14a0 c0003423fa70 d16ab8cc 
c00170fd5000
  [ 1909.623016] GPR04:    
7530
  [ 1909.623016] GPR08: c146c700 757465736d642f6e c146dbe0 
d16a2ef8
  [ 1909.623016] GPR12: c0609d00 c1b81200 0008 
0001
  [ 1909.623016] GPR16:    
46f05f80
  [ 1909.623016] GPR20: 46f061f8  46f05f58 
c0017fd4a808
  [ 1909.623016] GPR24: 0001 c00170fc7a30 c1326eb0 
d16a1648
  [ 1909.623016] GPR28: c1471c28 c00170fc7860 71ae4a20 
0058
  [ 1909.623990] NIP [d16a14f4] __virtscsi_set_affinity+0xac/0x200 
[virtio_scsi]
  [ 1909.624114] LR [d16a14a0] __virtscsi_set_affinity+0x58/0x200 
[virtio_scsi]
  [ 1909.624235] Call Trace:
  [ 1909.624278] [c0003423fa70] [d16a14a0] 
__virtscsi_set_affinity+0x58/0x200 [virtio_scsi] (unreliable)
  [ 1909.624445] [c0003423fac0] [d16a1678] 
virtscsi_cpu_online+0x30/0x70 [virtio_scsi]
  [ 1909.624746] [c0003423fae0] [c00db73c] 
cpuhp_invoke_callback+0x3ec/0x5a0
  [ 1909.624887] [c0003423fb50] [c00dba88] 
cpuhp_down_callbacks+0x78/0xf0
  [ 1909.625037] [c0003423fba0] [c0268bb0] _cpu_down+0x150/0x1b0
  [ 1909.625174] [c0003423fc00] [c00de1b4] do_cpu_down+0x64/0xb0
  [ 1909.625330] [c0003423fc40] [c074b834] 
cpu_subsys_offline+0x24/0x40
  [ 1909.625485] [c0003423fc60] [c0743284] device_offline+0xf4/0x130
  [ 1909.625610] [c0003423fca0] [c0743434] online_store+0x64/0xb0
  [ 1909.625736] [c0003423fce0] [c073e37c] dev_attr_store+0x3c/0x60
  [ 1909.625862] [c0003423fd00] [c03faa18] sysfs_kf_write+0x68/0xa0
  [ 1909.625984] [c0003423fd20] [c03f98bc] 
kernfs_fop_write+0x17c/0x250
  [ 1909.626132] [c0003423fd70] [c033c98c] __vfs_write+0x3c/0x70
  [ 1909.626253] [c0003423fd90] [c033e414] vfs_write+0xd4/0x240
  [ 1909.626374] [c0003423fde0] [c033ffc8] SyS_write+0x68/0x110
  [ 1909.626501] [c0003423fe30] [c000b184] system_call+0x38/0xe0
  [ 1909.626624] Instruction dump:
  [ 1909.626691] 2f89 419e0064 3be0 393f0021 3880 792926e4 7d3d4a14 
e9290010
  [ 1909.626835] 2fa9 7d234b78 419e002c e9290020  e9290058 
2fa9 7d2c4b78
  [ 1909.627003] ---[ end trace ecc8a323beb021a2 ]---

   
  crash>  bt
  PID: 27704  TASK: c00042a64200  CPU: 2   COMMAND: "ppc64_cpu"
   #0 [c0003423f630] crash_kexec at c01a04c4
   #1 [c0003423f670] oops_end at c0024da8
   #2 [c0003423f6f0] bad_page_fault at c00627b0
   #3 [c0003423f760] slb_miss_bad_addr at c0026828
   #4 [c0003423f780] bad_addr_slb at c0008acc
   Data SLB Access [380] exception frame:
   R0:  d16a14a0R1:  c0003423fa70R2:  d16ab8cc   
   R3:  c00170fd5000R4:  

[Kernel-packages] [Bug 1715073] Re: SRIOV: warning if unload VFs

[Stefan Bader]

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

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

Title:
  SRIOV: warning if unload VFs

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

Bug description:
  == Comment: #0 - Carol L. Soto  - 2017-02-23 16:11:47 ==
  ---Problem Description---
  When doing SRIOV if I unload VFs will see a warning:

  Feb 23 16:05:56 powerio-le11 kernel: [  201.343397] 
mlx5_3:wait_for_async_commands:674:(pid 6272): done with all pending requests
  Feb 23 16:05:56 powerio-le11 kernel: [  201.603999] iommu: Removing device 
0004:01:00.2 from group 7
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604078] pci 0004:01: 0.2: [PE# 
00] Removing DMA window #0
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604084] pci 0004:01: 0.2: [PE# 
00] Disabling 64-bit DMA bypass
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604350] mlx5_core 0004:01:00.0: 
VF BAR0: [mem 0x2400-0x2401 64bit pref] shifted to [mem 
0x2400-0x2401 64bit pref] (Disabling 1 VFs shifted by 0)
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604363] mlx5_core 0004:01:00.0: 
can't update enabled VF BAR0 [mem 0x2400-0x2401 64bit pref]
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604379] [ cut here 
]
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604386] WARNING: CPU: 14 PID: 
6272 at /build/linux-twbIHf/linux-4.10.0/drivers/pci/iov.c:584 
pci_iov_update_resource+0x178/0x1d0
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604388] Modules linked in: 
mlx5_ib xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp kvm_hv kvm_pr kvm 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bridge stp 
llc binfmt_misc ipmi_powernv ipmi_devintf uio_pdrv_genirq ipmi_msghandler uio 
vmx_crypto powernv_rng powernv_op_panel leds_powernv ibmpowernv ib_iser rdma_cm 
iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi knem(OE) ip_tables x_tables autofs4 btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear mlx4_en ses enclosure scsi_transport_sas 
crc32c_vpmsum mlx5_core mlx4_core
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604451]  tg3 ipr devlink
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604456] CPU: 14 PID: 6272 Comm: 
bash Tainted: G   OE   4.10.0-8-generic #10-Ubuntu
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604457] task: c00f40a6d600 
task.stack: c00f40ac8000
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604459] NIP: c06721b8 LR: 
c06721b4 CTR: 
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604461] REGS: c00f40acb590 
TRAP: 0700   Tainted: G   OE(4.10.0-8-generic)
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604462] MSR: 9282b033 

  Feb 23 16:05:56 powerio-le11 kernel: [  201.604470]   CR: 42424422  XER: 
2000
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] CFAR: c0b49db4 
SOFTE: 1
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR00: c06721b4 
c00f40acb810 c143c900 0063
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR04: 0001 
0539 c01fff70 00021a50
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR08: 0007 
0007 0001 656d5b2030524142
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR12: 4400 
cfb87e00 10180df8 10189e60
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR16: 10189ed8 
c00fdd0a2400 c01fff97d180 c0d46268
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR20: c0d4e410 
c0d41df8 c01fff97d190 c0d4d8d8
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR24: c0d4d8e0 
c00fe8f460a0 0001 
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604471] GPR28: c00fe8f80f80 
 c00fe8f46580 c00fe8f46000
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604498] NIP [c06721b8] 
pci_iov_update_resource+0x178/0x1d0
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604501] LR [c06721b4] 
pci_iov_update_resource+0x174/0x1d0
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604501] Call Trace:
  Feb 23 16:05:56 powerio-le11 kernel: [  201.604504] [c00f40acb810] 
[c06721b4] pci_iov_update_resource+0x174/0x1d0 (unreliable)
  Feb 23 

[Kernel-packages] [Bug 1678477] Re: Kernel has troule recognizing Corsair Strafe RGB keyboard

[Stefan Bader]

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

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

Title:
  Kernel has troule recognizing Corsair Strafe RGB keyboard

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  I recently bought a Corsair Strafe RGB keyboard, and while it works
  well when successfully recognized by Ubuntu at boot, that doesn't
  always happen.

  I see messages like this when booting my desktop up:

  [6.619510] usb 3-10: unable to read config index 0 descriptor/all
  [6.619543] usb 3-10: can't read configurations, error -110

  They sometimes repeat at 5-second intervals, culminating on a "can't
  set config #1" message or even "unable to enumerate USB device". This
  happens on the logic that deals with a new USB device being connected,
  so when it doesn't work it never gets to the HID drivers part of the
  code. When it does, hid-generic is quite able to control the keyboard,
  though this message appears on dmesg:

  [6.883811] usbhid 3-10:1.2: couldn't find an input interrupt
  endpoint

  
  From what I have been able to determine, the Corsair Strafe RGB has three 
inputs, with the last one being used as input/output and having something to do 
with the LEDs. It only has a single USB configuration, though I don't know why 
it times out.

  Searching on Google has a lot of people recommending this userspace
  drive to me: https://github.com/mattanger/ckb-next , and I've tried
  it, but it seems to be more about programming lighting effects into
  the keyboard than in controlling its basic operation, which is all I'm
  interested in. Its daemon was supposed to handle that part too, but it
  didn't fix those connection errors on boot.

  I have the following boot parameter set in my kernel, following advice
  from ckb-next's README, but it doesn't see to have an appreciable
  effect on my success rate:

  usbhid.quirks=0x1B1C:0x1B20:0x2448

  ckb-next recommended 0x2408, but I added the HID_QUIRK_MULTI_INPUT
  as well in an attempt to improve things, without success.

  GRUB is always able to correctly identify the keyboard and get it to
  work, too, which makes the fact that the full kernel can't always do
  it a little more frustrating.

  I would be happy to provide any extra information you require on this
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-45-generic 4.8.0-45.48
  ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
  Uname: Linux 4.8.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bira   2322 F pulseaudio
   /dev/snd/controlC0:  bira   2322 F pulseaudio
  CurrentDesktop: i3
  Date: Sat Apr  1 10:23:52 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-24 (767 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Z97M-D3H
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic 
root=UUID=d1db423d-2a50-49ac-b4e7-fd50d73afaff ro quiet splash 
usbhid.quirks=0x1B1C:0x1B20:0x2448
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-45-generic N/A
   linux-backports-modules-4.8.0-45-generic  N/A
   linux-firmware1.161.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97M-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/30/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97M-D3H
  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/1678477/+subscriptions

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

[Kernel-packages] [Bug 1713884] Re: [CIFS] Fix maximum SMB2 header size

[Stefan Bader]

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

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

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

Title:
  [CIFS] Fix maximum SMB2 header size

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  Won't Fix
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  In Progress

Bug description:
  Currently the maximum size of SMB2/3 header is set incorrectly which
  leads to hanging of directory listing operations on encrypted SMB3
  connections. Fix this by setting the maximum size to 170 bytes that
  is calculated as RFC1002 length field size (4) + transform header
  size (52) + SMB2 header size (64) + create response size (56).

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=47690ab81f4f29b12bbb0676d3579e61ab4d84de

  This applies across the board 3.16, 4.4, 4.10, artful, and azure.
  Microsoft would be happy to help test.

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

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

[Kernel-packages] [Bug 1715271] Re: Middle button of trackpoint doesn't work

[Stefan Bader]

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

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

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

Title:
  Middle button of trackpoint doesn't work

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  Middle button doesn't work on several Thinkpad laptops like E570,
  E475, E470, E575 and X1Carbon.

  When middle button fails to work, logs show:
  psmouse serio2: trackpoint: failed to get extended button data

  It fails to read out ext button info via PS2 command.
  Almost all the Thinkpad have 3 buttons, so set it to 3 button when it fails 
to read button info.

  And on Lenovo X1, there is a new version of trackpoint, add this ID
  for this new device.

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

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

[Kernel-packages] [Bug 1626984] Re: kernel BUG at /build/linux-lts-xenial-_hWfOZ/linux-lts-xenial-4.4.0/security/apparmor/include/context.h:69!

[Stefan Bader]

For Zesty the change was already applied as "UBUNTU: SAUCE: apparmor: fix 
parameters so that the permission test is bypas
sed at boot" (see bug #1678048) in 4.10.0-17.19 (pre release).

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

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

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

Title:
  kernel BUG at /build/linux-lts-xenial-_hWfOZ/linux-lts-
  xenial-4.4.0/security/apparmor/include/context.h:69!

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

Bug description:
  I am runing sosreport on ubuntu 14.04.4 LTS which has upgrade the kernel to 
4.4.0-38-generic, it get oops while copying 
/sys/module/apparmor/parameters/audit. and it also can be triggered with
  cat /sys/module/apparmor/parameters/audit.

  [  213.174092] [ cut here ]
  [  213.174130] kernel BUG at 
/build/linux-lts-xenial-_hWfOZ/linux-lts-xenial-4.4.0/security/apparmor/include/context.h:69!
  [  213.174187] invalid opcode:  [#1] SMP 
  [  213.174215] Modules linked in: ppdev lp joydev serio_raw parport_pc 
parport psmouse virtio_scsi floppy
  [  213.174283] CPU: 0 PID: 2246 Comm: cat Not tainted 4.4.0-38-generic 
#57~14.04.1-Ubuntu
  [  213.174324] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
rel-1.8.2-0-g33fbe13 by qemu-project.org 04/01/2014
  [  213.174380] task: 880037b15780 ti: 8800399c4000 task.ti: 
8800399c4000
  [  213.174419] RIP: 0010:[]  [] 
aa_current_raw_label.part.6+0x4/0x6
  [  213.174478] RSP: 0018:8800399c7d60  EFLAGS: 00010246
  [  213.174506] RAX:  RBX: 88003a426000 RCX: 
88003e3802a0
  [  213.174542] RDX: 88003a426000 RSI: 81ddc0d8 RDI: 
88003a426000
  [  213.174578] RBP: 8800399c7d60 R08: 88003e3802a0 R09: 

  [  213.174614] R10: 1000 R11: 0246 R12: 
81e44ae0
  [  213.174658] R13: 88003e3802a0 R14: 81e4c220 R15: 
88003c2b2e40
  [  213.174702] FS:  7f7bea106740() GS:88003fc0() 
knlGS:
  [  213.174743] CS:  0010 DS:  ES:  CR0: 80050033
  [  213.174781] CR2: 00a40038 CR3: 3cdfa000 CR4: 
06f0
  [  213.174819] Stack:
  [  213.174832]  8800399c7d88 8136d58a 88003a426000 
88003a426000
  [  213.174885]  88003e3802a0 8800399c7da0 8136fda2 
88003e39c5f0
  [  213.174928]  8800399c7dd0 8109a7e4 88003c2b2e40 
81a170c0
  [  213.174971] Call Trace:
  [  213.174996]  [] policy_view_capable+0x1ba/0x220
  [  213.175030]  [] param_get_audit+0x12/0x50
  [  213.175062]  [] param_attr_show+0x54/0xa0
  [  213.175092]  [] module_attr_show+0x1d/0x30
  [  213.175130]  [] sysfs_kf_seq_show+0xc2/0x1a0
  [  213.175162]  [] kernfs_seq_show+0x23/0x30
  [  213.175199]  [] seq_read+0xe5/0x350
  [  213.175227]  [] kernfs_fop_read+0x10d/0x170
  [  213.176170]  [] __vfs_read+0x18/0x40
  [  213.177101]  [] vfs_read+0x7f/0x130
  [  213.178016]  [] SyS_read+0x46/0xa0
  [  213.178932]  [] entry_SYSCALL_64_fastpath+0x16/0x75
  [  213.179814] Code: 80 3d 1a 7f b8 00 00 75 1d 55 be 2e 00 00 00 48 c7 c7 f0 
2f cb 81 48 89 e5 e8 7c 50 cf ff 5d c6 05 fb 7e b8 00 01 c3 55 48 89 e5 <0f> 0b 
b8 01 00 00 00 3e 0f c1 07 ff c0 ff c8 7f 26 80 3d df 7e 
  [  213.182634] RIP  [] aa_current_raw_label.part.6+0x4/0x6
  [  213.183528]  RSP 

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

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

[Kernel-packages] [Bug 1709179] Re: Drop GPL from of_node_to_nid() export to match other arches

[Stefan Bader]

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

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

Title:
  Drop GPL from of_node_to_nid() export to match other arches

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  == SRU Justification ==
  The commit requested in this bug exposes functionality needed by the Nvidia 
device driver on POWER9.

  This patch is a clean cherry pick and specific to powerpc.

  This commit is in mainline as of 4.11-rc1.

  == Comment: #0 - Reza A. Arbab  - 2017-08-07 15:34:04 ==
  We need to backport mainline commit be9ba9ff93cc ("Drop GPL from 
of_node_to_nid() export to match other arches") to the Ubuntu 4.10 kernel.

  This exposes functionality needed by the Nvidia device driver on
  POWER9.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1709179/+subscriptions

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

[Kernel-packages] [Bug 1714420] Re: kernel oops - kvm guest started at boot time

[Stefan Bader]

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

Was fixed in upstream stable 4.4.80 as "KVM: PPC: Book3S HV: Reload HTM
registers explicitly". I will mark this bug as duplicate of the stable
tracking bug for reference.

** This bug has been marked a duplicate of bug 1710646
   Xenial update to 4.4.80 stable 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/1714420

Title:
  kernel oops -  kvm guest started at boot time

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  New

Bug description:
  [SRU Justification]

  [Impact]
  ppc64le system OOPSes shortly after boot when KVM guests are started.

  [Fix]
  Cherry-pick patch e47057151422a67ce08747176fa21cb3b526a2c9

  [Testcase]
  Tested at IBM - boot a machine with a KVM guest configured to start at boot. 
Without this patch, observe OOPS, with this patch, observe no OOPS.

  [Regression Potential]
  Patch is contained in arch/powerpc; so regression potential limited to that 
arch. Patch accepted to kernel stable trees, suggesting others also believe it 
to be of low risk.

  [Original Report]

  [0.00] Linux version 4.4.0-93-generic
  (buildd@bos01-ppc64el-025) (gcc version 5.4.0 20160609 (Ubuntu/IBM
  5.4.0-6ubuntu1~16.04.4) ) #116-Ubuntu SMP Fri Aug 11 16:30:16 UTC 2017
  (Ubuntu 4.4.0-93.116-generic 4.4.79)

  ...
  [  380.184554] KVM guest htab at c0799900 (order 29), LPID 2
  [  380.527576] Facility 'TM' unavailable, exception at 0xd0003aad7f10, 
MSR=90009033
  [  380.527717] Oops: Unexpected facility unavailable exception, sig: 6 [#2]
  [  380.527775] SMP NR_CPUS=2048 NUMA PowerNV
  [  380.527823] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM 
iptable_mangle ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables 
ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user 
xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack br_netfilter 
overlay binfmt_misc bridge stp llc kvm_hv uio_pdrv_genirq uio leds_powernv 
ipmi_powernv ibmpowernv vmx_crypto powernv_rng ipmi_msghandler kvm_pr kvm 
autofs4 xfs btrfs raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 raid10 ses 
enclosure mlx4_en be2net lpfc vxlan mlx4_core scsi_transport_fc ip6_udp_tunnel 
udp_tunnel ipr
  [  380.528781] CPU: 24 PID: 4277 Comm: qemu-system-ppc Tainted: G  D  
   4.4.0-93-generic #116-Ubuntu
  [  380.528861] task: c3c389b0 ti: c01fb2428000 task.ti: 
c01fb2428000
  [  380.528929] NIP: d0003aad7f10 LR: d00037d52a14 CTR: 
d0003aad7e40
  [  380.528997] REGS: c01fb242b7b0 TRAP: 0f60   Tainted: G  D  
(4.4.0-93-generic)
  [  380.529076] MSR: 90009033   CR: 22024848  
XER: 
  [  380.529247] CFAR: d0003aad7ea4 SOFTE: 1
     GPR00: d00037d52a14 c01fb242ba30 d0003aaec018 
c01fdbf6
     GPR04: c01f8580 c01fb242bbc0  

     GPR08: 0001 c3c389b0 0001 
d00037d578f8
     GPR12: d0003aad7e40 cfb4e400  
001f
     GPR16: 3fff7206 0080 3fff892c4390 
3fff7285f200
     GPR20: 010009988430 0100099affd0 3fff7285eb60 
100c1ff0
     GPR24: 3bcf4e10 3fff72040028  
c01fdbf6
     GPR28:  c01f8580 c01fdbf6 
c01f8580
  [  380.530119] NIP [d0003aad7f10] kvmppc_vcpu_run_hv+0xd0/0xff0 [kvm_hv]
  [  380.530188] LR [d00037d52a14] kvmppc_vcpu_run+0x44/0x60 [kvm]
  [  380.530245] Call Trace:
  [  380.530270] [c01fb242ba30] [c01fb242bab0] 0xc01fb242bab0 
(unreliable)
  [  380.530353] [c01fb242bb70] [d00037d52a14] 
kvmppc_vcpu_run+0x44/0x60 [kvm]
  [  380.530436] [c01fb242bba0] [d00037d4f674] 
kvm_arch_vcpu_ioctl_run+0x64/0x170 [kvm]
  [  380.530519] [c01fb242bbe0] [d00037d43918] 
kvm_vcpu_ioctl+0x528/0x7b0 [kvm]
  [  380.530602] [c01fb242bd40] [c02fff60] do_vfs_ioctl+0x480/0x7d0
  [  380.530671] [c01fb242bde0] [c0300384] SyS_ioctl+0xd4/0xf0
  [  380.530742] [c01fb242be30] [c0009204] system_call+0x38/0xb4
  [  380.530837] Instruction dump:
  [  380.530904] e92d02a0 e9290a50 e9290108 792a07e3 41820058 e92d02a0 e9290a50 
e9290108
  [  380.531126] 7927e8a4 78e71f87 40820ed8 e92d02a0 <7d4022a6> f9490ee8 
e92d02a0 7d4122a6
  [  380.531350] ---[ end trace 8f9b3b82f9a07d76 ]---

  Needs kernel patch e47057151422a67ce08747176fa21cb3b526a2c9 according
  to Cyril

  ProblemType: 

[Kernel-packages] [Bug 1717430] Re: [Bug] Thunderbolt-patches: Related to the way the key for secure connection is handled

[Leann Ogasawara]

** Information type changed from Proprietary to Public

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

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

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

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

** Changed in: linux (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 in Ubuntu.
https://bugs.launchpad.net/bugs/1717430

Title:
  [Bug] Thunderbolt-patches: Related to the way the key for secure
  connection is handled

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

Bug description:
  . These patches allow security-related (preventing non-root users from 
reading the key) and functional capability (not blocking “connect once” flow).
  Merged in kernel v 4.14
  8fdd6ab36197 thunderbolt: Remove superfluous check – Needed to enable Allow 
clearing key 
  e545f0d8a54a thunderbolt: Allow clearing the key – user cannot reset the 
device key, without disconnecting device
  0956e4116922 thunderbolt: Make key root-only accessible – security, non-root 
users can read the key, possible security breach

  
  Target Release: 17.10

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

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

[Kernel-packages] [Bug 1711251] Re: vhost guest network randomly drops under stress (kvm)

[Stefan Bader]

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

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

Title:
  vhost guest network randomly drops under stress (kvm)

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  == SRU Justification ==

  A vhost performance patch was introduced in the 4.10 kernel upstream,
  and is currently included in the Zesty 4.10 kernel:

  commit 809ecb9bca6a9424ccd392d67e368160f8b76c92
  Author: Jason Wang 
  Date:   Mon Dec 12 14:46:49 2016 +0800

  vhost: cache used event for better performance

  --

  However I recently hit a functional issue linked to this patch which
  would cause random guests to lose their network connection under
  stress.  This is not architecture specific and more likely to be hit
  with high network stress (i.e. lots of uperf instances).

  The patch author has now reverted this patch upstream:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/vhost?id=8d65843c44269c21e95c98090d9bb4848d473853

  which reads:
  "
  Revert "vhost: cache used event for better performance"
  This reverts commit 809ecb9bca6a9424ccd392d67e368160f8b76c92. Since it
  was reported to break vhost_net. We want to cache used event and use
  it to check for notification. The assumption was that guest won't move
  the event idx back, but this could happen in fact when 16 bit index
  wraps around after 64K entries.

  Signed-off-by: Jason Wang 
  Acked-by: Michael S. Tsirkin 
  Signed-off-by: David S. Miller 
  "

  I am requesting this patch to revert the problematic one be pulled
  into Ubuntu Zesty (anything 4.10+).

  ---uname output---
  Linux p82qvirt 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:19 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8247-22L

  ---Steps to Reproduce---
   I can recreate the scenario with the following setup:
   - on a 20core host, start 20 1core VMs
   - I have a single linux bridge assigned to all guests using virtio
   - start a uperf benchmark between each guest pair (10 total) using a high 
number of uperf nprocs (32)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1711251/+subscriptions

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

[Kernel-packages] [Bug 1717431] Re: [Bug] Thunderbolt-patches: Fixes the issue regarding the order of ACPI calls w.r.t. PCI enumeration

[Leann Ogasawara]

** Information type changed from Proprietary to Public

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

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

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

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

** Also affects: linux (Ubuntu Artful)
   Importance: High
 Assignee: Seth Forshee (sforshee)
   Status: 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/1717431

Title:
  [Bug] Thunderbolt-patches: Fixes the issue regarding the order of ACPI
  calls w.r.t. PCI enumeration

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

Bug description:
  Description:

  Without these patches, TBT device that is connected on boot is usually not 
functional. Only reconnecting after OS up works. This is a serious usability 
issue.
  Merged in kernel v 4.14
  ecc1165b8b74 ACPICA: Dispatch active GPEs at init time 
  1312b7e0caca ACPICA: Make it possible to enable runtime GPEs earlier
  eb7f43c4adb4 ACPI / scan: Enable GPEs before scanning the namespace

  
  Target Release: 17.10

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

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

[Kernel-packages] [Bug 1713821] Re: arm64 arch_timer fixes

[Stefan Bader]

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

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

Title:
  arm64 arch_timer fixes

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

Bug description:
  [Impact]
  This bug captures a few issues with the ARM arch_timer driver:

  1) Some arm64 systems have hardware defects in their architected timer
  implementations that require errata, which we workaround in the
  kernel. However, it's possible that this workaround will not be
  applied if the timer was reset w/ the user access bit set.

  2) The Juno board fails to initialize a timer at boot:

    arch_timer: Unable to map frame @ 0x
    arch_timer: Frame missing phys irq.
    Failed to initialize '/timer@2a81': -22

  3) Possible boot warning from arch_timer_mem_of_init():
     'Trying to vfree() nonexistent vm area'

  4) There's a theoretical problem where the first frame of a timer
  could be used even though a better suited timer frame is available.

  5) An infinite recursion loop will occur when enabling the function
  tracer in builds with CONFIG_PREEMPT_TRACER=y. Ubuntu does not enable
  CONFIG_PREEMPT_TRACER, so this will only be a problem if that changes.

  [Test Case]
  I've regression tested this on both a system w/ an errata workaround 
(HiSilicon D05) and one that is not (Cavium ThunderX CRB1S). In both cases the 
timer was initialized correctly. Verified by looking at the boot messages:

  dannf@d05-3:~$ dmesg | grep arch_timer
  [0.00] arch_timer: Enabling global workaround for HiSilicon erratum 
161010101
  [0.00] arch_timer: CPU0: Trapping CNTVCT access
  [0.00] arch_timer: cp15 timer(s) running at 50.00MHz (phys).
  [0.194241] arch_timer: CPU1: Trapping CNTVCT access
  [0.197305] arch_timer: CPU2: Trapping CNTVCT access
  <.>
  [0.396228] arch_timer: CPU62: Trapping CNTVCT access
  [0.399752] arch_timer: CPU63: Trapping CNTVCT access

  ubuntu@grotrian:~$ dmesg | grep arch_timer
  [0.00] arch_timer: cp15 timer(s) running at 100.00MHz (phys).

  [Regression Risk]
  The regression risk is restricted to ARM systems, as this driver only applies 
there. Regressions could lead to a timer failing to initialize, or a system 
that requires errata not having the appropriate workaround applied. (Which are 
also the  conditions that the suggested backports are attempting to fix).

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

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

[Kernel-packages] [Bug 1708852] Re: Touchpad not detected

[Stefan Bader]

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

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

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

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

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

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

Title:
  Touchpad not detected

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

Bug description:
  SRU Justifications:

  [Impact] 
  Touchpad on Lenovo ideapad 320-14IKB does not work.

  [Test Case]
  After adding the ID to the elan_i2c driver, the touchpad works.

  
  [Regression Potential]
  Very low.
  It only adds device ID to the driver, no functional changes.

  ---

  The touchpad is not working in any linux distribution, but works in
  Windows. It is not getting detected. Seems like a kernel bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-30-generic 4.10.0-30.34
  ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matheus1504 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Aug  5 12:58:21 2017
  InstallationDate: Installed on 2017-08-05 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 5986:1127 Acer, Inc
   Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc.
   Bus 001 Device 002: ID 0101:0007
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80YF
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic.efi.signed 
root=UUID=d7c89f65-c9a7-4e7f-9bce-ed58751f0619 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-30-generic N/A
   linux-backports-modules-4.10.0-30-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN16WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Cairo 4A
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-14IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN16WW:bd02/22/2017:svnLENOVO:pn80YF:pvrLenovoideapad320-14IKB:rvnLENOVO:rnCairo4A:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-14IKB:
  dmi.product.name: 80YF
  dmi.product.version: Lenovo ideapad 320-14IKB
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1716634] Re: linux: 3.13.0-132.181 -proposed tracker

[Brad Figg]

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

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

Title:
  linux: 3.13.0-132.181 -proposed tracker

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

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

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

  backports: 1716635
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1716634/+subscriptions

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

[Kernel-packages] [Bug 1716616] Re: linux-aws: 4.4.0-1002.2 -proposed tracker

[Juerg Haefliger]

** Summary changed:

- linux-aws:  -proposed tracker
+ linux-aws: 4.4.0-1002.2 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger 
(juergh)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger 
(juergh)

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

Title:
  linux-aws: 4.4.0-1002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1716613
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1716616/+subscriptions

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

[Kernel-packages] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72

[Benjamin Knodel]

Same Problem...

- Server 2012 R2 / Ubuntu 16.4.x with Kernel 4.4.0-62 (and virtual DVD-
Drive) was fine for a long time with vm-backup via. Backup Exec.

- Server 2012 R2 / Ubuntu 16.4.x with updated Kernel to 4.4.0-81 (and
virtual DVD-Drive) was crashing a few minutes after vm-backup with
backupexec

- Server 2012 R2 / Ubuntu 16.4.x with updated Kernel to 4.4.0-83 (and
virtual DVD-Drive) was crashing a few minutes after vm-backup with
backupexec

- Server 2012 R2 / Ubuntu 16.4.x with updated Kernel to 4.4.0-83 (with
removed virtual DVD-Drive) was running over some weeks without problems,
but is now crashing after backup-exec-job.

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

Title:
  [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration
  after installing kernel 4.4.0-72

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

Bug description:
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's 
on Hyper-V.
  Microsoft Hyper-v 2012r2 Gen2 VMs

  See Attachment for what happens is immediately after backup starts I
  get an error.

  Eventually the kernel reports it has run out of memory and the machine
  just continuously scrolls errors message related to page allocation.

  When reseting the virtual machine no logs can be found of the problem.

  kernel 4.4.0-72-generic problem still here

  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  SourcePackage: linux-lts-xenial
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  5 12:05 seq
   crw-rw 1 root audio 116, 33 Apr  5 12:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-72-generic N/A
   linux-backports-modules-4.4.0-72-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 10 10:33 seq
   crw-rw 1 root audio 116, 33 Apr 10 10:33 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: 

[Kernel-packages] [Bug 1716483] Re: [SRU][Zesty] Fix lscpu segfault on ARM64 with SMBIOS v2.0

[Stefan Bader]

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

Title:
  [SRU][Zesty] Fix lscpu segfault on ARM64 with SMBIOS v2.0

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Zesty:
  New

Bug description:
  [Impact]
  On ARM64 systems with smbios v2.0, lscpu segfaults. This is caused by the 
fact that lspci issues a read() on /dev/mem at the offset where it expects to 
find the SMBIOS structure array. However, this
  region is classified as EFI_RUNTIME_SERVICE_DATA (as per the UEFI spec), and 
so it is omitted from the linear mapping.

  [Test]
  The issue was observed with kexec/kdump usecases when a FPDT ACPI table is 
presented to HLOS from the firmware.

  [Fix]
  Fixed upstream:
  1151f838cb62 arm64: kernel: restrict /dev/mem read() calls to linear region

  [Regression Potential]
  The patch is confined to ARM64 arch, and applies only to systems with SMBIOS 
v2.0. Risk is low.

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

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

[Kernel-packages] [Bug 1713553] Re: Intel i40e PF reset due to incorrect MDD detection

[Stefan Bader]

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

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

Title:
  Intel i40e PF reset due to incorrect MDD detection

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

Bug description:
  [Impact]

  Using an Intel i40e network device, under heavy traffic load with
  TSO enabled, the device will spontaneously reset itself and issue errors
  similar to the following:

  Jun 14 14:09:51 hostname kernel: [4253913.851053] i40e :05:00.1: TX 
driver issue detected, PF reset issued
  Jun 14 14:09:53 hostname kernel: [4253915.476283] i40e :05:00.1: TX 
driver issue detected, PF reset issued
  Jun 14 14:09:54 hostname kernel: [4253917.411264] i40e :05:00.1: TX 
driver issue detected, PF reset issued

   This causes a full reset of the PF, which causes an interruption
  in traffic flow.

  This was partially fixed by Xenial commit
  12f8cc59d5886b86372f45290166deca57a60d7a, however there is one
  additional upstream commit required to fully fix the issue:

  commit 841493a3f64395b60554afbcaa17f4350f90e764
  Author: Alexander Duyck 
  Date:   Tue Sep 6 18:05:04 2016 -0700

  i40e: Limit TX descriptor count in cases where frag size is
  greater than 16K

   This fix was never backported into the Xenial 4.4 kernel series, but
  is already present in the Xenial HWE (and Zesty) 4.10 kernel.

  [Testcase]

   In this case, the issue occurs at a customer site using i40e based
  Intel network cards with SR-IOV enabled. Under heavy load, the card will
  reset itself as described.

  [Regression Potential]

  As with any change to a network card driver, this may cause
  regressions with network I/O through i40e card(s).  However, this
  specific change only increases the likelyhood that any specific large
  TSO tx will need to be linearized, which will avoid the PF reset.
  Linearizing a TSO tx that did not need to be linearized will not cause
  any failures, it may only decrease performance slightly.  However this
  patch should only cause linearization when required to avoid the MDD
  detection and PF reset.

  [Other Info]

  The previous bug for this issue is bug 1700834.

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

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

[Kernel-packages] [Bug 1716626] Re: linux: 3.19.0-93.101 -proposed tracker

[Taihsiang Ho]

vivid is not supported by cert test anymore because it is EOL.

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

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

Title:
  linux: 3.19.0-93.101 -proposed tracker

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

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

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

  backports: 1716628
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1716626/+subscriptions

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

[Kernel-packages] [Bug 1715812] Re: Neighbour confirmation broken, breaks ARP cache aging

[Stefan Bader]

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

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

Title:
  Neighbour confirmation broken, breaks ARP cache aging

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  New
Status in linux source package in Zesty:
  New

Bug description:
  [SRU Justification]

  [Impact]
  A host can lose access to another host whose MAC address changes if they have 
active connections to other hosts that share a route. The ARP cache does not 
time out as expected - instead the old MAC address is continuously reconfirmed.

  [Fix]
  Apply series [1], which changes the algorithm for neighbour confirmation.
  That is, from upstream:
  51ce8bd4d17a net: pending_confirm is not used anymore 
  0dec879f636f net: use dst_confirm_neigh for UDP, RAW, ICMP, L2TP 
  63fca65d0863 net: add confirm_neigh method to dst_ops 
  c3a2e8370534 tcp: replace dst_confirm with sk_dst_confirm 
  c86a773c7802 sctp: add dst_pending_confirm flag 
  4ff0620354f2 net: add dst_pending_confirm flag to skbuff 
  9b8805a32559 sock: add sk_dst_pending_confirm flag 

  [Test case]
  Create 3 real or virtual systems, all hooked up to a switch.
  One system needs an active-backup bond with fail_over_mac=1 num_grat_arp=0.

  Put all the systems in the same subnet, e.g. 192.168.200.0/24

  Call the system with the bond A, and the other two systems B and C.

  On B, run in 3 shells:
   - netperf -t TCP_RR to C
   - ping -f A
   - watch 'ip -s neigh show 192.168.200.0/24'

  On A, cause the bond to fail over.

  Observe that:

   - without the patches, B intermittently fails to notice the change in
  A's MAC address. This presents as the ping failing and not recovering,
  and the arp table showing the old mac address never timing out and
  never being replace with a new mac address.

   - with the patches, the arp cache times out and B sends another mac
  probe and detects A's new address.

  It helps to use taskset to put ping and netperf on the same CPU, or
  use single-CPU vms.

  See [2] for more details.

  [References]
  [2] Original report: 
https://www.mail-archive.com/netdev@vger.kernel.org/msg138762.html
  [1]: https://www.spinics.net/lists/linux-rdma/msg45907.html

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

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

[Kernel-packages] [Bug 1715609] Re: kernel warning: skb_warn_bad_offload

[Pavel Oskov]

Also reproduced on:
Linux node-dock-b 4.4.0-93-generic #116-Ubuntu SMP Fri Aug 11 21:17:51 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
Running docker in bridge configuration

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

Title:
  kernel warning: skb_warn_bad_offload

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

Bug description:
  Since upgrading to kernel version 4.10.0-33.37, we're seeing a lot of
  call traces triggered by skb_warn_bad_offload in the syslog.

  Regression introduced when fixing this bug?
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705447


  kernel: [570943.49] [ cut here ]
  kernel: [570943.494448] WARNING: CPU: 3 PID: 21982 at 
/build/linux-hwe-YA6IuF/linux-hwe-4.10.0/net/core/dev.c:2576 
skb_warn_bad_offload+0xd1/0x120
  kernel: [570943.494450] e1000e: caps=(0x0030002149a9, 0x) 
len=1701 data_len=1659 gso_size=1480 gso_type=2 ip_summed=0
  kernel: [570943.494451] Modules linked in: udp_diag tcp_diag inet_diag 
echainiv authenc xfrm4_mode_tunnel xt_state binfmt_misc veth xfrm_user 
xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfrm_algo bridge stp 
llc iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_nat_ipv4 nf_nat ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter ip_tables x_tables 
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm ppdev 
irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel 
aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf hci_uart 
ie31200_edac btbcm edac_core intel_pch_thermal btqca serio_raw btintel 
bluetooth parport_pc parport mac_hid intel_lpss_acpi acpi_pad intel_lpss autofs4
  kernel: [570943.494500]  btrfs raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 
e1000e psmouse ptp ahci pps_core libahci wmi pinctrl_sunrisepoint i2c_hid video 
pinctrl_intel hid fjes
  kernel: [570943.494524] CPU: 3 PID: 21982 Comm: charon Tainted: GW
   4.10.0-33-generic #37~16.04.1-Ubuntu
  kernel: [570943.494524] Hardware name: ...
  kernel: [570943.494525] Call Trace:
  kernel: [570943.494541]  
  kernel: [570943.494544]  dump_stack+0x63/0x90
  kernel: [570943.494545]  __warn+0xcb/0xf0
  kernel: [570943.494546]  warn_slowpath_fmt+0x5f/0x80
  kernel: [570943.494547]  ? ___ratelimit+0xa2/0xf0
  kernel: [570943.494549]  skb_warn_bad_offload+0xd1/0x120
  kernel: [570943.494550]  __skb_gso_segment+0x17d/0x190
  kernel: [570943.494564]  validate_xmit_skb+0x14f/0x2a0
  kernel: [570943.494565]  validate_xmit_skb_list+0x43/0x70
  kernel: [570943.494567]  sch_direct_xmit+0x16b/0x1c0
  kernel: [570943.494568]  __dev_queue_xmit+0x47e/0x690
  kernel: [570943.494569]  dev_queue_xmit+0x10/0x20
  kernel: [570943.494570]  ip_finish_output2+0x27a/0x370
  kernel: [570943.494571]  ip_finish_output+0x176/0x270
  kernel: [570943.494571]  ip_output+0x76/0xe0
  kernel: [570943.494572]  ? ip_fragment.constprop.49+0x80/0x80
  kernel: [570943.494573]  ip_forward_finish+0x43/0x70
  kernel: [570943.494574]  ip_forward+0x385/0x460
  kernel: [570943.494575]  ? ip_frag_mem+0x50/0x50
  kernel: [570943.494575]  ip_rcv_finish+0x11b/0x400
  kernel: [570943.494576]  ip_rcv+0x28b/0x3a0
  ...
  kernel: [570943.494632] ---[ end trace f01d0adcc1256afe ]---

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

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

[Kernel-packages] [Bug 1714229] Re: hwclock will set the date to 2/2/2080 with given 2/2/80

[Po-Hsu Lin]

** Tags added: artful

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

Title:
  hwclock will set the date to 2/2/2080 with given 2/2/80

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On node lodygin, run:
  sudo /sbin/hwclock --set --date "2/2/80 03:04:00"

  Will set the date to 2/2/2080. Thus it failed the hwclock test, which
  expect the output of 1980

  This only happen on lodygin, other testing nodes (hainzel, rumford,
  rizzo, fozzie) are good.

  This issue has been tested on Xenial and Zesty, they will all behave
  in the same way.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-93-generic 4.4.0-93.116
  ProcVersionSignature: User Name 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 31 11:27 seq
   crw-rw 1 root audio 116, 33 Aug 31 11:27 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Aug 31 11:36:37 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: AMD Corporation Speedway
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=e54320fc-c0c6-4801-843e-13288cad433e ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-93-generic N/A
   linux-backports-modules-4.4.0-93-generic  N/A
   linux-firmware1.157.11
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: RSW1001E
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Speedway
  dmi.board.vendor: AMD Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: To be filled by O.E.M.
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrRSW1001E:bd07/24/2017:svnAMDCorporation:pnSpeedway:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnSpeedway:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct17:cvrTobefilledbyO.E.M.:
  dmi.product.name: Speedway
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: AMD Corporation

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

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

[Kernel-packages] [Bug 1716626] Re: linux: 3.19.0-93.101 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1716628
  derivatives:
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Tuesday, 12. September 2017 16:04 UTC
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Friday, 15. September 2017 08:02 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1716628
  derivatives:
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Friday, 15. September 2017 08:02 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 3.19.0-93.101 -proposed tracker

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

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

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

  backports: 1716628
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1716626/+subscriptions

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

[Kernel-packages] [Bug 1717455] Re: package linux-image-4.10.0-32-generic 4.10.0-32.36 failed to install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 4

[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 dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1717455

Title:
  package linux-image-4.10.0-32-generic 4.10.0-32.36 failed to
  install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited
  with return code 4

Status in dkms package in Ubuntu:
  New

Bug description:
  all kernel updates failed since I updated to 17.04

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic i686
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Sep 15 09:14:42 2017
  ErrorMessage: run-parts: /etc/kernel/header_postinst.d/dkms exited with 
return code 4
  HibernationDevice: RESUME=UUID=9947be18-3b74-4071-9c48-e6141f4d215b
  InstallationDate: Installed on 2010-05-11 (2683 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  Lsusb:
   Bus 001 Device 002: ID 9710:7830 MosChip Semiconductor MCS7830 10/100 Mbps 
Ethernet adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: LENOVO 20AWA00V00
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=dc4e6352-2043-4579-b6a1-22929b345a6b ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.2
  RfKill:
   
  SourcePackage: dkms
  Title: package linux-image-4.10.0-32-generic 4.10.0-32.36 failed to 
install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with 
return code 4
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/27/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET67WW (2.21 )
  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:bvnLENOVO:bvrGLET67WW(2.21):bd02/27/2014:svnLENOVO:pn20AWA00V00:pvrThinkPadT440p:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: 20AWA00V00
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1717455] Re: package linux-image-4.10.0-32-generic 4.10.0-32.36 failed to install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 4

[Teo West]

I running this ubuntu in a VirtualBox. It seems the error started since
I tried to install the correct VirtualBox GuestExtensions. But I'm not
sure.

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

Title:
  package linux-image-4.10.0-32-generic 4.10.0-32.36 failed to
  install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited
  with return code 4

Status in dkms package in Ubuntu:
  New

Bug description:
  all kernel updates failed since I updated to 17.04

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic i686
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Sep 15 09:14:42 2017
  ErrorMessage: run-parts: /etc/kernel/header_postinst.d/dkms exited with 
return code 4
  HibernationDevice: RESUME=UUID=9947be18-3b74-4071-9c48-e6141f4d215b
  InstallationDate: Installed on 2010-05-11 (2683 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  Lsusb:
   Bus 001 Device 002: ID 9710:7830 MosChip Semiconductor MCS7830 10/100 Mbps 
Ethernet adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: LENOVO 20AWA00V00
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=dc4e6352-2043-4579-b6a1-22929b345a6b ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.2
  RfKill:
   
  SourcePackage: dkms
  Title: package linux-image-4.10.0-32-generic 4.10.0-32.36 failed to 
install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with 
return code 4
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/27/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET67WW (2.21 )
  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:bvnLENOVO:bvrGLET67WW(2.21):bd02/27/2014:svnLENOVO:pn20AWA00V00:pvrThinkPadT440p:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: 20AWA00V00
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1717455] [NEW] package linux-image-4.10.0-32-generic 4.10.0-32.36 failed to install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 4

[Teo West]

Public bug reported:

all kernel updates failed since I updated to 17.04

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-32-generic 4.10.0-32.36
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic i686
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: i386
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Fri Sep 15 09:14:42 2017
ErrorMessage: run-parts: /etc/kernel/header_postinst.d/dkms exited with return 
code 4
HibernationDevice: RESUME=UUID=9947be18-3b74-4071-9c48-e6141f4d215b
InstallationDate: Installed on 2010-05-11 (2683 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
Lsusb:
 Bus 001 Device 002: ID 9710:7830 MosChip Semiconductor MCS7830 10/100 Mbps 
Ethernet adapter
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: LENOVO 20AWA00V00
ProcFB: 0 vboxdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=dc4e6352-2043-4579-b6a1-22929b345a6b ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.2
RfKill:
 
SourcePackage: dkms
Title: package linux-image-4.10.0-32-generic 4.10.0-32.36 failed to 
install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with 
return code 4
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/27/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GLET67WW (2.21 )
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:bvnLENOVO:bvrGLET67WW(2.21):bd02/27/2014:svnLENOVO:pn20AWA00V00:pvrThinkPadT440p:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.name: 20AWA00V00
dmi.product.version: ThinkPad T440p
dmi.sys.vendor: LENOVO

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


** Tags: apport-package i386 zesty

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

Title:
  package linux-image-4.10.0-32-generic 4.10.0-32.36 failed to
  install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited
  with return code 4

Status in dkms package in Ubuntu:
  New

Bug description:
  all kernel updates failed since I updated to 17.04

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic i686
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Sep 15 09:14:42 2017
  ErrorMessage: run-parts: /etc/kernel/header_postinst.d/dkms exited with 
return code 4
  HibernationDevice: RESUME=UUID=9947be18-3b74-4071-9c48-e6141f4d215b
  InstallationDate: Installed on 2010-05-11 (2683 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  Lsusb:
   Bus 001 Device 002: ID 9710:7830 MosChip Semiconductor MCS7830 10/100 Mbps 
Ethernet adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: LENOVO 20AWA00V00
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=dc4e6352-2043-4579-b6a1-22929b345a6b ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.2
  RfKill:
   
  SourcePackage: dkms
  Title: package linux-image-4.10.0-32-generic 4.10.0-32.36 failed to 
install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with 
return code 4
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/27/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET67WW (2.21 )
  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:bvnLENOVO:bvrGLET67WW(2.21):bd02/27/2014:svnLENOVO:pn20AWA00V00:pvrThinkPadT440p:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: 20AWA00V00
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

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

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

[bugproxy]

--- Comment From y...@cn.ibm.com 2017-09-15 03:17 EDT---
(In reply to comment #75)
> The version number is that of the meta package (linux-image-generic). But as
> long as uname -r returns 4.4.0-96-generic the correct kernel is running. And
> it should have the fixes included.

Ok. Thank you for the explanation!

When I installed it today, the version has changed to 119 already.

4.4.0-96-generic #119

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

Title:
  kernel panic -not syncing: Fatal exception: panic_on_oops

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  SRU justification:

  Impact: A race in context flushing is causing a kernel panic on the
  s390x architecture.

  Fix: Using a set of 3 patches (all restricted to arch code), one
  already upstream and the other 2 pending on linux-next. Regression
  risk should be low (limited to arch code and tested).

  Testcase: see below

  ---

  == Comment: #0 - QI YE  - 2017-08-02 04:11:25 ==
  ---Problem Description---
  Ubuntu got kernel panic

  ---uname output---
  #110-Ubuntu SMP Tue Jul 18 12:56:43 UTC 2017 s390x s390x s390x GNU/Linux

  ---Debugger Data---
  PID: 10991  TASK: 19872a0e8 CPU: 2   COMMAND: "hyperkube"
   LOWCORE INFO:
    -psw  : 0x0004c0018000 0x00115fa6
    -function : pcpu_delegate at 115fa6
    -prefix   : 0x7fe42000
    -cpu timer: 0x7ffab2827828aa50
    -clock cmp: 0xd2eb8b31445e4200
    -general registers:
   0x0004e001 0x001283b6
   0xc001 0x8380fcb8
   0x00115f9e 0x0056f6e2
   0x0004 0x00cf9070
   0x0001f3bfc000 0x00112fd8
   0x0001c72bb400 0x0002
   0x7fffc000 0x007c9ef0
   0x00115f9e 0x8380fc18
    -access registers:
   0x03ff 0x7910 00 00
   00 00 00 00
   00 00 00 00
   00 00 00 00
    -control registers:
   0x14066a12 0x7e6d81c7
   0x00011140 00
   0x2aef 0x0400
   0x5000 0x7e6d81c7
   00 00
   00 00
   00 0x00cfc007
   0xdb00 0x00011280
    -floating point registers:
   0x409c7e258000 0x401de4e0
   00 0x3fd24407ab0e073a
   0x3ff0 0x3fee
   0x3fef218f8a7a41a0 0x3fee
   0x0080 00
   0x03ff7f80 0x02aa4940e9e0
   0xd401 0x03ffe81fe110
   00 0x03fff2cfe638

   #0 [8380fc78] smp_find_processor_id at 1160f8
   #1 [8380fc90] machine_kexec at 1135d4
   #2 [8380fcb8] crash_kexec at 1fbb8a
   #3 [8380fd88] panic at 27d0e0
   #4 [8380fe28] die at 1142cc
   #5 [8380fe90] do_low_address at 12215e
   #6 [8380fea8] pgm_check_handler at 7c2ab4
   PSW:  070520018000 02aa267e0e42 (user space)
   GPRS:   02aa2c4fd690 0001
     02aa2c4fd690 03ff7fffee38  0002
     00029c0f 00c42001ea00 0001 0001
     00c42001c5c8 00c42082c1a0 02aa2666325e 03ff7fffed90

  Contact Information = Chee Ye / y...@cn.ibm.com

  Stack trace output:
   no

  Oops output:
   [43200.761465] docker0: port 10(vethb9132e9) entered forwarding state
  [50008.560926] hrtimer: interrupt took 1698076 ns
  [123483.768984] systemd[1]: apt-daily.timer: Adding 7h 34min 22.582204s 
random time.
  [123483.930058] systemd[1]: apt-daily.timer: Adding 2h 18min 14.857162s 
random time.
  [123484.064879] systemd[1]: apt-daily.timer: Adding 10h 46min 2.301756s 
random time.
  [123484.824760] systemd[1]: apt-daily.timer: Adding 6h 16min 22.178655s 
random time.
  [153113.703126] conntrack: generic helper won't handle protocol 47. Please 
consider loading the specific helper module.
  [477085.704538] Low-address protection: 0004 ilc:2 [#1] SMP
  [477085.704551] Modules linked in: xt_physdev veth xt_recent xt_comment 
xt_mark xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 xt_addrtype nf_nat br_netfilter bridge stp llc aufs 
ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 
xt_conntrack nf_conntrack iptable_filter ip_tables x_tables ghash_s390 prng 
aes_s390 des_s390 des_generic sha512_s390 qeth_l2 sha256_s390 qeth sha1_s390 
qdio sha_common 

[Kernel-packages] [Bug 1711358] Re: 20170817 - ISO hangs on boot on qemu with splash screen enabled and qxl graphics driver

[Jean-Baptiste Lallement]

It happens even if you start a VM directly with qemu from the command
line with the qxl driver (option -vga qxl) independently of virt-
manager.

For example, the following command will hang on boot:
/usr/bin/qemu-system-x86_64 -m 2G -smp 2 -localtime -no-reboot -cpu core2duo 
-enable-kvm -drive file=/tmp/disk.img,if=ide,media=disk -boot menu=on -soundhw 
all -display sdl -vga qxl -monitor stdio -cdrom 
/home/j-lallement/iso/ubuntu/artful-desktop-amd64.iso

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

Title:
  20170817 - ISO hangs on boot on qemu with splash screen enabled and
  qxl graphics driver

Status in linux package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  Test Case
  1. Boot artful desktop 20170817 under qemu with qxl
  2. Wait until ubiquity-dm is displayed

  Expected result
  It boots

  Actual result
  It hangs on the splash screen and the dots below the Ubuntu logo are not 
blinking. If the option 'splash' is removed from the boot command line it boots 
successfully.

  It also boots successfully with -vga std but in this case the splash
  screen is in text mode not graphical unlike with the qxl driver.

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

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

[Kernel-packages] [Bug 1708399] Re: kernel panic -not syncing: Fatal exception: panic_on_oops

[Stefan Bader]

The version number is that of the meta package (linux-image-generic).
But as long as uname -r returns 4.4.0-96-generic the correct kernel is
running. And it should have the fixes included.

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

Title:
  kernel panic -not syncing: Fatal exception: panic_on_oops

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  SRU justification:

  Impact: A race in context flushing is causing a kernel panic on the
  s390x architecture.

  Fix: Using a set of 3 patches (all restricted to arch code), one
  already upstream and the other 2 pending on linux-next. Regression
  risk should be low (limited to arch code and tested).

  Testcase: see below

  ---

  == Comment: #0 - QI YE  - 2017-08-02 04:11:25 ==
  ---Problem Description---
  Ubuntu got kernel panic

  ---uname output---
  #110-Ubuntu SMP Tue Jul 18 12:56:43 UTC 2017 s390x s390x s390x GNU/Linux

  ---Debugger Data---
  PID: 10991  TASK: 19872a0e8 CPU: 2   COMMAND: "hyperkube"
   LOWCORE INFO:
    -psw  : 0x0004c0018000 0x00115fa6
    -function : pcpu_delegate at 115fa6
    -prefix   : 0x7fe42000
    -cpu timer: 0x7ffab2827828aa50
    -clock cmp: 0xd2eb8b31445e4200
    -general registers:
   0x0004e001 0x001283b6
   0xc001 0x8380fcb8
   0x00115f9e 0x0056f6e2
   0x0004 0x00cf9070
   0x0001f3bfc000 0x00112fd8
   0x0001c72bb400 0x0002
   0x7fffc000 0x007c9ef0
   0x00115f9e 0x8380fc18
    -access registers:
   0x03ff 0x7910 00 00
   00 00 00 00
   00 00 00 00
   00 00 00 00
    -control registers:
   0x14066a12 0x7e6d81c7
   0x00011140 00
   0x2aef 0x0400
   0x5000 0x7e6d81c7
   00 00
   00 00
   00 0x00cfc007
   0xdb00 0x00011280
    -floating point registers:
   0x409c7e258000 0x401de4e0
   00 0x3fd24407ab0e073a
   0x3ff0 0x3fee
   0x3fef218f8a7a41a0 0x3fee
   0x0080 00
   0x03ff7f80 0x02aa4940e9e0
   0xd401 0x03ffe81fe110
   00 0x03fff2cfe638

   #0 [8380fc78] smp_find_processor_id at 1160f8
   #1 [8380fc90] machine_kexec at 1135d4
   #2 [8380fcb8] crash_kexec at 1fbb8a
   #3 [8380fd88] panic at 27d0e0
   #4 [8380fe28] die at 1142cc
   #5 [8380fe90] do_low_address at 12215e
   #6 [8380fea8] pgm_check_handler at 7c2ab4
   PSW:  070520018000 02aa267e0e42 (user space)
   GPRS:   02aa2c4fd690 0001
     02aa2c4fd690 03ff7fffee38  0002
     00029c0f 00c42001ea00 0001 0001
     00c42001c5c8 00c42082c1a0 02aa2666325e 03ff7fffed90

  Contact Information = Chee Ye / y...@cn.ibm.com

  Stack trace output:
   no

  Oops output:
   [43200.761465] docker0: port 10(vethb9132e9) entered forwarding state
  [50008.560926] hrtimer: interrupt took 1698076 ns
  [123483.768984] systemd[1]: apt-daily.timer: Adding 7h 34min 22.582204s 
random time.
  [123483.930058] systemd[1]: apt-daily.timer: Adding 2h 18min 14.857162s 
random time.
  [123484.064879] systemd[1]: apt-daily.timer: Adding 10h 46min 2.301756s 
random time.
  [123484.824760] systemd[1]: apt-daily.timer: Adding 6h 16min 22.178655s 
random time.
  [153113.703126] conntrack: generic helper won't handle protocol 47. Please 
consider loading the specific helper module.
  [477085.704538] Low-address protection: 0004 ilc:2 [#1] SMP
  [477085.704551] Modules linked in: xt_physdev veth xt_recent xt_comment 
xt_mark xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 xt_addrtype nf_nat br_netfilter bridge stp llc aufs 
ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 
xt_conntrack nf_conntrack iptable_filter ip_tables x_tables ghash_s390 prng 
aes_s390 des_s390 des_generic sha512_s390 qeth_l2 sha256_s390 qeth sha1_s390 
qdio sha_common ccwgroup vmur dasd_eckd_mod dasd_mod
  [477085.705522] CPU: 2 PID: 10991 Comm: hyperkube Not tainted 
4.4.0-87-generic #110-Ubuntu
  [477085.705525] task: 00019872a0e8 ti: 8380c000 task.ti: 
8380c000
  

[Kernel-packages] [Bug 1707610] Re: fanctl does not stop setup on first match

[Stefan Bader]

** Description changed:

  SRU Justification (Zesty/Xenial)
  
  Impact: When /etc/network/fan contains two entries for the same mapping
  (for example on mapping for the generic network mapping and one for a
  specific interface) it will try to set up the same Fan bridge twice.
  
- Fix: Add a break which exits the setup loop once there has been one
- successful run.
+ Fix: Modify fanctl to only bring up enabled networks in auto mode and to
+ correctly apply the most specific local configuration.
  
  Testcase: If in an environment that uses one of the 192.168.0.0/16 subnets, 
and host has for example a 192.168.1.0/24 address. Then trying to use
-  fanatic enable-fan -u 192.168.1.x/24 -o 250.0.0.0/8
+  fanatic enable-fan -u 192.168.1.x/24 -o 250.0.0.0/8
  would show an error now and with the fix applied work ok.
+ 
+ Regression Potential: We tested both cases of using an underlay/overlay
+ combination which is in the template section and one that was using a
+ subset for the underlay. The former was working before the latter not.
+ For that reason we anticipate a low risk of regression.

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

Title:
  fanctl does not stop setup on first match

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  New
Status in ubuntu-fan source package in Zesty:
  Incomplete

Bug description:
  SRU Justification (Zesty/Xenial)

  Impact: When /etc/network/fan contains two entries for the same
  mapping (for example on mapping for the generic network mapping and
  one for a specific interface) it will try to set up the same Fan
  bridge twice.

  Fix: Modify fanctl to only bring up enabled networks in auto mode and
  to correctly apply the most specific local configuration.

  Testcase: If in an environment that uses one of the 192.168.0.0/16 subnets, 
and host has for example a 192.168.1.0/24 address. Then trying to use
   fanatic enable-fan -u 192.168.1.x/24 -o 250.0.0.0/8
  would show an error now and with the fix applied work ok.

  Regression Potential: We tested both cases of using an
  underlay/overlay combination which is in the template section and one
  that was using a subset for the underlay. The former was working
  before the latter not. For that reason we anticipate a low risk of
  regression.

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

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