[Kernel-packages] [Bug 1698508] Re: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

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

Title:
  package linux-image-4.10.0-22-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Expired

Bug description:
  i am also getting issue with "suspend"
  when i click on suspend 
  it doest start back when i turn it on , it desnt even show a console mode 
besides a blank black screen
  i was also getting this issue in 16.04 and now in 17.04 too
  my specs
  lenovo ideapad  z50
  intel i5 4th gen 2 cores
  8gb ram
  2gb nvidia geforce 820m 
  1 tb hdd
  1080p display

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-22-generic (not installed)
  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.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mubix  1783 F pulseaudio
   /dev/snd/controlC1:  mubix  1783 F pulseaudio
  Date: Sat Jun 17 10:19:46 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-06-14 (2 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 20354
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=ed70addc-4319-4c31-9bdf-3c12bddf4af8 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2
  SourcePackage: linux
  Title: package linux-image-4.10.0-22-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANANO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoZ50-70:
  dmi.product.name: 20354
  dmi.product.version: Lenovo Z50-70
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1698472] Re: package linux-image-4.10.0-22-generic 4.10.0-22.24 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

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

Title:
  package linux-image-4.10.0-22-generic 4.10.0-22.24 failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Expired

Bug description:
  Running under Virtual Box under Windows 10

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-22-generic 4.10.0-22.24
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jim2083 F pulseaudio
  Date: Mon Jun 12 21:51:53 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-04-13 (64 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic 
root=UUID=cbb0d41e-8a7c-4cef-a662-25e5bbb78052 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.10.0-22-generic 4.10.0-22.24 failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1698561] Re: package linux-image-4.10.0-22-generic 4.10.0-22.24 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

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

Title:
  package linux-image-4.10.0-22-generic 4.10.0-22.24 failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Expired

Bug description:
  keeps popping up :-/

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-22-generic 4.10.0-22.24
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mohammad   1845 F pulseaudio
   /dev/snd/controlC1:  mohammad   1845 F pulseaudio
  Date: Sat Jun 17 14:05:10 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-06-16 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. G501JW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic 
root=UUID=a2414b49-0f72-486e-8dc7-7739e99a6937 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-image-4.10.0-22-generic 4.10.0-22.24 failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G501JW.209
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G501JW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG501JW.209:bd07/24/2015:svnASUSTeKCOMPUTERINC.:pnG501JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG501JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: G501JW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1698544] Re: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

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

Title:
  package linux-image-4.10.0-22-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Expired

Bug description:
  I was using the terminal to update the system and received the error
  message

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-22-generic (not installed)
  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.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  peeps  1525 F pulseaudio
   /dev/snd/controlC0:  peeps  1525 F pulseaudio
  Date: Sat Jun 17 14:01:02 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-06-17 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=1e517b73-cab9-445a-826b-48ab71ca1a96 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.10.0-22-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/20/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 216F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 31.22
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd11/20/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr097611405E0620180:rvnHewlett-Packard:rn216F:rvr31.22:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 097611405E0620180
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => Fix Released

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

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

Title:
  zesty unable to handle kernel NULL pointer dereference

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Fix Committed
Status in linux-hwe source package in Zesty:
  Confirmed

Bug description:
  Upgraded to zesty about a week ago. Ran into this on latest kernel.
  (during high load, nothing in particular seems to cause it to happen).

  Did not happen with previous (4.10.0.14.16) kernel. Only after update
  to 4.10.0.15.17, has happened about 3 times since then (or other
  crashes), this is the one I could capture.

  kern.log entries below. Let me know if you need anything else from me.

  Thanks!

  Apr  7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL 
pointer dereference at 0018
  Apr  7 11:20:28 doe kernel: [26003.796375] IP: 
gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  Apr  7 11:20:28 doe kernel: [26003.796404] PGD 0
  Apr  7 11:20:28 doe kernel: [26003.796405]
  Apr  7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP
  Apr  7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT 
nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat 
nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables 
ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack 
libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep 
zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 
hid_multitouch joydev i2c_designware_platform i2c_designware_core 
snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp 
snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic 
snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel 
snd_hda_codec snd_hda_core asus_nb_wmi
  Apr  7 11:20:28 doe kernel: [26003.796722]  snd_hwdep asus_wmi sparse_keymap 
snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device 
iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp 
uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops 
irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 
videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm 
elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf 
industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad 
int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi 
acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb 
int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless 
parport_pc ppdev lp parport ip_tables
  Apr  7 11:20:28 doe kernel: [26003.797026]  x_tables autofs4 algif_skcipher 
af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 
aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit 
drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm 
wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes
  Apr  7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: 
chromium-browse Tainted: P   O4.10.0-15-generic #17-Ubuntu
  Apr  7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER 
INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015
  Apr  7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: 
c25b5ea8c000
  Apr  7 11:20:28 doe kernel: [26003.797250] RIP: 
0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  Apr  7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 
00010246
  Apr  7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 
0003 RCX: 0003
  Apr  7 11:20:28 doe kernel: [26003.797325] RDX:  RSI: 
9bbae7c0a000 RDI: 9bbba0418000
  Apr  7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: 
 R09: 
  Apr  7 11:20:28 doe kernel: [26003.797378] R10:  R11: 
0041 R12: 9bbb5f00a000
  Apr  7 11:20:28 doe kernel: [26003.797405] R13: 9bbba932bb10 R14: 
fff97000 R15: 8000
  Apr  7 11:20:28 doe kernel: [26003.797440] FS:  7f70bd1df6c0() 
GS:93c0() knlGS:
  Apr  7 11:20:28 doe kernel: [26003.797470] CS:  0010 DS:  ES:  CR0: 
80050033
  Apr  7 11:20:28 doe kernel: [26003.797497] CR2: 0018 CR3: 
00016942 CR4: 003406f0
  Apr  7 11:20:28 doe kernel: 

[Kernel-packages] [Bug 1707395] Re: Synaptics touchpad does not work at all

[Sergio Gutierrez]

Output of the udevadm when booted 4.12

** Attachment added: "4.12"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707395/+attachment/4934929/+files/4.12

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

Title:
  Synaptics touchpad does not work at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My synaptics touchpad is not working because it is not being detected.
  It happens since I upgraded to Ubuntu 17.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-28-generic 4.10.0-28.32
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   saguti 8628 F...m pulseaudio
   /dev/snd/controlC1:  saguti 8628 F pulseaudio
   /dev/snd/controlC0:  saguti 8628 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Jul 29 08:25:15 2017
  HibernationDevice: RESUME=UUID=dece2035-1a42-4d1e-8304-9f2e23921132
  InstallationDate: Installed on 2016-07-24 (369 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Acer Aspire V3-472G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic.efi.signed 
root=UUID=c4a143c7-b490-423a-9645-ff2ffe57a345 ro quiet splash 
intel_pstate=disable "acp_osi=!Windows 2013" vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-28-generic N/A
   linux-backports-modules-4.10.0-28-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-07-29 (0 days ago)
  dmi.bios.date: 09/24/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA40_HB
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.21:bd09/24/2014:svnAcer:pnAspireV3-472G:pvrTBDbyOEM:rvnAcer:rnEA40_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire V3-472G
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1707395] Re: Synaptics touchpad does not work at all

[Sergio Gutierrez]

Output of the udevadm when booted 4.13-rc1

** Attachment added: "4.13-rc1"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707395/+attachment/4934928/+files/4.13-rc1

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

Title:
  Synaptics touchpad does not work at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My synaptics touchpad is not working because it is not being detected.
  It happens since I upgraded to Ubuntu 17.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-28-generic 4.10.0-28.32
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   saguti 8628 F...m pulseaudio
   /dev/snd/controlC1:  saguti 8628 F pulseaudio
   /dev/snd/controlC0:  saguti 8628 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Jul 29 08:25:15 2017
  HibernationDevice: RESUME=UUID=dece2035-1a42-4d1e-8304-9f2e23921132
  InstallationDate: Installed on 2016-07-24 (369 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Acer Aspire V3-472G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic.efi.signed 
root=UUID=c4a143c7-b490-423a-9645-ff2ffe57a345 ro quiet splash 
intel_pstate=disable "acp_osi=!Windows 2013" vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-28-generic N/A
   linux-backports-modules-4.10.0-28-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-07-29 (0 days ago)
  dmi.bios.date: 09/24/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA40_HB
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.21:bd09/24/2014:svnAcer:pnAspireV3-472G:pvrTBDbyOEM:rvnAcer:rnEA40_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire V3-472G
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1627828] Re: iwl3945 crashes randomly

[John Pilkington]

I have tried this script, modified to use wlp16s0.  It reports 'Power
save: off' on both entry and exit and has no apparent effect.  Still no
firmware load, and ifconfig -a shows no inet address.

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

Title:
  iwl3945 crashes randomly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Out of nothing a once properly working 
  0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] 
Network Connection (rev 02)
  started to crash with:
  Sep 22 14:38:16 seba-Latitude-D630 kernel: [26707.320032] iwl3945 
:0c:00.0: Error sending C_POWER_TBL: time out after 500ms.
  Sep 22 14:38:16 seba-Latitude-D630 kernel: [26707.320039] iwl3945 
:0c:00.0: set power fail, ret = -110
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.012031] iwl3945 
:0c:00.0: Queue 2 stuck for 2500 ms.
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.012039] iwl3945 
:0c:00.0: On demand firmware reload
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.050333] ieee80211 phy0: 
Hardware restart was requested
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.084769] retire_capture_urb: 
33 callbacks suppressed
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.098359] iwl3945 
:0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 
0xa5a5a5a2, s/b 0xf802020
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.098364] iwl3945 
:0c:00.0: Unable to set up bootstrap uCode: -5
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.145087] iwl3945 
:0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 
0xa5a5a5a2, s/b 0xf802020
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.145089] iwl3945 
:0c:00.0: Unable to set up bootstrap uCode: -5
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.191802] iwl3945 
:0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 
0xa5a5a5a2, s/b 0xf802020
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.191805] iwl3945 
:0c:00.0: Unable to set up bootstrap uCode: -5
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.238526] iwl3945 
:0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 
0xa5a5a5a2, s/b 0xf802020
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.238528] iwl3945 
:0c:00.0: Unable to set up bootstrap uCode: -5
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.285272] iwl3945 
:0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 
0xa5a5a5a2, s/b 0xf802020
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.285275] iwl3945 
:0c:00.0: Unable to set up bootstrap uCode: -5
  Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.322030] iwl3945 
:0c:00.0: Unable to initialize device after 5 attempts.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seba   1421 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Mon Sep 26 16:38:18 2016
  HibernationDevice: RESUME=UUID=64d7608d-53a8-46a6-884c-0ccf1814fb03
  InstallationDate: Installed on 2016-08-28 (29 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude D630
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=dce979b5-6a44-48cf-a87a-d314263a895c ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D630
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13

[Iron Davey]

I've tried this with the proposed xenial 4.11.0-13 kernel and it seems
to be working for me. I'm running a Precision 7510 with bios 1.13.6 . I
initially had a problem where the network card wasn't showing up, but
re-read earlier posts about disabling the thunderbolt dock security
feature in the BIOS. The only test I've done is to download the 16.04.3
iso image, and saw a peak of 11MB/s and a low of ~6MB/s.

As an aside, the TB16 I'm testing just showed up today, so I'm assuming
it has the latest firmware ;)

=
HTTP request sent, awaiting response... 200 OK
Length: 1587609600 (1.5G) [application/x-iso9660-image]
Saving to: ‘ubuntu-16.04.3-desktop-amd64.iso’

ubuntu-16.04.3-desk 100%[===>]   1.48G  7.80MB/sin
3m 16s

2017-08-18 15:13:37 (7.72 MB/s) - ‘ubuntu-16.04.3-desktop-amd64.iso’
saved [1587609600/1587609600]

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

Title:
  xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD
  ep_index 2 comp_code 13

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Released
Status in linux package in Arch Linux:
  New
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Unknown

Bug description:
  [SRU Justification]

  [Impact] 
  Dell TB16 docking station has issue to use gigabit ethernet. The ethernet
  will disconnect unless it's changed to 100Mb/s.

  
  [Test Case]
  Download some big files from the web.
  User confirms the patch fixes the issue.

  [Regression Potential] 
  This patch only effects ASMEDIA's ASM1042A.
  The regression potential is low, also limited to the specific device.

  ---

  My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit
  Ethernet Adapter which is on usb3 bus in my docking station (Dell
  TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3.

  I get usb related kernel error messages when I initiate a high speed
  transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current
  /zesty-desktop-amd64.iso) and the download fails.

  This does not happened when the Ethernet adapter is connected to a
  100Mb/s switch, but only when connected to 1000Mb/s. It also does not
  happened with slow traffic (e.g. web page browsing). This is not a new
  bug with kernel 4.10, but has been going on since at least 4.7 and
  maybe (probably?) since forever. I'm aware of several others with this
  configuration (RTL8153 on usb3 behind thunderbolt 3) that have the
  same issue. This bug is also not specific to Ubuntu; I also get it on
  Arch Linux. I've also tested and seen this bug with several different
  models of thunderbolt 3 docks.

  Here are the relevant kernel log messages:

  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9060 trb-start 

[Kernel-packages] [Bug 1709126] Re: kernel BUG at [tty_ldisc_reinit] mm/slub.c!

[Kamal Mostafa]

Waiving the verification-needed-xenial, since this was originally
reported against linux-lts-xenial (no known xenial test installation
exists).  Will ask the original reporter to re-verify the fix in linux-
lts-xenial.

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

Title:
  kernel BUG at [tty_ldisc_reinit] mm/slub.c!

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

Bug description:
  Reported in LP:#1707089:
  Reported against v4.4 LTS kernel on 14.04; probably applicable to main v4.4 
