[Kernel-packages] [Bug 972063] Re: [Dell Inspiron N411Z] Bluetooth Headset pairs but does not show up in Sound Settings profile

[Daniel van Vugt]

** Bug watch removed: Red Hat Bugzilla #827692
   https://bugzilla.redhat.com/show_bug.cgi?id=827692

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

Title:
  [Dell Inspiron N411Z] Bluetooth Headset pairs but does not show up in
  Sound Settings profile

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Expected Result:

  After pairing bluetooth headset the device should then show up in >
  Sound Settings and work like any other audio device

  Actual Result:

  Jabra Halo v2 Bluetooth Headset pairs fine but does not show up in
  sound settings therefore is unusable

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: pulseaudio 1:1.1-0ubuntu13
  ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
  Uname: Linux 3.2.0-21-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bkerensa   2121 F pulseaudio
  Date: Mon Apr  2 20:07:36 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120325)
  ProcEnviron:
   TERM=xterm
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/24/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 0VK06J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: FAB1
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd06/24/2011:svnDellInc.:pnDellSystemInspironN411Z:pvr:rvnDellInc.:rn0VK06J:rvrFAB1:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System Inspiron N411Z
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  InterestingModules: btusb rfcomm bnep bluetooth
  MachineType: Dell Inc. Dell System Inspiron N411Z
  Package: pulseaudio
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic 
root=UUID=281cfb17-fceb-4b60-b002-bbadb81bf79b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Tags:  precise running-unity
  Uname: Linux 3.2.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 06/24/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 0VK06J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: FAB1
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd06/24/2011:svnDellInc.:pnDellSystemInspironN411Z:pvr:rvnDellInc.:rn0VK06J:rvrFAB1:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System Inspiron N411Z
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: AC:72:89:44:9D:8B  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:828 acl:0 sco:0 events:34 errors:0
TX bytes:637 acl:0 sco:0 commands:33 errors:0

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

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

[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

[flux242]

ah, c'mon, how severe could this bug be? You, loosing hours of work
because your system freezes? Who cares? They have more important things
to care about - preparing for ipo and stuff. And don't forget to buy
canonical stocks as they out

canonical you really should mark 17.04 as testing and not recommended
for install

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

Title:
  kernel BUG at /build/linux-
  7LGLH_/linux-4.10.0/include/linux/swapops.h:129

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-edge package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux-hwe-edge source package in Zesty:
  In Progress

Bug description:
  Randomly, khugepaged process will take 100% CPU, and I can only
  restart the computer to recover it.

  Relevant dmesg attached (dmesg_crash.txt).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mathieu2221 F pulseaudio
   /dev/snd/pcmC1D0p:   mathieu2221 F...m pulseaudio
   /dev/snd/controlC1:  mathieu2221 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar 21 23:03:23 2017
  HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd
  InstallationDate: Installed on 2016-01-31 (415 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: LENOVO 20344
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1689408] Re: System hang when utilising OpenGL 4.5 features

[Timo Aaltonen]

great, thanks

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

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

Title:
  System hang when utilising OpenGL 4.5 features

Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  I've found this to be easily reproducible via unigine's heaven
  benchmark, which uses tessellation and other features extensively.
  Simply creating a OpenGL 4.5 context will not trigger the hang, and
  you must explicitly request an OGL 4+ context as the default will only
  be 3.0.

  On a successful trigger, the screen may flicker on and off a few times
  and eventually hang completely on a black screen, there's no way to
  recover the system from this state bar a power cycle (ie hold the
  power button).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  paulh  1405 F pulseaudio
   /dev/snd/controlC0:  paulh  1405 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue May  9 09:14:09 2017
  InstallationDate: Installed on 2017-01-05 (123 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  MachineType: HP HP Notebook
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=a5482167-6676-4a1a-b150-a86255560de6 ro rhgb quiet 
resume=/dev/sda6/swapfile resume_offset=7673856 quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (24 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1C
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8133
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 98.0E
  dmi.chassis.asset.tag: 5CG6124XBK
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1C:bd10/29/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8133:rvrKBCVersion98.0E:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1627474] Re: ath10k_pci 0000:03:00.0: firmware crashed! (uuid n/a)

[Jan Segre]

Although not using Ubuntu, I'm also experiencing this issue on both
4.9.27 and 4.10.15. I have been experiencing this issue since I first
setup my machine a few weeks ago.

This is the pattern that happens often when I leave my machine on:

```
[ 1008.043987] wlp2s0: AP 14:cc:20:da:1e:e5 changed bandwidth, new config is 
2412 MHz, width 2 (2422/0 MHz)
[ 1037.415409] ath10k_pci :02:00.0: firmware crashed! (uuid n/a)
[ 1037.415424] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 
0x00340aff sub 1028:0310
[ 1037.415428] ath10k_pci :02:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 
0 testmode 0
[ 1037.416312] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad 
crc32 75dee6c5
[ 1037.416748] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 
19644295
[ 1037.416753] ath10k_pci :02:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp 
max-sta 32 raw 0 hwcrypto 1
[ 1037.418802] ath10k_pci :02:00.0: firmware register dump:
[ 1037.418808] ath10k_pci :02:00.0: [00]: 0x0503 0x15B3 0x009860FA 
0x00955B31
[ 1037.418812] ath10k_pci :02:00.0: [04]: 0x009860FA 0x00060730 0x0004 
0x0040E8A0
[ 1037.418815] ath10k_pci :02:00.0: [08]: 0x004980AC 0x00955A00 0x000B 
0x0040
[ 1037.418819] ath10k_pci :02:00.0: [12]: 0x0009 0x 0x00952CD0 
0x00952CE6
[ 1037.418822] ath10k_pci :02:00.0: [16]: 0x00952CC4 0x00910712 0x 
0x
[ 1037.418826] ath10k_pci :02:00.0: [20]: 0x409860FA 0x0040E7E8 0x 
0x0041E0DC
[ 1037.418830] ath10k_pci :02:00.0: [24]: 0x800B5A1D 0x0040E848 0x000F 
0xC09860FA
[ 1037.418833] ath10k_pci :02:00.0: [28]: 0x809B3230 0x0040E948 0x0018 
0x004313B8
[ 1037.418837] ath10k_pci :02:00.0: [32]: 0x809B2992 0x0040E998 0x0040E9BC 
0x00429548
[ 1037.418840] ath10k_pci :02:00.0: [36]: 0x8091D252 0x0040E9B8 0x 
0x0001
[ 1037.418844] ath10k_pci :02:00.0: [40]: 0x809FF05D 0x0040EA68 0x0043A380 
0x00429C10
[ 1037.418847] ath10k_pci :02:00.0: [44]: 0x809FCFDB 0x0040EA88 0x0043A380 
0x0001
[ 1037.418851] ath10k_pci :02:00.0: [48]: 0x80911210 0x0040EAD8 0x0010 
0x004041D0
[ 1037.418855] ath10k_pci :02:00.0: [52]: 0x80911154 0x0040EB28 0x0040 
0x
[ 1037.418859] ath10k_pci :02:00.0: [56]: 0x8091122D 0x0040EB48 0x 
0x00400600
[ 1037.502646] ieee80211 phy0: Hardware restart was requested
[ 1039.891557] ath10k_pci :02:00.0: device successfully recovered
[ 2122.645627] wlp2s0: AP 14:cc:20:da:1e:e5 changed bandwidth, new config is 
2412 MHz, width 1 (2412/0 MHz)
```

After that happens (by the time I notice it, after 2122.645627) the
network seems down, even though it reports as connected. It all comes
back after a power off and power on of the card (either soft or hard
works).

Since this happens on a vanilla kernel it is an upstream bug. I'd be
glad to report to upstream if anyone can point to an existing bug or
specific tracker. I just happen to find this issue here and thought it
would be useful to report.

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

Title:
  ath10k_pci :03:00.0: firmware crashed! (uuid n/a)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The wireless card in my Acer V3-372-587T suffers from firmware crashes
  regularly (every 5-10mins approx).

  $ lsb_release -rd
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10

  Checking dmesg I see:

  $ dmesg | grep ath10k 
  [91/214]
  [7.773800] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [8.123875] request_firmware: ath10k/pre-cal-pci-:03:00.0.bin
  [8.126477] ath10k_pci :03:00.0: Direct firmware load for 
ath10k/pre-cal-pci-:03:00.0.bin fa$
  led with error -2
  [8.126481] request_firmware: ath10k/cal-pci-:03:00.0.bin
  [8.126492] ath10k_pci :03:00.0: Direct firmware load for 
ath10k/cal-pci-:03:00.0.bin failed
  with error -2
  [8.126493] request_firmware: ath10k/QCA6174/hw3.0/firmware-5.bin
  [8.127095] ath10k_pci :03:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/firmware-5.bin fa$
  led with error -2
  [8.127098] ath10k_pci :03:00.0: could not fetch firmware file 
'ath10k/QCA6174/hw3.0/firmware-5.$
  in': -2
  [8.127101] request_firmware: ath10k/QCA6174/hw3.0/firmware-4.bin
  [8.129458] ath10k_pci :03:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 105b:e09$
  [8.129460] ath10k_pci :03:00.0: kconfig debug 0 debugfs 0 tracing 0 
dfs 0 testmode 0
  [8.129954] ath10k_pci :03:00.0: firmware ver 
WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowla$
  ,ignore-otp,no-4addr-pad crc32 75dee6c5
  [8.195123] request_firmware: ath10k/QCA6174/hw3.0/boa

[Kernel-packages] [Bug 1689980] Re: AACRAID for power9 platform

[Narinder Gupta]

This is driver enablement for Power 9 so apport-collect does not make
sense.

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

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

Title:
  AACRAID for power9 platform

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello team,
  It seems Microsemi team has requested to backport few AACRAID driver patches 
for Power 9 platform for 17.04 and 16.04.3 kernel.

  Hi Narinder,

  We have submitted a handful of critical fixes for the AACRAID driver
  on to the kernel.org, targeting 4.11. These patches are bug fixes and
  our customer IBM is expecting these patches to go into the 16.04.3
  release, for to use with the Power9 platforms.

  Can you please let me know if these patches will be backported by your
  kernel team on to the upcoming 16.04.3? Do you also have a schedule in
  place for 16.04.3 release?

  Thanks,
  Gana

  Below are the patch details.

  Subject: [PATCH V2 00/19] aacraid: Patchset with reset rework and misc
  fixes

  This patchset primarily focuses on tweaking and hardening the
  controller reset support for both ARC and HBA1000 devices. Now the
  driver can only reset the controller thru eh reset. Included a srb
  memory fix and pci dma allocation fix.

  Changes in V2:
   - Corrected heading and description for srb memory patch and removed stray
 comment.
   - Removed incorrect up function call and cleared fib wait flag after call
 to down interruptible in the ioctl return on ctrl reset patch.
   - Added review acknowledgements by David Carroll thank you Dave for
 finding the above issues in the above 2 patches.

  Raghava Aditya Renukunta (19):
  [SCSI] aacraid: Remove __GFP_DMA for raw srb memory  
  [SCSI] aacraid: Fix DMAR issues with  iommu=pt  
  [SCSI] aacraid: Added 32 and 64 queue depth for arc natives  
  [SCSI] aacraid: Set correct Queue Depth for HBA1000 RAW disks  
  [SCSI] aacraid: Remove reset support from check_health  
  [SCSI] aacraid: Change wait time for fib completion  
  [SCSI] aacraid: Log count info of scsi cmds before reset  
  [SCSI] aacraid: Print ctrl status before eh reset  
  [SCSI] aacraid: Using single reset mask for IOP reset  
  [SCSI] aacraid: Rework IOP reset  
  [SCSI] aacraid: Add periodic checks to see IOP reset status  
  [SCSI] aacraid: Rework SOFT reset code  
  [SCSI] aacraid: Rework aac_src_restart  
  [SCSI] aacraid: Use correct function to get ctrl health  
  [SCSI] aacraid: Make sure ioctl returns on controller reset  
  [SCSI] aacraid: Enable ctrl reset for both hba and arc  
  [SCSI] aacraid: Add reset debugging statements  
  [SCSI] aacraid: Remove reference to Series-9  
  [SCSI] aacraid: Update driver version to 50834

  drivers/scsi/aacraid/aachba.c   |  17 ++-
  drivers/scsi/aacraid/aacraid.h  |  22 +++-  
  drivers/scsi/aacraid/commctrl.c |  15 ++-  
  drivers/scsi/aacraid/comminit.c |  18 +---  
  drivers/scsi/aacraid/commsup.c  |  78 +++---
  drivers/scsi/aacraid/linit.c| 232 
  drivers/scsi/aacraid/src.c  | 136 +--

   7 files changed, 298 insertions(+), 220 deletions(-)

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

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

[Kernel-packages] [Bug 1670930] Re: Laptop wakes up from sleep mode after seconds the second time it's put to sleep

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

Title:
  Laptop wakes up from sleep mode after seconds the second time it's put
  to sleep

Status in linux package in Ubuntu:
  Expired

Bug description:
  Laptop wakes up from sleep mode after seconds the second time it's put
  to sleep. The first time always works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-39-generic 4.8.0-39.42
  ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
  Uname: Linux 4.8.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode icp zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   BEN.PID ZUGR.  BEFEHL
   /dev/snd/controlC0:  richter   18063 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Mar  8 04:57:54 2017
  HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a
  InstallationDate: Installed on 2015-12-12 (451 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20221
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic 
root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro 
rootflags=subvol=ubuntu-main-root
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-39-generic N/A
   linux-backports-modules-4.8.0-39-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (141 days ago)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Nagy Ákos]

I have a same issue with GA-AB350-Gaming3 and Ryzen 1600.
It's sad Gigabyte response, now I buy a new AsRock AB350M Pro4, and in the 
future I don't chose gigabyte.

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

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.

  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.

  
  Following advice from various places, I've tried:disable cpu freq governor 
and cpu handling in acpi settings

  1. add "acpi=off" to boot params

  That helps, allowing me to boot into recovery mode, though it leaves
  me with system seeing only one core, is really slow and still only
  boots in recovery mode.

  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
  option.

  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.

  Some observed problems:

  1. dmesg reports *a lot* of messages like this all the time:

  [  163.362068] ->handle_irq():  87a7e090, 
  [  163.362081] bad_chained_irq+0x0/0x40
  [  163.362089] ->handle_irq():  87a7e090, 
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
  [  163.362090] ->irq_data.chip(): 88587e20, 
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
  [  163.362099] ->handle_irq():  87a7e090, 
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
  [  163.362100] ->irq_data.chip(): 88587e20, 
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0

  I've tried to redirect dmesg to a file, stopped after a short while,
  it generated 400M of those.

  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?

  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
  kernel and google are completely silent about AMDI0040.

  
  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1689886] [Bug #1689886] Please test this kernel and report results for SRU.

[Manoj Iyer]

Jeff,

Could you please test the kernel in PPA 
https://launchpad.net/~centriq-team/+archive/ubuntu/test/ that has 
Joeseph Chang's patch ipmi: Fix kernel panic at ipmi_ssif_thread() on a 
QDF2400 REP system and report your results? 
http://bugs.launchpad.net/bugs/1689886

When you report the test results please include the output of the 
working ipmi command.

Thanks
Manoj Iyer

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

Title:
  QDF2400 kernel oops on ipmitool fru write 0 fru.bin

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  $ sudo ipmitool fru print 0
   Chassis Type : Rack Mount Chassis
   Chassis Part Number : 
   Chassis Serial : 
   Board Mfg Date : Wed Jan 4 14:18:00 2017
   Board Mfg : WIWYNN
   Board Product : REP Board
   Board Serial : 12345
   Board Part Number : 
   Product Manufacturer : WIWYNN
   Product Name : REP
   Product Part Number : ..
   Product Version : EVT
   Product Serial : 
   Product Asset Tag :
  ubuntu@ubuntu:~/FRU$

  ubuntu@ubuntu:~/FRU$ sudo ipmitool fru write 0 fru.bin
  Fru Size : 1024 bytes
  Size to Write : 256 bytes
  [ 1815.412463] Unable to handle kernel NULL pointer dereference at virtual 
address 0025
  [ 1815.419668] pgd = 219ca2168000
  [ 1815.422986] [0025] *pgd=0003ee08d003, *pud=0003ee08e003, 
*pmd=
  [ 1815.431225] Internal error: Oops: 9604 [#1] SMP
  [ 1815.436086] Modules linked in: ipmi_devintf nls_utf8 nls_cp437 vfat fat 
aes_ce_blk ablk_helper cryptd aes_ce_cipher ghash_ce sha2_ce efi_pstore sha1_ce 
sg efivars ipmi_ssif ipmi_msghandler cppc_cpufreq i2c_qup i2c_core efivarfs 
autofs4 ext4 crc16 jbd2 mbcache sd_mod ahci_platform libahci_platform libahci 
xhci_plat_hcd libata xhci_hcd scsi_mod usbcore msm_emac sdhci_acpi sdhci 
usb_common pinctrl_qdf2xxx
  [ 1815.471677] CPU: 7 PID: 1950 Comm: kssif0042 Not tainted 4.7.0-2-generic 
#5~pdaw1.0+bandera.9-Ubuntu
  [ 1815.480789] Hardware name: Default string Default string/Default string, 
BIOS 5.12 12/12/2012
  [ 1815.489296] task: edf1aa074380 ti: edf1a782 task.ti: 
edf1a782
  [ 1815.496772] PC is at ipmi_ssif_thread+0x84/0x128 [ipmi_ssif]
  [ 1815.502407] LR is at ipmi_ssif_thread+0x6c/0x128 [ipmi_ssif]
  [ 1815.508046] pc : [] lr : [] pstate: 
00400145
  [ 1815.515424] sp : edf1a7823de0
  [ 1815.518723] x29: edf1a7823de0 x28: 
  [ 1815.524018] x27:  x26: 
  [ 1815.529313] x25:  x24: 
  [ 1815.534608] x23: edeeb9dbba08 x22: 219c9d0a3000
  [ 1815.539903] x21: 219c9d0a2420 x20: edeeb9dbba00
  [ 1815.545198] x19: edeeb9dbb800 x18: 0014
  [ 1815.550494] x17:  x16: 
  [ 1815.555789] x15:  x14: 
  [ 1815.561084] x13:  x12: 071c71c71c71c71c
  [ 1815.566379] x11: 00ba x10: 0960
  [ 1815.571674] x9 : 0040 x8 : edf1ad28
  [ 1815.576969] x7 :  x6 : edf1aa9f9600
  [ 1815.582264] x5 : edf1ad00 x4 : 
  [ 1815.587560] x3 : 0026 x2 : 0025
  [ 1815.592855] x1 : 0007 x0 : edf1aa2e4c00
  [ 1815.598150]
  [ 1815.599626] Process kssif0042 (pid: 1950, stack limit = 0xedf1a7820020)
  [ 1815.606571] Stack: (0xedf1a7823de0 to 0xedf1a7824000)
  [ 1815.612301] 3de0: edf1a7823e20 219ca122cb1c edf1ab9d5800 
219ca20cdfa8
  [ 1815.620113] 3e00: 219ca1aa2ee8 edeeb9dbb800 219c9d09f590 
edeeb9dbb800
  [ 1815.627925] 3e20:  219ca11c4f10 219ca122ca30 
edf1ab9d5800
  [ 1815.635737] 3e40:    

  [ 1815.643550] 3e60:  219ca12399a8 edeeb9dbb800 
edf1
  [ 1815.651363] 3e80:  edf1a7823e88 edf1a7823e88 

  [ 1815.659175] 3ea0:  edf1a7823ea8 edf1a7823ea8 
cb88537fdc8ba500
  [ 1815.666987] 3ec0:    

  [ 1815.674800] 3ee0:    

  [ 1815.682612] 3f00:    

  [ 1815.690425] 3f20:    

  [ 1815.698237] 3f40:    

  [ 1815.706050] 3f60:    

  [ 1815.713862] 3f80:    

  [ 1815.721675] 3fa0:    

  [ 1815.729487] 3fc

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

[Brad Figg]

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

apport-collect 1689980

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  AACRAID for power9 platform

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello team,
  It seems Microsemi team has requested to backport few AACRAID driver patches 
for Power 9 platform for 17.04 and 16.04.3 kernel.

  Hi Narinder,

  We have submitted a handful of critical fixes for the AACRAID driver
  on to the kernel.org, targeting 4.11. These patches are bug fixes and
  our customer IBM is expecting these patches to go into the 16.04.3
  release, for to use with the Power9 platforms.

  Can you please let me know if these patches will be backported by your
  kernel team on to the upcoming 16.04.3? Do you also have a schedule in
  place for 16.04.3 release?

  Thanks,
  Gana

  Below are the patch details.

  Subject: [PATCH V2 00/19] aacraid: Patchset with reset rework and misc
  fixes

  This patchset primarily focuses on tweaking and hardening the
  controller reset support for both ARC and HBA1000 devices. Now the
  driver can only reset the controller thru eh reset. Included a srb
  memory fix and pci dma allocation fix.

  Changes in V2:
   - Corrected heading and description for srb memory patch and removed stray
 comment.
   - Removed incorrect up function call and cleared fib wait flag after call
 to down interruptible in the ioctl return on ctrl reset patch.
   - Added review acknowledgements by David Carroll thank you Dave for
 finding the above issues in the above 2 patches.

  Raghava Aditya Renukunta (19):
  [SCSI] aacraid: Remove __GFP_DMA for raw srb memory  
  [SCSI] aacraid: Fix DMAR issues with  iommu=pt  
  [SCSI] aacraid: Added 32 and 64 queue depth for arc natives  
  [SCSI] aacraid: Set correct Queue Depth for HBA1000 RAW disks  
  [SCSI] aacraid: Remove reset support from check_health  
  [SCSI] aacraid: Change wait time for fib completion  
  [SCSI] aacraid: Log count info of scsi cmds before reset  
  [SCSI] aacraid: Print ctrl status before eh reset  
  [SCSI] aacraid: Using single reset mask for IOP reset  
  [SCSI] aacraid: Rework IOP reset  
  [SCSI] aacraid: Add periodic checks to see IOP reset status  
  [SCSI] aacraid: Rework SOFT reset code  
  [SCSI] aacraid: Rework aac_src_restart  
  [SCSI] aacraid: Use correct function to get ctrl health  
  [SCSI] aacraid: Make sure ioctl returns on controller reset  
  [SCSI] aacraid: Enable ctrl reset for both hba and arc  
  [SCSI] aacraid: Add reset debugging statements  
  [SCSI] aacraid: Remove reference to Series-9  
  [SCSI] aacraid: Update driver version to 50834

  drivers/scsi/aacraid/aachba.c   |  17 ++-
  drivers/scsi/aacraid/aacraid.h  |  22 +++-  
  drivers/scsi/aacraid/commctrl.c |  15 ++-  
  drivers/scsi/aacraid/comminit.c |  18 +---  
  drivers/scsi/aacraid/commsup.c  |  78 +++---
  drivers/scsi/aacraid/linit.c| 232 
  drivers/scsi/aacraid/src.c  | 136 +--

   7 files changed, 298 insertions(+), 220 deletions(-)

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

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

[Kernel-packages] [Bug 1689980] [NEW] AACRAID for power9 platform

[Narinder Gupta]

Public bug reported:

Hello team,
It seems Microsemi team has requested to backport few AACRAID driver patches 
for Power 9 platform for 17.04 and 16.04.3 kernel.

Hi Narinder,

We have submitted a handful of critical fixes for the AACRAID driver on
to the kernel.org, targeting 4.11. These patches are bug fixes and our
customer IBM is expecting these patches to go into the 16.04.3 release,
for to use with the Power9 platforms.

Can you please let me know if these patches will be backported by your
kernel team on to the upcoming 16.04.3? Do you also have a schedule in
place for 16.04.3 release?

Thanks,
Gana

Below are the patch details.

Subject: [PATCH V2 00/19] aacraid: Patchset with reset rework and misc
fixes

This patchset primarily focuses on tweaking and hardening the controller
reset support for both ARC and HBA1000 devices. Now the driver can only
reset the controller thru eh reset. Included a srb memory fix and pci
dma allocation fix.

Changes in V2:
 - Corrected heading and description for srb memory patch and removed stray
   comment.
 - Removed incorrect up function call and cleared fib wait flag after call
   to down interruptible in the ioctl return on ctrl reset patch.
 - Added review acknowledgements by David Carroll thank you Dave for
   finding the above issues in the above 2 patches.

Raghava Aditya Renukunta (19):
[SCSI] aacraid: Remove __GFP_DMA for raw srb memory  
[SCSI] aacraid: Fix DMAR issues with  iommu=pt  
[SCSI] aacraid: Added 32 and 64 queue depth for arc natives  
[SCSI] aacraid: Set correct Queue Depth for HBA1000 RAW disks  
[SCSI] aacraid: Remove reset support from check_health  
[SCSI] aacraid: Change wait time for fib completion  
[SCSI] aacraid: Log count info of scsi cmds before reset  
[SCSI] aacraid: Print ctrl status before eh reset  
[SCSI] aacraid: Using single reset mask for IOP reset  
[SCSI] aacraid: Rework IOP reset  
[SCSI] aacraid: Add periodic checks to see IOP reset status  
[SCSI] aacraid: Rework SOFT reset code  
[SCSI] aacraid: Rework aac_src_restart  
[SCSI] aacraid: Use correct function to get ctrl health  
[SCSI] aacraid: Make sure ioctl returns on controller reset  
[SCSI] aacraid: Enable ctrl reset for both hba and arc  
[SCSI] aacraid: Add reset debugging statements  
[SCSI] aacraid: Remove reference to Series-9  
[SCSI] aacraid: Update driver version to 50834

drivers/scsi/aacraid/aachba.c   |  17 ++-
drivers/scsi/aacraid/aacraid.h  |  22 +++-  
drivers/scsi/aacraid/commctrl.c |  15 ++-  
drivers/scsi/aacraid/comminit.c |  18 +---  
drivers/scsi/aacraid/commsup.c  |  78 +++---
drivers/scsi/aacraid/linit.c| 232 
drivers/scsi/aacraid/src.c  | 136 +--

 7 files changed, 298 insertions(+), 220 deletions(-)

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

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

Title:
  AACRAID for power9 platform

Status in linux package in Ubuntu:
  New

Bug description:
  Hello team,
  It seems Microsemi team has requested to backport few AACRAID driver patches 
for Power 9 platform for 17.04 and 16.04.3 kernel.

  Hi Narinder,

  We have submitted a handful of critical fixes for the AACRAID driver
  on to the kernel.org, targeting 4.11. These patches are bug fixes and
  our customer IBM is expecting these patches to go into the 16.04.3
  release, for to use with the Power9 platforms.

  Can you please let me know if these patches will be backported by your
  kernel team on to the upcoming 16.04.3? Do you also have a schedule in
  place for 16.04.3 release?

  Thanks,
  Gana

  Below are the patch details.

  Subject: [PATCH V2 00/19] aacraid: Patchset with reset rework and misc
  fixes

  This patchset primarily focuses on tweaking and hardening the
  controller reset support for both ARC and HBA1000 devices. Now the
  driver can only reset the controller thru eh reset. Included a srb
  memory fix and pci dma allocation fix.

  Changes in V2:
   - Corrected heading and description for srb memory patch and removed stray
 comment.
   - Removed incorrect up function call and cleared fib wait flag after call
 to down interruptible in the ioctl return on ctrl reset patch.
   - Added review acknowledgements by David Carroll thank you Dave for
 finding the above issues in the above 2 patches.

  Raghava Aditya Renukunta (19):
  [SCSI] aacraid: Remove __GFP_DMA for raw srb memory  
  [SCSI] aacraid: Fix DMAR issues with  iommu=pt  
  [SCSI] aacraid: Added 32 and 64 queue depth for arc natives  
  [SCSI] aacraid: Set correct Queue Depth for HBA1000 RAW disks  
  [SCSI] aacraid: Remove reset support from check_health  
  [SCSI] aacraid: Change wait time for fib completion  
  [SCSI] aacraid: Log count info of scsi cmds before reset  
  [SCSI] aacraid: Print ctrl status before eh reset  
  [SCSI] aacrai

[Kernel-packages] [Bug 1689408] Re: System hang when utilising OpenGL 4.5 features

[Paul]

https://bugs.freedesktop.org/show_bug.cgi?id=100995

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

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

Title:
  System hang when utilising OpenGL 4.5 features

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  I've found this to be easily reproducible via unigine's heaven
  benchmark, which uses tessellation and other features extensively.
  Simply creating a OpenGL 4.5 context will not trigger the hang, and
  you must explicitly request an OGL 4+ context as the default will only
  be 3.0.

  On a successful trigger, the screen may flicker on and off a few times
  and eventually hang completely on a black screen, there's no way to
  recover the system from this state bar a power cycle (ie hold the
  power button).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  paulh  1405 F pulseaudio
   /dev/snd/controlC0:  paulh  1405 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue May  9 09:14:09 2017
  InstallationDate: Installed on 2017-01-05 (123 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  MachineType: HP HP Notebook
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=a5482167-6676-4a1a-b150-a86255560de6 ro rhgb quiet 
resume=/dev/sda6/swapfile resume_offset=7673856 quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (24 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1C
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8133
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 98.0E
  dmi.chassis.asset.tag: 5CG6124XBK
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1C:bd10/29/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8133:rvrKBCVersion98.0E:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive

[Jan Drewes]

Update: With the above kernel, my system is now running for 16h without
problems, including long periods of both high and very little load.

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

Title:
  APST quirk needed for Samsung 512GB NVMe drive

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

Bug description:
  APST support just landed in the latest Zesty kernel (4.10.0-14.16) as
  part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602.
  That patch has a quirk for certain 256GB Samsung drives found in Dell
  laptops that do not behave well when APST is enabled. I am
  experiencing the same symptoms with the same model laptop except with
  a 512GB Samsung. Prior to manually disabling APST the drive would die
  and system would go down in flames with I/O errors within 20 to 40
  minutes of boot.

  $ sudo nvme list
  Node SN   Model   
 Namespace Usage  Format   FW Rev  
    
 - -- 
 
  /dev/nvme0n1   ** PM951 NVMe SAMSUNG 512GB
 1 500.20  GB / 512.11  GB512   B +  0 B   BXV76D0Q

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ajclayton   3305 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri Mar 31 09:42:38 2017
  InstallationDate: Installed on 2012-09-08 (1665 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic 
root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt 
nouveau.modeset=0 log_buf_len=20M
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  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.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1687267] Re: kernel BUG at /build/linux-2NWldV/linux-4.10.0/include/linux/swapops.h:129!

[Robert Taylor]

Sequence of events:
1) Firefox freezes. 
2) Tries to force close firefox in KDE
3) Window freezes
4) Tries to kill FF using pkill
5) Does not know pkill's commands so tries to open man pkill
6) man freezes inside of terminal emulator
7) Whole system freezes. Keyboard lights do not toggle, no disk activity, can 
not switch to other consoles using Ctr + Alt + F1
8) Force reset of system.


