[Kernel-packages] [Bug 1520343] Re: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported

[Yuan-Chen Cheng]

** Changed in: oem-priority
   Status: New => In Progress

** Changed in: oem-priority
   Status: In Progress => Triaged

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

Title:
  Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported

Status in HWE Next:
  New
Status in OEM Priority Project:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  ---

  STATUS 2016-03-17:

  ==
  WARNING: You need at least kernel 4.5.0 for the following new fix to work, 
else refer to the old method described in post #22
  ==

  The support for this card has now been merged to
  https://github.com/kvalo/ath10k-firmware. The repository now contains
  the required board.bin, board-2.bin and firmware-4.bin files for the
  card to initialize and connect to a bgn-access point (5GHz (ac-
  protocol) is still untested, feel free to modify this if you can
  confirm it works). Here are the new commands to get you online:

  sudo mkdir -p /lib/firmware/ath10k/QCA6174/hw3.0/

  sudo rm /lib/firmware/ath10k/QCA6174/hw3.0/* 2> /dev/null

  sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board.bin
  https://github.com/kvalo/ath10k-
  firmware/blob/master/QCA6174/hw3.0/board.bin?raw=true

  sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin
  https://github.com/kvalo/ath10k-
  firmware/blob/master/QCA6174/hw3.0/board-2.bin?raw=true

  sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/firmware-4.bin
  https://github.com/kvalo/ath10k-
  
firmware/blob/master/QCA6174/hw3.0/firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1?raw=true

  Reboot or reload the ath10k_pci module and you should be able to
  connect!

  ---

  STATUS 2015-12-22:

  Currently there is a fix for this problem in post #22 (originally post
  #19, but reposted due to command typos!) which seems to have fixed the
  issue for many. This bug is unique to revision 32 of the card
  [168c:003e], fixes for older revisions don't seem to work.

  There are a couple of issues regarding the fix for some people (not
  all):

  1. Wireless works, but network throughput stops some time after
  connecting to access point

  2. Bluetooth communications take a noticeable performance hit when
  transferring something over WiFi

  ---

  Original description:

  I have recently installed Ubuntu 15.10 (64-bit) alongside Windows 10 on an 
Acer Aspire VN7-792G-76ZH and discovered, that the Qualcomm wireless card 
doesn't work in it or 16.04.
  The card has the device id 168c:003e as many other cards, for example the 
Qualcomm Atheros Killer 
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184), but it has a 
newer revision number (32) and the suggested fixes work only partially and the 
wireless is unusable.

  The computer has just been released this summer and is Intel Skylake
  -based.

  I've tried the patch from bug 1383184, which has a fix for the card revision 
20:
  Make the directory /lib/firmware/ath10k/QCA6174/hw3.0/ and put in the patch 
files:
  board.bin
  firmware-4.bin
  notice_ath10k_firmware-4.txt

  ath10k_pci succeeds in loading the firmware, but it seems that the
  firmware is not working correctly:

  dmesg | grep ath
  [5.452683] ath10k_pci :07:00.0: pci irq msi-x interrupts 8 irq_mode 0 
reset_mode 0
  [5.678420] ath10k_pci :07:00.0: Direct firmware load for 
ath10k/cal-pci-:07:00.0.bin failed with error -2
  [5.678773] ath10k_pci :07:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/board-pci-168c:003e:11ad:0807.bin failed with error -2
  [5.678781] ath10k_pci :07:00.0: failed to load spec board file, 
falling back to generic: -2
  [5.679445] ath10k_pci :07:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
  [5.679453] ath10k_pci :07:00.0: could not fetch firmware file 
'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
  [7.802316] ath10k_pci :07:00.0: qca6174 hw3.2 (0x0503, 
0x00340aff, 168c:003e:11ad:0807 fallback) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 api 
4 htt 3.26 wmi 4 cal otp max_sta 32
  [7.802329] ath10k_pci :07:00.0: debug 0 debugfs 1 tracing 1 dfs 0 
testmode 0
  [8.200607] ath: EEPROM regdomain: 0x6c
  [8.200614] ath: EEPROM indicates we should expect a direct regpair map
  [8.200619] ath: Country alpha2 being used: 00
  [8.200621] ath: Regpair used: 0x6c
  [8.216605] ath10k_pci :07:00.0 wlp7s0: renamed from wlan0
  [   13.462029] ath10k_pci :07:00.0: failed to enable dynamic BW: -11
  [   16.461416] ath10k_pci :07:00.0: could not suspend target (-11)
  [   24.760062] ath10k_pci :07:00.0: failed to enable dynamic BW: -11
  [   27.759534] 

Re: [Kernel-packages] [Bug 1728417] Xubuntu suspend fails - shuts down instead

[Kai-Heng Feng]

> On 27 Nov 2017, at 7:09 AM, Colin Pretorius <1728...@bugs.launchpad.net> 
> wrote:
> 
> Thanks - for each of freezer, devices, platform, processors, and core, I
> was able to run './analyze_suspend.py -rtcwake 20 -f -m mem' and the
> machine suspends and resumes successfully. When I again return
> /sys/power/pm_test to none, it doesn't (same behaviour as before).

Then it’s highly likely to be a BIOS issue.
Is your BIOS up-to-date?
If it’s already the latest one, then you should ask the board manufacturer
to take a look.

> 
> I can upload the output of analyze_suspend.py if they'll be useful (I
> don't know if they will be, given that they show successful suspends and
> resumes).
> 
> -- 
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1728417
> 
> Title:
>  Xubuntu suspend fails - shuts down instead
> 
> Status in linux package in Ubuntu:
>  Confirmed
> 
> Bug description:
>  Suspending my machine (Xubuntu Whisker menu/Log out/Suspend) causes it
>  to shut down instead (or at the very least, to restart when powering
>  on again).
> 
>  Observed: after clicking on 'Suspend', the screen blanks, 10 seconds
>  pass, then the machine powers down. When I power up again, it returns
>  to the BIOS post screen, then Xubuntu boot splash screen, then login.
> 
>  Notes:
> 
>  * machine is a recent build, previously running 17.04. Had the same
>  issue (and suspend error messages in syslog), so this does not appear
>  to be related to the 17.10 upgrade.
> 
>  * given the "wpasupplicant failed with error code 254" line in syslog,
>  and following comments in https://bugs.debian.org/cgi-
>  bin/bugreport.cgi?bug=835648, I tried removing wpasupplicant from
>  /lib/systemd/system-suspend. This resulted in the machine suspending
>  sooner (no time-out), but suspend still failed.
> 
>  * Separately, I tried switching to the nouveau driver (I'd seem some
>  mentions of problematic proprietary nvidia drivers). This too made no
>  difference.
> 
>  Please let me know if I can provide any other information.
> 
>  ProblemType: Bug
>  DistroRelease: Ubuntu 17.10
>  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
>  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>  Uname: Linux 4.13.0-16-generic x86_64
>  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
>  ApportVersion: 2.20.7-0ubuntu3.1
>  Architecture: amd64
>  AudioDevicesInUse:
>   USERPID ACCESS COMMAND
>   /dev/snd/controlC0:  colin  1460 F pulseaudio
>   /dev/snd/controlC1:  colin  1460 F pulseaudio
>  CurrentDesktop: XFCE
>  Date: Sun Oct 29 15:03:36 2017
>  InstallationDate: Installed on 2017-10-13 (15 days ago)
>  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
>  MachineType: System manufacturer System Product Name
>  ProcFB: 0 EFI VGA
>  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
> root=UUID=dcb5dfa5-9644-4b53-be57-ffadb28e8f45 ro quiet splash vt.handoff=7
>  RelatedPackageVersions:
>   linux-restricted-modules-4.13.0-16-generic N/A
>   linux-backports-modules-4.13.0-16-generic  N/A
>   linux-firmware 1.169
>  SourcePackage: linux
>  UpgradeStatus: Upgraded to artful on 2017-10-25 (3 days ago)
>  dmi.bios.date: 09/08/2017
>  dmi.bios.vendor: American Megatrends Inc.
>  dmi.bios.version: 0902
>  dmi.board.asset.tag: Default string
>  dmi.board.name: ROG STRIX B350-F GAMING
>  dmi.board.vendor: ASUSTeK COMPUTER INC.
>  dmi.board.version: Rev X.0x
>  dmi.chassis.asset.tag: Default string
>  dmi.chassis.type: 3
>  dmi.chassis.vendor: Default string
>  dmi.chassis.version: Default string
>  dmi.modalias: 
> dmi:bvnAmericanMegatrendsInc.:bvr0902:bd09/08/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB350-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
>  dmi.product.family: To be filled by O.E.M.
>  dmi.product.name: System Product Name
>  dmi.product.version: System Version
>  dmi.sys.vendor: System manufacturer
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728417/+subscriptions

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

Title:
  Xubuntu suspend fails - shuts down instead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Suspending my machine (Xubuntu Whisker menu/Log out/Suspend) causes it
  to shut down instead (or at the very least, to restart when powering
  on again).

  Observed: after clicking on 'Suspend', the screen blanks, 10 seconds
  pass, then the machine powers down. When I power up again, it returns
  to the BIOS post screen, then Xubuntu boot splash screen, then login.

  Notes:

  * machine is a recent build, previously running 17.04. Had the same
  issue (and suspend error messages in 

[Kernel-packages] [Bug 1729736] Re: 10de:1c8c [MSI] Module nouveau fails to manage GeForce GTX 1050 Ti Mobile

[Bug Watch Updater]

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

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  10de:1c8c [MSI] Module nouveau fails to manage GeForce GTX 1050 Ti
  Mobile

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

Bug description:
  Trying to use 'Nvidia GeForce GTX 1050 Ti Mobile' with 'Ubuntu 17.10
  (Artful)' :

  - Linux kernel 4.13.0-16 from 'Ubuntu 17.10 (Artful)' systematically
  fails (1 CPU stuck).

  - Linux kernel 4.14.0-041400rc7 from http://kernel.ubuntu.com/~kernel-
  ppa/mainline seems to succeed.

  See attached kern.log

  
  After reboot on Linux kernel 4.13.0-16 with nouveau blacklisted :

  $ lspci -nn -v -s 1:0.0

  01:00.0 3D controller [0302]: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti 
Mobile] [10de:1c8c] (rev a1)
Subsystem: Micro-Star International Co., Ltd. [MSI] GP107M [GeForce GTX 
1050 Ti Mobile] [1462:11c8]
Flags: bus master, fast devsel, latency 0, IRQ 255
Memory at de00 (32-bit, non-prefetchable) [size=16M]
Memory at c000 (64-bit, prefetchable) [size=256M]
Memory at d000 (64-bit, prefetchable) [size=32M]
I/O ports at e000 [disabled] [size=128]
Expansion ROM at df00 [disabled] [size=512K]
Capabilities: 
Kernel modules: nvidiafb, nouveau

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

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

[Kernel-packages] [Bug 1726299] Re: Apple Thunderbolt 2 to FireWire adapter not working

[Paul White]

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

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=189731
   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/1726299

Title:
  Apple Thunderbolt 2 to FireWire adapter not working

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

Bug description:
  The adapter is connected through an Apple Thunderbolt 3 to Thunderbolt
  2 adapter. Ubuntu seems not to recognize the Firewire adapter.

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 17.04
  Release:17.04
  Codename:   zesty

  uname -r
  4.10.0-19-generic

  sudo lshw -short
  H/W-Pfad Gerät Klasse Beschreibung
  ===
  system Z170N-Gaming 5 (Default 
string)
  /0  busZ170N-Gaming 5
  /0/0memory 64KiB BIOS
  /0/3d   memory 16GiB Systemspeicher
  /0/3d/0 memory 8GiB DIMM DDR4 Synchron 
2133 MHz (0,5 ns)
  /0/3d/1 memory Project-Id-Version: 
lshwReport-Msgid-Bugs-To: FULL NAME POT-Creatio
  /0/3d/2 memory 8GiB DIMM DDR4 Synchron 
2133 MHz (0,5 ns)
  /0/3d/3 memory Project-Id-Version: 
lshwReport-Msgid-Bugs-To: FULL NAME POT-Creatio
  /0/43   memory 128KiB L1 Cache
  /0/44   memory 512KiB L2 Cache
  /0/45   memory 3MiB L3 Cache
  /0/46   processor  Intel(R) Core(TM) i3-6100T 
CPU @ 3.20GHz
  /0/100  bridge Skylake Host Bridge/DRAM 
Registers
  /0/100/1bridge Skylake PCIe Controller 
(x16)
  /0/100/1/0  displayOland GL [FirePro W2100]
  /0/100/1/0.1multimedia Cape Verde/Pitcairn HDMI 
Audio [Radeon HD 7700/7800 Series]
  /0/100/14   busSunrise Point-H USB 3.0 
xHCI Controller
  /0/100/14/0  usb1   busxHCI Host Controller
  /0/100/14/0/6   input  USB Gaming Keyboard
  /0/100/14/0/d   communication  Bluetooth-Schnittstelle
  /0/100/14/1  usb2   busxHCI Host Controller
  /0/100/14/1/5scsi6  storageStorage Media
  /0/100/14/1/5/0.0.0  /dev/sdb   disk   15GB Storage Media
  /0/100/14/1/5/0.0.0/0/dev/sdb   disk   15GB 
  /0/100/14/1/5/0.0.0/0/2  /dev/sdb2  volume 15EiB Windows FAT Laufwerk
  /0/100/16   communication  Sunrise Point-H CSME HECI 
#1
  /0/100/17   storageSunrise Point-H SATA 
controller [AHCI mode]
  /0/100/1b   bridge Sunrise Point-H PCI Root 
Port #17
  /0/100/1b.2 bridge Sunrise Point-H PCI Root 
Port #19
  /0/100/1b.3 bridge Sunrise Point-H PCI Root 
Port #20
  /0/100/1c   bridge Sunrise Point-H PCI 
Express Root Port #1
  /0/100/1c/0 bridge DSL6540 Thunderbolt 3 
Bridge [Alpine Ridge 4C 2015]
  /0/100/1c/0/0   bridge DSL6540 Thunderbolt 3 
Bridge [Alpine Ridge 4C 2015]
  /0/100/1c/0/1   bridge DSL6540 Thunderbolt 3 
Bridge [Alpine Ridge 4C 2015]
  /0/100/1c/0/2   bridge DSL6540 Thunderbolt 3 
Bridge [Alpine Ridge 4C 2015]
  /0/100/1c/0/2/0 busDSL6540 USB 3.1 Controller 
[Alpine Ridge]
  /0/100/1c/0/2/0/0usb3   busxHCI Host Controller
  /0/100/1c/0/2/0/0/1 genericThunderbolt 3 (USB-C) to 
Thunderbolt 2 Adapter
  /0/100/1c/0/2/0/0/2 input  USB Optical Mouse
  /0/100/1c/0/2/0/1usb4   busxHCI Host Controller
  /0/100/1c/0/4   bridge DSL6540 Thunderbolt 3 
Bridge [Alpine Ridge 4C 2015]
  /0/100/1c.2 bridge Sunrise Point-H PCI 
Express Root Port #3
  /0/100/1c.3 bridge Sunrise Point-H PCI 
Express Root Port #4
  /0/100/1c.4 bridge Sunrise Point-H PCI 
Express Root Port #5
  /0/100/1c.4/0enp13s0networkKiller E2400 Gigabit 
Ethernet Controller
  /0/100/1c.5 bridge Sunrise Point-H PCI 
Express 

[Kernel-packages] [Bug 1727544] Re: ELANTECH Touchpad is not detected in 'Lenovo Ideapad 320 14AST' after fresh install

[Agasi Gilang Persada]

kmously : Done. The touchpad is working fine with the kernel from
kaihengfeng.

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

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

Title:
  ELANTECH Touchpad is not detected in 'Lenovo Ideapad 320 14AST' after
  fresh install

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  I have installed Ubuntu 16.04 on my new Lenovo Ideapad 320 14AST. The 
touchpad is not working. I have followed this tutorial 
https://askubuntu.com/questions/763584/elantech-touchpad-not-working-on-ubuntu-16-04-and-arch-linux
 and it doesn't work. The touchpad is working fine on Windows. My kernel 
version is 4.10.0-37-generic.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  agasigp1605 F pulseaudio
   /dev/snd/controlC1:  agasigp1605 F pulseaudio
  CRDA:
   country ID: DFS-JP
(2402 - 2482 @ 20), (N/A, 20), (N/A)
(5735 - 5815 @ 20), (N/A, 23), (N/A)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=da16f5a9-567e-4dd7-994a-eb64b6797690
  InstallationDate: Installed on 2017-10-25 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 80XU
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=457b1305-a90d-462a-92c2-11d129eb1580 ro i8042.kbdreset=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.157.12
  Tags:  xenial
  Uname: Linux 4.10.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/28/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5PCN18WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-14AST
  dmi.modalias: 
dmi:bvnLENOVO:bvr5PCN18WW:bd09/28/2017:svnLENOVO:pn80XU:pvrLenovoideapad320-14AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad320-14AST:
  dmi.product.name: 80XU
  dmi.product.version: Lenovo ideapad 320-14AST
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1726299] [NEW] Apple Thunderbolt 2 to FireWire adapter not working

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

The adapter is connected through an Apple Thunderbolt 3 to Thunderbolt 2
adapter. Ubuntu seems not to recognize the Firewire adapter.

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.04
Release:17.04
Codename:   zesty

uname -r
4.10.0-19-generic

sudo lshw -short
H/W-Pfad Gerät Klasse Beschreibung
===
system Z170N-Gaming 5 (Default 
string)
/0  busZ170N-Gaming 5
/0/0memory 64KiB BIOS
/0/3d   memory 16GiB Systemspeicher
/0/3d/0 memory 8GiB DIMM DDR4 Synchron 2133 
MHz (0,5 ns)
/0/3d/1 memory Project-Id-Version: 
lshwReport-Msgid-Bugs-To: FULL NAME POT-Creatio
/0/3d/2 memory 8GiB DIMM DDR4 Synchron 2133 
MHz (0,5 ns)
/0/3d/3 memory Project-Id-Version: 
lshwReport-Msgid-Bugs-To: FULL NAME POT-Creatio
/0/43   memory 128KiB L1 Cache
/0/44   memory 512KiB L2 Cache
/0/45   memory 3MiB L3 Cache
/0/46   processor  Intel(R) Core(TM) i3-6100T 
CPU @ 3.20GHz
/0/100  bridge Skylake Host Bridge/DRAM 
Registers
/0/100/1bridge Skylake PCIe Controller (x16)
/0/100/1/0  displayOland GL [FirePro W2100]
/0/100/1/0.1multimedia Cape Verde/Pitcairn HDMI 
Audio [Radeon HD 7700/7800 Series]
/0/100/14   busSunrise Point-H USB 3.0 xHCI 
Controller
/0/100/14/0  usb1   busxHCI Host Controller
/0/100/14/0/6   input  USB Gaming Keyboard
/0/100/14/0/d   communication  Bluetooth-Schnittstelle
/0/100/14/1  usb2   busxHCI Host Controller
/0/100/14/1/5scsi6  storageStorage Media
/0/100/14/1/5/0.0.0  /dev/sdb   disk   15GB Storage Media
/0/100/14/1/5/0.0.0/0/dev/sdb   disk   15GB 
/0/100/14/1/5/0.0.0/0/2  /dev/sdb2  volume 15EiB Windows FAT Laufwerk
/0/100/16   communication  Sunrise Point-H CSME HECI #1
/0/100/17   storageSunrise Point-H SATA 
controller [AHCI mode]
/0/100/1b   bridge Sunrise Point-H PCI Root 
Port #17
/0/100/1b.2 bridge Sunrise Point-H PCI Root 
Port #19
/0/100/1b.3 bridge Sunrise Point-H PCI Root 
Port #20
/0/100/1c   bridge Sunrise Point-H PCI Express 
Root Port #1
/0/100/1c/0 bridge DSL6540 Thunderbolt 3 Bridge 
[Alpine Ridge 4C 2015]
/0/100/1c/0/0   bridge DSL6540 Thunderbolt 3 Bridge 
[Alpine Ridge 4C 2015]
/0/100/1c/0/1   bridge DSL6540 Thunderbolt 3 Bridge 
[Alpine Ridge 4C 2015]
/0/100/1c/0/2   bridge DSL6540 Thunderbolt 3 Bridge 
[Alpine Ridge 4C 2015]
/0/100/1c/0/2/0 busDSL6540 USB 3.1 Controller 
[Alpine Ridge]
/0/100/1c/0/2/0/0usb3   busxHCI Host Controller
/0/100/1c/0/2/0/0/1 genericThunderbolt 3 (USB-C) to 
Thunderbolt 2 Adapter
/0/100/1c/0/2/0/0/2 input  USB Optical Mouse
/0/100/1c/0/2/0/1usb4   busxHCI Host Controller
/0/100/1c/0/4   bridge DSL6540 Thunderbolt 3 Bridge 
[Alpine Ridge 4C 2015]
/0/100/1c.2 bridge Sunrise Point-H PCI Express 
Root Port #3
/0/100/1c.3 bridge Sunrise Point-H PCI Express 
Root Port #4
/0/100/1c.4 bridge Sunrise Point-H PCI Express 
Root Port #5
/0/100/1c.4/0enp13s0networkKiller E2400 Gigabit 
Ethernet Controller
/0/100/1c.5 bridge Sunrise Point-H PCI Express 
Root Port #6
/0/100/1c.5/0wlp14s0networkWireless 8260
/0/100/1c.6 bridge Sunrise Point-H PCI Express 
Root Port #7
/0/100/1c.7 bridge Sunrise Point-H PCI Express 
Root Port #8
/0/100/1d   bridge Sunrise Point-H PCI Express 
Root Port #9
/0/100/1f   bridge Sunrise Point-H LPC 
Controller
/0/100/1f.2 memory Memory controller
/0/100/1f.3 multimedia Sunrise 

[Kernel-packages] [Bug 1720393] Re: kernel BUG at /build/linux-s_bACt/linux-4.13.0/mm/usercopy.c:72!

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

Title:
  kernel BUG at /build/linux-s_bACt/linux-4.13.0/mm/usercopy.c:72!

Status in linux package in Ubuntu:
  Expired

Bug description:
  Generic manual install procedure on KVM/qemu guest

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4456 F pulseaudio
  CasperVersion: 1.384
  Date: Fri Sep 29 09:59:23 2017
  Failure: oops
  IwConfig:
   ens3  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcFB:
   0 cirrusdrmfb
   1 nouveaufb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: kernel BUG at /build/linux-s_bACt/linux-4.13.0/mm/usercopy.c:72!
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC

[Konrad Zapałowicz]

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

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

Title:
  Cannot pair BLE remote devices when using combo BT SoC

Status in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in bluez source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in bluez source package in Zesty:
  New
Status in linux source package in Zesty:
  Fix Committed
Status in bluez source package in Artful:
  New
Status in linux source package in Artful:
  Fix Committed

Bug description:
  It has been observed that sometimes it is not possible to pair with
  BLE remote devices when the host system is using combo (WiFi + BT)
  chip.

  The root cause of the disconnection has been identified as coming from
  the internal to bluez timeout. If bluez does not hear any reply from for
  two seconds the link is automagically disconnected. The reason fro the
  silence is not however a failure of the remote device but quite often a
  delay in the WiFi/BT combo driver that causes the packages not to reach
  the bluez stack.

  [Impact]

  Not possible to pair BLE remote devices such as sensors and such with
  Ubuntu when the host system uses BT+WiFi combo SoC. The connection
  attempt is disturbed with a timeout.

  [Fix]

  It has been fixed by increasing the timeout value from 2 seconds to
  4 seconds. It is enough for the events to reach the stack (measured
  that it takes between 3 and 3.5 seconds).

  [Testcase]

  Tested with the device that failed to connect to Ubuntu Core gateway.
  It fails w/o the patch, it connects just fine with the patch applied.

  [Regression Potential]

  Very small. The increased timeout is taken into consideration only for
  new and scan report triggered connections. It will not make any already
  working device to fail to pair.

  [Other Info]

  The bug has been discussed and fixed here:

  https://marc.info/?l=linux-bluetooth=150824844606937=2

  [Patch]

  https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-
  next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571

  The patch has been accepted by the upstream and will be a part of the next
  kernel release. Currently in the bluetooth-next tree.

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

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

[Kernel-packages] [Bug 1729510] Re: libhugetlbfs failed with "[Errno 95] Operation not supported" on s390x zVM

[Po-Hsu Lin]

** Description changed:

  Steps:
  1. sudo apt-get install git python-minimal -y
  2. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
  3. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
  4. rm -fr autotest/client/tests
  5. ln -sf ~/autotest-client-tests autotest/client/tests
  6. AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/libhugetlbfs/control
  
  It will failed with the following python code piece when trying to
  access /proc/sys/vm/nr_hugepages:
  
  utils.write_one_line('/proc/sys/vm/nr_hugepages', str(pages_requested))
  
  With error message:
    [Errno 95] Operation not supported
+ 
+ For Xenial, the error message is:
+   [Errno 524] Unknown error 524
  
  This issue is not a regression.
  
  Full error log:
  
  $ AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-
  local --verbose autotest/client/tests/libhugetlbfs/control
  
  07:20:37 INFO | Writing results to 
/home/ubuntu/autotest/client/results/default
  07:20:37 DEBUG| Initializing the state engine
  07:20:37 DEBUG| Persistent state client.steps now set to []
  07:20:37 DEBUG| Persistent option harness now set to None
  07:20:37 DEBUG| Persistent option harness_args now set to None
  07:20:37 DEBUG| Selected harness: standalone
  07:20:48 INFO | START timestamp=1509607248localtime=Nov 
02 07:20:48
  07:20:48 DEBUG| Persistent state client._record_indent now set to 1
  07:20:48 INFO |   START   libhugetlbfslibhugetlbfs
timestamp=1509607248localtime=Nov 02 07:20:48
  07:20:48 DEBUG| Persistent state client._record_indent now set to 2
  07:20:48 DEBUG| Persistent state client.unexpected_reboot now set to 
('libhugetlbfs', 'libhugetlbfs')
  07:20:49 DEBUG| Running 'apt-get install --yes --force-yes build-essential 
git gcc'
  07:20:50 DEBUG| [stdout] Reading package lists...
  07:20:50 DEBUG| [stdout] Building dependency tree...
  07:20:50 DEBUG| [stdout] Reading state information...
  07:20:50 DEBUG| [stdout] build-essential is already the newest version 
(12.4ubuntu1).
  07:20:50 DEBUG| [stdout] gcc is already the newest version (4:7.2.0-1ubuntu1).
  07:20:50 DEBUG| [stdout] git is already the newest version 
(1:2.14.1-1ubuntu4).
  07:20:50 DEBUG| [stdout] The following packages were automatically installed 
and are no longer required:
  07:20:50 DEBUG| [stdout]   containerd linux-headers-4.13.0-14 
linux-headers-4.13.0-14-generic
  07:20:50 DEBUG| [stdout]   linux-image-4.13.0-14-generic 
linux-image-extra-4.13.0-14-generic runc
  07:20:50 DEBUG| [stdout] Use 'sudo apt autoremove' to remove them.
  07:20:50 DEBUG| [stdout] 0 upgraded, 0 newly installed, 0 to remove and 0 not 
upgraded.
  07:20:50 ERROR| [stderr] W: --force-yes is deprecated, use one of the options 
starting with --allow instead.
  07:20:50 DEBUG| Running 'which gcc'
  07:20:50 DEBUG| [stdout] /usr/bin/gcc
  07:20:53 ERROR| Exception escaping from test:
  Traceback (most recent call last):
    File "/home/ubuntu/autotest/client/shared/test.py", line 378, in _exec
  _cherry_pick_call(self.initialize, *args, **dargs)
    File "/home/ubuntu/autotest/client/shared/test.py", line 738, in 
_cherry_pick_call
  return func(*p_args, **p_dargs)
    File "/home/ubuntu/autotest/client/tests/libhugetlbfs/libhugetlbfs.py", 
line 39, in initialize
  str(pages_requested))
    File "/home/ubuntu/autotest/client/shared/utils.py", line 408, in 
write_one_line
  open_write_close(filename, line.rstrip('\n') + '\n')
    File "/home/ubuntu/autotest/client/shared/utils.py", line 416, in 
open_write_close
  f.close()
  IOError: [Errno 95] Operation not supported
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic s390x
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Thu Nov  2 07:18:00 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
  
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
  
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/kl04vg01-kl04root crashkernel=196M 
BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   

[Kernel-packages] [Bug 1520343] Re: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported

[Alex Tu]

firmware submitted and should be included in next linux-firmware.
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1728523

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

Title:
  Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  ---

  STATUS 2016-03-17:

  ==
  WARNING: You need at least kernel 4.5.0 for the following new fix to work, 
else refer to the old method described in post #22
  ==

  The support for this card has now been merged to
  https://github.com/kvalo/ath10k-firmware. The repository now contains
  the required board.bin, board-2.bin and firmware-4.bin files for the
  card to initialize and connect to a bgn-access point (5GHz (ac-
  protocol) is still untested, feel free to modify this if you can
  confirm it works). Here are the new commands to get you online:

  sudo mkdir -p /lib/firmware/ath10k/QCA6174/hw3.0/

  sudo rm /lib/firmware/ath10k/QCA6174/hw3.0/* 2> /dev/null

  sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board.bin
  https://github.com/kvalo/ath10k-
  firmware/blob/master/QCA6174/hw3.0/board.bin?raw=true

  sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin
  https://github.com/kvalo/ath10k-
  firmware/blob/master/QCA6174/hw3.0/board-2.bin?raw=true

  sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/firmware-4.bin
  https://github.com/kvalo/ath10k-
  
firmware/blob/master/QCA6174/hw3.0/firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1?raw=true

  Reboot or reload the ath10k_pci module and you should be able to
  connect!

  ---

  STATUS 2015-12-22:

  Currently there is a fix for this problem in post #22 (originally post
  #19, but reposted due to command typos!) which seems to have fixed the
  issue for many. This bug is unique to revision 32 of the card
  [168c:003e], fixes for older revisions don't seem to work.

  There are a couple of issues regarding the fix for some people (not
  all):

  1. Wireless works, but network throughput stops some time after
  connecting to access point

  2. Bluetooth communications take a noticeable performance hit when
  transferring something over WiFi

  ---

  Original description:

  I have recently installed Ubuntu 15.10 (64-bit) alongside Windows 10 on an 
Acer Aspire VN7-792G-76ZH and discovered, that the Qualcomm wireless card 
doesn't work in it or 16.04.
  The card has the device id 168c:003e as many other cards, for example the 
Qualcomm Atheros Killer 
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184), but it has a 
newer revision number (32) and the suggested fixes work only partially and the 
wireless is unusable.

  The computer has just been released this summer and is Intel Skylake
  -based.

  I've tried the patch from bug 1383184, which has a fix for the card revision 
20:
  Make the directory /lib/firmware/ath10k/QCA6174/hw3.0/ and put in the patch 
files:
  board.bin
  firmware-4.bin
  notice_ath10k_firmware-4.txt

  ath10k_pci succeeds in loading the firmware, but it seems that the
  firmware is not working correctly:

  dmesg | grep ath
  [5.452683] ath10k_pci :07:00.0: pci irq msi-x interrupts 8 irq_mode 0 
reset_mode 0
  [5.678420] ath10k_pci :07:00.0: Direct firmware load for 
ath10k/cal-pci-:07:00.0.bin failed with error -2
  [5.678773] ath10k_pci :07:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/board-pci-168c:003e:11ad:0807.bin failed with error -2
  [5.678781] ath10k_pci :07:00.0: failed to load spec board file, 
falling back to generic: -2
  [5.679445] ath10k_pci :07:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
  [5.679453] ath10k_pci :07:00.0: could not fetch firmware file 
'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
  [7.802316] ath10k_pci :07:00.0: qca6174 hw3.2 (0x0503, 
0x00340aff, 168c:003e:11ad:0807 fallback) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 api 
4 htt 3.26 wmi 4 cal otp max_sta 32
  [7.802329] ath10k_pci :07:00.0: debug 0 debugfs 1 tracing 1 dfs 0 
testmode 0
  [8.200607] ath: EEPROM regdomain: 0x6c
  [8.200614] ath: EEPROM indicates we should expect a direct regpair map
  [8.200619] ath: Country alpha2 being used: 00
  [8.200621] ath: Regpair used: 0x6c
  [8.216605] ath10k_pci :07:00.0 wlp7s0: renamed from wlan0
  [   13.462029] ath10k_pci :07:00.0: failed to enable dynamic BW: -11
  [   16.461416] ath10k_pci :07:00.0: could not suspend target (-11)
  [   24.760062] ath10k_pci :07:00.0: failed to enable dynamic BW: -11
  [   27.759534] 

[Kernel-packages] [Bug 1729736] Re: 10de:1c8c [MSI] Module nouveau fails to manage GeForce GTX 1050 Ti Mobile

[Kai-Heng Feng]

** Also affects: linux via
   https://bugs.freedesktop.org/show_bug.cgi?id=101665
   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/1729736

Title:
  10de:1c8c [MSI] Module nouveau fails to manage GeForce GTX 1050 Ti
  Mobile

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

Bug description:
  Trying to use 'Nvidia GeForce GTX 1050 Ti Mobile' with 'Ubuntu 17.10
  (Artful)' :

  - Linux kernel 4.13.0-16 from 'Ubuntu 17.10 (Artful)' systematically
  fails (1 CPU stuck).

  - Linux kernel 4.14.0-041400rc7 from http://kernel.ubuntu.com/~kernel-
  ppa/mainline seems to succeed.

  See attached kern.log

  
  After reboot on Linux kernel 4.13.0-16 with nouveau blacklisted :

  $ lspci -nn -v -s 1:0.0

  01:00.0 3D controller [0302]: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti 
Mobile] [10de:1c8c] (rev a1)
Subsystem: Micro-Star International Co., Ltd. [MSI] GP107M [GeForce GTX 
1050 Ti Mobile] [1462:11c8]
Flags: bus master, fast devsel, latency 0, IRQ 255
Memory at de00 (32-bit, non-prefetchable) [size=16M]
Memory at c000 (64-bit, prefetchable) [size=256M]
Memory at d000 (64-bit, prefetchable) [size=32M]
I/O ports at e000 [disabled] [size=128]
Expansion ROM at df00 [disabled] [size=512K]
Capabilities: 
Kernel modules: nvidiafb, nouveau

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

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

[Kernel-packages] [Bug 1520343] Re: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported

[Alex Tu]

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
 Assignee: (unassigned) => Alex Tu (alextu)

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

Title:
  Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  ---

  STATUS 2016-03-17:

  ==
  WARNING: You need at least kernel 4.5.0 for the following new fix to work, 
else refer to the old method described in post #22
  ==

  The support for this card has now been merged to
  https://github.com/kvalo/ath10k-firmware. The repository now contains
  the required board.bin, board-2.bin and firmware-4.bin files for the
  card to initialize and connect to a bgn-access point (5GHz (ac-
  protocol) is still untested, feel free to modify this if you can
  confirm it works). Here are the new commands to get you online:

  sudo mkdir -p /lib/firmware/ath10k/QCA6174/hw3.0/

  sudo rm /lib/firmware/ath10k/QCA6174/hw3.0/* 2> /dev/null

  sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board.bin
  https://github.com/kvalo/ath10k-
  firmware/blob/master/QCA6174/hw3.0/board.bin?raw=true

  sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin
  https://github.com/kvalo/ath10k-
  firmware/blob/master/QCA6174/hw3.0/board-2.bin?raw=true

  sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/firmware-4.bin
  https://github.com/kvalo/ath10k-
  
firmware/blob/master/QCA6174/hw3.0/firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1?raw=true

  Reboot or reload the ath10k_pci module and you should be able to
  connect!

  ---

  STATUS 2015-12-22:

  Currently there is a fix for this problem in post #22 (originally post
  #19, but reposted due to command typos!) which seems to have fixed the
  issue for many. This bug is unique to revision 32 of the card
  [168c:003e], fixes for older revisions don't seem to work.

  There are a couple of issues regarding the fix for some people (not
  all):

  1. Wireless works, but network throughput stops some time after
  connecting to access point

  2. Bluetooth communications take a noticeable performance hit when
  transferring something over WiFi

  ---

  Original description:

  I have recently installed Ubuntu 15.10 (64-bit) alongside Windows 10 on an 
Acer Aspire VN7-792G-76ZH and discovered, that the Qualcomm wireless card 
doesn't work in it or 16.04.
  The card has the device id 168c:003e as many other cards, for example the 
Qualcomm Atheros Killer 
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184), but it has a 
newer revision number (32) and the suggested fixes work only partially and the 
wireless is unusable.

  The computer has just been released this summer and is Intel Skylake
  -based.

  I've tried the patch from bug 1383184, which has a fix for the card revision 
20:
  Make the directory /lib/firmware/ath10k/QCA6174/hw3.0/ and put in the patch 
files:
  board.bin
  firmware-4.bin
  notice_ath10k_firmware-4.txt

  ath10k_pci succeeds in loading the firmware, but it seems that the
  firmware is not working correctly:

  dmesg | grep ath
  [5.452683] ath10k_pci :07:00.0: pci irq msi-x interrupts 8 irq_mode 0 
reset_mode 0
  [5.678420] ath10k_pci :07:00.0: Direct firmware load for 
ath10k/cal-pci-:07:00.0.bin failed with error -2
  [5.678773] ath10k_pci :07:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/board-pci-168c:003e:11ad:0807.bin failed with error -2
  [5.678781] ath10k_pci :07:00.0: failed to load spec board file, 
falling back to generic: -2
  [5.679445] ath10k_pci :07:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
  [5.679453] ath10k_pci :07:00.0: could not fetch firmware file 
'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
  [7.802316] ath10k_pci :07:00.0: qca6174 hw3.2 (0x0503, 
0x00340aff, 168c:003e:11ad:0807 fallback) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 api 
4 htt 3.26 wmi 4 cal otp max_sta 32
  [7.802329] ath10k_pci :07:00.0: debug 0 debugfs 1 tracing 1 dfs 0 
testmode 0
  [8.200607] ath: EEPROM regdomain: 0x6c
  [8.200614] ath: EEPROM indicates we should expect a direct regpair map
  [8.200619] ath: Country alpha2 being used: 00
  [8.200621] ath: Regpair used: 0x6c
  [8.216605] ath10k_pci :07:00.0 wlp7s0: renamed from wlan0
  [   13.462029] ath10k_pci :07:00.0: failed to enable dynamic BW: -11
  [   16.461416] ath10k_pci :07:00.0: could not suspend target (-11)
  [   24.760062] ath10k_pci :07:00.0: failed to enable dynamic BW: -11
  [   

[Kernel-packages] [Bug 1520343] Re: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported

[AceLan Kao]

** Tags added: originate-from-1734862 somerville

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

Title:
  Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  ---

  STATUS 2016-03-17:

  ==
  WARNING: You need at least kernel 4.5.0 for the following new fix to work, 
else refer to the old method described in post #22
  ==

  The support for this card has now been merged to
  https://github.com/kvalo/ath10k-firmware. The repository now contains
  the required board.bin, board-2.bin and firmware-4.bin files for the
  card to initialize and connect to a bgn-access point (5GHz (ac-
  protocol) is still untested, feel free to modify this if you can
  confirm it works). Here are the new commands to get you online:

  sudo mkdir -p /lib/firmware/ath10k/QCA6174/hw3.0/

  sudo rm /lib/firmware/ath10k/QCA6174/hw3.0/* 2> /dev/null

  sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board.bin
  https://github.com/kvalo/ath10k-
  firmware/blob/master/QCA6174/hw3.0/board.bin?raw=true

  sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin
  https://github.com/kvalo/ath10k-
  firmware/blob/master/QCA6174/hw3.0/board-2.bin?raw=true

  sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/firmware-4.bin
  https://github.com/kvalo/ath10k-
  
firmware/blob/master/QCA6174/hw3.0/firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1?raw=true

  Reboot or reload the ath10k_pci module and you should be able to
  connect!

  ---

  STATUS 2015-12-22:

  Currently there is a fix for this problem in post #22 (originally post
  #19, but reposted due to command typos!) which seems to have fixed the
  issue for many. This bug is unique to revision 32 of the card
  [168c:003e], fixes for older revisions don't seem to work.

  There are a couple of issues regarding the fix for some people (not
  all):

  1. Wireless works, but network throughput stops some time after
  connecting to access point

  2. Bluetooth communications take a noticeable performance hit when
  transferring something over WiFi

  ---

  Original description:

  I have recently installed Ubuntu 15.10 (64-bit) alongside Windows 10 on an 
Acer Aspire VN7-792G-76ZH and discovered, that the Qualcomm wireless card 
doesn't work in it or 16.04.
  The card has the device id 168c:003e as many other cards, for example the 
Qualcomm Atheros Killer 
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184), but it has a 
newer revision number (32) and the suggested fixes work only partially and the 
wireless is unusable.

  The computer has just been released this summer and is Intel Skylake
  -based.

  I've tried the patch from bug 1383184, which has a fix for the card revision 
20:
  Make the directory /lib/firmware/ath10k/QCA6174/hw3.0/ and put in the patch 
files:
  board.bin
  firmware-4.bin
  notice_ath10k_firmware-4.txt

  ath10k_pci succeeds in loading the firmware, but it seems that the
  firmware is not working correctly:

  dmesg | grep ath
  [5.452683] ath10k_pci :07:00.0: pci irq msi-x interrupts 8 irq_mode 0 
reset_mode 0
  [5.678420] ath10k_pci :07:00.0: Direct firmware load for 
ath10k/cal-pci-:07:00.0.bin failed with error -2
  [5.678773] ath10k_pci :07:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/board-pci-168c:003e:11ad:0807.bin failed with error -2
  [5.678781] ath10k_pci :07:00.0: failed to load spec board file, 
falling back to generic: -2
  [5.679445] ath10k_pci :07:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
  [5.679453] ath10k_pci :07:00.0: could not fetch firmware file 
'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
  [7.802316] ath10k_pci :07:00.0: qca6174 hw3.2 (0x0503, 
0x00340aff, 168c:003e:11ad:0807 fallback) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 api 
4 htt 3.26 wmi 4 cal otp max_sta 32
  [7.802329] ath10k_pci :07:00.0: debug 0 debugfs 1 tracing 1 dfs 0 
testmode 0
  [8.200607] ath: EEPROM regdomain: 0x6c
  [8.200614] ath: EEPROM indicates we should expect a direct regpair map
  [8.200619] ath: Country alpha2 being used: 00
  [8.200621] ath: Regpair used: 0x6c
  [8.216605] ath10k_pci :07:00.0 wlp7s0: renamed from wlan0
  [   13.462029] ath10k_pci :07:00.0: failed to enable dynamic BW: -11
  [   16.461416] ath10k_pci :07:00.0: could not suspend target (-11)
  [   24.760062] ath10k_pci :07:00.0: failed to enable dynamic BW: -11
  [   27.759534] ath10k_pci :07:00.0: could not suspend target (-11)
  [   36.046205] ath10k_pci 

[Kernel-packages] [Bug 1520343] Re: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported

[Alex Tu]

** Tags added: lp1734862

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

** Project changed: ubuntux => oem-priority

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

Title:
  Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  ---

  STATUS 2016-03-17:

  ==
  WARNING: You need at least kernel 4.5.0 for the following new fix to work, 
else refer to the old method described in post #22
  ==

  The support for this card has now been merged to
  https://github.com/kvalo/ath10k-firmware. The repository now contains
  the required board.bin, board-2.bin and firmware-4.bin files for the
  card to initialize and connect to a bgn-access point (5GHz (ac-
  protocol) is still untested, feel free to modify this if you can
  confirm it works). Here are the new commands to get you online:

  sudo mkdir -p /lib/firmware/ath10k/QCA6174/hw3.0/

  sudo rm /lib/firmware/ath10k/QCA6174/hw3.0/* 2> /dev/null

  sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board.bin
  https://github.com/kvalo/ath10k-
  firmware/blob/master/QCA6174/hw3.0/board.bin?raw=true

  sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin
  https://github.com/kvalo/ath10k-
  firmware/blob/master/QCA6174/hw3.0/board-2.bin?raw=true

  sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/firmware-4.bin
  https://github.com/kvalo/ath10k-
  
firmware/blob/master/QCA6174/hw3.0/firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1?raw=true

  Reboot or reload the ath10k_pci module and you should be able to
  connect!

  ---

  STATUS 2015-12-22:

  Currently there is a fix for this problem in post #22 (originally post
  #19, but reposted due to command typos!) which seems to have fixed the
  issue for many. This bug is unique to revision 32 of the card
  [168c:003e], fixes for older revisions don't seem to work.

  There are a couple of issues regarding the fix for some people (not
  all):

  1. Wireless works, but network throughput stops some time after
  connecting to access point

  2. Bluetooth communications take a noticeable performance hit when
  transferring something over WiFi

  ---

  Original description:

  I have recently installed Ubuntu 15.10 (64-bit) alongside Windows 10 on an 
Acer Aspire VN7-792G-76ZH and discovered, that the Qualcomm wireless card 
doesn't work in it or 16.04.
  The card has the device id 168c:003e as many other cards, for example the 
Qualcomm Atheros Killer 
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184), but it has a 
newer revision number (32) and the suggested fixes work only partially and the 
wireless is unusable.

  The computer has just been released this summer and is Intel Skylake
  -based.

  I've tried the patch from bug 1383184, which has a fix for the card revision 
20:
  Make the directory /lib/firmware/ath10k/QCA6174/hw3.0/ and put in the patch 
files:
  board.bin
  firmware-4.bin
  notice_ath10k_firmware-4.txt

  ath10k_pci succeeds in loading the firmware, but it seems that the
  firmware is not working correctly:

  dmesg | grep ath
  [5.452683] ath10k_pci :07:00.0: pci irq msi-x interrupts 8 irq_mode 0 
reset_mode 0
  [5.678420] ath10k_pci :07:00.0: Direct firmware load for 
ath10k/cal-pci-:07:00.0.bin failed with error -2
  [5.678773] ath10k_pci :07:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/board-pci-168c:003e:11ad:0807.bin failed with error -2
  [5.678781] ath10k_pci :07:00.0: failed to load spec board file, 
falling back to generic: -2
  [5.679445] ath10k_pci :07:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
  [5.679453] ath10k_pci :07:00.0: could not fetch firmware file 
'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
  [7.802316] ath10k_pci :07:00.0: qca6174 hw3.2 (0x0503, 
0x00340aff, 168c:003e:11ad:0807 fallback) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 api 
4 htt 3.26 wmi 4 cal otp max_sta 32
  [7.802329] ath10k_pci :07:00.0: debug 0 debugfs 1 tracing 1 dfs 0 
testmode 0
  [8.200607] ath: EEPROM regdomain: 0x6c
  [8.200614] ath: EEPROM indicates we should expect a direct regpair map
  [8.200619] ath: Country alpha2 being used: 00
  [8.200621] ath: Regpair used: 0x6c
  [8.216605] ath10k_pci :07:00.0 wlp7s0: renamed from wlan0
  [   13.462029] ath10k_pci :07:00.0: failed to enable dynamic BW: -11
  [   16.461416] ath10k_pci :07:00.0: could not suspend target (-11)
  [   24.760062] ath10k_pci :07:00.0: failed to enable dynamic BW: -11
  [   27.759534] 

[Kernel-packages] [Bug 1698700] Re: hibmc driver does not include "pci:" prefix in bus ID

[Fred Kimmy]

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

** No longer affects: linux

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

Title:
  hibmc driver does not include "pci:" prefix in bus ID

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

Bug description:
  SRU Justification

  [Impact]
  On the HiSilicon D05 (arm64) board, X crashes when started. [0]

  [Fix]
  The crash is attributable to the bus ID that the hibmc driver reports for the 
hibmc graphics card on the board. In particular, the bus id is missing the 
"pci:" prefix that most other cards provide: [1]
  - The busid reported on the arm64 system is "0007:a1:00.0"
  - The busid reported on a amd64 system is "pci::00:02.0"

  X tests for this prefix. A missing prefix for PCI cards leads to an
  Xorg crash.

  Fix this by using the set_pci_busid function from the DRM core.

  [Testcase]
  Successfully tested on a D05 board. [2]

  [Regression Potential]
  Changes are limited to the hibmc driver, so any regression should also be 
limited to that driver.

  [Notes]
  I submitted the patch upstream. However, upstream is refactoring the drm 
core, and set_busid is going away. That does fix this issue but the regression 
potential of the refactor is enormous, so this seems like the wiser approach. 
[3]

  [0]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991
  [1]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/16
  [2]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/29
  [3]: https://www.spinics.net/lists/dri-devel/msg143831.html

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

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

[Kernel-packages] [Bug 1733546] Re: linux-aws: 4.4.0-1042.51 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

Title:
  linux-aws: 4.4.0-1042.51 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1733541
  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/1733546/+subscriptions

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

[Kernel-packages] [Bug 1733541] Re: linux: 4.4.0-102.125 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   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/1733541

Title:
  linux: 4.4.0-102.125 -proposed tracker

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

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

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

  backports: 1733542,1733543
  derivatives: 1733544,1733546,1733547,1733548,1733549,1733550
  -- 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/1733541/+subscriptions

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

[Kernel-packages] [Bug 1733530] Re: linux: 4.13.0-18.21 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   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/1733530

Title:
  linux: 4.13.0-18.21 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  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: 1733532,1733533,1733534,1733535
  derivatives: 1733536
  -- 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/1733530/+subscriptions

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Cannot boot without acpi=off

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bought a new laptop but after reinstalling cannot boot without
  acpi=off

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-generic 4.13.0.17.18
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arseniuss954 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Nov 29 02:25:57 2017
  InstallationDate: Installed on 2017-11-26 (2 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:2ca0 Sunplus Innovation Technology Inc. 
   Bus 001 Device 002: ID 04ca:3016 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Nitro AN515-51
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed 
root=UUID=7105a1eb-3d1e-4b00-9668-da7cce948f4e ro acpi=off
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.05
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Freed_KLS
  dmi.board.vendor: KBL
  dmi.board.version: V1.05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd05/18/2017:svnAcer:pnNitroAN515-51:pvrV1.05:rvnKBL:rnFreed_KLS:rvrV1.05:cvnAcer:ct10:cvrV1.05:
  dmi.product.family: Acer Nitro 5
  dmi.product.name: Nitro AN515-51
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1735024] [NEW] Cannot boot without acpi=off

[Armands Skolmeisters]

Public bug reported:

Bought a new laptop but after reinstalling cannot boot without acpi=off

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-generic 4.13.0.17.18
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  arseniuss954 F pulseaudio
CurrentDesktop: KDE
Date: Wed Nov 29 02:25:57 2017
InstallationDate: Installed on 2017-11-26 (2 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1bcf:2ca0 Sunplus Innovation Technology Inc. 
 Bus 001 Device 002: ID 04ca:3016 Lite-On Technology Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Nitro AN515-51
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed 
root=UUID=7105a1eb-3d1e-4b00-9668-da7cce948f4e ro acpi=off
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-17-generic N/A
 linux-backports-modules-4.13.0-17-generic  N/A
 linux-firmware 1.169
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/18/2017
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.05
dmi.board.asset.tag: Type2 - Board Serial Number
dmi.board.name: Freed_KLS
dmi.board.vendor: KBL
dmi.board.version: V1.05
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.05
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd05/18/2017:svnAcer:pnNitroAN515-51:pvrV1.05:rvnKBL:rnFreed_KLS:rvrV1.05:cvnAcer:ct10:cvrV1.05:
dmi.product.family: Acer Nitro 5
dmi.product.name: Nitro AN515-51
dmi.product.version: V1.05
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug artful

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

Title:
  Cannot boot without acpi=off

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bought a new laptop but after reinstalling cannot boot without
  acpi=off

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-generic 4.13.0.17.18
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arseniuss954 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Nov 29 02:25:57 2017
  InstallationDate: Installed on 2017-11-26 (2 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:2ca0 Sunplus Innovation Technology Inc. 
   Bus 001 Device 002: ID 04ca:3016 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Nitro AN515-51
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed 
root=UUID=7105a1eb-3d1e-4b00-9668-da7cce948f4e ro acpi=off
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.05
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Freed_KLS
  dmi.board.vendor: KBL
  dmi.board.version: V1.05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd05/18/2017:svnAcer:pnNitroAN515-51:pvrV1.05:rvnKBL:rnFreed_KLS:rvrV1.05:cvnAcer:ct10:cvrV1.05:
  dmi.product.family: Acer Nitro 5
  dmi.product.name: Nitro AN515-51
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1729119] Re: NVMe timeout is too short

[Eric Desrochers]

[VERIFICATION ZESTY]

# rmadison
linux-image-4.10.0-41-generic | 4.10.0-41.45 | zesty-proposed  | amd64, 
arm64, armhf, i386, ppc64el, s390x


# lsb_release -r
Release:17.04


# apt-get changelog linux-image-4.10.0-41-generic | grep -A2 1729119
  * NVMe timeout is too short (LP: #1729119)
- nvme: update timeout module parameter type


# uname -r
4.10.0-41-generic


I had no nvme drive at my disposal but the following test should suffice :

# lsmod | grep -i nvme

# modprobe nvme_core io_timeout=123456

# lsmod | grep -i nvme
nvme_core  57344  0

# cat /sys/module/nvme_core/parameters/io_timeout 
123456


** Note that it doesn't seems to work at runtime (if the module is already 
loaded). It only works when the module haven't been previously loaded for some 
reasons **

But I don't see this as a blocker for the current SRU.

root@zesty:~# lsmod | grep -i nvme
nvme_core  57344  0

root@zesty:~# modprobe nvme_core io_timeout=123457

root@zesty:~# cat /sys/module/nvme_core/parameters/io_timeout 
123456

- Eric



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

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

Title:
  NVMe timeout is too short

Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux-aws source package in Trusty:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in linux-aws source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed
Status in linux-aws source package in Zesty:
  Invalid
Status in linux source package in Artful:
  Fix Committed
Status in linux-aws source package in Artful:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  Some NVMe operations time out too quickly. The module parameters allow the 
timeouts to be extended, but only up to 255s, as the counters are bytes.

  [Fix]
  The underlying parameters are unsigned ints, so make the module parameters 
unsigned ints too, by picking patch 
http://lists.infradead.org/pipermail/linux-nvme/2017-September/012701.html

  (Trusty specific) This also requires picking the patch that converts
  the constant into a parameter, which is a clean cherry-pick.

  [Regression Potential]
  (X/Z/A) Very limited: only types of module parameters are changing, the patch 
is easily reviewable.

  (Trusty specific) Limited: a module parameter is added and its type is
  changed. The patches are easily reviewable.

  [Testing]
  (Trusty only) Boot tested on a c5.large instance on AWS which uses
  NVMe to boot. Verified that the system still boots with the patches,
  and that a timeout of 123456s is permitted.

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

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

[Kernel-packages] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72

[Sitsofe Wheeler]

As predicted 4.11.0-1015-azure #15-Ubuntu doesn't have the problem and
you see output like this:

[   24.635325] sd 1:0:0:0: Attached scsi generic sg2 type 0
[   24.638674] sd 1:0:0:0: [sdb] 500118192 512-byte logical blocks: (256 GB/238 
GiB)
[   24.641194] sd 1:0:0:0: [sdb] Write Protect is off
[   24.641197] sd 1:0:0:0: [sdb] Mode Sense: 0f 00 00 00
[   24.643644] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[   24.653398] sd 1:0:0:0: [sdb] Attached SCSI disk
[   24.741813] sd 1:0:0:0: [storvsc] Sense Key : Illegal Request [current] 
[   24.741818] sd 1:0:0:0: [storvsc] Add. Sense: Invalid command operation code
[   24.743397] sd 1:0:0:0: [storvsc] Sense Key : Illegal Request [current] 
[   24.743400] sd 1:0:0:0: [storvsc] Add. Sense: Invalid command operation code

It is also broken in 4.8.0-46-generic #49~16.04.1-Ubuntu and fixed in
4.8.0-49-generic #52~16.04.1-Ubuntu and broken on 4.4.0-71-generic
#92-Ubuntu and fixed in 4.4.0-75-generic #96-Ubuntu (driver history is
http://kernel.ubuntu.com/git/ubuntu/ubuntu-
xenial.git/log/drivers/scsi/storvsc_drv.c?h=Ubuntu-4.4.0-75.96 in it) so
it appears my previous 4.4.0 kernel simply wasn't new enough.

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

Title:
  [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration
  after installing kernel 4.4.0-72

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

Bug description:
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's 
on Hyper-V.
  Microsoft Hyper-v 2012r2 Gen2 VMs

  See Attachment for what happens is immediately after backup starts I
  get an error.

  Eventually the kernel reports it has run out of memory and the machine
  just continuously scrolls errors message related to page allocation.

  When reseting the virtual machine no logs can be found of the problem.

  kernel 4.4.0-72-generic problem still here

  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  SourcePackage: linux-lts-xenial
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  5 12:05 seq
   crw-rw 1 root audio 116, 33 Apr  5 12:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-72-generic N/A
   linux-backports-modules-4.4.0-72-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 

[Kernel-packages] [Bug 1504227] Re: Sound output starts several seconds late using DisplayPort with [AMD/ATI] Tahiti XT HDMI Audio [Radeon HD 7970 Series] [1002:aaa0]

[Etienne URBAH]

** Tags removed: kernel-bug-exists-upstream-4.13
** Tags added: kernel-bug-exists-upstream-4.15

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

Title:
  Sound output starts several seconds late using DisplayPort with
  [AMD/ATI] Tahiti XT HDMI Audio [Radeon HD 7970 Series] [1002:aaa0]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I am using simultaneously :
  -  an audio headset connected to the analog audio output,
  -  a DisplayPort cable to connect my display to my 'AMD Tahiti XT [Radeon HD 
7970 ...]' graphics + sound card.

  Using the 'Sound' panel of 'gnome-control-center', I systematically
  get following behaviour for sound output :

  -  If I choose the 'Line Out - Built-in Audio' device, the sound output comes 
immediately :
     For example, inside the 'Test Speakers' window, the correct sound 
systematically starts as soon as I hit any 'Test' button (under 'Front Left' or 
'Front Right').

  -  But if I choose the 'HDMI / DisplayPort - Tahiti XT HDMI Audio [Radeon HD 
7970 Series]' device, the sound output starts several seconds LATE :
     For example, inside the 'Test Speakers' window, the sound starts at the 
end of the 2nd time I hit any 'Test' button (under 'Front Left' or 'Front 
Right').  Then continuous sound is correct and in sync.
     But after approx. 10s of silence (no sound to output), new sound output 
starts several seconds LATE again.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-14-generic 4.2.0-14.16
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   z_admin1665 F...m pulseaudio
   /dev/snd/controlC0:  z_admin1665 F pulseaudio
   /dev/snd/controlC1:  z_admin1665 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Oct  8 17:46:05 2015
  HibernationDevice: RESUME=UUID=ccecc437-66d2-4e39-ac56-76ab11e18140
  InstallationDate: Installed on 2015-09-27 (10 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  IwConfig:
   enp2s0no wireless extensions.

   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic 
root=UUID=a5c156d8-eac3-47fa-835c-b2c4ebda969d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-14-generic N/A
   linux-backports-modules-4.2.0-14-generic  N/A
   linux-firmware1.149
  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: 04/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Kernel-packages] [Bug 1729736] Re: 10de:1c8c [MSI] Module nouveau fails to manage GeForce GTX 1050 Ti Mobile

[Etienne URBAH]

At https://bugs.freedesktop.org/ :

-  Product 'DRI' has NO component 'DRM/nouveau'.

-  In fact, this issue is already reported at
https://bugs.freedesktop.org/show_bug.cgi?id=101665 inside product
'xorg', component 'Driver/nouveau'.

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

Title:
  10de:1c8c [MSI] Module nouveau fails to manage GeForce GTX 1050 Ti
  Mobile

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Trying to use 'Nvidia GeForce GTX 1050 Ti Mobile' with 'Ubuntu 17.10
  (Artful)' :

  - Linux kernel 4.13.0-16 from 'Ubuntu 17.10 (Artful)' systematically
  fails (1 CPU stuck).

  - Linux kernel 4.14.0-041400rc7 from http://kernel.ubuntu.com/~kernel-
  ppa/mainline seems to succeed.

  See attached kern.log

  
  After reboot on Linux kernel 4.13.0-16 with nouveau blacklisted :

  $ lspci -nn -v -s 1:0.0

  01:00.0 3D controller [0302]: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti 
Mobile] [10de:1c8c] (rev a1)
Subsystem: Micro-Star International Co., Ltd. [MSI] GP107M [GeForce GTX 
1050 Ti Mobile] [1462:11c8]
Flags: bus master, fast devsel, latency 0, IRQ 255
Memory at de00 (32-bit, non-prefetchable) [size=16M]
Memory at c000 (64-bit, prefetchable) [size=256M]
Memory at d000 (64-bit, prefetchable) [size=32M]
I/O ports at e000 [disabled] [size=128]
Expansion ROM at df00 [disabled] [size=512K]
Capabilities: 
Kernel modules: nvidiafb, nouveau

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

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

[Kernel-packages] [Bug 1729573] Re: netplan breaks Xen VIF driver

[Mathieu Trudel-Lapierre]

** Tags removed: verification-failed

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

Title:
  netplan breaks Xen VIF driver

Status in linux package in Ubuntu:
  Won't Fix
Status in nplan package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in nplan source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Won't Fix
Status in nplan source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Won't Fix
Status in nplan source package in Artful:
  In Progress
Status in linux source package in Bionic:
  Won't Fix
Status in nplan source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  Some network interfaces on a Xen guest are broken by new behavior
  introduced by netplan.  On a Xen guest instance, when netplan is run
  to 'apply' its configuration, under certain circumstances netplan will
  try to "reset" the interface by unbinding and then re-binding the
  interface driver from the interface, by using the sysfs "bind" and
  "unbind" functions of the driver.  Normally, this results in the
  interface being released and then fully re-initialized by the driver.

  However the Xen VIF driver breaks when this is done.  The internal Xen
  backend state of the interface remains in 'closed' state after the
  driver re-connects to the interface, and attempts to open and use the
  interface result in a kernel Oops in the Xen VIF driver.

  To users, it appears that the interface is unusable because it has an
  all 0 mac address; but if the mac is manually set and the interface
  brought up the driver Oopses as mentioned above.

  This problem makes booting painful because of very long timeouts
  waiting for all network interfaces to start, and affected Xen VIF
  interfaces will of course never complete startup.

  [Fix]

  No fix yet.  Upstream kernel does not appear fixed.

  [Test Case]

  Create a guest instance under a Xen hypervisor (e.g. an AWS instance)
  that has Ubuntu Artful 17.10 installed.  Use only a single interface
  at first when creating it.  Then once it is ready, attach a second
  network interface to the instance.  From inside the instance,
  configure the new interface in netplan (i.e. add a /etc/netplan/
  config for it).  Make sure the new interface is down (netplan does not
  appear to unbind/bind interfaces that are up), and then run:

  $ sudo netplan apply

  or for debug,

  $ sudo netplan --debug apply

  this will unbind and re-bind the second interface, which will then
  have all-0 mac, and will be unusable, as described above.

  [Regression Potential]

  Changes to the Xen VIF driver can result in unusable network
  interfaces, or problems while using Xen VIF interfaces.

  [Other Info]

  Problem appears to exist upstream also.

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

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

[Kernel-packages] [Bug 1734733] Re: linux: 3.13.0-136.185 -proposed tracker

[Brad Figg]

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

** Tags added: block-proposed-trusty

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1734734
  derivatives:
  kernel-stable-phase-changed:Tuesday, 28. November 2017 16:01 UTC
  kernel-stable-phase:Uploaded
  
  -- swm properties --
+ boot-testing-requested: true
  phase: Uploaded

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

Title:
  linux: 3.13.0-136.185 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  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:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

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

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

  backports: 1734734
  derivatives:
  kernel-stable-phase-changed:Tuesday, 28. November 2017 16:01 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1734734] Re: linux-lts-trusty: 3.13.0-136.185~precise1 -proposed tracker

[Brad Figg]

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

** Tags added: block-proposed-precise

** Tags added: block-proposed

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

Title:
  linux-lts-trusty: 3.13.0-136.185~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  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:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1734733
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1728762] Re: Update iwlwifi firmware for 3160, 3168, 7260, 7265 and 7265D

[Seth Forshee]

Verified that the firmware files in each package match the files from
upstream which were identified as containing the CVE fixes.

** Tags added: verification-done-artful verification-done-trusty
verification-done-xenial 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/1728762

Title:
  Update iwlwifi firmware for 3160, 3168, 7260, 7265 and 7265D

Status in intel:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Trusty:
  Fix Committed
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Zesty:
  Fix Committed
Status in linux-firmware source package in Artful:
  Fix Committed
Status in linux-firmware source package in Bionic:
  Fix Released

Bug description:
  SRU Justification

  Impact: Intel wireless firmware WoWLAN functionality is vulnerable to
  some CVEs from the KRACK attack vulnerabilities, CVE-2017-13080 and
  CVE-2017-13081.

  Fix: Updated firmware from Intel containing fixes for these
  vulnerabilities.

  Test Case: Difficult to test; we are reliant on testing done by Intel.

  Regression Potential: There is always some possibility for regressions
  with firmware updates, but as these are bug fix updates the regression
  potential is minimal. I have been using the 7260 firmware for over a
  week now without issue.

  ---

  There are two parts of WIFI firmware update. Please double check if
  Ubuntu release has include them.

  A new firmware version for 8260 and 8265 WiFi devices.
  This our Core31 release (-34.ucode).
  
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=348d2b53326bcef4c260037cc7a6006fc80ca5bb

  A new firmware version  for 3160, 3168, 7260, 7265 and 7265D
  Note: This firmware version hasn't been pulled into mainline yet.
  This includes a security fix.
  The patch in iwlwifi/linux-firmware.git is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=11e310f97470f91e26e6f3408b09871fd6cd3c5c

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

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

[Kernel-packages] [Bug 1733901] Re: /build/linux-KM2a5S/linux-4.13.0/drivers/usb/core/devio.c is crashing on kvm / qemu machine bootup

[Brian Hampel]

@peter-maloney thanks for testing this!

@jsalisbury Added tag "kernel-fixed-upstream" and set it to confirmed.

** Tags added: kernel-fixed-upstream

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

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

Title:
  /build/linux-KM2a5S/linux-4.13.0/drivers/usb/core/devio.c is crashing
  on kvm / qemu machine bootup

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  since the upgrade to kernel 4.13.0-17 on ubuntu mate 17.10 the usb
  module is crashing if I bootup my windows 10 kvm / qemu machine. Its
  managed via virtmanager.

  Here is the trace:

  Nov 22 16:37:24 octo kernel: [  789.262361] [ cut here 
]
  Nov 22 16:37:24 octo kernel: [  789.262365] WARNING: CPU: 0 PID: 2978 at 
/build/linux-KM2a5S/linux-4.13.0/drivers/usb/core/devio.c:1583 
proc_do_submiturb+0x993/0xd50
  Nov 22 16:37:24 octo kernel: [  789.262365] Modules linked in: vhost_net 
vhost macvtap macvlan tap bnep ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_co
  nntrack nf_conntrack xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 
xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter nls_iso8859_1 snd_hda_codec_hdmi snd_usb_audio
   snd_usbmidi_lib snd_seq_midi snd_hda_codec_realtek snd_seq_midi_event 
snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp 
kvm_intel uvcvideo kvm snd_rawmidi videobuf2_vmalloc videobuf2_memops
   videobuf2_v4l2 snd_hda_intel videobuf2_core intel_cstate snd_hda_codec 
videodev snd_seq intel_rapl_perf snd_hda_core snd_seq_device media snd_hwdep 
snd_pcm serio_raw snd_timer eeepc_wmi snd asus_wmi mei_me
  Nov 22 16:37:24 octo kernel: [  789.262387]  sparse_keymap wmi_bmof soundcore 
input_leds joydev shpchp mei hci_uart btbcm serdev btqca btintel bluetooth 
ecdh_generic intel_lpss_acpi intel_lpss acpi_als acpi_pad 
  kfifo_buf mac_hid industrialio coretemp vfio_pci vfio_virqfd irqbypass 
vfio_iommu_type1 vfio parport_pc ppdev lp parport ip_tables x_tables autofs4 
algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov
   async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 
multipath linear raid1 hid_generic usbhid mxm_wmi i915 crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 i2c_alg
  o_bit crypto_simd drm_kms_helper glue_helper cryptd syscopyarea e1000e 
sysfillrect sysimgblt fb_sys_fops psmouse ptp drm pps_core ahci libahci wmi 
video pinctrl_sunrisepoint i2c_hid pinctrl_intel hid
  Nov 22 16:37:24 octo kernel: [  789.262416] CPU: 0 PID: 2978 Comm: 
qemu-system-x86 Not tainted 4.13.0-17-generic #20-Ubuntu
  Nov 22 16:37:24 octo kernel: [  789.262416] Hardware name: System 
manufacturer System Product Name/PRIME Z270-A, BIOS 0906 03/22/2017
  Nov 22 16:37:24 octo kernel: [  789.262417] task: 95633c5b5f00 
task.stack: b6e844318000
  Nov 22 16:37:24 octo kernel: [  789.262418] RIP: 
0010:proc_do_submiturb+0x993/0xd50
  Nov 22 16:37:24 octo kernel: [  789.262419] RSP: 0018:b6e84431bd38 
EFLAGS: 00010282
  Nov 22 16:37:24 octo kernel: [  789.262420] RAX: 002a RBX: 
9562b500c6c0 RCX: 8905fd08
  Nov 22 16:37:24 octo kernel: [  789.262420] RDX:  RSI: 
0092 RDI: 0247
  Nov 22 16:37:24 octo kernel: [  789.262421] RBP: b6e84431bdc0 R08: 
002a R09: 040e
  Nov 22 16:37:24 octo kernel: [  789.262421] R10: 0200 R11: 
 R12: 0001
  Nov 22 16:37:24 octo kernel: [  789.262422] R13: 95659f8b3540 R14: 
55ef781efcf8 R15: b6e84431be00
  Nov 22 16:37:24 octo kernel: [  789.262423] FS:  7f88e0b39c80() 
GS:9565bec0() knlGS:
  Nov 22 16:37:24 octo kernel: [  789.262423] CS:  0010 DS:  ES:  CR0: 
80050033
  Nov 22 16:37:24 octo kernel: [  789.262424] CR2: f80029b18800 CR3: 
0001e146d000 CR4: 003426f0
  Nov 22 16:37:24 octo kernel: [  789.262424] DR0:  DR1: 
 DR2: 
  Nov 22 16:37:24 octo kernel: [  789.262425] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Nov 22 16:37:24 octo kernel: [  789.262425] Call Trace:
  Nov 22 16:37:24 octo kernel: [  789.262429]  ? 
compat_poll_select_copy_remaining+0x120/0x120
  Nov 22 16:37:24 octo kernel: [  789.262430]  usbdev_do_ioctl+0xa34/0x1170
  Nov 22 16:37:24 octo kernel: [  789.262431]  ? 
compat_poll_select_copy_remaining+0x120/0x120
  Nov 22 16:37:24 octo kernel: [  789.262433]  usbdev_ioctl+0xe/0x20
  Nov 22 16:37:24 octo kernel: [  789.262434]  do_vfs_ioctl+0xa5/0x610
  Nov 22 16:37:24 octo kernel: [  789.262435]  SyS_ioctl+0x79/0x90
  Nov 22 16:37:24 octo kernel: [  789.262437]  

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

[Ben Noordhuis]

If it helps, I got a similar but not identical error today.  It's the
`BUG_ON(!PageCompound(page))` in the `!PageSlab(page)` branch inside
kfree().

[18592.784836] [ cut here ]
[18592.784837] kernel BUG at /build/linux-KM2a5S/linux-4.13.0/mm/slub.c:3878!
[18592.784841] invalid opcode:  [#1] PREEMPT SMP
[18592.784849] Modules linked in: xt_tcpudp iptable_filter cfg80211 binfmt_misc 
snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm snd_hda_codec_realtek irqbypass snd_hda_codec_generic r8712u(C) 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel pcbc 
snd_hda_codec input_leds aesni_intel aes_x86_64 crypto_simd glue_helper cryptd 
snd_hda_core snd_hwdep intel_cstate intel_rapl_perf snd_seq_midi snd_pcm 
snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd mei_me 
soundcore mei lpc_ich shpchp ie31200_edac mac_hid cuse parport_pc ppdev lp 
parport ip_tables x_tables autofs4 nouveau mxm_wmi wmi i2c_algo_bit ttm 
drm_kms_helper syscopyarea sysfillrect hid_generic sysimgblt fb_sys_fops uas 
ahci usbhid usb_storage drm r8169 libahci hid mii video
[18592.784900] CPU: 7 PID: 15983 Comm: cctest Tainted: G C  
4.13.0-17-lowlatency #20-Ubuntu
[18592.784904] Hardware name: MEDION H77H2-EM/H77H2-EM, BIOS EM0411-M8 
04/11/2012
[18592.784907] task: 8b9f42ad4c80 task.stack: a900cd9bc000
[18592.784913] RIP: 0010:kfree+0x144/0x190
[18592.784916] RSP: 0018:a900cd9bfd50 EFLAGS: 00010246
[18592.784919] RAX: db6b8e5c7fa0 RBX:  RCX: 0002
[18592.784922] RDX:  RSI: 00010080 RDI: 00031720
[18592.784925] RBP: a900cd9bfd68 R08: 0001f640 R09: 83fc7979
[18592.784929] R10: db6b8e5c7fc0 R11:  R12: 8b9dd7fa5000
[18592.784934] R13: 83baa5ee R14:  R15: 8b9f4c6110a0
[18592.784937] FS:  7f70c231eb80() GS:8b9f5edc() 
knlGS:
[18592.784941] CS:  0010 DS:  ES:  CR0: 80050033
[18592.784944] CR2: 7ffd2000fee8 CR3: 00040bf6b000 CR4: 001406e0
[18592.784947] Call Trace:
[18592.784953]  security_sk_free+0x3e/0x50
[18592.784958]  __sk_destruct+0x108/0x190
[18592.784961]  sk_destruct+0x20/0x30
[18592.784964]  __sk_free+0x82/0xa0
[18592.784967]  sk_free+0x19/0x20
[18592.784971]  tcp_close+0x230/0x3f0
[18592.784975]  inet_release+0x3c/0x60
[18592.784978]  sock_release+0x1f/0x80
[18592.784980]  sock_close+0x12/0x20
[18592.784984]  __fput+0xe1/0x220
[18592.784987]  fput+0xe/0x10
[18592.784991]  task_work_run+0x76/0x90
[18592.784995]  exit_to_usermode_loop+0xc4/0xd0
[18592.784998]  syscall_return_slowpath+0x59/0x60
[18592.785002]  entry_SYSCALL_64_fastpath+0xa7/0xa9
[18592.785006] RIP: 0033:0x7f70c122cdf0
[18592.785008] RSP: 002b:7ffd20010a10 EFLAGS: 0293 ORIG_RAX: 
0003
[18592.785012] RAX:  RBX: 000c RCX: 7f70c122cdf0
[18592.785015] RDX:  RSI: 0002 RDI: 000c
[18592.785018] RBP: 7ffd20010a50 R08: 5563aae89a50 R09: 7ffd20010a50
[18592.785021] R10: 7ffd20010a3c R11: 0293 R12: 7f70c231ead8
[18592.785024] R13: 0011 R14: 5563aa1bbeb8 R15: 5563aa1bc140
[18592.785028] Code: 85 c0 75 e6 65 ff 0d 8c e4 5d 7c 0f 85 f0 fe ff ff e8 ee 
40 dd ff e9 e6 fe ff ff 49 8b 02 f6 c4 80 75 0a 49 8b 42 20 a8 01 75 02 <0f> 0b 
49 8b 02 31 f6 f6 c4 80 74 04 41 8b 72 6c 4c 89 d7 e8 a4 
[18592.785050] RIP: kfree+0x144/0x190 RSP: a900cd9bfd50
[18592.809568] ---[ end trace b46b59552a7a66b7 ]---

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

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I can consistently reproduce this with the Ubuntu 17.10 kernel.  It
  never happens with a mainline 4.13.11 kernel built from source.

  To reproduce:

  1. clone https://github.com/nodejs/node (currently at commit 4ca4db0d4c)
  2. ./configure && make -j8
  3. ./out/Release/cctest

  cctest is sometimes killed, sometimes locks up the computer.  When the
  computer is still usable, the following message is logged:

  [36488.886799] BUG: unable to handle kernel paging request at df3cd60001a0
  [36488.886824] IP: kfree+0x53/0x190
  [36488.886831] PGD 0 
  [36488.886831] P4D 0 

  [36488.886844] Oops:  [#2] PREEMPT SMP
  [36488.886851] Modules linked in: xt_tcpudp iptable_filter cfg80211 
binfmt_misc snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd 
snd_hda_codec_realtek snd_hda_codec_generic intel_cstate r8712u(C) 
intel_rapl_perf snd_seq_midi snd_seq_midi_event 

[Kernel-packages] [Bug 1708409] Re: kdump service does not start after configure/reboot

[Thadeu Lima de Souza Cascardo]

It seems this has been reverted on systemd 235. However, as this might
come to bite us back again in the future (it was mentioned that
dependencies should not be added to aliases), and as Steve has pointed
out, it makes more sense to use multi-user.target, I am going to fix it
in a future release to come soon.

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

Title:
  kdump service does not start after configure/reboot

Status in The Ubuntu-power-systems project:
  Triaged
Status in makedumpfile package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Triaged
Status in makedumpfile source package in Artful:
  New
Status in systemd source package in Artful:
  New
Status in makedumpfile source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Triaged

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

  ...
  https://github.com/systemd/systemd/issues/6334

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

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

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

[Kernel-packages] [Bug 1733524] Re: linux: 4.10.0-41.45 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   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/1733524

Title:
  linux: 4.10.0-41.45 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  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: 1733526,1733528
  derivatives: 1733529
  -- 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/1733524/+subscriptions

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

[Kernel-packages] [Bug 1719697] Re: Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940

[Sujith Pandel]

Thank you.
We will revert back with the findings on xenial-proposed kernel.

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

Title:
  Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940

Status in dellserver:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Fix Committed

Bug description:

  == SRU Justification ==
  Kernel crashes when installation of Ubuntu-16.04.3 with HWE (ISO).
  Same observation while booting to 4.10.0-28 HWE kerenl of Ubuntu-16.04.3
  and 4.10.0-33 HWE as well.

  Seen only with 4.10 HWE kernels of Ubuntu-16.04.3.  4.4 kernels of
  Ubuntu-16.04.3 works fine. Daily builds of Ubuntu Server 17.10 works fine.

  Reducing the core count to <26 cores helps here. Boot & installation of
  HWE-kernel works fine.

  This bug was introduced by commit:
  dc6db24d2476 ("x86/acpi: Set persistent cpuid <-> nodeid mapping when 
booting")

  It is resolved by reverting commit dc6db24d2476, which was done in mainline 
by 
  commit c962cff17df as of v4.11-rc3.

  There are three additiona commits introduced by the same patch author when
  commit c962cff17df was submitted.  However, it was confirmed that only the 
single
  revert is needed to fix this particular bug.  Upstream thread:
   https://lkml.org/lkml/2017/2/20/66

  == Fix ==
  commit c962cff17dfa11f4a8227ac16de2b28aea3312e4
  Author: Dou Liyang 
  Date:   Fri Mar 3 16:02:23 2017 +0800

  Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when
  booting"

  == Regression Potential ==
  This is reverting a commit that introduced a bug.  This commit has also
  been reverted upstream.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.




  Setup:
  Dell PowerEdge R940 having 2 socket populated with 28 cores.

  Impact:
  This is a boot and installation failure for R940 users having 2 socket x 28 
cores.
  Requesting an SRU for the fix.

  Steps:
  1. Setup a Dell PowerEdge R940 with 28 cores CPUs on 2 sockets.
  2. Start installation of Ubuntu-16.04.3 with HWE kernel.
  3. Observe the screen remains blank. Console logs indicate kernel crash.

  Additional Info:
  * Seen only with 4.10 HWE kernels of Ubuntu-16.04.3.
    4.4 kernels of Ubuntu-16.04.3 works fine. Daily builds of Ubuntu Server 
17.10 works fine.

  * Reducing the core count to <26 cores helps here. Boot & installation
  of HWE-kernel works fine.

  * Attaching the console log and acpidump from the setup.

  * Patch causing this failure: 
https://github.com/torvalds/linux/commit/dc6db24d2476cd09c0ecf2b8d80313539f737a89
  x86/acpi: Set persistent cpuid <-> nodeid mapping when booting

  * Fix patch series: https://lkml.org/lkml/2017/2/20/66

  Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when booting"
  
https://github.com/torvalds/linux/commit/c962cff17dfa11f4a8227ac16de2b28aea3312e4#diff-6bd7ef719bca1a2a56b9ebf4bd0bd88d

  Revert"x86/acpi: Enable MADT APIs to return disabled apicids"
  
https://github.com/torvalds/linux/commit/09c3f2bd5c7e5f18687663acb6adc6b167484ca5

  acpi/processor: Implement DEVICE operator for processor enumeration
  
https://github.com/torvalds/linux/commit/8c8cb30f49b86333d8e036e1945cf1a78c03577e

  acpi/processor: Check for duplicate processor ids at hotplug time
  
https://github.com/torvalds/linux/commit/a77d6cd968497792e072b74dff45b891ba778ddb

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

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

[Kernel-packages] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72

[Joshua R. Poulson]

Interesting. Does this also reproduce with the linux-azure kernel, which
is based on 4.11? (this should also work for on premises use, but you
may have to install the "extra" package if you are using PCI
passthrough).

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

Title:
  [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration
  after installing kernel 4.4.0-72

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

Bug description:
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's 
on Hyper-V.
  Microsoft Hyper-v 2012r2 Gen2 VMs

  See Attachment for what happens is immediately after backup starts I
  get an error.

  Eventually the kernel reports it has run out of memory and the machine
  just continuously scrolls errors message related to page allocation.

  When reseting the virtual machine no logs can be found of the problem.

  kernel 4.4.0-72-generic problem still here

  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  SourcePackage: linux-lts-xenial
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  5 12:05 seq
   crw-rw 1 root audio 116, 33 Apr  5 12:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-72-generic N/A
   linux-backports-modules-4.4.0-72-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 10 10:33 seq
   crw-rw 1 root audio 116, 33 Apr 10 10:33 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (414 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless 

[Kernel-packages] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72

[Sitsofe Wheeler]

Joshua - I'm fairly certain it should be fixed in 4.11 - will reply when
I have a chance.

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

Title:
  [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration
  after installing kernel 4.4.0-72

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

Bug description:
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's 
on Hyper-V.
  Microsoft Hyper-v 2012r2 Gen2 VMs

  See Attachment for what happens is immediately after backup starts I
  get an error.

  Eventually the kernel reports it has run out of memory and the machine
  just continuously scrolls errors message related to page allocation.

  When reseting the virtual machine no logs can be found of the problem.

  kernel 4.4.0-72-generic problem still here

  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  SourcePackage: linux-lts-xenial
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  5 12:05 seq
   crw-rw 1 root audio 116, 33 Apr  5 12:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-72-generic N/A
   linux-backports-modules-4.4.0-72-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 10 10:33 seq
   crw-rw 1 root audio 116, 33 Apr 10 10:33 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (414 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command 

[Kernel-packages] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72

[Sitsofe Wheeler]

Perhaps in addition to the DVD fix 4.4 needs a few more of the patches
listed on https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git/log/drivers/scsi/storvsc_drv.c?h=v4.9.65 ?

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

Title:
  [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration
  after installing kernel 4.4.0-72

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

Bug description:
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's 
on Hyper-V.
  Microsoft Hyper-v 2012r2 Gen2 VMs

  See Attachment for what happens is immediately after backup starts I
  get an error.

  Eventually the kernel reports it has run out of memory and the machine
  just continuously scrolls errors message related to page allocation.

  When reseting the virtual machine no logs can be found of the problem.

  kernel 4.4.0-72-generic problem still here

  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  SourcePackage: linux-lts-xenial
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  5 12:05 seq
   crw-rw 1 root audio 116, 33 Apr  5 12:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-72-generic N/A
   linux-backports-modules-4.4.0-72-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 10 10:33 seq
   crw-rw 1 root audio 116, 33 Apr 10 10:33 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (414 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  

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

[Andrew Cloke]

Are we waiting on the patches referenced in the bug description and
comment #1 to land upstream before backporting?

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

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

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

Bug description:
  Issue:

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

  Environment:
  ppc64le PowerVM Lpar

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

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

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

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

  System gives call traces like:

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

  The following commit IDs were built into a 4.10.0-37-generic #41 test
  kernel and verified to fix the problem:

  a525108cf1cc14651602d678da38fa627a76a724
  e1073d1e7920946ac4776a619cc40668b9e1401b
  40692eb5eea209c2dd55857f44b4e1d7206e91d6
  e24a1307ba1f99fc62a0bd61d5e87fcfb6d5503d
  79cc38ded1e1ac86e69c90f604efadd50b0b3762
  4ae279c2c96ab38a78b954d218790a8f6db714e5

To 

[Kernel-packages] [Bug 1721070] Re: powerpc/64s: Add workaround for P9 vector CI load issue

[Manoj Iyer]

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

Title:
  powerpc/64s: Add workaround for P9 vector CI load issue

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  
  == SRU Justification ==
  POWER9 DD2.1 and earlier has an issue where some cache inhibited
  vector load will return bad data. The fix is two part, one
  firmware/microcode part triggers HMI interrupts when hitting such
  loads, the other part is commit 5080332c2c89 from linux-next which then
  emulates the instructions in Linux.

  The affected instructions are limited to lxvd2x, lxvw4x, lxvb16x and
  lxvh8x.

  Commit ccd3cd361341 is needed as a prereq for Artful.
  Commits a3d96f70c147 and ccd3cd361341 are needed as prereqs for Zesty.

  == Fixes ==
  a3d96f70c147 ("powerpc/64s: Fix system reset vs general interrupt reentrancy")
  ccd3cd361341 ("powerpc/mce: Move 64-bit machine check code into mce.c")
  5080332c2c89 ("powerpc/64s: Add workaround for P9 vector CI load issue")

  == Regression Potential ==
  These commits are specific to powerpc.  They required some back porting but
   have been tested by IBM.


  -- Problem Description --

  When an instruction triggers the HMI, all threads in the core will be
  sent to the HMI handler, not just the one running the vector load.

  In general, these spurious HMIs are detected by the emulation code and
  we just return back to the running process. Unfortunately, if a
  spurious interrupt occurs on a vector load that's to normal memory we
  have no way to detect that it's spurious (unless we walk the page
  tables, which is very expensive). In this case we emulate the load but
  we need do so using a vector load itself to ensure 128bit atomicity is
  preserved.

  Some additional debugfs emulated instruction counters are added also.

  In order to solve this bug, we need to cherry pick the following patch

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=5080332c2c893118dbc18755f35c8b0131cf0fc4

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

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

[Kernel-packages] [Bug 1721070] Re: powerpc/64s: Add workaround for P9 vector CI load issue

[Andrew Cloke]

** Changed in: ubuntu-power-systems
   Status: Fix Committed => Fix Released

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

Title:
  powerpc/64s: Add workaround for P9 vector CI load issue

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  
  == SRU Justification ==
  POWER9 DD2.1 and earlier has an issue where some cache inhibited
  vector load will return bad data. The fix is two part, one
  firmware/microcode part triggers HMI interrupts when hitting such
  loads, the other part is commit 5080332c2c89 from linux-next which then
  emulates the instructions in Linux.

  The affected instructions are limited to lxvd2x, lxvw4x, lxvb16x and
  lxvh8x.

  Commit ccd3cd361341 is needed as a prereq for Artful.
  Commits a3d96f70c147 and ccd3cd361341 are needed as prereqs for Zesty.

  == Fixes ==
  a3d96f70c147 ("powerpc/64s: Fix system reset vs general interrupt reentrancy")
  ccd3cd361341 ("powerpc/mce: Move 64-bit machine check code into mce.c")
  5080332c2c89 ("powerpc/64s: Add workaround for P9 vector CI load issue")

  == Regression Potential ==
  These commits are specific to powerpc.  They required some back porting but
   have been tested by IBM.


  -- Problem Description --

  When an instruction triggers the HMI, all threads in the core will be
  sent to the HMI handler, not just the one running the vector load.

  In general, these spurious HMIs are detected by the emulation code and
  we just return back to the running process. Unfortunately, if a
  spurious interrupt occurs on a vector load that's to normal memory we
  have no way to detect that it's spurious (unless we walk the page
  tables, which is very expensive). In this case we emulate the load but
  we need do so using a vector load itself to ensure 128bit atomicity is
  preserved.

  Some additional debugfs emulated instruction counters are added also.

  In order to solve this bug, we need to cherry pick the following patch

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=5080332c2c893118dbc18755f35c8b0131cf0fc4

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

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

[Kernel-packages] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72

[Sitsofe Wheeler]

I see this issue too. It is easy to get with a 4.4 kernel if you have an
SSD hooked up to the Windows host and then you connect the SSD to the
Hyper-V VM via the SCSI controller in passthrough mode. Error messages
will look like this:

[   20.476616] sd 3:0:0:0: [sdb] Synchronizing SCSI cache
[   38.374458] scsi 3:0:0:0: Direct-Access Samsung  SSD 850 PRO 256G EXM0 
PQ: 0 ANSI: 0
[   38.374703] scsi 3:0:0:1: Direct-Access
PQ: 0 ANSI: 0
[   38.374919] scsi 3:0:0:2: Direct-Access
PQ: 0 ANSI: 0
[   38.375368] scsi 3:0:0:3: Direct-Access
PQ: 0 ANSI: 0
[   38.375711] scsi 3:0:0:4: Direct-Access
PQ: 0 ANSI: 0
[   38.376526] scsi 3:0:0:5: Direct-Access
PQ: 0 ANSI: 0
[   38.376791] scsi 3:0:0:6: Direct-Access
PQ: 0 ANSI: 0
[   38.377114] scsi 3:0:0:7: Direct-Access
PQ: 0 ANSI: 0
[   38.392809] sd 3:0:0:0: Attached scsi generic sg2 type 0
[   38.393282] sd 3:0:0:0: [sdb] 500118192 512-byte logical blocks: (256 GB/238 
GiB)
[   38.393811] sd 3:0:0:1: [sdc] Sector size 0 reported, assuming 512.
[   38.393819] sd 3:0:0:1: [sdc] 1 512-byte logical blocks: (512 B/512 B)
[   38.393822] sd 3:0:0:1: [sdc] 0-byte physical blocks
[   38.393874] sd 3:0:0:1: Attached scsi generic sg3 type 0
[   38.394262] sd 3:0:0:0: [sdb] Write Protect is off
[   38.394267] sd 3:0:0:0: [sdb] Mode Sense: 0f 00 00 00
[   38.394277] sd 3:0:0:1: [sdc] Write Protect is off
[   38.394281] sd 3:0:0:1: [sdc] Mode Sense: 00 00 00 00
[   38.395394] sd 3:0:0:2: [sdd] Sector size 0 reported, assuming 512.
[   38.395402] sd 3:0:0:2: [sdd] 1 512-byte logical blocks: (512 B/512 B)
[   38.395405] sd 3:0:0:2: [sdd] 0-byte physical blocks
[   38.395553] sd 3:0:0:2: Attached scsi generic sg4 type 0
[   38.395730] sd 3:0:0:2: [sdd] Write Protect is off
[   38.395735] sd 3:0:0:2: [sdd] Mode Sense: 00 00 00 00
[   38.395746] sd 3:0:0:1: [sdc] Asking for cache data failed
[   38.395754] sd 3:0:0:1: [sdc] Assuming drive cache: write through
[   38.400079] sd 3:0:0:2: [sdd] Asking for cache data failed
[   38.400088] sd 3:0:0:2: [sdd] Assuming drive cache: write through
[   38.400268] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[   38.400418] sd 3:0:0:3: [sde] Sector size 0 reported, assuming 512.
[   38.400425] sd 3:0:0:3: [sde] 1 512-byte logical blocks: (512 B/512 B)
[   38.400427] sd 3:0:0:3: [sde] 0-byte physical blocks
[   38.400480] sd 3:0:0:3: [sde] Write Protect is off
[   38.400483] sd 3:0:0:3: [sde] Mode Sense: 00 00 00 00
[   38.401653] sd 3:0:0:3: [sde] Asking for cache data failed
[   38.401660] sd 3:0:0:3: [sde] Assuming drive cache: write through
[   38.401768] sd 3:0:0:1: [sdc] Sector size 0 reported, assuming 512.
[   38.402068] sd 3:0:0:2: [sdd] Sector size 0 reported, assuming 512.
[   38.402258] sd 3:0:0:3: [sde] Sector size 0 reported, assuming 512.
[...]
[   38.415473] sdi: partition table beyond EOD, enabling native capacity
[   38.416509] sd 3:0:0:7: [sdi] Sector size 0 reported, assuming 512.
[   38.417072] Dev sdi: unable to read RDB block 1
[   38.417093]  sdi: unable to read partition table
[   38.417099] sdi: partition table beyond EOD, truncated
[   38.417516] sd 3:0:0:7: [sdi] Sector size 0 reported, assuming 512.
[   38.417617] sd 3:0:0:7: [sdi] Attached SCSI disk
[   38.841506] sd 3:0:0:0: [storvsc] Sense Key : Illegal Request [current] 
[   38.841510] sd 3:0:0:0: [storvsc] Add. Sense: Invalid command operation code
[   38.841895] sd 3:0:0:0: [storvsc] Sense Key : Illegal Request [current] 
[   38.841898] sd 3:0:0:0: [storvsc] Add. Sense: Invalid command operation code

Sadly 4.4.0-67-generic #88~lp1679898Commitdf0a1b9cce531 mentioned in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677938/comments/6
doesn't fix the problem. It is also broken in 4.8.0-34-generic
#36~16.04.1-Ubuntu but it is FIXED in 4.8.0-58-generic
#63~16.04.1-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/1679898

Title:
  [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration
  after installing kernel 4.4.0-72

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

Bug description:
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's 
on Hyper-V.
  Microsoft Hyper-v 2012r2 Gen2 VMs

  See Attachment for what happens is immediately after backup starts I
  get an error.

  Eventually the kernel reports it has run out of memory and the machine
  just continuously scrolls errors message related to page allocation.

  When reseting the virtual machine no logs can be found of the problem.

  kernel 

[Kernel-packages] [Bug 1730660] Re: Set PANIC_TIMEOUT=10 on Power Systems

[Khaled El Mously]

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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

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!

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

Title:
  Set PANIC_TIMEOUT=10 on Power Systems

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

Bug description:
  [Impact]
  When stopping CPUs fail when doing kdump, the system will hang 
indefinitively, instead of rebooting. With this option set, it will reboot 
after 10 seconds when that happens.

  This setting has been the default for trusty, where panic_timeout is
  10. Later releases set it to 0.

  [Test Case]
  When booting a kernel, /proc/sys/kernel/panic should be 10. It's 0 for 
xenial, zesty and artful. After the fix, it's 10.

  [Regression Potential]
  For users that rely on the setting as 0, they will see their system reboot 10 
seconds after a panic. They can set it back to 0 or other value. Though, on 
some rare cases, the system might not boot enough for this setting to be set. 
Balancing that with the case where kdump is used and the system is expected to 
boot, we expect the 10 seconds setting is okay.

  ===

  For ppc64le, in some rare crash cases, kdump won't load unless timeout
  is greater than 0. Only 10 has been tested by IBM, so using a smaller
  value may not work.

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

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

[Kernel-packages] [Bug 1719853] Re: Plantronics P610 does not support sample rate reading

[Khaled El Mously]

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

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

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


** Tags added: verification-needed-xenial

** Tags added: verification-needed-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/1719853

Title:
  Plantronics P610 does not support sample rate reading

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

Bug description:
  As per
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622763/comments/29
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709282 , I
  believe the USB ID 0x047F 0xC02F needs to be added to quirks.c in
  order for me to use my Plantronics P610. Thanks!

  == SRU Justification ==

  [Impact]
  [ 74.344674] usb 3-1: 2:1: cannot get freq at ep 0x1
  ...the same message will flood over dmesg.

  [Test Case]
  With this patch, ALSA stops trying to read sample rate from device,
  hence no more error messages.

  [Fix]
  Make affected device to use sample rate quirk.

  [Regression Potential]
  Minimal. This patch only affect one device.

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

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

[Kernel-packages] [Bug 1714485] Re: Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs.

[Andrew Cloke]

** Tags added: ppc64el-kdump

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

Title:
  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

Status in The Ubuntu-power-systems project:
  Triaged
Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Zesty:
  New
Status in makedumpfile source package in Artful:
  New
Status in makedumpfile source package in Bionic:
  In Progress

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-08-31 00:33:37 ==
  ---Problem Description---

  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

  ---Steps to Reproduce---

  1. Install Ubuntu 16.04.03 with / as xfs.
  2. Configure kdump.
  3. trigger crash.

  Machine hangs after below log. Attaching console log.

  [  OK  ] Reached target Network is Online.
   Starting Kernel crash dump capture service...
   Starting iSCSI initiator daemon (iscsid)...
  [   12.263089] kdump-tools[1205]: /etc/init.d/kdump-tools: 26: [: -ne: 
unexpected operator
  [  OK  ] Started Kernel crash dump capture service.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).

  
  4. After manual reboot  /etc/default/kdump-tools is empty.

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

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

[Kernel-packages] [Bug 1730852] Re: Device hotplugging with MPT SAS cannot work for VMWare ESXi

[Khaled El Mously]

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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

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!

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

Title:
  Device hotplugging with MPT SAS cannot work for VMWare ESXi

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

Bug description:
  [Impact]
  The hotplugging disk cannot be detected with the simulated MPT SAS 
  device on VMWare ESXi.

  [Fix]
  Author: Hannes Reinecke 
  Date:   Thu Aug 24 14:52:43 2017 +0200

  scsi: mptsas: Fixup device hotplug for VMWare ESXi
  
  VMWare ESXi emulates an mptsas HBA, but exposes all drives as
  direct-attached SAS drives.  This it not how the driver originally
  envisioned things; SAS drives were supposed to be connected via an
  expander, and only SATA drives would be direct attached. As such, any 
  hotplug event for direct-attach SAS drives was silently ignored, and 
  the guest failed to detect new drives from within a VMWare ESXi
  environment.

  [Test]
  The patch has been verified based on the Ubuntu kernel v4.4.0-97.120.

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

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

[Kernel-packages] [Bug 1723736] Re: Touchpad not detected - Lenovo ideapad 320-15IKB

[Khaled El Mously]

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

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

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


** Tags added: verification-needed-xenial

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

Title:
  Touchpad not detected - Lenovo ideapad 320-15IKB

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  Description:  Ubuntu 17.04
  Release:  17.04

  Basically the same bug as described here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708852

  I'm using a Lenovo ideapad 320-15IKB, though.

  I also tried the latest mainline kernel (4.13.7) which didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: 
boot/vmlinuz-4.10.0-19-generic]
  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.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  meradanis   1747 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Oct 15 14:23:54 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=912e6e24-9770-4e44-914b-9d181193c23d
  InstallationDate: Installed on 2017-10-14 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 81BG
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic 
root=UUID=a7c89b92-6e62-49e5-a4b0-052b751a2d6e 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.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/28/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6JCN14WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr6JCN14WW:bd09/28/2017:svnLENOVO:pn81BG:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.name: 81BG
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1729119] Re: NVMe timeout is too short

[Khaled El Mously]

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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

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-zesty

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

Title:
  NVMe timeout is too short

Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux-aws source package in Trusty:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in linux-aws source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed
Status in linux-aws source package in Zesty:
  Invalid
Status in linux source package in Artful:
  Fix Committed
Status in linux-aws source package in Artful:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  Some NVMe operations time out too quickly. The module parameters allow the 
timeouts to be extended, but only up to 255s, as the counters are bytes.

  [Fix]
  The underlying parameters are unsigned ints, so make the module parameters 
unsigned ints too, by picking patch 
http://lists.infradead.org/pipermail/linux-nvme/2017-September/012701.html

  (Trusty specific) This also requires picking the patch that converts
  the constant into a parameter, which is a clean cherry-pick.

  [Regression Potential]
  (X/Z/A) Very limited: only types of module parameters are changing, the patch 
is easily reviewable.

  (Trusty specific) Limited: a module parameter is added and its type is
  changed. The patches are easily reviewable.

  [Testing]
  (Trusty only) Boot tested on a c5.large instance on AWS which uses
  NVMe to boot. Verified that the system still boots with the patches,
  and that a timeout of 123456s is permitted.

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

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

[Kernel-packages] [Bug 1729337] Re: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config

[Khaled El Mously]

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

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

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


** Tags added: verification-needed-xenial

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

Title:
  CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config

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

Bug description:
  == SRU Justification ==
  The bug reporter stated they have a cluster of servers that applied Xenial 
updates
  and then were unable to mount CIFS shares after upgrading to 4.4.0-98. The
  same machines on 4.4.0-97 do not hit the regression.  It was found that the
  regression is fixed by mainline commit:
  4587eee04e2a ("SMB3: Validate negotiate request must always be signed").

  This fix is required in all Ubuntu supported releases.  Commit 4587eee04e2a
  landed in mailine as of 4.14-rc7.  It  was also cc'd to upstream stable,
  but it has not landed in any stable releases yet, which is the reason for
  this SRU.


  == Fix ==
  commit 4587eee04e2ac7ac3ac9fa2bc164fb6e548f99cd
  Author: Steve French 
  Date:   Wed Oct 25 15:58:31 2017 -0500
  SMB3: Validate negotiate request must always be signed

  == Regression Potential ==
  This patch is to fix a regression.  It was also cc'd to upstream stable, so
  it received addition review upstream.

  We have a cluster of servers that applied a security update overnight
  and were unable to mount CIFS shares after upgrading to 4.4.0-98.  The
  same machines on 4.4.0-97 were fine the night before, and are fine
  after downgrading.  The only error message CIFS would report, even on
  verbose, was:

  [  257.089876] CIFS VFS: validate protocol negotiate failed: -11
  [  257.089964] CIFS VFS: cifs_mount failed w/return code = -5

  Rebooting did not help.  Nor did attempting to mount the share
  manually using mount -t cifs.

  Here's the offending line from our /etc/fstab (with hostnames
  sanitized):

  //server/share /mnt/share cifs 
rw,user,credentials=/etc/samba/credentials.share,uid=33,gid=33,file_mode=0770,dir_mode=0770
  ,exec,soft,noserverino,vers=3.0 0 0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-98-generic 4.4.0-98.121
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  1 07:56 seq
   crw-rw 1 root audio 116, 33 Nov  1 07:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Nov  1 08:49:47 2017
  HibernationDevice: RESUME=/dev/mapper/ubuntu--template--vg-swap_1
  InstallationDate: Installed on 2016-12-16 (319 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  PciMultimedia:

  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic 
root=/dev/mapper/ubuntu--template--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.157.13
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 

[Kernel-packages] [Bug 1727331] Re: NMI watchdog: BUG: soft lockup on Guest upon boot (KVM)

[Khaled El Mously]

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

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

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


** Tags added: verification-needed-xenial

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

Title:
  NMI watchdog: BUG: soft lockup on Guest upon boot (KVM)

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  == SRU Justification ==
  Xenial does not include the patch:
  "KVM: PPC: Book3S: Treat VTB as a per-subcore register, not per-thread",
  which is commit 88b02cf97bb7 in the upstream Linux kernel repository. The
  symptom of not having this patch is that guests running with threads > 1
  (that is, in SMT2, SMT4 or SMT8 mode) can give spurious soft-lockup messages 
  when they are not in fact locked up, if the guest kernel uses the VTB
  (virtual timebase) register in its softlockup detector code.

  IBM provided this backport of commit 88b02cf97bb7.

  == Fix ==
  commit 88b02cf97bb7e742db3e31671d54177e3e19fd89
  Author: Paul Mackerras 
  Date:   Thu Sep 15 13:42:52 2016 +1000

  KVM: PPC: Book3S: Treat VTB as a per-subcore register, not per-
  thread

  == Regression Potential ==
  This patch is specific to powerpc.  It was provided by and tested by IBM.



  Environment:
  Host OS: Ubuntu 16.04 (4.4.0-97-generic)
  Guest OS: Ubuntu 16.04

  Host is running NovaLink and GPFS.  Guest gets filesystem from gpfs
  cluster.

  Issue:

  While booting the guest OS went into recovery.  dmesg shows CPU soft
  lockup.  This issue is easily recreatable when multiple VMs (about 10)
  are being started simultaneously.

  
...

   - Paul Mackerras  - 2017-10-24 00:42:25 ==

  Looking at kernel sources:

  The Ubuntu host kernel (4.4.0-97) does not include the patch "KVM:
  PPC: Book3S: Treat VTB as a per-subcore register, not per-thread",
  which is commit 88b02cf97bb7 in the upstream Linux kernel repository.
  The symptom of not having this patch is that guests running with
  threads > 1 (that is, in SMT2, SMT4 or SMT8 mode) can give spurious
  soft-lockup messages when they are not in fact locked up, if the guest
  kernel uses the VTB (virtual timebase) register in its softlockup
  detector code.

  This is a backport of commit 88b02cf97bb7 from the upstream Linux
  kernel repository to the Ubuntu 4.4 kernel. It is the fix for the
  problem of seeing spurious soft lockup messages in guests running in
  an SMT mode greater than 1.

  These tests were run on a system with 20 cores.  Each VM had 1 core and 4 
threads (SMT=4).
  It is working very well with this patch

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

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

[Kernel-packages] [Bug 1729256] Re: Invalid btree pointer causes the kernel NULL pointer dereference

[Khaled El Mously]

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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

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!

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

Title:
  Invalid btree pointer causes the kernel NULL pointer dereference

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

Bug description:
  [Impact]
  The frequent kernel errors can be seen inside the XFS based OSD
  processes and it causes to crash and restart.

  BUG: unable to handle kernel NULL pointer dereference at 00a0
  IP: [] xfs_da3_node_read+0x30/0xb0 [xfs]
  CPU: 8 PID: 2855031 Comm: tp_fstore_op Not tainted 4.4.0-78-generic #99-Ubuntu
  Hardware name: HP ProLiant DL380 Gen9/ProLiant DL380 Gen9, BIOS P89 09/13/2016
  task: 880620f38e00 ti: 880678228000 task.ti: 880678228000
  RIP: 0010:[]  []
  xfs_da3_node_read+0x30/0xb0 [xfs]
  RSP: 0018:88067822bd00  EFLAGS: 00010286
  RAX:  RBX: 88078abff3f0 RCX: 0001
  RDX:  RSI:  RDI: 88067822bcb0
  RBP: 88067822bd20 R08: 0001 R09: fffe
  R10: ea001e2aff80 R11: 0001 R12: 88067822bd50
  R13: 8805a37f R14: 0001 R15: 8d180e3e
  FS:  7f7573c01700() GS:88103fa0()knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 00a0 CR3: 001686f3d000 CR4: 003406e0
  DR0:  DR1:  DR2: 
  DR3:  DR6: fffe0ff0 DR7: 0400
  Stack:
   c03cfb50 c03b0ecc 88067822bde0 0001
   88067822bd98 c038c8b3 00020008 88081cb06040
   0002d8723bf8 880fc142ae80  
  Call Trace:
   [] ? xfs_trans_roll+0x2c/0x50 [xfs]
   [] xfs_attr3_node_inactive+0x183/0x220 [xfs]
   [] xfs_attr3_root_inactive+0xac/0x100 [xfs]
   [] xfs_attr_inactive+0x14c/0x1a0 [xfs]
   [] xfs_inactive+0x85/0x120 [xfs]
   [] xfs_fs_evict_inode+0xa5/0x100 [xfs]
   [] evict+0xbe/0x190
   [] iput+0x1c1/0x240
   [] do_unlinkat+0x199/0x2d0
   [] SyS_unlink+0x16/0x20
   [] entry_SYSCALL_64_fastpath+0x16/0x71

  [Fix]
  commit e678a63e6c95f140befe6fcd81b49075ecb3c701
  Author: Brian Foster 
  Date:   Mon Oct 9 11:38:56 2017 -0700

  xfs: reinit btree pointer on attr tree inactivation walk

  xfs_attr3_root_inactive() walks the attr fork tree to invalidate the
  associated blocks. xfs_attr3_node_inactive() recursively descends from
  internal blocks to leaf blocks, caching block address values along the
  way to revisit parent blocks, locate the next entry and descend down
  that branch of the tree.

  The code that attempts to reread the parent block is unsafe because it
  assumes that the local xfs_da_node_entry pointer remains valid after
  an xfs_trans_brelse() and re-read of the parent buffer.  Under heavy
  memory pressure, it is possible that the buffer has been reclaimed and
  reallocated by the time the parent block is reread.  This means that
  'btree' can point to an invalid memory address, lead to a
  random/garbage value for child_fsb and cause the subsequent read of
  the attr fork to go off the rails and return a NULL buffer for an attr
  fork offset that is most likely not allocated.

  Note that this problem can be manufactured by setting
  XFS_ATTR_BTREE_REF to 0 to prevent LRU caching of attr buffers,
  creating a file with a multi-level attr fork and removing it to
  trigger inactivation.

  To address this problem, reinit the node/btree pointers to the parent
  buffer after it has been re-read. This ensures btree points to a valid
  record and allows the walk to proceed.

  [Test]
  The patch has been tested on the production system.

  [Regression Risk]
  Clean cherry-pick queued for stable, so we'll be picking it up anyway.

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

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

[Kernel-packages] [Bug 1730660] Re: Set PANIC_TIMEOUT=10 on Power Systems

[Khaled El Mously]

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

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

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


** Tags added: verification-needed-xenial

** Tags added: verification-needed-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/1730660

Title:
  Set PANIC_TIMEOUT=10 on Power Systems

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

Bug description:
  [Impact]
  When stopping CPUs fail when doing kdump, the system will hang 
indefinitively, instead of rebooting. With this option set, it will reboot 
after 10 seconds when that happens.

  This setting has been the default for trusty, where panic_timeout is
  10. Later releases set it to 0.

  [Test Case]
  When booting a kernel, /proc/sys/kernel/panic should be 10. It's 0 for 
xenial, zesty and artful. After the fix, it's 10.

  [Regression Potential]
  For users that rely on the setting as 0, they will see their system reboot 10 
seconds after a panic. They can set it back to 0 or other value. Though, on 
some rare cases, the system might not boot enough for this setting to be set. 
Balancing that with the case where kdump is used and the system is expected to 
boot, we expect the 10 seconds setting is okay.

  ===

  For ppc64le, in some rare crash cases, kdump won't load unless timeout
  is greater than 0. Only 10 has been tested by IBM, so using a smaller
  value may not work.

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

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

[Kernel-packages] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC

[Khaled El Mously]

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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

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!

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

Title:
  Cannot pair BLE remote devices when using combo BT SoC

Status in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in bluez source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in bluez source package in Zesty:
  New
Status in linux source package in Zesty:
  Fix Committed
Status in bluez source package in Artful:
  New
Status in linux source package in Artful:
  Fix Committed

Bug description:
  It has been observed that sometimes it is not possible to pair with
  BLE remote devices when the host system is using combo (WiFi + BT)
  chip.

  The root cause of the disconnection has been identified as coming from
  the internal to bluez timeout. If bluez does not hear any reply from for
  two seconds the link is automagically disconnected. The reason fro the
  silence is not however a failure of the remote device but quite often a
  delay in the WiFi/BT combo driver that causes the packages not to reach
  the bluez stack.

  [Impact]

  Not possible to pair BLE remote devices such as sensors and such with
  Ubuntu when the host system uses BT+WiFi combo SoC. The connection
  attempt is disturbed with a timeout.

  [Fix]

  It has been fixed by increasing the timeout value from 2 seconds to
  4 seconds. It is enough for the events to reach the stack (measured
  that it takes between 3 and 3.5 seconds).

  [Testcase]

  Tested with the device that failed to connect to Ubuntu Core gateway.
  It fails w/o the patch, it connects just fine with the patch applied.

  [Regression Potential]

  Very small. The increased timeout is taken into consideration only for
  new and scan report triggered connections. It will not make any already
  working device to fail to pair.

  [Other Info]

  The bug has been discussed and fixed here:

  https://marc.info/?l=linux-bluetooth=150824844606937=2

  [Patch]

  https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-
  next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571

  The patch has been accepted by the upstream and will be a part of the next
  kernel release. Currently in the bluetooth-next tree.

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

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

[Kernel-packages] [Bug 1728489] Re: tar -x sometimes fails on overlayfs

[Khaled El Mously]

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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

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!

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

Title:
  tar -x sometimes fails on overlayfs

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

Bug description:
  [SRU Justification]

  [Impact]
  A user is seeing failures from extracting tar archives on overlay filesystems 
on the 4.4 kernel in constrained environments. The error presents as: 

  `tar: ./deps/0/bin: Directory renamed before its status could be
  extracted`

  Following this thread (http://www.spinics.net/lists/linux-
  unionfs/msg00856.html), it appears that this occurs when entries in
  the kernel's inode cache are reclaimed, and subsequent lookups return
  new inode numbers.

  Further testing showed that when setting
  `/proc/sys/vm/vfs_cache_pressure` to 0 (don't allow the kernel to
  reclaim inode cache entries due to memory pressure) the error does not
  recur, supporting the hypothesis that cache entries are being evicted.
  However, this setting may lead to a kernel OOM so is not a reasonable
  workaround even temporarily.

  The error cannot be reproduced on a 4.13 kernel, due to the series at
  https://www.spinics.net/lists/linux-fsdevel/msg110235.html. The
  particular relevant commit is
  b7a807dc2010334e62e0afd89d6f7a8913eb14ff, which needs a couple of
  dependencies.

  [Fix]
  For Zesty, backport the entire series.
  For Xenial, where a full backport is not feasible, backport the key commit 
and the short list of dependencies.

  [Testcase]

  # Testing this bug

  The testcase for this particular bug is simple - create an overlay
  filesystem with all layers on the same underlying file system, and
  then see if the inode of a directory is constant across dropping the
  caches:

  mkdir -p /upper/upper /upper/work /lower
  mount -t overlay none /mnt -o 
lowerdir=/lower,upperdir=/upper/upper,workdir=/upper/work
  cd /mnt
  mkdir a
  stat a # observe inode number
  echo 2 > /proc/sys/vm/drop_caches
  stat a # compare inode number

  If the inode number is the same, the fix is successful.

  # Regression testing

  I have run the unionmount test suite from
  http://git.infradead.org/users/dhowells/unionmount-testsuite.git in
  overlay mode (./run --ov), and verified that it still passes.

  (The series cover letter mentions a fork of the test suite at
  https://github.com/amir73il/unionmount-testsuite/commits/overlayfs-
  devel. I have *not* attempted to get this running: it assumes a range
  of changes that are not present in our kernels.)

  [Regression Potential]
  As this changes overlayfs, there is potential for regression in the form of 
unexpected breakages to overlaysfs behaviour.

  I think this is adequately addressed by the regression testing.

  One option to reduce the regression potential on Zesty is to reduce
  the set of patches applied - rather than including the whole series we
  could include just the patches to solve this bug, which are much
  easier to inspect for correctness.

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

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

[Kernel-packages] [Bug 1729637] Re: Samba mount/umount in docker container triggers kernel Oops

[Khaled El Mously]

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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

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!

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

Title:
  Samba mount/umount in docker container triggers kernel Oops

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

Bug description:
  == SRU Justification ==
  This bug causes Samba mount and umounts in docker container to trigger 
  a kernel Oops.  When running 2 docker containers, one as samba server and 
  another one as samba client that mounts and umounts a smb share a kernel 
  OOps can be triggered.  

  This bug happens in Xenial and Zesty, and is fixed by the following two 
commits:
  76da0704507b ("ipv6: only call ip6_route_dev_notify() once for 
NETDEV_UNREGISTER")
  12d94a804946 ("ipv6: fix NULL dereference in ip6_route_dev_notify()")

  Both commits are clean cherry picks.  76da0704507b is in mainline as of v4.12.
  Commit 12d94a804946 is in mainline as of v4.13-rc6. 
  
  == Fixes ==
  commit 76da0704507bbc51875013f6557877ab308cfd0a
  Author: WANG Cong 
  Date:   Tue Jun 20 11:42:27 2017 -0700

  ipv6: only call ip6_route_dev_notify() once for NETDEV_UNREGISTER

  commit 12d94a804946af291e24b80fc53ec86264765781
  Author: Eric Dumazet 
  Date:   Tue Aug 15 04:09:51 2017 -0700

  ipv6: fix NULL dereference in ip6_route_dev_notify()

  == Regression Potential ==
  Both commits are specific to ipv6 and fix a regression introduced into Xenial 
and Zesty.

  == Test Case ==
  A test kernel was built with these patches and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  The kernel message:
    unregister_netdevice: waiting for lo to become free. Usage count = 1
  shows up, some minutes later the oops and/or warnings happens.

  The scripts to trigger the kernel Oops can be found at: 
https://github.com/fho/docker-samba-loop
  I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation 
with:

  - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
  - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
  - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1

  In a different scenario were Ubuntu 16.04 servers were running
  multiple docker containers with Nginx or small network applications in
  parallel, I was also able to reproduce the kernel Oopses also on:

  - linux-image-4.10.0-1004-gcp
  - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830

  I haven't tried again to reproduce it with those kernels on a clean Ubuntu
  installation and unfortunately didn't kept the kernel logs.

  The "unregister_netdevice: waiting for lo to become free. Usage count
  = 1" messages are related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is
  handled as separate issue.

  According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
  https://patchwork.ozlabs.org/patch/801533/
  https://patchwork.ozlabs.org/patch/778449/
  ---
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  3 09:51 seq
   crw-rw 1 root audio 116, 33 Nov  3 09:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Google Google Compute Engine
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=bf9a017a-931d-4191-84bc-b8434dbba527 ro scsi_mod.use_blk_mq=Y 
console=ttyS0
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images xenial uec-images
  Uname: Linux 

[Kernel-packages] [Bug 1711104] Re: [P9][Ubuntu 16.04.03] Additional PMU fixes for P9

[Andrew Cloke]

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

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

Title:
  [P9][Ubuntu 16.04.03] Additional PMU fixes for P9

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in perforate source package in Zesty:
  New

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2017-08-16 
04:07:45 ==
  Please integrate the following PMU fixes for P9.

  93fc5ca9a0048c ('powerpc/perf: Cleanup of PM_BR_CMPL vs. PM_BRU_CMPL in 
Power9 event list')
  91e0bd1e62519b ('powerpc/perf: Add PM_LD_MISS_L1 and PM_BR_2PATH to power9 
event list')
  70a7e720998d5b ('powerpc/perf: Factor out PPMU_ONLY_COUNT_RUN check code from 
power8')
  7aa345d84245a7 ('powerpc/perf: Update default sdar_mode value for power9')
  101dd590a7fa37 ('powerpc/perf: Avoid spurious PMU interrupts after idle')
  bdd21ddb919d28 ('powerpc/perf: Avoid spurious PMU interrupts after idle on 
Power9')
  3f0bd8dad0db73 ('powerpc/perf: Add POWER9 alternate PM_RUN_CYC and 
PM_RUN_INST_CMPL events')
  20dd4c624d2515 ('powerpc/perf: Fix SDAR_MODE value for continous sampling on 
Power9')
  24bedcb7c81137 ('powerpc/perf: Fix branch event code for power9')
  8c218578fcbbbd ('powerpc/perf: Fix Power9 test_adder fields')

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

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

[Kernel-packages] [Bug 1719853] Re: Plantronics P610 does not support sample rate reading

[Khaled El Mously]

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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

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!

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

Title:
  Plantronics P610 does not support sample rate reading

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

Bug description:
  As per
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622763/comments/29
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709282 , I
  believe the USB ID 0x047F 0xC02F needs to be added to quirks.c in
  order for me to use my Plantronics P610. Thanks!

  == SRU Justification ==

  [Impact]
  [ 74.344674] usb 3-1: 2:1: cannot get freq at ep 0x1
  ...the same message will flood over dmesg.

  [Test Case]
  With this patch, ALSA stops trying to read sample rate from device,
  hence no more error messages.

  [Fix]
  Make affected device to use sample rate quirk.

  [Regression Potential]
  Minimal. This patch only affect one device.

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

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

[Kernel-packages] [Bug 1729637] Re: Samba mount/umount in docker container triggers kernel Oops

[Khaled El Mously]

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

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

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


** Tags added: verification-needed-xenial

** Tags added: verification-needed-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/1729637

Title:
  Samba mount/umount in docker container triggers kernel Oops

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

Bug description:
  == SRU Justification ==
  This bug causes Samba mount and umounts in docker container to trigger 
  a kernel Oops.  When running 2 docker containers, one as samba server and 
  another one as samba client that mounts and umounts a smb share a kernel 
  OOps can be triggered.  

  This bug happens in Xenial and Zesty, and is fixed by the following two 
commits:
  76da0704507b ("ipv6: only call ip6_route_dev_notify() once for 
NETDEV_UNREGISTER")
  12d94a804946 ("ipv6: fix NULL dereference in ip6_route_dev_notify()")

  Both commits are clean cherry picks.  76da0704507b is in mainline as of v4.12.
  Commit 12d94a804946 is in mainline as of v4.13-rc6. 
  
  == Fixes ==
  commit 76da0704507bbc51875013f6557877ab308cfd0a
  Author: WANG Cong 
  Date:   Tue Jun 20 11:42:27 2017 -0700

  ipv6: only call ip6_route_dev_notify() once for NETDEV_UNREGISTER

  commit 12d94a804946af291e24b80fc53ec86264765781
  Author: Eric Dumazet 
  Date:   Tue Aug 15 04:09:51 2017 -0700

  ipv6: fix NULL dereference in ip6_route_dev_notify()

  == Regression Potential ==
  Both commits are specific to ipv6 and fix a regression introduced into Xenial 
and Zesty.

  == Test Case ==
  A test kernel was built with these patches and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  The kernel message:
    unregister_netdevice: waiting for lo to become free. Usage count = 1
  shows up, some minutes later the oops and/or warnings happens.

  The scripts to trigger the kernel Oops can be found at: 
https://github.com/fho/docker-samba-loop
  I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation 
with:

  - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
  - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
  - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1

  In a different scenario were Ubuntu 16.04 servers were running
  multiple docker containers with Nginx or small network applications in
  parallel, I was also able to reproduce the kernel Oopses also on:

  - linux-image-4.10.0-1004-gcp
  - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830

  I haven't tried again to reproduce it with those kernels on a clean Ubuntu
  installation and unfortunately didn't kept the kernel logs.

  The "unregister_netdevice: waiting for lo to become free. Usage count
  = 1" messages are related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is
  handled as separate issue.

  According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
  https://patchwork.ozlabs.org/patch/801533/
  https://patchwork.ozlabs.org/patch/778449/
  ---
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  3 09:51 seq
   crw-rw 1 root audio 116, 33 Nov  3 09:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Google Google Compute Engine
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=bf9a017a-931d-4191-84bc-b8434dbba527 ro scsi_mod.use_blk_mq=Y 
console=ttyS0
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such 

[Kernel-packages] [Bug 1729256] Re: Invalid btree pointer causes the kernel NULL pointer dereference

[Khaled El Mously]

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

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

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


** Tags added: verification-needed-xenial

** Tags added: verification-needed-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/1729256

Title:
  Invalid btree pointer causes the kernel NULL pointer dereference

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

Bug description:
  [Impact]
  The frequent kernel errors can be seen inside the XFS based OSD
  processes and it causes to crash and restart.

  BUG: unable to handle kernel NULL pointer dereference at 00a0
  IP: [] xfs_da3_node_read+0x30/0xb0 [xfs]
  CPU: 8 PID: 2855031 Comm: tp_fstore_op Not tainted 4.4.0-78-generic #99-Ubuntu
  Hardware name: HP ProLiant DL380 Gen9/ProLiant DL380 Gen9, BIOS P89 09/13/2016
  task: 880620f38e00 ti: 880678228000 task.ti: 880678228000
  RIP: 0010:[]  []
  xfs_da3_node_read+0x30/0xb0 [xfs]
  RSP: 0018:88067822bd00  EFLAGS: 00010286
  RAX:  RBX: 88078abff3f0 RCX: 0001
  RDX:  RSI:  RDI: 88067822bcb0
  RBP: 88067822bd20 R08: 0001 R09: fffe
  R10: ea001e2aff80 R11: 0001 R12: 88067822bd50
  R13: 8805a37f R14: 0001 R15: 8d180e3e
  FS:  7f7573c01700() GS:88103fa0()knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 00a0 CR3: 001686f3d000 CR4: 003406e0
  DR0:  DR1:  DR2: 
  DR3:  DR6: fffe0ff0 DR7: 0400
  Stack:
   c03cfb50 c03b0ecc 88067822bde0 0001
   88067822bd98 c038c8b3 00020008 88081cb06040
   0002d8723bf8 880fc142ae80  
  Call Trace:
   [] ? xfs_trans_roll+0x2c/0x50 [xfs]
   [] xfs_attr3_node_inactive+0x183/0x220 [xfs]
   [] xfs_attr3_root_inactive+0xac/0x100 [xfs]
   [] xfs_attr_inactive+0x14c/0x1a0 [xfs]
   [] xfs_inactive+0x85/0x120 [xfs]
   [] xfs_fs_evict_inode+0xa5/0x100 [xfs]
   [] evict+0xbe/0x190
   [] iput+0x1c1/0x240
   [] do_unlinkat+0x199/0x2d0
   [] SyS_unlink+0x16/0x20
   [] entry_SYSCALL_64_fastpath+0x16/0x71

  [Fix]
  commit e678a63e6c95f140befe6fcd81b49075ecb3c701
  Author: Brian Foster 
  Date:   Mon Oct 9 11:38:56 2017 -0700

  xfs: reinit btree pointer on attr tree inactivation walk

  xfs_attr3_root_inactive() walks the attr fork tree to invalidate the
  associated blocks. xfs_attr3_node_inactive() recursively descends from
  internal blocks to leaf blocks, caching block address values along the
  way to revisit parent blocks, locate the next entry and descend down
  that branch of the tree.

  The code that attempts to reread the parent block is unsafe because it
  assumes that the local xfs_da_node_entry pointer remains valid after
  an xfs_trans_brelse() and re-read of the parent buffer.  Under heavy
  memory pressure, it is possible that the buffer has been reclaimed and
  reallocated by the time the parent block is reread.  This means that
  'btree' can point to an invalid memory address, lead to a
  random/garbage value for child_fsb and cause the subsequent read of
  the attr fork to go off the rails and return a NULL buffer for an attr
  fork offset that is most likely not allocated.

  Note that this problem can be manufactured by setting
  XFS_ATTR_BTREE_REF to 0 to prevent LRU caching of attr buffers,
  creating a file with a multi-level attr fork and removing it to
  trigger inactivation.

  To address this problem, reinit the node/btree pointers to the parent
  buffer after it has been re-read. This ensures btree points to a valid
  record and allows the walk to proceed.

  [Test]
  The patch has been tested on the production system.

  [Regression Risk]
  Clean cherry-pick queued for stable, so we'll be picking it up anyway.

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

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

[Kernel-packages] [Bug 1719697] Re: Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940

[Khaled El Mously]

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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

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

Title:
  Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940

Status in dellserver:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Fix Committed

Bug description:

  == SRU Justification ==
  Kernel crashes when installation of Ubuntu-16.04.3 with HWE (ISO).
  Same observation while booting to 4.10.0-28 HWE kerenl of Ubuntu-16.04.3
  and 4.10.0-33 HWE as well.

  Seen only with 4.10 HWE kernels of Ubuntu-16.04.3.  4.4 kernels of
  Ubuntu-16.04.3 works fine. Daily builds of Ubuntu Server 17.10 works fine.

  Reducing the core count to <26 cores helps here. Boot & installation of
  HWE-kernel works fine.

  This bug was introduced by commit:
  dc6db24d2476 ("x86/acpi: Set persistent cpuid <-> nodeid mapping when 
booting")

  It is resolved by reverting commit dc6db24d2476, which was done in mainline 
by 
  commit c962cff17df as of v4.11-rc3.

  There are three additiona commits introduced by the same patch author when
  commit c962cff17df was submitted.  However, it was confirmed that only the 
single
  revert is needed to fix this particular bug.  Upstream thread:
   https://lkml.org/lkml/2017/2/20/66

  == Fix ==
  commit c962cff17dfa11f4a8227ac16de2b28aea3312e4
  Author: Dou Liyang 
  Date:   Fri Mar 3 16:02:23 2017 +0800

  Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when
  booting"

  == Regression Potential ==
  This is reverting a commit that introduced a bug.  This commit has also
  been reverted upstream.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.




  Setup:
  Dell PowerEdge R940 having 2 socket populated with 28 cores.

  Impact:
  This is a boot and installation failure for R940 users having 2 socket x 28 
cores.
  Requesting an SRU for the fix.

  Steps:
  1. Setup a Dell PowerEdge R940 with 28 cores CPUs on 2 sockets.
  2. Start installation of Ubuntu-16.04.3 with HWE kernel.
  3. Observe the screen remains blank. Console logs indicate kernel crash.

  Additional Info:
  * Seen only with 4.10 HWE kernels of Ubuntu-16.04.3.
    4.4 kernels of Ubuntu-16.04.3 works fine. Daily builds of Ubuntu Server 
17.10 works fine.

  * Reducing the core count to <26 cores helps here. Boot & installation
  of HWE-kernel works fine.

  * Attaching the console log and acpidump from the setup.

  * Patch causing this failure: 
https://github.com/torvalds/linux/commit/dc6db24d2476cd09c0ecf2b8d80313539f737a89
  x86/acpi: Set persistent cpuid <-> nodeid mapping when booting

  * Fix patch series: https://lkml.org/lkml/2017/2/20/66

  Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when booting"
  
https://github.com/torvalds/linux/commit/c962cff17dfa11f4a8227ac16de2b28aea3312e4#diff-6bd7ef719bca1a2a56b9ebf4bd0bd88d

  Revert"x86/acpi: Enable MADT APIs to return disabled apicids"
  
https://github.com/torvalds/linux/commit/09c3f2bd5c7e5f18687663acb6adc6b167484ca5

  acpi/processor: Implement DEVICE operator for processor enumeration
  
https://github.com/torvalds/linux/commit/8c8cb30f49b86333d8e036e1945cf1a78c03577e

  acpi/processor: Check for duplicate processor ids at hotplug time
  
https://github.com/torvalds/linux/commit/a77d6cd968497792e072b74dff45b891ba778ddb

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

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

[Kernel-packages] [Bug 1730852] Re: Device hotplugging with MPT SAS cannot work for VMWare ESXi

[Khaled El Mously]

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

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

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


** Tags added: verification-needed-xenial

** Tags added: verification-needed-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/1730852

Title:
  Device hotplugging with MPT SAS cannot work for VMWare ESXi

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

Bug description:
  [Impact]
  The hotplugging disk cannot be detected with the simulated MPT SAS 
  device on VMWare ESXi.

  [Fix]
  Author: Hannes Reinecke 
  Date:   Thu Aug 24 14:52:43 2017 +0200

  scsi: mptsas: Fixup device hotplug for VMWare ESXi
  
  VMWare ESXi emulates an mptsas HBA, but exposes all drives as
  direct-attached SAS drives.  This it not how the driver originally
  envisioned things; SAS drives were supposed to be connected via an
  expander, and only SATA drives would be direct attached. As such, any 
  hotplug event for direct-attach SAS drives was silently ignored, and 
  the guest failed to detect new drives from within a VMWare ESXi
  environment.

  [Test]
  The patch has been verified based on the Ubuntu kernel v4.4.0-97.120.

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

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

[Kernel-packages] [Bug 1727544] Re: ELANTECH Touchpad is not detected in 'Lenovo Ideapad 320 14AST' after fresh install

[Khaled El Mously]

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

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

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


** Tags added: verification-needed-xenial

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

Title:
  ELANTECH Touchpad is not detected in 'Lenovo Ideapad 320 14AST' after
  fresh install

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  I have installed Ubuntu 16.04 on my new Lenovo Ideapad 320 14AST. The 
touchpad is not working. I have followed this tutorial 
https://askubuntu.com/questions/763584/elantech-touchpad-not-working-on-ubuntu-16-04-and-arch-linux
 and it doesn't work. The touchpad is working fine on Windows. My kernel 
version is 4.10.0-37-generic.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  agasigp1605 F pulseaudio
   /dev/snd/controlC1:  agasigp1605 F pulseaudio
  CRDA:
   country ID: DFS-JP
(2402 - 2482 @ 20), (N/A, 20), (N/A)
(5735 - 5815 @ 20), (N/A, 23), (N/A)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=da16f5a9-567e-4dd7-994a-eb64b6797690
  InstallationDate: Installed on 2017-10-25 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 80XU
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=457b1305-a90d-462a-92c2-11d129eb1580 ro i8042.kbdreset=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.157.12
  Tags:  xenial
  Uname: Linux 4.10.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/28/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5PCN18WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-14AST
  dmi.modalias: 
dmi:bvnLENOVO:bvr5PCN18WW:bd09/28/2017:svnLENOVO:pn80XU:pvrLenovoideapad320-14AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad320-14AST:
  dmi.product.name: 80XU
  dmi.product.version: Lenovo ideapad 320-14AST
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1728098] Re: [kernel] tty/hvc: Use opal irqchip interface if available

[Khaled El Mously]

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

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

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


** Tags added: verification-needed-xenial

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

Title:
  [kernel] tty/hvc: Use opal irqchip interface if available

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:

  == SRU Justification ==
  This bug is fixed by commit 00dab8187e18.  The commit updates the hvc
  driver to use the OPAL irqchip if made available by the running firmware.
  If it is not present, the driver falls back to the existing OPAL event 
number.   

  Commit 00dab8187e18 was added to mainline is v4.8-rc1, so it is not needed in 
  releases newer than Xenial.  The commit is a clean cherry pick in Xenial.

  
  == Fix ==
  commit 00dab8187e182da41122f66c207707b192509df4
  Author: Sam Mendoza-Jonas 
  Date:   Mon Jul 11 13:38:58 2016 +1000

  tty/hvc: Use opal irqchip interface if available

  
  == Regression Potential ==
  This change is specific to the hvc driver and has been in mainline since 
v4.8-rc1
  without any issues reported.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  ---Problem Description---
  Please backport console irq patch .

  commit 00dab8187e182da41122f66c207707b192509df4
  Author: Sam Mendoza-Jonas 
  Date:   Mon Jul 11 13:38:58 2016 +1000

  tty/hvc: Use opal irqchip interface if available

  Update the hvc driver to use the OPAL irqchip if made available by the
  running firmware. If it is not present, the driver falls back to the
  existing OPAL event number.

  Signed-off-by: Samuel Mendoza-Jonas 
  Signed-off-by: Michael Ellerman 

  ---uname output---
  Linux tul217p1 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:23:01 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = FSP based PowerNV system

  Canonical,

  We need this patch in 16.04 GA 4.4 kernel. This fix will avoid the
  following error:

  Oct 19 22:15:07 tul217p1 kernel: sched: RT throttling activated
  Oct 19 22:15:49 tul217p1 kernel: INFO: rcu_sched self-detected stall on CPU
  Oct 19 22:15:49 tul217p1 kernel:21-...: (85 GPs behind) 
idle=d29/142/0 softirq=26316/26316 fqs=4417
  Oct 19 22:15:49 tul217p1 kernel: (t=5250 jiffies g=30019 c=30018 
q=20591)
  Oct 19 22:15:49 tul217p1 kernel: Call Trace:
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f110] [c00fcbe0] 
sched_show_task+0xe0/0x180 (unreliable)
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f180] [c013fcf4] 
rcu_dump_cpu_stacks+0xe4/0x150
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f1d0] [c0145424] 
rcu_check_callbacks+0x6b4/0x9b0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f300] [c014d288] 
update_process_times+0x58/0xa0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f330] [c01649b8] 
tick_sched_handle.isra.6+0x48/0xe0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f370] [c0164ab4] 
tick_sched_timer+0x64/0xd0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f3b0] [c014dd54] 
__hrtimer_run_queues+0x124/0x450
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f440] [c014ed7c] 
hrtimer_interrupt+0xec/0x2c0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f500] [c001f5fc] 
__timer_interrupt+0x8c/0x290
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f550] [c001f9b0] 
timer_interrupt+0xa0/0xe0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f580] [c00099d8] 
restore_check_irq_replay+0x54/0x70
  Oct 19 22:15:49 tul217p1 kernel: --- interrupt: 901 at 
arch_local_irq_restore+0x74/0x90
   LR = arch_local_irq_restore+0x74/0x90
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f870] [7fff] 
0x7fff (unreliable)
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f890] [c00bf808] 
__do_softirq+0xd8/0x3e0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f980] [c00bfd88] 
irq_exit+0xc8/0x100
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f9a0] [c001f9b4] 

[Kernel-packages] [Bug 1728489] Re: tar -x sometimes fails on overlayfs

[Khaled El Mously]

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

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

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


** Tags added: verification-needed-xenial

** Tags added: verification-needed-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/1728489

Title:
  tar -x sometimes fails on overlayfs

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

Bug description:
  [SRU Justification]

  [Impact]
  A user is seeing failures from extracting tar archives on overlay filesystems 
on the 4.4 kernel in constrained environments. The error presents as: 

  `tar: ./deps/0/bin: Directory renamed before its status could be
  extracted`

  Following this thread (http://www.spinics.net/lists/linux-
  unionfs/msg00856.html), it appears that this occurs when entries in
  the kernel's inode cache are reclaimed, and subsequent lookups return
  new inode numbers.

  Further testing showed that when setting
  `/proc/sys/vm/vfs_cache_pressure` to 0 (don't allow the kernel to
  reclaim inode cache entries due to memory pressure) the error does not
  recur, supporting the hypothesis that cache entries are being evicted.
  However, this setting may lead to a kernel OOM so is not a reasonable
  workaround even temporarily.

  The error cannot be reproduced on a 4.13 kernel, due to the series at
  https://www.spinics.net/lists/linux-fsdevel/msg110235.html. The
  particular relevant commit is
  b7a807dc2010334e62e0afd89d6f7a8913eb14ff, which needs a couple of
  dependencies.

  [Fix]
  For Zesty, backport the entire series.
  For Xenial, where a full backport is not feasible, backport the key commit 
and the short list of dependencies.

  [Testcase]

  # Testing this bug

  The testcase for this particular bug is simple - create an overlay
  filesystem with all layers on the same underlying file system, and
  then see if the inode of a directory is constant across dropping the
  caches:

  mkdir -p /upper/upper /upper/work /lower
  mount -t overlay none /mnt -o 
lowerdir=/lower,upperdir=/upper/upper,workdir=/upper/work
  cd /mnt
  mkdir a
  stat a # observe inode number
  echo 2 > /proc/sys/vm/drop_caches
  stat a # compare inode number

  If the inode number is the same, the fix is successful.

  # Regression testing

  I have run the unionmount test suite from
  http://git.infradead.org/users/dhowells/unionmount-testsuite.git in
  overlay mode (./run --ov), and verified that it still passes.

  (The series cover letter mentions a fork of the test suite at
  https://github.com/amir73il/unionmount-testsuite/commits/overlayfs-
  devel. I have *not* attempted to get this running: it assumes a range
  of changes that are not present in our kernels.)

  [Regression Potential]
  As this changes overlayfs, there is potential for regression in the form of 
unexpected breakages to overlaysfs behaviour.

  I think this is adequately addressed by the regression testing.

  One option to reduce the regression potential on Zesty is to reduce
  the set of patches applied - rather than including the whole series we
  could include just the patches to solve this bug, which are much
  easier to inspect for correctness.

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

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

[Kernel-packages] [Bug 1728739] Re: Attempt to map rbd image from ceph jewel/luminous hangs

[Khaled El Mously]

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

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

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


** Tags added: verification-needed-xenial

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

Title:
  Attempt to map rbd image from ceph jewel/luminous hangs

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

Bug description:
  [Impact]

  Attempting to map an rbd image using the 4.4 LTS (Xenial) kernel
  client from a Jewel or Luminous Ceph cluster with optimal tunables
  fails due to feature set mismatch.

  The Jewel release of Ceph introduced a new set of CRUSH tunables.
  These tunables were first introduced in the 4.5 Linux kernel and are
  thus not available in the 16.04 LTS 4.4 Linux Kernel. Attempting to
  map RBD images as block devices will fail due to not being able to
  understand these new tunables:

  (from kern.log)

  Oct 30 21:19:05 ceph-7 kernel: [  815.674075] Key type ceph registered
  Oct 30 21:19:05 ceph-7 kernel: [  815.676862] libceph: loaded (mon/osd proto 
15/24)
  Oct 30 21:19:05 ceph-7 kernel: [  815.678970] rbd: loaded (major 251)
  Oct 30 21:19:05 ceph-7 kernel: [  815.689556] libceph: mon0 10.5.0.19:6789 
feature set mismatch, my 106b84a842a42 < server's 40106b84a842a42, missing 
400
  Oct 30 21:19:05 ceph-7 kernel: [  815.692897] libceph: mon0 10.5.0.19:6789 
missing required protocol features

  Support for the new CRUSH tunables were added in upstream kernel 4.5
  in http://www.spinics.net/lists/ceph-devel/msg28421.html.

  [Test Case]

  1. Deploy a Jewel or Luminous Ceph cluster.
  2. Create rbd image suitable for the kernel client:
$ rbd create --pool rbd --image-feature layering --size 1G test
  3. Map the rbd image to the local server:
$ rbd map --pool rbd test

  [Regression Potential]

  Minimal. Code is limited to kernel rbd driver and new code should
  primarily affect clients connecting to clusters with the new tunables
  options.

  [Additional Info]

  A workaround is to change the crush tunables configured for the Ceph
  cluster to a legacy version (hammer or lower) via:

  $ ceph osd crush tunables hammer

  However, changing the tunables to hammer fails to allow the cluster to take 
advantage of newer placement strategies which reduces the amount of data 
movement throughout the cluster.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 01:23 seq
   crw-rw 1 root audio 116, 33 Oct 31 01:23 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-0001
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic 
root=UUID=d7006b2f-ace6-464d-8b21-17180b3ed360 ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-98-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.1-1ubuntu1~cloud0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-zesty
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.1-1ubuntu1~cloud0:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr15.0.6:cvnQEMU:ct1:cvrpc-i440fx-zesty:
  dmi.product.name: OpenStack Nova
  dmi.product.version: 15.0.6
  dmi.sys.vendor: OpenStack Foundation

To manage 

[Kernel-packages] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC

[Khaled El Mously]

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

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

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


** Tags added: verification-needed-xenial

** Tags added: verification-needed-zesty

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

Title:
  Cannot pair BLE remote devices when using combo BT SoC

Status in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in bluez source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in bluez source package in Zesty:
  New
Status in linux source package in Zesty:
  Fix Committed
Status in bluez source package in Artful:
  New
Status in linux source package in Artful:
  Fix Committed

Bug description:
  It has been observed that sometimes it is not possible to pair with
  BLE remote devices when the host system is using combo (WiFi + BT)
  chip.

  The root cause of the disconnection has been identified as coming from
  the internal to bluez timeout. If bluez does not hear any reply from for
  two seconds the link is automagically disconnected. The reason fro the
  silence is not however a failure of the remote device but quite often a
  delay in the WiFi/BT combo driver that causes the packages not to reach
  the bluez stack.

  [Impact]

  Not possible to pair BLE remote devices such as sensors and such with
  Ubuntu when the host system uses BT+WiFi combo SoC. The connection
  attempt is disturbed with a timeout.

  [Fix]

  It has been fixed by increasing the timeout value from 2 seconds to
  4 seconds. It is enough for the events to reach the stack (measured
  that it takes between 3 and 3.5 seconds).

  [Testcase]

  Tested with the device that failed to connect to Ubuntu Core gateway.
  It fails w/o the patch, it connects just fine with the patch applied.

  [Regression Potential]

  Very small. The increased timeout is taken into consideration only for
  new and scan report triggered connections. It will not make any already
  working device to fail to pair.

  [Other Info]

  The bug has been discussed and fixed here:

  https://marc.info/?l=linux-bluetooth=150824844606937=2

  [Patch]

  https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-
  next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571

  The patch has been accepted by the upstream and will be a part of the next
  kernel release. Currently in the bluetooth-next tree.

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

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

[Kernel-packages] [Bug 1708130] Re: ISST-LTE: Ubuntu16.04.03: PowerNV: 'ppc64_cpu' commands hangs while changing SMT value with Leaf IO and BASE tests

[Manoj Iyer]

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Kernel (canonical-kernel)

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

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

Title:
  ISST-LTE: Ubuntu16.04.03: PowerNV: 'ppc64_cpu' commands hangs while
  changing SMT value with Leaf IO and BASE tests

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

Bug description:
  == Comment: #0 - INDIRA P. JOGA  - 2017-07-07 
03:56:54 ==
  Description:
  --
  Started Leaf IO and BASE(without smt tests)and then tried to change the SMT 
value manually where it hangs

UBUNTU BUILD: 4.10.0-26-generic

  Steps to re-create:
  --
  > Installed latest Ubuntu160403 kernel on system lotkvm
  4.10.0-26-generic

  > Leaf microcode: KMIPP113

  > Started Leaf IO and BASE tests(without smt tests).

  root@lotkvm:/home# show.report.py
  HOSTNAMEKERNEL VERSION   DISTRO INFO
  ----
  lotkvm  4.10.0-26-genericUbuntu 16.04.2 LTS \n \l

   Current Time: Tue Jul  4 00:55:37 2017 
  Job-IDFOCUS   Start-Time  DurationFunction
  ---   --  
  1 IO  20170704-00:44:45   0.0 hr(s) 10.0 min(s)   IO_Focus
  2 BASE20170704-00:44:52   0.0 hr(s) 10.0 min(s)   Test

  FOCUS IO  BASESUM
  TOTAL 76  25  101
  FAIL  0   4   4
  PASS  76  21  97
  (%)   (100%)  (84%)   (96%)

  >Now manually changed the smt value

  root@lotkvm:/home# ppc64_cpu --smt
  SMT=8
  root@lotkvm:/home# date
  Tue Jul  4 00:46:01 CDT 2017
  root@lotkvm:/home# ppc64_cpu --smt=2
  root@lotkvm:/home# ppc64_cpu --smt
  SMT=2
  root@lotkvm:/home# date
  Tue Jul  4 00:50:01 CDT 2017
  root@lotkvm:/home# ppc64_cpu --smt=4
  root@lotkvm:/home# ppc64_cpu --smt
  SMT=4
  root@lotkvm:/home# date
  Tue Jul  4 00:54:38 CDT 2017
  root@lotkvm:/home# ppc64_cpu --smt=8

  
  [ 2055.142781] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 
seconds.
  [ 2055.142915]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.142978] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.143150] INFO: task kworker/48:0H:21755 blocked for more than 120 
seconds.
  [ 2055.143226]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.143289] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.143570] INFO: task kworker/u259:3:22436 blocked for more than 120 
seconds.
  [ 2055.143647]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.143709] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.143953] INFO: task kworker/8:188:118516 blocked for more than 120 
seconds.
  [ 2055.144029]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144091] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.144289] INFO: task mkfs.ntfs:95505 blocked for more than 120 seconds.
  [ 2055.144353]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.144600] INFO: task ppc64_cpu:80305 blocked for more than 120 seconds.
  [ 2055.144665]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144727] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.144872] INFO: task rm:80950 blocked for more than 120 seconds.
  [ 2055.144936]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144998] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.145133] INFO: task rm:80951 blocked for more than 120 seconds.
  [ 2055.145195]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.145257] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2175.974718] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 
seconds.
  [ 2175.974848]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2175.974912] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2175.975068] INFO: task kworker/48:0H:21755 blocked for more than 120 
seconds.
  [ 2175.975144]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2175.975206] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  
  >  root@lotkvm:# ps -eaf | grep ppc*
  root  48054  12068  0 01:24 pts/000:00:00 grep --color=auto ppc*
  root  

[Kernel-packages] [Bug 1708130] Re: ISST-LTE: Ubuntu16.04.03: PowerNV: 'ppc64_cpu' commands hangs while changing SMT value with Leaf IO and BASE tests

[Andrew Cloke]

** Changed in: ubuntu-power-systems
   Status: Triaged => 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/1708130

Title:
  ISST-LTE: Ubuntu16.04.03: PowerNV: 'ppc64_cpu' commands hangs while
  changing SMT value with Leaf IO and BASE tests

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

Bug description:
  == Comment: #0 - INDIRA P. JOGA  - 2017-07-07 
03:56:54 ==
  Description:
  --
  Started Leaf IO and BASE(without smt tests)and then tried to change the SMT 
value manually where it hangs

UBUNTU BUILD: 4.10.0-26-generic

  Steps to re-create:
  --
  > Installed latest Ubuntu160403 kernel on system lotkvm
  4.10.0-26-generic

  > Leaf microcode: KMIPP113

  > Started Leaf IO and BASE tests(without smt tests).

  root@lotkvm:/home# show.report.py
  HOSTNAMEKERNEL VERSION   DISTRO INFO
  ----
  lotkvm  4.10.0-26-genericUbuntu 16.04.2 LTS \n \l

   Current Time: Tue Jul  4 00:55:37 2017 
  Job-IDFOCUS   Start-Time  DurationFunction
  ---   --  
  1 IO  20170704-00:44:45   0.0 hr(s) 10.0 min(s)   IO_Focus
  2 BASE20170704-00:44:52   0.0 hr(s) 10.0 min(s)   Test

  FOCUS IO  BASESUM
  TOTAL 76  25  101
  FAIL  0   4   4
  PASS  76  21  97
  (%)   (100%)  (84%)   (96%)

  >Now manually changed the smt value

  root@lotkvm:/home# ppc64_cpu --smt
  SMT=8
  root@lotkvm:/home# date
  Tue Jul  4 00:46:01 CDT 2017
  root@lotkvm:/home# ppc64_cpu --smt=2
  root@lotkvm:/home# ppc64_cpu --smt
  SMT=2
  root@lotkvm:/home# date
  Tue Jul  4 00:50:01 CDT 2017
  root@lotkvm:/home# ppc64_cpu --smt=4
  root@lotkvm:/home# ppc64_cpu --smt
  SMT=4
  root@lotkvm:/home# date
  Tue Jul  4 00:54:38 CDT 2017
  root@lotkvm:/home# ppc64_cpu --smt=8

  
  [ 2055.142781] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 
seconds.
  [ 2055.142915]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.142978] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.143150] INFO: task kworker/48:0H:21755 blocked for more than 120 
seconds.
  [ 2055.143226]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.143289] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.143570] INFO: task kworker/u259:3:22436 blocked for more than 120 
seconds.
  [ 2055.143647]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.143709] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.143953] INFO: task kworker/8:188:118516 blocked for more than 120 
seconds.
  [ 2055.144029]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144091] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.144289] INFO: task mkfs.ntfs:95505 blocked for more than 120 seconds.
  [ 2055.144353]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.144600] INFO: task ppc64_cpu:80305 blocked for more than 120 seconds.
  [ 2055.144665]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144727] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.144872] INFO: task rm:80950 blocked for more than 120 seconds.
  [ 2055.144936]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144998] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.145133] INFO: task rm:80951 blocked for more than 120 seconds.
  [ 2055.145195]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.145257] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2175.974718] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 
seconds.
  [ 2175.974848]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2175.974912] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2175.975068] INFO: task kworker/48:0H:21755 blocked for more than 120 
seconds.
  [ 2175.975144]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2175.975206] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  
  >  root@lotkvm:# ps -eaf | grep ppc*
  root  48054  12068  0 01:24 pts/000:00:00 grep --color=auto ppc*
  root  80305   5719  0 00:54 hvc0 00:00:00 ppc64_cpu --smt 8

  > ppc64_cpu --smt command hangs here . Not able to change the SMT
  value from 4 to 8.

  > Attached dmesg logs

  == Comment: #2 - VIPIN K. 

[Kernel-packages] [Bug 1708409] Re: kdump service does not start after configure/reboot

[Andrew Cloke]

** Tags added: ppc64el-kdump

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

Title:
  kdump service does not start after configure/reboot

Status in The Ubuntu-power-systems project:
  Triaged
Status in makedumpfile package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Triaged
Status in makedumpfile source package in Artful:
  New
Status in systemd source package in Artful:
  New
Status in makedumpfile source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Triaged

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

  ...
  https://github.com/systemd/systemd/issues/6334

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

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

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

[Kernel-packages] [Bug 1707875] Re: [18.04] include support for Python bindings in "perf"

[Manoj Iyer]

** Summary changed:

- include support for Python bindings in "perf"
+ [18.04] include support for Python bindings in "perf"

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

Title:
  [18.04] include support for Python bindings in "perf"

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

Bug description:
  == Comment: #0 - Paul A. Clarke  - 2017-07-26 09:59:57 ==
  ---Problem Description---
  Request to build python bindings support with perf.

  ---Steps to Reproduce---
   Ubuntu-17.04# perf script -g python
  Python scripting not supported.  Install libpython and rebuild perf to enable 
it.
  For example:
# apt-get install python-dev (ubuntu)
# yum install python-devel (Fedora)
etc.
   
  Userspace tool common name: perf 
   
  Userspace rpm: linux-tools-common 

  Userspace tool obtained from project website:  na

  == Comment: #2 - MAMATHA INAMDAR  - 2017-08-01 05:02:34 
==
  After installing libpython, downloaded ubuntu 17.04 linux source code and 
compiled perf tool then it works fine.

  # ./perf script  -g python 
  generated Python script: perf-script.py

  but when I run perf tool without rebuilding after installing libpython
  it shows an error

  # perf script  -g python 
  Python scripting not supported.  Install libpython and rebuild perf to enable 
it.
  For example:
# apt-get install python-dev (ubuntu)
# yum install python-devel (Fedora)
etc.
  root@p8wookie:/home/Mamatha/ubuntu/ubuntu-zesty/tools/perf# perf --version
  perf version 4.10.17

  == Comment: #3 - MAMATHA INAMDAR  - 2017-08-01 05:03:44 
==
  Request to build python bindings support with perf.

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

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

[Kernel-packages] [Bug 1708096] Re: Ubuntu16.04.3 Installation fails for JFS file system

[Manoj Iyer]

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

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

Title:
  Ubuntu16.04.3 Installation fails for JFS file system

Status in The Ubuntu-power-systems project:
  Opinion
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ---Problem Description---

  Ubuntu16.04.3 installation fails for JFS file system.

  
  ---Environment---
  Garrison Power8

  
  ---Steps to reproduce---
   Install Ubuntu 16.04.3 with 
   - prepboot
  - /root [JFS filesystem]
  - swap space

  
  ---Fails in below step---

   ?? [!!] Install the GRUB boot loader on a hard disk ??
? ?
?  ?Unable to install GRUB in /dev/sdi1 ? ?
?  ? Executing 'grub-install /dev/sdi1' failed. ? ?
?  ?? ?
? Running "? This is a fatal error. ? ?
?  ?? ?
 ? ?
   ??
   ??



  
   moves;  selects;  activates buttons



  
   ? [!!] Install the GRUB boot loader on a hard disk ??
   ?   ?
   ? Installation step failed  ?
   ? An installation step failed. You can try to run the failing item  ?
   ? again from the menu, or skip it and choose something else. The?
   ? failing step is: Install the GRUB boot loader on a hard disk  ?
   ?   ?
   ? ?
   ?   ?
   ?



  
   moves;  selects;  activates buttons

  
  Comment 3 2017-07-20 04:31:05 CDT

  Based on your error, may be you deleted partition 1 (8MB the PReP boot
  partition) which is required for installing the boot loader in IBM
  power systems.  Or maybe you changed the use type to JFS from PReP
  boot.

  Partition 1 (PReP boot) does NOT contain a filesystem and is not
  mounted.Grub is written to it raw and the firmware loads the contents
  of the partition into ram and executes it raw.

  Can you try one more time,
  Pick the default guided partitioning, then change the root 
partition(partition 2) from ext4(or  filesystem) to JFS.Do not delete and 
create any partitions from the default guided setup. Paste the results.

  Comment 4  2017-07-20 09:22:22 CDT

  (In reply to comment #3)
  > Based on your error, may be you deleted partition 1 (8MB the PReP boot
  > partition) which is required for installing the boot loader in IBM power
  > systems.  Or maybe you changed the use type to JFS from PReP boot. 
  > 
  > Partition 1 (PReP boot) does NOT contain a filesystem and is not
  > mounted.Grub is written to it raw and the firmware loads the contents of the
  > partition into ram and executes it raw.
  > 
  > Can you try one more time,
  > Pick the default guided partitioning, then change the root
  > partition(partition 2) from ext4(or  filesystem) to JFS.Do not delete
  > and create any partitions from the default guided setup. Paste the results.

  No, I have not deleted partition and I have not changed the use type
  to JFS from PReP boot.

  Any ways I tried again and it still fails.

  ?? [!!] Partition disks ???
? ?
? This is an overview of your currently configured partitions and mount   ?
? points. Select a partition to modify its settings (file system, mount   ?
? point, etc.), a free space to create partitions, or a device to ?
? initialize its partition table. ?
? ?
?  SCSI4 (0,0,0) (sdi) - 1.0 TB ATA ST1000NX0313  ?
?  >1.0 MBFREE SPACE  ?   ?
?  > #1 7.3 MB K  ?   ?
?  > #2   959.7 GB F  ext4  / ?   ?
?  > #340.5 GB f  swap  swap  ?
?  >  728.6 kBFREE SPACE  ?   ?
?  SCSI5 (0,0,0) (sdj) - 1.0 TB ATA ST1000NX0313  ?   ?

[Kernel-packages] [Bug 1704730] Re: xfstest fails with corrupt file /mnt/scratch/1 - non-zero size but no extents ( ext4 )

[Andrew Cloke]

** Tags removed: triage-a
** Tags added: triage-r

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

Title:
  xfstest fails with corrupt file /mnt/scratch/1 - non-zero size but no
  extents ( ext4 )

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

Bug description:
  xfstests fails non-zero size but no extents on ext4 filesystem

  Environment
  --
  Kernel Build:  4.12.1-041201-generic

  Model  : 8247-22L
  Platform:  PowerNV ( P8 )

  Uname output
  ---
  # uname -a
  Linux ltc-test-ci2 4.12.1-041201-generic #201707121132 SMP Wed Jul 12 
17:03:25 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Create a loop device with ext4 filesystem
  2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd 
xfstests-dev
  3. make
  4. Create a local.config for running with created loop device
  5. Run xfstests-dev test  : ./check tests/generic/044

  The test 044 fails with following
  generic/044 - output mismatch (see 
/root/harish/xfstests-dev/results//generic/044.out.bad)
  --- tests/generic/044.out 2017-07-13 06:04:36.208323135 -0400
  +++ /root/harish/xfstests-dev/results//generic/044.out.bad
2017-07-14 06:24:08.153731112 -0400
  @@ -1 +1,1000 @@
   QA output created by 044
  +corrupt file /mnt/scratch/1 - non-zero size but no extents
  +corrupt file /mnt/scratch/2 - non-zero size but no extents
  +corrupt file /mnt/scratch/3 - non-zero size but no extents
  +corrupt file /mnt/scratch/4 - non-zero size but no extents
  +corrupt file /mnt/scratch/5 - non-zero size but no extents
  +corrupt file /mnt/scratch/6 - non-zero size but no extents
  ...
  (Run 'diff -u tests/generic/044.out 
/root/harish/xfstests-dev/results//generic/044.out.bad'  to see the entire diff)
  Ran: generic/044
  Failures: generic/044
  Failed 1 of 1 tests

  
  Dmesg:
  --
  [17244.878673] EXT4-fs (loop0): mounted filesystem with ordered data mode. 
Opts: (null)
  [17245.517227] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17245.697100] EXT4-fs (loop0): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17245.710634] run fstests generic/044 at 2017-07-14 06:23:49
  [17246.534410] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17246.535534] EXT4-fs (loop2): shut down requested (1)
  [17246.535625] Aborting journal on device loop2-8.
  [17247.278467] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17259.888304] EXT4-fs (loop2): shut down requested (2)
  [17259.995751] Aborting journal on device loop2-8.
  [17260.113582] EXT4-fs (loop2): recovery complete
  [17260.113902] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17260.190076] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr
  [17264.821978] EXT4-fs (loop2): mounted filesystem with ordered data mode. 
Opts: acl,user_xattr


  == Comment: #2 - SEETEENA THOUFEEK  - 2017-07-17 
02:10:52 ==
  Issue does not happen when running the same test with xfs file system. (ie, 
creating loop device with xfs file system).

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

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

[Kernel-packages] [Bug 1681909] Re: Ubuntu 17.04: dump is not captured in remote host when kdump over ssh is configured on firestone.

[Andrew Cloke]

** Tags added: ppc64el-kdump

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

Title:
  Ubuntu 17.04: dump is not captured in remote host when kdump over ssh
  is configured on firestone.

Status in The Ubuntu-power-systems project:
  New
Status in makedumpfile package in Ubuntu:
  New

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH  - 2017-03-07 
05:00:29 ==
  ---Problem Description---

  Ubuntu 17.04: dump is not captured in remote host when kdump over ssh
  is configured on firestone.

  ---Steps to Reproduce---

  1. Configure kdump.
  2. Check whether kdump is operational using ?# kdump-config show?.
  3. Install ?kernel-debuginfo? and ?kernel-debuginfo-common? rpms.
  4. Setup password less ssh connection, generate rsa key.
  # ssh-keygen -t rsa
  5. verify id_rsa and id_rsa.pub are created under /root/.ssh/
  6. Edit /etc/default/kdump-tools and add below entries.
  SSH="ubuntu@9.114.15.239"
  SSH_KEY=/root/.ssh/id_rsa
  7. Propagate RSA key.
  # kdump-config propagate
  8. Restart kdump service.
  # kdump-config load
  9. Trigger Crash using below commands.
  # echo "1" > /proc/sys/kernel/sysrq
  # echo "c" > /proc/sysrq-trigger
  10. Verify dump is available in remote server in configured path.

  Machine details
  ===

  $ ipmitool -I lanplus -H  9.47.70.3 -U ADMIN -P admin sol activate

  $ ssh ubuntu@9.47.70.29

  PW: shriya101

  
  Attaching logs

  == Comment: #1 - PAVITHRA R. PRAKASH  -
  2017-03-07 05:01:42 ==

  
  == Comment: #5 - PAVITHRA R. PRAKASH  - 2017-03-07 
23:19:46 ==
  Hi, 

  Attaching the logs.

  Network info:

  root@ltc-firep3:~# hwinfo --network
  36: None 00.0: 10700 Loopback   
[Created at net.126]
Unique ID: ZsBS.GQNx7L4uPNA
SysFS ID: /class/net/lo
Hardware Class: network interface
Model: "Loopback network interface"
Device File: lo
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown

  37: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: 2lHw.ndpeucax6V1
Parent ID: mIXc.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f2
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.2
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f2
HW Address: 98:be:94:03:18:4a
Permanent HW Address: 98:be:94:03:18:4a
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #15 (Ethernet controller)

  38: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: 7Onn.ndpeucax6V1
Parent ID: sx0U.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f0
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.0
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f0
HW Address: 98:be:94:03:18:48
Permanent HW Address: 98:be:94:03:18:48
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #16 (Ethernet controller)

  39: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: VwX_.ndpeucax6V1
Parent ID: DUng.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f3
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.3
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f3
HW Address: 98:be:94:03:18:4b
Permanent HW Address: 98:be:94:03:18:4b
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #25 (Ethernet controller)

  40: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: bZ1s.ndpeucax6V1
Parent ID: J7HY.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f1
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.1
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f1
HW Address: 98:be:94:03:18:49
Permanent HW Address: 98:be:94:03:18:49
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #4 (Ethernet controller)
  root@ltc-firep3:~# 


  Thanks,
  Pavithra

  == Comment: #6 - PAVITHRA R. PRAKASH  -
  2017-03-07 23:20:47 ==

  
  == Comment: #7 - PAVITHRA R. PRAKASH  - 2017-03-07 
23:21:27 ==

  
  == Comment: #8 - Urvashi Jawere  - 2017-03-08 02:48:15 ==
  I am able to see some errors in syslog ;

  auxiliary
  Mar  7 04:57:44 ltc-firep3 

[Kernel-packages] [Bug 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore

[Andrew Cloke]

** Tags added: ppc64el-kdump

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04.2: cp: error reading '/proc/vmcore':
  Bad address when trying to dump vmcore

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

Bug description:
  == Comment: #0 - Ping Tian Han  - 2017-01-09 02:51:00 ==
  ---Problem Description---
  Vmcore cannot be saved when triggering bug 150353 on roselp4:

  Copying data   : [  2.0 %] \/usr/sbin/kdump-config: line 
591:  5502 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [  512.833872] kdump-tools[5450]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [  573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad 
address
  [  573.605717] kdump-tools[5450]:  * kdump-tools: failed to save vmcore in 
/var/crash/201701090223
  [  573.765417] kdump-tools[5450]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701090223/dmesg.201701090223
  [  574.285506] kdump-tools[5450]: The kernel version is not supported.
  [  574.285672] kdump-tools[5450]: The makedumpfile operation may be 
incomplete.
  [  574.285767] kdump-tools[5450]: The dmesg log is saved to 
/var/crash/201701090223/dmesg.201701090223.
  [  574.305422] kdump-tools[5450]: makedumpfile Completed.
  [  574.315363] kdump-tools[5450]:  * kdump-tools: saved dmesg content in 
/var/crash/201701090223
  [  574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600
  [  574.705384] kdump-tools[5450]: Rebooting.
   Stopping ifup for ib0...
  [  OK  ] Stopped ifup for ib0.
  [ 1008.579897] reboot: Restarting system
   
  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com 
   
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. config kdump on roselp4
  2. try to trigger bug 150353

   
  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan  -
  2017-01-10 02:42:25 ==

  root@roselp4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic 
root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet 
crashkernel=384M-:512M

  root@roselp4:~# dmesg | grep Reser
  [0.00] Reserving 512MB of memory at 128MB for crashkernel (System 
RAM: 21760MB)

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

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

[Kernel-packages] [Bug 1635597] Re: Ubuntu:talclp1: Kdump failed with multipath disk

[Andrew Cloke]

** Tags added: ppc64el-kdump

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

Title:
  Ubuntu:talclp1: Kdump failed with multipath disk

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Confirmed
Status in linux source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  Confirmed

Bug description:
  [Impact]
  When the target device where to dump the kernel is under a multipath 
configuration, dumping will fail, possibly leaving the system stuck in the 
kdump kernel.
  The fix is to include some scsi device handlers needed for the multipath 
setup inside the initramfs image that is used by kdump.
  All modules currently loaded in the system are included.

  [Test Case]
  Setting up kdump to target a multipath device using an appropriate storage 
that requires such scsi_dh modules and triggering a crash will demonstrate that 
kdump fails.
  After the fix, it works fine.

  [Regression Potential]
  If a bug is introduced, loading kdump might fail, and a crash will not be 
generated. A worse regression that might be considered is the system is stuck 
in such a kdump kernel and needs to be rebooted locally (and the crash file is 
not generated either). But since this is what we are trying to fix, we don't 
expect other systems to break. This didn't happen on a small (less than 1GiB of 
RAM) x86 VM, though.

  Problem  Description
  ==
  On talclp1, I enabled kdump. But kdump failed and it drop to BusyBox.

  root@talclp1:~# echo c> /proc/sysrq-trigger
  [  132.643690] sysrq: SysRq : Trigger a crash
  [  132.643739] Unable to handle kernel paging request for data at address 
0x
  [  132.643745] Faulting instruction address: 0xc05c28f4
  [  132.643749] Oops: Kernel access of bad area, sig: 11 [#1]
  [  132.643753] SMP NR_CPUS=2048 NUMA pSeries
  [  132.643758] Modules linked in: fuse ufs qnx4 hfsplus hfs minix ntfs msdos 
jfs rpadlpar_io rpaphp rpcsec_gss_krb5 nfsv4 dccp_diag cifs nfs dns_resolver 
dccp tcp_diag fscache udp_diag inet_diag unix_diag af_packet_diag netlink_diag 
binfmt_misc xfs libcrc32c pseries_rng rng_core ghash_generic gf128mul 
vmx_crypto sg nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache crc32c_generic btrfs xor raid6_pq 
dm_round_robin sr_mod sd_mod cdrom ses enclosure scsi_transport_sas ibmveth 
crc32c_vpmsum ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath dm_mod
  [  132.643819] CPU: 49 PID: 10174 Comm: bash Not tainted 4.8.0-15-generic 
#16-Ubuntu
  [  132.643824] task: c00111767080 task.stack: c000d82e
  [  132.643828] NIP: c05c28f4 LR: c05c39d8 CTR: 
c05c28c0
  [  132.643832] REGS: c000d82e3990 TRAP: 0300   Not tainted  
(4.8.0-15-generic)
  [  132.643836] MSR: 80009033   CR: 28242422  
XER: 0001
  [  132.643848] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1
  GPR00: c05c39d8 c000d82e3c10 c0f67b00 0063
  GPR04: c0011d04a9b8 c0011d05f7e0 c0047fb0 00015998
  GPR08: 0007 0001  0001
  GPR12: c05c28c0 c7b4b900  2200
  GPR16: 10170dc8 01002b566368 10140f58 100c7570
  GPR20:  1017dd58 10153618 1017b608
  GPR24: 3e87a294 0001 c0ebff60 0004
  GPR28: c0ec0320 0063 c0e72a90 
  [  132.643906] NIP [c05c28f4] sysrq_handle_crash+0x34/0x50
  [  132.643911] LR [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643914] Call Trace:
  [  132.643917] [c000d82e3c10] [c0a245e8] 0xc0a245e8 
(unreliable)
  [  132.643923] [c000d82e3c30] [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643928] [c000d82e3cd0] [c05c4188] 
write_sysrq_trigger+0x78/0xa0
  [  132.643935] [c000d82e3d00] [c03ad770] proc_reg_write+0xb0/0x110
  [  132.643941] [c000d82e3d50] [c030fc3c] __vfs_write+0x6c/0xe0
  [  132.643946] [c000d82e3d90] [c0311144] vfs_write+0xd4/0x240
  [  132.643950] [c000d82e3de0] [c0312e5c] SyS_write+0x6c/0x110
  [  132.643957] [c000d82e3e30] [c00095e0] system_call+0x38/0x108
  [  132.643961] Instruction dump:
  [  132.643963] 38425240 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 
3949ba60
  [  132.643972] 3921 912a 7c0004ac 3940 

[Kernel-packages] [Bug 1658733] Re: Ubuntu 16.04.2KVM:kdump fails to mount root file system when noirqdistrib is missing as dump kernel parameter

[Andrew Cloke]

** Tags added: ppc64el-kdump

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

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system when
  noirqdistrib is missing as dump kernel parameter

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  In Progress
Status in kexec-tools source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  New
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  In Progress
Status in kexec-tools source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  New
Status in kexec-tools source package in Artful:
  Invalid
Status in makedumpfile source package in Artful:
  In Progress

Bug description:
  [Impact]
  On Power Systems, some interrupts are missed, and dumping the crash will 
fail. Adding the noirqdistrib kernel parameter to the kdump kernel will fix 
this.

  [Test Case]
  Setting up kdump to target a virtio-scsi device on a Power System.

  [Regression Potential]
  The parameter could be interpreted differently on a different platform and 
kdump would fail. However, it has been verified that no other platform uses 
such parameter. If another parameter would have been incorrectly removed on the 
patch, kdump could fail on other systems.


  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel
  fails to mount the root file system.  This error does not occur in a
  similar guest installed to a single path device.

  Full console output of the kdump failure is attached.  These messages
  from the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.

  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest

  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  >
  > Could you please recreate the guest for further debug?

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and perform its tasks by setting
  > KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see
  > http://pastebin.hursley.ibm.com/8239
  >
  > I'm still investigating to figure out what is the reason behind this
  > behavior.
  >
  > Thanks,
  >
  > --
  > maurosr

 

[Kernel-packages] [Bug 1680349] Re: Ubuntu 17.04: Kdump fails to capture dump on Firestone NV when machine crashes while running stress-ng.

[Andrew Cloke]

** Tags added: ppc64el-kdump

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

Title:
  Ubuntu 17.04: Kdump fails to capture dump on Firestone NV when machine
  crashes while running stress-ng.

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

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-03-10 02:43:10 ==
  ---Problem Description---

  Ubuntu 17.04: Kdump fails to capture dump on Firestone NV when machine
  crashes while running stress-ng. Machine hangs.

  ---Steps to Reproduce---

  1. Configure kdump.
  2. Install stress-ng
  # apt-get install stress-ng
  3. Run stress-ng
  # stress-ng - a 0

  
  Logs:
  
  root@ltc-firep3:~# kdump-config load
  Modified cmdline:root=UUID=8b0d5b99-6087-4f40-82ea-375c83a4c139 ro quiet 
splash irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0 elfcorehdr=155200K 
   * loaded kdump kernel
  root@ltc-firep3:~# 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.10.0-11-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.10.0-11-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=8b0d5b99-6087-4f40-82ea-375c83a4c139 ro quiet splash 
irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img 
/var/lib/kdump/vmlinuz
  root@ltc-firep3:~# stress-ng -a 0
  stress-ng: info:  [3900] defaulting to a 86400 second run per stressor
  stress-ng: info:  [3900] dispatching hogs: 160 af-alg, 160 affinity, 160 aio, 
160 aiol, 160 apparmor, 160 atomic, 160 bigheap, 160 brk, 160 bsearch, 160 
cache, 160 cap, 160 chdir, 160 chmod, 160 chown, 160 chroot, 160 clock, 160 
clone, 160 context, 160 copy-file, 160 cpu, 160 cpu-online, 160 crypt, 160 
daemon, 160 dccp, 160 dentry, 160 dir, 160 dirdeep, 160 dnotify, 160 dup, 160 
epoll, 160 eventfd, 160 exec, 160 fallocate, 160 fanotify, 160 fault, 160 
fcntl, 160 fiemap, 160 fifo, 160 filename, 160 flock, 160 fork, 160 fp-error, 
160 fstat, 160 full, 160 futex, 160 get, 160 getdent, 160 getrandom, 160 
handle, 160 hdd, 160 heapsort, 160 hsearch, 160 icache, 160 icmp-flood, 160 
inotify, 160 io, 160 iomix, 160 ioprio, 160 itimer, 160 kcmp, 160 key, 160 
kill, 160 klog, 160 lease, 160 link, 160 locka, 160 lockbus, 160 lockf, 160 
lockofd, 160 longjmp, 160 lsearch, 160 madvise, 160 malloc, 160 matrix, 160 
membarrier, 160 memcpy, 160 memfd, 160 mergesort, 160 mincore, 160 mknod, 160 
mlock, 160 mmap, 160 mmapfork, 160 mmapmany, 160 mq, 160 mremap, 160 msg, 160 
msync, 160 netlink-proc, 160 nice, 160 nop, 160 null, 160 numa, 160 oom-pipe, 
160 opcode, 160 open, 160 personality, 160 pipe, 160 poll, 160 procfs, 160 
pthread, 160 ptrace, 160 pty, 160 qsort, 160 quota, 160 rdrand, 160 readahead, 
160 remap, 160 rename, 160 resources, 160 rlimit, 160 rmap, 160 rtc, 160 
schedpolicy, 160 sctp, 160 seal, 160 seccomp, 160 seek, 160 sem, 160 sem-sysv, 
160 sendfile, 160 shm, 160 shm-sysv, 160 sigfd, 160 sigfpe, 160 sigpending, 160 
sigq, 160 sigsegv, 160 sigsuspend, 160 sleep, 160 sock, 160 sockfd, 160 
sockpair, 160 spawn, 160 splice, 160 stack, 160 stackmmap, 160 str, 160 stream, 
160 switch, 160 symlink, 160 sync-file, 160 sysfs, 160 sysinfo, 160 tee, 160 
timer, 160 timerfd, 160 tlb-shootdown, 160 tmpfs, 160 tsc, 160 tsearch, 160 
udp, 160 udp-flood, 160 unshare, 160 urandom, 160 userfaultfd, 160 utime, 160 
vecmath, 160 vfork, 160 vforkmany, 160 vm, 160 vm-rw, 160 vm-splice, 160 wait, 
160 wcs, 160 xattr, 160 yield, 160 zero, 160 zlib, 160 zombie
  stress-ng: info:  [3900] cache allocate: using built-in defaults as unable to 
determine cache details
  stress-ng: info:  [3900] cache allocate: default cache size: 2048K
  stress-ng: info:  [3907] stress-ng-atomic: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: info:  [3955] stress-ng-exec: running as root, won't run test.
  stress-ng: info:  [3999] stress-ng-icache: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: info:  [4040] stress-ng-lockbus: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: info:  [4313] stress-ng-numa: system has 2 of a maximum 256 memory 
NUMA nodes
  stress-ng: info:  [4455] stress-ng-rdrand: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: fail:  [4558] stress-ng-rtc: ioctl RTC_ALRM_READ failed, errno=22 
(Invalid argument)
  stress-ng: fail:  [4017] stress-ng-key: keyctl KEYCTL_DESCRIBE failed, 
errno=127 (Key has expired)
  stress-ng: fail:  [4017] 

[Kernel-packages] [Bug 1733864] Re: kernel 4.10.0-40 is hanging with a CPU soft lock

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   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/1733864

Title:
  kernel 4.10.0-40 is hanging with a CPU soft lock

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

Bug description:
  Kernel 4.10.0-40-generic is causing CPU hung on POWER machines. I got
  this problem on a POWER8 KVM virtual machine

  [ 1912.003255] NMI watchdog: BUG: soft lockup - CPU#12 stuck for 24s! 
[dpkg-deb:31284]
  [ 1912.004496] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs msdos jfs 
xfs ipt_REJECT nf_reject_ipv4 xfrm_user xfrm_algo xt_addrtype xt_conntrack 
br_netfilter ebtable_filter ebtables ip6table_filter ip6_tables ib_srpt 
dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio tcm_qla2xxx qla2xxx 
vhost_scsi vhost usb_f_tcm tcm_usb_gadget libcomposite udc_core tcm_fc libfc 
scsi_transport_fc tcm_loop iscsi_target_mod target_core_file target_core_iblock 
target_core_pscsi target_core_mod ipmi_devintf ipmi_msghandler xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat xt_tcpudp 
iptable_filter ip_tables x_tables openvswitch nf_conntrack_ipv6 nf_nat_ipv6 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack 
binfmt_misc zfs(PO) zunicode(PO) zavl(PO) zcommon(PO)
  [ 1912.004575]  znvpair(PO) spl(O) bridge 8021q garp mrp stp llc vmx_crypto 
kvm 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 ibmvscsi ibmveth crc32c_vpmsum virtio_blk
  [ 1912.004624] CPU: 12 PID: 31284 Comm: dpkg-deb Tainted: P   O
4.10.0-40-generic #44~16.04.1-Ubuntu
  [ 1912.004626] task: c00775551e00 task.stack: c007755ac000
  [ 1912.004627] NIP: 3fff86b71960 LR: 3fff86b7319c CTR: 
002d
  [ 1912.004628] REGS: c007755afea0 TRAP: 0901   Tainted: P   O 
(4.10.0-40-generic)
  [ 1912.004629] MSR: 8280f033 
  [ 1912.004635]   CR: 42004442  XER: 2000
  [ 1912.004636] CFAR: 3fff86b719b4 SOFTE: 1 
 GPR00: 00a4 3fffd53f7d70 3fff86ba5008 
0040 
 GPR04: 038a20fc 3fff86467d4b 036c0ed8 
002a 
 GPR08: 3fff81c41010 000a20f5 0081 
ffec0ed1 
 GPR12: 00a6 3fff86c8db30 
  [ 1912.004646] NIP [3fff86b71960] 0x3fff86b71960
  [ 1912.004647] LR [3fff86b7319c] 0x3fff86b7319c
  [ 1912.004647] Call Trace:

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1698700

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

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

Title:
  hibmc driver does not include "pci:" prefix in bus ID

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

Bug description:
  SRU Justification

  [Impact]
  On the HiSilicon D05 (arm64) board, X crashes when started. [0]

  [Fix]
  The crash is attributable to the bus ID that the hibmc driver reports for the 
hibmc graphics card on the board. In particular, the bus id is missing the 
"pci:" prefix that most other cards provide: [1]
  - The busid reported on the arm64 system is "0007:a1:00.0"
  - The busid reported on a amd64 system is "pci::00:02.0"

  X tests for this prefix. A missing prefix for PCI cards leads to an
  Xorg crash.

  Fix this by using the set_pci_busid function from the DRM core.

  [Testcase]
  Successfully tested on a D05 board. [2]

  [Regression Potential]
  Changes are limited to the hibmc driver, so any regression should also be 
limited to that driver.

  [Notes]
  I submitted the patch upstream. However, upstream is refactoring the drm 
core, and set_busid is going away. That does fix this issue but the regression 
potential of the refactor is enormous, so this seems like the wiser approach. 
[3]

  [0]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991
  [1]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/16
  [2]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/29
  [3]: https://www.spinics.net/lists/dri-devel/msg143831.html

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

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

[Kernel-packages] [Bug 1729573] Re: netplan breaks Xen VIF driver

[Dan Streetman]

xenial build 32~16.04.1 failed for all archs; looks like a typo in one
of the python test cases.

https://launchpad.net/ubuntu/+source/nplan/0.32~16.04.1

https://launchpadlibrarian.net/346856943/buildlog_ubuntu-xenial-
amd64.nplan_0.32~16.04.1_BUILDING.txt.gz

/usr/bin/pyflakes3 src/netplan  tests/generate.py tests/cli.py 
tests/integration.py
tests/integration.py:1030:46: invalid syntax
if (self.backend == "NetworkManager")
 ^
Makefile:24: recipe for target 'check' failed
make[1]: *** [check] Error 1
make[1]: Leaving directory '/<>'
dh_auto_test: make -j1 check returned exit code 2
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2


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

** Tags removed: verification-needed
** Tags added: verification-failed

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

Title:
  netplan breaks Xen VIF driver

Status in linux package in Ubuntu:
  Won't Fix
Status in nplan package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in nplan source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Won't Fix
Status in nplan source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Won't Fix
Status in nplan source package in Artful:
  In Progress
Status in linux source package in Bionic:
  Won't Fix
Status in nplan source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  Some network interfaces on a Xen guest are broken by new behavior
  introduced by netplan.  On a Xen guest instance, when netplan is run
  to 'apply' its configuration, under certain circumstances netplan will
  try to "reset" the interface by unbinding and then re-binding the
  interface driver from the interface, by using the sysfs "bind" and
  "unbind" functions of the driver.  Normally, this results in the
  interface being released and then fully re-initialized by the driver.

  However the Xen VIF driver breaks when this is done.  The internal Xen
  backend state of the interface remains in 'closed' state after the
  driver re-connects to the interface, and attempts to open and use the
  interface result in a kernel Oops in the Xen VIF driver.

  To users, it appears that the interface is unusable because it has an
  all 0 mac address; but if the mac is manually set and the interface
  brought up the driver Oopses as mentioned above.

  This problem makes booting painful because of very long timeouts
  waiting for all network interfaces to start, and affected Xen VIF
  interfaces will of course never complete startup.

  [Fix]

  No fix yet.  Upstream kernel does not appear fixed.

  [Test Case]

  Create a guest instance under a Xen hypervisor (e.g. an AWS instance)
  that has Ubuntu Artful 17.10 installed.  Use only a single interface
  at first when creating it.  Then once it is ready, attach a second
  network interface to the instance.  From inside the instance,
  configure the new interface in netplan (i.e. add a /etc/netplan/
  config for it).  Make sure the new interface is down (netplan does not
  appear to unbind/bind interfaces that are up), and then run:

  $ sudo netplan apply

  or for debug,

  $ sudo netplan --debug apply

  this will unbind and re-bind the second interface, which will then
  have all-0 mac, and will be unusable, as described above.

  [Regression Potential]

  Changes to the Xen VIF driver can result in unusable network
  interfaces, or problems while using Xen VIF interfaces.

  [Other Info]

  Problem appears to exist upstream also.

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

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

[Kernel-packages] [Bug 1698700] Re: hibmc driver does not include "pci:" prefix in bus ID

[dann frazier]

Reopening for bionic/artful, as it is reported to have regressed post-
zesty.

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

Title:
  hibmc driver does not include "pci:" prefix in bus ID

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

Bug description:
  SRU Justification

  [Impact]
  On the HiSilicon D05 (arm64) board, X crashes when started. [0]

  [Fix]
  The crash is attributable to the bus ID that the hibmc driver reports for the 
hibmc graphics card on the board. In particular, the bus id is missing the 
"pci:" prefix that most other cards provide: [1]
  - The busid reported on the arm64 system is "0007:a1:00.0"
  - The busid reported on a amd64 system is "pci::00:02.0"

  X tests for this prefix. A missing prefix for PCI cards leads to an
  Xorg crash.

  Fix this by using the set_pci_busid function from the DRM core.

  [Testcase]
  Successfully tested on a D05 board. [2]

  [Regression Potential]
  Changes are limited to the hibmc driver, so any regression should also be 
limited to that driver.

  [Notes]
  I submitted the patch upstream. However, upstream is refactoring the drm 
core, and set_busid is going away. That does fix this issue but the regression 
potential of the refactor is enormous, so this seems like the wiser approach. 
[3]

  [0]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991
  [1]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/16
  [2]: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/comments/29
  [3]: https://www.spinics.net/lists/dri-devel/msg143831.html

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

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

[Kernel-packages] [Bug 1729573] Re: netplan breaks Xen VIF driver

[Dan Streetman]

Zesty:

ubuntu@ip-172-31-53-199:~$ dpkg -l | grep nplan
ii  nplan  0.23~17.04.1 
 amd64YAML network configuration abstraction for various 
backends
ubuntu@ip-172-31-53-199:~$ ip l show eth1
4: eth1:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
link/ether 12:f6:8a:ee:fc:96 brd ff:ff:ff:ff:ff:ff
ubuntu@ip-172-31-53-199:~$ sudo netplan --debug apply
** (generate:1349): DEBUG: Processing input file 
//etc/netplan/10-ifupdown.yaml..
** (generate:1349): DEBUG: starting new processing pass
** (generate:1349): DEBUG: eth0: setting default backend to 1
** (generate:1349): DEBUG: Generating output files..
** (generate:1349): DEBUG: NetworkManager: definition eth0 is not for us 
(backend 1)
DEBUG:netplan generated networkd configuration exists, restarting networkd
DEBUG:no netplan generated NM configuration exists
DEBUG:device eth0 operstate is up, not replugging
DEBUG:netplan triggering .link rules for eth0
DEBUG:device lo operstate is unknown, not replugging
DEBUG:netplan triggering .link rules for lo
DEBUG:replug eth1: unbinding vif-2 from /sys/bus/xen/drivers/vif
DEBUG:replug eth1: rebinding vif-2 to /sys/bus/xen/drivers/vif
ubuntu@ip-172-31-53-199:~$ ip l show eth1
5: eth1:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff


ubuntu@ip-172-31-53-199:~$ dpkg -l | grep nplan
ii  nplan  0.32~17.04.1 
 amd64YAML network configuration abstraction for various 
backends
ubuntu@ip-172-31-53-199:~$ ip l show eth1
3: eth1:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
link/ether 12:f6:8a:ee:fc:96 brd ff:ff:ff:ff:ff:ff
ubuntu@ip-172-31-53-199:~$ sudo netplan --debug apply
** (generate:1282): DEBUG: Processing input file 
//etc/netplan/10-ifupdown.yaml..
** (generate:1282): DEBUG: starting new processing pass
** (generate:1282): DEBUG: eth0: setting default backend to 1
** (generate:1282): DEBUG: Generating output files..
** (generate:1282): DEBUG: NetworkManager: definition eth0 is not for us 
(backend 1)
DEBUG:netplan generated networkd configuration exists, restarting networkd
DEBUG:no netplan generated NM configuration exists
DEBUG:replug eth1: xen:vif fails on rebinding, ignoring
DEBUG:netplan triggering .link rules for eth1
DEBUG:device lo operstate is unknown, not replugging
DEBUG:netplan triggering .link rules for lo
DEBUG:device eth0 operstate is up, not replugging
DEBUG:netplan triggering .link rules for eth0
ubuntu@ip-172-31-53-199:~$ ip l show eth1
3: eth1:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
link/ether 12:f6:8a:ee:fc:96 brd ff:ff:ff:ff:ff:ff

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

Title:
  netplan breaks Xen VIF driver

Status in linux package in Ubuntu:
  Won't Fix
Status in nplan package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in nplan source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Won't Fix
Status in nplan source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Won't Fix
Status in nplan source package in Artful:
  In Progress
Status in linux source package in Bionic:
  Won't Fix
Status in nplan source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  Some network interfaces on a Xen guest are broken by new behavior
  introduced by netplan.  On a Xen guest instance, when netplan is run
  to 'apply' its configuration, under certain circumstances netplan will
  try to "reset" the interface by unbinding and then re-binding the
  interface driver from the interface, by using the sysfs "bind" and
  "unbind" functions of the driver.  Normally, this results in the
  interface being released and then fully re-initialized by the driver.

  However the Xen VIF driver breaks when this is done.  The internal Xen
  backend state of the interface remains in 'closed' state after the
  driver re-connects to the interface, and attempts to open and use the
  interface result in a kernel Oops in the Xen VIF driver.

  To users, it appears that the interface is unusable because it has an
  all 0 mac address; but if the mac is manually set and the interface
  brought up the driver Oopses as mentioned above.

  This problem makes booting painful because of very long timeouts
  waiting for all network interfaces to start, and affected Xen VIF
  interfaces will of course never complete startup.

  [Fix]

  No fix yet.  Upstream kernel does not appear fixed.

  [Test Case]

  Create a guest instance under a Xen hypervisor (e.g. an AWS instance)
  that has Ubuntu Artful 17.10 installed.  Use 

[Kernel-packages] [Bug 1734733] Re: linux: 3.13.0-136.185 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1734734
  derivatives:
+ kernel-stable-phase-changed:Tuesday, 28. November 2017 16:01 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1734734
  derivatives:
  kernel-stable-phase-changed:Tuesday, 28. November 2017 16:01 UTC
  kernel-stable-phase:Uploaded
+ 
+ -- swm properties --
+ phase: Uploaded

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

Title:
  linux: 3.13.0-136.185 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  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:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

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

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

  backports: 1734734
  derivatives:
  kernel-stable-phase-changed:Tuesday, 28. November 2017 16:01 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1729010] Re: USB hub stops working after suspend(s?)

[Joe Barnett]

I should probably test a few more suspend cycles, but so far on
4.12.0-11-generic I'm not seeing the 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/1729010

Title:
  USB hub stops working after suspend(s?)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On initial boot, my usb hub works fine, but after a (series of?)
  suspends, I stop being able to see devices that are plugged into it.
  journalctl output on plugging it in:

  Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 
using xhci_hcd
  Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, 
idProduct=005a
  Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, 
Product=0, SerialNumber=0
  Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found
  Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected
  Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= 
SRC=fe80::::a299:9bff:fe17:9047 
DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 
FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 
using xhci_hcd
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, idVendor=0b95, 
idProduct=772a
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, 
Product=2, SerialNumber=3
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp.
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2
  Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at 
usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.0438] 
manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/7)
  Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: 
"/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1"
  Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP 
device
  Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is 
unset or enabled, the speed and duplex are not writable.
  Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from 
eth0
  Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session 
opened for user root by (uid=1000)
  Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] 
[TTY=unknown] [CWD=/home/jbarnett] 
[COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 
31]
  Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another 
user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] 
[COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 
48]
  Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error 
executing command as another user: Not authorized
  Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This 
incident has been reported.
  Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to enx0050b647ede2
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1066] device 
(eth0): interface index 10 renamed iface from 'eth0' to 'enx0050b647ede2'
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1214] 
devices added (path: 
/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2,
 iface: enx0050b647ede2)
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1214] device 
added (path: 
/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2,
 iface: enx0050b647ede2): no ifupdown configuration found.
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1217] device 
(enx0050b647ede2): state change: unmanaged -> unavailable (reason 'managed', 
internal state 'external')
  Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: 
link is not ready
  Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: 
link is not ready
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1274] 
keyfile: add connection in-memory (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired 
connection 4")
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1284] 
settings: (enx0050b647ede2): created default wired connection 'Wired connection 
4'
  Oct 31 07:08:37 spiny systemd[1]: Starting 
systemd-resolved-update-resolvconf.service...
  Oct 31 07:08:37 spiny systemd[1]: Started 
systemd-resolved-update-resolvconf.service.
  Oct 31 07:08:37 spiny kernel: usb 1-1.2: new full-speed USB device number 23 
using xhci_hcd
  Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device found, idVendor=0d8c, 
idProduct=0105
  Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device strings: Mfr=3, 
Product=1, 

[Kernel-packages] [Bug 1720228] Re: User reports excessive ALUA retry messages

[Launchpad Bug Tracker]

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

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

Title:
  User reports excessive ALUA retry messages

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

Bug description:
   SRU Justification:

  Impact:
  User reports excessive ALUA messages on Ubuntu Trusty, kernel 
Ubuntu-lts-4.4.0-91.114_14.04.1
  Messages appear after a LUN disappears and there are hundreds of them 
flooding the log...

  [263095.795873] sd 3:0:0:129: alua: rtpg retry
  [263095.795874] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.795876] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported

  This causes an intense requeing of the ALUA work queue for 60 seconds
  and it floods the kernel log

  
  Fix:
  UBUNTU: scsi: fixe excessive ALUA (LP: #1720228)
  
  BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720228

  The err value was initialized to 0 to prevent random assignemtn
  the fix is a cherry-pick from linus tree 
a4bd85203190990ad808abbd4a5dc848a950002c

  
  Testcase:
  User reports issue when a network iscsi disk gets disconnected.

  
  Original Bug Text:

  User reports excessive ALUA messages on Ubuntu Trusty, kernel Ubuntu-
  lts-4.4.0-91.114_14.04.1

  Messages appear after a LUN disappears and there are hundreds of them
  flooding the log...

  [263095.795873] sd 3:0:0:129: alua: rtpg retry
  [263095.795874] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.795876] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.795961] sd 3:0:0:129: alua: rtpg retry
  [263095.795962] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.795964] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796049] sd 3:0:0:129: alua: rtpg retry
  [263095.796052] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796054] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796140] sd 3:0:0:129: alua: rtpg retry
  [263095.796142] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796143] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796224] sd 3:0:0:129: alua: rtpg retry
  [263095.796226] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796227] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796473] sd 3:0:0:129: alua: rtpg retry
  [263095.796475] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796476] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796604] sd 3:0:0:129: alua: rtpg retry
  [263095.796606] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796607] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796691] sd 3:0:0:129: alua: rtpg retry
  [263095.796693] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796694] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796778] sd 3:0:0:129: alua: rtpg retry
  [263095.796780] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796781] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796868] sd 3:0:0:129: alua: rtpg retry
  [263095.796869] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796871] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.796951] sd 3:0:0:129: alua: rtpg retry
  [263095.796953] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.796954] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797034] sd 3:0:0:129: alua: rtpg retry
  [263095.797035] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797037] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797117] sd 3:0:0:129: alua: rtpg retry
  [263095.797119] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797120] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797202] sd 3:0:0:129: alua: rtpg retry
  [263095.797203] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797205] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797288] sd 3:0:0:129: alua: rtpg retry
  [263095.797289] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797290] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797387] sd 3:0:0:129: alua: rtpg retry
  [263095.797388] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current]
  [263095.797390] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported
  [263095.797470] sd 3:0:0:129: alua: rtpg retry
  [263095.797471] sd 3:0:0:129: [alua] Sense Key : Illegal 

[Kernel-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

[Kleber Sacilotto de Souza]

It turns out that the commit mentioned on the previous comment is
necessary but not sufficient to fix the issue. The testcase also needs
to be fixed.

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

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

Bug description:
  ppc64el ADT log:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
Building modules, stage 2.
MODPOST 1 modules
CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

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

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

[Kernel-packages] [Bug 1734901] Re: linux: 4.14.0-10.12 -proposed tracker

[Brad Figg]

** Changed in: kernel-development-workflow/prepare-package
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.14.0-10.12 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ kernel-phase-changed:Tuesday, 28. November 2017 15:01 UTC
+ kernel-phase:Packaging

** Description changed:

  This bug is for tracking the 4.14.0-10.12 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  kernel-phase-changed:Tuesday, 28. November 2017 15:01 UTC
  kernel-phase:Packaging
+ 
+ -- swm properties --
+ phase: Packaging

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

Title:
  linux: 4.14.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 28. November 2017 15:01 UTC
  kernel-phase:Packaging

  -- swm properties --
  phase: Packaging

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

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

[Kernel-packages] [Bug 1734695] Re: linux: 4.14.0-8.10 -proposed tracker

[Seth Forshee]

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

** This bug is no longer a duplicate of bug 1734728
   linux: 4.14.0-9.11 -proposed tracker
** This bug has been marked a duplicate of bug 1734901
   linux: 4.14.0-10.12 -proposed tracker

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

Title:
  linux: 4.14.0-8.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.14.0-8.10 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

  kernel-phase:Packaging
  kernel-phase-changed:Monday, 27. November 2017 14:00 UTC

  -- swm properties --
  phase: Packaging

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

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

[Kernel-packages] [Bug 1734728] Re: linux: 4.14.0-9.11 -proposed tracker

[Seth Forshee]

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

** This bug has been marked a duplicate of bug 1734901
   linux: 4.14.0-10.12 -proposed tracker

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

Title:
  linux: 4.14.0-9.11 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.14.0-9.11 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

  kernel-phase:Packaging
  kernel-phase-changed:Monday, 27. November 2017 18:00 UTC

  -- swm properties --
  phase: Packaging

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

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

[Kernel-packages] [Bug 1734901] [NEW] linux: 4.14.0-10.12 -proposed tracker

[Seth Forshee]

Public bug reported:

This bug is for tracking the 4.14.0-10.12 upload package. This bug will
contain status and testing results related to that upload.

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

** Affects: kernel-development-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-development-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-development-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live

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

** Tags added: kernel-release-tracking-bug-live

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

** Tags added: bionic

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

** Also affects: kernel-development-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/regression-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-development-workflow
   Status: New => In Progress

** Changed in: kernel-development-workflow
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: kernel-development-workflow/regression-testing
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/regression-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

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

Title:
  linux: 4.14.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status 

[Kernel-packages] [Bug 1734744] Re: OOM killer with kernel 4.4.0-92

[Willem]

I cannot run apport-collect 1734744 right now, so manually changed to confirmed.
Hopefully the attached logs will help

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

Title:
  OOM killer with kernel 4.4.0-92

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When putting pressure on a Linux Node in Azure we see OOM killers (similar 
to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842 but not this 
is a different kernel)
  Reverting the kernel to 4.4.0-57 fixes the problem.

  dmesg and kernel.log attached

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

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

[Kernel-packages] [Bug 1734084] Re: Kernel Update Causes HDMI Port to Stop Working

[Niall Newman]

I tested with the latest upstream v4.14 kernels and the issue appears to
be fixed.

Kind regards,
Niall

** Tags added: kernel-fixed-upstream

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

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

Title:
  Kernel Update Causes HDMI Port to Stop Working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading the kernel on my Ubuntu 17.04 laptop from 
linux-image-4.13.0-16-generic to linux-image-4.13.0-17-generic the HDMI port 
was no longer recognised by the system causing the external display to stop 
working.
  Reverting the kernel to linux-image-4.13.0-16-generic fixes the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-17-generic (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  linus  2762 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 23 09:17:32 2017
  HibernationDevice: RESUME=UUID=864b1d5d-3e65-4d95-b439-941a5825c74f
  InstallationDate: Installed on 2017-10-18 (35 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Dell Inc. Latitude E7470
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/02/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.16.4
  dmi.board.name: 0T6HHJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.4:bd06/02/2017:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude E7470
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1734734] Re: linux-lts-trusty: 3.13.0-136.185~precise1 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1734733
  phase: Uploaded

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

Title:
  linux-lts-trusty: 3.13.0-136.185~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  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:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1734733
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1734038] Re: utils don't understand «include "/where/ever"» (was: Potential regression found with apparmor test on Xenial/Zesty)

[Michael Vogt]

We merged https://github.com/snapcore/snapd/pull/4306 which fixes this.

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

Title:
  utils don't understand «include "/where/ever"» (was: Potential
  regression found with apparmor test on Xenial/Zesty)

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Invalid

Bug description:
  Issue found with Xenial kernel 4.4.0-102 and Zesty kernel 4.10.0-41,
  across different architectures

  Multiple tests from ubuntu_qrt_apparmor test suite failed with the same error 
message:
  ERROR: Syntax Error: Unknown line found in file 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real line 15:
  include "/var/lib/snapd/apparmor/snap-confine.d" /etc/ld.so.cache r,

  (BTW the include and this ld.so.cache are not in the same line, please
  refer to comment #3 for attachment)

  This issue will gone if you downgrade the snapd and ubuntu-core-launcher 
package:
  sudo apt-get install snapd=2.28.5 ubuntu-core-launcher=2.28.5

  Debug information:
  ubuntu@kernel01:~$ snap version
  snap2.29.3
  snapd   2.29.3
  series  16
  ubuntu  16.04
  kernel  4.4.0-102-generic

  ubuntu@kernel01:~$ apt list snapd
  Listing... Done
  snapd/xenial-proposed,now 2.29.3 s390x [installed]
  N: There are 2 additional versions. Please use the '-a' switch to see them.

  ubuntu@kernel01:~$ apt list apparmor -a
  Listing... Done
  apparmor/xenial-updates,now 2.10.95-0ubuntu2.7 s390x [installed]
  apparmor/xenial-security 2.10.95-0ubuntu2.6 s390x
  apparmor/xenial 2.10.95-0ubuntu2 s390x

  Steps to run the Apparmor test from QA Regression testing suite:
1. git clone --depth 1 https://git.launchpad.net/qa-regression-testing
2. sudo ./qa-regression-testing/scripts/test-apparmor.py

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-102-generic 4.4.0-102.125
  ProcVersionSignature: Ubuntu 4.4.0-102.125-generic 4.4.98
  Uname: Linux 4.4.0-102-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:

  Date: Thu Nov 23 01:36:31 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-102-generic N/A
   linux-backports-modules-4.4.0-102-generic  N/A
   linux-firmware 1.157.13
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1708409] Re: kdump service does not start after configure/reboot

[Dimitri John Ledkov]

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

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

** Also affects: makedumpfile (Ubuntu Bionic)
   Importance: Undecided
 Assignee: Canonical Foundations Team (canonical-foundations)
   Status: Confirmed

** Also affects: systemd (Ubuntu Bionic)
   Importance: High
 Assignee: Canonical Foundations Team (canonical-foundations)
   Status: Triaged

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

Title:
  kdump service does not start after configure/reboot

Status in The Ubuntu-power-systems project:
  Triaged
Status in makedumpfile package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Triaged
Status in makedumpfile source package in Artful:
  New
Status in systemd source package in Artful:
  New
Status in makedumpfile source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Triaged

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

  ...
  https://github.com/systemd/systemd/issues/6334

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

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

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

[Kernel-packages] [Bug 1728762] Re: Update iwlwifi firmware for 3160, 3168, 7260, 7265 and 7265D

[Andy Whitcroft]

Hello quanxian, or anyone else affected,

Accepted linux-firmware into trusty-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.127.24 in a few hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  Update iwlwifi firmware for 3160, 3168, 7260, 7265 and 7265D

Status in intel:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Trusty:
  Fix Committed
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Zesty:
  Fix Committed
Status in linux-firmware source package in Artful:
  Fix Committed
Status in linux-firmware source package in Bionic:
  Fix Released

Bug description:
  SRU Justification

  Impact: Intel wireless firmware WoWLAN functionality is vulnerable to
  some CVEs from the KRACK attack vulnerabilities, CVE-2017-13080 and
  CVE-2017-13081.

  Fix: Updated firmware from Intel containing fixes for these
  vulnerabilities.

  Test Case: Difficult to test; we are reliant on testing done by Intel.

  Regression Potential: There is always some possibility for regressions
  with firmware updates, but as these are bug fix updates the regression
  potential is minimal. I have been using the 7260 firmware for over a
  week now without issue.

  ---

  There are two parts of WIFI firmware update. Please double check if
  Ubuntu release has include them.

  A new firmware version for 8260 and 8265 WiFi devices.
  This our Core31 release (-34.ucode).
  
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=348d2b53326bcef4c260037cc7a6006fc80ca5bb

  A new firmware version  for 3160, 3168, 7260, 7265 and 7265D
  Note: This firmware version hasn't been pulled into mainline yet.
  This includes a security fix.
  The patch in iwlwifi/linux-firmware.git is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=11e310f97470f91e26e6f3408b09871fd6cd3c5c

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

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

[Kernel-packages] [Bug 1641049] Re: NFSv4 do not invalidate cached information about deleted files

[Petr gregor]

This problem seems very similar
https://bugzilla.redhat.com/show_bug.cgi?id=1416532

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

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

Title:
  NFSv4 do not invalidate cached information about deleted files

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When using NFSv4 client in Ubuntu 16.04 the the following sequence of
  actions fails.

  You need a NFS server (S) and two clients (A and B).

  Let the NFS share be mounted at /nfsdata

  A: echo test > /nfsdata/file
  B: cat /nfsdata/file ===> test
  A: rm /nfsdata/file
  B: cat /nfsdata/file ===> cat: No such file or directory
  A: echo test > /nfsdata/file
  B: cat /nfsdata/file ===> cat: No such file or directory (!)

  Doing echo 3 > proc/sys/vm/drop_caches as root makes the file visible
  on B.

  14.04 works without any problem.

  I have attached log from one of our servers, 4.4.0-47 kernel does not fix 
this issue. 
  Syslog contains rpcdebug -m nfs -s all output for the scenario (with 
different filenames).
  I can do full packet capture of NFS traffic if you want.
  Mounting nfs with lookupcache=positive do not fix this issue.

  NFSv4 server is CentOS 6.7 in our case.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-45-generic 4.4.0-45.66
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  8 03:13 seq
   crw-rw 1 root audio 116, 33 Nov  8 03:13 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  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: Fri Nov 11 17:06:51 2016
  HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1
  InstallationDate: Installed on 2016-11-07 (3 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp.
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R630
  PciMultimedia:

  ProcEnviron:
   LC_CTYPE=en_US.UTF-8
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=11e697e5-38f8-41ae-863c-2755793044a6 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.0.1
  dmi.board.name: 02C2CP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.0.1:bd02/12/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA01:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R630
  dmi.sys.vendor: Dell Inc.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  8 03:13 seq
   crw-rw 1 root audio 116, 33 Nov  8 03:13 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1
  InstallationDate: Installed on 2016-11-07 (3 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R630
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LC_CTYPE=en_US.UTF-8
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  

[Kernel-packages] [Bug 1728762] Re: Update iwlwifi firmware for 3160, 3168, 7260, 7265 and 7265D

[Seth Forshee]

** Description changed:

+ SRU Justification
+ 
+ Impact: Intel wireless firmware WoWLAN functionality is vulnerable to
+ some CVEs from the KRACK attack vulnerabilities, CVE-2017-13080 and
+ CVE-2017-13081.
+ 
+ Fix: Updated firmware from Intel containing fixes for these
+ vulnerabilities.
+ 
+ Test Case: Difficult to test; we are reliant on testing done by Intel.
+ 
+ Regression Potential: There is always some possibility for regressions
+ with firmware updates, but as these are bug fix updates the regression
+ potential is minimal. I have been using the 7260 firmware for over a
+ week now without issue.
+ 
+ ---
+ 
  There are two parts of WIFI firmware update. Please double check if
  Ubuntu release has include them.
  
  A new firmware version for 8260 and 8265 WiFi devices.
  This our Core31 release (-34.ucode).
  
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=348d2b53326bcef4c260037cc7a6006fc80ca5bb
  
- 
  A new firmware version  for 3160, 3168, 7260, 7265 and 7265D
  Note: This firmware version hasn't been pulled into mainline yet.
  This includes a security fix.
  The patch in iwlwifi/linux-firmware.git is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=11e310f97470f91e26e6f3408b09871fd6cd3c5c

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

Title:
  Update iwlwifi firmware for 3160, 3168, 7260, 7265 and 7265D

Status in intel:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Trusty:
  In Progress
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Zesty:
  Fix Committed
Status in linux-firmware source package in Artful:
  Fix Committed
Status in linux-firmware source package in Bionic:
  Fix Released

Bug description:
  SRU Justification

  Impact: Intel wireless firmware WoWLAN functionality is vulnerable to
  some CVEs from the KRACK attack vulnerabilities, CVE-2017-13080 and
  CVE-2017-13081.

  Fix: Updated firmware from Intel containing fixes for these
  vulnerabilities.

  Test Case: Difficult to test; we are reliant on testing done by Intel.

  Regression Potential: There is always some possibility for regressions
  with firmware updates, but as these are bug fix updates the regression
  potential is minimal. I have been using the 7260 firmware for over a
  week now without issue.

  ---

  There are two parts of WIFI firmware update. Please double check if
  Ubuntu release has include them.

  A new firmware version for 8260 and 8265 WiFi devices.
  This our Core31 release (-34.ucode).
  
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=348d2b53326bcef4c260037cc7a6006fc80ca5bb

  A new firmware version  for 3160, 3168, 7260, 7265 and 7265D
  Note: This firmware version hasn't been pulled into mainline yet.
  This includes a security fix.
  The patch in iwlwifi/linux-firmware.git is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=11e310f97470f91e26e6f3408b09871fd6cd3c5c

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

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

[Kernel-packages] [Bug 1734874] Re: I updated it froze and I restarted still cant see low latency kernels after updating grubpackage linux-signed-image-4.13.0-17-generic 4.13.0-17.20 failed to install

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  I updated it froze and I restarted still cant see low latency kernels
  after updating grubpackage linux-signed-image-4.13.0-17-generic
  4.13.0-17.20 failed to install/upgrade: subprocess installed post-
  installation script returned error exit status 1

Status in linux-signed package in Ubuntu:
  New

Bug description:
  update and it crashed

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-signed-image-4.13.0-17-generic 4.13.0-17.20
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  Date: Tue Nov 28 03:17:52 2017
  DuplicateSignature:
   package:linux-signed-image-4.13.0-17-generic:4.13.0-17.20
   Setting up linux-signed-image-4.13.0-17-generic (4.13.0-17.20) ...
   cp: cannot stat '/boot/vmlinuz-4.13.0-17-generic': No such file or directory
   dpkg: error processing package linux-signed-image-4.13.0-17-generic 
(--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-11-22 (5 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: linux-signed
  Title: package linux-signed-image-4.13.0-17-generic 4.13.0-17.20 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to artful on 2017-11-23 (5 days ago)

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

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

[Kernel-packages] [Bug 1734874] [NEW] I updated it froze and I restarted still cant see low latency kernels after updating grubpackage linux-signed-image-4.13.0-17-generic 4.13.0-17.20 failed to insta

[mbele3000]

Public bug reported:

update and it crashed

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: linux-signed-image-4.13.0-17-generic 4.13.0-17.20
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
Date: Tue Nov 28 03:17:52 2017
DuplicateSignature:
 package:linux-signed-image-4.13.0-17-generic:4.13.0-17.20
 Setting up linux-signed-image-4.13.0-17-generic (4.13.0-17.20) ...
 cp: cannot stat '/boot/vmlinuz-4.13.0-17-generic': No such file or directory
 dpkg: error processing package linux-signed-image-4.13.0-17-generic 
(--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-11-22 (5 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: linux-signed
Title: package linux-signed-image-4.13.0-17-generic 4.13.0-17.20 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: Upgraded to artful on 2017-11-23 (5 days ago)

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


** Tags: amd64 apport-package artful

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

Title:
  I updated it froze and I restarted still cant see low latency kernels
  after updating grubpackage linux-signed-image-4.13.0-17-generic
  4.13.0-17.20 failed to install/upgrade: subprocess installed post-
  installation script returned error exit status 1

Status in linux-signed package in Ubuntu:
  New

Bug description:
  update and it crashed

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-signed-image-4.13.0-17-generic 4.13.0-17.20
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  Date: Tue Nov 28 03:17:52 2017
  DuplicateSignature:
   package:linux-signed-image-4.13.0-17-generic:4.13.0-17.20
   Setting up linux-signed-image-4.13.0-17-generic (4.13.0-17.20) ...
   cp: cannot stat '/boot/vmlinuz-4.13.0-17-generic': No such file or directory
   dpkg: error processing package linux-signed-image-4.13.0-17-generic 
(--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-11-22 (5 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: linux-signed
  Title: package linux-signed-image-4.13.0-17-generic 4.13.0-17.20 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to artful on 2017-11-23 (5 days ago)

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

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

[Kernel-packages] [Bug 1730374] Re: NULL pointer dereference during writeback

[Metta Crawler]

Installation of 4.14.2
https://gist.github.com/mettacrawler/7d60c8f51a19b506ea1cb575c2ed4032

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

Title:
  NULL pointer dereference during writeback

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Happened during dd of 40GB LV:

  $ sudo dd if=/dev/vg0/gentoo of=/dev/vg1/gentoo

  I also used SIGUSR1 on the dd to monitor it occasionally.  There was
  other activity at the time as well.

  It appears that an attempt was made to fix this in 4.10
  https://patchwork.kernel.org/patch/9614353/
  but it is still happening in 4.13

  Nov 06 04:19:13 lakshmi kernel: BUG: unable to handle kernel NULL pointer 
dereference at   (null)
  Nov 06 04:19:13 lakshmi kernel: IP: 
locked_inode_to_wb_and_lock_list+0x26/0x110
  Nov 06 04:19:13 lakshmi kernel: PGD 0
  Nov 06 04:19:14 lakshmi kernel: P4D 0
  Nov 06 04:19:14 lakshmi kernel:
  Nov 06 04:19:14 lakshmi kernel: Oops:  [#1] SMP
  Nov 06 04:19:14 lakshmi kernel: Modules linked in: xt_CHECKSUM iptable_mangle 
ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_
  Nov 06 04:19:14 lakshmi kernel:  async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid0 multipath linear raid1 hid_g
  Nov 06 04:19:14 lakshmi kernel: CPU: 0 PID: 67 Comm: kswapd0 Not tainted 
4.13.0-16-generic #19-Ubuntu
  Nov 06 04:19:14 lakshmi kernel: Hardware name: System manufacturer System 
Product Name/M4A89GTD-PRO/USB3, BIOS 302907/05/2012
  Nov 06 04:19:14 lakshmi kernel: task: 93db5adc8000 task.stack: 
b03b01d94000
  Nov 06 04:19:14 lakshmi kernel: RIP: 
0010:locked_inode_to_wb_and_lock_list+0x26/0x110
  Nov 06 04:19:14 lakshmi kernel: RSP: 0018:b03b01d97bc8 EFLAGS: 00010292
  Nov 06 04:19:14 lakshmi kernel: RAX:  RBX:  
RCX: 93d9758dfe28
  Nov 06 04:19:14 lakshmi kernel: RDX: 0001 RSI: 05080020 
RDI: 93d9758dea58
  Nov 06 04:19:14 lakshmi kernel: RBP: b03b01d97bf0 R08:  
R09: 93d9cd655468
  Nov 06 04:19:14 lakshmi kernel: R10: 0228 R11:  
R12: 93d9758dea58
  Nov 06 04:19:14 lakshmi kernel: R13: 93d9758deae0 R14:  
R15: 0059
  Nov 06 04:19:14 lakshmi kernel: FS:  () 
GS:93db77c0() knlGS:
  Nov 06 04:19:14 lakshmi kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Nov 06 04:19:14 lakshmi kernel: CR2:  CR3: 0001d7e08000 
CR4: 06f0
  Nov 06 04:19:14 lakshmi kernel: Call Trace:
  Nov 06 04:19:14 lakshmi kernel:  inode_io_list_del+0x23/0x50
  Nov 06 04:19:14 lakshmi kernel:  evict+0x55/0x1a0
  Nov 06 04:19:14 lakshmi kernel:  dispose_list+0x39/0x50
  Nov 06 04:19:14 lakshmi kernel:  prune_icache_sb+0x5a/0x80
  Nov 06 04:19:14 lakshmi kernel:  super_cache_scan+0x134/0x1b0
  Nov 06 04:19:14 lakshmi kernel:  shrink_slab.part.48+0x1d6/0x3d0
  Nov 06 04:19:14 lakshmi kernel:  shrink_slab+0x1b/0x30
  Nov 06 04:19:14 lakshmi kernel:  shrink_node+0x11e/0x300
  Nov 06 04:19:14 lakshmi kernel:  kswapd+0x2cc/0x750
  Nov 06 04:19:14 lakshmi kernel:  kthread+0x125/0x140
  Nov 06 04:19:14 lakshmi kernel:  ? mem_cgroup_shrink_node+0x180/0x180
  Nov 06 04:19:14 lakshmi kernel:  ? kthread_create_on_node+0x70/0x70
  Nov 06 04:19:14 lakshmi kernel:  ret_from_fork+0x25/0x30
  Nov 06 04:19:14 lakshmi kernel: Code: 00 00 00 00 00 0f 1f 44 00 00 55 48 89 
e5 41 56 41 55 41 54 53 4c 8d af 88 00 00 00 49 89 fc
  Nov 06 04:19:14 lakshmi kernel: RIP: 
locked_inode_to_wb_and_lock_list+0x26/0x110 RSP: b03b01d97bc8
  Nov 06 04:19:14 lakshmi kernel: CR2: 
  Nov 06 04:19:14 lakshmi kernel: ---[ end trace 5aa11bcf674e53cc ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ksta   3322 F pulseaudio
   /dev/snd/controlC0:  ksta   3322 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  6 06:59:50 2017
  HibernationDevice: RESUME=/dev/mapper/vg1-swap
  InstallationDate: Installed on 2017-11-05 (0 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/vg1-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  

[Kernel-packages] [Bug 1730374] Re: NULL pointer dereference during writeback

[Metta Crawler]

I was unable to reproduce this on 4.13 until Nov 23 when it happened
again.

This time the logs show that I was handling PDF files via Nautilus which
doesn't imply as much disk I/O as the previous 40G dd did.

A quote from:
https://patchwork.kernel.org/patch/9614361/
{{ I am able to reproduce the problem by adding articial [artificial] delays in
__blkdev_put() and writeback_sb_inodes(). Please see the repro patch
below: }}

Nov 23 06:20:38 lakshmi kernel: BUG: unable to handle kernel NULL pointer 
dereference at   (null)
Nov 23 06:20:38 lakshmi kernel: IP: locked_inode_to_wb_and_lock_list+0x26/0x110
Nov 23 06:20:38 lakshmi kernel: PGD 0 
Nov 23 06:20:39 lakshmi kernel: P4D 0 
Nov 23 06:20:39 lakshmi kernel: 
Nov 23 06:20:39 lakshmi kernel: Oops:  [#1] SMP
Nov 23 06:20:39 lakshmi kernel: Modules linked in: ufs qnx4 hfsplus hfs minix 
ntfs msdos jfs vhost_net vhost tap uas usb_storage xt_C
Nov 23 06:20:39 lakshmi kernel:  ppdev lp parport ip_tables x_tables autofs4 
xfs btrfs raid10 raid456 async_raid6_recov async_memcpy 
Nov 23 06:20:39 lakshmi kernel: CPU: 2 PID: 67 Comm: kswapd0 Not tainted 
4.13.0-16-generic #19-Ubuntu
Nov 23 06:20:39 lakshmi kernel: Hardware name: System manufacturer System 
Product Name/M4A89GTD-PRO/USB3, BIOS 302907/05/2012
Nov 23 06:20:39 lakshmi kernel: task: 99631ae28000 task.stack: 
b98741d98000
Nov 23 06:20:39 lakshmi kernel: RIP: 
0010:locked_inode_to_wb_and_lock_list+0x26/0x110
Nov 23 06:20:39 lakshmi kernel: RSP: 0018:b98741d9bbc8 EFLAGS: 00010292
Nov 23 06:20:39 lakshmi kernel: RAX:  RBX:  
RCX: 9961358ddc68
Nov 23 06:20:39 lakshmi kernel: RDX: 0001 RSI: 05080020 
RDI: 9961358dea58
Nov 23 06:20:39 lakshmi kernel: RBP: b98741d9bbf0 R08:  
R09: 99629957efc8
Nov 23 06:20:39 lakshmi kernel: R10: 0228 R11: 99629957cd90 
R12: 9961358dea58
Nov 23 06:20:39 lakshmi kernel: R13: 9961358deae0 R14:  
R15: 00e3
Nov 23 06:20:39 lakshmi kernel: FS:  () 
GS:996337c8() knlGS:
Nov 23 06:20:39 lakshmi kernel: CS:  0010 DS:  ES:  CR0: 
80050033
Nov 23 06:20:39 lakshmi kernel: CR2:  CR3: 000292009000 
CR4: 06e0
Nov 23 06:20:39 lakshmi kernel: Call Trace:
Nov 23 06:20:39 lakshmi kernel:  inode_io_list_del+0x23/0x50
Nov 23 06:20:39 lakshmi kernel:  evict+0x55/0x1a0
Nov 23 06:20:39 lakshmi kernel:  dispose_list+0x39/0x50
Nov 23 06:20:39 lakshmi kernel:  prune_icache_sb+0x5a/0x80
Nov 23 06:20:39 lakshmi kernel:  super_cache_scan+0x134/0x1b0
Nov 23 06:20:39 lakshmi kernel:  shrink_slab.part.48+0x1d6/0x3d0
Nov 23 06:20:39 lakshmi kernel:  shrink_slab+0x1b/0x30
Nov 23 06:20:39 lakshmi kernel:  shrink_node+0x11e/0x300
Nov 23 06:20:39 lakshmi kernel:  kswapd+0x2cc/0x750
Nov 23 06:20:39 lakshmi kernel:  kthread+0x125/0x140
Nov 23 06:20:39 lakshmi kernel:  ? mem_cgroup_shrink_node+0x180/0x180
Nov 23 06:20:39 lakshmi kernel:  ? kthread_create_on_node+0x70/0x70
Nov 23 06:20:39 lakshmi kernel:  ret_from_fork+0x25/0x30
Nov 23 06:20:39 lakshmi kernel: Code: 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 
41 56 41 55 41 54 53 4c 8d af 88 00 00 00 49 89 fc 48
Nov 23 06:20:39 lakshmi kernel: RIP: 
locked_inode_to_wb_and_lock_list+0x26/0x110 RSP: b98741d9bbc8
Nov 23 06:20:39 lakshmi kernel: CR2: 
Nov 23 06:20:39 lakshmi kernel: ---[ end trace c0c5ab8e419a23c0 ]---

I'm going to put on 4.14.2 and see
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14.2/

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

Title:
  NULL pointer dereference during writeback

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Happened during dd of 40GB LV:

  $ sudo dd if=/dev/vg0/gentoo of=/dev/vg1/gentoo

  I also used SIGUSR1 on the dd to monitor it occasionally.  There was
  other activity at the time as well.

  It appears that an attempt was made to fix this in 4.10
  https://patchwork.kernel.org/patch/9614353/
  but it is still happening in 4.13

  Nov 06 04:19:13 lakshmi kernel: BUG: unable to handle kernel NULL pointer 
dereference at   (null)
  Nov 06 04:19:13 lakshmi kernel: IP: 
locked_inode_to_wb_and_lock_list+0x26/0x110
  Nov 06 04:19:13 lakshmi kernel: PGD 0
  Nov 06 04:19:14 lakshmi kernel: P4D 0
  Nov 06 04:19:14 lakshmi kernel:
  Nov 06 04:19:14 lakshmi kernel: Oops:  [#1] SMP
  Nov 06 04:19:14 lakshmi kernel: Modules linked in: xt_CHECKSUM iptable_mangle 
ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_
  Nov 06 04:19:14 lakshmi kernel:  async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid0 multipath linear raid1 hid_g
  Nov 06 04:19:14 lakshmi kernel: CPU: 0 PID: 67 Comm: kswapd0 Not tainted 
4.13.0-16-generic #19-Ubuntu
  Nov 06 04:19:14 lakshmi kernel: Hardware name: System