kernel on 16.04 also.

  --

  The ubuntu 14.04 kernel panics on boot about 1% of the time.

  
  [ 0.00] Linux version 4.4.0-83-generic (buildd@lgw01-10) (gcc version 
4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #106~14.04.1-Ubuntu SMP Mon Jun 26 
18:10:19 UTC 2017 (Ubuntu 4.4.0-83.106~14.04.1-generic 4.4.70)
  [ 0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 
root=UUID=1edb4b60-6835-4d9c-8aeb-be3418d70937 ro scsi_mod.use_blk_mq=Y 
console=ttyS0
  .
  [ 8.510775] [ cut here ]
  [ 8.512172] kernel BUG at 
/build/linux-lts-xenial-ep3zLI/linux-lts-xenial-4.4.0/mm/slub.c:3627!
  [ 8.514572] invalid opcode:  [#1] SMP
  [ 8.515937] Modules linked in: crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd psmouse virtio_scsi
  [ 8.521408] CPU: 3 PID: 1 Comm: init Not tainted 4.4.0-83-generic 
#106~14.04.1-Ubuntu
  [ 8.523723] Hardware name: Google Google Compute Engine/Google Compute 
Engine, BIOS Google 01/01/2011
  [ 8.526418] task: 8803ee608000 ti: 8803ee604000 task.ti: 
8803ee604000
  [ 8.528521] RIP: 0010:[] [] 
kfree+0x14a/0x150
  [ 8.530794] RSP: 0018:8803ee607cf8 EFLAGS: 00010246
  [ 8.532516] RAX: ea000bb817e0 RBX: 8802ee05fbe0 RCX: 00018040001f
  [ 8.534833] RDX: 77ff8000 RSI: 0282 RDI: 8802ee05fbe0
  [ 8.536833] RBP: 8803ee607d10 R08: 8800bb80ae80 R09: 00018040001f
  [ 8.538830] R10: bb80ac01 R11: ea000bb817c0 R12: 8802ee05fbe0
  [ 8.540956] R13: 814dd53d R14: 8803ee747990 R15: 
  [ 8.543009] FS: 7f7d1c626840() GS:8803ffd8() 
knlGS:
  [ 8.545542] CS: 0010 DS:  ES:  CR0: 80050033
  [ 8.547433] CR2: 7f9201dd07d0 CR3: 0003e8455000 CR4: 001406e0
  [ 8.549688] Stack:
  [ 8.550384] 880036697400 8802ee05fbe0  
8803ee607d40
  [ 8.552627] 814dd53d 880036697400 8802ee05fbe0 
0002
  [ 8.554791]  8803ee607d68 814ddb24 

  [ 8.556542] Call Trace:
  [ 8.557249] [] tty_ldisc_reinit+0x6d/0xe0
  [ 8.558855] [] tty_ldisc_hangup+0xd4/0x1f0
  [ 8.560500] [] __tty_hangup+0x302/0x420
  [ 8.562263] [] tty_vhangup+0x10/0x20
  [ 8.563748] [] pty_close+0x148/0x190
  [ 8.565396] [] tty_release+0x105/0x570
  [ 8.566995] [] __fput+0xe4/0x210
  [ 8.568528] [] ? tty_ldisc_deref+0x16/0x20
  [ 8.570225] [] fput+0xe/0x10
  [ 8.571779] [] task_work_run+0x86/0xb0
  [ 8.573355] [] exit_to_usermode_loop+0x73/0xa2
  [ 8.575236] [] syscall_return_slowpath+0x4e/0x60
  [ 8.576499] [] int_ret_from_sys_call+0x25/0x8f
  [ 8.578334] Code: 8b 03 31 f6 f6 c4 40 74 04 41 8b 73 6c 4c 89 df e8 cc cc fa 
ff e9 73 ff ff ff 4c 8d 58 ff e9 20 ff ff ff 49 8b 43 20 a8 01 75 d4 <0f> 0b 0f 
1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 41 55
  [ 8.586832] RIP [] kfree+0x14a/0x150
  [ 8.588673] RSP 
  [ 8.589869] ---[ end trace 87fcf5b5cdf6b7f0 ]---
  [ 8.591565] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b
  [ 8.591565]
  [ 8.594520] Kernel Offset: disabled
  [ 8.595719] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b
  [ 8.595719]

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

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

Re: [Kernel-packages] [Bug 1696325] Re: USB, display and ethernet ports in HP Thunderbolt dock don't work

[Markus Paaso]

Unfortunately I don't have that laptop anymore. Currently I have Dell
Precision M5520 with Ubuntu 16.04 pre-installed and almost everything is
working excellently with its TB16 dock.

(3440x1440 resolution through HDMI is not always working at first try, but
after disabling and enabling few times the external display from System
Settings > Display, it starts to work. But that might be some hardware or
cable issue.)

I am using mainline kernel v4.12.5 installed with Ukuu.

18.8.2017 22.41 "Mika Westerberg"  kirjoitti:

Thunderbolt support for PCs is included in v4.13-rc1 and later kernels.
Do you have a possibility to try the latest mainline kernel?

Note the userspace support is not yet ready so you need to authorize
device manually. See for example:https://www.kernel.org/doc/html/latest
/admin-guide/thunderbolt.html how it can be done.

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1696325

Title:
  USB, display and ethernet ports in HP Thunderbolt dock don't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have laptop HP ZBook G3 Studio with Thunderbolt dock P5Q58AA.
  Installed OS is Ubuntu 16.04.2 LTS

  When I connect dock into laptop only power works and laptop can be
  shutdown by pressing power button in dock. USB ports, display ports,
  ethernet port and audio plug are not working.


  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  $ apt-cache policy linux-image-generic-hwe-16.04
  linux-image-generic-hwe-16.04:
Installed: 4.8.0.54.25
Candidate: 4.8.0.54.25
Version table:
   *** 4.8.0.54.25 500
  500 http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64
Packages
  100 /var/lib/dpkg/status
  ---
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  markus 3304 F pulseaudio
   /dev/snd/controlC0:  markus 3304 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-07 (61 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
   Bus 001 Device 002: ID 045e:07f8 Microsoft Corp. Wired Keyboard 600
(model 1576)
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ZBook Studio G3
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-54-generic.efi.signed
root=UUID=2b78b572-05a1-4c01-b97d-9c1fea406faf ro quiet splash nomodeset
pnpacpi=off vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-54-generic N/A
   linux-backports-modules-4.8.0-54-generic  N/A
   linux-firmware1.157.10
  Tags:  xenial
  Uname: Linux 4.8.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/02/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N82 Ver. 01.15
  dmi.board.name: 80D4
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 11.67
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: dmi:bvnHP:bvrN82Ver.01.15:bd11/02/2016:svnHP:
pnHPZBookStudioG3:pvr:rvnHP:rn80D4:rvrKBCVersion11.67:cvnHP:ct10:cvr:
  dmi.product.name: HP ZBook Studio G3
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696325/+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/1696325

Title:
  USB, display and ethernet ports in HP Thunderbolt dock don't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have laptop HP ZBook G3 Studio with Thunderbolt dock P5Q58AA.
  Installed OS is Ubuntu 16.04.2 LTS

  When I connect dock into laptop only power works and laptop can be
  shutdown by pressing power button in dock. USB ports, display ports,
  ethernet port and audio plug are not working.

  
  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  $ apt-cache policy linux-image-generic-hwe-16.04
  linux-image-generic-hwe-16.04:
Installed: 4.8.0.54.25
Candidate: 4.8.0.54.25
Version table:
   *** 4.8.0.54.25 500
  500 http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 

[Kernel-packages] [Bug 1696325] Re: USB, display and ethernet ports in HP Thunderbolt dock don't work

[Mika Westerberg]

Thunderbolt support for PCs is included in v4.13-rc1 and later kernels.
Do you have a possibility to try the latest mainline kernel?

Note the userspace support is not yet ready so you need to authorize
device manually. See for example:https://www.kernel.org/doc/html/latest
/admin-guide/thunderbolt.html how it can be done.

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

Title:
  USB, display and ethernet ports in HP Thunderbolt dock don't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have laptop HP ZBook G3 Studio with Thunderbolt dock P5Q58AA.
  Installed OS is Ubuntu 16.04.2 LTS

  When I connect dock into laptop only power works and laptop can be
  shutdown by pressing power button in dock. USB ports, display ports,
  ethernet port and audio plug are not working.

  
  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  $ apt-cache policy linux-image-generic-hwe-16.04
  linux-image-generic-hwe-16.04:
Installed: 4.8.0.54.25
Candidate: 4.8.0.54.25
Version table:
   *** 4.8.0.54.25 500
  500 http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
  --- 
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  markus 3304 F pulseaudio
   /dev/snd/controlC0:  markus 3304 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-07 (61 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
   Bus 001 Device 002: ID 045e:07f8 Microsoft Corp. Wired Keyboard 600 (model 
1576)
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ZBook Studio G3
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-54-generic.efi.signed 
root=UUID=2b78b572-05a1-4c01-b97d-9c1fea406faf ro quiet splash nomodeset 
pnpacpi=off vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-54-generic N/A
   linux-backports-modules-4.8.0-54-generic  N/A
   linux-firmware1.157.10
  Tags:  xenial
  Uname: Linux 4.8.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/02/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N82 Ver. 01.15
  dmi.board.name: 80D4
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 11.67
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN82Ver.01.15:bd11/02/2016:svnHP:pnHPZBookStudioG3:pvr:rvnHP:rn80D4:rvrKBCVersion11.67:cvnHP:ct10:cvr:
  dmi.product.name: HP ZBook Studio G3
  dmi.sys.vendor: HP

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

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

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

[bugproxy]

--- Comment From hbath...@in.ibm.com 2017-08-18 13:50 EDT---
Noticed that the offset for crashkernel is set to 32MB in
/etc/default/grub.d/kdump-tools..ppc64el file . Any specific reason
why this value is chosen? With the default offset on powerpc being
128MB, this seems way off (considering there is only so much real
memory available.) Can the offset (@32M) be stripped from
/etc/default/grub.d/kdump-tools..ppc64el file to fall back to the
kernel default..

Thanks
Hari

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

Title:
  kdump-tools uses the wrong crashkernel command line parameter in
  ppc64le

Status in The Ubuntu-power-systems project:
  New
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile package in Debian:
  Fix Released

Bug description:
  == Comment: #0 - Thiago Jung Bauermann  - 2017-03-24 
11:44:39 ==
  ---Problem Description---
  kdump-tools uses the wrong crashkernel command line parameter in ppc64le:

  u1704le?? grep crashkernel /boot/grub/grub.cfg
  linux   /boot/vmlinux-4.10.0-13-generic 
root=UUID=2d6f73c7-b463-4f02-9ec4-8d4afed0635d ro   crashkernel=384M-:128M

  128M of reserved memory is too small for ppc64le.

  That happens because /etc/default/grub.d/kdump-tools.cfg links to the
  wrong file:

  u1704le??  ls -l /etc/default/grub.d/
  total 8.0K
  lrwxrwxrwx 1 root root  39 Mar 24 13:34 kdump-tools.cfg -> 
/etc/default/grub.d/kdump-tools.default
  -rw-r--r-- 1 root root  80 Jan  5 08:07 kdump-tools.default
  -rw-r--r-- 1 root root 137 Jan  5 08:07 kdump-tools..ppc64el
  u1704le?? 

  As can be seen, it should be pointing to kdump-tools..ppc64el but
  isn't.

  Also, kdump-tools..ppc64el has two dots in it. That doesn't seem right.
  Possibly just a cosmetic issue, but it would be nice if that was fixed.
   
  Contact Information = thiag...@br.ibm.com 
   
  ---uname output---
  Linux u1704le 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:27:28 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Any ppc64le machine. In this case, a KVM guest hosted on an 
8286-42A. 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   sudo apt intall kdump-tools
  Select 'Yes' when asked whether kdump should be enabled.
   
  Userspace tool common name: kdump 
   
  The userspace tool has the following bit modes: 64 bit 

  Userspace rpm: kdump-tools

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for thiag...@br.ibm.com:
  -Attach ltrace and strace of userspace application.

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

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

[Kernel-packages] [Bug 1707610] Re: fanctl does not stop setup on first match

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-fan - 0.12.4

---
ubuntu-fan (0.12.4) artful; urgency=medium

  [ Andy Whitcroft ]
  * fanctl: only bring up enabled Fan Networks in --auto mode (LP: #1707610)
  * fanctl: correctly specify local interface specific config (LP: #1707610)
  * fanatic: recast advanced commands as non-interactive
  * fanatic: fix spelling in primary help
  * fanatic: fix references to fanatic manual page

  [ Stefan Bader ]
  * fanatic: Fix typo in progress output
  * README: Refresh documentation
  * fanctl.8: Refresh documentation
  * fanatic.8: Refresh documentation
  * fanatic.8: Reword advanced to non-interactive usage
  * DEP8: lxd: Suppress stderr on profile list

 -- Stefan Bader   Wed, 16 Aug 2017 15:58:46
+0200

** Changed in: ubuntu-fan (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  fanctl does not stop setup on first match

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  New
Status in ubuntu-fan source package in Zesty:
  New

Bug description:
  SRU Justification (Zesty/Xenial)

  Impact: When /etc/network/fan contains two entries for the same
  mapping (for example on mapping for the generic network mapping and
  one for a specific interface) it will try to set up the same Fan
  bridge twice.

  Fix: Add a break which exits the setup loop once there has been one
  successful run.

  Testcase: If in an environment that uses one of the 192.168.0.0/16 subnets, 
and host has for example a 192.168.1.0/24 address. Then trying to use
   fanatic enable-fan -u 192.168.1.x/24 -o 250.0.0.0/8
  would show an error now and with the fix applied work ok.

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

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

[Kernel-packages] [Bug 1707570] Re: CVE-2017-7533

[Steve Beattie]

Fixed in USNs 3377-1, 3377-1, 3378-1, and 3378-2. Making public and
closing.

** Information type changed from Private Security to Public Security

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

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

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

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

Title:
  CVE-2017-7533

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  CRD: 2017-08-03 15:00 UTC
  OWNERS:
   security: sbeattie
   kernel:
   archive admin:

  break-fix:  7053aee26a3548ebaba046ae2e52396ccf56ac6c
  49d31c2f389acfe83417083e1208422b4091cd9e

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

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

[Kernel-packages] [Bug 1682644] Re: IPR driver causes multipath to fail paths/stuck IO on Medium Errors

[Mauricio Faria de Oliveira]

Bug description updated w/ SRU template.

Patch submitted to kernel-team mailing list.

[SRU Z/X][PATCH] scsi: ipr: do not set DID_PASSTHROUGH on CHECK CONDITION
https://lists.ubuntu.com/archives/kernel-team/2017-August/086518.html

Requested for 
- Zesty/17.04 (target 16.04.3 HWE kernel / v4.10-based) and 
- Xenial/16.04 (GA kernel / v4.4-based). 

Already applied on 
- Artful/17.10 (16.04.4 HWE kernel).


** Description changed:

+ SRU Justification:
+ 
+ Impact: stuck I/O to multipath disks with medium errors (on IPR controllers)
+ Fix: upstream commit for IPR driver to allow SCSI layer to handle the error
+ Testcase: perform I/O to a failing disk which is multipathed (on IPR
+   controller), which returns SCSI Medium Errors (without the fix,
+   the I/O gets stuck). 
+   the commit message describes a test-case w/ sg_dd.
+ 
+ 
  ---Problem Description---
  IPR driver causes multipath to fail paths/stuck IO on Medium Errors
  
  This problem is resolved with this upstream accepted patch, scheduled for 
4.11.
  The detailed problem description and resolution are described in the commit 
message.
  
  > scsi: ipr: do not set DID_PASSTHROUGH on CHECK CONDITION
- > 
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi.git;a=commit;h=785a470496d8e0a32e3d39f376984eb2c98ca5b3
+ > 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=785a470496d8e0a32e3d39f376984eb2c98ca5b3
  
- Please apply to 17.04 and 16.04.
+ Please apply to 17.04 (target 16.04.3 HWE kernel) and 16.04 (GA kernel).
+ Patch already applied to 17.10.
  
  The business justification for the SRU is:
  
  Clients with a dual-controller multipathed IPR configuration that
  eventually runs into failing disk/sectors, will experience an I/O hang
  once the drive reports a Medium Error, which can hang an application or
  even the root filesystem (whatever is doing I/O to the failing drive),
  potentially hanging the system.
  
  Thanks.
-  
+ 
  ---Additional Hardware Info---
- Dual (IPR) controller setup, multipath enabled 
-  
+ Dual (IPR) controller setup, multipath enabled
+ 
  ---Steps to Reproduce---
  1) Use a disk with bad sectors (or force such condition, via internal/special 
tools)
  2) Multipath that disk
  3) Run IO to the multipath device on the bad sectors
  4) Both paths will be failed, and IO is stuck due to queue_if_no_path 
(enabled by default for IPR)
  
  The detailed problem description and resolution are described in the
  commit message.

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

Title:
  IPR driver causes multipath to fail paths/stuck IO on Medium Errors

Status in linux package in Ubuntu:
  Triaged

Bug description:
  SRU Justification:

  Impact: stuck I/O to multipath disks with medium errors (on IPR controllers)
  Fix: upstream commit for IPR driver to allow SCSI layer to handle the error
  Testcase: perform I/O to a failing disk which is multipathed (on IPR
controller), which returns SCSI Medium Errors (without the fix,
the I/O gets stuck). 
the commit message describes a test-case w/ sg_dd.

  
  ---Problem Description---
  IPR driver causes multipath to fail paths/stuck IO on Medium Errors

  This problem is resolved with this upstream accepted patch, scheduled for 
4.11.
  The detailed problem description and resolution are described in the commit 
message.

  > scsi: ipr: do not set DID_PASSTHROUGH on CHECK CONDITION
  > 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=785a470496d8e0a32e3d39f376984eb2c98ca5b3

  Please apply to 17.04 (target 16.04.3 HWE kernel) and 16.04 (GA kernel).
  Patch already applied to 17.10.

  The business justification for the SRU is:

  Clients with a dual-controller multipathed IPR configuration that
  eventually runs into failing disk/sectors, will experience an I/O hang
  once the drive reports a Medium Error, which can hang an application
  or even the root filesystem (whatever is doing I/O to the failing
  drive), potentially hanging the system.

  Thanks.

  ---Additional Hardware Info---
  Dual (IPR) controller setup, multipath enabled

  ---Steps to Reproduce---
  1) Use a disk with bad sectors (or force such condition, via internal/special 
tools)
  2) Multipath that disk
  3) Run IO to the multipath device on the bad sectors
  4) Both paths will be failed, and IO is stuck due to queue_if_no_path 
(enabled by default for IPR)

  The detailed problem description and resolution are described in the
  commit message.

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

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

[Kernel-packages] [Bug 1676884] Re: kdump-tools uses the wrong crashkernel command line parameter in ppc64le

[dann frazier]

The fixed from Debian has now been merged into artful.

** Changed in: makedumpfile (Ubuntu)
   Status: New => Fix Released

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

Title:
  kdump-tools uses the wrong crashkernel command line parameter in
  ppc64le

Status in The Ubuntu-power-systems project:
  New
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile package in Debian:
  Fix Released

Bug description:
  == Comment: #0 - Thiago Jung Bauermann  - 2017-03-24 
11:44:39 ==
  ---Problem Description---
  kdump-tools uses the wrong crashkernel command line parameter in ppc64le:

  u1704le?? grep crashkernel /boot/grub/grub.cfg
  linux   /boot/vmlinux-4.10.0-13-generic 
root=UUID=2d6f73c7-b463-4f02-9ec4-8d4afed0635d ro   crashkernel=384M-:128M

  128M of reserved memory is too small for ppc64le.

  That happens because /etc/default/grub.d/kdump-tools.cfg links to the
  wrong file:

  u1704le??  ls -l /etc/default/grub.d/
  total 8.0K
  lrwxrwxrwx 1 root root  39 Mar 24 13:34 kdump-tools.cfg -> 