kernel BUG at /build/linux-2NWldV/linux-4.10.0/include/linux/swapops.h:129!
invalid opcode:  [#1] SMP
Modules linked in: bnep binfmt_misc intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm irqbypass joydev input_leds 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_codec_hdmi 
snd_hda_codec_realtek snd_hda_codec_generic pcbc aesni_intel snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep aes_x86_64 snd_pcm snd_seq_midi 
snd_seq_midi_event snd_rawmidi hci_uart shpchp snd_seq snd_seq_device snd_timer 
snd mei_me crypto_simd intel_pch_thermal soundcore btbcm mei glue_helper cryptd 
btqca btintel intel_cstate bluetooth intel_rapl_perf acpi_als kfifo_buf 
industrialio mac_hid acpi_pad intel_lpss_acpi intel_lpss parport_pc ppdev lp 
parport ip_tables x_tables autofs4 hid_generic usbhid mxm_wmi i915 i2c_algo_bit 
drm_kms_helper e1000e syscopyarea sysfillrect sysimgblt ptp
fb_sys_fops pps_core drm ahci libahci wmi i2c_hid video pinctrl_sunrisepoint 
hid pinctrl_intel fjes
CPU: 1 PID: 12522 Comm: firefox Not tainted 4.10.0-20-generic #22-Ubuntu
Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170 Extreme4, 
BIOS P1.00 07/01/2015
task: 8b7a27681700 task.stack: a5aa46ea4000
RIP: 0010:__migration_entry_wait+0x16a/0x180
RSP: :a5aa46ea7d68 EFLAGS: 00010246
RAX: 0017c0048078 RBX: f66e08999ab0 RCX: f66e08999ab0
RDX: 0001 RSI: 8b7a2666a008 RDI: f66e06618040
RBP: a5aa46ea7d80 R08: 8b7c53513e00 R09: 8b7c53513e00
R10: 7f3b6d400119 R11: 0206 R12: f66e06618040
R13: 3e198601 R14: a5aa46ea7e30 R15: 8b7a27a9d708
FS:  7f3b6e7be740() GS:8b7c6ec4() knlGS:
CS:  0010 DS:  ES:  CR0: 80050033
CR2: 7f3b03001588 CR3: 000227afb000 CR4: 003406e0
DR0:  DR1:  DR2: 
DR3:  DR6: fffe0ff0 DR7: 0400
Call Trace:
migration_entry_wait+0x74/0x80
  do_swap_page+0x5b3/0x770
  ? futex_wake+0x90/0x170
  handle_mm_fault+0x873/0x1360
  __do_page_fault+0x23e/0x4e0
  do_page_fault+0x22/0x30
  page_fault+0x28/0x30
RIP: 0033:0x5578da41de4b
RSP: 002b:7ffe5edb51a0 EFLAGS: 00010246
RAX: 7f3b05701688 RBX: 7f3b6d400118 RCX: 7f3b03001580
RDX: 7f3b02601790 RSI: 7f3b05801790 RDI: 7f3b02601790
RBP: 7f3b02601790 R08: 6000 R09: 7f3b04300710
R10: 7f3b6d400119 R11: 0206 R12: 7f3b6d400110
R13: 7f3b6d400118 R14: 7f3b05801790 R15: 7f3b04300350
Code: ff ff ff 4c 89 e7 e8 96 a2 f8 ff e9 3c ff ff ff 85 d2 0f 84 2a ff ff ff 
8d 4a 01 89 d0 f0 41 0f b1 4d 00 39 d0 74 81 89 c2 eb e5 <0f> 0b 4c 89 e7 e8 0c 
fb f9 ff eb b8 4c 8d 60 ff 4c 8d 68 1b eb 
RIP: __migration_entry_wait+0x16a/0x180 RSP: a5aa46ea7d68
---[ end trace c3166351e2a21ab7 ]---

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

Title:
  kernel BUG at /build/linux-
  2NWldV/linux-4.10.0/include/linux/swapops.h:129!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  First traceback looks to be the cause.  The second traceback is the
  effect that followed (repeatedly).

  Don't think it's specific to system76.

  
  Apr 30 09:56:10 galago kernel: [97085.090114] [ cut here 
]
  Apr 30 09:56:10 galago kernel: [97085.090137] kernel BUG at 
/build/linux-2NWldV/linux-4.10.0/include/linux/swapops.h:129!
  Apr 30 09:56:10 galago kernel: [97085.090157] invalid opcode:  [#1] SMP
  Apr 30 09:56:10 galago kernel: [97085.090167] Modules linked in: 
nls_iso8859_1 uas usb_storage ccm rfcomm 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 xt_conntrack nf_nat nf_conntrack libcrc32c 
br_netfilter bridge stp llc aufs ec_sys cmac bnep arc4 intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm 
irqbypass crct10dif_pclmul crc32_pclmul snd_hda_codec_via ghash_clmulni_intel 
snd_hda_codec_generic pcbc snd_hda_intel snd_hda_codec iwlmvm snd_hda_core 
snd_hwdep aesni_intel snd_pcm uvcvideo mac80211 aes_x86_64 snd_seq_midi 
videobuf2_vmalloc crypto_simd snd_seq_midi_event glue_helper videobuf2_memops 
cryptd videobuf2_v4l2 btusb snd_rawmidi videobuf2_core btrtl snd_seq btbcm 
intel_cstate videodev btintel
  Apr 30 09:56:10 galago kernel: [97085.090334]  bluetooth snd_seq_device media 
intel_rapl_perf i

[Kernel-packages] [Bug 1447664] Re: 14e4:1687 broadcom tg3 network driver disconnects under high load

[Christopher M. Penalver]

** Tags removed: kernel-bug-exists-upstream-4.0
** Tags added: kernel-bug-exists-upstream-4.11

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

Title:
  14e4:1687 broadcom tg3 network driver disconnects under high load

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

Bug description:
  The tg3 broadcom network driver that binds with chipset 5762 goes offline and 
unable to recover (even with tg3 watchdog timeout) when network transmit is 
under high load.  Call trace:
  https://launchpadlibrarian.net/204185480/dmesg

  When this happens, only a reboot would be able to fix it.  Sometimes,
  however, bringing the interface offline and online (via ifconfig)
  would recover networking.  I've also tested with the latest tg3 driver
  (dec 2014 version) and networking is still problematic.  I have also
  disabled TSO, GSO etc... with ethtool and the bug still surfaces.
  This bug may be related to the integrated Firmware.

  Here is the procedure to replicate the issue because it is hard to
  replicate it under moderate network load.

  1. Bootup a machine with a broadcom 5762 NIC (ie. HP DeskElite 705) using a 
Ubuntu/Kubunu Live CD 14.04-15.04.
  2. from another machine: start 5 sessions, repetitively copy (scp with public 
key authentication) a 70 meg file back and forth to the tg3 machine in each 
session. (not sure if this is necessary)
  3. create a 1GB file on the tg3 machine, with something like dd 
if=/dev/urandom of=/my/test/file bs=1024 count=$((1024*1000))
  4. from another machine: repetitively scp copy that 1GB file from the tg3 
machine. This can be done with something like:

  while [ 0 ]; do
     scp -i /my/scp/private.key u...@ip.of.tg3:/my/test/file /tmp
  done;

  Networking will mostly goes offline in about 10-30 minutes.

  WORKAROUND: Add udev rule to make the changes permanent in 
/etc/udev/rules.d/80-tg3-fix.rules :
  ACTION=="add", SUBSYSTEM=="net", ATTRS{vendor}=="0x14e4", 
ATTRS{device}=="0x1687", RUN+="/sbin/ethtool -K %k highdma off"

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-15-generic 3.19.0-15.15
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kubuntu3748 F pulseaudio
   /dev/snd/controlC0:  kubuntu3748 F pulseaudio
  CasperVersion: 1.360
  Date: Thu Apr 23 11:16:24 2015
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  LiveMediaBuild: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Hewlett-Packard HP EliteDesk 705 G1 MT
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper maybe-ubiquity quiet splash ---
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  RfKill:

  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/22/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L06 v02.15
  dmi.board.asset.tag: 2UA5041TG4
  dmi.board.name: 2215
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA5041TG4
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL06v02.15:bd10/22/2014:svnHewlett-Packard:pnHPEliteDesk705G1MT:pvr:rvnHewlett-Packard:rn2215:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP EliteDesk 705 G1 MT
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1689383] Re: Broadcom BCM5762 Ethernet tg3 times out with stack trace

[Christopher M. Penalver]

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

Daniel, despite the duplicate status, to maximize the probability of
this bug being addressed by developers, you will want to contact them as
advised in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689383/comments/19
.

Could you please advise?

** Attachment removed: "error_dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689383/+attachment/4874927/+files/error_dmesg.log

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

Title:
  Broadcom BCM5762 Ethernet tg3 times out with stack trace

Status in linux package in Ubuntu:
  Triaged

Bug description:
  The ethernet driver will disconnect with dmesg reporting a stack trace and a 
time out:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689383/+attachment/4873674/+files/CurrentDmesg.txt

  The computer doesn't have to have network activity in order to trigger
  this to happen, and it usually happens within a few minutes after
  bootup.

  
  ---
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pmlinux64   1532 F pulseaudio
   /dev/snd/controlC0:  pmlinux64   1532 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=348ce048-e1ac-41dc-9c2b-ad0587ae3f89
  MachineType: Hewlett-Packard HP EliteDesk 705 G1 MT
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-51-generic 
root=UUID=3e798621-37cf-4518-a8fd-886ce43416d0 ro quiet splash
  ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-51-generic N/A
   linux-backports-modules-4.8.0-51-generic  N/A
   linux-firmware1.157.8
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  StagingDrivers: r8712u
  Tags:  xenial staging
  Uname: Linux 4.8.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/11/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L06 v02.17
  dmi.board.asset.tag: 2UA5301Y6H
  dmi.board.name: 2215
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA5301Y6H
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL06v02.17:bd12/11/2014:svnHewlett-Packard:pnHPEliteDesk705G1MT:pvr:rvnHewlett-Packard:rn2215:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP EliteDesk 705 G1 MT
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

[Nazar Mokrynskyi]

I agree that this should be released much faster. For instance, one bug
I found in btrfs-progs that was fixed in less that a week after 2 weeks
from reporting was fixed in Ubuntu, while bug only affected small subset
of btrfs users with additional features and didn't actually corrupt or
hang anything. Waiting almost 3 weeks to release something that causes
many systems to hang randomly is way too long. Consider releasing this
sooner, please.

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

Title:
  kernel BUG at /build/linux-
  7LGLH_/linux-4.10.0/include/linux/swapops.h:129

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-edge package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux-hwe-edge source package in Zesty:
  In Progress

Bug description:
  Randomly, khugepaged process will take 100% CPU, and I can only
  restart the computer to recover it.

  Relevant dmesg attached (dmesg_crash.txt).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mathieu2221 F pulseaudio
   /dev/snd/pcmC1D0p:   mathieu2221 F...m pulseaudio
   /dev/snd/controlC1:  mathieu2221 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar 21 23:03:23 2017
  HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd
  InstallationDate: Installed on 2016-01-31 (415 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: LENOVO 20344
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

[Mathieu Pellerin]

Hmm, a June 5 release date for this fix seems to be wait too late for
the severity of this system freeze bug. A large number of people who run
Ubuntu now (either long-time users or newcomers testing the desktop
platform) has his/her computer crash every hour or so. On that basis,
shouldn't Canonical speed up the fix delivery?

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

Title:
  kernel BUG at /build/linux-
  7LGLH_/linux-4.10.0/include/linux/swapops.h:129

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-edge package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux-hwe-edge source package in Zesty:
  In Progress

Bug description:
  Randomly, khugepaged process will take 100% CPU, and I can only
  restart the computer to recover it.

  Relevant dmesg attached (dmesg_crash.txt).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mathieu2221 F pulseaudio
   /dev/snd/pcmC1D0p:   mathieu2221 F...m pulseaudio
   /dev/snd/controlC1:  mathieu2221 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar 21 23:03:23 2017
  HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd
  InstallationDate: Installed on 2016-01-31 (415 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: LENOVO 20344
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1689383] Re: Broadcom BCM5762 Ethernet tg3 times out with stack trace

[Daniel]

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

Readding attachment with proper file extension so browsers can display
it properly.

** Attachment added: "error_dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689383/+attachment/4874928/+files/error_dmesg.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/1689383

Title:
  Broadcom BCM5762 Ethernet tg3 times out with stack trace

Status in linux package in Ubuntu:
  Triaged

Bug description:
  The ethernet driver will disconnect with dmesg reporting a stack trace and a 
time out:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689383/+attachment/4873674/+files/CurrentDmesg.txt

  The computer doesn't have to have network activity in order to trigger
  this to happen, and it usually happens within a few minutes after
  bootup.

  
  ---
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pmlinux64   1532 F pulseaudio
   /dev/snd/controlC0:  pmlinux64   1532 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=348ce048-e1ac-41dc-9c2b-ad0587ae3f89
  MachineType: Hewlett-Packard HP EliteDesk 705 G1 MT
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-51-generic 
root=UUID=3e798621-37cf-4518-a8fd-886ce43416d0 ro quiet splash
  ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-51-generic N/A
   linux-backports-modules-4.8.0-51-generic  N/A
   linux-firmware1.157.8
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  StagingDrivers: r8712u
  Tags:  xenial staging
  Uname: Linux 4.8.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/11/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L06 v02.17
  dmi.board.asset.tag: 2UA5301Y6H
  dmi.board.name: 2215
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA5301Y6H
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL06v02.17:bd12/11/2014:svnHewlett-Packard:pnHPEliteDesk705G1MT:pvr:rvnHewlett-Packard:rn2215:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP EliteDesk 705 G1 MT
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1689383] Re: Broadcom BCM5762 Ethernet tg3 times out with stack trace

[Daniel]

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

Uploading dmesg output when running with kernel 4.11.0-041100-generic
for reference

** Attachment added: "error_dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689383/+attachment/4874927/+files/error_dmesg.log

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

Title:
  Broadcom BCM5762 Ethernet tg3 times out with stack trace

Status in linux package in Ubuntu:
  Triaged

Bug description:
  The ethernet driver will disconnect with dmesg reporting a stack trace and a 
time out:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689383/+attachment/4873674/+files/CurrentDmesg.txt

  The computer doesn't have to have network activity in order to trigger
  this to happen, and it usually happens within a few minutes after
  bootup.

  
  ---
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pmlinux64   1532 F pulseaudio
   /dev/snd/controlC0:  pmlinux64   1532 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=348ce048-e1ac-41dc-9c2b-ad0587ae3f89
  MachineType: Hewlett-Packard HP EliteDesk 705 G1 MT
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-51-generic 
root=UUID=3e798621-37cf-4518-a8fd-886ce43416d0 ro quiet splash
  ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-51-generic N/A
   linux-backports-modules-4.8.0-51-generic  N/A
   linux-firmware1.157.8
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  StagingDrivers: r8712u
  Tags:  xenial staging
  Uname: Linux 4.8.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/11/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L06 v02.17
  dmi.board.asset.tag: 2UA5301Y6H
  dmi.board.name: 2215
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA5301Y6H
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL06v02.17:bd12/11/2014:svnHewlett-Packard:pnHPEliteDesk705G1MT:pvr:rvnHewlett-Packard:rn2215:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP EliteDesk 705 G1 MT
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1689390] Re: Kernel 4.11 update

[ashirviskas]

Sorry, there actually is a new patch:
https://pkgs.rpmfusion.org/cgit/nonfree/nvidia-340xx-
kmod.git/plain/4.11_kernel.patch

Good luck!

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

Title:
  Kernel 4.11 update

Status in dkms package in Ubuntu:
  New

Bug description:
  I was trying to update my Ubuntu 16.04 with the last kernel version.
  My current version is
  uname -r
  4.8.8-040808-generic
  And I would like to update the kernel to the new 4.11.

  I downloaded from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/ the 
files
linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb
linux-headers-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb
linux-image-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb
  to a folder, there I executed the first one without errors, but on the second 
one I have a problem.

  This is the log generated on the installation...

  root@Ratrichus-HP-ENVY-17:/home/alucasr/Descargas/SW/Kernels# dpkg -i 
linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb 
  Seleccionando el paquete linux-headers-4.11.0-041100 previamente no 
seleccionado.
  (Leyendo la base de datos ... 389575 ficheros o directorios instalados 
actualmente.)
  Preparando para desempaquetar 
linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb ...
  Desempaquetando linux-headers-4.11.0-041100 (4.11.0-041100.201705041534) ...
  Configurando linux-headers-4.11.0-041100 (4.11.0-041100.201705041534) ...

  root@Ratrichus-HP-ENVY-17:/home/alucasr/Descargas/SW/Kernels# dpkg -i 
linux-headers-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb 
  Seleccionando el paquete linux-headers-4.11.0-041100-generic previamente no 
seleccionado.
  (Leyendo la base de datos ... 407178 ficheros o directorios instalados 
actualmente.)
  Preparando para desempaquetar 
linux-headers-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb ...
  Desempaquetando linux-headers-4.11.0-041100-generic 
(4.11.0-041100.201705041534) ...
  Configurando linux-headers-4.11.0-041100-generic (4.11.0-041100.201705041534) 
...
  Examining /etc/kernel/header_postinst.d.
  run-parts: executing /etc/kernel/header_postinst.d/dkms 4.11.0-041100-generic 
/boot/vmlinuz-4.11.0-041100-generic
  ERROR (dkms apport): kernel package linux-headers-4.11.0-041100-generic is 
not supported
  Error! Bad return status for module build on kernel: 4.11.0-041100-generic 
(x86_64)
  Consult /var/lib/dkms/nvidia-304/304.135/build/make.log for more information.

  
  I have attached the make.log file.

  How could I make the update?
  Thank you very much in advance
  Kind regards

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

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

[Kernel-packages] [Bug 1689390] Re: Kernel 4.11 update

[ashirviskas]

Your problem is that Nvidia experiences errors when building for this
kernel. It needs a new patch, try contacting people here:

https://devtalk.nvidia.com/default/topic/968448/linux/304-135-driver-
does-not-build-on-4-10-kernels/2

https://devtalk.nvidia.com/default/topic/995636/-patches-378-13-4-10-and-4-11-rc5/

Or you could use a patch for 4.10 and install 4.10 kernel.

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

Title:
  Kernel 4.11 update

Status in dkms package in Ubuntu:
  New

Bug description:
  I was trying to update my Ubuntu 16.04 with the last kernel version.
  My current version is
  uname -r
  4.8.8-040808-generic
  And I would like to update the kernel to the new 4.11.

  I downloaded from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/ the 
files
linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb
linux-headers-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb
linux-image-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb
  to a folder, there I executed the first one without errors, but on the second 
one I have a problem.

  This is the log generated on the installation...

  root@Ratrichus-HP-ENVY-17:/home/alucasr/Descargas/SW/Kernels# dpkg -i 
linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb 
  Seleccionando el paquete linux-headers-4.11.0-041100 previamente no 
seleccionado.
  (Leyendo la base de datos ... 389575 ficheros o directorios instalados 
actualmente.)
  Preparando para desempaquetar 
linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb ...
  Desempaquetando linux-headers-4.11.0-041100 (4.11.0-041100.201705041534) ...
  Configurando linux-headers-4.11.0-041100 (4.11.0-041100.201705041534) ...

  root@Ratrichus-HP-ENVY-17:/home/alucasr/Descargas/SW/Kernels# dpkg -i 
linux-headers-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb 
  Seleccionando el paquete linux-headers-4.11.0-041100-generic previamente no 
seleccionado.
  (Leyendo la base de datos ... 407178 ficheros o directorios instalados 
actualmente.)
  Preparando para desempaquetar 
linux-headers-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb ...
  Desempaquetando linux-headers-4.11.0-041100-generic 
(4.11.0-041100.201705041534) ...
  Configurando linux-headers-4.11.0-041100-generic (4.11.0-041100.201705041534) 
...
  Examining /etc/kernel/header_postinst.d.
  run-parts: executing /etc/kernel/header_postinst.d/dkms 4.11.0-041100-generic 
/boot/vmlinuz-4.11.0-041100-generic
  ERROR (dkms apport): kernel package linux-headers-4.11.0-041100-generic is 
not supported
  Error! Bad return status for module build on kernel: 4.11.0-041100-generic 
(x86_64)
  Consult /var/lib/dkms/nvidia-304/304.135/build/make.log for more information.

  
  I have attached the make.log file.

  How could I make the update?
  Thank you very much in advance
  Kind regards

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

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

[Kernel-packages] [Bug 1689946] Suggested patch for the fix.

[bugproxy]

Default Comment by Bridge

** Attachment added: "Suggested patch for the fix."
   
https://bugs.launchpad.net/bugs/1689946/+attachment/4874889/+files/0001-blk-mq-NVMe-512B-4K-T10-DIF-DIX-format-returns-I-O-e.patch

** Changed in: ubuntu
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

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

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

Title:
  Ubuntu16.04: NVMe 4K+T10 DIF/DIX format returns I/O error on dd with
  split op

Status in linux package in Ubuntu:
  New

Bug description:
   State: Open by: mdate on 19 March 2017 12:33:34 

  On a Bolt adapter in a system with Ubuntu 16.04, I've formatted the
  Bolt for T10 and am using it to do a dd with a 2M block size.

  Here are the commands:
  nvme format /dev/nvme0n1 --lbaf=1 --pil=0 --ms=0 --pi=2

  dd if=/dev/urandom of=/dev/nvme0n1 bs=2M oflag=direct count=1

  I get an error on the dd.
root@x1623bp1:~# dd if=/dev/urandom of=/dev/nvme0n1 bs=2M oflag=direct 
count=1
dd: error writing '/dev/nvme0n1': Input/output error
1+0 records in
0+0 records out
0 bytes copied, 0.0525061 s, 0.0 kB/s

  dmesg shows:
  [589997.985151] blk_update_request: I/O error, dev nvme0n1, sector 0

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

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

[Kernel-packages] [Bug 1689946] [NEW] Ubuntu16.04: NVMe 4K+T10 DIF/DIX format returns I/O error on dd with split op

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

 State: Open by: mdate on 19 March 2017 12:33:34 

On a Bolt adapter in a system with Ubuntu 16.04, I've formatted the Bolt
for T10 and am using it to do a dd with a 2M block size.

Here are the commands:
nvme format /dev/nvme0n1 --lbaf=1 --pil=0 --ms=0 --pi=2

dd if=/dev/urandom of=/dev/nvme0n1 bs=2M oflag=direct count=1

I get an error on the dd.
root@x1623bp1:~# dd if=/dev/urandom of=/dev/nvme0n1 bs=2M oflag=direct 
count=1
dd: error writing '/dev/nvme0n1': Input/output error
1+0 records in
0+0 records out
0 bytes copied, 0.0525061 s, 0.0 kB/s

dmesg shows:
[589997.985151] blk_update_request: I/O error, dev nvme0n1, sector 0

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-152710 severity-high 
targetmilestone-inin16043
-- 
Ubuntu16.04: NVMe 4K+T10 DIF/DIX format returns I/O error on dd with split op
https://bugs.launchpad.net/bugs/1689946
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1242408] Re: Whole system freezes while copying files

[Jacob Solvemybug]

I have the same issue, that's the second time I'm trying to copy 250GB from a 
NTFS partition of my internal harddrive to my Ntfs external hard drive (usb3) 
and then it frozen after random time from beginnig...
I'm currently seeing the External drive del blinking so I'm waiting it stop and 
then I'll make SysReq 
This bug should be fix!
Ubuntu 17.04, kernel 4.10.~20, completly frozen : Ctrl-Alt-F1 isn't working...

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

Title:
  Whole system freezes while copying files

Status in linux package in Ubuntu:
  Expired

Bug description:
  The same issue occurred to me 3 times today in Ubuntu 13.10, under
  different circumstances.

  I was copying files in Nautilus from my internal HD to an external HD,
  when after about one minute the whole system froze to the point that I
  had to shut down my PC brutally using the power button.

  Here are the details about the drives and partitions:
  - Internal: 500 GB drive, 460 GB NTFS partition, distinct from my Ubuntu 
partition
  - External: 1 TB, one single NTFS partition

  I've been using Ubuntu for just about 4 weeks, but before today I'd been 
reading and writing from both drives involved without any issue. I was not able 
to clearly identify the particular conditions that were causing the copy 
operation to fail, as the circumstances varied:
  - In one occurrence of the bug, I also had a second external HD (320 GB) 
plugged in; however, when the problem reoccurred this was no longer the case.
  - The folder I was trying to copy that first caused the issue was an SVN 
repository (30 MB). However, I was subsequently able to copy it succesfully. 
Besides, later on the issue occurred with a different folder containing photos 
(12 GB).

  **EDIT**: After the issue occurred again, I feel like I should add
  some more details regarding how exactly it manifests.

  The exact symptoms of the freeze are variable:
  - Sometimes, the system just gets downright frozen - I can't do anything, 
even move the mouse.
  - Sometimes, I'm able to move the mouse around, but that's all I can do.
  - Last time it happened, when I saw that the copying was blocked I was able 
to close the copy dialog. But a few seconds afterwards, all Nautilus windows 
were grayed out, so I pressed Alt+F2 in order to open xkill. The menu did open, 
but the system then froze before I could launch xkill. **END OF EDIT**

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  Date: Sun Oct 20 20:11:57 2013
  InstallationDate: Installed on 2013-09-30 (19 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130829)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1689365] Re: ibmvscsis: Do not send aborted task response

[bugproxy]

** Tags removed: architecture-ppc64le
** Tags added: architecture-ppc64

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

Title:
  ibmvscsis: Do not send aborted task response

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