/etc/default/grub.d/kdump-tools.default
  -rw-r--r-- 1 root root  80 Jan  5 08:07 kdump-tools.default
  -rw-r--r-- 1 root root 137 Jan  5 08:07 kdump-tools..ppc64el
  u1704le?? 

  As can be seen, it should be pointing to kdump-tools..ppc64el but
  isn't.

  Also, kdump-tools..ppc64el has two dots in it. That doesn't seem right.
  Possibly just a cosmetic issue, but it would be nice if that was fixed.
   
  Contact Information = thiag...@br.ibm.com 
   
  ---uname output---
  Linux u1704le 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:27:28 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Any ppc64le machine. In this case, a KVM guest hosted on an 
8286-42A. 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   sudo apt intall kdump-tools
  Select 'Yes' when asked whether kdump should be enabled.
   
  Userspace tool common name: kdump 
   
  The userspace tool has the following bit modes: 64 bit 

  Userspace rpm: kdump-tools

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for thiag...@br.ibm.com:
  -Attach ltrace and strace of userspace application.

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

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

[Kernel-packages] [Bug 1711251] Re: vhost guest network randomly drops under stress (kvm)

[Frank Heimes]

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

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

Title:
  vhost guest network randomly drops under stress (kvm)

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

Bug description:
  ---Problem Description---
  A vhost performance patch was introduced in the 4.10 kernel upstream, and is 
currently included in the Zesty 4.10 kernel:

  commit 809ecb9bca6a9424ccd392d67e368160f8b76c92
  Author: Jason Wang 
  Date:   Mon Dec 12 14:46:49 2016 +0800

  vhost: cache used event for better performance

  --

  However I recently hit a functional issue linked to this patch which
  would cause random guests to lose their network connection under
  stress.  This is not architecture specific and more likely to be hit
  with high network stress (i.e. lots of uperf instances).

  The patch author has now reverted this patch upstream:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/vhost?id=8d65843c44269c21e95c98090d9bb4848d473853

  which reads:
  " 
  Revert "vhost: cache used event for better performance"
  This reverts commit 809ecb9bca6a9424ccd392d67e368160f8b76c92. Since it
  was reported to break vhost_net. We want to cache used event and use
  it to check for notification. The assumption was that guest won't move
  the event idx back, but this could happen in fact when 16 bit index
  wraps around after 64K entries.

  Signed-off-by: Jason Wang 
  Acked-by: Michael S. Tsirkin 
  Signed-off-by: David S. Miller 
  "

  I am requesting this patch to revert the problematic one be pulled into 
Ubuntu Zesty (anything 4.10+).
   
  ---uname output---
  Linux p82qvirt 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:19 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8247-22L 
   
  ---Steps to Reproduce---
   I can recreate the scenario with the following setup:
   - on a 20core host, start 20 1core VMs
   - I have a single linux bridge assigned to all guests using virtio
   - start a uperf benchmark between each guest pair (10 total) using a high 
number of uperf nprocs (32)

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

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

[Kernel-packages] [Bug 1711251] Re: vhost guest network randomly drops under stress (kvm)

[Joseph Salisbury]

I built a Zesty test kernel with a revert of commit 809ecb9bca.  The
test kernel can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1711251

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

Thanks in advance!

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

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

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

Title:
  vhost guest network randomly drops under stress (kvm)

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

Bug description:
  ---Problem Description---
  A vhost performance patch was introduced in the 4.10 kernel upstream, and is 
currently included in the Zesty 4.10 kernel:

  commit 809ecb9bca6a9424ccd392d67e368160f8b76c92
  Author: Jason Wang 
  Date:   Mon Dec 12 14:46:49 2016 +0800

  vhost: cache used event for better performance

  --

  However I recently hit a functional issue linked to this patch which
  would cause random guests to lose their network connection under
  stress.  This is not architecture specific and more likely to be hit
  with high network stress (i.e. lots of uperf instances).

  The patch author has now reverted this patch upstream:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/vhost?id=8d65843c44269c21e95c98090d9bb4848d473853

  which reads:
  " 
  Revert "vhost: cache used event for better performance"
  This reverts commit 809ecb9bca6a9424ccd392d67e368160f8b76c92. Since it
  was reported to break vhost_net. We want to cache used event and use
  it to check for notification. The assumption was that guest won't move
  the event idx back, but this could happen in fact when 16 bit index
  wraps around after 64K entries.

  Signed-off-by: Jason Wang 
  Acked-by: Michael S. Tsirkin 
  Signed-off-by: David S. Miller 
  "

  I am requesting this patch to revert the problematic one be pulled into 
Ubuntu Zesty (anything 4.10+).
   
  ---uname output---
  Linux p82qvirt 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:19 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8247-22L 
   
  ---Steps to Reproduce---
   I can recreate the scenario with the following setup:
   - on a 20core host, start 20 1core VMs
   - I have a single linux bridge assigned to all guests using virtio
   - start a uperf benchmark between each guest pair (10 total) using a high 
number of uperf nprocs (32)

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

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

[Kernel-packages] [Bug 1567557] Re: Performance degradation of "zfs clone"

[Colin Ian King]

Tested with zfs 0.6.5.6-0ubuntu18 on Xenial. Passes zfs smoke tests. The
performance increase on Xenial is not so significant than later
releases, but I'm seeing double digit % increase in performance with a
test of 3000 clones.

** Tags added: verification-done-xenial

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

Title:
  Performance degradation of "zfs clone"

Status in Native ZFS for Linux:
  New
Status in lxd package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in lxd source package in Xenial:
  New
Status in zfs-linux source package in Xenial:
  Fix Committed
Status in lxd source package in Zesty:
  New
Status in zfs-linux source package in Zesty:
  Fix Committed
Status in lxd source package in Artful:
  Confirmed
Status in zfs-linux source package in Artful:
  Fix Released

Bug description:
  [SRU Justification]

  Creating tens of hundreds of clones can be prohibitively slow. The
  underlying mechanism to gather clone information is using a 16K buffer
  which limits performance.  Also, the initial assumption is to pass in
  zero sized buffer to   the underlying ioctl() to get an idea of the
  size of the buffer required to fetch information back to userspace.
  If we bump the initial buffer to a larger size then we reduce the need
  for two ioctl calls which improves performance.

  [Fix]
  Bump initial buffer size from 16K to 256K

  [Regression Potential]
  This is minimal as this is just a tweak in the initial buffer size and larger 
sizes are handled correctly by ZFS since they are normally used on the second 
ioctl() call once we have established the size of the buffer required from the 
first ioctl() call. Larger initial buffers just remove the need for the initial 
size estimation for most cases where the number of clones is less than ~5000.  
There is a risk that a larger buffer size could lead to a ENOMEM issue when 
allocating the buffer, but the size of buffer used is still trivial for modern 
large 64 bit servers running ZFS.

  [Test case]
  Create 4000 clones. With the fix this takes 35-40% less time than without the 
fix. See the example test.sh script as an example of how to create this many 
clones.


  
  --

  I've been running some scale tests for LXD and what I've noticed is
  that "zfs clone" gets slower and slower as the zfs filesystem is
  getting busier.

  It feels like "zfs clone" requires some kind of pool-wide lock or
  something and so needs for all operations to complete before it can
  clone a new filesystem.

  A basic LXD scale test with btrfs vs zfs shows what I mean, see below
  for the reports.

  The test is run on a completely dedicated physical server with the
  pool on a dedicated SSD, the exact same machine and SSD was used for
  the btrfs test.

  The zfs filesystem is configured with those settings:
   - relatime=on
   - sync=disabled
   - xattr=sa

  So it shouldn't be related to pending sync() calls...

  The workload in this case is ultimately 1024 containers running busybox as 
their init system and udhcpc grabbing an IP.
  The problem gets significantly worse if spawning busier containers, say a 
full Ubuntu system.

  === zfs ===
  root@edfu:~# /home/ubuntu/lxd-benchmark spawn --count=1024 
--image=images:alpine/edge/amd64 --privileged=true
  Test environment:
    Server backend: lxd
    Server version: 2.0.0.rc8
    Kernel: Linux
    Kernel architecture: x86_64
    Kernel version: 4.4.0-16-generic
    Storage backend: zfs
    Storage version: 5
    Container backend: lxc
    Container version: 2.0.0.rc15

  Test variables:
    Container count: 1024
    Container mode: privileged
    Image: images:alpine/edge/amd64
    Batches: 128
    Batch size: 8
    Remainder: 0

  [Apr  3 06:42:51.170] Importing image into local store: 
64192037277800298d8c19473c055868e0288b039349b1c6579971fe99fdbac7
  [Apr  3 06:42:52.657] Starting the test
  [Apr  3 06:42:53.994] Started 8 containers in 1.336s
  [Apr  3 06:42:55.521] Started 16 containers in 2.864s
  [Apr  3 06:42:58.632] Started 32 containers in 5.975s
  [Apr  3 06:43:05.399] Started 64 containers in 12.742s
  [Apr  3 06:43:20.343] Started 128 containers in 27.686s
  [Apr  3 06:43:57.269] Started 256 containers in 64.612s
  [Apr  3 06:46:09.112] Started 512 containers in 196.455s
  [Apr  3 06:58:19.309] Started 1024 containers in 926.652s
  [Apr  3 06:58:19.309] Test completed in 926.652s

  === btrfs ===
  Test environment:
    Server backend: lxd
    Server version: 2.0.0.rc8
    Kernel: Linux
    Kernel architecture: x86_64
    Kernel version: 4.4.0-16-generic
    Storage backend: btrfs
    Storage version: 4.4
    Container backend: lxc
    Container version: 2.0.0.rc15

  Test variables:
    Container count: 1024
    Container mode: privileged
    Image: images:alpine/edge/amd64
    Batches: 128
    

[Kernel-packages] [Bug 1708432] Re: [17.10 FEAT] Enable NVMe driver - kernel

[Seth Forshee]

Set CONFIG_BLK_DEV_NVME=m in the artful 4.12 and 4.13 kernels. kdump
will automatically pull the module into the initrd for the crash kernel
if it is needed, no changes are required to make that happen.

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

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

Title:
  [17.10 FEAT] Enable NVMe driver - kernel

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Distributor ToDos:
  - Enable Linux kernel configuration options related to the Linux PCI NVMe 
device driver (CONFIG_BLK_DEV_NVME)
  - Include NVMe driver in kdump kernel

  - Include package "nvme-cli" on s390x -> already available !

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

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

[Kernel-packages] [Bug 1658352] Re: package initramfs-tools 0.103ubuntu4.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1.

[Rolf Leggewie]

Asif, did Steve's instructions help you to resolve the issue?

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

** Changed in: linux-firmware (Ubuntu)
 Assignee: (unassigned) => Rolf Leggewie (r0lf)

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

Title:
  package initramfs-tools 0.103ubuntu4.7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1.

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  whenever i try to upgrade my operating system from ubuntu 14.04 to
  16.04 error show "could not install initramfs-tools", "could not
  install linux-firmware" and "could not install linux-
  image-4.4.0-59-generic" and te upgrade is failed show could not
  install upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.103ubuntu4.7
  ProcVersionSignature: Ubuntu 3.13.0-108.155-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-108-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Sat Jan 21 23:52:45 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  DuplicateSignature: package:initramfs-tools:0.103ubuntu4.7: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-01-14 (7 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.103ubuntu4.7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-01-21 (0 days ago)

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

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

[Kernel-packages] [Bug 1708432] Re: [17.10 FEAT] Enable NVMe driver - kernel

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: New => Fix Committed

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

Title:
  [17.10 FEAT] Enable NVMe driver - kernel

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Distributor ToDos:
  - Enable Linux kernel configuration options related to the Linux PCI NVMe 
device driver (CONFIG_BLK_DEV_NVME)
  - Include NVMe driver in kdump kernel

  - Include package "nvme-cli" on s390x -> already available !

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

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

[Kernel-packages] [Bug 1708432] Re: [17.10 FEAT] Enable NVMe driver - kernel

[Seth Forshee]

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

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

** Changed in: linux (Ubuntu)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

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

Title:
  [17.10 FEAT] Enable NVMe driver - kernel

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Distributor ToDos:
  - Enable Linux kernel configuration options related to the Linux PCI NVMe 
device driver (CONFIG_BLK_DEV_NVME)
  - Include NVMe driver in kdump kernel

  - Include package "nvme-cli" on s390x -> already available !

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

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

[Kernel-packages] [Bug 1711571] Re: linux: 4.12.0-12.13 -proposed tracker

[Brad Figg]

** Changed in: kernel-development-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-development-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-development-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-development-workflow/automated-testing
   Status: Confirmed => Incomplete

** Description changed:

  This bug is for tracking the 4.12.0-12.13 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:Uploaded
- kernel-phase-changed:Friday, 18. August 2017 10:41 UTC
- 
  -- swm properties --
  phase: Uploaded
+ kernel-phase:Promoted to proposed
+ kernel-phase-changed:Friday, 18. August 2017 13:01 UTC

** Description changed:

  This bug is for tracking the 4.12.0-12.13 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 --
- phase: Uploaded
- kernel-phase:Promoted to proposed
- kernel-phase-changed:Friday, 18. August 2017 13:01 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 4.12.0-12.13 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.12.0-12.13 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 --
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1711401] Re: accessing /dev/hvc1 with stress-ng on Ubuntu xenial causes crash

[Stefan Bader]

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

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

Title:
  accessing /dev/hvc1 with stress-ng on Ubuntu xenial causes crash

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

Bug description:
  [SRU REQUEST][XENIAL]

  When running stress-ng --dev stressor accessing /dev/hvc1 causes the
  stressor to lock up and never terminal.

  [FIX]
  Upstream commmit:From bbc3dfe8805de86874b1a1b1429a002e8670043e Mon Sep 17 
00:00:00 2001
  From: Sam Mendoza-Jonas 
  Date: Mon, 11 Jul 2016 13:38:57 +1000
  Subject: [PATCH] tty/hvc: Use IRQF_SHARED for OPAL hvc consoles

  [TESTING]
  Without the fix, stress-ng --dev run as root hangs, and one gets an irq 
failed error and an oops:

  [ 2096.476610] hvc_open: request_irq failed with rc -16.
  [ 2096.476634] Unable to handle kernel paging request for data at address 
0x00a8
  [ 2096.476641] Faulting instruction address: 0xc0b0d8a4
  [ 2096.476647] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 2096.476650] SMP NR_CPUS=2048 NUMA PowerNV

  With the fix, the stressor runs w/o any issues

  [REGRESSION POTENTIAL]
  This is specific to one driver for ppc64el, so the risk potential is limited. 
The fix has limited regression potential as it essentially marks a flag to 
allow interrupt to be shared and fundamentally this is a very minor change to  
the interrupt handling functionality in the driver.

  ---

  stress-ng run as root, --dev stressor, accessing /dev/hvc1:

  [ 2096.476610] hvc_open: request_irq failed with rc -16.
  [ 2096.476634] Unable to handle kernel paging request for data at address 
0x00a8
  [ 2096.476641] Faulting instruction address: 0xc0b0d8a4
  [ 2096.476647] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 2096.476650] SMP NR_CPUS=2048 NUMA PowerNV
  [ 2096.476657] Modules linked in: kvm_hv kvm_pr kvm cuse userio hci_vhci 
bluetooth uhid hid vhost_net vhost macvtap macvlan snd_seq snd_seq_device 
snd_timer snd soundcore ipmi_powernv ipmi_msghandler vmx_crypto leds_powernv 
uio_pdrv_genirq uio powernv_rng ibmpowernv ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr 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 dm_round_robin ses 
enclosure ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath
  [ 2096.476718] CPU: 74 PID: 23074 Comm: stress-ng-dev Not tainted 
4.4.0-92-generic #115-Ubuntu
  [ 2096.476724] task: c00fe8499030 ti: c00f0fa0c000 task.ti: 
c00f0fa0c000
  [ 2096.476728] NIP: c0b0d8a4 LR: c069648c CTR: 
c0696450
  [ 2096.476732] REGS: c00f0fa0f6b0 TRAP: 0300   Not tainted  
(4.4.0-92-generic)
  [ 2096.476736] MSR: 90009033   CR: 2248  
XER: 
  [ 2096.476749] CFAR: c0008468 DAR: 00a8 DSISR: 4000 
SOFTE: 0
     GPR00: c069648c c00f0fa0f930 c15f8000 
00a8
     GPR04: c00ff0082400 0002 001ffe7d 
0036
     GPR08: c3236b90  804a 
c01e4e568880
     GPR12: c0696450 cfb6bf00 000f 
010023d22660
     GPR16: 3fff9ca5 0080 c01e43dde100 
c00fe459c800
     GPR20:  0001 0e51 
00010004
     GPR24: 00010800  f000 
c1892448
     GPR28: c00fef98da28 c00fe459c800 0001 
00a8
  [ 2096.476805] NIP [c0b0d8a4] _raw_spin_lock_irqsave+0x44/0x130
  [ 2096.476812] LR [c069648c] hvc_open+0x3c/0x1a0
  [ 2096.476815] Call Trace:
  [ 2096.476818] [c00f0fa0f930] [c00f0fa0f970] 0xc00f0fa0f970 
(unreliable)
  [ 2096.476824] [c00f0fa0f970] [c069648c] hvc_open+0x3c/0x1a0
  [ 2096.476829] [c00f0fa0f9f0] [c066c514] tty_open+0x194/0x7c0
  [ 2096.476836] [c00f0fa0fa90] [c02ec234] chrdev_open+0x114/0x270
  [ 2096.476841] [c00f0fa0faf0] [c02e1480] 
do_dentry_open+0x2c0/0x460
  [ 2096.476846] [c00f0fa0fb50] [c02f9aa8] do_last+0x178/0xff0
  [ 2096.476851] [c00f0fa0fc10] [c02fab3c] path_openat+0xcc/0x3c0
  [ 2096.476857] [c00f0fa0fc90] [c02fca5c] do_filp_open+0xfc/0x170
  [ 2096.476861] [c00f0fa0fdb0] [c02e3270] do_sys_open+0x1c0/0x3b0
  [ 2096.476867] [c00f0fa0fe30] [c0009204] system_call+0x38/0xb4
  [ 2096.476870] Instruction dump:
  [ 2096.476873] fbe1fff8 f8010010 f821ffc1 7c7f1b78 6000 

[Kernel-packages] [Bug 1708931] Re: Bluetooth service disconnects mouse after few minutes in Ubuntu Budgie 17.04

[Justas Malinauskas]

Does Ubuntu Budgie has TLP preinstalled? Thats would explain everything.

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

Title:
  Bluetooth service disconnects mouse after few minutes in Ubuntu Budgie
  17.04

Status in bluez package in Ubuntu:
  New

Bug description:
  It happens at every reset, after using bluetooth mouse for a few
  minutes.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: bluez 5.43-0ubuntu1 [modified: lib/systemd/system/bluetooth.service]
  ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sun Aug  6 16:42:56 2017
  InstallationDate: Installed on 2017-08-05 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80E5
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-30-generic 
root=UUID=0585caf9-68a0-4a81-ba3d-c030affa951e ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0CN97WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo G50-80
  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 G50-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0CN97WW:bd01/08/2016:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoG50-80:
  dmi.product.name: 80E5
  dmi.product.version: Lenovo G50-80
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: B4:6D:83:B1:A7:87  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING 
RX bytes:301634 acl:15117 sco:0 events:1578 errors:0
TX bytes:2425 acl:31 sco:0 commands:169 errors:0

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

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

[Kernel-packages] [Bug 1711401] Re: accessing /dev/hvc1 with stress-ng on Ubuntu xenial causes crash

[Colin Ian King]

Fix is upstream commit:

>From bbc3dfe8805de86874b1a1b1429a002e8670043e Mon Sep 17 00:00:00 2001
From: Sam Mendoza-Jonas 
Date: Mon, 11 Jul 2016 13:38:57 +1000
Subject: [PATCH] tty/hvc: Use IRQF_SHARED for OPAL hvc consoles

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

Title:
  accessing /dev/hvc1 with stress-ng on Ubuntu xenial causes crash

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [SRU REQUEST][XENIAL]

  When running stress-ng --dev stressor accessing /dev/hvc1 causes the
  stressor to lock up and never terminal.

  [FIX]
  Upstream commmit:From bbc3dfe8805de86874b1a1b1429a002e8670043e Mon Sep 17 
00:00:00 2001
  From: Sam Mendoza-Jonas 
  Date: Mon, 11 Jul 2016 13:38:57 +1000
  Subject: [PATCH] tty/hvc: Use IRQF_SHARED for OPAL hvc consoles

  [TESTING]
  Without the fix, stress-ng --dev run as root hangs, and one gets an irq 
failed error and an oops:

  [ 2096.476610] hvc_open: request_irq failed with rc -16.
  [ 2096.476634] Unable to handle kernel paging request for data at address 
0x00a8
  [ 2096.476641] Faulting instruction address: 0xc0b0d8a4
  [ 2096.476647] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 2096.476650] SMP NR_CPUS=2048 NUMA PowerNV

  With the fix, the stressor runs w/o any issues

  [REGRESSION POTENTIAL]
  This is specific to one driver for ppc64el, so the risk potential is limited. 
The fix has limited regression potential as it essentially marks a flag to 
allow interrupt to be shared and fundamentally this is a very minor change to  
the interrupt handling functionality in the driver.

  ---

  stress-ng run as root, --dev stressor, accessing /dev/hvc1:

  [ 2096.476610] hvc_open: request_irq failed with rc -16.
  [ 2096.476634] Unable to handle kernel paging request for data at address 
0x00a8
  [ 2096.476641] Faulting instruction address: 0xc0b0d8a4
  [ 2096.476647] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 2096.476650] SMP NR_CPUS=2048 NUMA PowerNV
  [ 2096.476657] Modules linked in: kvm_hv kvm_pr kvm cuse userio hci_vhci 
bluetooth uhid hid vhost_net vhost macvtap macvlan snd_seq snd_seq_device 
snd_timer snd soundcore ipmi_powernv ipmi_msghandler vmx_crypto leds_powernv 
uio_pdrv_genirq uio powernv_rng ibmpowernv ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr 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 dm_round_robin ses 
enclosure ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath
  [ 2096.476718] CPU: 74 PID: 23074 Comm: stress-ng-dev Not tainted 
4.4.0-92-generic #115-Ubuntu
  [ 2096.476724] task: c00fe8499030 ti: c00f0fa0c000 task.ti: 
c00f0fa0c000
  [ 2096.476728] NIP: c0b0d8a4 LR: c069648c CTR: 
c0696450
  [ 2096.476732] REGS: c00f0fa0f6b0 TRAP: 0300   Not tainted  
(4.4.0-92-generic)
  [ 2096.476736] MSR: 90009033   CR: 2248  
XER: 
  [ 2096.476749] CFAR: c0008468 DAR: 00a8 DSISR: 4000 
SOFTE: 0
     GPR00: c069648c c00f0fa0f930 c15f8000 
00a8
     GPR04: c00ff0082400 0002 001ffe7d 
0036
     GPR08: c3236b90  804a 
c01e4e568880
     GPR12: c0696450 cfb6bf00 000f 
010023d22660
     GPR16: 3fff9ca5 0080 c01e43dde100 
c00fe459c800
     GPR20:  0001 0e51 
00010004
     GPR24: 00010800  f000 
c1892448
     GPR28: c00fef98da28 c00fe459c800 0001 
00a8
  [ 2096.476805] NIP [c0b0d8a4] _raw_spin_lock_irqsave+0x44/0x130
  [ 2096.476812] LR [c069648c] hvc_open+0x3c/0x1a0
  [ 2096.476815] Call Trace:
  [ 2096.476818] [c00f0fa0f930] [c00f0fa0f970] 0xc00f0fa0f970 
(unreliable)
  [ 2096.476824] [c00f0fa0f970] [c069648c] hvc_open+0x3c/0x1a0
  [ 2096.476829] [c00f0fa0f9f0] [c066c514] tty_open+0x194/0x7c0
  [ 2096.476836] [c00f0fa0fa90] [c02ec234] chrdev_open+0x114/0x270
  [ 2096.476841] [c00f0fa0faf0] [c02e1480] 
do_dentry_open+0x2c0/0x460
  [ 2096.476846] [c00f0fa0fb50] [c02f9aa8] do_last+0x178/0xff0
  [ 2096.476851] [c00f0fa0fc10] [c02fab3c] path_openat+0xcc/0x3c0
  [ 2096.476857] [c00f0fa0fc90] [c02fca5c] do_filp_open+0xfc/0x170
  [ 2096.476861] [c00f0fa0fdb0] [c02e3270] do_sys_open+0x1c0/0x3b0
  [ 2096.476867] [c00f0fa0fe30] [c0009204] 

[Kernel-packages] [Bug 1711401] Re: accessing /dev/hvc1 with stress-ng on Ubuntu xenial causes crash

[Colin Ian King]

Fix only required in Xenial, issue does not occur in Zesty upwards.

** Description changed:

+ [SRU REQUEST][XENIAL]
+ 
+ When running stress-ng --dev stressor accessing /dev/hvc1 causes the
+ stressor to lock up and never terminal.
+ 
+ [FIX]
+ Upstream commmit:From bbc3dfe8805de86874b1a1b1429a002e8670043e Mon Sep 17 
00:00:00 2001
+ From: Sam Mendoza-Jonas 
+ Date: Mon, 11 Jul 2016 13:38:57 +1000
+ Subject: [PATCH] tty/hvc: Use IRQF_SHARED for OPAL hvc consoles
+ 
+ [TESTING]
+ Without the fix, stress-ng --dev run as root hangs, and one gets an irq 
failed error and an oops:
+ 
+ [ 2096.476610] hvc_open: request_irq failed with rc -16.
+ [ 2096.476634] Unable to handle kernel paging request for data at address 
0x00a8
+ [ 2096.476641] Faulting instruction address: 0xc0b0d8a4
+ [ 2096.476647] Oops: Kernel access of bad area, sig: 11 [#1]
+ [ 2096.476650] SMP NR_CPUS=2048 NUMA PowerNV
+ 
+ With the fix, the stressor runs w/o any issues
+ 
+ [REGRESSION POTENTIAL]
+ This is specific to one driver for ppc64el, so the risk potential is limited. 
The fix has limited regression potential as it essentially marks a flag to 
allow interrupt to be shared and fundamentally this is a very minor change to  
the interrupt handling functionality in the driver.
+ 
+ ---
+ 
  stress-ng run as root, --dev stressor, accessing /dev/hvc1:
  
  [ 2096.476610] hvc_open: request_irq failed with rc -16.
  [ 2096.476634] Unable to handle kernel paging request for data at address 
0x00a8
  [ 2096.476641] Faulting instruction address: 0xc0b0d8a4
  [ 2096.476647] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 2096.476650] SMP NR_CPUS=2048 NUMA PowerNV
  [ 2096.476657] Modules linked in: kvm_hv kvm_pr kvm cuse userio hci_vhci 
bluetooth uhid hid vhost_net vhost macvtap macvlan snd_seq snd_seq_device 
snd_timer snd soundcore ipmi_powernv ipmi_msghandler vmx_crypto leds_powernv 
uio_pdrv_genirq uio powernv_rng ibmpowernv ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr 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 dm_round_robin ses 
enclosure ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath
  [ 2096.476718] CPU: 74 PID: 23074 Comm: stress-ng-dev Not tainted 
4.4.0-92-generic #115-Ubuntu
  [ 2096.476724] task: c00fe8499030 ti: c00f0fa0c000 task.ti: 
c00f0fa0c000
  [ 2096.476728] NIP: c0b0d8a4 LR: c069648c CTR: 
c0696450
  [ 2096.476732] REGS: c00f0fa0f6b0 TRAP: 0300   Not tainted  
(4.4.0-92-generic)
  [ 2096.476736] MSR: 90009033   CR: 2248  
XER: 
- [ 2096.476749] CFAR: c0008468 DAR: 00a8 DSISR: 4000 
SOFTE: 0 
-GPR00: c069648c c00f0fa0f930 c15f8000 
00a8 
-GPR04: c00ff0082400 0002 001ffe7d 
0036 
-GPR08: c3236b90  804a 
c01e4e568880 
-GPR12: c0696450 cfb6bf00 000f 
010023d22660 
-GPR16: 3fff9ca5 0080 c01e43dde100 
c00fe459c800 
-GPR20:  0001 0e51 
00010004 
-GPR24: 00010800  f000 
c1892448 
-GPR28: c00fef98da28 c00fe459c800 0001 
00a8 
+ [ 2096.476749] CFAR: c0008468 DAR: 00a8 DSISR: 4000 
SOFTE: 0
+    GPR00: c069648c c00f0fa0f930 c15f8000 
00a8
+    GPR04: c00ff0082400 0002 001ffe7d 
0036
+    GPR08: c3236b90  804a 
c01e4e568880
+    GPR12: c0696450 cfb6bf00 000f 
010023d22660
+    GPR16: 3fff9ca5 0080 c01e43dde100 
c00fe459c800
+    GPR20:  0001 0e51 
00010004
+    GPR24: 00010800  f000 
c1892448
+    GPR28: c00fef98da28 c00fe459c800 0001 
00a8
  [ 2096.476805] NIP [c0b0d8a4] _raw_spin_lock_irqsave+0x44/0x130
  [ 2096.476812] LR [c069648c] hvc_open+0x3c/0x1a0
  [ 2096.476815] Call Trace:
  [ 2096.476818] [c00f0fa0f930] [c00f0fa0f970] 0xc00f0fa0f970 
(unreliable)
  [ 2096.476824] [c00f0fa0f970] [c069648c] hvc_open+0x3c/0x1a0
  [ 2096.476829] [c00f0fa0f9f0] [c066c514] tty_open+0x194/0x7c0
  [ 2096.476836] [c00f0fa0fa90] [c02ec234] chrdev_open+0x114/0x270
  [ 2096.476841] [c00f0fa0faf0] [c02e1480] 

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

[bugproxy]

--- Comment From dougm...@us.ibm.com 2017-08-18 07:51 EDT---
Test results with the binary kernel package show the same symptoms, I/Os 
getting delayed longer than 10 minutes. It seems that those three patches 
together cause a regression of the "cfq-iosched: fix the delay of cfq_group's 
vdisktime under iops mode" patch.

So, in summary, with *only* the patch:

5be6b75610cefd1e21b98a218211922c2feb6e08  "cfq-iosched: fix the delay of 
cfq_group's vdisktime under
iops mode"

I see some improvement of the I/Os delays, although the delays are still
too long. But by adding these two patches:

4d608baac5f4e72b033a122b2d6d9499532c3afc  "block: Initialize cfqq->ioprio_class 
in cfq_get_queue()"
142bbdfccc8b3e9f7342f2ce8422e76a3b45beae  "cfq: Disable writeback throttling by 
default"

I see a regression of the delays back to what I was seeing without any
patches.

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

Title:
  Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to
  adapter for a very long time.

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:
  ---Problem Description---
  When running stress test, sometimes seeing IO hung in dmesg or seeing "Host 
adapter abort request" error.

  ---Steps to Reproduce---
   There are two ways to re-create the issues:
  (1)running HTX, you will see IO timeout backtrace in dmesg in several hours
  (2)running some IO test, then reboot system, repeat this two steps, it takes 
long time to re-create the issue.
   
  ---uname output---
  4.10.0-11-generic

  The bulk of the effort for this issue is currently being worked in
  MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.

  Ran an interesting test: Ran HTX until I started getting the "stall"
  messages on the console, then shutdown HTX and examined the I/O
  counters for the tested disks in sysfs:

  root@bostonp15:~# for i in 
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
 do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
  0:2:2:0 0x5eba3d 0x5eba3d
  0:2:3:0 0x773cc9 0x773cc9
  0:2:4:0 0x782c61 0x782c61
  0:2:5:0 0x5ca134 0x5ca134
  root@bostonp15:~#

  So, none of the disks showed any evidence of having lost an I/O. I
  then restarted HTX and aside from having to manually restart one of
  the disks, see no problems with the testing. It appears that what was
  "hung" was purely in userland.

  This does not absolve the kernel or aacraid driver from blame, but it
  shows that the OS "believes" that it completed the I/O and thus
  removed it from the queue. What we don't know is whether the OS truly
  notified HTX about the completion, or if HTX (or userland libraries)
  just failed to process the notification.

  Tests are running again, will see what happens next.

  Update from JIRA:

  I have run some more experiments. Not sure what it tells us, but
  here's what I've seen.

  First test, ran until I got kernel messages about stalled tasks, then
  shutdown HTX. After HTX was down, I checked the above mentioned
  counters and found that on each disk iorequest_cnt matched iodone_cnt.
  The disks were usable and I could restart HTX. This suggests that the
  problem is not in the PM8069 firmware, and makes the case for the
  aacraid driver having a bug somewhat weaker. However, this merely says
  that the driver "completed" the I/O as far as the kernel is concerned,
  not that a completion rippled back to the application.

  I restarted HTX and have run until errors. This time, I am leaving HTX
  running and observing. Two of the disks reached the HTX error
  threshold and the testers stopped (those 2 disks are now idle).
  Another disks saw errors but then stopped and appears to be running
  fine now. The last disk has not seen any errors (yet). On the two idle
  (errored-out) disks I see  iorequest_cnt matches iodone_cnt. I am able
  to "terminate and restart" the two idle disks and HTX appears to be
  testing them again "normally". Note that no reboot was required,
  further supporting the evidence that, as far as the kernel is
  concerned, there is nothing wrong with the disks and their I/O paths.

  So, I don't believe this completely eliminates aacraid from the
  picture, especially given we don't see this behavior on other
  systems/drivers. But, it probably moves the focus of the investigation
  away form the adapter firmware.

  Tried build upstream 4.11 kernel on Ubuntu. This still gets the hangs.
  Both Ubuntu 4.10 and upstream 4.11 have aacraid driver
  1.2.1[50792]-custom.

  Good new/bad news... While doing an initial evaluation of the LSI-3008
  SAS HBA on Boston and Ubuntu 17.04, I am hitting this same problem.
  So, it appears to have nothing specific to do with the PM8069 

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