Bug description:
  ---Problem Description---
  ibmvscsis: Do not send aborted task response

  The driver is sending a response to the actual scsi op that was
  aborted by an abort task TM, while LIO is sending a response to
  the abort task TM.

  ibmvscsis_tgt does not send the response to the client until
  release_cmd time. The reason for this was because if we did it
  at queue_status time, then the client would be free to reuse the
  tag for that command, but we're still using the tag until the
  command is released at release_cmd time, so we chose to delay
  sending the response until then. That then caused this issue, because
  release_cmd is always called, even if queue_status is not.

  SCSI spec says that the initiator that sends the abort task
  TM NEVER gets a response to the aborted op and with the current
  code it will send a response. Thus this fix will remove that response
  if the CMD_T_ABORTED && !CMD_T_TAS.

  Another case with a small timing window is the case where if LIO sends a
  TMR_DOES_NOT_EXIST, and the release_cmd callback is called for the TMR Abort
  cmd before the release_cmd for the (attemped) aborted cmd, then we need to
  ensure that we send the response for the (attempted) abort cmd to the client
  before we send the response for the TMR Abort cmd.

  [PATCH v3] ibmvscsis: Do not send aborted task response
  https://www.spinics.net/lists/stable/msg170418.html

  This patch also requires a patch that was accepted upstream which is:

  target: Fix unknown fabric callback queue-full errors
  https://patchwork.kernel.org/patch/9405013/
   
  ---uname output---
  Latest Yakkety master branch
   
  Machine Type = P8 

  ---Steps to Reproduce---
   Send abort ops over and over and you will hit it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1689365/+subscriptions

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

[Kernel-packages] [Bug 1677685] Re: Target: Configfs Crashes and kernel crash fixes

[bugproxy]

--- Comment From b...@us.ibm.com 2017-05-10 16:12 EDT---
Works fine

** Tags added: verification-done-xenial verification-done-yakkety
verification-done-zesty

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

Title:
  Target: Configfs Crashes and kernel crash fixes

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

Bug description:
  A number of patches that need to be backported for target subsystem.

  target: Don't BUG_ON during NodeACL dynamic -> explicit conversion
  https://patchwork.kernel.org/patch/9560085/

  target: Use correct SCSI status during EXTENDED_COPY exception
  https://patchwork.kernel.org/patch/9560083/

  target: Fix early transport_generic_handle_tmr abort scenario
  https://patchwork.kernel.org/patch/9560077/

  target: Fix multi-session dynamic se_node_acl double free OOPs
  https://patchwork.kernel.org/patch/9560081/

  target: Fix COMPARE_AND_WRITE ref leak for non GOOD status
  https://patchwork.kernel.org/patch/9560065/

  target: Fix NULL dereference during LUN lookup + active I/O shutdown
  https://patchwork.kernel.org/patch/9587799/

  target: Avoid mappedlun symlink creation during lun shutdown
  https://lkml.org/lkml/2017/3/30/180

   
  Contact Information = Bryant G. Ly/b...@us.ibm.com

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1677685/+subscriptions

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

[Kernel-packages] [Bug 1689359] Re: Target: Fix VERIFY_16, WRITE_VERIFY, VERIFY, and WRITE_VERIFY_16

[bugproxy]

--- Comment From b...@us.ibm.com 2017-05-10 16:16 EDT---
Works fine

** Tags added: verification-done-xenial verification-done-yakkety
verification-done-zesty

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

Title:
  Target: Fix VERIFY_16, WRITE_VERIFY, VERIFY, and WRITE_VERIFY_16

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

Bug description:
  ---Problem Description---
  List of patches that is in regards to scsi commands.

  VERIFY_16 does not handle the returned CHECK_CONDITION properly
  resulting an in infinite loop.

  Fix VERIFY and WRITE VERIFY command parsing

  Use the value of the BYTCHK field to determine the size of the
  Data-Out buffer. For VERIFY, honor the VRPROTECT, DPO and FUA
  fields. This patch avoids that LIO complains about a mismatch
  between the expected transfer length and the SCSI CDB length
  if the value of the BYTCHK field is 0.

  WRITE_VERIFY_16 - Large volume groups such as AIX need this command. 
   
  ---uname output---
  Latest Yakkety master branch
   
  Machine Type = P8 
   
  The target is for 16.04.02 Yakkety. Below are the links to the patches that 
need to be backported.

  target: Fix VERIFY_16 handling in sbc_parse_cdb
  https://patchwork.kernel.org/patch/9643687/

  target: Fix VERIFY and WRITE VERIFY command parsing
  https://patchwork.kernel.org/patch/9617875/

  target: Add WRITE_VERIFY_16
  https://patchwork.kernel.org/patch/9686085/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1689359/+subscriptions

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

[Kernel-packages] [Bug 1689365] ibmvscsis: Fix the incorrect req_lim_delta

[bugproxy]

--- Comment on attachment From b...@us.ibm.com 2017-05-10 16:17 EDT---


This patch is also an addition to both:
commit 25e78531268e ("ibmvscsis: Do not send aborted task response")
commit 38b2788edbd6 ("ibmvscsis: Clear left-over abort_cmd pointers")

** Attachment added: "ibmvscsis: Fix the incorrect req_lim_delta"
   
https://bugs.launchpad.net/bugs/1689365/+attachment/4874835/+files/0001-ibmvscsis-Fix-the-incorrect-req_lim_delta.patch

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

Title:
  ibmvscsis: Do not send aborted task response

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

Bug description:
  ---Problem Description---
  ibmvscsis: Do not send aborted task response

  The driver is sending a response to the actual scsi op that was
  aborted by an abort task TM, while LIO is sending a response to
  the abort task TM.

  ibmvscsis_tgt does not send the response to the client until
  release_cmd time. The reason for this was because if we did it
  at queue_status time, then the client would be free to reuse the
  tag for that command, but we're still using the tag until the
  command is released at release_cmd time, so we chose to delay
  sending the response until then. That then caused this issue, because
  release_cmd is always called, even if queue_status is not.

  SCSI spec says that the initiator that sends the abort task
  TM NEVER gets a response to the aborted op and with the current
  code it will send a response. Thus this fix will remove that response
  if the CMD_T_ABORTED && !CMD_T_TAS.

  Another case with a small timing window is the case where if LIO sends a
  TMR_DOES_NOT_EXIST, and the release_cmd callback is called for the TMR Abort
  cmd before the release_cmd for the (attemped) aborted cmd, then we need to
  ensure that we send the response for the (attempted) abort cmd to the client
  before we send the response for the TMR Abort cmd.

  [PATCH v3] ibmvscsis: Do not send aborted task response
  https://www.spinics.net/lists/stable/msg170418.html

  This patch also requires a patch that was accepted upstream which is:

  target: Fix unknown fabric callback queue-full errors
  https://patchwork.kernel.org/patch/9405013/
   
  ---uname output---
  Latest Yakkety master branch
   
  Machine Type = P8 

  ---Steps to Reproduce---
   Send abort ops over and over and you will hit it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1689365/+subscriptions

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

[Kernel-packages] [Bug 1689818] Re: tty: pl011: fix earlycon work-around for QDF2400 erratum 44

[Manoj Iyer]

Tested on QDF2400 system. The console used here is an SOL connection to
the server.

== With earlycon=qdf2400_e44,0xff78ef1000 (SOL) ==

Loading Linux 4.10.0-20-generic ...
Loading initial ramdisk ...
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services and installing virtual address map...
[0.00] Booting Linux on physical CPU 0x0
[0.00] Linux version 4.10.0-20-generic (manjo@tangerine) (gcc version 
5.3.1 20160413 (Ubuntu/Linaro 5.3.1-14ubuntu2) ) #22~lp1689818+sru3.4 SMP Wed 
May 10 19:28:25 UTC 2017 (Ubuntu 4.10.0-20.22~lp1689818+sru3.4-generic 4.10.8)
[0.00] Boot CPU: AArch64 Processor [510f8000]
[0.00] earlycon: qdf2400_e44 at MMIO 0x00ff78ef1000 (options '')
[0.00] bootconsole [qdf2400_e44] enabled
[0.00] efi: Getting EFI parameters from FDT:
[0.00] efi: EFI v2.60 by Qualcomm
[0.00] efi:  ACPI 2.0=0x95e  PROP=0xe823580  SMBIOS 3.0=0x575  
ESRT=0xac7c198  MEMATTR=0xac58018  RNG=0xe7ce798
[0.00] esrt: Reserving ESRT space from 0x0ac7c198 to 
0x0ac7c270.
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0x095E 24 (v02 QCOM  )
[0.00] ACPI: XSDT 0x095D 84 (v01 QCOM   QDF2400  
 QCOM 0001)
[0.00] ACPI: FACP 0x093D 000114 (v06 QCOM   QDF2400  
 INTL 20150515)
[0.00] ACPI: DSDT 0x093E 0344BE (v02 QCOM   QDF2400  
0004 INTL 20150515)
[0.00] ACPI: DBG2 0x0947 72 (v00 QCOM   QDF2400  
0001 INTL 20150515)
[0.00] ACPI: IORT 0x0945 000A40 (v00 QCOM   QDF2400  
0001 INTL 20150515)
[0.00] ACPI: TPM2 0x0944 40 (v04 QCOM   QDF2400  
0001 INTL 20150515)
[0.00] ACPI: BERT 0x0942 30 (v01 QCOM   QDF2400  
0001 INTL 20150515)
[0.00] ACPI: GTDT 0x093C 7C (v02 QCOM   QDF2400  
0001 INTL 20150515)
[0.00] ACPI: PCCT 0x093A AC (v01 QCOM   QDF2400  
0001 INTL 20150515)
[0.00] ACPI: SPMI 0x0939 41 (v04 QCOM   QDF2400  
 INTL 20150515)
[0.00] ACPI: APIC 0x0943 000F70 (v04 QCOM   QDF2400  
0001 INTL 20150515)
[0.00] ACPI: HEST 0x0946 000288 (v01 QCOM   QDF2400  
0001 INTL 20150515)
[0.00] ACPI: MCFG 0x093B 5C (v01 QCOM   QDF2400  
0001 QCOM 0001)
[0.00] ACPI: SPCR 0x042D 50 (v04 QCOM   QDF2400  
0001 QCOM 0001)
[0.00] ACPI: SPCR: console: qdf2400_e44,mmio,0xff78ef1000,115200
[0.00] ACPI: NUMA: Failed to initialise from firmware
[0.00] NUMA: Faking a node at [mem 
0x-0x0017]
[0.00] NUMA: Adding memblock [0x20 - 0x20] on node 0
[0.00] NUMA: Adding memblock [0x82 - 0x307] on node 0
[0.00] NUMA: Adding memblock [0x308 - 0x308] on node 0
[0.00] NUMA: Adding memblock [0x309 - 0x31f] on node 0
[0.00] NUMA: Adding memblock [0x320 - 0x33f] on node 0
[0.00] NUMA: Adding memblock [0x341 - 0x42c] on node 0
[0.00] NUMA: Adding memblock [0x42d - 0x42d] on node 0
[0.00] NUMA: Adding memblock [0x42e - 0x573] on node 0
[0.00] NUMA: Adding memblock [0x574 - 0x57f] on node 0
[0.00] NUMA: Adding memblock [0x580 - 0x5806fff] on node 0
[0.00] NUMA: Adding memblock [0x5807000 - 0x580afff] on node 0
[0.00] NUMA: Adding memblock [0x580b000 - 0x588] on node 0
[0.00] NUMA: Adding memblock [0x589 - 0x592] on node 0
[0.00] NUMA: Adding memblock [0x593 - 0x5b2bfff] on node 0
[0.00] NUMA: Adding memblock [0x5b2c000 - 0x8b3dfff] on node 0
[0.00] NUMA: Adding memblock [0x8b3e000 - 0x8be] on node 0
[0.00] NUMA: Adding memblock [0x8bf - 0x8dc] on node 0
[0.00] NUMA: Adding memblock [0x8dd - 0x8dd] on node 0
[0.00] NUMA: Adding memblock [0x8de - 0x919] on node 0
[0.00] NUMA: Adding memblock [0x91a - 0x91a0fff] on node 0
[0.00] NUMA: Adding memblock [0x91a1000 - 0x91a3fff] on node 0
[0.00] NUMA: Adding memblock [0x91a4000 - 0x91c] on node 0
[0.00] NUMA: Adding memblock [0x91d - 0x930] on node 0
[0.00] NUMA: Adding memblock [0x931 - 0x938] on node 0
[0.00] NUMA: Adding memblock [0x939 - 0x947] on node 0
[0.00] NUMA: Adding memblock [0x948 - 0x948cfff] on node 0
[0.00] NUMA: Adding memblock [0x948d000 - 0x97c] on node 0
[0.00] NUMA: Adding memblock [0x97d - 0x97d0fff] on node 0
[0.00] NUMA: Adding memblock [0x97d1000 - 0x97dbfff] on node 0
[0.00] NUMA: Adding memblock [0x97dc000 - 0xe7b] on node 0
[0.00] NUMA: Ad

[Kernel-packages] [Bug 1689918] [NEW] BUG: unable to handle kernel NULL pointer dereference at 0000000000000018

[Benjamin]

Public bug reported:

I ran K3B with a DVD-RW inserted while extracting an archive.

My desktop froze and I found this in dmesg:

[ 3293.518501] sr 4:0:0:0: [sr0] tag#5 CDB: Read(10) 28 00 00 23 04 00 00 00 02 
00
[ 3293.518502] blk_update_request: I/O error, dev sr0, sector 9179136
[ 3293.518506] Buffer I/O error on dev sr0, logical block 1147392, async page 
read
[ 3293.606203] sr 4:0:0:0: [sr0] tag#7 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[ 3293.606208] sr 4:0:0:0: [sr0] tag#7 Sense Key : Illegal Request [current] 
[ 3293.606212] sr 4:0:0:0: [sr0] tag#7 Add. Sense: Logical block address out of 
range
[ 3293.606216] sr 4:0:0:0: [sr0] tag#7 CDB: Read(10) 28 00 00 23 05 3a 00 00 02 
00
[ 3293.606219] blk_update_request: I/O error, dev sr0, sector 9180392
[ 3293.617985] sr 4:0:0:0: [sr0] tag#8 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[ 3293.617990] sr 4:0:0:0: [sr0] tag#8 Sense Key : Illegal Request [current] 
[ 3293.617994] sr 4:0:0:0: [sr0] tag#8 Add. Sense: Logical block address out of 
range
[ 3293.617998] sr 4:0:0:0: [sr0] tag#8 CDB: Read(10) 28 00 00 23 05 3a 00 00 02 
00
[ 3293.618001] blk_update_request: I/O error, dev sr0, sector 9180392
[ 3293.618009] Buffer I/O error on dev sr0, logical block 1147549, async page 
read
[ 3302.607388] isofs_fill_super: root inode is not a directory. Corrupted media?
[ 3328.320211] BUG: unable to handle kernel NULL pointer dereference at 
0018
[ 3328.320257] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
[ 3328.320274] PGD 0 

[ 3328.320287] Oops: 0002 [#1] SMP
[ 3328.320296] Modules linked in: isofs bnep pci_stub vboxpci(OE) 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_multiport iptable_filter 
binfmt_misc intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic aesni_intel 
crypto_simd intel_cstate glue_helper cryptd intel_rapl_perf aes_x86_64 
nls_iso8859_1 dm_crypt snd_hda_intel snd_hda_codec snd_hda_core snd_usb_audio 
snd_usbmidi_lib snd_hwdep input_leds snd_seq_midi snd_seq_midi_event 
snd_rawmidi uvcvideo videobuf2_vmalloc snd_seq videobuf2_memops videobuf2_v4l2 
videobuf2_core snd_pcm snd_seq_device videodev media joydev snd_timer snd 
soundcore serio_raw mei_me shpchp mei intel_pch_thermal hci_uart mac_hid btbcm
[ 3328.320453]  btqca btintel acpi_als bluetooth intel_lpss_acpi intel_lpss 
kfifo_buf acpi_pad industrialio parport_pc ppdev lp parport ip_tables x_tables 
autofs4 btrfs xor raid6_pq hid_generic usbhid mxm_wmi i915 i2c_algo_bit 
drm_kms_helper e1000e syscopyarea sysfillrect sysimgblt ptp fb_sys_fops 
pps_core drm ahci libahci wmi video pinctrl_sunrisepoint pinctrl_intel i2c_hid 
hid fjes
[ 3328.320533] CPU: 1 PID: 1371 Comm: Xorg Tainted: G   OE   
4.10.0-20-generic #22-Ubuntu
[ 3328.320553] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./B150M Pro4S/D3, BIOS P7.00 12/06/2016
[ 3328.320575] task: 9c01613d2b00 task.stack: b72801ca4000
[ 3328.320600] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 
[i915]
[ 3328.320617] RSP: :b72801ca7898 EFLAGS: 00010246
[ 3328.320629] RAX: 9c00b2bf2040 RBX: 0003 RCX: 0003
[ 3328.320645] RDX:  RSI: 9c015bc82000 RDI: 9c015d3b
[ 3328.320670] RBP: b72801ca78f0 R08:  R09: 
[ 3328.320692] R10:  R11: 9c016dfd5dc0 R12: 9c00c9aee000
[ 3328.320709] R13: 9c00eb435110 R14: fffd5000 R15: 1000
[ 3328.320726] FS:  7f34ee1eba40() GS:9c016dd0() 
knlGS:
[ 3328.320744] CS:  0010 DS:  ES:  CR0: 80050033
[ 3328.320757] CR2: 0018 CR3: 0001dcce6000 CR4: 002406e0
[ 3328.320774] Call Trace:
[ 3328.320792]  gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915]
[ 3328.320807]  ? swiotlb_map_sg_attrs+0x49/0x110
[ 3328.320827]  gen8_alloc_va_range+0x23d/0x470 [i915]
[ 3328.320849]  i915_vma_bind+0x7e/0x170 [i915]
[ 3328.320870]  __i915_vma_do_pin+0x2a5/0x450 [i915]
[ 3328.320891]  i915_gem_execbuffer_reserve_vma.isra.31+0x144/0x1b0 [i915]
[ 3328.320915]  i915_gem_execbuffer_reserve.isra.32+0x39e/0x3d0 [i915]
[ 3328.320938]  i915_gem_do_execbuffer.isra.38+0x4a2/0x1750 [i915]
[ 3328.320954]  ? kmem_cache_alloc_trace+0x142/0x190
[ 3328.320973]  ? drm_gem_handle_create_tail+0xaf/0x190 [drm]
[ 3328.320995]  i915_gem_execbuffer2+0xa1/0x1e0 [i915]
[ 3328.321010]  drm_ioctl+0x21b/0x4c0 [drm]
[ 3328.321030]  ? i915_gem_execbuffer+0x310/0x310 [i915]
[ 3328.321043]  do_vfs_ioctl+0xa3/0x610
[ 3328.321053]  ? do_munmap+0x338/0x460
[ 3328.321063]  SyS_ioctl+0x79/0x90
[ 3328.321072]  entry_SYSCALL_64_fastpath+0x1e/0xad
[ 3328.321084] RIP: 0033:0x7f34ebbff987
[ 3328.321093] RSP: 002b:7ffec8a5dba8 EFLAGS: 3246 ORIG_RAX: 
0010
[ 3328.32] RAX: ffda RBX: 7f34e7af80

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

[Brad Figg]

This change was made by a bot.

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

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

Title:
  BUG: unable to handle kernel NULL pointer dereference at
  0018

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I ran K3B with a DVD-RW inserted while extracting an archive.

  My desktop froze and I found this in dmesg:

  [ 3293.518501] sr 4:0:0:0: [sr0] tag#5 CDB: Read(10) 28 00 00 23 04 00 00 00 
02 00
  [ 3293.518502] blk_update_request: I/O error, dev sr0, sector 9179136
  [ 3293.518506] Buffer I/O error on dev sr0, logical block 1147392, async page 
read
  [ 3293.606203] sr 4:0:0:0: [sr0] tag#7 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
  [ 3293.606208] sr 4:0:0:0: [sr0] tag#7 Sense Key : Illegal Request [current] 
  [ 3293.606212] sr 4:0:0:0: [sr0] tag#7 Add. Sense: Logical block address out 
of range
  [ 3293.606216] sr 4:0:0:0: [sr0] tag#7 CDB: Read(10) 28 00 00 23 05 3a 00 00 
02 00
  [ 3293.606219] blk_update_request: I/O error, dev sr0, sector 9180392
  [ 3293.617985] sr 4:0:0:0: [sr0] tag#8 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
  [ 3293.617990] sr 4:0:0:0: [sr0] tag#8 Sense Key : Illegal Request [current] 
  [ 3293.617994] sr 4:0:0:0: [sr0] tag#8 Add. Sense: Logical block address out 
of range
  [ 3293.617998] sr 4:0:0:0: [sr0] tag#8 CDB: Read(10) 28 00 00 23 05 3a 00 00 
02 00
  [ 3293.618001] blk_update_request: I/O error, dev sr0, sector 9180392
  [ 3293.618009] Buffer I/O error on dev sr0, logical block 1147549, async page 
read
  [ 3302.607388] isofs_fill_super: root inode is not a directory. Corrupted 
media?
  [ 3328.320211] BUG: unable to handle kernel NULL pointer dereference at 
0018
  [ 3328.320257] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 
[i915]
  [ 3328.320274] PGD 0 

  [ 3328.320287] Oops: 0002 [#1] SMP
  [ 3328.320296] Modules linked in: isofs bnep pci_stub vboxpci(OE) 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_multiport iptable_filter 
binfmt_misc intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic aesni_intel 
crypto_simd intel_cstate glue_helper cryptd intel_rapl_perf aes_x86_64 
nls_iso8859_1 dm_crypt snd_hda_intel snd_hda_codec snd_hda_core snd_usb_audio 
snd_usbmidi_lib snd_hwdep input_leds snd_seq_midi snd_seq_midi_event 
snd_rawmidi uvcvideo videobuf2_vmalloc snd_seq videobuf2_memops videobuf2_v4l2 
videobuf2_core snd_pcm snd_seq_device videodev media joydev snd_timer snd 
soundcore serio_raw mei_me shpchp mei intel_pch_thermal hci_uart mac_hid btbcm
  [ 3328.320453]  btqca btintel acpi_als bluetooth intel_lpss_acpi intel_lpss 
kfifo_buf acpi_pad industrialio parport_pc ppdev lp parport ip_tables x_tables 
autofs4 btrfs xor raid6_pq hid_generic usbhid mxm_wmi i915 i2c_algo_bit 
drm_kms_helper e1000e syscopyarea sysfillrect sysimgblt ptp fb_sys_fops 
pps_core drm ahci libahci wmi video pinctrl_sunrisepoint pinctrl_intel i2c_hid 
hid fjes
  [ 3328.320533] CPU: 1 PID: 1371 Comm: Xorg Tainted: G   OE   
4.10.0-20-generic #22-Ubuntu
  [ 3328.320553] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./B150M Pro4S/D3, BIOS P7.00 12/06/2016
  [ 3328.320575] task: 9c01613d2b00 task.stack: b72801ca4000
  [ 3328.320600] RIP: 
0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  [ 3328.320617] RSP: :b72801ca7898 EFLAGS: 00010246
  [ 3328.320629] RAX: 9c00b2bf2040 RBX: 0003 RCX: 
0003
  [ 3328.320645] RDX:  RSI: 9c015bc82000 RDI: 
9c015d3b
  [ 3328.320670] RBP: b72801ca78f0 R08:  R09: 

  [ 3328.320692] R10:  R11: 9c016dfd5dc0 R12: 
9c00c9aee000
  [ 3328.320709] R13: 9c00eb435110 R14: fffd5000 R15: 
1000
  [ 3328.320726] FS:  7f34ee1eba40() GS:9c016dd0() 
knlGS:
  [ 3328.320744] CS:  0010 DS:  ES:  CR0: 80050033
  [ 3328.320757] CR2: 0018 CR3: 0001dcce6000 CR4: 
002406e0
  [ 3328.320774] Call Trace:
  [ 3328.320792]  gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915]
  [ 3328.320807]  ? swiotlb_map_sg_attrs+0x49/0x110
  [ 3328.320827]  gen8_alloc_va_range+0x23d/0x470 [i915]
  [ 3328.320849]  i915_vma_bind+0x7e/0x170 [i915]
  [ 3328.320870]  __i915_vma_do_pin+0x2a5/0x450 [i915]
  [ 3328.320891]  i915_gem_execbuffer_reserve_vma.isra.31+0x144/0x1b0 [i915]
  [ 3328.320915]  i915_gem_execbuffer_reserve.isra.32+0x39e/0x3d0 [i915]
  [ 3328.320938]  i915_gem_do_execbuffer.isra.38+0x4a2/0x1750 [i915]
  [ 3328.320954]  ? kmem_cache_alloc_trace+0x142/0x190
  [ 3328.320973]  ? drm_gem_handle_create_tail+0xaf/0x190 [drm]
  [ 3328.320995]

[Kernel-packages] [Bug 1682999] Re: Ubuntu crashes on Intel j4205 Apollo Lake

[Wojciech Pietruszewski]

Sorry for no feedback. I've been running Windows 10 to exclude the
possibility of hardware issues. It's been running for over 2 weeks with
no issue. Today I installed kernel 4.11
(vmlinuz-4.11.0-041100rc7-lowlatency). I will continue testing the board
and update when I get anything.

One thing I noticed on 4.10 is error in dmesg

May 07 19:25:20 server kernel: smpboot: CPU0: Intel(R) Pentium(R) CPU J4205 @ 
1.50GHz (family: 0x6, model: 0x5c, stepping: 0x9)
May 07 19:25:20 server kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 
Bank 4: e6020408
May 07 19:25:20 server kernel: mce: [Hardware Error]: TSC 0 ADDR fef13b80 
May 07 19:25:20 server kernel: mce: [Hardware Error]: PROCESSOR 0:506c9 TIME 
1494177867 SOCKET 0 APIC 0 microcode 1e
May 07 19:25:20 server kernel: Performance Events: PEBS fmt3+, Goldmont events, 
32-deep LBR, full-width counters, Intel PMU driver.

It doesn't show each time I boot the server.

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

Title:
  Ubuntu crashes on Intel j4205 Apollo Lake

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using Ubuntu 17.04 on ASRock j4205-ITX with BIOS v1.20. ASRock
  states that this platform is supported by Ubuntu 16.10 but after
  installation it kept freezing after few minuts. There was no trace of
  error in dmesg nor in any log. Not even a crashdump. After
  installation of Ubuntu 17.04 I was able to see an error:

  Apr 14 20:40:12 server kernel: BUG: unable to handle kernel paging request at 
af7b244c32d0
  Apr 14 20:40:12 server kernel: IP: xfsaild+0x12f/0x750 [xfs]
  Apr 14 20:40:12 server kernel: PGD 0 
  Apr 14 20:40:13 server kernel: 
  Apr 14 20:40:13 server kernel: Oops:  [#1] SMP
  Apr 14 20:40:13 server kernel: Modules linked in: intel_rapl 
intel_telemetry_pltdrv intel_pmc_ipc intel_punit_ipc intel_telemetry_core 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
intel_rapl_perf mei_me mei shpchp
  Apr 14 20:40:13 server kernel:  glue_helper ahci i2c_hid cryptd mii libahci 
drm hid video fjes pinctrl_broxton pinctrl_intel
  Apr 14 20:40:13 server kernel: CPU: 1 PID: 402 Comm: xfsaild/md1 Not tainted 
4.10.0-19-generic #21-Ubuntu
  Apr 14 20:40:13 server kernel: Hardware name: To Be Filled By O.E.M. To Be 
Filled By O.E.M./J4205-ITX, BIOS P1.20 12/16/2016
  Apr 14 20:40:13 server kernel: task: 8f7b24718000 task.stack: 
ba8581edc000
  Apr 14 20:40:13 server kernel: RIP: 0010:xfsaild+0x12f/0x750 [xfs]
  Apr 14 20:40:13 server kernel: RSP: 0018:ba8581edfe50 EFLAGS: 00010246
  Apr 14 20:40:13 server kernel: RAX:  RBX: 8f7b24718000 
RCX: 
  Apr 14 20:40:13 server kernel: RDX: 8000 RSI: 0246 
RDI: 0246
  Apr 14 20:40:13 server kernel: RBP: ba8581edfef8 R08:  
R09: 
  Apr 14 20:40:13 server kernel: R10: 08eb R11: 0920 
R12: b1499b24
  Apr 14 20:40:13 server kernel: R13: af7b244c3280 R14: 8f7b280bf5a0 
R15: 8f7b24309000
  Apr 14 20:40:13 server kernel: FS:  () 
GS:8f7b3fc8() knlGS:
  Apr 14 20:40:13 server kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Apr 14 20:40:13 server kernel: CR2: af7b244c32d0 CR3: 000237c09000 
CR4: 003406e0
  Apr 14 20:40:13 server kernel: Call Trace:
  Apr 14 20:40:13 server kernel:  kthread+0x101/0x140
  Apr 14 20:40:13 server kernel:  ? xfs_trans_ail_cursor_first+0x90/0x90 [xfs]
  Apr 14 20:40:13 server kernel:  ? kthread_create_on_node+0x60/0x60
  Apr 14 20:40:13 server kernel:  ret_from_fork+0x2c/0x40
  Apr 14 20:40:13 server kernel: Code: f0 49 c7 c4 24 9b 49 b1 85 c0 0f 85 05 
05 00 00 48 c7 43 08 00 00 00 00 e8 1f 96 3e f0 8b 05 ed 40 db f0 85 c0 0f 85 
1b 05 00 00 <41> 8b 45 50 4d 8b 75 00 85 c0 74 60 49 83 7d 48 00 75 59 49 8d 
  Apr 14 20:40:13 server kernel: RIP: xfsaild+0x12f/0x750 [xfs] RSP: 
ba8581edfe50
  Apr 14 20:40:13 server kernel: CR2: af7b244c32d0
  Apr 14 20:40:13 server kernel: ---[ end trace a03641228bdafba1 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 14 21:31 seq
   crw-rw 1 root audio 116, 33 Apr 14 21:31 timer
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.10.0-19-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu4
  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: Sat Apr 15 09:16:45 2017
  Hibernati

[Kernel-packages] [Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

[Vasile Gorcinschi]

I have the same issue when shutting down from Ubuntu 16.04 LTS. Machine:
Dell Precision 3520

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

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

Status in linux package in Ubuntu:
  Triaged

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

  Important part of log:

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

[Kernel-packages] [Bug 1683976] Re: Please backport fix to reference leak in cgroup blkio throttle

[Chunwei Chen]

Verified on 3.13.0-119-generic

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

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

Title:
  Please backport fix to reference leak in cgroup blkio throttle

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

Bug description:
  This is fixed in Linux 4.5
  
https://github.com/torvalds/linux/commit/39a169b62b415390398291080dafe63aec751e0a

  Basically the module reference will leak whenever you write to
  /sys/fs/cgroup/blkio/blkio.throttle.*

  $ uname -a
  Linux david-kvm 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  $ lsmod | grep ^zfs
  zfs  2813952  1
  $ sudo sh -c 'i=100; while [ $i -gt 0 ]; do echo "230:0 1024" > 
/sys/fs/cgroup/blkio/blkio.throttle.read_bps_device; i=$(($i - 1)); done'
  $ lsmod | grep ^zfs
  zfs  2813952  101

  This patch should be applied to all kernel < 4.5

  Thanks

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

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

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

[bugproxy]

--- Comment From b...@us.ibm.com 2017-05-10 14:58 EDT---
Which has also been accepted by maintainer - 
https://www.spinics.net/lists/linux-scsi/msg108639.html

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

Title:
  ibmvscsis: Do not send aborted task response

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

Bug description:
  ---Problem Description---
  ibmvscsis: Do not send aborted task response

  The driver is sending a response to the actual scsi op that was
  aborted by an abort task TM, while LIO is sending a response to
  the abort task TM.

  ibmvscsis_tgt does not send the response to the client until
  release_cmd time. The reason for this was because if we did it
  at queue_status time, then the client would be free to reuse the
  tag for that command, but we're still using the tag until the
  command is released at release_cmd time, so we chose to delay
  sending the response until then. That then caused this issue, because
  release_cmd is always called, even if queue_status is not.

  SCSI spec says that the initiator that sends the abort task
  TM NEVER gets a response to the aborted op and with the current
  code it will send a response. Thus this fix will remove that response
  if the CMD_T_ABORTED && !CMD_T_TAS.

  Another case with a small timing window is the case where if LIO sends a
  TMR_DOES_NOT_EXIST, and the release_cmd callback is called for the TMR Abort
  cmd before the release_cmd for the (attemped) aborted cmd, then we need to
  ensure that we send the response for the (attempted) abort cmd to the client
  before we send the response for the TMR Abort cmd.

  [PATCH v3] ibmvscsis: Do not send aborted task response
  https://www.spinics.net/lists/stable/msg170418.html

  This patch also requires a patch that was accepted upstream which is:

  target: Fix unknown fabric callback queue-full errors
  https://patchwork.kernel.org/patch/9405013/
   
  ---uname output---
  Latest Yakkety master branch
   
  Machine Type = P8 

  ---Steps to Reproduce---
   Send abort ops over and over and you will hit it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1689365/+subscriptions

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

[Kernel-packages] [Bug 1689365] ibmvscsis: Clear left-over abort_cmd pointers

[bugproxy]

--- Comment on attachment From b...@us.ibm.com 2017-05-10 14:57 EDT---


This is an additional needed fix to the original commit 25e78531268e 
("ibmvscsis: Do not send aborted task response") that was previously posted 
here.

** Attachment added: "ibmvscsis: Clear left-over abort_cmd pointers"
   
https://bugs.launchpad.net/bugs/1689365/+attachment/4874794/+files/0001-ibmvscsis-Clear-left-over-abort_cmd-pointers.patch

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

Title:
  ibmvscsis: Do not send aborted task response

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

Bug description:
  ---Problem Description---
  ibmvscsis: Do not send aborted task response

  The driver is sending a response to the actual scsi op that was
  aborted by an abort task TM, while LIO is sending a response to
  the abort task TM.

  ibmvscsis_tgt does not send the response to the client until
  release_cmd time. The reason for this was because if we did it
  at queue_status time, then the client would be free to reuse the
  tag for that command, but we're still using the tag until the
  command is released at release_cmd time, so we chose to delay
  sending the response until then. That then caused this issue, because
  release_cmd is always called, even if queue_status is not.

  SCSI spec says that the initiator that sends the abort task
  TM NEVER gets a response to the aborted op and with the current
  code it will send a response. Thus this fix will remove that response
  if the CMD_T_ABORTED && !CMD_T_TAS.

  Another case with a small timing window is the case where if LIO sends a
  TMR_DOES_NOT_EXIST, and the release_cmd callback is called for the TMR Abort
  cmd before the release_cmd for the (attemped) aborted cmd, then we need to
  ensure that we send the response for the (attempted) abort cmd to the client
  before we send the response for the TMR Abort cmd.

  [PATCH v3] ibmvscsis: Do not send aborted task response
  https://www.spinics.net/lists/stable/msg170418.html

  This patch also requires a patch that was accepted upstream which is:

  target: Fix unknown fabric callback queue-full errors
  https://patchwork.kernel.org/patch/9405013/
   
  ---uname output---
  Latest Yakkety master branch
   
  Machine Type = P8 

  ---Steps to Reproduce---
   Send abort ops over and over and you will hit it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1689365/+subscriptions

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

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

[Brad Figg]

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

apport-collect 1689886

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  QDF2400 kernel oops on ipmitool fru write 0 fru.bin

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  $ sudo ipmitool fru print 0
   Chassis Type : Rack Mount Chassis
   Chassis Part Number : 
   Chassis Serial : 
   Board Mfg Date : Wed Jan 4 14:18:00 2017
   Board Mfg : WIWYNN
   Board Product : REP Board
   Board Serial : 12345
   Board Part Number : 
   Product Manufacturer : WIWYNN
   Product Name : REP
   Product Part Number : ..
   Product Version : EVT
   Product Serial : 
   Product Asset Tag :
  ubuntu@ubuntu:~/FRU$

  ubuntu@ubuntu:~/FRU$ sudo ipmitool fru write 0 fru.bin
  Fru Size : 1024 bytes
  Size to Write : 256 bytes
  [ 1815.412463] Unable to handle kernel NULL pointer dereference at virtual 
address 0025
  [ 1815.419668] pgd = 219ca2168000
  [ 1815.422986] [0025] *pgd=0003ee08d003, *pud=0003ee08e003, 
*pmd=
  [ 1815.431225] Internal error: Oops: 9604 [#1] SMP
  [ 1815.436086] Modules linked in: ipmi_devintf nls_utf8 nls_cp437 vfat fat 
aes_ce_blk ablk_helper cryptd aes_ce_cipher ghash_ce sha2_ce efi_pstore sha1_ce 
sg efivars ipmi_ssif ipmi_msghandler cppc_cpufreq i2c_qup i2c_core efivarfs 
autofs4 ext4 crc16 jbd2 mbcache sd_mod ahci_platform libahci_platform libahci 
xhci_plat_hcd libata xhci_hcd scsi_mod usbcore msm_emac sdhci_acpi sdhci 
usb_common pinctrl_qdf2xxx
  [ 1815.471677] CPU: 7 PID: 1950 Comm: kssif0042 Not tainted 4.7.0-2-generic 
#5~pdaw1.0+bandera.9-Ubuntu
  [ 1815.480789] Hardware name: Default string Default string/Default string, 
BIOS 5.12 12/12/2012
  [ 1815.489296] task: edf1aa074380 ti: edf1a782 task.ti: 
edf1a782
  [ 1815.496772] PC is at ipmi_ssif_thread+0x84/0x128 [ipmi_ssif]
  [ 1815.502407] LR is at ipmi_ssif_thread+0x6c/0x128 [ipmi_ssif]
  [ 1815.508046] pc : [] lr : [] pstate: 
00400145
  [ 1815.515424] sp : edf1a7823de0
  [ 1815.518723] x29: edf1a7823de0 x28: 
  [ 1815.524018] x27:  x26: 
  [ 1815.529313] x25:  x24: 
  [ 1815.534608] x23: edeeb9dbba08 x22: 219c9d0a3000
  [ 1815.539903] x21: 219c9d0a2420 x20: edeeb9dbba00
  [ 1815.545198] x19: edeeb9dbb800 x18: 0014
  [ 1815.550494] x17:  x16: 
  [ 1815.555789] x15:  x14: 
  [ 1815.561084] x13:  x12: 071c71c71c71c71c
  [ 1815.566379] x11: 00ba x10: 0960
  [ 1815.571674] x9 : 0040 x8 : edf1ad28
  [ 1815.576969] x7 :  x6 : edf1aa9f9600
  [ 1815.582264] x5 : edf1ad00 x4 : 
  [ 1815.587560] x3 : 0026 x2 : 0025
  [ 1815.592855] x1 : 0007 x0 : edf1aa2e4c00
  [ 1815.598150]
  [ 1815.599626] Process kssif0042 (pid: 1950, stack limit = 0xedf1a7820020)
  [ 1815.606571] Stack: (0xedf1a7823de0 to 0xedf1a7824000)
  [ 1815.612301] 3de0: edf1a7823e20 219ca122cb1c edf1ab9d5800 
219ca20cdfa8
  [ 1815.620113] 3e00: 219ca1aa2ee8 edeeb9dbb800 219c9d09f590 
edeeb9dbb800
  [ 1815.627925] 3e20:  219ca11c4f10 219ca122ca30 
edf1ab9d5800
  [ 1815.635737] 3e40:    

  [ 1815.643550] 3e60:  219ca12399a8 edeeb9dbb800 
edf1
  [ 1815.651363] 3e80:  edf1a7823e88 edf1a7823e88 

  [ 1815.659175] 3ea0:  edf1a7823ea8 edf1a7823ea8 
cb88537fdc8ba500
  [ 1815.666987] 3ec0:    

  [ 1815.674800] 3ee0:    

  [ 1815.682612] 3f00:    

  [ 1815.690425] 3f20:    

  [ 1815.698237] 3f40:    

  [ 1815.706050] 3f60:    

  [ 1815.713862] 3f80:   000

[Kernel-packages] [Bug 1689886] [NEW] QDF2400 kernel oops on ipmitool fru write 0 fru.bin

[Manoj Iyer]

Public bug reported:

[Impact]
$ sudo ipmitool fru print 0
 Chassis Type : Rack Mount Chassis
 Chassis Part Number : 
 Chassis Serial : 
 Board Mfg Date : Wed Jan 4 14:18:00 2017
 Board Mfg : WIWYNN
 Board Product : REP Board
 Board Serial : 12345
 Board Part Number : 
 Product Manufacturer : WIWYNN
 Product Name : REP
 Product Part Number : ..
 Product Version : EVT
 Product Serial : 
 Product Asset Tag :
ubuntu@ubuntu:~/FRU$

ubuntu@ubuntu:~/FRU$ sudo ipmitool fru write 0 fru.bin
Fru Size : 1024 bytes
Size to Write : 256 bytes
[ 1815.412463] Unable to handle kernel NULL pointer dereference at virtual 
address 0025
[ 1815.419668] pgd = 219ca2168000
[ 1815.422986] [0025] *pgd=0003ee08d003, *pud=0003ee08e003, 
*pmd=
[ 1815.431225] Internal error: Oops: 9604 [#1] SMP
[ 1815.436086] Modules linked in: ipmi_devintf nls_utf8 nls_cp437 vfat fat 
aes_ce_blk ablk_helper cryptd aes_ce_cipher ghash_ce sha2_ce efi_pstore sha1_ce 
sg efivars ipmi_ssif ipmi_msghandler cppc_cpufreq i2c_qup i2c_core efivarfs 
autofs4 ext4 crc16 jbd2 mbcache sd_mod ahci_platform libahci_platform libahci 
xhci_plat_hcd libata xhci_hcd scsi_mod usbcore msm_emac sdhci_acpi sdhci 
usb_common pinctrl_qdf2xxx
[ 1815.471677] CPU: 7 PID: 1950 Comm: kssif0042 Not tainted 4.7.0-2-generic 
#5~pdaw1.0+bandera.9-Ubuntu
[ 1815.480789] Hardware name: Default string Default string/Default string, 
BIOS 5.12 12/12/2012
[ 1815.489296] task: edf1aa074380 ti: edf1a782 task.ti: 
edf1a782
[ 1815.496772] PC is at ipmi_ssif_thread+0x84/0x128 [ipmi_ssif]
[ 1815.502407] LR is at ipmi_ssif_thread+0x6c/0x128 [ipmi_ssif]
[ 1815.508046] pc : [] lr : [] pstate: 
00400145
[ 1815.515424] sp : edf1a7823de0
[ 1815.518723] x29: edf1a7823de0 x28: 
[ 1815.524018] x27:  x26: 
[ 1815.529313] x25:  x24: 
[ 1815.534608] x23: edeeb9dbba08 x22: 219c9d0a3000
[ 1815.539903] x21: 219c9d0a2420 x20: edeeb9dbba00
[ 1815.545198] x19: edeeb9dbb800 x18: 0014
[ 1815.550494] x17:  x16: 
[ 1815.555789] x15:  x14: 
[ 1815.561084] x13:  x12: 071c71c71c71c71c
[ 1815.566379] x11: 00ba x10: 0960
[ 1815.571674] x9 : 0040 x8 : edf1ad28
[ 1815.576969] x7 :  x6 : edf1aa9f9600
[ 1815.582264] x5 : edf1ad00 x4 : 
[ 1815.587560] x3 : 0026 x2 : 0025
[ 1815.592855] x1 : 0007 x0 : edf1aa2e4c00
[ 1815.598150]
[ 1815.599626] Process kssif0042 (pid: 1950, stack limit = 0xedf1a7820020)
[ 1815.606571] Stack: (0xedf1a7823de0 to 0xedf1a7824000)
[ 1815.612301] 3de0: edf1a7823e20 219ca122cb1c edf1ab9d5800 
219ca20cdfa8
[ 1815.620113] 3e00: 219ca1aa2ee8 edeeb9dbb800 219c9d09f590 
edeeb9dbb800
[ 1815.627925] 3e20:  219ca11c4f10 219ca122ca30 
edf1ab9d5800
[ 1815.635737] 3e40:    

[ 1815.643550] 3e60:  219ca12399a8 edeeb9dbb800 
edf1
[ 1815.651363] 3e80:  edf1a7823e88 edf1a7823e88 

[ 1815.659175] 3ea0:  edf1a7823ea8 edf1a7823ea8 
cb88537fdc8ba500
[ 1815.666987] 3ec0:    

[ 1815.674800] 3ee0:    

[ 1815.682612] 3f00:    

[ 1815.690425] 3f20:    

[ 1815.698237] 3f40:    

[ 1815.706050] 3f60:    

[ 1815.713862] 3f80:    

[ 1815.721675] 3fa0:    

[ 1815.729487] 3fc0:  0005  

[ 1815.737300] 3fe0:    

[ 1815.745112] Call trace:
[ 1815.747543] Exception stack(0xedf1a7823bf0 to 0xedf1a7823d20)
[ 1815.753966] 3be0: edeeb9dbb800 0001
[ 1815.761779] 3c00: edf1a7823de0 219c9d09f614 00400145 
219c9d0067c0
[ 1815.769592] 3c20: edf1a5a59840 0005  
0042
[ 1815.777404] 3c40: 0006  edf1a7823db0 

[ 1815.785217] 3c60:  219ca1878a7c 7fff 
219ca1875158
[ 1815.793029] 3c80: edf1a7823d30 00220042 edf1a7823cd0 
00010042
[ 1815.800842] 3ca0

[Kernel-packages] [Bug 1684731] Re: zfs-share.service: Failed at step EXEC spawning /usr/bin/rm: No such file or directory

[James Bowery]

Affecting my 17.04 system.

`May 10 12:22:08 ... systemd[2146]: zfs-share.service: Failed at step
EXEC spawning /usr/bin/rm: No such file or directory`

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

Title:
  zfs-share.service: Failed at step EXEC spawning /usr/bin/rm: No such
  file or directory

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  wrong `rm` path on /lib/systemd/system/zfs-share.service

  ExecStartPre=-/usr/bin/rm -f /etc/dfs/sharetab

  there is no file such /usr/bin/rm

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

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

[Kernel-packages] [Bug 1688769] Re: Login loop and low resolution with 4.4.0-77-generic

[Kay]

Ok, upgrading to the newest Nvidia driver helped me solving this issue.

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

Title:
  Login loop and low resolution with 4.4.0-77-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I updated my kernel to the latest version from the repository and now
  I have to always boot from a previous kernel.

  When I boot into linux-4.4.0-77-generic I got a stuck in LightDM and
  have an extreme low resolution.

  I'm using a GTX 750ti with proprietary test drivers (375.29)

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

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

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

[Brad Figg]

This change was made by a bot.

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

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

Title:
  Kernel bug after probable OOM?

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Symptoms were a hung tab in Firefox (nightly) which then left a zombie
  process lingering around after introducing the processes to Mr Kill
  -KILL.

  I don't have swap configured because I like to be different.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed May 10 17:28:21 2017
  HibernationDevice: RESUME=UUID=fda86ae0-6316-4551-a064-a782b5d2a754
  InstallationDate: Installed on 2015-07-04 (676 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: MSI MS-7917
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=c992784f-51c3-441c-b9ae-e4e9278f2a4b ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-24 (16 days ago)
  dmi.bios.date: 12/23/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97 GAMING 5 (MS-7917)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd12/23/2014:svnMSI:pnMS-7917:pvr1.0:rvnMSI:rnZ97GAMING5(MS-7917):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7917
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1647826] Re: intel 8260 doesn't work with linux kernel 4.8+ when using ucode version 22

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware - 1.164.1

---
linux-firmware (1.164.1) zesty; urgency=medium

  * intel 8260 doesn't work with linux kernel 4.8+ when using ucode version 22
(LP: #1647826)
- UBUNTU: SAUCE: Remove iwlwifi-8000C-22.ucode

 -- Seth Forshee   Fri, 21 Apr 2017 11:36:23
-0500

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

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

Title:
  intel 8260 doesn't work with linux kernel 4.8+ when using ucode
  version 22

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Yakkety:
  Fix Released
Status in linux-firmware source package in Zesty:
  Fix Released
Status in linux-firmware source package in Artful:
  Fix Released

Bug description:
  SRU Justification

  Impact: The -22 firmware for iwlwifi introduces regressions with some
  hardware versus earlier firmware versions. As no newer firmware is
  available, the only fix is to revert back to the older firmware which
  does work.

  Test Case: Using the -22 firmware with affected hardware produces the
  behavior described below. The -21 firmware does not.

  Regression Potential: Switching back to -21 could cause some
  regressions with other hardware supported by this firmware. However as
  -22 causes some hardware to completely fail to work any regressions
  are almost certain to be less severe than the current problems.

  ---

  The -22 microcode for the intel 8260 wifi adapter has compatibility
  issues with Linux Kernel 4.8 under certain hardware configurations.

  The iwlwifi module crashes resulting in wifi failing with "device not
  ready" and kernel errors reported in dmesg.

  [   10.691115] iwlwifi :6e:00.0: Microcode SW error detected.
  Restarting 0x200.

  Renaming the ucode file at /lib/firmware/iwlwifi-8000C-22.ucode to
  fallback to the -21 ucode resolves the issue and wifi begins working
  normally again.

  This is an issue with Linux kernel 4.8 on both yakkety and xenial, so
  the bug doesn't currently affect users on xenial, but will begin to
  after the 16.04.2 HWE release.  Kernel 4.4 is unaffected because it
  doesn't attempt to use the -22 ucode

  The failure doesn't necessarily affect all machines of a given model
  with the 8260, but I can reproduce it on multiple laptops when 64GB of
  RAM are installed (4x16GB).  The RAM itself does not appear to be an
  issue.

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

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

[Kernel-packages] [Bug 1647826] Re: intel 8260 doesn't work with linux kernel 4.8+ when using ucode version 22

[Robie Basak]

The current verification-done tag looks like it is intended for Zesty
only, and the Xenial proposed package still needs verification.

** Tags removed: verification-done
** Tags added: verification-done-zesty

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

Title:
  intel 8260 doesn't work with linux kernel 4.8+ when using ucode
  version 22

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Yakkety:
  Fix Released
Status in linux-firmware source package in Zesty:
  Fix Released
Status in linux-firmware source package in Artful:
  Fix Released

Bug description:
  SRU Justification

  Impact: The -22 firmware for iwlwifi introduces regressions with some
  hardware versus earlier firmware versions. As no newer firmware is
  available, the only fix is to revert back to the older firmware which
  does work.

  Test Case: Using the -22 firmware with affected hardware produces the
  behavior described below. The -21 firmware does not.

  Regression Potential: Switching back to -21 could cause some
  regressions with other hardware supported by this firmware. However as
  -22 causes some hardware to completely fail to work any regressions
  are almost certain to be less severe than the current problems.

  ---

  The -22 microcode for the intel 8260 wifi adapter has compatibility
  issues with Linux Kernel 4.8 under certain hardware configurations.

  The iwlwifi module crashes resulting in wifi failing with "device not
  ready" and kernel errors reported in dmesg.

  [   10.691115] iwlwifi :6e:00.0: Microcode SW error detected.
  Restarting 0x200.

  Renaming the ucode file at /lib/firmware/iwlwifi-8000C-22.ucode to
  fallback to the -21 ucode resolves the issue and wifi begins working
  normally again.

  This is an issue with Linux kernel 4.8 on both yakkety and xenial, so
  the bug doesn't currently affect users on xenial, but will begin to
  after the 16.04.2 HWE release.  Kernel 4.4 is unaffected because it
  doesn't attempt to use the -22 ucode

  The failure doesn't necessarily affect all machines of a given model
  with the 8260, but I can reproduce it on multiple laptops when 64GB of
  RAM are installed (4x16GB).  The RAM itself does not appear to be an
  issue.

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

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

[Kernel-packages] [Bug 1687256] Re: byd touchpad no longer detected

[Christopher M. Penalver]

** Tags added: kernel-bug-exists-upstream-4.11-rc8 needs-upstream-
testing

** Tags added: needs-bisect regression-update

** Tags added: zesty

** Description changed:

  When running on kernel 4.8.0-34 my Lafite byd touchpad is recognised 
correctly and shows with xinput --list as BYDPS/2 BYD Touchpad.
  If I use any higher upgrade, eg 4.8.0-46 in 16.10 then touchpad is only 
identified as ImPS/2 Generic Wheel Mouse. The same applies if I try 17.04 from 
an external drive, touchpad does not work and cursor remains in top rh corner 
of screen.
  This could be related to the changelog 
https://launchpad.net/ubuntu/+source/linux/+changelog
  
  4.8.0-36.38 in yakkety-proposed
  
    * Yakkety update to v4.8.13 stable release (LP: #1650581)
  ...
  - Input: psmouse - disable automatic probing of BYD touchpads
  
- Any thought on what has changed and how to resolve issue so that I can 
upgrade to later version?
- Thanks
+ https://patchwork.kernel.org/patch/9424421/
+ 
  ---
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   3590 F pulseaudio
   /dev/snd/controlC1:  dave   3590 F pulseaudio
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=0b7a1f56-4391-4d9d-90ed-d0f5f5d76c90
  InstallationDate: Installed on 2015-05-17 (714 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Intel Corporation SharkBay Platform
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-34-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-34-generic N/A
   linux-backports-modules-4.8.0-34-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.8.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
  
  _MarkForUpload: True
  dmi.bios.date: 03/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.6.5
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: WhiteTip Mountain1 Fab2
  dmi.board.vendor: Topstar
  dmi.board.version: Fab2
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd03/27/2015:svnIntelCorporation:pnSharkBayPlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrFab2:cvnToBeFilledByO.E.M.:ct9:cvrToBeFilledByO.E.M.:
  dmi.product.name: SharkBay Platform
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

** Tags removed: needs-bisect

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

Title:
  byd touchpad no longer detected

Status in linux package in Ubuntu:
  Triaged

Bug description:
  When running on kernel 4.8.0-34 my Lafite byd touchpad is recognised 
correctly and shows with xinput --list as BYDPS/2 BYD Touchpad.
  If I use any higher upgrade, eg 4.8.0-46 in 16.10 then touchpad is only 
identified as ImPS/2 Generic Wheel Mouse. The same applies if I try 17.04 from 
an external drive, touchpad does not work and cursor remains in top rh corner 
of screen.
  This could be related to the changelog 
https://launchpad.net/ubuntu/+source/linux/+changelog

  4.8.0-36.38 in yakkety-proposed

    * Yakkety update to v4.8.13 stable release (LP: #1650581)
  ...
  - Input: psmouse - disable automatic probing of BYD touchpads

  https://patchwork.kernel.org/patch/9424421/

  ---
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   3590 F pulseaudio
   /dev/snd/controlC1:  dave   3590 F pulseaudio
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=0b7a1f56-4391-4d9d-90ed-d0f5f5d76c90
  InstallationDate: Installed on 2015-05-17 (714 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Intel Corporation SharkBay Platform
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-34-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8

[Kernel-packages] [Bug 1689661] Re: No PMU support for ACPI-based arm64 systems

[dann frazier]

** Description changed:

  [Impact]
  ACPI-based arm64 systems, such as the Qualcomm QDF2400 and the Hisilicon D05, 
do not currently have PMU support. This means that tools like perf are unable 
to use the built-in hardware event counters.
  
  [Test Case]
  On an ACPI-based arm64 system, run the following commands:
  
  sudo perf list pmu
  sudo perf list hw
  
  Without ACPI PMU support, these will be empty.
  
  [Regression Risk]
  The changes are restricted to ARM-specific code, other than an added enum 
value in linux/cpuhotplug.h. This reduces the non-negligible regression risk to 
the ARM architecture.
  
- For ACPI-based ARM platforms, regression risk is negligible because they
- did not have PMU support previously. The non-perf related code is
- restricted to a change in arch/arm64/kernel/smp.c that saves off
- pointers to each CPU's MADT GICC tables. The code is populating a static
- array - so pretty low risk (no pointer dereferences, etc).
+ For ACPI-based ARM platforms, regression risk is limited because they
+ did not have PMU support previously. However, if this code is buggy,
+ previously working commands that just made use of non-PMU events (e.g.
+ perf top) might start causing problems. To mitigate this, I did a
+ perf_fuzzer run on a QDF2400 (ACPI-based) and confirmed it survived
+ (Note: this included a workaround for LP: #1689855, which will need to
+ be fixed separately once upstreamed).
  
- The most significant regression risk is to ARM non-ACPI platforms. To
- mitigate this, we should test this backport on Cavium ThunderX and HP
- m400 systems.
+ For non-ACPI-based (i.e. devicetree) ARM platforms, there is a chance
+ that the changes have broken PMU support. To mitigate that, I also did a
+ perf_fuzzer run on a Cavium ThunderX system booted in DT mode, which it
+ survived.
+ 
+ Finally, the non-perf related changes in this series are restricted to a
+ change in arch/arm64/kernel/smp.c that saves off pointers to each CPU's
+ MADT GICC tables. The code is populating a static array with existing
+ data - so pretty low risk (no pointer dereferences, etc).

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

Title:
  No PMU support for ACPI-based arm64 systems

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

Bug description:
  [Impact]
  ACPI-based arm64 systems, such as the Qualcomm QDF2400 and the Hisilicon D05, 
do not currently have PMU support. This means that tools like perf are unable 
to use the built-in hardware event counters.

  [Test Case]
  On an ACPI-based arm64 system, run the following commands:

  sudo perf list pmu
  sudo perf list hw

  Without ACPI PMU support, these will be empty.

  [Regression Risk]
  The changes are restricted to ARM-specific code, other than an added enum 
value in linux/cpuhotplug.h. This reduces the non-negligible regression risk to 
the ARM architecture.

  For ACPI-based ARM platforms, regression risk is limited because they
  did not have PMU support previously. However, if this code is buggy,
  previously working commands that just made use of non-PMU events (e.g.
  perf top) might start causing problems. To mitigate this, I did a
  perf_fuzzer run on a QDF2400 (ACPI-based) and confirmed it survived
  (Note: this included a workaround for LP: #1689855, which will need to
  be fixed separately once upstreamed).

  For non-ACPI-based (i.e. devicetree) ARM platforms, there is a chance
  that the changes have broken PMU support. To mitigate that, I also did
  a perf_fuzzer run on a Cavium ThunderX system booted in DT mode, which
  it survived.

  Finally, the non-perf related changes in this series are restricted to
  a change in arch/arm64/kernel/smp.c that saves off pointers to each
  CPU's MADT GICC tables. The code is populating a static array with
  existing data - so pretty low risk (no pointer dereferences, etc).

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

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

[Kernel-packages] [Bug 1689855] [NEW] perf hangs on QDF 2400 servers (Falkor SoC)

[dann frazier]

Public bug reported:

[Impact]
There's a hardware errata that causes hangs when using PMU counters.
It has been assigned errata ID E1029.

[Test Case]
sudo perf top

After a few moments, you should notice hangs, most likely with rcu_sched
messages on the console.

[Regression Risk]
(TBD, one upstream fix is identified)

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

** Affects: linux (Ubuntu Zesty)
 Importance: High
 Status: Confirmed

** Description changed:

  [Impact]
  There's a hardware errata that causes hangs when using PMU counters.
+ It has been assigned errata ID E1029.
  
  [Test Case]
  sudo perf top
  
  After a few moments, you should notice hangs, most likely with rcu_sched
  messages on the console.
  
  [Regression Risk]
  (TBD, one upstream fix is identified)

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

Title:
  perf hangs on QDF 2400 servers (Falkor SoC)

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

Bug description:
  [Impact]
  There's a hardware errata that causes hangs when using PMU counters.
  It has been assigned errata ID E1029.

  [Test Case]
  sudo perf top

  After a few moments, you should notice hangs, most likely with
  rcu_sched messages on the console.

  [Regression Risk]
  (TBD, one upstream fix is identified)

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

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

[Kernel-packages] [Bug 1687107] Re: CVE-2016-8645: Linux kernel mishandles socket buffer (skb) truncation

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'. If the problem still exists,
change the tag 'verification-needed-trusty' to 'verification-failed-
trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

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

Title:
  CVE-2016-8645: Linux kernel mishandles socket buffer (skb) truncation

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

Bug description:
  [Impact]

  From CVE description:
  https://people.canonical.com/~ubuntu-security/cve/2016/CVE-2016-8645.html

  "The TCP stack in the Linux kernel before 4.8.10 mishandles skb truncation,
  which allows local users to cause a denial of service (system crash) via a
  crafted application that makes sendto system calls, related to
  net/ipv4/tcp_ipv4.c and net/ipv6/tcp_ipv6.c."

  [Test Case]
  See references in the CVE page.

  [Regression Potential]
  This modifies the code that handles all tcp packets, so it could cause 
problems with network traffic, although unlikely since it's been applied 
upstream and to various stable kernels (but not the 3.13.y stable branch).

  [Other Info]
  The patch appears to have been pulled into xenial through the 4.4.y stable 
tree, but it doesn't appear that the patch will be applied to the 3.13.y stable 
tree, so this bug is track manually adding the patch.

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

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

[Kernel-packages] [Bug 1689855] Re: perf hangs on QDF 2400 servers (Falkor SoC)

[dann frazier]

Initial upstream workaround submission:
https://patchwork.kernel.org/patch/9601819/

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

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

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

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

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

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

Title:
  perf hangs on QDF 2400 servers (Falkor SoC)

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

Bug description:
  [Impact]
  There's a hardware errata that causes hangs when using PMU counters.
  It has been assigned errata ID E1029.

  [Test Case]
  sudo perf top

  After a few moments, you should notice hangs, most likely with
  rcu_sched messages on the console.

  [Regression Risk]
  (TBD, one upstream fix is identified)

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

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

[Kernel-packages] [Bug 1683976] Re: Please backport fix to reference leak in cgroup blkio throttle

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'. If the problem still exists,
change the tag 'verification-needed-trusty' to 'verification-failed-
trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

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

Title:
  Please backport fix to reference leak in cgroup blkio throttle

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

Bug description:
  This is fixed in Linux 4.5
  
https://github.com/torvalds/linux/commit/39a169b62b415390398291080dafe63aec751e0a

  Basically the module reference will leak whenever you write to
  /sys/fs/cgroup/blkio/blkio.throttle.*

  $ uname -a
  Linux david-kvm 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  $ lsmod | grep ^zfs
  zfs  2813952  1
  $ sudo sh -c 'i=100; while [ $i -gt 0 ]; do echo "230:0 1024" > 
/sys/fs/cgroup/blkio/blkio.throttle.read_bps_device; i=$(($i - 1)); done'
  $ lsmod | grep ^zfs
  zfs  2813952  101

  This patch should be applied to all kernel < 4.5

  Thanks

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

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

[Kernel-packages] [Bug 1678676] Re: linux_3.13.0-*.*: nVMX: Check current_vmcs12 before accessing in handle_invept()

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'. If the problem still exists,
change the tag 'verification-needed-trusty' to 'verification-failed-
trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

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

Title:
  linux_3.13.0-*.*: nVMX: Check current_vmcs12 before accessing in
  handle_invept()

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  KVM in linux 3.11 - 3.14 (including ubuntu 14.04 linux <= 3.13.0-113.160) has 
a
  flaw in INVEPT emulation that could crash the host.

  [ 1046.384746] BUG: unable to handle kernel NULL pointer dereference at 
0070
  [ 1046.387386] IP: [] handle_invept+0x123/0x170 [kvm_intel]
  [ 1046.389577] PGD 0 
  [ 1046.390273] Oops:  [#1] SMP 

  (tested with Ubuntu 14.04 linux-image-3.13.0-113-generic)

  The host KVM touches NULL pointer (vmx->nested.current_vmcs12) when a
  (crafted or buggy) guest issues a single-context INVEPT instruction
  *without* VMPTRLD like this:

kvm_cpu_vmxon(phys_addr);
ept_sync_context(0);

  (requires nested EPT; full linux kernel module code attached)

  This code is introduced in upstream commit 
bfd0a56b90005f8c8a004baf407ad90045c2b11e
  (nEPT: Nested INVEPT) and removed in 4b855078601fc422dbac3059f2215e776f49780f
  (KVM: nVMX: Don't advertise single context invalidation for invept).
  Therefore there should be two ways to fix this.

  a. pullup bfd0a56b90005f (and 45e11817d5703e)
  b. check current_vmcs12 before accessing for minimal fix:

  diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
  index d9e567f..d785e9c 100644
  --- a/arch/x86/kvm/vmx.c
  +++ b/arch/x86/kvm/vmx.c
  @@ -6391,6 +6391,8 @@ static int handle_invept(struct kvm_vcpu *vcpu)
   
switch (type) {
case VMX_EPT_EXTENT_CONTEXT:
  + if (to_vmx(vcpu)->nested.current_vmptr == -1ull)
  + break;
if ((operand.eptp & eptp_mask) !=
(nested_ept_get_cr3(vcpu) & eptp_mask))
break;

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

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

[Kernel-packages] [Bug 1689856] [NEW] perf: qcom: Add L3 cache PMU driver

[dann frazier]

Public bug reported:

[Impact]
Without this driver, users of Qualcomm QDF2400 servers will be unable to 
profile L3 cache events.

[Test case]
ubuntu@ubuntu:~$ sudo perf list | grep l3cache | wc -l
84

Without this driver, there are 0.

[Regression Risk]
This is a new driver that is only used on these servers, so the regression risk 
is pretty isolated to this platform. To mitigate the risk there, I ran 
perf_fuzzer on that system and verified that it survived. Note: I did this 
testing w/ a workaround for LP: #1689855 applied, to avoid hangs caused by a 
hardware issue.

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

** Affects: linux (Ubuntu Zesty)
 Importance: High
 Assignee: dann frazier (dannf)
 Status: Confirmed

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

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

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

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

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

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

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

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

Title:
  perf: qcom: Add L3 cache PMU driver

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

Bug description:
  [Impact]
  Without this driver, users of Qualcomm QDF2400 servers will be unable to 
profile L3 cache events.

  [Test case]
  ubuntu@ubuntu:~$ sudo perf list | grep l3cache | wc -l
  84

  Without this driver, there are 0.

  [Regression Risk]
  This is a new driver that is only used on these servers, so the regression 
risk is pretty isolated to this platform. To mitigate the risk there, I ran 
perf_fuzzer on that system and verified that it survived. Note: I did this 
testing w/ a workaround for LP: #1689855 applied, to avoid hangs caused by a 
hardware issue.

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

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

[Kernel-packages] [Bug 1689853] [NEW] Kernel bug after probable OOM?

[Adam Collard]

Public bug reported:

Symptoms were a hung tab in Firefox (nightly) which then left a zombie
process lingering around after introducing the processes to Mr Kill
-KILL.

I don't have swap configured because I like to be different.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-19-generic 4.10.0-19.21
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Wed May 10 17:28:21 2017
HibernationDevice: RESUME=UUID=fda86ae0-6316-4551-a064-a782b5d2a754
InstallationDate: Installed on 2015-07-04 (676 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: MSI MS-7917
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=c992784f-51c3-441c-b9ae-e4e9278f2a4b ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-19-generic N/A
 linux-backports-modules-4.10.0-19-generic  N/A
 linux-firmware 1.164
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-04-24 (16 days ago)
dmi.bios.date: 12/23/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.9
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97 GAMING 5 (MS-7917)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd12/23/2014:svnMSI:pnMS-7917:pvr1.0:rvnMSI:rnZ97GAMING5(MS-7917):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7917
dmi.product.version: 1.0
dmi.sys.vendor: MSI

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


** Tags: amd64 apport-bug zesty

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

Title:
  Kernel bug after probable OOM?

Status in linux package in Ubuntu:
  New

Bug description:
  Symptoms were a hung tab in Firefox (nightly) which then left a zombie
  process lingering around after introducing the processes to Mr Kill
  -KILL.

  I don't have swap configured because I like to be different.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed May 10 17:28:21 2017
  HibernationDevice: RESUME=UUID=fda86ae0-6316-4551-a064-a782b5d2a754
  InstallationDate: Installed on 2015-07-04 (676 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: MSI MS-7917
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=c992784f-51c3-441c-b9ae-e4e9278f2a4b ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-24 (16 days ago)
  dmi.bios.date: 12/23/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97 GAMING 5 (MS-7917)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd12/23/2014:svnMSI:pnMS-7917:pvr1.0:rvnMSI:rnZ97GAMING5(MS-7917):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7917
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1684010] Re: 17.04, i915 freeze on VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller

[Traumflug]

Congratulations for managing to get a backtrace, @Jonas Slivka!

Did you run a kernel with debug symbols, perhaps? My kern.log has zero
backtraces, despite at least 5 freezes.

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

Title:
  17.04, i915 freeze on VGA compatible controller: Intel Corporation
  Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Just freezes all unity and/or X.
  Nothing in any logs though.

  16.10 worked just fine.

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

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

[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe)

[goldyfruit]

@Thiago, same for us. Hope it will be fixed soon !

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

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or
  4.8.0-49, xenial-hwe)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  In Progress
Status in linux-hwe source package in Yakkety:
  Confirmed
Status in linux-hwe-edge source package in Yakkety:
  Confirmed
Status in linux source package in Zesty:
  Fix Released
Status in linux-hwe source package in Zesty:
  Confirmed
Status in linux-hwe-edge source package in Zesty:
  Confirmed

Bug description:
  Since I upgraded the kernel from linux-image-4.8.0-46-generic to
  linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to
  change the MTU.

  It seems to be known bug already fixed:
  https://bugzilla.kernel.org/show_bug.cgi?id=194763

  # ip l sh eno49
  2: eno49:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh eno50
  3: eno50:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh bond0
  6: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l set mtu 9000 bond0
  RTNETLINK answers: Invalid argument

  root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog
  Apr  4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 
requested, hw max 1500

  # modinfo ixgbe
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.4.0-k
  license:GPL
  description:Intel(R) 10 Gigabit PCI Express Network Driver

  # modinfo bonding
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko
  author: Thomas Davis, tada...@lbl.gov and many others
  description:Ethernet Channel Bonding Driver, v3.7.1
  version:3.7.1

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

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

[Kernel-packages] [Bug 1689651] Re: vblank wait timed out on crtc 0 after screen lock on Dell Latitude e6220

[Thomas Nilefalk]

Here's a partial dmesg log from a locked screen to the hang with
drm:debug=0xe.

** Attachment added: "dmesg_drm_debug.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689651/+attachment/4874740/+files/dmesg_drm_debug.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/1689651

Title:
  vblank wait timed out on crtc 0 after screen lock on Dell Latitude
  e6220

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After a screen lock, the screen hangs, with the attached stack dump in
  dmesg.

  I've seen multiple bug reports with similar effect, but the workaround
  has been "video=SVIDEO-1:d" as boot parameters, but this does not
  affect my case. Also, the other reports, such as
  https://bugs.freedesktop.org/show_bug.cgi?id=93782, includes
  'intel_tv_detect' which mine does not.

  lspci:
  00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family 
DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09)
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network 
Connection (rev 04)
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 04)
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 04)
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b4)
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b4)
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b4)
  00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 6 (rev b4)
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation QM67 Express Chipset Family LPC 
Controller (rev 04)
  00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller 
[RAID mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus 
Controller (rev 04)
  02:00.0 Network controller: Broadcom Corporation BCM43228 802.11a/b/g/n
  09:00.0 SD Host controller: O2 Micro, Inc. OZ600FJ0/OZ900FJ0/OZ600FJS SD/MMC 
Card Reader Controller (rev 05)
  09:00.1 Mass storage controller: O2 Micro, Inc. Device 8231 (rev 03)

  ProblemType: Bug
  DistroRelease: elementary 0.4
  Package: linux-image-4.4.0-77-generic 4.4.0-77.98 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thoni561567 F pulseaudio
  Date: Tue May  9 22:40:05 2017
  HibernationDevice: RESUME=UUID=924774bb-ccbe-446b-a22e-2caa4b84f3b6
  InstallationDate: Installed on 2017-05-03 (5 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Latitude E6220
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic 
root=UUID=4238aca4-33a0-457b-81fa-81d7b2316a6c ro quiet splash video=SVIDEO-1:d 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-77-generic N/A
   linux-backports-modules-4.4.0-77-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0R97MN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd06/28/2013:svnDellInc.:pnLatitudeE6220:pvr01:rvnDellInc.:rn0R97MN:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6220
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

Re: [Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

[Seth Forshee]

On Wed, May 10, 2017 at 02:19:26PM -, Vidar Braut Haarr wrote:
> Will it be included in the next artful kernel, or only zesty? I ask
> because the email subject says "[PATCH 0/4][Zesty SRU]".
> 
> And when will it be, roughly? 2 weeks? 3 months? Tomorrow?

Currently artful is using the same kernel as zesty. As per previous
testing on this bug, kernels after 4.10 should not be affected.

Given the current SRU schedule (and barring any unforeseen
circumstances), the kernel with this fix should release on June 5.

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

Title:
  kernel BUG at /build/linux-
  7LGLH_/linux-4.10.0/include/linux/swapops.h:129

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-edge package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux-hwe-edge source package in Zesty:
  In Progress

Bug description:
  Randomly, khugepaged process will take 100% CPU, and I can only
  restart the computer to recover it.

  Relevant dmesg attached (dmesg_crash.txt).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mathieu2221 F pulseaudio
   /dev/snd/pcmC1D0p:   mathieu2221 F...m pulseaudio
   /dev/snd/controlC1:  mathieu2221 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar 21 23:03:23 2017
  HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd
  InstallationDate: Installed on 2016-01-31 (415 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: LENOVO 20344
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1689372] Re: disable many ACPI features

[Leann Ogasawara]

** Description changed:

  Many ACPI features can be disabled, per Colin King's research.
+ 
+ Colin King has demonstrated measurable boot speed improvements (up to 3%)
+ by disabling many ACPI features not used by cloud kernels.  That work also
+ allows us to unhook additional unused subsystems (Nouveau, gpiolib, pincntrl).
+ Disk space utilization of the kernel is reduced:
+   /boot by ~200KB
+   /lib/modules by ~170 Kb

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

Title:
  disable many ACPI features

Status in linux-aws package in Ubuntu:
  In Progress

Bug description:
  Many ACPI features can be disabled, per Colin King's research.

  Colin King has demonstrated measurable boot speed improvements (up to 3%)
  by disabling many ACPI features not used by cloud kernels.  That work also
  allows us to unhook additional unused subsystems (Nouveau, gpiolib, pincntrl).
  Disk space utilization of the kernel is reduced:
/boot by ~200KB
/lib/modules by ~170 Kb

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

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

[Kernel-packages] [Bug 1689374] Re: disable GPIOLIB, PINCTRL, and all consumers of them

[Leann Ogasawara]

** Description changed:

  These can be disabled in linux-aws, and must be disabled in order to
  disable various ACPI features.
+ 
+ Colin King has demonstrated measurable boot speed improvements (up to 3%)
+ by disabling many ACPI features not used by cloud kernels.  That work also
+ allows us to unhook additional unused subsystems (Nouveau, gpiolib, pincntrl).
+ Disk space utilization of the kernel is reduced:
+   /boot by ~200KB
+   /lib/modules by ~170 Kb

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

Title:
  disable GPIOLIB, PINCTRL, and all consumers of them

Status in linux-aws package in Ubuntu:
  In Progress

Bug description:
  These can be disabled in linux-aws, and must be disabled in order to
  disable various ACPI features.

  Colin King has demonstrated measurable boot speed improvements (up to 3%)
  by disabling many ACPI features not used by cloud kernels.  That work also
  allows us to unhook additional unused subsystems (Nouveau, gpiolib, pincntrl).
  Disk space utilization of the kernel is reduced:
/boot by ~200KB
/lib/modules by ~170 Kb

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

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

[Kernel-packages] [Bug 1689373] Re: disable NOUVEAU

[Leann Ogasawara]

** Description changed:

  Nouveau can be disabled in linux-aws, and must be disabled in order to
  disable some ACPI features.
+ 
+ Colin King has demonstrated measurable boot speed improvements (up to 3%)
+ by disabling many ACPI features not used by cloud kernels.  That work also
+ allows us to unhook additional unused subsystems (Nouveau, gpiolib, pincntrl).
+ Disk space utilization of the kernel is reduced:
+   /boot by ~200KB
+   /lib/modules by ~170 Kb

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

Title:
  disable NOUVEAU

Status in linux-aws package in Ubuntu:
  In Progress

Bug description:
  Nouveau can be disabled in linux-aws, and must be disabled in order to
  disable some ACPI features.

  Colin King has demonstrated measurable boot speed improvements (up to 3%)
  by disabling many ACPI features not used by cloud kernels.  That work also
  allows us to unhook additional unused subsystems (Nouveau, gpiolib, pincntrl).
  Disk space utilization of the kernel is reduced:
/boot by ~200KB
/lib/modules by ~170 Kb

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

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

[Kernel-packages] [Bug 1688158] RE: how to test iommu.passthough=0/1 ??

[Manoj Iyer]

ccing bug for the record on testing.

On Wed, May 10, 2017 at 10:07 AM, Nate Watterson 
 wrote:
> Unless this is a PCIe attached SATA disk, you will not see any impact 
> from the iommu.passthrough setting since the SATA SMMUs are not even 
> enabled! Additionally, the FIO results you sent last week I think 
> showed rates beyond the physical capabilities of SATA so you should 
> probably make sure that file system caching is disabled or just 
> access the disk directly using a readonly profile.  Also, the SMMU is 
> sufficiently fast that you will typically not even see the SMMU 
> impact on a relatively low BW peripheral like SATA. I would recommend 
> getting an NVME drive.
> -Nate
> 
> From: Manoj Iyer [mailto:manoj.i...@canonical.com]
> Sent: Wednesday, May 10, 2017 10:05 AM
> To: Nate Watterson 
> Cc: Timur Tabi 
> Subject: RE: how to test iommu.passthough=0/1 ??
> 
> 
> 
> On Wed, May 10, 2017 at 8:33 AM, Nate Watterson 
>  wrote:
> 
>> Ok, what is the physical device that ./fio.virtualfs is being 
>> created on? Is it and NVME or SATA (internal or PCI attached) disk?
> 
> Ah! it was on the SATA drive. Sorry misunderstood your initial 
> question.
> 
> 
>> -Original Message- From: Manoj Iyer 
>> [mailto:manoj.i...@canonical.com] Sent: Wednesday, May 10, 2017 9:06 
>> AM To: Nate Watterson  Cc: Manoj Iyer 
>> ; Timur Tabi  
>> Subject: RE: how to test iommu.passthough=0/1 ?? On Wed, 10 May 
>> 2017, Nate Watterson wrote:
>>> Manoj, What was the backing store for the file mounted as 
>>> /dev/loop0 in the results you sent?
>> dd if=/dev/zero of=./fio.virtualfs bs=1M count=5120 mkfs.ext4 
>> ./fio.virtualfs sudo losetup /dev/loop0 ./fio.virtualfs
>>>   For iperf, I typically only test the target device as the iperf 
>>> server and directly connect a host PC to run the client threads. I 
>>> test this way because it usually has the worst performance with 
>>> SMMU enabled.   Target CMD: iperf -s Client CMD: iperf -c 
>>> 192.168.2.222 -fg -i10 -t60 -P8   -Nate   From: Manoj Iyer 
>>> [mailto:manoj.i...@canonical.com] Sent: Tuesday, May 9, 2017 10:29 
>>> PM To: Nate Watterson  Cc: Timur Tabi 
>>>  Subject: RE: how to test 
>>> iommu.passthough=0/1 ??   Nate,   Thanks for that info. I will give 
>>> that a try. Did you see my iperf results ? those were kind of odd 
>>> too.. I thought with the mlx card I might be testing with PCIe 
>>> device .. but may I was hitting a limitation with iperf..Also, 
>>> I tested the same kernel on Cavium system, and with 
>>> iommu.passthough=1/0 was I seeing a significant difference in the 
>>> iops with a file mounted to /dev/loop0. Its attached here..   On 
>>> Tue, May 9, 2017 at 8:52 PM, Nate Watterson 
>>>  wrote: Hi Manoj, Sorry for the late 
>>> reply. I finally found some time to test passthrough mode and 
>>> verified using the SMMU performance counters that the 
>>> ‘iommu.passthrough’ param is working as I would expect it to (1 
>>> == Passthrough / 0 == non-Passthrough). I am not sure why you’re 
>>> seeing this strange behavior but based on the logs you’ve sent, I 
>>> have a few comments:   Your boot log is showing that only the PCIe 
>>> SMMUs are enabled (this is good, it means your FW is recent). 
>>> Because of this, you will need to do your testing with a PCIe 
>>> attached device instead of the SD card or SSD (assuming it was 
>>> connected to the onboard SATA). I would recommend using an NVME 
>>> drive as the impact of enabling passthrough mode will only really 
>>> be apparent with devices capable of sustaining high IO throughput.  
>>>  I would recommend changing your FIO profile to access the device 
>>> directly instead of going through the filesystem. Additionally, I 
>>> would recommend using a readonly profile without randomization to 
>>> preserve the disk and get consistent results.  The following is the 
>>> FIO command that I use:   fio --name=global --readonly 
>>> --group_reporting \ --direct=1 --ioengine=libaio --rw=read 
>>> --eta-newline=1s \ --size=1T --blocksize=512k --iodepth=32 
>>> --numjobs=1 --runtime=10s \ --name=nvme_0 --filename=/dev/nvme0n1   
>>> *** iommu.passthrough=1 *** READ: io=25301MB, aggrb=2528.3MB/s, 
>>> minb=2528.3MB/s, maxb=2528.3MB/s, mint=10007msec, maxt=10007msec   
>>> *** iommu.passthrough=0 *** READ: io=22657MB, aggrb=2265.5MB/s, 
>>> minb=2265.5MB/s, maxb=2265.5MB/s, mint=10001msec, maxt=10001msec   
>>> Hopefully this helps. Let me know if you have any more questions. 
>>> -Nate   From: Manoj Iyer [mailto:manoj.i...@canonical.com] Sent: 
>>> Thursday, May 4, 2017 4:55 PM To: Nate Watterson 
>>>  Cc: Timur Tabi  
>>> Subject: RE: how to test iommu.passthough=0/1 ??   Nate,   I am 
>>> attaching fio output for the CAF kernel that is available in the 
>>> centriq PPA. The results are not that much different. This time I 
>>> ran fio on the loop back disk and also on the mmcblk0 SD card.   
>>> Please see the attached test report.Thanks Manoj Iyer On Thu, 
>>> May 4, 2017 at 2:46 PM, Manoj 

[Kernel-packages] [Bug 1688158] RE: how to test iommu.passthough=0/1 ??

[Manoj Iyer]

ccing bug for the record on testing

On Wed, May 10, 2017 at 8:33 AM, Nate Watterson 
 wrote:
> Ok, what is the physical device that ./fio.virtualfs is being created 
> on? Is it and NVME or SATA (internal or PCI attached) disk?
> 
> -Original Message-
> From: Manoj Iyer [mailto:manoj.i...@canonical.com]
> Sent: Wednesday, May 10, 2017 9:06 AM
> To: Nate Watterson 
> Cc: Manoj Iyer ; Timur Tabi 
> 
> Subject: RE: how to test iommu.passthough=0/1 ??
> 
> On Wed, 10 May 2017, Nate Watterson wrote:
> 
>> 
>>  Manoj,
>> 
>>  What was the backing store for the file mounted as /dev/loop0 in 
>> the results
>>  you sent?
> 
> dd if=/dev/zero of=./fio.virtualfs bs=1M count=5120
> mkfs.ext4 ./fio.virtualfs
> sudo losetup /dev/loop0 ./fio.virtualfs
> 
> 
>> 
>> 
>> 
>>  For iperf, I typically only test the target device as the iperf 
>> server and
>>  directly connect a host PC to run the client threads. I test this 
>> way
>>  because it usually has the worst performance with SMMU enabled.
>> 
>> 
>> 
>>  Target CMD: iperf -s
>> 
>>  Client CMD: iperf -c 192.168.2.222 -fg -i10 -t60 -P8
>> 
>> 
>> 
>>  -Nate
>> 
>> 
>> 
>>  From: Manoj Iyer [mailto:manoj.i...@canonical.com]
>>  Sent: Tuesday, May 9, 2017 10:29 PM
>>  To: Nate Watterson 
>>  Cc: Timur Tabi 
>>  Subject: RE: how to test iommu.passthough=0/1 ??
>> 
>> 
>> 
>>  Nate,
>> 
>> 
>> 
>>  Thanks for that info. I will give that a try. Did you see my iperf 
>> results ?
>>  those were kind of odd too.. I thought with the mlx card I might be 
>> testing
>>  with PCIe device .. but may I was hitting a limitation with iperf..
>> 
>> 
>> 
>>  Also, I tested the same kernel on Cavium system, and with
>>  iommu.passthough=1/0 was I seeing a significant difference in the 
>> iops with
>>  a file mounted to /dev/loop0. Its attached here..
>> 
>> 
>> 
>> 
>>  On Tue, May 9, 2017 at 8:52 PM, Nate Watterson 
>> 
>>  wrote:
>> 
>>Hi Manoj,
>> 
>>Sorry for the late reply. I finally found some time to test
>>passthrough mode and verified using the SMMU performance
>>counters that the ‘iommu.passthrough’ param is working as 
>> I
>>would expect it to (1 == Passthrough / 0 == non-Passthrough). 
>> I
>>am not sure why you’re seeing this strange behavior but 
>> based on
>>the logs you’ve sent, I have a few comments:
>> 
>> 
>> 
>>Your boot log is showing that only the PCIe SMMUs are enabled
>>(this is good, it means your FW is recent). Because of this, 
>> you
>>will need to do your testing with a PCIe attached device 
>> instead
>>of the SD card or SSD (assuming it was connected to the 
>> onboard
>>SATA). I would recommend using an NVME drive as the impact of
>>enabling passthrough mode will only really be apparent with
>>devices capable of sustaining high IO throughput.
>> 
>> 
>> 
>>I would recommend changing your FIO profile to access the 
>> device
>>directly instead of going through the filesystem. 
>> Additionally,
>>I would recommend using a readonly profile without 
>> randomization
>>to preserve the disk and get consistent results.  The 
>> following
>>is the FIO command that I use:
>> 
>> 
>> 
>>fio --name=global --readonly --group_reporting \
>> 
>>--direct=1 --ioengine=libaio --rw=read --eta-newline=1s \
>> 
>>--size=1T --blocksize=512k --iodepth=32 --numjobs=1
>>--runtime=10s \
>> 
>>--name=nvme_0 --filename=/dev/nvme0n1
>> 
>> 
>> 
>>*** iommu.passthrough=1 ***
>> 
>>READ: io=25301MB, aggrb=2528.3MB/s, minb=2528.3MB/s,
>>maxb=2528.3MB/s, mint=10007msec, maxt=10007msec
>> 
>> 
>> 
>>*** iommu.passthrough=0 ***
>> 
>>READ: io=22657MB, aggrb=2265.5MB/s, minb=2265.5MB/s,
>>maxb=2265.5MB/s, mint=10001msec, maxt=10001msec
>> 
>> 
>> 
>>Hopefully this helps. Let me know if you have any more
>>questions.
>> 
>>-Nate
>> 
>> 
>> 
>>From: Manoj Iyer [mailto:manoj.i...@canonical.com]
>>Sent: Thursday, May 4, 2017 4:55 PM
>>To: Nate Watterson 
>>Cc: Timur Tabi 
>>Subject: RE: how to test iommu.passthough=0/1 ??
>> 
>> 
>> 
>>Nate,
>> 
>> 
>> 
>>  I am attaching fio output for the CAF kernel that is available in 
>> the
>>  centriq PPA. The results are not that much different. This time I 
>> ran
>>  fio on the loop back disk and also on the mmcblk0 SD card.
>> 
>> 
>> 
>>  Please see the attached test report.
>> 
>> 
>> 
>>  Thanks
>> 
>>  Manoj Iyer
>> 
>>  On Thu, May 4, 2017 at 2:46 PM, Manoj Iyer 
>> 
>>  wrote:
>> 
>>I have attached the boot log from the system with
>>iommu.passthrough=1.
>> 
>> 
>> 
>>  Also I ran iperf on the mlx card interface.. and again the
>>  results don't make sense. I was expecting see better numbers
>>  with iommu.passthrough=1. Please see the attached test data for
>>  UDP and TCP.
>> 
>> 
>> 
>>  Figuring out wh

[Kernel-packages] [Bug 1687267] Re: kernel BUG at /build/linux-2NWldV/linux-4.10.0/include/linux/swapops.h:129!

[Tim Passingham]

Is this a duplicate of #1674838, or different?

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

Title:
  kernel BUG at /build/linux-
  2NWldV/linux-4.10.0/include/linux/swapops.h:129!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  First traceback looks to be the cause.  The second traceback is the
  effect that followed (repeatedly).

  Don't think it's specific to system76.

  
  Apr 30 09:56:10 galago kernel: [97085.090114] [ cut here 
]
  Apr 30 09:56:10 galago kernel: [97085.090137] kernel BUG at 
/build/linux-2NWldV/linux-4.10.0/include/linux/swapops.h:129!
  Apr 30 09:56:10 galago kernel: [97085.090157] invalid opcode:  [#1] SMP
  Apr 30 09:56:10 galago kernel: [97085.090167] Modules linked in: 
nls_iso8859_1 uas usb_storage ccm rfcomm 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 xt_conntrack nf_nat nf_conntrack libcrc32c 
br_netfilter bridge stp llc aufs ec_sys cmac bnep arc4 intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm 
irqbypass crct10dif_pclmul crc32_pclmul snd_hda_codec_via ghash_clmulni_intel 
snd_hda_codec_generic pcbc snd_hda_intel snd_hda_codec iwlmvm snd_hda_core 
snd_hwdep aesni_intel snd_pcm uvcvideo mac80211 aes_x86_64 snd_seq_midi 
videobuf2_vmalloc crypto_simd snd_seq_midi_event glue_helper videobuf2_memops 
cryptd videobuf2_v4l2 btusb snd_rawmidi videobuf2_core btrtl snd_seq btbcm 
intel_cstate videodev btintel
  Apr 30 09:56:10 galago kernel: [97085.090334]  bluetooth snd_seq_device media 
intel_rapl_perf iwlwifi snd_timer joydev input_leds cfg80211 rtsx_pci_ms snd 
memstick mei_me soundcore mei lpc_ich shpchp serio_raw tpm_infineon mac_hid 
binfmt_misc cuse parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs 
xor raid6_pq dm_mirror dm_region_hash dm_log i915 rtsx_pci_sdmmc i2c_algo_bit 
drm_kms_helper psmouse e1000e syscopyarea sysfillrect ahci sysimgblt 
fb_sys_fops libahci drm ptp rtsx_pci pps_core wmi fjes video
  Apr 30 09:56:10 galago kernel: [97085.090439] CPU: 0 PID: 3534 Comm: JS 
Helper Not tainted 4.10.0-20-generic #22-Ubuntu
  Apr 30 09:56:10 galago kernel: [97085.090457] Hardware name: System76, Inc. 
Galago UltraPro/W740SU  , BIOS 4.6.5 12/12/2013
  Apr 30 09:56:10 galago kernel: [97085.090481] task: 9003eb142d00 
task.stack: a0fb83c34000
  Apr 30 09:56:10 galago kernel: [97085.090499] RIP: 
0010:__migration_entry_wait+0x16a/0x180
  Apr 30 09:56:10 galago kernel: [97085.090512] RSP: :a0fb83c37d68 
EFLAGS: 00010246
  Apr 30 09:56:10 galago kernel: [97085.090525] RAX: 000fc0048078 RBX: 
faefcf1c69f0 RCX: faefcf1c69f0
  Apr 30 09:56:10 galago kernel: [97085.090542] RDX: 0001 RSI: 
9003c71a7800 RDI: faefc2f44000
  Apr 30 09:56:10 galago kernel: [97085.090559] RBP: a0fb83c37d80 R08: 
9003ebb38000 R09: 9003ebb38000
  Apr 30 09:56:10 galago kernel: [97085.090576] R10: 7fc0379000c8 R11: 
0206 R12: faefc2f44000
  Apr 30 09:56:10 galago kernel: [97085.090592] R13: 3e0bd100 R14: 
a0fb83c37e30 R15: 9003d0b80898
  Apr 30 09:56:10 galago kernel: [97085.090609] FS:  7fc01b3fa700() 
GS:90041fa0() knlGS:
  Apr 30 09:56:10 galago kernel: [97085.090628] CS:  0010 DS:  ES:  
CR0: 80050033
  Apr 30 09:56:10 galago kernel: [97085.090642] CR2: 7fc004700018 CR3: 
0003c70f9000 CR4: 001406f0
  Apr 30 09:56:10 galago kernel: [97085.090658] Call Trace:
  Apr 30 09:56:10 galago kernel: [97085.090667]  migration_entry_wait+0x74/0x80
  Apr 30 09:56:10 galago kernel: [97085.090680]  do_swap_page+0x5b3/0x770
  Apr 30 09:56:10 galago kernel: [97085.090691]  handle_mm_fault+0x873/0x1360
  Apr 30 09:56:10 galago kernel: [97085.090703]  __do_page_fault+0x23e/0x4e0
  Apr 30 09:56:10 galago kernel: [97085.090715]  do_page_fault+0x22/0x30
  Apr 30 09:56:10 galago kernel: [97085.090726]  page_fault+0x28/0x30
  Apr 30 09:56:10 galago kernel: [97085.090735] RIP: 0033:0x56520e6072b4
  Apr 30 09:56:10 galago kernel: [97085.090744] RSP: 002b:7fc01b3f9c40 
EFLAGS: 00010203
  Apr 30 09:56:10 galago kernel: [97085.090757] RAX:  RBX: 
7fc037900040 RCX: 7fc037b7b137
  Apr 30 09:56:10 galago kernel: [97085.090774] RDX: 0008 RSI: 
2000 RDI: 7fc0047ba000
  Apr 30 09:56:10 galago kernel: [97085.090790] RBP: 7fc00470 R08: 
7fc0379000c8 R09: 
  Apr 30 09:56:10 galago kernel: [97085.090807] R10: 7fc0379000c8 R11: 
0206 R12: 0080
  Apr 30 09:56:10 galago kernel: [97085.090824] R13: 7fc0379000c8 R14: 
00b9 R15: 0002
  Apr 30 09:56:10 galago kernel: [97085.090840] Code: ff ff ff 4c 89 e7 e8 96

[Kernel-packages] [Bug 1667531] Re: [Hyper-V] Include bondvf in /usr/sbin for SR-IOV interface bonding

[Joshua R. Poulson]

We did test this specific scenario in our combined testing. We are
telling preview customers to download this script manually right now and
I'm being asked for an ETA for when this will start appearing on images.

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

Title:
  [Hyper-V] Include bondvf in /usr/sbin for SR-IOV interface bonding

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

Bug description:
  Please include bondvf.sh from kernel git tools/hv/ in /usr/sbin

  commit fd7aabb062fa1a8331a786d617744de220eaf002
  Author: Haiyang Zhang 
  Date:   Fri Dec 2 15:55:38 2016 -0800

  tools: hv: Enable network manager for bonding scripts on RHEL

  We found network manager is necessary on RHEL to make the synthetic
  NIC, VF NIC bonding operations handled automatically. So, enabling
  network manager here.

  Signed-off-by: Haiyang Zhang 
  Reviewed-by: K. Y. Srinivasan 
  Signed-off-by: David S. Miller 

  commit 178cd55f086629cf0bad9c66c793a7e2bcc3abb6
  Author: Haiyang Zhang 
  Date:   Mon Jul 11 17:06:42 2016 -0700

  tools: hv: Add a script to help bonding synthetic and VF NICs

  This script helps to create bonding network devices based on synthetic NIC
  (the virtual network adapter usually provided by Hyper-V) and the matching
  VF NIC (SRIOV virtual function). So the synthetic NIC and VF NIC can
  function as one network device, and fail over to the synthetic NIC if VF 
is
  down.

  Mayjor distros (RHEL, Ubuntu, SLES) supported by Hyper-V are supported by
  this script.

  Signed-off-by: Haiyang Zhang 
  Reviewed-by: K. Y. Srinivasan 
  Signed-off-by: David S. Miller 

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

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

[Kernel-packages] [Bug 1689818] Re: What is the command to enable earlycon?

[Manoj Iyer]

On Wed, May 10, 2017 at 9:15 AM, Timur Tabi  
wrote:
> You need all four patches.  The last one is in the tty-next tree:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next&id=5a0722b898f851b9ef108ea7babc529e4efc773d

Thanks will cherry pick from there.

> 
> From: Manoj Iyer 
> Date: Wednesday, May 10, 2017 at 9:02 AM
> To: Timur Tabi 
> Cc: Manoj Iyer <1689...@bugs.launchpad.net>
> Subject: Re: What is the command to enable earlycon?
> 
> 
> 
> On Wed, May 10, 2017 at 8:42 AM, Timur Tabi  
> wrote:
>> You need these patches:
>> 
>>tty: pl011: Work around QDF2400 E44 stuck BUSY bit (4.10)
>>tty: acpi/spcr: QDF2400 E44 checks for wrong OEM revision (4.11)
>>tty: pl011: fix earlycon work-around for QDF2400 erratum 44 (4.11)
> 
> These are in linus's tree or  linux-next
>>tty: pl011: use "qdf2400_e44" as the earlycon name for QDF2400 
>> E44 (4.12)
> 
> But this one is not in linux-next yet.
> 
>> and then it's one of these two:
>> 
>> earlycon=qdf2400_e44,0xff78ed1000 (UART)
>> earlycon=qdf2400_e44,0xff78ef1000 (SOL)
>> 
>> Or you can just do "earlycon" without anything after that, but that 
>> triggers after the ACPI tables have been parsed.
>> 
>> From: Manoj Iyer 
>> Date: Wednesday, May 10, 2017 at 8:30 AM
>> To: Timur Tabi 
>> Subject: What is the command to enable earlycon?
>> 
>> Timur,
>> 
>> What is the kernel parameter to enable earlycon? I know it changed 
>> for AW and we have never used it . I need it to test 
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689818
>> 
>> Thanks
>> Manoj Iyer

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

Title:
  tty: pl011: fix earlycon work-around for QDF2400 erratum 44

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  The work-around for the Qualcomm Datacenter Technologies QDF2400 erratum 44 
sets the qdf2400_e44_present" global variable if the work-around is needed. 
However, this check does not happen until after earlycon is initialized, which 
means the work-around is not used, and the console hangs as soon as it displays 
one character.

  [Test Case]
  Enable earlycon and boot the kernel.

  [Regression Potential]
  This impacts only Qualcomm Datacenter Technologies QDF2400 platforms.

  [Fix]
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e53e597fd4c4a0b6ae58e57d76a240927fd17eaa

  https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h
  =tty-testing&id=5a0722b898f851b9ef108ea7babc529e4efc773d

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

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

[Kernel-packages] [Bug 1677297] Re: [Zesty] d-i: replace msm_emac with qcom_emac

[Manoj Iyer]

** Tags added: qdf2400

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

Title:
  [Zesty] d-i: replace msm_emac with qcom_emac

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  We landed a patch to support msm_emac module in initrd for amberwing 
platforms. But the upstream driver has since been renamed to qcom_emac. This 
module is needed in d-i's initrd so that these nics can be used to d-i install 
the system. The driver already exists in the zesty kernel under 
drivers/net/ethernet/qualcomm/emac/

  Revert commit 14893d91c9c391f8a4c2668b96ffe60aa728ad23 and add
  qcom_emac to initrd, and change the module name to qcom_emac.

  [Test Case]
  D-I install zesty on amberwing platform and notice that DI does not recognize 
the onboard two port nic.

  [Regression Potential]
  At present this driver applies only to amberwing systems, any regression will 
be isolated to amberwing platforms. The over all risk of regression is low.

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

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

[Kernel-packages] [Bug 1680549] Re: [Zesty] QDF2400 ARM64 server - NMI watchdog: BUG: soft lockup - CPU#8 stuck for 22s!

[Manoj Iyer]

** Tags added: qdf2400

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

Title:
  [Zesty] QDF2400 ARM64 server - NMI watchdog: BUG: soft lockup - CPU#8
  stuck for 22s!

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  New

Bug description:
  [IMPACT]
  Booting Zesty 4.10 kernel on Qualcomm Centriq 2400 ARM64 servers causes soft 
lockups on multiple CPUs.

  [  104.205397] Modules linked in: nls_iso8859_1 cdc_acm bridge stp llc
  ipmi_ssif ipmi_devintf ipmi_msghandler shpchp hdma hdma_mgmt i2c_qup
  cppc_cpufreq ib_iser rdma_cm iw_cm ib_cm ib_core configfs iscsi_tcp
  libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10
  raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor
  raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage at803x
  aes_ce_blk aes_ce_cipher crc32_ce crct10dif_ce ghash_ce sha2_ce
  sha1_ce mlx5_core devlink ptp pps_core ahci_platform libahci_platform
  libahci qcom_emac sdhci_acpi sdhci xhci_plat_hcd pinctrl_qdf2xxx fjes
  aes_neon_blk crypto_simd cryptd

  [  104.205442] CPU: 47 PID: 0 Comm: swapper/47 Tainted: G L  
4.10.0-16-generic #18ubuntuRC03+.1
  [  104.205443] Hardware name: Qualcomm QDF2400 DP/ABW|SYS|CVR,1DPC|V3 
  , BIOS XBL.DF.2.0.R3-00153 QDF2400_REL CRM 02/ 8/2017
  [  104.205444] task: 9fa30ed49c00 task.stack: 9fa30ed5c000
  [  104.205447] PC is at _raw_spin_unlock_irqrestore+0x2c/0x38
  [  104.205450] LR is at alloc_iova+0x1cc/0x2a0
  [  104.205451] pc : [] lr : [] pstate: 
20400145
  [  104.205452] sp : 9fa31fbecc00
  [  104.205453] x29: 9fa31fbecc00 x28: 000efe46
  [  104.205455] x27: 0040 x26: 000f
  [  104.205458] x25: 3f06251f8000 x24: 0001
  [  104.205460] x23: 9fa30da06008 x22: 
  [  104.205462] x21: 9fa2e2af8740 x20: 9fa30da06008
  [  104.205464] x19: 0140 x18: a5e112c1
  [  104.205466] x17: 4d48a1ed x16: b0f9c455
  [  104.205468] x15: aa4269e9 x14: 85094ac4
  [  104.205471] x13: 9b3b00da x12: 8aae8d9c
  [  104.205473] x11: 9fa31fbf90b0 x10: 3f0624eb70eb
  [  104.205475] x9 :  x8 : 0004
  [  104.205477] x7 : 9fa2e2875400 x6 : 
  [  104.205479] x5 : 9fa2e2875401 x4 : 
  [  104.205481] x3 : 9fa2e2a27b00 x2 : 9fa2e2875400
  [  104.205483] x1 : 0140 x0 : f7c2

  [  111.198062] INFO: rcu_sched self-detected stall on CPU
  [  111.198971] INFO: rcu_sched detected stalls on CPUs/tasks:
  [  111.198977]31-...: (1 GPs behind) idle=1b3/2/0 softirq=432/433 
fqs=6805
  [  111.198979]32-...: (1 GPs behind) idle=291/1/0 softirq=469/470 
fqs=6805
  [  111.198980](detected by 2, t=15002 jiffies, g=143, c=142, q=6968)
  [  111.199000] Task dump for CPU 31:
  [  111.199002] swapper/31  R  running task0 0  1 
0x0002
  [  111.199006] Call trace:
  [  111.199012] [] __switch_to+0x98/0xb0
  [  111.199014] [<000b7160dcd2>] 0xb7160dcd2
  [  111.199015] Task dump for CPU 32:
  [  111.199016] swapper/32  R  running task0 0  1 
0x0002
  [  111.199018] Call trace:
  [  111.199019] [] __switch_to+0x98/0xb0
  [  111.199020] [<000bcde2fa4e>] 0xbcde2fa4e
  [  111.227703]31-...: (1 GPs behind) idle=1b3/2/0 softirq=432/433 
fqs=6809
  [  111.234558] (t=15010 jiffies g=143 c=142 q=6968)
  [  111.239334] Task dump for CPU 31:
  [  111.239335] swapper/31  R  running task0 0  1 
0x0002
  [  111.239338] Call trace:
  [  111.239344] [] dump_backtrace+0x0/0x2b0
  [  111.239346] [] show_stack+0x24/0x30
  [  111.239350] [] sched_show_task+0x128/0x178
  [  111.239352] [] dump_cpu_task+0x48/0x58
  [  111.239356] [] rcu_dump_cpu_stacks+0xbc/0xf0
  [  111.239359] [] rcu_check_callbacks+0x7a8/0x968
  [  111.239362] [] update_process_times+0x34/0x60
  [  111.239365] [] tick_sched_handle.isra.7+0x38/0x70
  [  111.239367] [] tick_sched_timer+0x4c/0x98
  [  111.239369] [] __hrtimer_run_queues+0xe8/0x2e8
  [  111.239371] [] hrtimer_interrupt+0xa8/0x228
  [  111.239376] [] arch_timer_handler_phys+0x3c/0x50
  [  111.239379] [] handle_percpu_devid_irq+0x8c/0x230
  [  111.239383] [] generic_handle_irq+0x34/0x50
  [  111.239385] [] __handle_domain_irq+0x68/0xc0
  [  111.239386] [] gic_handle_irq+0xc4/0x170
  [  111.239388] Exception stack(0x9fa31fa7caa0 to 0x9fa31fa7cbd0)
  [  111.239390] caa0: 9fa31fa7cad0 0001 9fa31fa7cc00 
3f0624a00974
  [  111.239392] cac0: 20400145 0001 00fe 
0140
  [  111.239394] cae0: 9fa2e10b1c00 9fa2e11c8800  
9fa2e10b1c01
  [  111.239396] cb00:  9fa2e10b1c00 9fa3035ee681 

[Kernel-packages] [Bug 1688158] Re: [SRU][Zesty] Support SMMU passthrough using the default domain

[Manoj Iyer]

** Tags added: qdf2400

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

Title:
  [SRU][Zesty] Support SMMU passthrough using the default domain

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Have the SMMU come up in a passthrough configuration, and then allow 
subsequent translation for things such as VFIO. Rather than do this in each 
SMMU driver, it's much cleaner to allow the default domain to be configured to 
be something other than DMA.

  This patch series implements a command-line option to configure the
  default domain type. Currently, it supports "dma" and "identity" which
  is sufficient for the passthrough use-case.

  [Fix]
  The following patch series in linux-next adds this support to the kernel.
  4a8d8a14c0d0 arm64: dma-mapping: Only swizzle DMA ops for IOMMU_DOMAIN_DMA
  fccb4e3b8ab0 iommu: Allow default domain type to be set on the kernel command 
line
  beb3c6a066bf iommu/arm-smmu-v3: Install bypass STEs for IOMMU_DOMAIN_IDENTITY 
domains
  67560edcd8e5 iommu/arm-smmu-v3: Make arm_smmu_install_ste_for_dev return void
  61bc671179f1 iommu/arm-smmu: Install bypass S2CRs for IOMMU_DOMAIN_IDENTITY 
domains
  0834cc28fa56 iommu/arm-smmu: Restrict domain attributes to UNMANAGED domains

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

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

[Kernel-packages] [Bug 1689818] Re: tty: pl011: fix earlycon work-around for QDF2400 erratum 44

[Manoj Iyer]

** Tags added: qdf2400

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

Title:
  tty: pl011: fix earlycon work-around for QDF2400 erratum 44

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  The work-around for the Qualcomm Datacenter Technologies QDF2400 erratum 44 
sets the qdf2400_e44_present" global variable if the work-around is needed. 
However, this check does not happen until after earlycon is initialized, which 
means the work-around is not used, and the console hangs as soon as it displays 
one character.

  [Test Case]
  Enable earlycon and boot the kernel.

  [Regression Potential]
  This impacts only Qualcomm Datacenter Technologies QDF2400 platforms.

  [Fix]
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e53e597fd4c4a0b6ae58e57d76a240927fd17eaa

  https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h
  =tty-testing&id=5a0722b898f851b9ef108ea7babc529e4efc773d

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

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

[Kernel-packages] [Bug 1684010] Re: 17.04, i915 freeze on VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller

[Jonas Slivka]

Got freeze on -9 as well:

➜  ~ uname -a
Linux dell 4.10.0-9-generic #11-Ubuntu SMP Mon Feb 20 13:47:35 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux

Attaching a portion of kern.log with call trace.

** Attachment added: "Output of kern.log during the freeze"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684010/+attachment/4874698/+files/kern_ubuntu_17.04_x64_vmlinuz-4.10.0-9-generic.log

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

Title:
  17.04, i915 freeze on VGA compatible controller: Intel Corporation
  Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Just freezes all unity and/or X.
  Nothing in any logs though.

  16.10 worked just fine.

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

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

[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive

[Jan Drewes]

I too have experienced this issue (Dell Precision 5510, Samsung PM951
512GB). I am now running the Kernel from Kai-Heng Feng (Posting #61)
since about 4.5h with no troubles. I'll let the machine run downloads
through the night, if it crashes I will report back. For now the fix
seems to work.

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

Title:
  APST quirk needed for Samsung 512GB NVMe drive

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

Bug description:
  APST support just landed in the latest Zesty kernel (4.10.0-14.16) as
  part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602.
  That patch has a quirk for certain 256GB Samsung drives found in Dell
  laptops that do not behave well when APST is enabled. I am
  experiencing the same symptoms with the same model laptop except with
  a 512GB Samsung. Prior to manually disabling APST the drive would die
  and system would go down in flames with I/O errors within 20 to 40
  minutes of boot.

  $ sudo nvme list
  Node SN   Model   
 Namespace Usage  Format   FW Rev  
    
 - -- 
 
  /dev/nvme0n1   ** PM951 NVMe SAMSUNG 512GB
 1 500.20  GB / 512.11  GB512   B +  0 B   BXV76D0Q

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ajclayton   3305 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri Mar 31 09:42:38 2017
  InstallationDate: Installed on 2012-09-08 (1665 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic 
root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt 
nouveau.modeset=0 log_buf_len=20M
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  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.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1687267] Re: kernel BUG at /build/linux-2NWldV/linux-4.10.0/include/linux/swapops.h:129!

[Tim Passingham]

This affects one of my xubuntu systems as well.  Is there any simple way
round it for now?  An earlier or later kernel?

May 10 15:09:44 ChrisP kernel: [ 7353.196114] kernel BUG at 
/build/linux-2NWldV/linux-4.10.0/include/linux/swapops.h:129!
May 10 15:09:44 ChrisP kernel: [ 7353.196153] invalid opcode:  [#1] SMP
May 10 15:09:44 ChrisP kernel: [ 7353.196172] Modules linked in: 
talpa_vfshook(OE) talpa_pedconnector(OE) talpa_pedevice(OE) talpa_vcdevice(OE) 
talpa_core(OE) talpa_linux(OE) talpa_syscallhook(OE) binfmt_misc joydev 
input_leds gpio_ich dcdbas dell_smm_hwmon snd_hda_codec_conexant snd_seq_midi 
snd_hda_codec_generic snd_seq_midi_event intel_rapl snd_hda_codec_hdmi 
x86_pkg_temp_thermal snd_rawmidi intel_powerclamp coretemp snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep kvm_intel snd_pcm kvm irqbypass 
crct10dif_pclmul snd_seq crc32_pclmul ghash_clmulni_intel cryptd snd_seq_device 
intel_cstate snd_timer intel_rapl_perf serio_raw snd mei_me shpchp lpc_ich 
soundcore mei mac_hid ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt 
nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 xt_limit xt_tcpudp 
xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4
May 10 15:09:44 ChrisP kernel: [ 7353.196515]  xt_conntrack sunrpc 
ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp nf_nat libcrc32c nf_conntrack_ftp nf_conntrack iptable_filter 
parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_logitech_hidpp 
amdkfd amd_iommu_v2 hid_logitech_dj radeon psmouse i2c_algo_bit ttm 
drm_kms_helper ums_realtek usbhid syscopyarea uas sysfillrect sysimgblt hid 
usb_storage fb_sys_fops r8169 drm pata_acpi mii fjes
May 10 15:09:44 ChrisP kernel: [ 7353.196712] CPU: 2 PID: 2842 Comm: JS Helper 
Tainted: G   OE   4.10.0-20-generic #22-Ubuntu
May 10 15:09:44 ChrisP kernel: [ 7353.196753] Hardware name: Dell Inc. Inspiron 
620s/0GDG8Y   , BIOS A02 07/27/2011
May 10 15:09:44 ChrisP kernel: [ 7353.196790] task: 9a19a68e9680 
task.stack: b11882dac000
May 10 15:09:44 ChrisP kernel: [ 7353.196823] RIP: 
0010:__migration_entry_wait+0x16a/0x180
May 10 15:09:44 ChrisP kernel: [ 7353.196849] RSP: :b11882dafd68 
EFLAGS: 00010246
May 10 15:09:44 ChrisP kernel: [ 7353.196874] RAX: 000fc0048078 RBX: 
f2bd82d597b0 RCX: f2bd82d597b0
May 10 15:09:44 ChrisP kernel: [ 7353.196908] RDX: 0001 RSI: 
9a19b565e800 RDI: f2bd81b04000
May 10 15:09:44 ChrisP kernel: [ 7353.196941] RBP: b11882dafd80 R08: 
9a1a31117440 R09: 9a1a31117440
May 10 15:09:44 ChrisP kernel: [ 7353.196974] R10: 7f70c71000c8 R11: 
0206 R12: f2bd81b04000
May 10 15:09:44 ChrisP kernel: [ 7353.197007] R13: 3e06c100 R14: 
b11882dafe30 R15: 9a19a07300c8
May 10 15:09:44 ChrisP kernel: [ 7353.197041] FS:  7f70b3ffa700() 
GS:9a1a3f50() knlGS:
May 10 15:09:44 ChrisP kernel: [ 7353.197079] CS:  0010 DS:  ES:  CR0: 
80050033
May 10 15:09:44 ChrisP kernel: [ 7353.197106] CR2: 7f70abd00018 CR3: 
b5757000 CR4: 000406e0
May 10 15:09:44 ChrisP kernel: [ 7353.197140] Call Trace:
May 10 15:09:44 ChrisP kernel: [ 7353.197155]  migration_entry_wait+0x74/0x80
May 10 15:09:44 ChrisP kernel: [ 7353.197178]  do_swap_page+0x5b3/0x770
May 10 15:09:44 ChrisP kernel: [ 7353.197198]  handle_mm_fault+0x873/0x1360
May 10 15:09:44 ChrisP kernel: [ 7353.197221]  __do_page_fault+0x23e/0x4e0
May 10 15:09:44 ChrisP kernel: [ 7353.197242]  do_page_fault+0x22/0x30
May 10 15:09:44 ChrisP kernel: [ 7353.197262]  page_fault+0x28/0x30
May 10 15:09:44 ChrisP kernel: [ 7353.197279] RIP: 0033:0x55bc9423606c
May 10 15:09:44 ChrisP kernel: [ 7353.197299] RSP: 002b:7f70b3ff9c80 
EFLAGS: 00010207
May 10 15:09:44 ChrisP kernel: [ 7353.197325] RAX:  RBX: 
7f70c7100040 RCX: 7f70c734e137
May 10 15:09:44 ChrisP kernel: [ 7353.197358] RDX: 0008 RSI: 
1000 RDI: 7f70abdca000
May 10 15:09:44 ChrisP kernel: [ 7353.197391] RBP: 7f70abd0 R08: 
7f70c71000c8 R09: 
May 10 15:09:44 ChrisP kernel: [ 7353.197424] R10: 7f70c71000c8 R11: 
0206 R12: 0200
May 10 15:09:44 ChrisP kernel: [ 7353.197457] R13: 7f70c71000c8 R14: 
00c9 R15: 0001
May 10 15:09:44 ChrisP kernel: [ 7353.197491] Code: ff ff ff 4c 89 e7 e8 96 a2 
f8 ff e9 3c ff ff ff 85 d2 0f 84 2a ff ff ff 8d 4a 01 89 d0 f0 41 0f b1 4d 00 
39 d0 74 81 89 c2 eb e5 <0f> 0b 4c 89 e7 e8 0c fb f9 ff eb b8 4c 8d 60 ff 4c 8d 
68 1b eb 
May 10 15:09:44 ChrisP kernel: [ 7353.197606] RIP: 
__migration_entry_wait+0x16a/0x180 RSP: b11882dafd68
May 10 15:09:44 ChrisP kernel: [ 7353.209009] ---[

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

Title:
  kernel BUG at /build/linux-
  2NWldV/linux-4.10.0/include/linux/swapops.h:129!

St

[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

[Vidar Braut Haarr]

Will it be included in the next artful kernel, or only zesty? I ask
because the email subject says "[PATCH 0/4][Zesty SRU]".

And when will it be, roughly? 2 weeks? 3 months? Tomorrow?

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

Title:
  kernel BUG at /build/linux-
  7LGLH_/linux-4.10.0/include/linux/swapops.h:129

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-edge package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux-hwe-edge source package in Zesty:
  In Progress

Bug description:
  Randomly, khugepaged process will take 100% CPU, and I can only
  restart the computer to recover it.

  Relevant dmesg attached (dmesg_crash.txt).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mathieu2221 F pulseaudio
   /dev/snd/pcmC1D0p:   mathieu2221 F...m pulseaudio
   /dev/snd/controlC1:  mathieu2221 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar 21 23:03:23 2017
  HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd
  InstallationDate: Installed on 2016-01-31 (415 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: LENOVO 20344
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1689818] Re: What is the command to enable earlycon?

[Manoj Iyer]

On Wed, May 10, 2017 at 8:42 AM, Timur Tabi  
wrote:
> You need these patches:
> 
>tty: pl011: Work around QDF2400 E44 stuck BUSY bit (4.10)
>tty: acpi/spcr: QDF2400 E44 checks for wrong OEM revision (4.11)
>tty: pl011: fix earlycon work-around for QDF2400 erratum 44 (4.11)

These are in linus's tree or  linux-next
> 
>tty: pl011: use "qdf2400_e44" as the earlycon name for QDF2400 E44 
> (4.12)

But this one is not in linux-next yet.

> and then it's one of these two:
> 
> earlycon=qdf2400_e44,0xff78ed1000 (UART)
> earlycon=qdf2400_e44,0xff78ef1000 (SOL)
> 
> Or you can just do "earlycon" without anything after that, but that 
> triggers after the ACPI tables have been parsed.
> 
> From: Manoj Iyer 
> Date: Wednesday, May 10, 2017 at 8:30 AM
> To: Timur Tabi 
> Subject: What is the command to enable earlycon?
> 
> Timur,
> 
> What is the kernel parameter to enable earlycon? I know it changed 
> for AW and we have never used it . I need it to test 
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689818
> 
> Thanks
> Manoj Iyer

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

Title:
  tty: pl011: fix earlycon work-around for QDF2400 erratum 44

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  The work-around for the Qualcomm Datacenter Technologies QDF2400 erratum 44 
sets the qdf2400_e44_present" global variable if the work-around is needed. 
However, this check does not happen until after earlycon is initialized, which 
means the work-around is not used, and the console hangs as soon as it displays 
one character.

  [Test Case]
  Enable earlycon and boot the kernel.

  [Regression Potential]
  This impacts only Qualcomm Datacenter Technologies QDF2400 platforms.

  [Fix]
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e53e597fd4c4a0b6ae58e57d76a240927fd17eaa

  https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h
  =tty-testing&id=5a0722b898f851b9ef108ea7babc529e4efc773d

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

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

[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe)

[Thiago Martins]

I'm also expecting this on Xenial ASAP!

I'm using OpenStack with OVN, and the OpenFlow rules does not work with
Kernel 4.4! And MTU does not work with 4.8!

Very bad situation...   :-(

Also expecting the fix for:

https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1685742

...in one shot!

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

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or
  4.8.0-49, xenial-hwe)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  In Progress
Status in linux-hwe source package in Yakkety:
  Confirmed
Status in linux-hwe-edge source package in Yakkety:
  Confirmed
Status in linux source package in Zesty:
  Fix Released
Status in linux-hwe source package in Zesty:
  Confirmed
Status in linux-hwe-edge source package in Zesty:
  Confirmed

Bug description:
  Since I upgraded the kernel from linux-image-4.8.0-46-generic to
  linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to
  change the MTU.

  It seems to be known bug already fixed:
  https://bugzilla.kernel.org/show_bug.cgi?id=194763

  # ip l sh eno49
  2: eno49:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh eno50
  3: eno50:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh bond0
  6: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l set mtu 9000 bond0
  RTNETLINK answers: Invalid argument

  root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog
  Apr  4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 
requested, hw max 1500

  # modinfo ixgbe
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.4.0-k
  license:GPL
  description:Intel(R) 10 Gigabit PCI Express Network Driver

  # modinfo bonding
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko
  author: Thomas Davis, tada...@lbl.gov and many others
  description:Ethernet Channel Bonding Driver, v3.7.1
  version:3.7.1

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

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

[Kernel-packages] [Bug 1686976] Re: linux: 4.8.0-52.55 -proposed tracker

[Taihsiang Ho]

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/yakkety/4.8.0-52.55
/yakkety-proposed-published.html

** Tags added: certification-testing-passed

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

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

Title:
  linux: 4.8.0-52.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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: 1686978
  derivatives: 1686979
  -- 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/1686976/+subscriptions

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

[Kernel-packages] [Bug 1689408] Re: System hang when utilising OpenGL 4.5 features

[Timo Aaltonen]

so file it upstream

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

Title:
  System hang when utilising OpenGL 4.5 features

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  I've found this to be easily reproducible via unigine's heaven
  benchmark, which uses tessellation and other features extensively.
  Simply creating a OpenGL 4.5 context will not trigger the hang, and
  you must explicitly request an OGL 4+ context as the default will only
  be 3.0.

  On a successful trigger, the screen may flicker on and off a few times
  and eventually hang completely on a black screen, there's no way to
  recover the system from this state bar a power cycle (ie hold the
  power button).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  paulh  1405 F pulseaudio
   /dev/snd/controlC0:  paulh  1405 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue May  9 09:14:09 2017
  InstallationDate: Installed on 2017-01-05 (123 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  MachineType: HP HP Notebook
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=a5482167-6676-4a1a-b150-a86255560de6 ro rhgb quiet 
resume=/dev/sda6/swapfile resume_offset=7673856 quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (24 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1C
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8133
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 98.0E
  dmi.chassis.asset.tag: 5CG6124XBK
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1C:bd10/29/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8133:rvrKBCVersion98.0E:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

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

[Brad Figg]

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

apport-collect 1689818

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  tty: pl011: fix earlycon work-around for QDF2400 erratum 44

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  The work-around for the Qualcomm Datacenter Technologies QDF2400 erratum 44 
sets the qdf2400_e44_present" global variable if the work-around is needed. 
However, this check does not happen until after earlycon is initialized, which 
means the work-around is not used, and the console hangs as soon as it displays 
one character.

  [Test Case]
  Enable earlycon and boot the kernel.

  [Regression Potential]
  This impacts only Qualcomm Datacenter Technologies QDF2400 platforms.

  [Fix]
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e53e597fd4c4a0b6ae58e57d76a240927fd17eaa

  https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h
  =tty-testing&id=5a0722b898f851b9ef108ea7babc529e4efc773d

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

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

[Kernel-packages] [Bug 1689818] [NEW] tty: pl011: fix earlycon work-around for QDF2400 erratum 44

[Manoj Iyer]

Public bug reported:

[Impact]
The work-around for the Qualcomm Datacenter Technologies QDF2400 erratum 44 
sets the qdf2400_e44_present" global variable if the work-around is needed. 
However, this check does not happen until after earlycon is initialized, which 
means the work-around is not used, and the console hangs as soon as it displays 
one character.

[Test Case]
Enable earlycon and boot the kernel.

[Regression Potential]
This impacts only Qualcomm Datacenter Technologies QDF2400 platforms.

[Fix]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e53e597fd4c4a0b6ae58e57d76a240927fd17eaa

https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h
=tty-testing&id=5a0722b898f851b9ef108ea7babc529e4efc773d

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Manoj Iyer (manjo)
 Status: Incomplete

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

Title:
  tty: pl011: fix earlycon work-around for QDF2400 erratum 44

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  The work-around for the Qualcomm Datacenter Technologies QDF2400 erratum 44 
sets the qdf2400_e44_present" global variable if the work-around is needed. 
However, this check does not happen until after earlycon is initialized, which 
means the work-around is not used, and the console hangs as soon as it displays 
one character.

  [Test Case]
  Enable earlycon and boot the kernel.

  [Regression Potential]
  This impacts only Qualcomm Datacenter Technologies QDF2400 platforms.

  [Fix]
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e53e597fd4c4a0b6ae58e57d76a240927fd17eaa

  https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h
  =tty-testing&id=5a0722b898f851b9ef108ea7babc529e4efc773d

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

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

[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe)

[Michal Linuxak]

Any chance, that xenial will be fixed anytime soon? :-)

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

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or
  4.8.0-49, xenial-hwe)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  In Progress
Status in linux-hwe source package in Yakkety:
  Confirmed
Status in linux-hwe-edge source package in Yakkety:
  Confirmed
Status in linux source package in Zesty:
  Fix Released
Status in linux-hwe source package in Zesty:
  Confirmed
Status in linux-hwe-edge source package in Zesty:
  Confirmed

Bug description:
  Since I upgraded the kernel from linux-image-4.8.0-46-generic to
  linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to
  change the MTU.

  It seems to be known bug already fixed:
  https://bugzilla.kernel.org/show_bug.cgi?id=194763

  # ip l sh eno49
  2: eno49:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh eno50
  3: eno50:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh bond0
  6: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l set mtu 9000 bond0
  RTNETLINK answers: Invalid argument

  root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog
  Apr  4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 
requested, hw max 1500

  # modinfo ixgbe
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.4.0-k
  license:GPL
  description:Intel(R) 10 Gigabit PCI Express Network Driver

  # modinfo bonding
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko
  author: Thomas Davis, tada...@lbl.gov and many others
  description:Ethernet Channel Bonding Driver, v3.7.1
  version:3.7.1

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

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

[Kernel-packages] [Bug 1686687] Re: fstrim destroying XFS on SAN

[Anonymous]

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

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

Title:
  fstrim destroying XFS on SAN

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We observed severe data loss/filesystem corruption when executing
  fstrim on a filesystem hosted on an Eternus DX600 S3 system.

  There is multipathing via a fibre channel fabrics but the issue could
  be reproduced when disabling multipathing and using one of the block
  devices directly.

  It could not be reproduced when creating a multipathing device via
  dmsetup with four paths pointing to four loop devices mapping the same
  file.

  The observed behavior is that XFS cannot read vital filesystem
  metadata as the underlying storage device returns blocks of 0x00. The
  blocks are discarded via UNMAP commands and since thin provisioning is
  used, the SAN deallocates them and returns 0x00 on subsequent reads.
  Invoking find yields error messages like "find: ./dir_16: Structure
  needs cleaning". In other tests, where more data had been written,
  files were accessible but checksums did no longer match.

  In consequence, the XFS filesystem is in an unusable state and has to
  be created freshly, equaling complete data loss. Trying to repair the
  filesystem had proven not to be worth it as backups were available and
  trust had already been compromised.

  The problem was discovered after installing a new storage server with
  ubuntu 16.04, intending to replace the current machine running 14.04.
  Every weekend, the test volumes were corrupted. Investigation pointed
  towards Sunday, 06:47, which is the time `cron.weekly` is run. The job
  file `/etc/cron.weekly/fstrim` seemed most likely, so `fstrim -a` was
  run manually after `mkfs.xfs` and the filesystem became damaged. The
  damage only became apparent after a `umount` `mount` cycle, when all
  buffers were flushed and data was re-read from the device.

  We now could use config management to install a cronjob that (every
  minute!) checks for /sbin/fstrim and renames it, if present. This
  would be extremely unsatisfactory as it is a brittle workaround. So
  for now, we are locked on ubuntu 14.04. Since util-linux is one of the
  most central packages, there is no way to not have fstrim or the
  cronjob on a ubuntu system.

  I have attached a script used to reproduce the bug reliably on our
  system and its log output, as well as excerpts from syslog and md5sum.

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

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

[Kernel-packages] [Bug 1689408] Re: System hang when utilising OpenGL 4.5 features

[Paul]

The default is ignored however if the game requires tessellation or
other 4+ features, which is pretty much every big game released in the
past few years...

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

Title:
  System hang when utilising OpenGL 4.5 features

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  I've found this to be easily reproducible via unigine's heaven
  benchmark, which uses tessellation and other features extensively.
  Simply creating a OpenGL 4.5 context will not trigger the hang, and
  you must explicitly request an OGL 4+ context as the default will only
  be 3.0.

  On a successful trigger, the screen may flicker on and off a few times
  and eventually hang completely on a black screen, there's no way to
  recover the system from this state bar a power cycle (ie hold the
  power button).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  paulh  1405 F pulseaudio
   /dev/snd/controlC0:  paulh  1405 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue May  9 09:14:09 2017
  InstallationDate: Installed on 2017-01-05 (123 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  MachineType: HP HP Notebook
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=a5482167-6676-4a1a-b150-a86255560de6 ro rhgb quiet 
resume=/dev/sda6/swapfile resume_offset=7673856 quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (24 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1C
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8133
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 98.0E
  dmi.chassis.asset.tag: 5CG6124XBK
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1C:bd10/29/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8133:rvrKBCVersion98.0E:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1686687] Re: fstrim destroying XFS on SAN

[Anonymous]

We did get around to do more testing and follow suggestions. The
filesystem corruption could be reproduced. The run was done bypassing
multipathing and using a single path directly.

OUTPUT reproduce.sh (tail):

+ fstrim -v /mnt/san
/mnt/san: 120 TiB (131939249291264 bytes) trimmed
+ umount -vvv /mnt/san
umount: /mnt/san unmounted
+ sync
+ mount -vvv
/dev/disk/by-path/pci-:02:00.0-fc-0x-lun-0 /mnt/san
mount: mount /dev/sde on /mnt/san failed: Structure needs cleaning
+ fail '3rd mount failed'
+ echo 'ERROR: 3rd mount failed'
ERROR: 3rd mount failed
+ exit 11

OUTPUT dmesg:

[13568.741492] XFS (sde): metadata I/O error: block 0x39fc70
("xfs_trans_read_buf_map") error 74 numblks 8 [13568.891639] XFS (sde): 
Metadata CRC error detected at
xfs_agi_read_verify+0x5e/0x110 [xfs], xfs_agi block 0x3a7c68 [13569.033899] 
XFS (sde): Unmount and run xfs_repair [13569.103826] XFS (sde): First 64 bytes 
of corrupted metadata buffer:
[13569.174222] 9107a8836000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 
[13569.314629] 9107a8836010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 
[13569.454924] 9107a8836020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 
[13569.595204] 9107a8836030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 



Since there is no fstab entry, mount options are determined by whatever
mechanism decides on defaults. In this case, mount reported the
following:

xfs (rw,relatime,attr2,inode64,noquota)

The kernel for this run:

$ uname -a
Linux xxx 4.11.0-041100rc8-generic #201704232131 SMP Mon Apr 24 01:32:55 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

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

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

Title:
  fstrim destroying XFS on SAN

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We observed severe data loss/filesystem corruption when executing
  fstrim on a filesystem hosted on an Eternus DX600 S3 system.

  There is multipathing via a fibre channel fabrics but the issue could
  be reproduced when disabling multipathing and using one of the block
  devices directly.

  It could not be reproduced when creating a multipathing device via
  dmsetup with four paths pointing to four loop devices mapping the same
  file.

  The observed behavior is that XFS cannot read vital filesystem
  metadata as the underlying storage device returns blocks of 0x00. The
  blocks are discarded via UNMAP commands and since thin provisioning is
  used, the SAN deallocates them and returns 0x00 on subsequent reads.
  Invoking find yields error messages like "find: ./dir_16: Structure
  needs cleaning". In other tests, where more data had been written,
  files were accessible but checksums did no longer match.

  In consequence, the XFS filesystem is in an unusable state and has to
  be created freshly, equaling complete data loss. Trying to repair the
  filesystem had proven not to be worth it as backups were available and
  trust had already been compromised.

  The problem was discovered after installing a new storage server with
  ubuntu 16.04, intending to replace the current machine running 14.04.
  Every weekend, the test volumes were corrupted. Investigation pointed
  towards Sunday, 06:47, which is the time `cron.weekly` is run. The job
  file `/etc/cron.weekly/fstrim` seemed most likely, so `fstrim -a` was
  run manually after `mkfs.xfs` and the filesystem became damaged. The
  damage only became apparent after a `umount` `mount` cycle, when all
  buffers were flushed and data was re-read from the device.

  We now could use config management to install a cronjob that (every
  minute!) checks for /sbin/fstrim and renames it, if present. This
  would be extremely unsatisfactory as it is a brittle workaround. So
  for now, we are locked on ubuntu 14.04. Since util-linux is one of the
  most central packages, there is no way to not have fstrim or the
  cronjob on a ubuntu system.

  I have attached a script used to reproduce the bug reliably on our
  system and its log output, as well as excerpts from syslog and md5sum.

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

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

[Kernel-packages] [Bug 1672819] Re: exec'ing a setuid binary from a threaded program sometimes fails to setuid

[John Lenton]

With the kernel from #16 I am no longer able to reproduce the issue, not
with the simplified reproducers described in this bug, nor with the
original (slower and more convoluted) snapd reproducer.

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

Title:
  exec'ing a setuid binary from a threaded program sometimes fails to
  setuid

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

Bug description:
  This can be reproduced with
  https://gist.github.com/chipaca/806c90d96c437444f27f45a83d00a813

  With that, and go 1.8, if you run “make” and then

  for i in `seq 99`; do ./a_go; done

  you'll see a variable number of ”GOT 1000” (or whatever your user id
  is). If you don't, add one or two more 9s on there.

  That's a simple go reproducer. You can also use “a_p” instead of
  “a_go” to see one that only uses pthreads. “a_c” is a C version that
  does *not* reproduce the issue.

  But it's not pthreads: if in a_go.go you comment out the “import "C"”,
  you'll still see the “GOT 1000” messages, in a static binary that uses
  no pthreads, just clone(2). You'll also see a bunch of warnings
  because it's not properly handling an EAGAIN from clone, but that's
  unrelated.

  If you pin the process to a single thread using taskset, you don't get
  the issue from a_go; a_p continues to reproduce the issue. In some
  virtualized environments we haven't been able to reproduce the issue
  either (e.g. some aws instances), but kvm works (you need -smp to see
  the issue from a_go).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   john   2354 F...m pulseaudio
   /dev/snd/controlC0:  john   2354 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Mar 14 17:17:23 2017
  HibernationDevice: RESUME=UUID=b9fd155b-dcbe-4337-ae77-6daa6569beaf
  InstallationDate: Installed on 2014-04-27 (1051 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Latitude E6510
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic 
root=/dev/mapper/ubuntu--vg-root ro enable_mtrr_cleanup mtrr_spare_reg_nr=8 
mtrr_gran_size=32M mtrr_chunk_size=32M quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  UpgradeStatus: Upgraded to xenial on 2015-06-18 (634 days ago)
  dmi.bios.date: 12/05/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/05/2013:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6510
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1689787] [NEW] Realtek Wifi card rtl8723be [10ec:b723] WiFi does not work with Xenial-4.8 and Yakkety

[Taihsiang Ho]

Public bug reported:

Install 16.04.2 or 16.10 on HP 245 G4 Notebook PC and its wifi RTL8723BE
PCIe Wireless Network Adapter [10ec:b723] does not work.

--

$ lspci -knn

05:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE 
PCIe Wireless Network Adapter [10ec:b723]
DeviceName:  
Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network 
Adapter [103c:804c]
Kernel driver in use: rtl8723be
Kernel modules: rtl8723be

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-52-generic 4.8.0-52.55
ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
Uname: Linux 4.8.0-52-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  ubuntu 1929 F pulseaudio
 /dev/snd/controlC0:  ubuntu 1929 F pulseaudio
Date: Wed May 10 06:17:41 2017
HibernationDevice: RESUME=UUID=f3e58c36-a649-4db0-afb8-19d4acc491c0
InstallationDate: Installed on 2017-05-05 (4 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: Hewlett-Packard Test product name
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-52-generic 
root=UUID=c1ee6ec3-1d6c-4bcc-92a2-b3996ef451a3 ro rootdelay=60 quiet splash 
initcall_debug net.ifnames=0 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-52-generic N/A
 linux-backports-modules-4.8.0-52-generic  N/A
 linux-firmware1.161.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/15/2015
dmi.bios.vendor: Insyde
dmi.bios.version: B.18
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 8133
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 98.0C
dmi.chassis.asset.tag: 75214P108U
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrB.18:bd07/15/2015:svnHewlett-Packard:pnTestproductname:pvrType1ProductConfigId:rvnHewlett-Packard:rn8133:rvrKBCVersion98.0C:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: Test product name
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug package-from-proposed taipei-lab yakkety

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

Title:
  Realtek Wifi card rtl8723be [10ec:b723] WiFi does not work with
  Xenial-4.8 and Yakkety

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Install 16.04.2 or 16.10 on HP 245 G4 Notebook PC and its wifi
  RTL8723BE PCIe Wireless Network Adapter [10ec:b723] does not work.

  --

  $ lspci -knn

  05:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE 
PCIe Wireless Network Adapter [10ec:b723]
  DeviceName:  
  Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network 
Adapter [103c:804c]
  Kernel driver in use: rtl8723be
  Kernel modules: rtl8723be

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-52-generic 4.8.0-52.55
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1929 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1929 F pulseaudio
  Date: Wed May 10 06:17:41 2017
  HibernationDevice: RESUME=UUID=f3e58c36-a649-4db0-afb8-19d4acc491c0
  InstallationDate: Installed on 2017-05-05 (4 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Hewlett-Packard Test product name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-52-generic 
root=UUID=c1ee6ec3-1d6c-4bcc-92a2-b3996ef451a3 ro rootdelay=60 quiet splash 
initcall_debug net.ifnames=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-52-generic N/A
   linux-backports-modules-4.8.0-52-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: B.18
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8133
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 98.0C
  dmi.chassis.asset.tag: 75214P108U
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrB.18:bd07/15/2015:svnHewlett-Packard:pnTestproductname:pvrType1ProductConfigId:rvnHewlett-Packard:rn8133:rvrKBCVersion98.0C:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dm

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

[Brad Figg]

This change was made by a bot.

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

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

Title:
  Realtek Wifi card rtl8723be [10ec:b723] WiFi does not work with
  Xenial-4.8 and Yakkety

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Install 16.04.2 or 16.10 on HP 245 G4 Notebook PC and its wifi
  RTL8723BE PCIe Wireless Network Adapter [10ec:b723] does not work.

  --

  $ lspci -knn

  05:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE 
PCIe Wireless Network Adapter [10ec:b723]
  DeviceName:  
  Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network 
Adapter [103c:804c]
  Kernel driver in use: rtl8723be
  Kernel modules: rtl8723be

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-52-generic 4.8.0-52.55
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1929 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1929 F pulseaudio
  Date: Wed May 10 06:17:41 2017
  HibernationDevice: RESUME=UUID=f3e58c36-a649-4db0-afb8-19d4acc491c0
  InstallationDate: Installed on 2017-05-05 (4 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Hewlett-Packard Test product name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-52-generic 
root=UUID=c1ee6ec3-1d6c-4bcc-92a2-b3996ef451a3 ro rootdelay=60 quiet splash 
initcall_debug net.ifnames=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-52-generic N/A
   linux-backports-modules-4.8.0-52-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: B.18
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8133
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 98.0C
  dmi.chassis.asset.tag: 75214P108U
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrB.18:bd07/15/2015:svnHewlett-Packard:pnTestproductname:pvrType1ProductConfigId:rvnHewlett-Packard:rn8133:rvrKBCVersion98.0C:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Test product name
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1626269] Re: Ubuntu 16.10: kdump is not working in 4.8 kernel.

[Louis Bouchard]

** Changed in: makedumpfile (Ubuntu Xenial)
 Assignee: Louis Bouchard (louis) => (unassigned)

** Changed in: makedumpfile (Ubuntu Trusty)
 Assignee: Louis Bouchard (louis) => (unassigned)

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

Title:
  Ubuntu 16.10: kdump is not working in 4.8 kernel.

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Trusty:
  Confirmed
Status in makedumpfile source package in Xenial:
  Fix Released
Status in makedumpfile source package in Yakkety:
  Fix Released

Bug description:
  [SRU justification]
  makedumpfile fails to execute if executed on a 4.8 kernel

  [Impact]
  Unable to generate compressed kernel dumps on those platform

  [Fix]
  Backport commits 2c21d4656e8d3c2af2b1e14809d076941ae69e96 and 
  0c9dd01d8ee2e4ec1821a11f5e174fdba56012b8.

  The second commit is required since, once the initial issue is fixed,
  it triggers a second issue fixed on Debian by https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=842019

  [Test Case]
  - Install kernel 4.8 along with the linux-crashdump metapackage
  - Reboot to enable kdump
  - Trigger a kernel panic with "echo c > /proc/sysrq-trigger"

  Without the patch, the following message will appear and makedumpfile
  will fail :

   get_mem_map: Can't distinguish the memory type.

  With the fix, makedumpfile completes correctly.

  [Regression]
  None expected. The modification keeps the initial structure when kernels 
before 4.8 are used.

  [Original description of the problem]

  == Comment: #0 - PAVITHRA R. PRAKASH - 2016-09-21 00:50:22 ==
  ---Problem Description---

  Ubuntu 16.10: kdump is not working in 4.8 kernel.

  ---Steps to Reproduce---

  1) apt-get install linux-crashdump
  2) increase crashdump size:
  sudo vim /etc/default/grub.d/kexec-tools.cfg

  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel
  =2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M"

  3) sudo update-grub ; reboot the machine
  4) sudo sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools
  5) kdump-config show
  6) echo "c" > /proc/sysrq-trigger

  Logs
  

  root@ubuntu:/home/ubuntu# uname -a
  Linux ubuntu 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  root@ubuntu:/home/ubuntu# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.8.0-11-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.8.0-11-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.8.0-11-generic 
root=UUID=7ea3831b-f4c3-4f69-8f77-79aefcda70e3 ro splash quiet irqpoll 
nr_cpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@ubuntu:/home/ubuntu# cd
  root@ubuntu:~# echo "c" > /proc/sysrq-trigger
  [   50.733424] sysrq: SysRq : Trigger a crash
  [   50.733437] Unable to handle kernel paging request for data at address 
0x
  [   50.733441] Faulting instruction address: 0xc05af3f4
  [   50.733444] Oops: Kernel access of bad area, sig: 11 [#1]
  [   50.733446] SMP NR_CPUS=2048 NUMA pSeries
  [   50.733450] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag pseries_rng sg 
rng_core binfmt_misc ghash_generic gf128mul vmx_crypto ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache sr_mod cdrom sd_mod bnx2x ibmvscsi 
ibmveth scsi_transport_srp ptp pps_core mdio libcrc32c crc32c_generic 
crc32c_vpmsum
  [   50.733477] CPU: 2 PID: 1517 Comm: bash Not tainted 4.8.0-11-generic 
#12-Ubuntu
  [   50.733480] task: c004f7906880 task.stack: c004f7898000
  [   50.733482] NIP: c05af3f4 LR: c05b04d8 CTR: 
c05af3c0
  [   50.733485] REGS: c004f789b990 TRAP: 0300   Not tainted  
(4.8.0-11-generic)
  [   50.733488] MSR: 80009033   CR: 28242422  
XER: 0001
  [   50.733496] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1
  GPR00: c05b04d8 c004f789bc10 c0f46700 0063
  GPR04: c005ef78a9b8 c005ef79f7d8 c0063fe82300 5970
  GPR08: 0007 0001  0001
  GPR12: c05af3c0 c7b31200  2200
  GPR16: 10170dc8 0100111c0538 10140f58 100c7570
  GPR20:  1017dd58 10153618 1017b608
  GPR24: 310b9624 0001 c0e9fd40 0004
  GPR28: c0ea0100 0063 c0e528e8 

[Kernel-packages] [Bug 1689777] Re: NFS lockd error

[Alexander]

Attached log includes the existing problem at rotation time. Then a
reboot was issued.

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

Title:
  NFS lockd error

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System:
  Description:  Ubuntu 14.04.5 LTS
  Release:  14.04
  Version signature: Ubuntu 4.4.0-75.96~14.04.1-generic 4.4.59

  Using NFS-common and NFS-kernel-server version 1:1.2.8-6ubuntu1.2
  before kernel update and after.

  After an update from linux-image-generic-lts-xenial:amd64 4.4.0.64.50 to 
version 4.4.0.75.62, our NFS server refuses any exclusive file locks after 
every night. Symptoms are that NFS clients cannot execute programs that use 
exclusive file locks (e.g. cradle), if using a UI like Ubuntu Desktop, the 
whole UI is stuck. However files can still be accessed and created via shell on 
a client through nfs.
  Following log is produced on a client that mounts nfs:

  May 10 00:46:23 irminen kernel: [2972685.514114] lockd: server 
pranger.uni-trier.de OK
  May 10 00:47:24 irminen kernel: [2972746.611297] lockd: server 
pranger.uni-trier.de not responding, still trying

  The nfs server produces following log:

  May  8 22:30:22 pranger kernel: [6267842.076551] Btrfs loaded
  May  9 04:16:02 pranger kernel: [6288582.711415] lockd: cannot monitor client
  May  9 04:17:02 pranger kernel: [6288642.871345] lockd: cannot monitor client
  May  9 04:18:03 pranger kernel: [6288703.031317] lockd: cannot monitor client
  May  9 04:19:03 pranger kernel: [6288763.191282] lockd: cannot monitor client
  May  9 04:20:03 pranger kernel: [6288823.351247] lockd: cannot monitor client
  May  9 04:21:03 pranger kernel: [623.511292] lockd: cannot monitor client
  May  9 04:22:03 pranger kernel: [6288943.671215] lockd: cannot monitor client
  May  9 04:23:03 pranger kernel: [6289003.831189] lockd: cannot monitor client

  Restarting the NFS Server does not resolve the issue, I had to reboot
  the server completely. After one day running the same problem appears
  again.

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

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

[Kernel-packages] [Bug 1689777] Re: NFS lockd error

[Alexander]

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689777/+attachment/4874565/+files/syslog

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

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

Title:
  NFS lockd error

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System:
  Description:  Ubuntu 14.04.5 LTS
  Release:  14.04
  Version signature: Ubuntu 4.4.0-75.96~14.04.1-generic 4.4.59

  Using NFS-common and NFS-kernel-server version 1:1.2.8-6ubuntu1.2
  before kernel update and after.

  After an update from linux-image-generic-lts-xenial:amd64 4.4.0.64.50 to 
version 4.4.0.75.62, our NFS server refuses any exclusive file locks after 
every night. Symptoms are that NFS clients cannot execute programs that use 
exclusive file locks (e.g. cradle), if using a UI like Ubuntu Desktop, the 
whole UI is stuck. However files can still be accessed and created via shell on 
a client through nfs.
  Following log is produced on a client that mounts nfs:

  May 10 00:46:23 irminen kernel: [2972685.514114] lockd: server 
pranger.uni-trier.de OK
  May 10 00:47:24 irminen kernel: [2972746.611297] lockd: server 
pranger.uni-trier.de not responding, still trying

  The nfs server produces following log:

  May  8 22:30:22 pranger kernel: [6267842.076551] Btrfs loaded
  May  9 04:16:02 pranger kernel: [6288582.711415] lockd: cannot monitor client
  May  9 04:17:02 pranger kernel: [6288642.871345] lockd: cannot monitor client
  May  9 04:18:03 pranger kernel: [6288703.031317] lockd: cannot monitor client
  May  9 04:19:03 pranger kernel: [6288763.191282] lockd: cannot monitor client
  May  9 04:20:03 pranger kernel: [6288823.351247] lockd: cannot monitor client
  May  9 04:21:03 pranger kernel: [623.511292] lockd: cannot monitor client
  May  9 04:22:03 pranger kernel: [6288943.671215] lockd: cannot monitor client
  May  9 04:23:03 pranger kernel: [6289003.831189] lockd: cannot monitor client

  Restarting the NFS Server does not resolve the issue, I had to reboot
  the server completely. After one day running the same problem appears
  again.

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

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

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

[Brad Figg]

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

apport-collect 1689777

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

** Tags added: trusty

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

Title:
  NFS lockd error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  System:
  Description:  Ubuntu 14.04.5 LTS
  Release:  14.04
  Version signature: Ubuntu 4.4.0-75.96~14.04.1-generic 4.4.59

  Using NFS-common and NFS-kernel-server version 1:1.2.8-6ubuntu1.2
  before kernel update and after.

  After an update from linux-image-generic-lts-xenial:amd64 4.4.0.64.50 to 
version 4.4.0.75.62, our NFS server refuses any exclusive file locks after 
every night. Symptoms are that NFS clients cannot execute programs that use 
exclusive file locks (e.g. cradle), if using a UI like Ubuntu Desktop, the 
whole UI is stuck. However files can still be accessed and created via shell on 
a client through nfs.
  Following log is produced on a client that mounts nfs:

  May 10 00:46:23 irminen kernel: [2972685.514114] lockd: server 
pranger.uni-trier.de OK
  May 10 00:47:24 irminen kernel: [2972746.611297] lockd: server 
pranger.uni-trier.de not responding, still trying

  The nfs server produces following log:

  May  8 22:30:22 pranger kernel: [6267842.076551] Btrfs loaded
  May  9 04:16:02 pranger kernel: [6288582.711415] lockd: cannot monitor client
  May  9 04:17:02 pranger kernel: [6288642.871345] lockd: cannot monitor client
  May  9 04:18:03 pranger kernel: [6288703.031317] lockd: cannot monitor client
  May  9 04:19:03 pranger kernel: [6288763.191282] lockd: cannot monitor client
  May  9 04:20:03 pranger kernel: [6288823.351247] lockd: cannot monitor client
  May  9 04:21:03 pranger kernel: [623.511292] lockd: cannot monitor client
  May  9 04:22:03 pranger kernel: [6288943.671215] lockd: cannot monitor client
  May  9 04:23:03 pranger kernel: [6289003.831189] lockd: cannot monitor client

  Restarting the NFS Server does not resolve the issue, I had to reboot
  the server completely. After one day running the same problem appears
  again.

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

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

[Kernel-packages] [Bug 1689777] [NEW] NFS lockd error

[Alexander]

Public bug reported:

System:
Description:Ubuntu 14.04.5 LTS
Release:14.04
Version signature: Ubuntu 4.4.0-75.96~14.04.1-generic 4.4.59

Using NFS-common and NFS-kernel-server version 1:1.2.8-6ubuntu1.2 before
kernel update and after.

After an update from linux-image-generic-lts-xenial:amd64 4.4.0.64.50 to 
version 4.4.0.75.62, our NFS server refuses any exclusive file locks after 
every night. Symptoms are that NFS clients cannot execute programs that use 
exclusive file locks (e.g. cradle), if using a UI like Ubuntu Desktop, the 
whole UI is stuck. However files can still be accessed and created via shell on 
a client through nfs.
Following log is produced on a client that mounts nfs:

May 10 00:46:23 irminen kernel: [2972685.514114] lockd: server 
pranger.uni-trier.de OK
May 10 00:47:24 irminen kernel: [2972746.611297] lockd: server 
pranger.uni-trier.de not responding, still trying

The nfs server produces following log:

May  8 22:30:22 pranger kernel: [6267842.076551] Btrfs loaded
May  9 04:16:02 pranger kernel: [6288582.711415] lockd: cannot monitor client
May  9 04:17:02 pranger kernel: [6288642.871345] lockd: cannot monitor client
May  9 04:18:03 pranger kernel: [6288703.031317] lockd: cannot monitor client
May  9 04:19:03 pranger kernel: [6288763.191282] lockd: cannot monitor client
May  9 04:20:03 pranger kernel: [6288823.351247] lockd: cannot monitor client
May  9 04:21:03 pranger kernel: [623.511292] lockd: cannot monitor client
May  9 04:22:03 pranger kernel: [6288943.671215] lockd: cannot monitor client
May  9 04:23:03 pranger kernel: [6289003.831189] lockd: cannot monitor client

Restarting the NFS Server does not resolve the issue, I had to reboot
the server completely. After one day running the same problem appears
again.

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

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

Title:
  NFS lockd error

Status in linux package in Ubuntu:
  New

Bug description:
  System:
  Description:  Ubuntu 14.04.5 LTS
  Release:  14.04
  Version signature: Ubuntu 4.4.0-75.96~14.04.1-generic 4.4.59

  Using NFS-common and NFS-kernel-server version 1:1.2.8-6ubuntu1.2
  before kernel update and after.

  After an update from linux-image-generic-lts-xenial:amd64 4.4.0.64.50 to 
version 4.4.0.75.62, our NFS server refuses any exclusive file locks after 
every night. Symptoms are that NFS clients cannot execute programs that use 
exclusive file locks (e.g. cradle), if using a UI like Ubuntu Desktop, the 
whole UI is stuck. However files can still be accessed and created via shell on 
a client through nfs.
  Following log is produced on a client that mounts nfs:

  May 10 00:46:23 irminen kernel: [2972685.514114] lockd: server 
pranger.uni-trier.de OK
  May 10 00:47:24 irminen kernel: [2972746.611297] lockd: server 
pranger.uni-trier.de not responding, still trying

  The nfs server produces following log:

  May  8 22:30:22 pranger kernel: [6267842.076551] Btrfs loaded
  May  9 04:16:02 pranger kernel: [6288582.711415] lockd: cannot monitor client
  May  9 04:17:02 pranger kernel: [6288642.871345] lockd: cannot monitor client
  May  9 04:18:03 pranger kernel: [6288703.031317] lockd: cannot monitor client
  May  9 04:19:03 pranger kernel: [6288763.191282] lockd: cannot monitor client
  May  9 04:20:03 pranger kernel: [6288823.351247] lockd: cannot monitor client
  May  9 04:21:03 pranger kernel: [623.511292] lockd: cannot monitor client
  May  9 04:22:03 pranger kernel: [6288943.671215] lockd: cannot monitor client
  May  9 04:23:03 pranger kernel: [6289003.831189] lockd: cannot monitor client

  Restarting the NFS Server does not resolve the issue, I had to reboot
  the server completely. After one day running the same problem appears
  again.

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

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

[Kernel-packages] [Bug 1683445] Re: E6430 brightness control not working

[Kai-Heng Feng]

** Branch linked: lp:~kaihengfeng/unity-settings-daemon/lp1683445

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

Title:
  E6430 brightness control not working

Status in Linux:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-settings-daemon source package in Zesty:
  In Progress
Status in unity-settings-daemon source package in Zesty:
  Triaged

Bug description:
  Impact
  --
  It looks like GNOME's brightness control simply used the first backlight 
device it saw instead of one currently in use. This meant that the brightness 
control would not work on some computers with multiple GPUs.

  Test Case
  -
  From Ubuntu GNOME 17.04 on a dual-GPU computer, install the update.
  Restart.
  Does the brightness control now work correctly?

  Regression Potential
  
  This looks like a minimal fix for this issue. It was accepted as part of 
gnome-settings-daemon 3.24.2 which all GNOME 3.24 distros  will be upgrading to.

  Original Bug Report
  ---
  The Dell E6430 with Nvidia Optimus enables in BIOS, using the Open Source 
Nouveau driver shows the brightness slider moving but does not affect the 
brightness.

  When using the kernel boot option acpi_backlight=vendor , the
  brightness control works.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2081 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Apr 17 20:00:56 2017
  HibernationDevice: RESUME=UUID=66528b53-0f42-4043-9ff8-da8f86036be6
  InstallationDate: Installed on 2017-04-10 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Latitude E6430
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=4e08c33d-f8cf-4159-a559-a0463d67b96c ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0H3MT5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd01/18/2016:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0H3MT5:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6430
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1542743] Re: Bluetooth: Patch file not found ar3k/AthrBT_0x00000200.dfu

[The Raf 90]

Sorry, previous post was UNRELATED to the bug, I changed the swap
partition location and my PC (strangely after to perfect reboots)
started looking for it elsewhere...

The .deb file has worked fine for me as well!

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

Title:
  Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Since some Versions of Linux Kernel and Ubuntu Releases this problem
  exists.

  I am now running ubuntu 16.04 prerelease and still have the same
  problem.

  Bluetooth does not work with the atheros device on  msi gt 72 2qd
  notebook.

  WORKAROUND FOR [0CF3:3004] DEVICE ONLY with kernel 4.4:

  sudo apt install dkms
  wget 
https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files/btusb-lp1542743-dkms_0.1_all.deb
  sudo dpkg -i btusb-lp1542743-dkms_0.1_all.deb

  FOR KERNEL 4.8 A WORKAROUND DKMS DEB IS

  https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files
  /btusb-lp1542743-dkms_0.2~4.8_all.deb

  dmesg | grep Bluetooth:
  [2.655360] Bluetooth: Core ver 2.21
  [2.655373] Bluetooth: HCI device and connection manager initialized
  [2.655377] Bluetooth: HCI socket layer initialized
  [2.655379] Bluetooth: L2CAP socket layer initialized
  [2.655385] Bluetooth: SCO socket layer initialized
  [6.612790] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [6.612794] Bluetooth: BNEP filters: protocol multicast
  [6.612798] Bluetooth: BNEP socket layer initialized
  [9.016880] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu
  [9.016882] Bluetooth: Loading patch file failed

  hwinfo | grep Bluetooth:
  <6>[6.612790] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    <6>[6.612794] Bluetooth: BNEP filters: protocol multicast
    <6>[6.612798] Bluetooth: BNEP socket layer initialized
    <3>[9.016880] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu
    <3>[9.016882] Bluetooth: Loading patch file failed
  60: USB 00.0: 11500 Bluetooth Device
    Model: "Atheros AR3012 Bluetooth 4.0"
    Device: usb 0x3004 "AR3012 Bluetooth 4.0"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.36-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Sun Feb  7 00:38:04 2016
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  InstallationDate: Installed on 2015-10-24 (105 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: bnep btusb bluetooth
  MachineType: Micro-Star International Co., Ltd. GT72 2QD
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic 
root=UUID=f7880b23-39b5-423a-bdbf-62b111783450 ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2016-02-02 (4 days ago)
  dmi.bios.date: 12/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10I
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10I:bd12/19/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QD:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QD
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  hciconfig:

  rfkill:
   0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no

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

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

[Kernel-packages] [Bug 1542743] Re: Bluetooth: Patch file not found ar3k/AthrBT_0x00000200.dfu

[The Raf 90]

Hi there, I've installed the latest patch given because I was suffering
from the same bluetooth issue. Unfortunately after the patch my boot
sequence has become excruciatingly long!!! this is where it stops for ~2
minutes:

[CODE]
May 10 09:55:58 Aaron-Linux systemd[1]: Started Tell Plymouth To Write Out 
Runtime Data.
May 10 09:55:58 Aaron-Linux systemd[1]: 
dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev 
dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device appeared twice 
with different sysfs paths 
/sys/devices/pci:00/:00:1d.0/:3c:00.0/nvme/nvme0/nvme0n1/nvme0n1p1 
and 
/sys/devices/pci:00/:00:17.0/ata4/host3/target3:0:0/3:0:0:0/block/sda/sda4
May 10 09:55:58 Aaron-Linux systemd[1]: Found device Crucial_CT1050MX300SSD1 
HAL.
May 10 09:55:58 Aaron-Linux apparmor[665]:  * Starting AppArmor profiles
May 10 09:55:58 Aaron-Linux systemd[1]: Mounting /mnt/HAL...
May 10 09:55:58 Aaron-Linux systemd[1]: Activating swap Swap Partition...
May 10 09:55:58 Aaron-Linux systemd[1]: Starting Network Time Synchronization...
May 10 09:55:58 Aaron-Linux systemd[1]: Starting Update UTMP about System 
Boot/Shutdown...
May 10 09:55:58 Aaron-Linux apparmor[665]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
May 10 09:55:58 Aaron-Linux systemd[1]: Activated swap Swap Partition.
May 10 09:55:58 Aaron-Linux systemd[1]: Started Set console font and keymap.
May 10 09:55:58 Aaron-Linux apparmor[665]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
May 10 09:55:58 Aaron-Linux systemd-timesyncd[760]: The system is configured to 
read the RTC time in the local time zone. This mode can not be fully supported. 
All system time to RTC updates are disabled.
May 10 09:55:58 Aaron-Linux systemd[1]: Started Network Time Synchronization.
May 10 09:55:58 Aaron-Linux systemd[1]: Reached target System Time Synchronized.
May 10 09:55:58 Aaron-Linux systemd[1]: Created slice system-getty.slice.
May 10 09:55:58 Aaron-Linux systemd[1]: Started Update UTMP about System 
Boot/Shutdown.
May 10 09:55:58 Aaron-Linux apparmor[665]:...done.
May 10 09:55:58 Aaron-Linux systemd[1]: Started LSB: AppArmor initialization.
May 10 09:55:58 Aaron-Linux systemd[1]: Starting Raise network interfaces...
May 10 09:55:58 Aaron-Linux systemd[1]: Started Raise network interfaces.
May 10 09:55:58 Aaron-Linux ntfs-3g[844]: Version 2015.3.14AR.1 integrated FUSE 
28
May 10 09:55:58 Aaron-Linux ntfs-3g[844]: Mounted /dev/sda4 (Read-Write, label 
"HAL", NTFS 3.1)
May 10 09:55:58 Aaron-Linux ntfs-3g[844]: Cmdline options: rw,nosuid,nodev
May 10 09:55:58 Aaron-Linux ntfs-3g[844]: Mount options: 
rw,nosuid,nodev,allow_other,nonempty,relatime,fsname=/dev/sda4,blkdev,blksize=4096
May 10 09:55:58 Aaron-Linux ntfs-3g[844]: Ownership and permissions disabled, 
configuration type 7
May 10 09:55:58 Aaron-Linux systemd[1]: Mounted /mnt/HAL.
May 10 09:55:58 Aaron-Linux mtp-probe: checking bus 1, device 5: 
"/sys/devices/pci:00/:00:14.0/usb1/1-11"
May 10 09:55:58 Aaron-Linux mtp-probe: checking bus 1, device 2: 
"/sys/devices/pci:00/:00:14.0/usb1/1-1"
May 10 09:55:58 Aaron-Linux mtp-probe: checking bus 1, device 3: 
"/sys/devices/pci:00/:00:14.0/usb1/1-3"
May 10 09:55:58 Aaron-Linux mtp-probe: bus: 1, device: 2 was not an MTP device
May 10 09:55:58 Aaron-Linux mtp-probe: bus: 1, device: 5 was not an MTP device
May 10 09:55:58 Aaron-Linux mtp-probe: bus: 1, device: 3 was not an MTP device
May 10 09:55:58 Aaron-Linux systemd[1]: Starting Load/Save RF Kill Switch 
Status...
May 10 09:55:58 Aaron-Linux systemd[1]: Started Load/Save RF Kill Switch Status.
May 10 09:55:58 Aaron-Linux systemd[1]: Starting Tell Plymouth To Write Out 
Runtime Data...
May 10 09:55:58 Aaron-Linux systemd[1]: Started Braille Device Support.
May 10 09:55:58 Aaron-Linux systemd[1]: Started Tell Plymouth To Write Out 
Runtime Data.
May 10 09:55:58 Aaron-Linux systemd[1]: 
dev-disk-by\x2duuid-c91bdb32\x2db56f\x2d417a\x2da8d3\x2d587fd46ab99b.device: 
Job 
dev-disk-by\x2duuid-c91bdb32\x2db56f\x2d417a\x2da8d3\x2d587fd46ab99b.device/start
 timed out.
[\CODE]


Furthermore while the laptop is sitting on my desk it keeps logging out this 
crap:

[CODE]

May 10 09:56:54 Aaron-Linux os-prober: debug: /dev/sda5: is active swap
May 10 09:56:57 Aaron-Linux gnome-session[1462]: (gnome-shell:1652): St-WARNING 
**: Ignoring excess values in shadow definition
May 10 09:56:57 Aaron-Linux gnome-session[1462]: message repeated 7 times: [ 
(gnome-shell:1652): St-WARNING **: Ignoring excess values in shadow definition]
May 10 09:57:01 Aaron-Linux google-chrome.desktop[6995]: 
[1,1449989952:07:57:01.033389] Native Client module will be loaded at base 
address 0x095b
May 10 09:57:19 Aaron-Linux systemd[1]: 
dev-disk-by\x2duuid-c91bdb32\x2db56f\x2d417a\x2da8d3\x2d587fd46ab99b.device: 
Job 
dev-disk-by\x2duuid-c91bdb32\x2db56f\x2d417a\x2da8d3\x2d587fd46ab99b.device/start
 timed out.
May 10 09:57:19 Aaron-Linux systemd[1

[Kernel-packages] [Bug 1684010] Re: 17.04, i915 freeze on VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller

[Jonas Slivka]

I'm also experiencing freezes on Ubuntu Gnome 17.04 (x64). I'm on dell
Latitude E5470 with the following specs:

Intel® Core™ i5-6440HQ CPU @ 2.60GHz × 4 
Intel® HD Graphics 530 (Skylake GT2)

Tried -20, -17, -14 kernels - all experiencing complete freezes. Now
I've been on -9 for a day without any freezes.

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

Title:
  17.04, i915 freeze on VGA compatible controller: Intel Corporation
  Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Just freezes all unity and/or X.
  Nothing in any logs though.

  16.10 worked just fine.

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

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

[Kernel-packages] [Bug 1683277] Re: Mute key LED does not work on HP notebooks

[Steven H]

How can I ensure that this bug is also known to upstream? Will it get
reported automatically, or will this bug just sit here and should I
report it elsewhere myself?

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

Title:
  Mute key LED does not work on HP notebooks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description of problem:
  The F6/mute key on the keyboard of HP notebooks often has a built in LED 
indicator to show if the sound is muted. The LED state is never toggled. It 
will just retain its state, even though the audio is succesfully muted/unmuted.

  Tested with HP Envy 15 from 2015. HP Stream 11 from 2015 and HP Stream
  11 from 2016.

  Version-Release number of selected component (if applicable):

  
  How reproducible:
  Always.

  Steps to Reproduce:
  1. Press mute key on HP laptop

  Actual results:
  Mute state in software toggles, LED in mute key does not.

  
  Expected results:
  Mute state in software and LED in mute key toggle.

  
  Additional info:
  This happens on kernel 4.8, 4.9 and 4.10. I have not tested any other 
versions.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stevenh1659 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Apr 17 11:02:20 2017
  HibernationDevice: RESUME=UUID=2d246125-abf7-4945-9542-45b25fb8fcb2
  InstallationDate: Installed on 2016-09-13 (215 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 05c8:038e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY Notebook
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=fa0986da-ae48-47e2-9e62-a8ef25ce5b73 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.23
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81CC
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 60.26
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.23:bd09/13/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81CC:rvrKBCVersion60.26:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive

[Ian De Silva]

I experienced the same issue with 16.10 on a Dell 9550 (#1689357).

I installed the kernel from @kaihengfeng and have been using the new
kernel for the better part of the day (about 14 hours, 8 of which was
active-use time). No issues thus far.

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

Title:
  APST quirk needed for Samsung 512GB NVMe drive

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

Bug description:
  APST support just landed in the latest Zesty kernel (4.10.0-14.16) as
  part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602.
  That patch has a quirk for certain 256GB Samsung drives found in Dell
  laptops that do not behave well when APST is enabled. I am
  experiencing the same symptoms with the same model laptop except with
  a 512GB Samsung. Prior to manually disabling APST the drive would die
  and system would go down in flames with I/O errors within 20 to 40
  minutes of boot.

  $ sudo nvme list
  Node SN   Model   
 Namespace Usage  Format   FW Rev  
    
 - -- 
 
  /dev/nvme0n1   ** PM951 NVMe SAMSUNG 512GB
 1 500.20  GB / 512.11  GB512   B +  0 B   BXV76D0Q

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ajclayton   3305 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri Mar 31 09:42:38 2017
  InstallationDate: Installed on 2012-09-08 (1665 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic 
root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt 
nouveau.modeset=0 log_buf_len=20M
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  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.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1580272] Re: i915-bpo crashes on external hdmi input

[Timo Aaltonen]

This is properly fixed since v4.8.6, but the i915_bpo backport in xenial
just needs the warning silenced as requested.

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

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

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

Title:
  i915-bpo crashes on external hdmi input

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

Bug description:
  This issue happens when plugging in an external HDMI projector in
  mirrored mode.

  To reproduce this issue:
  1) Plug in external HDMI monitor
  2) Set mirrored displays
  3) Unplug HDMI
  4) check dmesg for warnings

  --

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.39
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mark   4296 F pulseaudio
  Date: Tue May 10 10:25:07 2016
  InstallationDate: Installed on 2016-05-02 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d4 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
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  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.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1689357] Re: Filesystem becomes read-only while in use

[Ian De Silva]

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

** This bug has been marked a duplicate of bug 1678184
   APST quirk needed for Samsung 512GB NVMe drive

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

Title:
  Filesystem becomes read-only while in use

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu GNOME 16.10.  After updating to kernel 4.8.0-49.52
  (and subsequently to 4.8.0-51.54) via apt, my file system switches to
  read-only during use.  This bug does not occur on kernel 4.8.0-46.49
  (the linux-image-4.8.0-46-generic package).

  Also, note, I'm running with an encrypted filesystem (LUKS with LVM)
  on a dual-boot machine with a large SSD.  I followed these
  instructions:  https://askubuntu.com/questions/293028/how-can-i
  -install-ubuntu-encrypted-with-luks-with-dual-boot

  The bug takes a while to manifest.  I'm not certain how long.  The
  only consistent behavior pattern I've observed is that the system
  suspended (often for a few hours/overnight), works for a while, and
  then, while working within Atom or IntelliJ, the filesystem,
  unexpectedly, becomes read-only.  Sometimes the entire system hangs
  while other times I still have a somewhat working terminal.  If I
  manage to trigger a reboot, the system hangs midway through it.

  Ubuntu version:  16.10 (Ubuntu GNOME)

  System:  Dell XPS 9550
  Storage info:  
  *-storage
 description: Non-Volatile memory controller
 product: NVMe SSD Controller
 vendor: Samsung Electronics Co Ltd
 physical id: 0
 bus info: pci@:04:00.0
 version: 01
 width: 64 bits
 clock: 33MHz
 capabilities: storage pm msi pciexpress msix nvm_express bus_master 
cap_list
 configuration: driver=nvme latency=0
 resources: irq:16 memory:de40-de403fff ioport:c000(size=256)

  
  I've also attached the kernel log.  It seems like around 11:42 the system had 
a hard time finding files and at 11:41:50 we see the the file system remounted 
read only.

  Any help you could provide would be greatly appreciated!  Thanks!
  -Ian

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-46-generic 4.8.0-46.49
  ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  desilvai   1630 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon May  8 11:42:52 2017
  HibernationDevice: RESUME=UUID=c3f8c23a-ad61-4e97-9215-577f9d5cf9e7
  InstallationDate: Installed on 2016-10-31 (189 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d4 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-46-generic.efi.signed 
root=/dev/mapper/cryptovg-lv_root ro 
cryptopts=target=cryptoroot,source=/dev/disk/by-uuid/a20274d1-2c9f-4eca-bec5-4107099610e7,lvm=cryptovg
 quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-46-generic N/A
   linux-backports-modules-4.8.0-46-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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