[bugproxy]

--- Comment From martin.schwidef...@de.ibm.com 2017-08-18 07:31 EDT---
@Canonical can you please build another test kernel which includes the three 
new patches?

The patches are against kernel version 4.4.0-89.112.

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

Title:
  kernel panic -not syncing: Fatal exception: panic_on_oops

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

Bug description:
  == Comment: #0 - QI YE  - 2017-08-02 04:11:25 ==
  ---Problem Description---
  Ubuntu got kernel panic

  ---uname output---
  #110-Ubuntu SMP Tue Jul 18 12:56:43 UTC 2017 s390x s390x s390x GNU/Linux
   
  ---Debugger Data---
  PID: 10991  TASK: 19872a0e8 CPU: 2   COMMAND: "hyperkube"
   LOWCORE INFO:
-psw  : 0x0004c0018000 0x00115fa6
-function : pcpu_delegate at 115fa6
-prefix   : 0x7fe42000
-cpu timer: 0x7ffab2827828aa50
-clock cmp: 0xd2eb8b31445e4200
-general registers:
   0x0004e001 0x001283b6
   0xc001 0x8380fcb8
   0x00115f9e 0x0056f6e2
   0x0004 0x00cf9070
   0x0001f3bfc000 0x00112fd8
   0x0001c72bb400 0x0002
   0x7fffc000 0x007c9ef0
   0x00115f9e 0x8380fc18
-access registers:
   0x03ff 0x7910 00 00
   00 00 00 00
   00 00 00 00
   00 00 00 00
-control registers:
   0x14066a12 0x7e6d81c7
   0x00011140 00
   0x2aef 0x0400
   0x5000 0x7e6d81c7
   00 00
   00 00
   00 0x00cfc007
   0xdb00 0x00011280
-floating point registers:
   0x409c7e258000 0x401de4e0
   00 0x3fd24407ab0e073a
   0x3ff0 0x3fee
   0x3fef218f8a7a41a0 0x3fee
   0x0080 00
   0x03ff7f80 0x02aa4940e9e0
   0xd401 0x03ffe81fe110
   00 0x03fff2cfe638

   #0 [8380fc78] smp_find_processor_id at 1160f8
   #1 [8380fc90] machine_kexec at 1135d4
   #2 [8380fcb8] crash_kexec at 1fbb8a
   #3 [8380fd88] panic at 27d0e0
   #4 [8380fe28] die at 1142cc
   #5 [8380fe90] do_low_address at 12215e
   #6 [8380fea8] pgm_check_handler at 7c2ab4
   PSW:  070520018000 02aa267e0e42 (user space)
   GPRS:   02aa2c4fd690 0001
 02aa2c4fd690 03ff7fffee38  0002
 00029c0f 00c42001ea00 0001 0001
 00c42001c5c8 00c42082c1a0 02aa2666325e 03ff7fffed90 
   
  Contact Information = Chee Ye / y...@cn.ibm.com 
   
  Stack trace output:
   no
   
  Oops output:
   [43200.761465] docker0: port 10(vethb9132e9) entered forwarding state
  [50008.560926] hrtimer: interrupt took 1698076 ns
  [123483.768984] systemd[1]: apt-daily.timer: Adding 7h 34min 22.582204s 
random time.
  [123483.930058] systemd[1]: apt-daily.timer: Adding 2h 18min 14.857162s 
random time.
  [123484.064879] systemd[1]: apt-daily.timer: Adding 10h 46min 2.301756s 
random time.
  [123484.824760] systemd[1]: apt-daily.timer: Adding 6h 16min 22.178655s 
random time.
  [153113.703126] conntrack: generic helper won't handle protocol 47. Please 
consider loading the specific helper module.
  [477085.704538] Low-address protection: 0004 ilc:2 [#1] SMP
  [477085.704551] Modules linked in: xt_physdev veth xt_recent xt_comment 
xt_mark xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 xt_addrtype nf_nat br_netfilter bridge stp llc aufs 
ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 
xt_conntrack nf_conntrack iptable_filter ip_tables x_tables ghash_s390 prng 
aes_s390 des_s390 des_generic sha512_s390 qeth_l2 sha256_s390 qeth sha1_s390 
qdio sha_common ccwgroup vmur dasd_eckd_mod dasd_mod
  [477085.705522] CPU: 2 PID: 10991 Comm: hyperkube Not tainted 
4.4.0-87-generic #110-Ubuntu
  [477085.705525] task: 00019872a0e8 ti: 8380c000 task.ti: 
8380c000
  [477085.705529] User PSW : 070520018000 02aa267e0e42
  [477085.705532]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
EA:3
  User GPRS:   02aa2c4fd690 
0001
  [477085.705539]02aa2c4fd690 03ff7fffee38  
0002
  [477085.705553]00029c0f 

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

[Po-Hsu Lin]

3.13.0-129.178~precise1 - generic
Regression test CMPL.
http://kernel.ubuntu.com/testing/tracker-index.html

Issue to note in amd64:
  aio_dio_bugs - aio-cve-2016-10044 failed, expected result

Issue to note in i386:
  aio_dio_bugs - aio-cve-2016-10044 failed, expected result

ARM64 / ppc64el cannot be tested, no Precise image on MaaS.

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

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

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

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

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

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

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

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

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

[bugproxy]

--- Comment From martin.schwidef...@de.ibm.com 2017-08-18 07:05 EDT---
I have added three patches to replace the test patch that Heiko already
marked as invalid:

0001-s390-mm-no-local-TLB-flush-for-clearing-by-ASCE-IDTE.patch
0002-s390-mm-fix-local-TLB-flushing-vs.-detach-of-an-mm-a.patch
0003-s390-mm-fix-race-on-mm-context.flush_mm.patch

The first is an upstream patch which removes the code that tries to
use the local flushing option on an IDTE clearing-by-ASCE instruction.
The local flushing option only exists for IDTE invalidation-and-clearing.

Patches #2 and #3 fix race conditions in the architecture specific TLB
flushing code. I have run my TLB stress tests on a z/VM guest with 4 CPUs
for a few hours with the three patches applied. Nothing undue happened,
but my TLB stress did run without these patches as well. Seems like
we need the specific timing of the workload to trigger the problem.

Now, if you could run a test for us with these patches applied and the bug
does not show up again, I would declare these patches as final solution.

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

Title:
  kernel panic -not syncing: Fatal exception: panic_on_oops

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

Bug description:
  == Comment: #0 - QI YE  - 2017-08-02 04:11:25 ==
  ---Problem Description---
  Ubuntu got kernel panic

  ---uname output---
  #110-Ubuntu SMP Tue Jul 18 12:56:43 UTC 2017 s390x s390x s390x GNU/Linux
   
  ---Debugger Data---
  PID: 10991  TASK: 19872a0e8 CPU: 2   COMMAND: "hyperkube"
   LOWCORE INFO:
-psw  : 0x0004c0018000 0x00115fa6
-function : pcpu_delegate at 115fa6
-prefix   : 0x7fe42000
-cpu timer: 0x7ffab2827828aa50
-clock cmp: 0xd2eb8b31445e4200
-general registers:
   0x0004e001 0x001283b6
   0xc001 0x8380fcb8
   0x00115f9e 0x0056f6e2
   0x0004 0x00cf9070
   0x0001f3bfc000 0x00112fd8
   0x0001c72bb400 0x0002
   0x7fffc000 0x007c9ef0
   0x00115f9e 0x8380fc18
-access registers:
   0x03ff 0x7910 00 00
   00 00 00 00
   00 00 00 00
   00 00 00 00
-control registers:
   0x14066a12 0x7e6d81c7
   0x00011140 00
   0x2aef 0x0400
   0x5000 0x7e6d81c7
   00 00
   00 00
   00 0x00cfc007
   0xdb00 0x00011280
-floating point registers:
   0x409c7e258000 0x401de4e0
   00 0x3fd24407ab0e073a
   0x3ff0 0x3fee
   0x3fef218f8a7a41a0 0x3fee
   0x0080 00
   0x03ff7f80 0x02aa4940e9e0
   0xd401 0x03ffe81fe110
   00 0x03fff2cfe638

   #0 [8380fc78] smp_find_processor_id at 1160f8
   #1 [8380fc90] machine_kexec at 1135d4
   #2 [8380fcb8] crash_kexec at 1fbb8a
   #3 [8380fd88] panic at 27d0e0
   #4 [8380fe28] die at 1142cc
   #5 [8380fe90] do_low_address at 12215e
   #6 [8380fea8] pgm_check_handler at 7c2ab4
   PSW:  070520018000 02aa267e0e42 (user space)
   GPRS:   02aa2c4fd690 0001
 02aa2c4fd690 03ff7fffee38  0002
 00029c0f 00c42001ea00 0001 0001
 00c42001c5c8 00c42082c1a0 02aa2666325e 03ff7fffed90 
   
  Contact Information = Chee Ye / y...@cn.ibm.com 
   
  Stack trace output:
   no
   
  Oops output:
   [43200.761465] docker0: port 10(vethb9132e9) entered forwarding state
  [50008.560926] hrtimer: interrupt took 1698076 ns
  [123483.768984] systemd[1]: apt-daily.timer: Adding 7h 34min 22.582204s 
random time.
  [123483.930058] systemd[1]: apt-daily.timer: Adding 2h 18min 14.857162s 
random time.
  [123484.064879] systemd[1]: apt-daily.timer: Adding 10h 46min 2.301756s 
random time.
  [123484.824760] systemd[1]: apt-daily.timer: Adding 6h 16min 22.178655s 
random time.
  [153113.703126] conntrack: generic helper won't handle protocol 47. Please 
consider loading the specific helper module.
  [477085.704538] Low-address protection: 0004 ilc:2 [#1] SMP
  [477085.704551] Modules linked in: xt_physdev veth xt_recent xt_comment 
xt_mark xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 xt_addrtype nf_nat br_netfilter bridge stp llc aufs 
ipt_REJECT 

[Kernel-packages] [Bug 1711571] Re: linux: 4.12.0-12.13 -proposed tracker

[Brad Figg]

** Changed in: kernel-development-workflow/prepare-package-signed
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Andy Whitcroft 
(apw)

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

Title:
  linux: 4.12.0-12.13 -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:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Committed
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 Artful:
  Confirmed

Bug description:
  This bug is for tracking the 4.12.0-12.13 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:Uploaded
  kernel-phase-changed:Friday, 18. August 2017 10:41 UTC

  -- swm properties --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1708399] Fix race on mm->context.flush_mm

[bugproxy]

--- Comment (attachment only) From martin.schwidef...@de.ibm.com 2017-08-18 
06:52 EDT---


** Attachment added: "Fix race on mm->context.flush_mm"
   
https://bugs.launchpad.net/bugs/1708399/+attachment/4934705/+files/0003-s390-mm-fix-race-on-mm-context.flush_mm.patch

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

Title:
  kernel panic -not syncing: Fatal exception: panic_on_oops

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

Bug description:
  == Comment: #0 - QI YE  - 2017-08-02 04:11:25 ==
  ---Problem Description---
  Ubuntu got kernel panic

  ---uname output---
  #110-Ubuntu SMP Tue Jul 18 12:56:43 UTC 2017 s390x s390x s390x GNU/Linux
   
  ---Debugger Data---
  PID: 10991  TASK: 19872a0e8 CPU: 2   COMMAND: "hyperkube"
   LOWCORE INFO:
-psw  : 0x0004c0018000 0x00115fa6
-function : pcpu_delegate at 115fa6
-prefix   : 0x7fe42000
-cpu timer: 0x7ffab2827828aa50
-clock cmp: 0xd2eb8b31445e4200
-general registers:
   0x0004e001 0x001283b6
   0xc001 0x8380fcb8
   0x00115f9e 0x0056f6e2
   0x0004 0x00cf9070
   0x0001f3bfc000 0x00112fd8
   0x0001c72bb400 0x0002
   0x7fffc000 0x007c9ef0
   0x00115f9e 0x8380fc18
-access registers:
   0x03ff 0x7910 00 00
   00 00 00 00
   00 00 00 00
   00 00 00 00
-control registers:
   0x14066a12 0x7e6d81c7
   0x00011140 00
   0x2aef 0x0400
   0x5000 0x7e6d81c7
   00 00
   00 00
   00 0x00cfc007
   0xdb00 0x00011280
-floating point registers:
   0x409c7e258000 0x401de4e0
   00 0x3fd24407ab0e073a
   0x3ff0 0x3fee
   0x3fef218f8a7a41a0 0x3fee
   0x0080 00
   0x03ff7f80 0x02aa4940e9e0
   0xd401 0x03ffe81fe110
   00 0x03fff2cfe638

   #0 [8380fc78] smp_find_processor_id at 1160f8
   #1 [8380fc90] machine_kexec at 1135d4
   #2 [8380fcb8] crash_kexec at 1fbb8a
   #3 [8380fd88] panic at 27d0e0
   #4 [8380fe28] die at 1142cc
   #5 [8380fe90] do_low_address at 12215e
   #6 [8380fea8] pgm_check_handler at 7c2ab4
   PSW:  070520018000 02aa267e0e42 (user space)
   GPRS:   02aa2c4fd690 0001
 02aa2c4fd690 03ff7fffee38  0002
 00029c0f 00c42001ea00 0001 0001
 00c42001c5c8 00c42082c1a0 02aa2666325e 03ff7fffed90 
   
  Contact Information = Chee Ye / y...@cn.ibm.com 
   
  Stack trace output:
   no
   
  Oops output:
   [43200.761465] docker0: port 10(vethb9132e9) entered forwarding state
  [50008.560926] hrtimer: interrupt took 1698076 ns
  [123483.768984] systemd[1]: apt-daily.timer: Adding 7h 34min 22.582204s 
random time.
  [123483.930058] systemd[1]: apt-daily.timer: Adding 2h 18min 14.857162s 
random time.
  [123484.064879] systemd[1]: apt-daily.timer: Adding 10h 46min 2.301756s 
random time.
  [123484.824760] systemd[1]: apt-daily.timer: Adding 6h 16min 22.178655s 
random time.
  [153113.703126] conntrack: generic helper won't handle protocol 47. Please 
consider loading the specific helper module.
  [477085.704538] Low-address protection: 0004 ilc:2 [#1] SMP
  [477085.704551] Modules linked in: xt_physdev veth xt_recent xt_comment 
xt_mark xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 xt_addrtype nf_nat br_netfilter bridge stp llc aufs 
ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 
xt_conntrack nf_conntrack iptable_filter ip_tables x_tables ghash_s390 prng 
aes_s390 des_s390 des_generic sha512_s390 qeth_l2 sha256_s390 qeth sha1_s390 
qdio sha_common ccwgroup vmur dasd_eckd_mod dasd_mod
  [477085.705522] CPU: 2 PID: 10991 Comm: hyperkube Not tainted 
4.4.0-87-generic #110-Ubuntu
  [477085.705525] task: 00019872a0e8 ti: 8380c000 task.ti: 
8380c000
  [477085.705529] User PSW : 070520018000 02aa267e0e42
  [477085.705532]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
EA:3
  User GPRS:   02aa2c4fd690 
0001
  [477085.705539]02aa2c4fd690 03ff7fffee38  
0002
  

[Kernel-packages] [Bug 1708399] Fix race local TLB flushing vs. context switch

[bugproxy]

--- Comment (attachment only) From martin.schwidef...@de.ibm.com 2017-08-18 
06:51 EDT---


** Attachment added: "Fix race local TLB flushing vs. context switch"
   
https://bugs.launchpad.net/bugs/1708399/+attachment/4934704/+files/0002-s390-mm-fix-local-TLB-flushing-vs.-detach-of-an-mm-a.patch

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

Title:
  kernel panic -not syncing: Fatal exception: panic_on_oops

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

Bug description:
  == Comment: #0 - QI YE  - 2017-08-02 04:11:25 ==
  ---Problem Description---
  Ubuntu got kernel panic

  ---uname output---
  #110-Ubuntu SMP Tue Jul 18 12:56:43 UTC 2017 s390x s390x s390x GNU/Linux
   
  ---Debugger Data---
  PID: 10991  TASK: 19872a0e8 CPU: 2   COMMAND: "hyperkube"
   LOWCORE INFO:
-psw  : 0x0004c0018000 0x00115fa6
-function : pcpu_delegate at 115fa6
-prefix   : 0x7fe42000
-cpu timer: 0x7ffab2827828aa50
-clock cmp: 0xd2eb8b31445e4200
-general registers:
   0x0004e001 0x001283b6
   0xc001 0x8380fcb8
   0x00115f9e 0x0056f6e2
   0x0004 0x00cf9070
   0x0001f3bfc000 0x00112fd8
   0x0001c72bb400 0x0002
   0x7fffc000 0x007c9ef0
   0x00115f9e 0x8380fc18
-access registers:
   0x03ff 0x7910 00 00
   00 00 00 00
   00 00 00 00
   00 00 00 00
-control registers:
   0x14066a12 0x7e6d81c7
   0x00011140 00
   0x2aef 0x0400
   0x5000 0x7e6d81c7
   00 00
   00 00
   00 0x00cfc007
   0xdb00 0x00011280
-floating point registers:
   0x409c7e258000 0x401de4e0
   00 0x3fd24407ab0e073a
   0x3ff0 0x3fee
   0x3fef218f8a7a41a0 0x3fee
   0x0080 00
   0x03ff7f80 0x02aa4940e9e0
   0xd401 0x03ffe81fe110
   00 0x03fff2cfe638

   #0 [8380fc78] smp_find_processor_id at 1160f8
   #1 [8380fc90] machine_kexec at 1135d4
   #2 [8380fcb8] crash_kexec at 1fbb8a
   #3 [8380fd88] panic at 27d0e0
   #4 [8380fe28] die at 1142cc
   #5 [8380fe90] do_low_address at 12215e
   #6 [8380fea8] pgm_check_handler at 7c2ab4
   PSW:  070520018000 02aa267e0e42 (user space)
   GPRS:   02aa2c4fd690 0001
 02aa2c4fd690 03ff7fffee38  0002
 00029c0f 00c42001ea00 0001 0001
 00c42001c5c8 00c42082c1a0 02aa2666325e 03ff7fffed90 
   
  Contact Information = Chee Ye / y...@cn.ibm.com 
   
  Stack trace output:
   no
   
  Oops output:
   [43200.761465] docker0: port 10(vethb9132e9) entered forwarding state
  [50008.560926] hrtimer: interrupt took 1698076 ns
  [123483.768984] systemd[1]: apt-daily.timer: Adding 7h 34min 22.582204s 
random time.
  [123483.930058] systemd[1]: apt-daily.timer: Adding 2h 18min 14.857162s 
random time.
  [123484.064879] systemd[1]: apt-daily.timer: Adding 10h 46min 2.301756s 
random time.
  [123484.824760] systemd[1]: apt-daily.timer: Adding 6h 16min 22.178655s 
random time.
  [153113.703126] conntrack: generic helper won't handle protocol 47. Please 
consider loading the specific helper module.
  [477085.704538] Low-address protection: 0004 ilc:2 [#1] SMP
  [477085.704551] Modules linked in: xt_physdev veth xt_recent xt_comment 
xt_mark xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 xt_addrtype nf_nat br_netfilter bridge stp llc aufs 
ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 
xt_conntrack nf_conntrack iptable_filter ip_tables x_tables ghash_s390 prng 
aes_s390 des_s390 des_generic sha512_s390 qeth_l2 sha256_s390 qeth sha1_s390 
qdio sha_common ccwgroup vmur dasd_eckd_mod dasd_mod
  [477085.705522] CPU: 2 PID: 10991 Comm: hyperkube Not tainted 
4.4.0-87-generic #110-Ubuntu
  [477085.705525] task: 00019872a0e8 ti: 8380c000 task.ti: 
8380c000
  [477085.705529] User PSW : 070520018000 02aa267e0e42
  [477085.705532]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
EA:3
  User GPRS:   02aa2c4fd690 
0001
  [477085.705539]02aa2c4fd690 03ff7fffee38 

[Kernel-packages] [Bug 1708399] Upstream patch that removes local flushing for clearing-by-ASCE

[bugproxy]

--- Comment (attachment only) From martin.schwidef...@de.ibm.com 2017-08-18 
06:50 EDT---


** Attachment added: "Upstream patch that removes local flushing for 
clearing-by-ASCE"
   
https://bugs.launchpad.net/bugs/1708399/+attachment/4934703/+files/0001-s390-mm-no-local-TLB-flush-for-clearing-by-ASCE-IDTE.patch

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

Title:
  kernel panic -not syncing: Fatal exception: panic_on_oops

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

Bug description:
  == Comment: #0 - QI YE  - 2017-08-02 04:11:25 ==
  ---Problem Description---
  Ubuntu got kernel panic

  ---uname output---
  #110-Ubuntu SMP Tue Jul 18 12:56:43 UTC 2017 s390x s390x s390x GNU/Linux
   
  ---Debugger Data---
  PID: 10991  TASK: 19872a0e8 CPU: 2   COMMAND: "hyperkube"
   LOWCORE INFO:
-psw  : 0x0004c0018000 0x00115fa6
-function : pcpu_delegate at 115fa6
-prefix   : 0x7fe42000
-cpu timer: 0x7ffab2827828aa50
-clock cmp: 0xd2eb8b31445e4200
-general registers:
   0x0004e001 0x001283b6
   0xc001 0x8380fcb8
   0x00115f9e 0x0056f6e2
   0x0004 0x00cf9070
   0x0001f3bfc000 0x00112fd8
   0x0001c72bb400 0x0002
   0x7fffc000 0x007c9ef0
   0x00115f9e 0x8380fc18
-access registers:
   0x03ff 0x7910 00 00
   00 00 00 00
   00 00 00 00
   00 00 00 00
-control registers:
   0x14066a12 0x7e6d81c7
   0x00011140 00
   0x2aef 0x0400
   0x5000 0x7e6d81c7
   00 00
   00 00
   00 0x00cfc007
   0xdb00 0x00011280
-floating point registers:
   0x409c7e258000 0x401de4e0
   00 0x3fd24407ab0e073a
   0x3ff0 0x3fee
   0x3fef218f8a7a41a0 0x3fee
   0x0080 00
   0x03ff7f80 0x02aa4940e9e0
   0xd401 0x03ffe81fe110
   00 0x03fff2cfe638

   #0 [8380fc78] smp_find_processor_id at 1160f8
   #1 [8380fc90] machine_kexec at 1135d4
   #2 [8380fcb8] crash_kexec at 1fbb8a
   #3 [8380fd88] panic at 27d0e0
   #4 [8380fe28] die at 1142cc
   #5 [8380fe90] do_low_address at 12215e
   #6 [8380fea8] pgm_check_handler at 7c2ab4
   PSW:  070520018000 02aa267e0e42 (user space)
   GPRS:   02aa2c4fd690 0001
 02aa2c4fd690 03ff7fffee38  0002
 00029c0f 00c42001ea00 0001 0001
 00c42001c5c8 00c42082c1a0 02aa2666325e 03ff7fffed90 
   
  Contact Information = Chee Ye / y...@cn.ibm.com 
   
  Stack trace output:
   no
   
  Oops output:
   [43200.761465] docker0: port 10(vethb9132e9) entered forwarding state
  [50008.560926] hrtimer: interrupt took 1698076 ns
  [123483.768984] systemd[1]: apt-daily.timer: Adding 7h 34min 22.582204s 
random time.
  [123483.930058] systemd[1]: apt-daily.timer: Adding 2h 18min 14.857162s 
random time.
  [123484.064879] systemd[1]: apt-daily.timer: Adding 10h 46min 2.301756s 
random time.
  [123484.824760] systemd[1]: apt-daily.timer: Adding 6h 16min 22.178655s 
random time.
  [153113.703126] conntrack: generic helper won't handle protocol 47. Please 
consider loading the specific helper module.
  [477085.704538] Low-address protection: 0004 ilc:2 [#1] SMP
  [477085.704551] Modules linked in: xt_physdev veth xt_recent xt_comment 
xt_mark xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 xt_addrtype nf_nat br_netfilter bridge stp llc aufs 
ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 
xt_conntrack nf_conntrack iptable_filter ip_tables x_tables ghash_s390 prng 
aes_s390 des_s390 des_generic sha512_s390 qeth_l2 sha256_s390 qeth sha1_s390 
qdio sha_common ccwgroup vmur dasd_eckd_mod dasd_mod
  [477085.705522] CPU: 2 PID: 10991 Comm: hyperkube Not tainted 
4.4.0-87-generic #110-Ubuntu
  [477085.705525] task: 00019872a0e8 ti: 8380c000 task.ti: 
8380c000
  [477085.705529] User PSW : 070520018000 02aa267e0e42
  [477085.705532]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
EA:3
  User GPRS:   02aa2c4fd690 
0001
  [477085.705539]02aa2c4fd690 

[Kernel-packages] [Bug 1711535] Re: Xenial update to 4.4.82 stable release

[Stefan Bader]

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Stefan Bader (smb)

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

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

Title:
  Xenial update to 4.4.82 stable release

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

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.82 stable release shall be applied:
  * tcp: avoid setting cwnd to invalid ssthresh after cwnd reduction states
  * net: fix keepalive code vs TCP_FASTOPEN_CONNECT
  * bpf, s390: fix jit branch offset related to ldimm64
  * net: sched: set xt_tgchk_param par.nft_compat as 0 in ipt_init_target
  * tcp: fastopen: tcp_connect() must refresh the route
  * net: avoid skb_warn_bad_offload false positives on UFO
  * sparc64: Prevent perf from running during super critical sections
  * KVM: arm/arm64: Handle hva aging while destroying the vm
  * mm/mempool: avoid KASAN marking mempool poison checks as use-after-free
  * Linux 4.4.82

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

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

[Kernel-packages] [Bug 1711557] Re: Xenial update to 4.4.83 stable release

[Stefan Bader]

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Stefan Bader (smb)

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

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

Title:
  Xenial update to 4.4.83 stable release

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

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.83 stable release shall be applied:
  * cpuset: fix a deadlock due to incomplete patching of cpusets_enabled()
  * mm: ratelimit PFNs busy info message
  * iscsi-target: fix memory leak in iscsit_setup_text_cmd()
  * iscsi-target: Fix iscsi_np reset hung task during parallel delete
  * fuse: initialize the flock flag in fuse_file on allocation
  * nfs/flexfiles: fix leak of nfs4_ff_ds_version arrays
  * USB: serial: option: add D-Link DWM-222 device ID
  * USB: serial: cp210x: add support for Qivicon USB ZigBee dongle
  * USB: serial: pl2303: add new ATEN device id
  * usb: musb: fix tx fifo flush handling again
  * USB: hcd: Mark secondary HCD as dead if the primary one died
  * staging:iio:resolver:ad2s1210 fix negative IIO_ANGL_VEL read
  * iio: accel: bmc150: Always restore device to normal mode after
suspend-resume
  * iio: light: tsl2563: use correct event code
  * uas: Add US_FL_IGNORE_RESIDUE for Initio Corporation INIC-3069
  * USB: Check for dropped connection before switching to full speed
  * usb: core: unlink urbs from the tail of the endpoint's urb_list
  * usb: quirks: Add no-lpm quirk for Moshi USB to Ethernet Adapter
  * usb:xhci:Add quirk for Certain failing HP keyboard on reset after resume
  * iio: adc: vf610_adc: Fix VALT selection value for REFSEL bits
  * pnfs/blocklayout: require 64-bit sector_t
  * pinctrl: sunxi: add a missing function of A10/A20 pinctrl driver
  * pinctrl: samsung: Remove bogus irq_[un]mask from resource management
  * Linux 4.4.83

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

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

[Kernel-packages] [Bug 1711571] Re: linux: 4.12.0-12.13 -proposed tracker

[Brad Figg]

** Changed in: kernel-development-workflow/prepare-package
   Status: New => Confirmed

** Changed in: kernel-development-workflow/promote-to-proposed
   Status: New => Fix Committed

** Tags added: block-proposed-artful

** Tags added: block-proposed

** Changed in: kernel-development-workflow/prepare-package
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Andy Whitcroft 
(apw)

** Changed in: kernel-development-workflow/prepare-package-meta
   Status: New => Confirmed

** Changed in: kernel-development-workflow/prepare-package-signed
   Status: New => Confirmed

** Changed in: kernel-development-workflow/prepare-package-meta
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Andy Whitcroft 
(apw)

** Description changed:

  This bug is for tracking the 4.12.0-12.13 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:Uploaded
+ kernel-phase-changed:Friday, 18. August 2017 10:41 UTC

** Description changed:

  This bug is for tracking the 4.12.0-12.13 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:Uploaded
  kernel-phase-changed:Friday, 18. August 2017 10:41 UTC
+ 
+ -- 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/1711571

Title:
  linux: 4.12.0-12.13 -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:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Committed
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 Artful:
  Confirmed

Bug description:
  This bug is for tracking the 4.12.0-12.13 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:Uploaded
  kernel-phase-changed:Friday, 18. August 2017 10:41 UTC

  -- swm properties --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1711571] [NEW] linux: 4.12.0-12.13 -proposed tracker

[Andy Whitcroft]

Public bug reported:

This bug is for tracking the 4.12.0-12.13 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:Uploaded
kernel-phase-changed:Friday, 18. August 2017 10:41 UTC

-- swm properties --
phase: Uploaded

** 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: Andy Whitcroft (apw)
 Status: Fix Released

** Affects: kernel-development-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Andy Whitcroft (apw)
 Status: Fix Released

** Affects: kernel-development-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-development-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Fix Committed

** 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 Artful)
 Importance: Medium
 Status: Confirmed


** Tags: artful block-proposed block-proposed-artful 
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 Artful)
   Importance: Undecided
   Status: New

** Tags added: artful

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

[Kernel-packages] [Bug 1709292] Re: linux: 3.13.0-129.178 -proposed tracker

[Po-Hsu Lin]

3.13.0-129.178 - generic
Regression test CMPL.
http://kernel.ubuntu.com/testing/tracker-index.html

Issue to note in amd64:
  aio_dio_bugs - aio-cve-2016-10044 failed, expected result
  libhugetlbfs - FAIL no fallocate support in kernels before 4.3.0
  ubuntu_kvm_unit_tests - ioapic, smap, pku, svm, hyperv_clock and realmode 
(only on onibi) failed, issue seen before

Issue to note in arm64:
  aio_dio_bugs - aio-cve-2016-10044 failed, expected result
  hwclock - failed to change time, issue seen before
  libhugetlbfs - failed to build, bug 1707887
  ubuntu_cts_kernel - lp1262692 failed, issue seen before
  ubuntu_qrt_apparmor - test_old_trusty_regression_testsuite failed to build, 
bug 1699987
  ubuntu_qrt_kernel_security - 021, 022, 050, 060,  072, 075, 140 failed, issue 
seen before bug 163 (082 skipped)

Issue to note in i386:
  aio_dio_bugs - aio-cve-2016-10044 failed, expected result
  libhugetlbfs - FAIL no fallocate support in kernels before 4.3.0

Issue to note in ppc64le:
  ubuntu_blktrace_smoke_test - grub-ieee1275 issue, bug 1641567
  ubuntu_cts_kernel - grub-ieee1275 issue, bug 1641567
  ubuntu_kvm_unit_tests - grub-ieee1275 issue, bug 1641567
  ubuntu_leap_seconds - grub-ieee1275 issue, bug 1641567
  ubuntu_lxc - grub-ieee1275 issue, bug 1641567
  ubuntu_qrt_apparmor - grub-ieee1275 issue, bug 1641567
  ubuntu_qrt_kernel_aslr_collisions - grub-ieee1275 issue, bug 1641567
  ubuntu_qrt_kernel_hardening - grub-ieee1275 issue, bug 1641567
  ubuntu_qrt_kernel_panic - grub-ieee1275 issue, bug 1641567
  ubuntu_qrt_kernel_security - grub-ieee1275 issue, bug 1641567
  ubuntu_squashfs_smoke_test - grub-ieee1275 issue, bug 1641567

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

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

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

Title:
  linux: 3.13.0-129.178 -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:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

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

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

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

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

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

[Kernel-packages] [Bug 1711557] Re: Xenial update to 4.4.83 stable release

[Stefan Bader]

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The 4.4.83 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The 4.4.83 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
- 
-The following patches from the 4.4.83 stable release shall be
- applied:
+ The following patches from the 4.4.83 stable release shall be applied:
+ * cpuset: fix a deadlock due to incomplete patching of cpusets_enabled()
+ * mm: ratelimit PFNs busy info message
+ * iscsi-target: fix memory leak in iscsit_setup_text_cmd()
+ * iscsi-target: Fix iscsi_np reset hung task during parallel delete
+ * fuse: initialize the flock flag in fuse_file on allocation
+ * nfs/flexfiles: fix leak of nfs4_ff_ds_version arrays
+ * USB: serial: option: add D-Link DWM-222 device ID
+ * USB: serial: cp210x: add support for Qivicon USB ZigBee dongle
+ * USB: serial: pl2303: add new ATEN device id
+ * usb: musb: fix tx fifo flush handling again
+ * USB: hcd: Mark secondary HCD as dead if the primary one died
+ * staging:iio:resolver:ad2s1210 fix negative IIO_ANGL_VEL read
+ * iio: accel: bmc150: Always restore device to normal mode after
+   suspend-resume
+ * iio: light: tsl2563: use correct event code
+ * uas: Add US_FL_IGNORE_RESIDUE for Initio Corporation INIC-3069
+ * USB: Check for dropped connection before switching to full speed
+ * usb: core: unlink urbs from the tail of the endpoint's urb_list
+ * usb: quirks: Add no-lpm quirk for Moshi USB to Ethernet Adapter
+ * usb:xhci:Add quirk for Certain failing HP keyboard on reset after resume
+ * iio: adc: vf610_adc: Fix VALT selection value for REFSEL bits
+ * pnfs/blocklayout: require 64-bit sector_t
+ * pinctrl: sunxi: add a missing function of A10/A20 pinctrl driver
+ * pinctrl: samsung: Remove bogus irq_[un]mask from resource management
+ * Linux 4.4.83

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

Title:
  Xenial update to 4.4.83 stable release

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

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.83 stable release shall be applied:
  * cpuset: fix a deadlock due to incomplete patching of cpusets_enabled()
  * mm: ratelimit PFNs busy info message
  * iscsi-target: fix memory leak in iscsit_setup_text_cmd()
  * iscsi-target: Fix iscsi_np reset hung task during parallel delete
  * fuse: initialize the flock flag in fuse_file on allocation
  * nfs/flexfiles: fix leak of nfs4_ff_ds_version arrays
  * USB: serial: option: add D-Link DWM-222 device ID
  * USB: serial: cp210x: add support for Qivicon USB ZigBee dongle
  * USB: serial: pl2303: add new ATEN device id
  * usb: musb: fix tx fifo flush handling again
  * USB: hcd: Mark secondary HCD as dead if the primary one died
  * staging:iio:resolver:ad2s1210 fix negative IIO_ANGL_VEL read
  * iio: accel: bmc150: Always restore device to normal mode after
suspend-resume
  * iio: light: tsl2563: use correct event code
  * uas: Add US_FL_IGNORE_RESIDUE for Initio Corporation INIC-3069
  * USB: Check for dropped connection before switching to full speed
  * usb: core: unlink urbs from the tail of the endpoint's urb_list
  * usb: quirks: Add no-lpm quirk for Moshi USB to Ethernet Adapter
  * usb:xhci:Add quirk for Certain failing HP keyboard on reset after resume
  * iio: adc: vf610_adc: Fix VALT selection value for REFSEL bits
  * 

[Kernel-packages] [Bug 1711401] Re: accessing /dev/hvc1 with stress-ng on Ubuntu xenial causes crash

[Colin Ian King]

OK in 4.10

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

Title:
  accessing /dev/hvc1 with stress-ng on Ubuntu xenial causes crash

Status in linux package in Ubuntu:
  In Progress

Bug description:
  stress-ng run as root, --dev stressor, accessing /dev/hvc1:

  [ 2096.476610] hvc_open: request_irq failed with rc -16.
  [ 2096.476634] Unable to handle kernel paging request for data at address 
0x00a8
  [ 2096.476641] Faulting instruction address: 0xc0b0d8a4
  [ 2096.476647] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 2096.476650] SMP NR_CPUS=2048 NUMA PowerNV
  [ 2096.476657] Modules linked in: kvm_hv kvm_pr kvm cuse userio hci_vhci 
bluetooth uhid hid vhost_net vhost macvtap macvlan snd_seq snd_seq_device 
snd_timer snd soundcore ipmi_powernv ipmi_msghandler vmx_crypto leds_powernv 
uio_pdrv_genirq uio powernv_rng ibmpowernv ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr 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 dm_round_robin ses 
enclosure ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath
  [ 2096.476718] CPU: 74 PID: 23074 Comm: stress-ng-dev Not tainted 
4.4.0-92-generic #115-Ubuntu
  [ 2096.476724] task: c00fe8499030 ti: c00f0fa0c000 task.ti: 
c00f0fa0c000
  [ 2096.476728] NIP: c0b0d8a4 LR: c069648c CTR: 
c0696450
  [ 2096.476732] REGS: c00f0fa0f6b0 TRAP: 0300   Not tainted  
(4.4.0-92-generic)
  [ 2096.476736] MSR: 90009033   CR: 2248  
XER: 
  [ 2096.476749] CFAR: c0008468 DAR: 00a8 DSISR: 4000 
SOFTE: 0 
 GPR00: c069648c c00f0fa0f930 c15f8000 
00a8 
 GPR04: c00ff0082400 0002 001ffe7d 
0036 
 GPR08: c3236b90  804a 
c01e4e568880 
 GPR12: c0696450 cfb6bf00 000f 
010023d22660 
 GPR16: 3fff9ca5 0080 c01e43dde100 
c00fe459c800 
 GPR20:  0001 0e51 
00010004 
 GPR24: 00010800  f000 
c1892448 
 GPR28: c00fef98da28 c00fe459c800 0001 
00a8 
  [ 2096.476805] NIP [c0b0d8a4] _raw_spin_lock_irqsave+0x44/0x130
  [ 2096.476812] LR [c069648c] hvc_open+0x3c/0x1a0
  [ 2096.476815] Call Trace:
  [ 2096.476818] [c00f0fa0f930] [c00f0fa0f970] 0xc00f0fa0f970 
(unreliable)
  [ 2096.476824] [c00f0fa0f970] [c069648c] hvc_open+0x3c/0x1a0
  [ 2096.476829] [c00f0fa0f9f0] [c066c514] tty_open+0x194/0x7c0
  [ 2096.476836] [c00f0fa0fa90] [c02ec234] chrdev_open+0x114/0x270
  [ 2096.476841] [c00f0fa0faf0] [c02e1480] 
do_dentry_open+0x2c0/0x460
  [ 2096.476846] [c00f0fa0fb50] [c02f9aa8] do_last+0x178/0xff0
  [ 2096.476851] [c00f0fa0fc10] [c02fab3c] path_openat+0xcc/0x3c0
  [ 2096.476857] [c00f0fa0fc90] [c02fca5c] do_filp_open+0xfc/0x170
  [ 2096.476861] [c00f0fa0fdb0] [c02e3270] do_sys_open+0x1c0/0x3b0
  [ 2096.476867] [c00f0fa0fe30] [c0009204] system_call+0x38/0xb4
  [ 2096.476870] Instruction dump:
  [ 2096.476873] fbe1fff8 f8010010 f821ffc1 7c7f1b78 6000 6000 3920 
8bcd02ca 
  [ 2096.476881] 992d02ca 3940 994d02cc 814d0008 <7d20f829> 2c09 
40c20010 7d40f92d 
  [ 2096.476893] ---[ end trace c902066e4cc54f9e ]---

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

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

[Kernel-packages] [Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state

[Kai-Heng Feng]

I guess NVMe probably needs a to sleep exlat time (6000 here) to let it
transit back to power state 0.

Please try http://people.canonical.com/~khfeng/lp1705748-sleep/

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

Title:
  Samsung SSD 960 EVO 500GB refused to change power state

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Originally thought my issue was same as this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  but requested to report as separate bug

  System becomes unusable at seemingly random times but especially after
  resume from suspend due to disk 'disappearing' becoming inaccessible,
  with hundreds of I/O errors logged.

  After viewing the above bug report yesterday as a quick temporary fix I added 
kernel param, updated grub, etc with:
  GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0"

  System appears to have been stable for the last day, but is presumably
  using more power than it should.

  System, drive details below:

  M2 nvme drive: Samsung SSD 960 EVO 500GB

  Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17

  M/B Asus Prime B350m-A
  Ryzen 1600 cpu

  Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST 
device=00:00.0 address=0xfffdf800 flags=0x0a00]
  Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is 
down; will reset: CSTS=0x, PCI_STATUS=0x
  Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 
callbacks suppressed
  Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to 
change power state, currently in D3
  Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe 
failure status: -19
  Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change 
from 500107862016 to 0
  Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, 
dev nvme0n1, sector 0

  
  nvme list

  /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB
  / 500.11 GB 512 B + 0 B 2B7QCXE7

  sudo nvme id-ctrl /dev/nvme0

  NVME Identify Controller:
  vid : 0x144d
  ssvid : 0x144d
  sn : S3EUNX0J305518L
  mn : Samsung SSD 960 EVO 500GB
  fr : 2B7QCXE7
  rab : 2
  ieee : 002538
  cmic : 0
  mdts : 9
  cntlid : 2
  ver : 10200
  rtd3r : 7a120
  rtd3e : 4c4b40
  oaes : 0
  oacs : 0x7
  acl : 7
  aerl : 3
  frmw : 0x16
  lpa : 0x3
  elpe : 63
  npss : 4
  avscc : 0x1
  apsta : 0x1
  wctemp : 350
  cctemp : 352
  mtfa : 0
  hmpre : 0
  hmmin : 0
  tnvmcap : 500107862016
  unvmcap : 0
  rpmbs : 0
  sqes : 0x66
  cqes : 0x44
  nn : 1
  oncs : 0x1f
  fuses : 0
  fna : 0x5
  vwc : 0x1
  awun : 255
  awupf : 0
  nvscc : 1
  acwu : 0
  sgls : 0
  ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
  ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
  ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
  ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
  ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  drgrumpy   2192 F pulseaudio
   /dev/snd/pcmC1D0p:   drgrumpy   2192 F...m pulseaudio
   /dev/snd/controlC1:  drgrumpy   2192 F pulseaudio
  DistroRelease: Linux 18.2
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=a6896cdd-6bac-4e7f-9e13-55460859c3ec
  InstallationDate: Installed on 2017-07-06 (15 days ago)
  InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic 
root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro 
nvme_core.default_ps_max_latency_us=0
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  RfKill:
   
  Tags:  sonya
  Uname: Linux 4.10.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  

[Kernel-packages] [Bug 1680513] Re: Migrating KSM page causes the VM lock up as the KSM page merging list is too large

[Gavin Guo]

** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1680513

Title:
  Migrating KSM page causes the VM lock up as the KSM page merging list
  is too large

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  After numad is enabled and there are several VMs running on the same
  host machine(host kernel version: 4.4.0-72-generic #93), the
  softlockup messages can be observed inside the VMs' dmesg.

  First, the crashdump was captured when the symptom was observed. At
  the first glance, it looks like an IPI lost issue. The numad process
  initiates a migration of memory, and as part of this, needs to flush
  the TLB cache of another CPU. When the crash dump was taken, that
  other CPU has the TLB flush pending, but not executed. 

  The numad kernel task is holding a semaphore lock mmap_sem(for the
  VM's memory) to do the migration, and the tasks that actually end up
  being blocked are other virtual CPUs for the same VM. These tasks need
  to access or make changes to the memory map for the VM because of the
  VM page fault, but cannot acquire the semaphore lock.

  However, the original thoughts on the root cause (unhandled IPI or csd
  lock issue) are incorrect.

  We originally suspected an issue with a lost IPI (inter processor
  interrupt) that performs remote CPU cache flushes during page
  migration, or a known issue with the "csd" lock used to synchronize
  the remote CPU cache flush.  A lost IPI would be a function of the
  system firmware or chipset (it is not a CPU issue), but the known csd
  issue is hardware independent. 

  Gavin created the hotfix kernel with changes in the csd_lock_wait
  function that would time out if the unlock never happens (the end
  result of either cause), and print messages to the console when that
  timeout occurred. The messages look like: 

  csd_lock_wait called %d times

  csd: Detected non-responsive CSD lock (#%d) on CPU#%02d, waiting
  %Ld.%03Ld secs for CPU#%02d

  However, the VMs are still experiencing the hangs, but the
  csd_lock_wait timeout is not happening. This suggests that the csd
  lock / lost IPI is not the actual cause.

  In the crash dump, the numad task has induced a migration, and the
  stack is as follows: 

  #1 [885f8fb4fb78] smp_call_function_many 
  #2 [885f8fb4fbc0] native_flush_tlb_others 
  #3 [885f8fb4fc08] flush_tlb_page 
  #4 [885f8fb4fc30] ptep_clear_flush 
  #5 [885f8fb4fc60] try_to_unmap_one 
  #6 [885f8fb4fcd0] rmap_walk_ksm 
  #7 [885f8fb4fd28] rmap_walk 
  #8 [885f8fb4fd80] try_to_unmap 
  #9 [885f8fb4fdc8] migrate_pages 
  #10 [885f8fb4fe80] do_migrate_pages 

  
  The frame #1 is actually in the csd_lock_wait function mentioned
  above, but the compiler has optimized that call and it does not appear
  in the stack. 

  What happens here is that do_migrate_pages (frame #10) acquires the
  semaphore that everything else is waiting for (and that eventually
  produce the hang warnings), and it holds that semaphore for the
  duration of the page migration.  This strongly suggests that this
  single do_migrate_pages call is taking in excess of 10 seconds, and if
  the csd lock is not stuck, then something else within its call path is
  not functioning correctly. 

  We originally suspected that the lost IPI/csd lock hang was
  responsible for the hung task timeouts, but in the absence of the csd
  warning messages, the cause presumably lies elsewhere. 

  A KSM function appears in frame #6; this is the function that will
  search out the merged pages to handle them for the migration. 

  Gavin have tried to disassemble the code and finally find the 
  stable_node->hlist is as long as 2306920 entries:

  rmap_item list(stable_node->hlist): 
  stable_node: 0x881f836ba000 stable_node->hlist->first = 
0x883f3e5746b0 

  struct hlist_head { 
  [0] struct hlist_node *first; 
  } 
  struct hlist_node { 
  [0] struct hlist_node *next; 
  [8] struct hlist_node **pprev; 
  } 

  crash> list hlist_node.next 0x883f3e5746b0 > rmap_item.lst

  $ wc -l rmap_item.lst 
  2306920 rmap_item.lst

  This is roughly 9 GB of pages. The theory is that KSM has merged a
  very large number of pages that are empty (the value of all locations
  in the page are zero).

  The bug can be observed by the perf flame graph[1]:

  [1]. http://kernel.ubuntu.com/~gavinguo/sf00131845/numa-131845.svg

  [Fix]
  Andrea Arcangeli already sent out the patch[2] in the 2015/11/10.
  Andrew Morton also said he will apply the patch. However, the patch
  finally disappears from the mmtom tree in April 2016. Andrea suggested
  apply the 3 patches[3].

  [2]. [PATCH 1/1] ksm: introduce ksm_max_page_sharing 

[Kernel-packages] [Bug 1711557] [NEW] Xenial update to 4.4.83 stable release

[Stefan Bader]

Public bug reported:


SRU Justification

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

   git://git.kernel.org/

TEST CASE: TBD

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

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

Title:
  Xenial update to 4.4.83 stable release

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

Bug description:
  
  SRU Justification

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

 git://git.kernel.org/

  TEST CASE: TBD

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

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

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

[Kernel-packages] [Bug 1711535] Re: Xenial update to 4.4.82 stable release

[Stefan Bader]

Patch "packet: fix tp_reserve race in packet_set_ring" was skipped
because it is already applied for CVE-2017-1000111.

Skipped a whole bunch of changes, namely:

* revert "net: account for current skb length when
  deciding about UFO"
* revert "ipv4: Should use consistent conditional judgement for ip
  fragment in __ip_append_data and ip_finish_output"
* udp: consistently apply ufo or fragmentation
* ipv4: Should use consistent conditional judgement for ip fragment
  in __ip_append_data and ip_finish_output
* net: account for current skb length when deciding about UFO

I checked the resulting files net/ipv4/udp.c, net/ipv4/ip_output.c, and
net/ipv6/ip6_output.c from the 4.4.y tree and our Xenial tree. And
overall there is only one difference in the ip*_ouput.c files which come
from applying "udp: avoid ufo handling on IP payload compression
packets" and "ipv6: Don't use ufo handling on later transformed packets"
which I picked as additional patches to be part of CVE-2017-1000112. And
those still look like fixes to valid issues (though probably not
directly related to the CVE). So I would suggest we stay at what we got
right now.


** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The 4.4.82 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The 4.4.82 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
- 
-The following patches from the 4.4.82 stable release shall be
- applied:
+ The following patches from the 4.4.82 stable release shall be applied:
+ * tcp: avoid setting cwnd to invalid ssthresh after cwnd reduction states
+ * net: fix keepalive code vs TCP_FASTOPEN_CONNECT
+ * bpf, s390: fix jit branch offset related to ldimm64
+ * net: sched: set xt_tgchk_param par.nft_compat as 0 in ipt_init_target
+ * tcp: fastopen: tcp_connect() must refresh the route
+ * net: avoid skb_warn_bad_offload false positives on UFO
+ * sparc64: Prevent perf from running during super critical sections
+ * KVM: arm/arm64: Handle hva aging while destroying the vm
+ * mm/mempool: avoid KASAN marking mempool poison checks as use-after-free
+ * Linux 4.4.82

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

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

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

Title:
  Xenial update to 4.4.82 stable release

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

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.82 stable release shall be applied:
  * tcp: avoid setting cwnd to invalid ssthresh after cwnd reduction states
  * net: fix keepalive code vs TCP_FASTOPEN_CONNECT
  * bpf, s390: fix jit branch offset related to ldimm64
  * net: sched: set xt_tgchk_param par.nft_compat as 0 in ipt_init_target
  * tcp: fastopen: tcp_connect() must refresh the route
  * net: avoid skb_warn_bad_offload false positives on UFO
  * sparc64: Prevent perf from running during super critical sections
  * KVM: arm/arm64: Handle hva aging while destroying the vm
  * mm/mempool: avoid KASAN marking mempool poison checks as use-after-free
  * Linux 4.4.82

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

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

[Kernel-packages] [Bug 1711535] [NEW] Xenial update to 4.4.82 stable release

[Stefan Bader]

Public bug reported:


SRU Justification

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

   git://git.kernel.org/

TEST CASE: TBD

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

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

Title:
  Xenial update to 4.4.82 stable release

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

Bug description:
  
  SRU Justification

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

 git://git.kernel.org/

  TEST CASE: TBD

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

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

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

[Kernel-packages] [Bug 1711526] Re: Xenial update to 4.4.81 stable release

[Stefan Bader]

The following patches were skipped because they were already applied as part of 
the update for CVE-2017-1000112:
- ipv4: Should use consistent conditional judgement for ip fragment in
  __ip_append_data and ip_finish_output
- net: account for current skb length when deciding about UFO

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The 4.4.81 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The 4.4.81 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
- 
-The following patches from the 4.4.81 stable release shall be
- applied:
+ The following patches from the 4.4.81 stable release shall be applied:
+ * libata: array underflow in ata_find_dev()
+ * workqueue: restore WQ_UNBOUND/max_active==1 to be ordered
+ * ALSA: hda - Fix speaker output from VAIO VPCL14M1R
+ * ASoC: do not close shared backend dailink
+ * KVM: async_pf: make rcu irq exit if not triggered from idle task
+ * mm/page_alloc: Remove kernel address exposure in free_reserved_area()
+ * ext4: fix SEEK_HOLE/SEEK_DATA for blocksize < pagesize
+ * ext4: fix overflow caused by missing cast in ext4_resize_fs()
+ * ARM: dts: armada-38x: Fix irq type for pca955
+ * media: platform: davinci: return -EINVAL for VPFE_CMD_S_CCDC_RAW_PARAMS
+   ioctl
+ * target: Avoid mappedlun symlink creation during lun shutdown
+ * iscsi-target: Always wait for kthread_should_stop() before kthread exit
+ * iscsi-target: Fix early sk_data_ready LOGIN_FLAGS_READY race
+ * iscsi-target: Fix initial login PDU asynchronous socket close OOPs
+ * iscsi-target: Fix delayed logout processing greater than
+   SECONDS_FOR_LOGOUT_COMP
+ * iser-target: Avoid isert_conn->cm_id dereference in isert_login_recv_done
+ * mm, mprotect: flush TLB if potentially racing with a parallel reclaim
+   leaving stale TLB entries
+ * media: lirc: LIRC_GET_REC_RESOLUTION should return microseconds
+ * f2fs: sanity check checkpoint segno and blkoff
+ * drm: rcar-du: fix backport bug
+ * saa7164: fix double fetch PCIe access condition
+ * ipv4: ipv6: initialize treq->txhash in cookie_v[46]_check()
+ * net: Zero terminate ifr_name in dev_ifname().
+ * ipv6: avoid overflow of offset in ip6_find_1stfragopt
+ * ipv4: initialize fib_trie prior to register_netdev_notifier call.
+ * rtnetlink: allocate more memory for dev_set_mac_address()
+ * mcs7780: Fix initialization when CONFIG_VMAP_STACK is enabled
+ * openvswitch: fix potential out of bound access in parse_ct
+ * packet: fix use-after-free in prb_retire_rx_blk_timer_expired()
+ * ipv6: Don't increase IPSTATS_MIB_FRAGFAILS twice in ip6_fragment()
+ * net: ethernet: nb8800: Handle all 4 RGMII modes identically
+ * dccp: fix a memleak that dccp_ipv6 doesn't put reqsk properly
+ * dccp: fix a memleak that dccp_ipv4 doesn't put reqsk properly
+ * dccp: fix a memleak for dccp_feat_init err process
+ * sctp: don't dereference ptr before leaving _sctp_walk_{params, errors}()
+ * sctp: fix the check for _sctp_walk_params and _sctp_walk_errors
+ * net/mlx5: Fix command bad flow on command entry allocation failure
+ * net: phy: Correctly process PHY_HALTED in phy_stop_machine()
+ * net: phy: Fix PHY unbind crash
+ * xen-netback: correctly schedule rate-limited queues
+ * sparc64: Measure receiver forward progress to avoid send mondo timeout
+ * wext: handle NULL extra data in iwe_stream_add_point better
+ * sh_eth: R8A7740 supports packet shecksumming
+ * net: phy: dp83867: fix irq generation
+ * tg3: Fix race condition in tg3_get_stats64().
+ * x86/boot: Add missing declaration of string functions
+ * phy state machine: failsafe leave invalid RUNNING state
+ * scsi: qla2xxx: Get mutex lock before checking optrom_state
+ * drm/virtio: fix framebuffer sparse warning
+ * virtio_blk: fix panic in initialization error path
+ * ARM: 8632/1: ftrace: fix syscall name matching
+ * mm, slab: make sure that KMALLOC_MAX_SIZE will fit into MAX_ORDER
+ * lib/Kconfig.debug: fix frv build failure
+ * signal: protect SIGNAL_UNKILLABLE from unintentional clearing.
+ * mm: don't dereference struct page fields of 

[Kernel-packages] [Bug 1709303] Re: linux: 4.10.0-33.37 -proposed tracker

[Po-Hsu Lin]

4.10.0-33.37 - generic
Regression test CMPL.
http://kernel.ubuntu.com/testing/tracker-index.html

Issue to note in amd64:
  monotonic_time - gtod failed, issue seen before
  ubuntu_32_on_64 - dpkg interrupted, not a real bug
  ubuntu_bpf - test case issue, passed on two nodes
  ubuntu_kvm_unit_tests - smap, pku and svm failed, issue seen before
  ubuntu_leap_seconds - dpkg interrupted, not a real bug
  ubuntu_lxc - Failed to start networking in ubuntu-cloud container on some 
nodes
  ubuntu_unionmount_overlayfs_suite - only failed on rumford, passed on other 
two
  xfstests - btrfs, xfs failed, not regression

Issue to note in arm64:
  hwclock - failed to change time
  ubuntu_bpf - failed to build, bug 1675395
  ubuntu_kernel_selftests - breakpoint test failed to build, bug 1680507
  ubuntu_zfs_xfs_generic - test 079, 317 failed

Issue to note in i386:
  ubuntu_bpf - test_maps bpf test crashed, bug 1711512
  xfstests - btrfs, xfs failed, not regression

Issue to note in ppc64le:
  ubuntu_kvm_unit_tests - ld: powerpc/selftest.elf: Not enough room for program 
headers
  xfstests - The file /dev/sdb1 does not exist and no size was specified.

Issue to note in s390x (zKVM):
  aio_dio_bugs - event res -22, not regression
  libhugetlbfs - 10 failed, 7 killed by signal, 1 bad config, issue seen before
  scrashme - failed to build bug 1689240
  ubuntu_bpf - failed to build, bug 1711299
  ubuntu_ecryptfs - miscdev-bad-count.sh.xfs ~ namelen.sh failed, issue seen 
before

Issue to note in s390x (zVM):
  aio_dio_bugs - event res -22, not regression
  libhugetlbfs - IOError: [Errno 95] Operation not supported
  scrashme - failed to build bug 1689240
  ubuntu_bpf - failed to build, bug 1711299
  ubuntu_ecryptfs - miscdev-bad-count.sh.xfs ~ namelen.sh failed, issue seen 
before

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

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

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

Title:
  linux: 4.10.0-33.37 -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: 1709304
  derivatives: 1709305
  -- 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/1709303/+subscriptions

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

[Kernel-packages] [Bug 1711526] [NEW] Xenial update to 4.4.81 stable release

[Stefan Bader]

Public bug reported:

SRU Justification

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

   git://git.kernel.org/

TEST CASE: TBD

The following patches from the 4.4.81 stable release shall be applied:
* libata: array underflow in ata_find_dev()
* workqueue: restore WQ_UNBOUND/max_active==1 to be ordered
* ALSA: hda - Fix speaker output from VAIO VPCL14M1R
* ASoC: do not close shared backend dailink
* KVM: async_pf: make rcu irq exit if not triggered from idle task
* mm/page_alloc: Remove kernel address exposure in free_reserved_area()
* ext4: fix SEEK_HOLE/SEEK_DATA for blocksize < pagesize
* ext4: fix overflow caused by missing cast in ext4_resize_fs()
* ARM: dts: armada-38x: Fix irq type for pca955
* media: platform: davinci: return -EINVAL for VPFE_CMD_S_CCDC_RAW_PARAMS
  ioctl
* target: Avoid mappedlun symlink creation during lun shutdown
* iscsi-target: Always wait for kthread_should_stop() before kthread exit
* iscsi-target: Fix early sk_data_ready LOGIN_FLAGS_READY race
* iscsi-target: Fix initial login PDU asynchronous socket close OOPs
* iscsi-target: Fix delayed logout processing greater than
  SECONDS_FOR_LOGOUT_COMP
* iser-target: Avoid isert_conn->cm_id dereference in isert_login_recv_done
* mm, mprotect: flush TLB if potentially racing with a parallel reclaim
  leaving stale TLB entries
* media: lirc: LIRC_GET_REC_RESOLUTION should return microseconds
* f2fs: sanity check checkpoint segno and blkoff
* drm: rcar-du: fix backport bug
* saa7164: fix double fetch PCIe access condition
* ipv4: ipv6: initialize treq->txhash in cookie_v[46]_check()
* net: Zero terminate ifr_name in dev_ifname().
* ipv6: avoid overflow of offset in ip6_find_1stfragopt
* ipv4: initialize fib_trie prior to register_netdev_notifier call.
* rtnetlink: allocate more memory for dev_set_mac_address()
* mcs7780: Fix initialization when CONFIG_VMAP_STACK is enabled
* openvswitch: fix potential out of bound access in parse_ct
* packet: fix use-after-free in prb_retire_rx_blk_timer_expired()
* ipv6: Don't increase IPSTATS_MIB_FRAGFAILS twice in ip6_fragment()
* net: ethernet: nb8800: Handle all 4 RGMII modes identically
* dccp: fix a memleak that dccp_ipv6 doesn't put reqsk properly
* dccp: fix a memleak that dccp_ipv4 doesn't put reqsk properly
* dccp: fix a memleak for dccp_feat_init err process
* sctp: don't dereference ptr before leaving _sctp_walk_{params, errors}()
* sctp: fix the check for _sctp_walk_params and _sctp_walk_errors
* net/mlx5: Fix command bad flow on command entry allocation failure
* net: phy: Correctly process PHY_HALTED in phy_stop_machine()
* net: phy: Fix PHY unbind crash
* xen-netback: correctly schedule rate-limited queues
* sparc64: Measure receiver forward progress to avoid send mondo timeout
* wext: handle NULL extra data in iwe_stream_add_point better
* sh_eth: R8A7740 supports packet shecksumming
* net: phy: dp83867: fix irq generation
* tg3: Fix race condition in tg3_get_stats64().
* x86/boot: Add missing declaration of string functions
* phy state machine: failsafe leave invalid RUNNING state
* scsi: qla2xxx: Get mutex lock before checking optrom_state
* drm/virtio: fix framebuffer sparse warning
* virtio_blk: fix panic in initialization error path
* ARM: 8632/1: ftrace: fix syscall name matching
* mm, slab: make sure that KMALLOC_MAX_SIZE will fit into MAX_ORDER
* lib/Kconfig.debug: fix frv build failure
* signal: protect SIGNAL_UNKILLABLE from unintentional clearing.
* mm: don't dereference struct page fields of invalid pages
* workqueue: implicit ordered attribute should be overridable
* Linux 4.4.81

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

** Affects: linux (Ubuntu Xenial)
 Importance: Medium
 Assignee: Stefan Bader (smb)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

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

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

Title:
  Xenial update to 4.4.81 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a 

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

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

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

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

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

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

Title:
  ubuntu_bpf test crashed on i386 zesty

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  test_maps bpf test crashed on the i386 testing node with Zesty kernel
  (4.10.0-33.37)

  echo 'Running test_maps bpf test..'
  bpf/test_maps
  /home/ubuntu/autotest/client/tests/ubuntu_bpf/ubuntu_bpf.sh: line 106: 25432 
Segmentation fault (core dumped) bpf/test_maps > ${TMP}
  Programs crashed during test execution
  Please verify 
/home/ubuntu/autotest/client/results/default/ubuntu_bpf.ubuntu-bjf/debug/crash.test_maps.25432
 for more info

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

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

[Kernel-packages] [Bug 1711512] [NEW] ubuntu_bpf test crashed on i386 zesty

[Po-Hsu Lin]

Public bug reported:

test_maps bpf test crashed on the i386 testing node with Zesty kernel
(4.10.0-33.37)

echo 'Running test_maps bpf test..'
bpf/test_maps
/home/ubuntu/autotest/client/tests/ubuntu_bpf/ubuntu_bpf.sh: line 106: 25432 
Segmentation fault (core dumped) bpf/test_maps > ${TMP}
Programs crashed during test execution
Please verify 
/home/ubuntu/autotest/client/results/default/ubuntu_bpf.ubuntu-bjf/debug/crash.test_maps.25432
 for more info

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


** Tags: bot-stop-nagging 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/1711512

Title:
  ubuntu_bpf test crashed on i386 zesty

Status in linux package in Ubuntu:
  New

Bug description:
  test_maps bpf test crashed on the i386 testing node with Zesty kernel
  (4.10.0-33.37)

  echo 'Running test_maps bpf test..'
  bpf/test_maps
  /home/ubuntu/autotest/client/tests/ubuntu_bpf/ubuntu_bpf.sh: line 106: 25432 
Segmentation fault (core dumped) bpf/test_maps > ${TMP}
  Programs crashed during test execution
  Please verify 
/home/ubuntu/autotest/client/results/default/ubuntu_bpf.ubuntu-bjf/debug/crash.test_maps.25432
 for more info

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

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

[Dexuan Cui]

I read through the long bug log and found an interesting thing:

In #36, Andrey Vertexx (vertexx) reported the issue was fixed by the
kernel in #30, but later Andrey thought the same kernel couldn't work
any more?

In #47, #48, #54, #59 a lot of people ,   Aleksey (noirfry) , Khallaf
(mkhallaf),  Eric (jumpiem) etc.,  said removing the virtual DVD could
resolve the issue or the boot issue? But it looks later this workaround
can't work any more?

Please correct me if I don't get it right.

PS, I'm debugging a similar (or the same?) issue with RHEL 7.3 + LIS
4.2.2, and I happened to find this Ubuntu bug.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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', 

[Kernel-packages] [Bug 1706833] Re: atheros bt failed after S3

[Kai-Heng Feng]

Bluetooth works great in 100 times S3 cycle. No more firmware loading
issue.

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

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

Title:
  atheros bt failed after S3

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

Bug description:
  [Impact]
  BT fails to load firmware after S3. On my system it's atheros' chip, but the 
same issue can be seen with broadcom's chip, too.
 [542.6274] WARNING: CPU: 0 PID: 20729 at 
/build/linux-MD8jsN/linux-4.4.0/drivers/base/firmware_class.c:1148 
_request_firmware+0x7c2/0xaf0()

  The root cause of this issue is request_firmware() is being called at
  the wrong time.

  [Fix]
  The fix is from this old thread[1], but the patch didn't be accepted by the 
maintainer.
  It prevents the work queue from being re-created and calls request_firmware() 
immediately before usermodehelper is fully resumed. Making the workqueue 
freezable preserves the delay and will postpone the firmware loading time.

  [Test Case]
  Verified on the machine has this issue, and confirm this patch works.

  [Regression Potential]
  From what I can see, I think this change should be safe, and after 240 times 
S3 test, the system and BT functions are still working.

  1. http://lists.openwall.net/netdev/2015/05/06/3

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

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

[Kernel-packages] [Bug 1709296] Re: linux: 4.4.0-93.116 -proposed tracker

[Gavin Lin]

Hardware Certification have begun testing this -proposed kernel.

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => Gavin 
Lin (gavin.lin)

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

Title:
  linux: 4.4.0-93.116 -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:
  In Progress
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: 1709297
  derivatives: 1709298,1709299,1709300,1709301
  -- 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/1709296/+subscriptions

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