date:20171009

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

Title:
  Random system lock up

Status in linux package in Ubuntu:
  Expired

Bug description:
  Over the last several kernel upgrades, my system has been locking up
  at random times. Some times it will run for hours without locking up
  and other times it will lock up within 5 minutes of booting.

  This happens when I am browsing the internet, and it doesn't seem to
  be anything specific. At times I can watch full screen YouTube videos,
  and others time just a regular window. The last lockup was just now
  while browsing a page on the Ubuntu Forums.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-12-generic 4.11.0-12.17
  ProcVersionSignature: Ubuntu 4.11.0-12.17-generic 4.11.12
  Uname: Linux 4.11.0-12-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cariboo1362 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Jul 31 12:45:33 2017
  InstallationDate: Installed on 2017-07-12 (18 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 003: ID 04f2:b446 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 276d:1119  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA Satellite C50-B
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-12-generic.efi.signed 
root=UUID=3761b276-a029-42c9-9b8e-d345ae543443 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-12-generic N/A
   linux-backports-modules-4.11.0-12-generic  N/A
   linux-firmware 1.167
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.70
  dmi.board.asset.tag: *
  dmi.board.name: ZBWAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.70:bd12/11/2014:svnTOSHIBA:pnSatelliteC50-B:pvrPSCMLC-02Y00T:rvnTOSHIBA:rnZBWAA:rvr1.00:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: Satellite C50-B
  dmi.product.version: PSCMLC-02Y00T
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1707845] Re: package linux-image-extra-4.4.0-87-generic 4.4.0-87.110 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before atte

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

Title:
  package linux-image-extra-4.4.0-87-generic 4.4.0-87.110 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in linux package in Ubuntu:
  Expired

Bug description:
  Errors were encountered while processing:
   linux-image-extra-4.4.0-87-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-87-generic 4.4.0-87.110
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  velu   2511 F pulseaudio
   /dev/snd/controlC1:  velu   2511 F pulseaudio
  Date: Mon Jul 31 14:20:30 2017
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  HibernationDevice: RESUME=UUID=00852b7b-0641-4e5c-b531-792c625c8131
  InstallationDate: Installed on 2016-05-25 (432 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic 
root=UUID=e3070825-0887-4eab-bec5-b5d3e96ee2da ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-extra-4.4.0-87-generic 4.4.0-87.110 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1707139] Re: kernel 4.10 dose not work with ndiswrapper , 4.8 kernel works

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

Title:
  kernel 4.10 dose not work with ndiswrapper , 4.8 kernel works

Status in linux package in Ubuntu:
  Expired

Bug description:
  https://askubuntu.com/questions/568056/usb-wireless-netgear-adapter
  "what i do to get my WiFi card working"

   i did the update to kernel 4.10.0-28  and my wifi drivers stop
  working with my net-gear wnd "brodcom" device,,   i can load up with
  the 4.8.0-53 kernel and it will start working agin  im having this
  problem with every distro of linux with the 4.10 kernel

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

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

[Kernel-packages] [Bug 1707422] Re: RT5370 Wi-Fi USB-stick fails to connect network

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

Title:
  RT5370 Wi-Fi USB-stick fails to connect network

Status in linux package in Ubuntu:
  Expired

Bug description:
  Wi-Fi networks appear in selection menu, but system fails to connect
  to any of them. Everything works alright on Windows 10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-generic 4.10.0.28.29
  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/controlC1:  ab123321   1358 F pulseaudio
   /dev/snd/controlC0:  ab123321   1358 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Jul 29 20:14:37 2017
  InstallationDate: Installed on 2017-07-29 (0 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: System manufacturer System Product Name
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic.efi.signed 
root=UUID=f297a62c-9a48-446d-973c-7089593b2811 ro quiet splash 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
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0809
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z270-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0809:bd07/07/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ270-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

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

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

Title:
  package linux-image-4.4.0-87-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:
  having problems updating

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-87-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laurence   1647 F pulseaudio
  Date: Thu Jul 27 22:58:52 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=80df043f-2917-407a-8050-b2477b65b385
  InstallationDate: Installed on 2016-09-13 (316 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20FU0007UK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic.efi.signed 
root=UUID=b8f58a9d-2806-4032-9a5e-2085d6a04fcf 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.4.0-87-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: 04/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R08ET40W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FU0007UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR08ET40W(1.14):bd04/20/2016:svnLENOVO:pn20FU0007UK:pvrThinkPadL460:rvnLENOVO:rn20FU0007UK:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FU0007UK
  dmi.product.version: ThinkPad L460
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1707111] Re: Hardware clock isn't updated anymore

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

Title:
  Hardware clock isn't updated anymore

Status in linux package in Ubuntu:
  Expired

Bug description:
  For some months I'm noticing that my hardware clock doesn't get updated 
anymore while the software clock successfully updates ("ntpd -q" runs every 
hour). This appears on my laptop (kernel version 4.11.10) and my PC (kernel 
version 4.8.17). Could it be that the 11 minute mode was enabled in past kernel 
versions but not anymore in recent kernel versions?
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.8.0-48-generic.
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16'
 Mixer name : 'Realtek ALC662 rev1'
 Components : 'HDA:10ec0662,18497662,00100101'
 Controls  : 37
 Simple ctrls  : 19
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19'
 Mixer name : 'Nvidia GPU 42 HDMI/DP'
 Components : 'HDA:10de0042,14583555,00100100'
 Controls  : 21
 Simple ctrls  : 3
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=23b2ee46-5930-41bc-a3e5-33800a236db2
  IwConfig: Error: [Errno 2] No such file or directory
  JournalErrors:
   No journal files were found.
   -- No entries --
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-48-generic 
root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq
  ProcVersionSignature: Ubuntu 4.8.0-48.51-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-48-generic N/A
   linux-backports-modules-4.8.0-48-generic  N/A
   linux-firmware1.167
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  artful
  Uname: Linux 4.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers 
wireshark
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 07/23/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: 960GM/U3S3 FX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1706499] Re: NMI Watchdog Soft Lockup CPU Frozen for 22s

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

Title:
  NMI Watchdog Soft Lockup CPU Frozen for 22s

Status in linux package in Ubuntu:
  Expired

Bug description:
  Whenever switching from high to low, or low to high CPU loads I
  encounter the attached lockup. This happens at least twice daily when
  the server is left alone, more often when it actually does anything.

  The CPU# changes with each crash, but seems to always be for 22s.

  ul 25 08:01:59 necronomicon kernel: [32989.183560] [ cut here 
]
  Jul 25 08:01:59 necronomicon kernel: [32989.183569] WARNING: CPU: 0 PID: 0 at 
/build/linux-Fsa3B1/linux-4.10.0/net/sched/sch_generic.c:316 
dev_watchdog+0x22c/0x230
  Jul 25 08:01:59 necronomicon kernel: [32989.183571] NETDEV WATCHDOG: enp37s0 
(r8169): transmit queue 0 timed out
  Jul 25 08:01:59 necronomicon kernel: [32989.183572] Modules linked in: 
binfmt_misc nls_iso8859_1 joydev input_leds snd_hda_codec_hdmi 
snd_hda_codec_realtek eeepc_wmi snd_hda_codec_generic asus_wmi snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer snd soundcore 
sparse_keymap ccp edac_mce_amd edac_core shpchp i2c_piix4 kvm irqbypass 
i2c_designware_platform i2c_designware_core 8250_dw mac_hid ib_iser rdma_cm 
iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid nouveau 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc mxm_wmi video 
i2c_algo_bit ttm drm_kms_helper aesni_intel syscopyarea aes_x86_64 sysfillrect
  Jul 25 08:01:59 necronomicon kernel: [32989.183610]  crypto_simd sysimgblt 
glue_helper fb_sys_fops cryptd drm r8169 mii ahci libahci wmi gpio_amdpt fjes 
gpio_generic
  Jul 25 08:01:59 necronomicon kernel: [32989.183619] CPU: 0 PID: 0 Comm: 
swapper/0 Tainted: G L  4.10.0-28-generic #32-Ubuntu
  Jul 25 08:01:59 necronomicon kernel: [32989.183620] Hardware name: System 
manufacturer System Product Name/PRIME B350M-A, BIOS 0805 06/20/2017
  Jul 25 08:01:59 necronomicon kernel: [32989.183621] Call Trace:
  Jul 25 08:01:59 necronomicon kernel: [32989.183623]  
  Jul 25 08:01:59 necronomicon kernel: [32989.183627]  dump_stack+0x63/0x81
  Jul 25 08:01:59 necronomicon kernel: [32989.183629]  __warn+0xcb/0xf0
  Jul 25 08:01:59 necronomicon kernel: [32989.183631]  
warn_slowpath_fmt+0x5f/0x80
  Jul 25 08:01:59 necronomicon kernel: [32989.183634]  dev_watchdog+0x22c/0x230
  Jul 25 08:01:59 necronomicon kernel: [32989.183637]  ? 
qdisc_rcu_free+0x50/0x50
  Jul 25 08:01:59 necronomicon kernel: [32989.183639]  call_timer_fn+0x35/0x140
  Jul 25 08:01:59 necronomicon kernel: [32989.183641]  
run_timer_softirq+0x215/0x4b0
  Jul 25 08:01:59 necronomicon kernel: [32989.183643]  ? ktime_get+0x41/0xb0
  Jul 25 08:01:59 necronomicon kernel: [32989.183646]  ? 
lapic_next_event+0x1d/0x30
  Jul 25 08:01:59 necronomicon kernel: [32989.183648]  ? 
clockevents_program_event+0x7f/0x120
  Jul 25 08:01:59 necronomicon kernel: [32989.183651]  __do_softirq+0x104/0x2af
  Jul 25 08:01:59 necronomicon kernel: [32989.183654]  irq_exit+0xb6/0xc0
  Jul 25 08:01:59 necronomicon kernel: [32989.183656]  
smp_apic_timer_interrupt+0x3d/0x50
  Jul 25 08:01:59 necronomicon kernel: [32989.183659]  
apic_timer_interrupt+0x89/0x90
  Jul 25 08:01:59 necronomicon kernel: [32989.183661] RIP: 
0010:native_safe_halt+0x6/0x10
  Jul 25 08:01:59 necronomicon kernel: [32989.183662] RSP: 
0018:bec03de0 EFLAGS: 0246 ORIG_RAX: ff10
  Jul 25 08:01:59 necronomicon kernel: [32989.183665] RAX:  
RBX: bec10500 RCX: 
  Jul 25 08:01:59 necronomicon kernel: [32989.183666] RDX:  
RSI:  RDI: 
  Jul 25 08:01:59 necronomicon kernel: [32989.183667] RBP: bec03de0 
R08: 0100 R09: 1e001b9b5d00
  Jul 25 08:01:59 necronomicon kernel: [32989.183668] R10: 0001007cafbd 
R11:  R12: 
  Jul 25 08:01:59 necronomicon kernel: [32989.183668] R13: bec10500 
R14:  R15: 
  Jul 25 08:01:59 necronomicon kernel: [32989.183670]  
  Jul 25 08:01:59 necronomicon kernel: [32989.183673]  default_idle+0x20/0xd0
  Jul 25 08:01:59 necronomicon kernel: [32989.183675]  arch_cpu_idle+0xf/0x20
  Jul 25 08:01:59 necronomicon kernel: [32989.183677]  
default_idle_call+0x23/0x30
  Jul 25 08:01:59 necronomicon kernel: [32989.183679]  do_idle+0x16f/0x200
  Jul 25 08:01:59 necronomicon kernel: [32989.183682]  
cpu_startup_entry+0x71/0x80
  Jul 25 08:01:59 necronomicon kernel:

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

This change was made by a bot.

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

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

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  steam app

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1096 F pulseaudio
lurker 1495 F pulseaudio
   /dev/snd/controlC1:  gdm1096 F pulseaudio
lurker 1495 F pulseaudio
  Date: Mon Oct  9 22:36:54 2017
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: find_get_entry+0x36/0xd0 RSP: ac0bc94d7cd0
  Failure: oops
  InstallationDate: Installed on 2017-09-01 (38 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170831)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=95d1045d-861f-4b90-97bd-50f9f6aff303 ro quiet
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at 00040020
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3701
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3701:bd03/31/2017:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1722430] [NEW] BUG: unable to handle kernel paging request at 0000000400000020

2017-10-09 Thread John Schweiger

Public bug reported:

steam app

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-12-generic 4.13.0-12.13
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1096 F pulseaudio
  lurker 1495 F pulseaudio
 /dev/snd/controlC1:  gdm1096 F pulseaudio
  lurker 1495 F pulseaudio
Date: Mon Oct  9 22:36:54 2017
DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: find_get_entry+0x36/0xd0 RSP: ac0bc94d7cd0
Failure: oops
InstallationDate: Installed on 2017-09-01 (38 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170831)
IwConfig:
 lono wireless extensions.
 
 eno1  no wireless extensions.
MachineType: ASUS All Series
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=95d1045d-861f-4b90-97bd-50f9f6aff303 ro quiet
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
RfKill:
 
SourcePackage: linux
Title: BUG: unable to handle kernel paging request at 00040020
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/31/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3701
dmi.board.asset.tag: Default string
dmi.board.name: X99-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3701:bd03/31/2017:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS

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


** Tags: amd64 apport-kerneloops artful kernel-oops

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

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

Status in linux package in Ubuntu:
  New

Bug description:
  steam app

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1096 F pulseaudio
lurker 1495 F pulseaudio
   /dev/snd/controlC1:  gdm1096 F pulseaudio
lurker 1495 F pulseaudio
  Date: Mon Oct  9 22:36:54 2017
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: find_get_entry+0x36/0xd0 RSP: ac0bc94d7cd0
  Failure: oops
  InstallationDate: Installed on 2017-09-01 (38 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170831)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=95d1045d-861f-4b90-97bd-50f9f6aff303 ro quiet
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at 00040020
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3701
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3701:bd03/31/2017:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor:

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

2017-10-09 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

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

Status in linux package in Ubuntu:
  New

Bug description:
  steam app

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1096 F pulseaudio
lurker 1495 F pulseaudio
   /dev/snd/controlC1:  gdm1096 F pulseaudio
lurker 1495 F pulseaudio
  Date: Mon Oct  9 22:36:54 2017
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: find_get_entry+0x36/0xd0 RSP: ac0bc94d7cd0
  Failure: oops
  InstallationDate: Installed on 2017-09-01 (38 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170831)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=95d1045d-861f-4b90-97bd-50f9f6aff303 ro quiet
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at 00040020
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3701
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3701:bd03/31/2017:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1697450] Re: Gnome Shell hangs at startup

2017-10-09 Thread Daniel van Vugt

It looks like that error is caused by sudo. Please just run:
  apport-collect 1697450

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

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

Title:
  Gnome Shell hangs at startup

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to install from the daily Artful desktop image (20170612).

  After boot, the gnome session hangs at startup, while the "zoom"
  animation is being shown.

  I have an intel card:

  
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])
  Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller
  Flags: bus master, fast devsel, latency 0, IRQ 29
  Memory at f780 (64-bit, non-prefetchable) [size=4M]
  Memory at e000 (64-bit, prefetchable) [size=256M]
  I/O ports at f000 [size=64]
  [virtual] Expansion ROM at 000c [disabled] [size=128K]
  Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
  Capabilities: [d0] Power Management version 2
  Capabilities: [a4] PCI Advanced Features
  Kernel driver in use: i915
  Kernel modules: i915

  
  I'm not sure how to debug this further, but I had similar issues with the 
installer from Zesty as well (see 
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1681846)
  With Artful, at least it gets past the splash screen but then it hangs.

  Note that the system is currently running Yakkety with no issue.

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

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

[Kernel-packages] [Bug 1718573] Re: Cannot unlock lock screen

2017-10-09 Thread jeremy-list

I can no longer replicate this bug with the 4.13.0-12-generic kernel.

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

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

Title:
  Cannot unlock lock screen

Status in gnome-shell package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  To replicate:
  Leave the computer unattended until the screen locks, then press some keys 
and click the mouse.

  Expected results:
  A password confirmation dialog should appear.

  Actual results:
  All mouse clicks and key presses are ignored except ctrl-alt-F1.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-settings-daemon 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 21 15:39:09 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
  InstallationDate: Installed on 2017-08-15 (36 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to artful on 2017-09-14 (6 days ago)

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

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

[Kernel-packages] [Bug 1693369] Re: 5U84 - ses driver isn't binding right - cannot blink lights on 1 of the 2 5u84

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

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

Title:
  5U84 - ses driver isn't binding right - cannot blink lights on 1 of
  the 2 5u84

Status in The Ubuntu-power-systems project:
  In Progress
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

Bug description:
  
  == SRU Justification ==
  This bug is resolved by commit 62e62ffd95539b9220894a7900a619e0f3ef4756.

  Without this patch, the symlink in sysfs which binds a SAS device to an 
enclosure 
  slot does not get created. This makes disk hotplug near impossible on large 
  JBOD disk drawers.

  Commit 62e62ffd95 is also needed in Xenial.  However, Xenial also needed some 
  prereq commits, so it's SRU will be sent separately.

  Commit 62e62ffd95 is in mainline as of 4.13-rc1.

  
  == Fix ==
  commit 62e62ffd95539b9220894a7900a619e0f3ef4756
  Author: Maurizio Lombardi 
  Date:   Tue Jun 27 11:53:27 2017 +0200

  scsi: ses: do not add a device to an enclosure if
  enclosure_add_links() fails.

  == Regression Potential ==
  This patch was also cc'd and applied to upstream stable, so there is 
  upstream confidence in it.

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


  
  This is a request to add the following upstream commit to both Ubuntu 16.04.1 
and 16.04.2:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/scsi/ses.c?id=9373eba6cfae48911b977d14323032cd5d161aae

  Without this patch, the symlink in sysfs which binds a SAS device to
  an enclosure slot does not get created. This makes disk hotplug near
  impossible on large JBOD disk drawers.

  You should be able to do:

  ls /sys/block/sdb/device/ | grep enclosure

  and see something like:

  enclosure_device:1

  If you cd to this directory, you can then access the SES controls for
  that slot to flash the LED to assist in locating the disk to replace a
  failed disk.

  Currently with 16.04.1 and 16.04.2, these symlinks are not getting
  created.

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

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

[Kernel-packages] [Bug 1718578] Re: Support setting I2C_TIMEOUT via ioctl for i2c-designware

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

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

Title:
  Support setting I2C_TIMEOUT via ioctl for i2c-designware

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

Bug description:
  SRU Justification

  [Impact]
  The timeout value in i2c-designware is hardcoded. Userspace tool may want to 
change the timeout value via ioctl I2C_TIMEOUT, but it doesn't work for 
i2c-designware.

  [Test Case]
  Change the timeout value via ioctl I2C_TIMEOUT. Nothing happened.
  With the patch, timeout value for i2c-designware will be updated correctly.

  [Regression Potential]
  Minimal. The change only applies to a specific driver, i2c-designware. Also, 
it has minimal code change.

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

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

[Kernel-packages] [Bug 1720466] Re: Add installer support for Broadcom BCM573xx network drivers.

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

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

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

Title:
  Add installer support for Broadcom BCM573xx network drivers.

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

Bug description:
  Please add bnxt_en to nic-modules to Ubuntu kernels 4.4 and later.

  bnxt_en has been available since upstream Linux 4.4 commit
  c0c050c58d840994ba842ad1c338a98e7c12b764 ("bnxt_en: New Broadcom
  ethernet driver.").

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

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

[Kernel-packages] [Bug 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

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

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

Title:
  Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  SRU Justification:
  [Impact]
  Touchpad on Lenovo X1 Yoga / Yoga 720-15IKB does not work.

  [Test Case]
  Touchpad doesn't work on the system.
  With the patch, touchpad works.

  [Regression Potential]
  Minimal. The it adds a device ID to intel-lpss-pci, so it's limited to
  one device.

  ---

  Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I
  tried in live mode and after full installation. I was able to connect
  an external mouse and a bluetooth mouse and both worked. I checked my
  xinput list and no sign:

  ⎡ Virtual core pointerid=2[master pointer
  (3)] ⎜   ↳ Virtual core XTEST pointer  id=4[slave
  pointer  (2)] ⎜   ↳ Wacom HID 50FE Finger touch id=12
  [slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen stylus
  id=13[slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen eraser
  id=16[slave  pointer  (2)] ⎜   ↳ byron's trackpad
  id=17[slave  pointer  (2)] ⎣ Virtual core keyboard
  id=3[master keyboard (2)]↳ Virtual core XTEST keyboard
  id=5[slave  keyboard (3)]↳ Power Button
  id=6[slave  keyboard (3)]↳ Video Bus
  id=7[slave  keyboard (3)]↳ Video Bus
  id=8[slave  keyboard (3)]↳ Power Button
  id=9[slave  keyboard (3)]↳ Apple Inc. Magic Keyboard
  id=10[slave  keyboard (3)]↳ EasyCamera
  id=11[slave  keyboard (3)]↳ Ideapad extra buttons
  id=14[slave  keyboard (3)]↳ AT Translated Set 2 keyboard
  id=15[slave  keyboard (3)]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-24-generic 4.10.0-24.28
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  byron  1794 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Jun 26 16:51:37 2017
  InstallationDate: Installed on 2017-06-26 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80X7
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed 
root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-24-generic N/A
   linux-backports-modules-4.10.0-24-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4MCN20WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo YOGA 720-15IKB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 720-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB:
  dmi.product.name: 80X7
  dmi.product.version: Lenovo YOGA 720-15IKB
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1720359] Re: Controller lockup detected on ProLiant DL380 Gen9 with P440 Controller

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

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

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

Title:
  Controller lockup detected on ProLiant DL380 Gen9 with P440 Controller

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

Bug description:
  Deploying ceph osd on Trusty/14.04 (LTS) with Ubuntu 4.4 series kernel
  on HP HW[1] system triggers "Controller lockup"[2]

  [1] - HW
  System Information
   Manufacturer: HP
   Product Name: ProLiant DL380 Gen9

  BIOS
    Vendor: HP
    Version: P89
    Release Date: 02/17/2017

  Smart Array Controller
   Smart Array P440 Controller

  [2] - /var/log/kern.log
  ...
  ceph-osd: 2017-09-26 15:34:42.259205 7f99a3d38700  1 heartbeat_map is_healthy 
'FileStore::op_tp thread 0x7f99ad69d700' had timed out after 60
  eph-osd: 2017-09-26 15:34:42.259215 7f99a553b700  1 heartbeat_map is_healthy 
'FileStore::op_tp thread 0x7f99ace9c700' had timed out after 60
  ceph-osd: 2017-09-26 15:34:42.259219 7f99a553b700  1 heartbeat_map is_healthy 
'FileStore::op_tp thread 0x7f99ad69d700' had timed out after 60
  hpsa :08:00.0: Controller lockup detected: 0x00130001 after 30
  hpsa :08:00.0: hpsa_send_abort_ioaccel2: Tag:0x:0190: unknown 
abort service response 0x00
  

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

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

[Kernel-packages] [Bug 1718397] Re: multipath -ll is not showing the disks which are actually multipath

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

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

Title:
  multipath -ll is not showing the disks which are actually multipath

Status in The Ubuntu-power-systems project:
  In Progress
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

Bug description:
  [Impact]

   * The number of available AIO contexts is severely limited
 on systems with a large number of possible CPUs 
 (e.g., IBM POWER8 processors w/ 20ish cores * 8 threads/core,
 and other multithreaded server-class processors).

   * This prevents application such as multipath/directio checker
 to provide all of the available devices to the system.

   * Other applications which depend on AIO can be affected/limited.

   * The patch fixes how aio increments the number of active contexts
 (seen in /proc/sys/fs/aio-nr) and checks that against the global
 limit (seen in /proc/sys/fs/aio-max-nr).

  [Test Case]

   * A synthetic test-case is attached (io_setup_v2.c) and demonstrated
 (original/patched kernels) in comment #4.

   * Trying to perform multipath discovery in debug/verbose mode
 (i.e., "multipath -v3" command) with sufficient number of 
 individual paths using the "directio" path checker should
 demonstrate the problem/solution as well (i.e., presence or
 not of "io_setup failed" messages).

  [Regression Potential]

   * Note the fix is trivial and has been tested by several users,
 even caused the introduction of a new test-case in "libaio";
 (but that can never be a strong enough reason for no more errors).

   * Applications which use aio with small "nr_events" value as argument
 to "io_setup()" now have access to a much larger number of aio contexts;
 but hopefully those apps are already only requesting what they need,
 not trying to get more and more.

   * Applications which relied in the _incorrect_ behavior of 
'/proc/sys/fs/aio-nr'
 being possibly greater than '/proc/sys/fs/aio-max-nr' might have problems,
 but those apps should be fixed.


  Problem Description
  =
  I am facing this issue for Texan Flash storage 840 disks which are coming 
from coho and salfish adapter

  coho adapter with 840 storage  is 3G disks and salfish adapter with
  840 is 12G disks

  I am able to see those disks in lsblk o/p but not in multipath -ll
  comamnd

  0004:01:00.0 Coho: Saturn-X  U78C9.001.WZS0060-P1-C6 
0x1090fa2a51f8  host10  Online
  0004:01:00.1 Coho: Saturn-X  U78C9.001.WZS0060-P1-C6 
0x1090fa2a51f9  host11  Online

  0005:09:00.0 Sailfish: QLogic 8GBU78C9.001.WZS0060-P1-C9 
0x2124ff787778  host2   Online
  0005:09:00.1 Sailfish: QLogic 8GBU78C9.001.WZS0060-P1-C9 
0x2124ff787779  host4   Online

  root@luckyv1:/dev/disk# multipath -ll | grep "size=3.0G" -B 1
  root@luckyv1:/dev/disk# multipath -ll | grep "size=12G" -B 1
  root@luckyv1:/dev/disk#

  == Comment: #3 - Luciano Chavez  - 2016-09-20 20:22:20 ==
  I edited /etc/multipath.conf and added
  verbosity 6

  to crank up the output and ran multipath -ll and saved it off to a
  text file (attached). All the using the directio checker failed and
  those using the tur checker seem to work.

  Sep 20 20:07:36 | loading //lib/multipath/libcheckdirectio.so checker
  Sep 20 20:07:36 | loading //lib/multipath/libprioconst.so prioritizer
  Sep 20 20:07:36 | Discover device 
/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/block/sdai
  Sep 20 20:07:36 | sdai: udev property ID_WWN whitelisted
  Sep 20 20:07:36 | sdai: not found in pathvec
  Sep 20 20:07:36 | sdai: mask = 0x25
  Sep 20 20:07:36 | sdai: dev_t = 66:32
  Sep 20 20:07:36 | open 
'/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/block/sdai/size'
  Sep 20 20:07:36 | sdai: size = 20971520
  Sep 20 20:07:36 | sdai: vendor = IBM
  Sep 20 20:07:36 | sdai: product = FlashSystem-9840
  Sep 20 20:07:36 | sdai: rev = 1442
  Sep 20 20:07:36 | sdai: h:b:t:l = 3:0:0:0
  Sep 20 20:07:36 | SCSI target 3:0:0 -> FC rport 3:0-2
  Sep 20 20:07:36 | sdai: tgt_node_name = 0x500507605e839800
  Sep 20 20:07:36 | open 
'/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/state'
  Sep 20 20:07:36 | sdai: path state = running
  Sep 20 20:07:36 | sdai: get_state
  Sep 20 20:07:36 | sdai: path_checker = directio (internal default)
  Sep 20 20:07:36 | sdai: checker timeout = 30 ms (internal default)
  Sep 20 20:07:36 |

[Kernel-packages] [Bug 1720977] Re: [Dell Docking IE][0bda:8153] Realtek USB Ethernet leads to system hang

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

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

Title:
  [Dell Docking IE][0bda:8153] Realtek USB Ethernet leads to system hang

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

Bug description:
  [Impact]
  There is a USB Ethernet port, 0bda:8153, on Dell IE Docking.
  After plugged in the docking, system hard hangs.

  [Fix]
  This issue has been fix after v4.11-rc4, so after bisecting the kernel, we 
found the first bad commit, and realized this issue is from Realtek USB 
Ethernet driver with a non-initialized list.
 98d068a r8152: fix the list rx_done may be used without initialization

  [Test Case]
  Verified on the Dell XPS and IE docking, and confirm this patch works.

  [Regression Potential]
  It's a one line patch and do the initialization of the list variable, there 
should be no any regression would be resulted from this.

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

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

[Kernel-packages] [Bug 1594214] Re: ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop)

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

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

Title:
  ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W
  laptop)

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

Bug description:
  SRU Justification

  [Impact]
  Touchpad on Gigabyte P57W laptop does not gets detected reliably.

  [Test Case]
  Touchpad not does not gets detected reliably.
  With the patch, it can get detected reliably.

  [Regression Potential]
  Minimal. The change limits to a single specific laptop.
  ---

  On my Gigabyte P57W laptop the ETPS/2 Elantech touchpad is
  inconsistently detected at boot. Trying mainline 4.6 kernel did not
  help.

  WORKAROUND: Add kernel boot parameter:
  i8042.kbdreset=1

  The device is id=17 on xinput below:
  $ xinput

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Kingsis Peripherals  Evoluent VerticalMouse 3   id=12   [slave  pointer 
 (2)]
  ⎜   ↳ Sunrex/JME Ghost Key Elimiantion Keyboard   id=14   [slave  pointer 
 (2)]
  ⎜   ↳ ETPS/2 Elantech Touchpadid=17   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Power Buttonid=10   [slave  
keyboard (3)]
  ↳ Sleep Buttonid=11   [slave  
keyboard (3)]
  ↳ Sunrex/JME Ghost Key Elimiantion Keyboard   id=13   [slave  
keyboard (3)]
  ↳ Chicony USB 2.0 Camera  id=15   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=16   [slave  
keyboard (3)]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.4.0-24-generic 4.4.0-24.43~14.04.1
  ProcVersionSignature: Ubuntu 4.4.0-24.43~14.04.1-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Mon Jun 20 10:56:33 2016
  InstallationDate: Installed on 2014-05-20 (761 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: linux-lts-xenial
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1713575] Re: Vlun resize request could fail with cxlflash driver

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

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

Title:
  Vlun resize request could fail with cxlflash driver

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

Bug description:
  == Comment: #0 - UMA KRISHNAN  - 2017-08-28 12:14:12 ==
  ---Problem Description---
  Recently a regression in cxlflash driver was identified and a fix has been 
upstreamed to  kernel.org. We would like to get that included in Xenial 16.04.3 
SRU (HWE v4.10 kernel). Even though regression patch is the very last one, I 
have also listed the missing patches in-between, that are minor and will be 
easier for further cxlflash updates to Xenial.

  eeac8cda2c957e156093933b860eec09e488fe15 scsi: cxlflash: return -EFAULT if 
copy_from_user() fails
  9ff870417e56b1fb7b15b2cda74de639d3cd8559 scsi: cxlflash: Fix an error 
handling path in 'cxlflash_disk_attach()'
  48a17ad5931c3832eec68411620bc3527021c193 scsi: cxlflash: Remove unnecessary 
existence check
  1a9e394154e34728f58c1f697b993aaaf89a4db2 scsi: cxlflash: Avoid double mutex 
unlock
  07a191f762a7b8d0db13c38036380927116e29bb scsi: cxlflash: Fix vlun resize 
failure in the shrink path
   
  ---Steps to Reproduce---
   Vlun resize request could fail after updating to a kernel that includes 
Commit 565180723294 ("scsi: cxlflash: SISlite updates to support 4 ports")

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

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

[Kernel-packages] [Bug 1696049] Re: xfstest sanity checks on seek operations fails

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

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

Title:
  xfstest sanity checks on seek operations fails

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

Bug description:
  == Comment: #0 - Harish Sriram 
  Issue:
  --
  xfstest fails with sanity checks on seek operations

  # uname -a
  Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 
12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Create a loop device with xfs filesystem
  2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd 
xfstests-dev
  3. make
  4. Create a local.config for running with created loop device
  5. Run xfstests-dev test  : ./check tests/generic/285 or ./check 
tests/generic/436

  The test 285 fails with following
  ...
  ...
  07. Test file with unwritten extents, only have dirty pages
  07.01 SEEK_HOLE expected 0 or 45056, got 0.   succ
  07.02 SEEK_HOLE expected 1 or 45056, got 1.   succ
  07.03 SEEK_DATA expected 40960 or 40960, got -1.  FAIL
  07.04 SEEK_DATA expected 40960 or 40960, got -1.  FAIL

  08. Test file with unwritten extents, only have unwritten pages
  08.01 SEEK_HOLE expected 0 or 45056, got 0.   succ
  08.02 SEEK_HOLE expected 1 or 45056, got 1.   succ
  08.03 SEEK_DATA expected 40960 or 40960, got -1.  FAIL
  08.04 SEEK_DATA expected 40960 or 40960, got -1.  FAIL

  The test 436 fails with 
  ...
  ...
  14. Test file with unwritten extents, small hole after pagevec dirty pages
  14.01 SEEK_HOLE expected 917504 or 4194304, got 3670016.  FAIL
  14.02 SEEK_HOLE expected 917504 or 4194304, got 3670016.  FAIL
  14.03 SEEK_HOLE expected 3670016 or 4194304, got 3670016. succ
  14.04 SEEK_DATA expected 0 or 0, got 0.   succ
  14.05 SEEK_DATA expected 1 or 1, got 1.   succ
  14.06 SEEK_DATA expected 2752512 or 2752512, got 2752512. succ

  seek sanity check failed!

  Full log is attached.

  == Comment: #6 - Harish Sriram

  commit 5375023ae1266553a7baa0845e82917d8803f48c
  Author: Jan Kara 
  Date:   Thu May 18 16:36:22 2017 -0700

  xfs: Fix missed holes in SEEK_HOLE implementation
  XFS SEEK_HOLE implementation could miss a hole in an unwritten extent as
  can be seen by the following command:
  
  xfs_io -c "falloc 0 256k" -c "pwrite 0 56k" -c "pwrite 128k 8k"
 -c "seek -h 0" file
  wrote 57344/57344 bytes at offset 0
  56 KiB, 14 ops; 0. sec (49.312 MiB/sec and 12623.9856 ops/sec)
  wrote 8192/8192 bytes at offset 131072
  8 KiB, 2 ops; 0. sec (70.383 MiB/sec and 18018.0180 ops/sec)
  Whence  Result
  HOLE139264
  
  Where we can see that hole at offset 56k was just ignored by SEEK_HOLE
  implementation. The bug is in xfs_find_get_desired_pgoff() which does
  not properly detect the case when pages are not contiguous.
  
  Fix the problem by properly detecting when found page has larger offset
  than expected.
  
  CC: sta...@vger.kernel.org
  Fixes: d126d43f631f996daeee5006714fed914be32368
  Signed-off-by: Jan Kara 
  Reviewed-by: Brian Foster 
  Reviewed-by: Darrick J. Wong 
  Signed-off-by: Darrick J. Wong 

  
  The above commit fixes the generic/436 test, but generic/285 still FAILS.

  The generic/285 failure is reproducible on most P8/P9 systems.

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

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

[Kernel-packages] [Bug 1706033] Re: [P9, Power NV][ WSP][Ubuntu 16.04.03] : perf hw breakpoint command results in call traces and system goes for reboot.

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

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

Title:
  [P9, Power NV][ WSP][Ubuntu 16.04.03] : perf hw breakpoint command
  results in call traces and system goes for reboot.

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

Bug description:
  == Comment: #0 - Shriya R. Kulkarni <> - 2017-06-14 04:38:16 ==
  Problem Description :
  =
   
  While running perftool - testsuite, the perf hw breakpoint fails and it 
result in call traces , hence system goes for reboot .

  Machine details :
  ==
  System : P9 , WSP , Bare metal.
  OS : Ubuntu 16.04.03
  uname -a : Linux ltc-wspoon3 4.10.0-23-generic #25~16.04.1-Ubuntu SMP Fri Jun 
9 10:43:34 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Install perf.
  2. git clone perftool-testsuite.
  https://github.com/rfmvh/perftool-testsuite
  3. Do make.
  4. Test fails at step : -- [ FAIL ] -- perf_stat :: test_hw_breakpoints :: 
kspace address execution mem:0xc035c020:x (command exitcode + output 
regexp parsing
  and call trace is seen as system goes for reboot.

  Call traces :
  ===

  ubuntu@ltc-wspoon3:~$ [1602513.518414] Unable to handle kernel paging request 
for data at address 0xc135d3b8
  [1602513.518553] Faulting instruction address: 0xc02869bc
  [1602513.518694] Oops: Kernel access of bad area, sig: 11 [#1]
  [1602513.518782] SMP NR_CPUS=2048 
  [1602513.518784] NUMA 
  [1602513.518842] PowerNV
  [1602513.518922] Modules linked in: vmx_crypto ofpart ipmi_powernv 
cmdlinepart ipmi_devintf powernv_flash ipmi_msghandler ibmpowernv opal_prd mtd 
at24 nvmem_core uio_pdrv_genirq uio autofs4 ast i2c_algo_bit drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops crc32c_vpmsum ttm drm tg3 ahci 
libahci
  [1602513.519399] CPU: 27 PID: 4069 Comm: sysctl Not tainted 4.10.0-22-generic 
#24
  [1602513.519524] task: c000203968c42c00 task.stack: c00020396571
  [1602513.519624] NIP: c02869bc LR: c03f7348 CTR: 
c0286990
  [1602513.519747] REGS: c000203965713a40 TRAP: 0300   Not tainted  
(4.10.0-22-generic)
  [1602513.519876] MSR: 90009033 
  [1602513.519889]   CR: 22002448  XER: 
  [1602513.520058] CFAR: c03f7344 DAR: c135d3b8 DSISR: 0040 
SOFTE: 1 
  [1602513.520058] GPR00: c03f7348 c000203965713cc0 c145d100 
c134af00 
  [1602513.520058] GPR04:  4ee50300 c000203965713d20 
c000203965713e00 
  [1602513.520058] GPR08:  c135d100  
c0b71020 
  [1602513.520058] GPR12: c0286990 c7b4f300  
 
  [1602513.520058] GPR16:    
 
  [1602513.520058] GPR20:    
0001 
  [1602513.520058] GPR24: 3fffc542f5a0 0400 c000203965713e00 
4ee50300 
  [1602513.520058] GPR28: c134af00  c03fee038800 
 
  [1602513.521280] NIP [c02869bc] dirty_ratio_handler+0x2c/0x90
  [1602513.521374] LR [c03f7348] proc_sys_call_handler+0x138/0x1c0
  [1602513.521481] Call Trace:
  [1602513.521526] [c000203965713cc0] [c000203965713d00] 0xc000203965713d00 
(unreliable)
  [1602513.521655] [c000203965713d00] [c03f7348] 
proc_sys_call_handler+0x138/0x1c0
  [1602513.521797] [c000203965713d70] [c03436ec] __vfs_read+0x3c/0x70
  [1602513.521907] [c000203965713d90] [c034516c] vfs_read+0xbc/0x1b0
  [1602513.522016] [c000203965713de0] [c0346dd8] SyS_read+0x68/0x110
  [1602513.522112] [c000203965713e30] [c000b184] system_call+0x38/0xe0
  [1602513.522243] Instruction dump:
  [1602513.522303] 6042 3c4c011d 38426770 7c0802a6 6000 7c0802a6 
fbc1fff0 fbe1fff8 
  [1602513.522445] f8010010 f821ffc1 3d22fff0 7c9f2378  4be66da9 
6000 3d22fff0 
  [1602513.522564] ---[ end trace 17c76e13e641d3c6 ]---
  [1602513.522657] 

  It goes for reboot :

  After booting to Ubuntu , I see series of call traces.

  Ubuntu 16.04.2 LTS ltc-wspoon3 hvc0

  ltc-wspoon3 login: [ 3476.626263] Unable to handle kernel paging request for 
data at address 0xc13ad438
  [ 3476.626422] Faulting instruction address: 0xc029a140
  [ 3476.626537] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 3476.626615] SMP NR_CPUS=2048 
  [ 3476.626616] NUMA 
  [ 3476.626673] PowerNV
  [ 3476.626746] Modules linked in: ipmi_powernv at24 ipmi_devintf nvmem_core 
ipmi_msghandler ofpart cmdlinepart powernv_flash mtd opal_prd vmx_crypto 
ibmpowernv uio_pdrv_genirq uio autofs4 ast

[Kernel-packages] [Bug 1698470] Re: [Zesty][Yakkety] rtl8192e bug fixes

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

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

Title:
  [Zesty][Yakkety] rtl8192e bug fixes

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Yakkety:
  Won't Fix
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  == SRU Justification ==
  The following commits needed to be added to the 4.10 and 4.4 kernels
  for stable operation of r8192e_pci driver. They are already in Xenial because 
  they came in with upstream stable updates.  However, upstream v4.10 is EOL so 
  these commits are being submitted via SRU request.

  All four commits are in mainline as of v4.12-rc2.

  == Fixes ==
  baabd567f87b ("staging: rtl8192e: rtl92e_fill_tx_desc fix write to mapped out 
memory.")
  867510bde14e ("staging: rtl8192e: fix 2 byte alignment of register BSSIDR.")
  90be652c9f15 ("staging: rtl8192e: rtl92e_get_eeprom_size Fix read size of 
EPROM_CMD.")
  95d93e271d92 ("staging: rtl8192e: GetTs Fix invalid TID 7 warning.")

  == Regression Potential ==
  These commits were also cc'd to stable and accepted, so additional upstream 
review
  was performed.

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


  
  The following commits needed to be added to 4.10 and 4.8 kernels for stable 
operation of r8192e_pci driver. They are already in 4.11 and in 4.4.

  commit baabd567f87be05330faa5140f72a91960e7405a upstream
  staging: rtl8192e: rtl92e_fill_tx_desc fix write to mapped out memory.

  commit 867510bde14e7b7fc6dd0f50b48f6753cfbd227a upstream.
  staging: rtl8192e: fix 2 byte alignment of register BSSIDR.

  commit 90be652c9f157d44b9c2803f902a8839796c090d upstream.
  staging: rtl8192e: rtl92e_get_eeprom_size Fix read size of EPROM_CMD.

  commit 95d93e271d920dfda369d4740b1cc1061d41fe7f upstream.
  staging: rtl8192e: GetTs Fix invalid TID 7 warning.

  ProblemType: Bug
  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/controlC1:  canaries-64   2006 F pulseaudio
   /dev/snd/controlC0:  canaries-64   2006 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri Jun 16 23:11:13 2017
  HibernationDevice: RESUME=UUID=f23ec6f5-7e6a-4559-a7f1-af640124e970
  InstallationDate: Installed on 2015-10-31 (594 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151027)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic 
root=UUID=48898cca-fae3-4cdc-9785-fc0b97f4cbd9 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-22-generic N/A
   linux-backports-modules-4.10.0-22-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   0: phy1: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  StagingDrivers: rtllib r8192e_pci
  UpgradeStatus: Upgraded to zesty on 2016-10-23 (236 days ago)
  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: N3700-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd04/18/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3700-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1693369] Re: 5U84 - ses driver isn't binding right - cannot blink lights on 1 of the 2 5u84

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

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

Title:
  5U84 - ses driver isn't binding right - cannot blink lights on 1 of
  the 2 5u84

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

Bug description:
  
  == SRU Justification ==
  This bug is resolved by commit 62e62ffd95539b9220894a7900a619e0f3ef4756.

  Without this patch, the symlink in sysfs which binds a SAS device to an 
enclosure 
  slot does not get created. This makes disk hotplug near impossible on large 
  JBOD disk drawers.

  Commit 62e62ffd95 is also needed in Xenial.  However, Xenial also needed some 
  prereq commits, so it's SRU will be sent separately.

  Commit 62e62ffd95 is in mainline as of 4.13-rc1.

  
  == Fix ==
  commit 62e62ffd95539b9220894a7900a619e0f3ef4756
  Author: Maurizio Lombardi 
  Date:   Tue Jun 27 11:53:27 2017 +0200

  scsi: ses: do not add a device to an enclosure if
  enclosure_add_links() fails.

  == Regression Potential ==
  This patch was also cc'd and applied to upstream stable, so there is 
  upstream confidence in it.

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


  
  This is a request to add the following upstream commit to both Ubuntu 16.04.1 
and 16.04.2:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/scsi/ses.c?id=9373eba6cfae48911b977d14323032cd5d161aae

  Without this patch, the symlink in sysfs which binds a SAS device to
  an enclosure slot does not get created. This makes disk hotplug near
  impossible on large JBOD disk drawers.

  You should be able to do:

  ls /sys/block/sdb/device/ | grep enclosure

  and see something like:

  enclosure_device:1

  If you cd to this directory, you can then access the SES controls for
  that slot to flash the LED to assist in locating the disk to replace a
  failed disk.

  Currently with 16.04.1 and 16.04.2, these symlinks are not getting
  created.

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

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

[Kernel-packages] [Bug 1706243] Re: Stranded with ENODEV after mdadm --readonly

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

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

Title:
  Stranded with ENODEV after mdadm --readonly

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

Bug description:
  == SRU Justification ==
  The bug reporter was trying to turn on the RAID journal.  One of the steps
  is to set the device readonly.  This did not work as planned, or indeed at
  all. After the first --readonly, all requests for the device report
  "No such device or address" until a reboot, though /proc/mdstat says the
  device is still there.

  This bug is fixed by mainline commit 065e519e71b2c1f41936cce75b46b5ab34adb588,
  which is in mainline as of 4.12-rc1.  The commit was also cc'd to stable, but
  upstream 4.10 is EOL, so that is the reason for the SRU request.

  == Fix ==
  commit 065e519e71b2c1f41936cce75b46b5ab34adb588
  Author: NeilBrown 
  Date:   Thu Apr 6 11:16:33 2017 +0800

  md: MD_CLOSING needs to be cleared after called md_set_readonly or
  do_md_stop

  == Regression Potential ==
  This commit was also cc'd to stable and accepted, so additional upstream 
review
  was performed.

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



  Please backport upstream fix.

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588
  ---
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   trent 10668 F...m pulseaudio
   /dev/snd/pcmC0D0p:   trent 10668 F...m pulseaudio
   /dev/snd/controlC0:  trent 10668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=848108cd-a607-494c-a6ea-626267ed0a12
  InstallationDate: Installed on 2014-12-23 (944 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p11p1 no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB 
Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=7afb765b-b26b-44cc-ace1-654320cd85b2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  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:  xenial xenial
  Uname: Linux 4.10.0-26-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to xenial on 2017-07-01 (24 days ago)
  UserGroups: adm audio cdrom dip glftpd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 06/16/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0808
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B250M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0808:bd06/16/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1713576] Re: More migrations with constant load

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

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

Title:
  More migrations with constant load

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

Bug description:
  == SRU Justification ==
  There is a significantly higher number of task migrations when the load is 
  fixed and not balanced across cores.

  Benchmark results are posted in the bug description and in the commits
  git log.

  This bug is resolved by mainline commit 
05b40e057734811ce452344fb3690d09965a7b6a, which is 
  in mailine as of 4.12-rc1.

  
  == Fix ==
  commit 05b40e057734811ce452344fb3690d09965a7b6a
  Author: Srikar Dronamraju 
  Date:   Wed Mar 22 23:27:50 2017 +0530

  sched/fair: Prefer sibiling only if local group is under-utilized

  == Regression Potential ==
  Medium, since this commit does touch the scheduler.  However, the commit only 
makes a change to 
  allow a local group to pull a task, if the source group has more number of 
  tasks than the local group.

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


  
  == Comment: #0 - PUVICHAKRAVARTHY RAMACHANDRAN  - 2017-08-06 13:44:45 ==
  ---Problem Description---
  Significantly higher number of task migrations when the load is fixed but not 
balanced across cores.

  ---uname output---
  Linux isvbos3 4.10.0-29-generic #33~16.04.1-Ubuntu SMP Tue Jul 25 18:17:06 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  ---Additional Hardware Info---
  Power9 dd2.0

  Machine Type = Power9

  ---Steps to Reproduce---
   Benchmark : Multithreaded - cpu intensive. The system had 2 socket/ 32 
cores/ SMT4 mode.

  When 64 threads was run - the migrations were less over 10s interval.
  when 80 threads were run - the migrations were very high.

  Ideally, it should have been very minimal, as the over all load was
  constant

  == Comment: #3 - SRIKAR DRONAMRAJU - 2017-08-11 06:56:47 ==
  As suspected (commit :  05b40e0577 : "sched/fair: Prefer sibiling only if 
local group is under-utilized")
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=05b40e0577
  should fix the problem

  Ran ' perf stat -a -r 5 -e sched:sched_migrate_task 
/home/srikar/work/ebizzy-0.3/ebizzy -t 35 -S 100'
  to detect the problem and verify the fix

  Here is perf stat without fix.

  Performance counter stats for 'system wide' (5 runs):

   7,758  sched:sched_migrate_task
  ( +-  1.28% )

   100.015658079 seconds time elapsed
  ( +-  0.00% )

  perf stat with fix.

  Performance counter stats for 'system wide' (5 runs):

     415  sched:sched_migrate_task
  ( +- 11.74% )

   100.016021787 seconds time elapsed
  ( +-  0.00% )

  git describe on upstream kernel says v4.11-rc2
  # git describe 05b40e0577
  v4.11-rc2-227-g05b40e0

  == Comment: #4 - SRIKAR DRONAMRAJU - 2017-08-11 07:05:37 ==
  Attaching the patch that needs to be applied to fix this bug.
  Verified that patch fixes the problem.

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

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

[Kernel-packages] [Bug 1718397] Re: multipath -ll is not showing the disks which are actually multipath

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

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

Title:
  multipath -ll is not showing the disks which are actually multipath

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

Bug description:
  [Impact]

   * The number of available AIO contexts is severely limited
 on systems with a large number of possible CPUs 
 (e.g., IBM POWER8 processors w/ 20ish cores * 8 threads/core,
 and other multithreaded server-class processors).

   * This prevents application such as multipath/directio checker
 to provide all of the available devices to the system.

   * Other applications which depend on AIO can be affected/limited.

   * The patch fixes how aio increments the number of active contexts
 (seen in /proc/sys/fs/aio-nr) and checks that against the global
 limit (seen in /proc/sys/fs/aio-max-nr).

  [Test Case]

   * A synthetic test-case is attached (io_setup_v2.c) and demonstrated
 (original/patched kernels) in comment #4.

   * Trying to perform multipath discovery in debug/verbose mode
 (i.e., "multipath -v3" command) with sufficient number of 
 individual paths using the "directio" path checker should
 demonstrate the problem/solution as well (i.e., presence or
 not of "io_setup failed" messages).

  [Regression Potential]

   * Note the fix is trivial and has been tested by several users,
 even caused the introduction of a new test-case in "libaio";
 (but that can never be a strong enough reason for no more errors).

   * Applications which use aio with small "nr_events" value as argument
 to "io_setup()" now have access to a much larger number of aio contexts;
 but hopefully those apps are already only requesting what they need,
 not trying to get more and more.

   * Applications which relied in the _incorrect_ behavior of 
'/proc/sys/fs/aio-nr'
 being possibly greater than '/proc/sys/fs/aio-max-nr' might have problems,
 but those apps should be fixed.


  Problem Description
  =
  I am facing this issue for Texan Flash storage 840 disks which are coming 
from coho and salfish adapter

  coho adapter with 840 storage  is 3G disks and salfish adapter with
  840 is 12G disks

  I am able to see those disks in lsblk o/p but not in multipath -ll
  comamnd

  0004:01:00.0 Coho: Saturn-X  U78C9.001.WZS0060-P1-C6 
0x1090fa2a51f8  host10  Online
  0004:01:00.1 Coho: Saturn-X  U78C9.001.WZS0060-P1-C6 
0x1090fa2a51f9  host11  Online

  0005:09:00.0 Sailfish: QLogic 8GBU78C9.001.WZS0060-P1-C9 
0x2124ff787778  host2   Online
  0005:09:00.1 Sailfish: QLogic 8GBU78C9.001.WZS0060-P1-C9 
0x2124ff787779  host4   Online

  root@luckyv1:/dev/disk# multipath -ll | grep "size=3.0G" -B 1
  root@luckyv1:/dev/disk# multipath -ll | grep "size=12G" -B 1
  root@luckyv1:/dev/disk#

  == Comment: #3 - Luciano Chavez  - 2016-09-20 20:22:20 ==
  I edited /etc/multipath.conf and added
  verbosity 6

  to crank up the output and ran multipath -ll and saved it off to a
  text file (attached). All the using the directio checker failed and
  those using the tur checker seem to work.

  Sep 20 20:07:36 | loading //lib/multipath/libcheckdirectio.so checker
  Sep 20 20:07:36 | loading //lib/multipath/libprioconst.so prioritizer
  Sep 20 20:07:36 | Discover device 
/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/block/sdai
  Sep 20 20:07:36 | sdai: udev property ID_WWN whitelisted
  Sep 20 20:07:36 | sdai: not found in pathvec
  Sep 20 20:07:36 | sdai: mask = 0x25
  Sep 20 20:07:36 | sdai: dev_t = 66:32
  Sep 20 20:07:36 | open 
'/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/block/sdai/size'
  Sep 20 20:07:36 | sdai: size = 20971520
  Sep 20 20:07:36 | sdai: vendor = IBM
  Sep 20 20:07:36 | sdai: product = FlashSystem-9840
  Sep 20 20:07:36 | sdai: rev = 1442
  Sep 20 20:07:36 | sdai: h:b:t:l = 3:0:0:0
  Sep 20 20:07:36 | SCSI target 3:0:0 -> FC rport 3:0-2
  Sep 20 20:07:36 | sdai: tgt_node_name = 0x500507605e839800
  Sep 20 20:07:36 | open 
'/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/state'
  Sep 20 20:07:36 | sdai: path state = running
  Sep 20 20:07:36 | sdai: get_state
  Sep 20 20:07:36 | sdai: path_checker = directio (internal default)
  Sep 20 20:07:36 | sdai: checker timeout = 30 ms (internal default)
  Sep 20 20:07:36 |

[Kernel-packages] [Bug 1716491] Re: New PMU fixes for marked events.

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

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

Title:
  New PMU fixes for marked events.

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

Bug description:
  == SRU Justification ==
  The current Zesty kernel does not enable marked events on Power9. The 
  following fixes are required:

  101dd590a7fa ("powerpc/perf: Avoid spurious PMU interrupts after idle")
  09539f9b1236 ("powerpc/perf: POWER9 PMU stops after idle workaround")

  Commit 101dd590a7fa was added to mainline in v4.13-rc3 and commit 
09539f9b1236 
  was added in v4.13-rc4.

  
  == Fixes ==
  commit 101dd590a7fa37954540cf3149a1c502c0acc524
  Author: Nicholas Piggin 
  Date:   Mon Jul 10 16:19:38 2017 +1000

  powerpc/perf: Avoid spurious PMU interrupts after idle

  commit 09539f9b123652e969894d6299ae0df2fe12cb5d
  Author: Nicholas Piggin 
  Date:   Thu Jul 20 11:53:22 2017 +1000

  powerpc/perf: POWER9 PMU stops after idle workaround

  
  == Regression Potential ==
  Low, since these commits are specific to powerpc.


  
  Dear Canonical,

  Please include the following fixes into Ubuntu Zesty (4.10) kernel.
  The current kernel does not enable marked events on Power9. And the
  following fixes are required:

  09539f9b1236 ("powerpc/perf: POWER9 PMU stops after idle workaround")
  101dd590a7fa ("powerpc/perf: Avoid spurious PMU interrupts after idle")

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

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

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

This change was made by a bot.

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

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [qtdemux0:sink:9073]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Received this error on boot up after logging in

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic i686
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2151 F pulseaudio
clownfish   2579 F pulseaudio
  Date: Mon Oct  9 18:24:40 2017
  Failure: oops
  InstallationDate: Installed on 2017-07-25 (76 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release i386 (20170412)
  MachineType: Dell Inc. Precision M90
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=7a8d75fd-cfc9-4561-a976-d3d78d36c120 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [qtdemux0:sink:9073]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0YD632
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/16/2008:svnDellInc.:pnPrecisionM90:pvr:rvnDellInc.:rn0YD632:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Precision M90
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1722360] [NEW] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [qtdemux0:sink:9073]

2017-10-09 Thread Clownfishy

Public bug reported:

Received this error on boot up after logging in

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-12-generic 4.13.0-12.13
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic i686
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.7-0ubuntu2
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm2151 F pulseaudio
  clownfish   2579 F pulseaudio
Date: Mon Oct  9 18:24:40 2017
Failure: oops
InstallationDate: Installed on 2017-07-25 (76 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release i386 (20170412)
MachineType: Dell Inc. Precision M90
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=7a8d75fd-cfc9-4561-a976-d3d78d36c120 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
SourcePackage: linux
Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [qtdemux0:sink:9073]
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/16/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0YD632
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/16/2008:svnDellInc.:pnPrecisionM90:pvr:rvnDellInc.:rn0YD632:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Precision M90
dmi.sys.vendor: Dell Inc.

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


** Tags: apport-kerneloops artful i386 kernel-driver-nouveau kernel-oops

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [qtdemux0:sink:9073]

Status in linux package in Ubuntu:
  New

Bug description:
  Received this error on boot up after logging in

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic i686
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2151 F pulseaudio
clownfish   2579 F pulseaudio
  Date: Mon Oct  9 18:24:40 2017
  Failure: oops
  InstallationDate: Installed on 2017-07-25 (76 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release i386 (20170412)
  MachineType: Dell Inc. Precision M90
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=7a8d75fd-cfc9-4561-a976-d3d78d36c120 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [qtdemux0:sink:9073]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0YD632
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/16/2008:svnDellInc.:pnPrecisionM90:pvr:rvnDellInc.:rn0YD632:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Precision M90
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1515513] Please test proposed package

2017-10-09 Thread Łukasz Zemczak

Hello Robin, or anyone else affected,

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

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

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

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

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

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

Status in dkms package in Ubuntu:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  New
Status in dkms source package in Zesty:
  Fix Committed
Status in initramfs-tools source package in Zesty:
  New
Status in dkms package in Debian:
  New

Bug description:
  [Impact]
  If a dkms package is installed which has REMAKE_INITRD or the same setting 
has be manually configured by a user then when a kernel is removed its possible 
for an ".old-dkms" file to be left in /boot with no associated kernel.

  [Test Case]
  On a system with two old kernels and one new kernel available in -updates:
  1) install r8168-dkms
  2) install the dkms module for the old kernel e.g. 'sudo dkms install -m 
r8168 -v 8.041.00 -k 4.4.0-31-generic'
  3) upgrade your kernel e.g. "sudo apt install linux-image-generic'
  4) sudo apt autoremove
  5) observe something like "initrd.img-4.4.0-31-generic.old-dkms" in /boot 
without a corresponding "initrd.img-4.4.0-31-generic"

  With the version of dkms in -proposed, the .old-dkms file will be
  removed when the kernel is auto removed.

  [Regression Potential]
  Somebody out there might expect the .old-dkms file to be kept, but that seems 
like an odd expectation.

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

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

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

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

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

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

2017-10-09 Thread Łukasz Zemczak

Hello Robin, or anyone else affected,

Accepted dkms into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/dkms/2.3-3ubuntu1.2 in
a few hours, and then in the -proposed repository.

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

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

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

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

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

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

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

Status in dkms package in Ubuntu:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  New
Status in dkms source package in Zesty:
  Fix Committed
Status in initramfs-tools source package in Zesty:
  New
Status in dkms package in Debian:
  New

Bug description:
  [Impact]
  If a dkms package is installed which has REMAKE_INITRD or the same setting 
has be manually configured by a user then when a kernel is removed its possible 
for an ".old-dkms" file to be left in /boot with no associated kernel.

  [Test Case]
  On a system with two old kernels and one new kernel available in -updates:
  1) install r8168-dkms
  2) install the dkms module for the old kernel e.g. 'sudo dkms install -m 
r8168 -v 8.041.00 -k 4.4.0-31-generic'
  3) upgrade your kernel e.g. "sudo apt install linux-image-generic'
  4) sudo apt autoremove
  5) observe something like "initrd.img-4.4.0-31-generic.old-dkms" in /boot 
without a corresponding "initrd.img-4.4.0-31-generic"

  With the version of dkms in -proposed, the .old-dkms file will be
  removed when the kernel is auto removed.

  [Regression Potential]
  Somebody out there might expect the .old-dkms file to be kept, but that seems 
like an odd expectation.

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

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

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

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

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

[Kernel-packages] [Bug 1721394] Re: Cannot open nvidia-settings on pc with a hybrid device (or use prime-select), missing python

2017-10-09 Thread Alberto Milone

** No longer affects: nvidia-settings (Ubuntu)

** Changed in: nvidia-prime (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Cannot open nvidia-settings on pc with a hybrid device (or use prime-
  select), missing python

Status in nvidia-prime package in Ubuntu:
  In Progress

Bug description:
  You would see -
  $ nvidia-settings
  ** Message: PRIME: Requires offloading
  ** Message: PRIME: is it supported? yes

  ** (nvidia-settings:1848): ERROR **: PRIME error: Failed to execute child 
process “/usr/bin/prime-select” (No such file or directory)
  Trace/breakpoint trap

  Additionally if trying to run prime-select you'd see -
  sudo: unable to execute /usr/bin/prime-select: No such file or directory

  One would need to go
   python3 /usr/bin/prime-select intel

  This is because the python package has been removed from image & isn't
  installed by either nvidia-settings or nvidia-prime.

  Please adjust this packages to either use python3 or dep to python

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nvidia-settings 367.35-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 17:16:44 2017
  InstallationDate: Installed on 2017-10-04 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2017-10-09 Thread Mauricio Faria de Oliveira

Joseph,

Again, thanks.

I had a few suggestions on the submitted backports, and observed a subtle 
problem in one of them.
If you prefer, I can submit the ones I have here, if that saves you some cycles.

cheers,
Mauricio

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

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

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
Status in linux source package in Artful:
  In Progress

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

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

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

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

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


  -- Problem Description --

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

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

  Some additional debugfs emulated instruction counters are added also.

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

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

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

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

[Kernel-packages] [Bug 1697450] Re: Gnome Shell hangs at startup

2017-10-09 Thread Alberto Donato

Is there any way I could debug the issue with 4.13?

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

Title:
  Gnome Shell hangs at startup

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to install from the daily Artful desktop image (20170612).

  After boot, the gnome session hangs at startup, while the "zoom"
  animation is being shown.

  I have an intel card:

  
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])
  Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller
  Flags: bus master, fast devsel, latency 0, IRQ 29
  Memory at f780 (64-bit, non-prefetchable) [size=4M]
  Memory at e000 (64-bit, prefetchable) [size=256M]
  I/O ports at f000 [size=64]
  [virtual] Expansion ROM at 000c [disabled] [size=128K]
  Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
  Capabilities: [d0] Power Management version 2
  Capabilities: [a4] PCI Advanced Features
  Kernel driver in use: i915
  Kernel modules: i915

  
  I'm not sure how to debug this further, but I had similar issues with the 
installer from Zesty as well (see 
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1681846)
  With Artful, at least it gets past the splash screen but then it hangs.

  Note that the system is currently running Yakkety with no issue.

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

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

[Kernel-packages] [Bug 1722335] Re: linux: -proposed tracker

** Also affects: linux (Ubuntu Trusty)
   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/1722335

Title:
  linux:  -proposed tracker

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

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

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

  backports: 1722336
  derivatives:

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

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

[Kernel-packages] [Bug 1722336] Re: linux-lts-trusty: -proposed tracker

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

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

Title:
  linux-lts-trusty:  -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1722335

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

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

[Kernel-packages] [Bug 1722337] Re: linux: -proposed tracker

** Also affects: linux (Ubuntu Precise)
   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/1722337

Title:
  linux:  -proposed tracker

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

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

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

  backports: 
  derivatives:

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

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

[Kernel-packages] [Bug 1722299] Re: linux: -proposed tracker

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-publish series:
  New
Status in Kernel SRU Workflow snap-qa-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

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

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

  backports: 1722301,1722302
  derivatives: 1722303,1722304,1722306,1722308,1722310

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

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

[Kernel-packages] [Bug 1722306] Re: linux-aws: -proposed tracker

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

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

Title:
  linux-aws:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-publish series:
  New
Status in Kernel SRU Workflow snap-qa-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1722299

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

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

[Kernel-packages] [Bug 1722302] Re: linux-aws: -proposed tracker

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

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

Title:
  linux-aws:  -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1722299

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

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

[Kernel-packages] [Bug 1722335] [NEW] linux: -proposed tracker

Public bug reported:

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: 1722336
derivatives:

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

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

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2017.10.09-1 kernel-sru-master-kernel trusty

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

** Tags added: kernel-release-tracking-bug-live

** Tags added: trusty

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee:

[Kernel-packages] [Bug 1722336] [NEW] linux-lts-trusty: -proposed tracker

Public bug reported:

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

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 1722335

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

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

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-lts-trusty (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1722335 kernel-sru-cycle-2017.10.09-1 precise

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

** Tags added: kernel-release-tracking-bug-live

** Tags added: precise

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided

[Kernel-packages] [Bug 1722337] [NEW] linux: -proposed tracker

Public bug reported:

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

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

backports: 
derivatives:

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

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

** Affects: kernel-sru-workflow/prepare-package-lbm
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2017.10.09-1 kernel-sru-master-kernel precise

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

** Tags added: kernel-release-tracking-bug-live

** Tags added: precise

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-lbm
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-lbm
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-lbm
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical

[Kernel-packages] [Bug 1721373] Re: linux: 4.13.0-15.16 -proposed tracker

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

** Changed in: kernel-development-workflow/promote-to-release
   Status: New => Confirmed

** Tags removed: block-proposed-artful

** Tags removed: block-proposed

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

Title:
  linux: 4.13.0-15.16 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Confirmed
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  This bug is for tracking the 4.13.0-15.16 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/1721373/+subscriptions

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

[Kernel-packages] [Bug 1721373] Re: linux: 4.13.0-15.16 -proposed tracker

2017-10-09 Thread Seth Forshee

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

Title:
  linux: 4.13.0-15.16 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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:
  Confirmed
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  This bug is for tracking the 4.13.0-15.16 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/1721373/+subscriptions

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

[Kernel-packages] [Bug 1722330] [NEW] linux: -proposed tracker

Public bug reported:

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: 1722331,1722333
derivatives: 1722334

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

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

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2017.10.09-1 kernel-sru-master-kernel zesty

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

** Tags added: kernel-release-tracking-bug-live

** Tags added: zesty

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-signed

[Kernel-packages] [Bug 1683587] Re: LSI Harpoon support in megaraid_sas module

2017-10-09 Thread Colin Tregenza Dancer

Is it possible to get a copy of a patched 17.04 iso?  I too am trying to
get an R740 system installed, and would be happy to give the code a
whirl.

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

Title:
  LSI Harpoon support in megaraid_sas module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Dell PERC H740 series RAID controllers, codename "Harpoon", are
  not supported in standard Ubuntu kernels.

  There is a series of kernel patches required to support these:
  http://www.mail-archive.com/linux-
  ker...@vger.kernel.org/msg1307314.html

  There is also a relevant follow-up series:
  https://www.spinics.net/lists/linux-scsi/msg104667.html especially
  patches 1 and 12.

  The relevant PCI IDs from the PCI database
  (http://pciids.sourceforge.net/v2.2/pci.ids) are:

  0016 MegaRAID Tri-Mode SAS3508
  1028 1fc9 PERC H840 Adapter
  1028 1fcb PERC H740P Adapter
  1028 1fcd PERC H740P Mini
  1028 1fcf PERC H740P Mini

  They should be supported from Xenial onwards. The upstream commit is
  going in for 4.11, so this will need to be backported to v4.4 and
  v4.10.

  I am working on SRU patches for this.

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

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

[Kernel-packages] [Bug 1721921] Re: Kernel issue

2017-10-09 Thread Rabin Adhikari

System suspends whenever I close two windows simultaneously. It is
highly unstable.

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

Title:
  Kernel issue

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using Ubuntu Budgie 17.10. System suspended suddenly. And when I
  tried to use twofinger scrolling, it didn't work so when I went to
  mouse and touchpad settings there was mouse instead of touchpad. I
  informed budgie team about this issue but they told me that this is a
  kernel issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  maverick   1331 F pulseaudio
   /dev/snd/controlC0:  maverick   1331 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Sat Oct  7 10:47:35 2017
  HibernationDevice: RESUME=UUID=d2fe9fee-24f6-4677-b908-a9d5f79f9f1d
  InstallationDate: Installed on 2017-10-02 (4 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha amd64 
(20170829)
  MachineType: Acer Aspire ES1-521
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed 
root=UUID=205738eb-f955-43c3-b330-8f6318222ad8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: BELLEMERE_BE
  dmi.board.vendor: Acer
  dmi.board.version: V1.06
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd08/11/2015:svnAcer:pnAspireES1-521:pvrV1.06:rvnAcer:rnBELLEMERE_BE:rvrV1.06:cvnAcer:ct9:cvrChassisVersion:
  dmi.product.family: BE
  dmi.product.name: Aspire ES1-521
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1722311] Re: softlockups/rcu sched

2017-10-09 Thread Ryan Harper

** Attachment added: "lspci-vnvn log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722311/+attachment/4965976/+files/lspci-vnvn.log

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

Title:
  softlockups/rcu sched

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1.$ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  2. $ apt-cache policy linux-image-virtual
  linux-image-virtual:
Installed: 4.13.0.11.12
Candidate: 4.13.0.11.12
Version table:
   *** 4.13.0.11.12 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3. System shutsdown cleanly, qemu exits non-zero

  4. System stays hung until testcase timesout.

  Single VCPU kvm guest on Artful host.

  Reached target Shutdown.
  [   60.036030] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
  [   88.036012] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
  [   96.920015] INFO: rcu_sched detected stalls on CPUs/tasks:
  [   96.920526](detected by 0, t=15002 jiffies, g=3321, c=3320, q=377)
  [   96.921161] All QSes seen, last rcu_sched kthread activity 15002 
(4294916526-4294901524), jiffies_till_next_fqs=1, root ->qsmask 0x0
  [   96.922409] rcu_sched kthread starved for 15002 jiffies! g3321 c3320 f0x2 
RCU_GP_WAIT_FQS(3) ->state=0x0
  [  124.036015] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
  [  152.036020] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
  [  180.036016] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
  [  208.036013] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
  [  236.036015] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
  [  264.036012] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
  [  276.940010] INFO: rcu_sched detected stalls on CPUs/tasks:
  [  276.940520](detected by 0, t=60007 jiffies, g=3321, c=3320, q=377)
  [  276.941088] All QSes seen, last rcu_sched kthread activity 60007 
(4294961531-4294901524), jiffies_till_next_fqs=1, root ->qsmask 0x0
  [  276.942165] rcu_sched kthread starved for 60007 jiffies! g3321 c3320 f0x2 
RCU_GP_WAIT_FQS(3) ->state=0x0

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: User Name 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct  9 15:06 seq
   crw-rw 1 root audio 116, 33 Oct  9 15:06 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Mon Oct  9 15:13:30 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-artful
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-artful:cvnQEMU:ct1:cvrpc-i440fx-artful:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-artful
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1722311] Re: softlockups/rcu sched

2017-10-09 Thread Ryan Harper

** Attachment added: "kernel version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722311/+attachment/4965975/+files/version.log

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

Title:
  softlockups/rcu sched

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1.$ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  2. $ apt-cache policy linux-image-virtual
  linux-image-virtual:
Installed: 4.13.0.11.12
Candidate: 4.13.0.11.12
Version table:
   *** 4.13.0.11.12 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3. System shutsdown cleanly, qemu exits non-zero

  4. System stays hung until testcase timesout.

  Single VCPU kvm guest on Artful host.

  Reached target Shutdown.
  [   60.036030] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
  [   88.036012] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
  [   96.920015] INFO: rcu_sched detected stalls on CPUs/tasks:
  [   96.920526](detected by 0, t=15002 jiffies, g=3321, c=3320, q=377)
  [   96.921161] All QSes seen, last rcu_sched kthread activity 15002 
(4294916526-4294901524), jiffies_till_next_fqs=1, root ->qsmask 0x0
  [   96.922409] rcu_sched kthread starved for 15002 jiffies! g3321 c3320 f0x2 
RCU_GP_WAIT_FQS(3) ->state=0x0
  [  124.036015] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
  [  152.036020] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
  [  180.036016] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
  [  208.036013] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
  [  236.036015] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
  [  264.036012] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
  [  276.940010] INFO: rcu_sched detected stalls on CPUs/tasks:
  [  276.940520](detected by 0, t=60007 jiffies, g=3321, c=3320, q=377)
  [  276.941088] All QSes seen, last rcu_sched kthread activity 60007 
(4294961531-4294901524), jiffies_till_next_fqs=1, root ->qsmask 0x0
  [  276.942165] rcu_sched kthread starved for 60007 jiffies! g3321 c3320 f0x2 
RCU_GP_WAIT_FQS(3) ->state=0x0

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: User Name 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct  9 15:06 seq
   crw-rw 1 root audio 116, 33 Oct  9 15:06 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Mon Oct  9 15:13:30 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-artful
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-artful:cvnQEMU:ct1:cvrpc-i440fx-artful:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-artful
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1722299] Re: linux: -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ backports: 1722301,1722302
+ derivatives: 1722303,1722304,1722306,1722308,1722310

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-publish series:
  New
Status in Kernel SRU Workflow snap-qa-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid

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: 1722301,1722302
  derivatives: 1722303,1722304,1722306,1722308,1722310

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

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

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

This change was made by a bot.

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

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

Title:
  softlockups/rcu sched

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1.$ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  2. $ apt-cache policy linux-image-virtual
  linux-image-virtual:
Installed: 4.13.0.11.12
Candidate: 4.13.0.11.12
Version table:
   *** 4.13.0.11.12 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3. System shutsdown cleanly, qemu exits non-zero

  4. System stays hung until testcase timesout.

  Single VCPU kvm guest on Artful host.

  Reached target Shutdown.
  [   60.036030] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
  [   88.036012] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
  [   96.920015] INFO: rcu_sched detected stalls on CPUs/tasks:
  [   96.920526](detected by 0, t=15002 jiffies, g=3321, c=3320, q=377)
  [   96.921161] All QSes seen, last rcu_sched kthread activity 15002 
(4294916526-4294901524), jiffies_till_next_fqs=1, root ->qsmask 0x0
  [   96.922409] rcu_sched kthread starved for 15002 jiffies! g3321 c3320 f0x2 
RCU_GP_WAIT_FQS(3) ->state=0x0
  [  124.036015] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
  [  152.036020] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
  [  180.036016] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
  [  208.036013] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
  [  236.036015] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
  [  264.036012] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
  [  276.940010] INFO: rcu_sched detected stalls on CPUs/tasks:
  [  276.940520](detected by 0, t=60007 jiffies, g=3321, c=3320, q=377)
  [  276.941088] All QSes seen, last rcu_sched kthread activity 60007 
(4294961531-4294901524), jiffies_till_next_fqs=1, root ->qsmask 0x0
  [  276.942165] rcu_sched kthread starved for 60007 jiffies! g3321 c3320 f0x2 
RCU_GP_WAIT_FQS(3) ->state=0x0

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: User Name 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct  9 15:06 seq
   crw-rw 1 root audio 116, 33 Oct  9 15:06 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Mon Oct  9 15:13:30 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-artful
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-artful:cvnQEMU:ct1:cvrpc-i440fx-artful:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-artful
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1722311] [NEW] softlockups/rcu sched

2017-10-09 Thread Ryan Harper

Public bug reported:

1.$ lsb_release -rd
Description:Ubuntu Artful Aardvark (development branch)
Release:17.10

2. $ apt-cache policy linux-image-virtual
linux-image-virtual:
  Installed: 4.13.0.11.12
  Candidate: 4.13.0.11.12
  Version table:
 *** 4.13.0.11.12 500
500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status


3. System shutsdown cleanly, qemu exits non-zero

4. System stays hung until testcase timesout.

Single VCPU kvm guest on Artful host.

Reached target Shutdown.
[   60.036030] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[   88.036012] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[   96.920015] INFO: rcu_sched detected stalls on CPUs/tasks:
[   96.920526]  (detected by 0, t=15002 jiffies, g=3321, c=3320, q=377)
[   96.921161] All QSes seen, last rcu_sched kthread activity 15002 
(4294916526-4294901524), jiffies_till_next_fqs=1, root ->qsmask 0x0
[   96.922409] rcu_sched kthread starved for 15002 jiffies! g3321 c3320 f0x2 
RCU_GP_WAIT_FQS(3) ->state=0x0
[  124.036015] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[  152.036020] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[  180.036016] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[  208.036013] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[  236.036015] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[  264.036012] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[  276.940010] INFO: rcu_sched detected stalls on CPUs/tasks:
[  276.940520]  (detected by 0, t=60007 jiffies, g=3321, c=3320, q=377)
[  276.941088] All QSes seen, last rcu_sched kthread activity 60007 
(4294961531-4294901524), jiffies_till_next_fqs=1, root ->qsmask 0x0
[  276.942165] rcu_sched kthread starved for 60007 jiffies! g3321 c3320 f0x2 
RCU_GP_WAIT_FQS(3) ->state=0x0

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-11-generic 4.13.0-11.12
ProcVersionSignature: User Name 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Oct  9 15:06 seq
 crw-rw 1 root audio 116, 33 Oct  9 15:06 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
Date: Mon Oct  9 15:13:30 2017
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
 
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-11-generic N/A
 linux-backports-modules-4.13.0-11-generic  N/A
 linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.10.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-artful
dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-artful:cvnQEMU:ct1:cvrpc-i440fx-artful:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-artful
dmi.sys.vendor: QEMU

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


** Tags: amd64 apport-bug artful curtin uec-images

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

Title:
  softlockups/rcu sched

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1.$ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  2. $ apt-cache policy linux-image-virtual
  linux-image-virtual:
Installed: 4.13.0.11.12
Candidate: 4.13.0.11.12
Version table:
   *** 4.13.0.11.12 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3. System shutsdown cleanly, qemu exits non-zero

  4. System stays hung until testcase timesout.

  Single VCPU kvm guest on Artful host.

  Reached target Shutdown.
  [   60.036030] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
  [   88.036012] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
  [   96.920015] INFO: rcu_sched detected stalls on CPUs/tasks:
  [   96.920526]

[Kernel-packages] [Bug 1711358] Re: 20170817 - ISO hangs on boot on qemu with splash screen enabled and qxl graphics driver

2017-10-09 Thread Seth Forshee

I ran a bisect which identifies this as the first commit with this bug:

3538e80a869b drm: qxl: Atomic phase 1: Implement mode_set_nofb

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

Title:
  20170817 - ISO hangs on boot on qemu with splash screen enabled and
  qxl graphics driver

Status in linux package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  Test Case
  1. Boot artful desktop 20170817 under qemu with qxl
  2. Wait until ubiquity-dm is displayed

  Expected result
  It boots

  Actual result
  It hangs on the splash screen and the dots below the Ubuntu logo are not 
blinking. If the option 'splash' is removed from the boot command line it boots 
successfully.

  It also boots successfully with -vga std but in this case the splash
  screen is in text mode not graphical unlike with the qxl driver.

  - It started with kernel 4.12.
  - It is still happening with kernel 4.13.
  - It only happens when booting from an ISO and not on an installed system.
  - It works with cirrus/vga, but not qxl
  - It works if nosplash is set (or splash removed from the boot command line)
  - It works on Xenial but not on Artful

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

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

[Kernel-packages] [Bug 1722302] [NEW] linux-aws: -proposed tracker

Public bug reported:

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

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 1722299

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

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

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1722299 kernel-sru-cycle-2017.10.09-1 trusty

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

** Tags added: kernel-release-tracking-bug-live

** Tags added: trusty

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru)

** Changed in: kernel-sru-workflow/promote-to-security
   Importance: Undecided => Medium

** Changed in:

[Kernel-packages] [Bug 1722306] [NEW] linux-aws: -proposed tracker

Public bug reported:

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

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 1722299

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

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

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/snap-certification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-publish
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-qa-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-beta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-candidate
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-edge
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-stable
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2017.10.09-1 kernel-sru-derivative-of-1722299 xenial

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

** Tags added: kernel-release-tracking-bug-live

** Tags added: xenial

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-publish
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-qa-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-beta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-candidate

[Kernel-packages] [Bug 1722294] Re: linux: -proposed tracker

** Changed in: kernel-sru-workflow
   Status: In Progress => Invalid

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => Invalid

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => Invalid

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => Invalid

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

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

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

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Invalid

** Changed in: kernel-sru-workflow/snap-certification-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/snap-publish
   Status: New => Invalid

** Changed in: kernel-sru-workflow/snap-qa-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: New => Invalid

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: New => Invalid

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: New => Invalid

** Changed in: kernel-sru-workflow/snap-release-to-stable
   Status: New => Invalid

** Changed in: kernel-sru-workflow/verification-testing
   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/1722294

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow snap-certification-testing series:
  Invalid
Status in Kernel SRU Workflow snap-publish series:
  Invalid
Status in Kernel SRU Workflow snap-qa-testing series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-beta series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-edge series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid

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

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Monday, 09. October 2017 15:03 UTC

  -- swm properties --
  phase: Packaging

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

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

[Kernel-packages] [Bug 1722299] [NEW] linux: -proposed tracker

Public bug reported:

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

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

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

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/snap-certification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-publish
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-qa-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-beta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-candidate
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-edge
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-stable
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2017.10.09-1 kernel-sru-master-kernel xenial

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

** Tags added: kernel-release-tracking-bug-live

** Tags added: xenial

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-publish
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-qa-testing
   Importance: Undecided
   Status: New

** Also affects:

[Kernel-packages] [Bug 1722294] Re: linux: -proposed tracker

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ kernel-stable-phase:Packaging
+ kernel-stable-phase-changed:Monday, 09. October 2017 15:03 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Monday, 09. October 2017 15:03 UTC
+ 
+ -- swm properties --
+ phase: Packaging

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow snap-certification-testing series:
  Invalid
Status in Kernel SRU Workflow snap-publish series:
  Invalid
Status in Kernel SRU Workflow snap-qa-testing series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-beta series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-edge series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid

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

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Monday, 09. October 2017 15:03 UTC

  -- swm properties --
  phase: Packaging

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

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

[Kernel-packages] [Bug 1722294] Re: linux: -proposed tracker

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-publish
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-qa-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-beta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-candidate
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-edge
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-stable
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru)

** Changed in: kernel-sru-workflow/promote-to-security
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru)

** Changed in: kernel-sru-workflow/promote-to-updates
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-updates
 Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru)

** Changed in: kernel-sru-workflow/regression-testing
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/security-signoff
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: (unassigned) => Canonical Security Team (canonical-security)

** Changed in: kernel-sru-workflow/snap-certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/snap-certification-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/snap-publish
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/snap-publish
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/snap-qa-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/snap-qa-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in:

[Kernel-packages] [Bug 1722287] Re: linux: -proposed tracker

** Changed in: kernel-sru-workflow
   Status: New => Invalid

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Invalid

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid

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

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

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

[Kernel-packages] [Bug 1722294] [NEW] linux: -proposed tracker

Public bug reported:

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

** Affects: kernel-sru-workflow
 Importance: Undecided
 Status: New

** Affects: kernel-sru-workflow/automated-testing
 Importance: Undecided
 Status: New

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


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live xenial

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

** Tags added: kernel-release-tracking-bug-live

** Tags added: xenial

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  New
Status in Kernel SRU Workflow automated-testing series:
  New
Status in linux package in Ubuntu:
  New

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

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

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

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

[Kernel-packages] [Bug 1722287] [NEW] linux: -proposed tracker

Public bug reported:

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

** Affects: kernel-sru-workflow
 Importance: Undecided
 Status: Invalid

** Affects: kernel-sru-workflow/automated-testing
 Importance: Undecided
 Status: Invalid

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


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live xenial

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

** Tags added: kernel-release-tracking-bug-live

** Tags added: xenial

** Also affects: kernel-sru-workflow/automated-testing
   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/1722287

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid

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

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

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

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

This change was made by a bot.

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

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

Title:
  [Apple Computer, Inc. MacBookPro2,2] suspend/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  on resume: OOPS

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  Annotation: This occurred during a previous suspend, and prevented the system 
from resuming properly.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1230 F pulseaudio
paul   1630 F pulseaudio
  Date: Mon Oct  9 16:06:32 2017
  DuplicateSignature: suspend/resume:Apple Computer, Inc. 
MacBookPro2,2:MBP22.88Z.00A5.B07.0708131242
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=50186c73-ecfa-4adb-b6f5-f58e122e4efa
  InstallationDate: Installed on 2016-05-09 (518 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterpreterPath: /usr/bin/python3.6
  MachineType: Apple Computer, Inc. MacBookPro2,2
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed 
root=UUID=6e9f60c0-8848-4ceb-bb41-857369395b7d ro nomodeset 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.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  Title: [Apple Computer, Inc. MacBookPro2,2] suspend/resume failure
  UpgradeStatus: Upgraded to artful on 2017-10-03 (6 days ago)
  UserGroups:
   
  dmi.bios.date: 08/13/07
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP22.88Z.00A5.B07.0708131242
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F42187C8
  dmi.board.vendor: Apple Computer, Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F42187C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP22.88Z.00A5.B07.0708131242:bd08/13/07:svnAppleComputer,Inc.:pnMacBookPro2,2:pvr1.0:rvnAppleComputer,Inc.:rnMac-F42187C8:rvrPVT:cvnAppleInc.:ct8:cvrMac-F42187C8:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro2,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Computer, Inc.

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

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

[Kernel-packages] [Bug 1722285] [NEW] [Apple Computer, Inc. MacBookPro2, 2] suspend/resume failure

2017-10-09 Thread Paul Oranje

Public bug reported:

on resume: OOPS

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-12-generic 4.13.0-12.13
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
Annotation: This occurred during a previous suspend, and prevented the system 
from resuming properly.
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1230 F pulseaudio
  paul   1630 F pulseaudio
Date: Mon Oct  9 16:06:32 2017
DuplicateSignature: suspend/resume:Apple Computer, Inc. 
MacBookPro2,2:MBP22.88Z.00A5.B07.0708131242
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=50186c73-ecfa-4adb-b6f5-f58e122e4efa
InstallationDate: Installed on 2016-05-09 (518 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
InterpreterPath: /usr/bin/python3.6
MachineType: Apple Computer, Inc. MacBookPro2,2
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 PATH=(custom, no user)
 LANG=nl_NL.UTF-8
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed 
root=UUID=6e9f60c0-8848-4ceb-bb41-857369395b7d ro nomodeset 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.
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-12-generic N/A
 linux-backports-modules-4.13.0-12-generic  N/A
 linux-firmware 1.169
SourcePackage: linux
Title: [Apple Computer, Inc. MacBookPro2,2] suspend/resume failure
UpgradeStatus: Upgraded to artful on 2017-10-03 (6 days ago)
UserGroups:
 
dmi.bios.date: 08/13/07
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP22.88Z.00A5.B07.0708131242
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F42187C8
dmi.board.vendor: Apple Computer, Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 8
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F42187C8
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP22.88Z.00A5.B07.0708131242:bd08/13/07:svnAppleComputer,Inc.:pnMacBookPro2,2:pvr1.0:rvnAppleComputer,Inc.:rnMac-F42187C8:rvrPVT:cvnAppleInc.:ct8:cvrMac-F42187C8:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro2,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Computer, Inc.

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


** Tags: amd64 apport-kerneloops artful resume suspend

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

Title:
  [Apple Computer, Inc. MacBookPro2,2] suspend/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  on resume: OOPS

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  Annotation: This occurred during a previous suspend, and prevented the system 
from resuming properly.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1230 F pulseaudio
paul   1630 F pulseaudio
  Date: Mon Oct  9 16:06:32 2017
  DuplicateSignature: suspend/resume:Apple Computer, Inc. 
MacBookPro2,2:MBP22.88Z.00A5.B07.0708131242
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=50186c73-ecfa-4adb-b6f5-f58e122e4efa
  InstallationDate: Installed on 2016-05-09 (518 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterpreterPath: /usr/bin/python3.6
  MachineType: Apple Computer, Inc. MacBookPro2,2
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed 
root=UUID=6e9f60c0-8848-4ceb-bb41-857369395b7d ro nomodeset 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.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage:

[Kernel-packages] [Bug 1722285] Re: [Apple Computer, Inc. MacBookPro2, 2] suspend/resume failure

2017-10-09 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  [Apple Computer, Inc. MacBookPro2,2] suspend/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  on resume: OOPS

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  Annotation: This occurred during a previous suspend, and prevented the system 
from resuming properly.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1230 F pulseaudio
paul   1630 F pulseaudio
  Date: Mon Oct  9 16:06:32 2017
  DuplicateSignature: suspend/resume:Apple Computer, Inc. 
MacBookPro2,2:MBP22.88Z.00A5.B07.0708131242
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=50186c73-ecfa-4adb-b6f5-f58e122e4efa
  InstallationDate: Installed on 2016-05-09 (518 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterpreterPath: /usr/bin/python3.6
  MachineType: Apple Computer, Inc. MacBookPro2,2
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed 
root=UUID=6e9f60c0-8848-4ceb-bb41-857369395b7d ro nomodeset 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.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  Title: [Apple Computer, Inc. MacBookPro2,2] suspend/resume failure
  UpgradeStatus: Upgraded to artful on 2017-10-03 (6 days ago)
  UserGroups:
   
  dmi.bios.date: 08/13/07
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP22.88Z.00A5.B07.0708131242
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F42187C8
  dmi.board.vendor: Apple Computer, Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F42187C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP22.88Z.00A5.B07.0708131242:bd08/13/07:svnAppleComputer,Inc.:pnMacBookPro2,2:pvr1.0:rvnAppleComputer,Inc.:rnMac-F42187C8:rvrPVT:cvnAppleInc.:ct8:cvrMac-F42187C8:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro2,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Computer, Inc.

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

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

[Kernel-packages] [Bug 1722282] [NEW] linux: -proposed tracker

Public bug reported:

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

** Affects: kernel-sru-workflow
 Importance: Undecided
 Status: Invalid

** Affects: kernel-sru-workflow/automated-testing
 Importance: Undecided
 Status: Invalid

** Affects: kernel-sru-workflow/certification-testing
 Importance: Undecided
 Status: Invalid

** Affects: kernel-sru-workflow/prepare-package
 Importance: Undecided
 Status: Invalid

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Undecided
 Status: Invalid

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Undecided
 Status: Invalid

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Undecided
 Status: Invalid

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Undecided
 Status: Invalid

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Undecided
 Status: Invalid

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


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live xenial

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

** Tags added: kernel-release-tracking-bug-live

** Tags added: xenial

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => Invalid

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Invalid

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => Invalid

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => Invalid

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

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

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

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in linux package in Ubuntu:
  Invalid

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

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

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

[Kernel-packages] [Bug 1722276] [NEW] linux: -proposed tracker

Public bug reported:

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

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Invalid

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: Invalid

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

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Invalid

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

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: Invalid

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: Invalid

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: Invalid

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Invalid

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: Invalid

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Invalid

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


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live xenial

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

** Tags added: kernel-release-tracking-bug-live

** Tags added: xenial

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

**

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

2017-10-09 Thread Tim De Pauw

Thanks!

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

Title:
  Plantronics P610 does not support sample rate reading

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

This change was made by a bot.

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

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

Title:
  No graphical boot with 4.4.0-96 and NVIDIA 475

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My computer (using XUbuntu 16.04) boots and works normally with kernel
  4.4.0-92 but upgrading to 4.4.0-96 prevents lightdm from starting. In
  fact, the GPU detection service fails.

  The problem also appears with proposed 4.4.0-97.

  I tested with mainline kernel 4.13. It boots to lightdm but it is
  difficult to exactly tell what happens as some modules for my hardware
  were not found/compiled/installed (as a result, I cannot connect to
  wifi with this kernel).

  GPU is GEForce 840M with proprietary nvidia 475 drivers (purged and
  reinstalled once).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  NonfreeKernelModules: wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yann   1476 F pulseaudio
   /dev/snd/controlC0:  yann   1476 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct  9 15:40:16 2017
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (448 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1722269] [NEW] No graphical boot with 4.4.0-96 and NVIDIA 475

2017-10-09 Thread YS1

Public bug reported:

My computer (using XUbuntu 16.04) boots and works normally with kernel
4.4.0-92 but upgrading to 4.4.0-96 prevents lightdm from starting. In
fact, the GPU detection service fails.

The problem also appears with proposed 4.4.0-97.

I tested with mainline kernel 4.13. It boots to lightdm but it is
difficult to exactly tell what happens as some modules for my hardware
were not found/compiled/installed (as a result, I cannot connect to wifi
with this kernel).

GPU is GEForce 840M with proprietary nvidia 475 drivers (purged and
reinstalled once).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-92-generic 4.4.0-92.115
ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
Uname: Linux 4.4.0-92-generic x86_64
NonfreeKernelModules: wl nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  yann   1476 F pulseaudio
 /dev/snd/controlC0:  yann   1476 F pulseaudio
CurrentDesktop: XFCE
Date: Mon Oct  9 15:40:16 2017
HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
InstallationDate: Installed on 2016-07-18 (448 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Dell Inc. Latitude E7450
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-92-generic N/A
 linux-backports-modules-4.4.0-92-generic  N/A
 linux-firmware1.157.12
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/05/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 0NC6G7
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7450
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  No graphical boot with 4.4.0-96 and NVIDIA 475

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My computer (using XUbuntu 16.04) boots and works normally with kernel
  4.4.0-92 but upgrading to 4.4.0-96 prevents lightdm from starting. In
  fact, the GPU detection service fails.

  The problem also appears with proposed 4.4.0-97.

  I tested with mainline kernel 4.13. It boots to lightdm but it is
  difficult to exactly tell what happens as some modules for my hardware
  were not found/compiled/installed (as a result, I cannot connect to
  wifi with this kernel).

  GPU is GEForce 840M with proprietary nvidia 475 drivers (purged and
  reinstalled once).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  NonfreeKernelModules: wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yann   1476 F pulseaudio
   /dev/snd/controlC0:  yann   1476 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct  9 15:40:16 2017
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (448 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1722261] [NEW] deadlock in mount umount and sync

2017-10-09 Thread alberto fiaschi

Public bug reported:

I use zfs vesion  0.6.5.6  on  Ubuntu 16.04.2 LTS . I have  many zombie process 
on auto-mount of snapshot and on sync !
903 process are   in deadlock.  i can't mount a new file system or snapshot . 
Partial output of ps alx |grep 'call_r D'  below .

what is the cause? what can I do ?

0 0   2371  1  20   0   6016   752 call_r D?  0:00 /bin/sync
0 0  15290  1  20   0   6016   676 call_r D?  0:00 /bin/sync
0 0  18919  1  20   0   6016   708 call_r D?  0:00 /bin/sync
0 0  27076  1  20   0   6016   808 call_r D?  0:00 /bin/sync
4 0  31976  1  20   0  22084  1344 call_r D?  0:00 umount 
-t zfs -n /samba/shares/Aat/.zfs/snapshot/2017-10-04_09.00.05--5d

error in kern.log:
9 13:20:28 zfs-cis kernel: [5368563.592834] WARNING: Unable to automount 
/samba/shares/Trapianti/.zfs/snapshot/2017-10-03_08.00.03--5d/pool_z2_samba/shares/Trapianti@2017-10-03_08.00.03--5d:
 256
Oct  9 13:20:28 zfs-cis kernel: [5368563.597868] WARNING: Unable to automount 
/samba/shares/Trapianti/.zfs/snapshot/2017-10-03_08.00.03--5d/pool_z2_samba/shares/Trapianti@2017-10-03_08.00.03--5d:
 256
Oct  9 13:20:28 zfs-cis kernel: [5368563.601730] WARNING: Unable to automount 
/samba/shares/Trapianti/.zfs/snapshot/2017-10-03_08.00.03--5d/pool_z2_samba/shares/Trapianti@2017-10-03_08.00.03--5d:
 256
Oct  9 13:22:57 zfs-cis kernel: [5368713.187001] WARNING: Unable to automount 
/samba/shares/Trapianti/.zfs/snapshot/2017-10-03_10.00.03--5d/pool_z2_samba/shares/Trapianti@2017-10-03_10.00.03--5d:
 256
Oct  9 13:22:57 zfs-cis kernel: [5368713.13] WARNING: Unable to automount 
/samba/shares/Cardiologia2/.zfs/snapshot/2017-10-03_12.00.03--5d/pool_z2_samba/shares/Cardiologia2@2017-10-03_12.00.03--5d:
 256
Oct  9 13:22:57 zfs-cis kernel: [5368713.15] WARNING: Unable to automount 
/samba/shares/Trapianti/.zfs/snapshot/2017-10-03_14.00.04--5d/pool_z2_samba/shares/Trapianti@2017-10-03_14.00.04--5d:
 256
Oct  9 13:22:57 zfs-cis kernel: [5368713.189005] WARNING: Unable to automount 
/samba/shares/Aat/.zfs/snapshot/2017-10-03_20.00.04--5d/pool_z2_samba/shares/Aat@2017-10-03_20.00.04--5d:
 256
Oct  9 13:22:57 zfs-cis kernel: [5368713.190105] WARNING: Unable to automount 
/samba/shares/Trapianti/.zfs/snapshot/2017-10-03_10.00.03--5d/pool_z2_samba/shares/Trapianti@2017-10-03_10.00.03--5d:
 256
Oct  9 13:22:57 zfs-cis kernel: [5368713.192847] WARNING: Unable to automount 
/samba/shares/Trapianti/.zfs/snapshot/2017-10-03_10.00.03--5d/pool_z2_samba/shares/Trapianti@2017-10-03_10.00.03--5d:
 256
Oct  9 13:22:57 zfs-cis kernel: [5368713.193617] WARNING: Unable to automount 
/samba/shares/Trapianti/.zfs/snapshot/2017-10-03_14.00.04--5d/pool_z2_samba/shares/Trapianti@2017-10-03_14.00.04--5d:
 256
Oct  9 13:22:57 zfs-cis kernel: [5368713.198096] WARNING: Unable to automount 
/samba/shares/Trapianti/.zfs/snapshot/2017-10-03_14.00.04--5d/pool_z2_samba/shares/Trapianti@2017-10-03_14.00.04--5d:
 256


in syslog :

Oct  9 12:22:12 zfs-cis systemd[1]: Got message type=method_call sender=n/a 
destination=org.freedesktop.systemd1 
object=/org/freedesktop/systemd1/unit/samba_2dshares_2dChtrapianti_2emount 
interface=org.freedesktop.DBus.Properties member=GetAll cookie=155 
reply_cookie=0 error=n/a
Oct  9 12:22:12 zfs-cis systemd[1]: Got message type=method_call sender=n/a 
destination=org.freedesktop.systemd1 
object=/org/freedesktop/systemd1/unit/samba_2dshares_2dLaboratorio_5fTrapianti_2emount
 interface=org.freedesktop.DBus.Properties member=GetAll cookie=202 
reply_cookie=0 error=n/a
Oct  9 12:22:12 zfs-cis systemd[1]: Got message type=method_call sender=n/a 
destination=org.freedesktop.systemd1 
object=/org/freedesktop/systemd1/unit/samba_2dshares_2dProgettoTrapianti_2emount
 interface=org.freedesktop.DBus.Properties member=GetAll cookie=260 
reply_cookie=0 error=n/a
Oct  9 12:22:12 zfs-cis systemd[1]: Got message type=method_call sender=n/a 
destination=org.freedesktop.systemd1 
object=/org/freedesktop/systemd1/unit/samba_2dshares_2dTrapianti_2emount 
interface=org.freedesktop.DBus.Properties member=GetAll cookie=291 
reply_cookie=0 error=n/a
Oct  9 12:22:13 zfs-cis systemd[1]: Got message type=method_call sender=n/a 
destination=org.freedesktop.systemd1 
object=/org/freedesktop/systemd1/unit/samba_2dshares_2dChtrapianti_2emount 
interface=org.freedesktop.DBus.Properties member=GetAll cookie=155 
reply_cookie=0 error=n/a
Oct  9 12:22:13 zfs-cis systemd[1]: Got message type=method_call sender=n/a 
destination=org.freedesktop.systemd1 
object=/org/freedesktop/systemd1/unit/samba_2dshares_2dLaboratorio_5fTrapianti_2emount
 interface=org.freedesktop.DBus.Properties member=GetAll cookie=202 
reply_cookie=0 error=n/a
Oct  9 12:22:13 zfs-cis systemd[1]: Got message type=method_call sender=n/a 
destination=org.freedesktop.systemd1 
object=/org/freedesktop/systemd1/unit/samba_2dshares_2dProgettoTrapianti_2emount
 interface=org.freedesktop.DBus.Properties

[Kernel-packages] [Bug 172937] Re: SQUASHFS error while booting from live cd

2017-10-09 Thread midobona

am using ubuntu server 14.04.1 and i want edit filesystem.squashfs
after installed squashfs-tools and unsquashfs and edit filesystem and
mksquashfs and build iso i get this error

base-installer: info: Using squashfs support for 
/cdrom/install/filesystem.squashfs
anna-install: Installing squashfs-modules
anna[21857]: DEBUG: resolver (kernel-image-4.2.0-16-generic-di): package 
doesn't exist (ignored)
anna[21857]: DEBUG: retrieving squashfs-modules-4.2.0-16-generic-di 4.2.0-16.19
kernel: [44.008353] squashfs: version 4.0 (2009/01/31) Phillip Lougher
main-menu[3537]: (process:21801): getfattr: .: Operation not supported
main-menu[3537]: (process:21801): getfattr: ./bin: Operation not supported
main-menu[3537]: (process:21801): getfattr: ./bin/bunzip2: Operation not 
supported
main-menu[3537]: (process:21801): getfattr: ./bin/bzcat: Operation not supported
main-menu[3537]: (process:21801): getfattr: ./bin/bzcmp: Operation not supported

i think this error becouse kernel version not equal squashfs-tools

is this right ?

and i want install right package squashfs-tools support kernel ubuntu-
server 14.04.1

and sorry if my english is bad

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

Title:
  SQUASHFS error while booting from live cd

Status in linux package in Ubuntu:
  Won't Fix
Status in linux package in Fedora:
  Won't Fix
Status in linux package in Mandriva:
  Invalid

Bug description:
  Some users have reported being unable to boot from the Ubuntu LiveCD,
  due to SquasFS errors like this:

  [  135.292409] SQUASHFS error: sb_bread failed reading block 0x9d7f3
  [  135.292411] SQUASHFS error: Unable to read fragment cache block [275faa28]
  [  135.292413] SQUASHFS error: Unable to read page, block 275faa28, size 23a7

  These errors can be due to a variety of reasons:

  * bad media (solution: try burning the iso image to a new disc)
  * a bad dvd drive (solution: if possible, try using a different cd/dvd 
drive)
  * bad memory modules (solution: use memtest86+ to check your memory)
  * a corrupted iso image (solution: run an md5 checksum, and if they don't 
match, download the iso image again)
  * an optical drive connected via SATA instead of PATA and running in 
Enhanced mode (solution: change the IDE configuration to "compatible" in the 
BIOS)

  This is all described in more detail here:
  https://help.ubuntu.com/community/SquashfsErrors

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

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

[Kernel-packages] [Bug 1664545] Re: In Ubuntu17.04 as Kvm guest : While trigger kdump console hung having call traces

2017-10-09 Thread Andrew Cloke

Following comment #8, closing bug.

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

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

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

Title:
  In Ubuntu17.04 as Kvm guest  : While trigger kdump console hung having
  call traces

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

Bug description:
  In ubuntu17.04 as KVM guest on ubuntu KVM Host and trying kdump on
  guest while kdump process  console got hung having call traces

  
  Reproducible Step:

  1- Install Ubuntu17.04 as kvm guest  on ubuntu kvm host 
  2- configure kdump 
  3- trigger kdump 

  Expected Result :

  Kdump should capture

  Actual Result :

  Kdump console hung having continuous call traces

  LOG:

  [0.488534] Freeing unused kernel memory: 4416K (c8e8 - 
c92d)
  [0.488725] This architecture does not have kernel memory protection.
  Loading, please wait...
  starting version 232
  [0.501616] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.501830] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.501981] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.502162] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.502254] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.502433] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.503188] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.503270] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.503978] random: systemd-udevd: uninitialized urandom read (16 bytes 
read)
  [0.504218] random: systemd-udevd: uninitialized urandom read (16 bytes 
read)
  [  242.663388] INFO: task systemd-udevd:151 blocked for more than 120 seconds.
  [  242.663514]   Not tainted 4.9.0-15-generic #16-Ubuntu
  [  242.663553] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.663755] systemd-udevd   D0   151145 0x00040002
  [  242.663795] Call Trace:
  [  242.663868] [c0001fe4ecd0] [c801c3a0] __switch_to+0x2e0/0x4c0
  [  242.663964] [c0001fe4ed30] [c8b19398] __schedule+0x2f8/0x990
  [  242.664076] [c0001fe4ee10] [c8b19a78] schedule+0x48/0xc0
  [  242.664179] [c0001fe4ee40] [c8b1de54] 
schedule_timeout+0x274/0x470
  [  242.664334] [c0001fe4ef30] [c8b19010] 
io_schedule_timeout+0xd0/0x160
  [  242.664502] [c0001fe4ef80] [c8b1a720] bit_wait_io+0x30/0x90
  [  242.664618] [c0001fe4efb0] [c8b1a168] __wait_on_bit+0xf8/0x170
  [  242.664754] [c0001fe4f000] [c824b238] 
wait_on_page_bit+0x98/0xb0
  [  242.664847] [c0001fe4f060] [c824d60c] 
do_read_cache_page+0x21c/0x4e0
  [  242.665008] [c0001fe4f0d0] [c859be78] 
read_dev_sector+0xb8/0x140
  [  242.665126] [c0001fe4f100] [c85a5d88] 
read_lba.isra.0+0x148/0x250
  [  242.665259] [c0001fe4f170] [c85a652c] efi_partition+0x12c/0x830
  [  242.665363] [c0001fe4f2e0] [c859e768] 
check_partition+0x158/0x2d0
  [  242.665469] [c0001fe4f360] [c859c760] 
rescan_partitions+0xe0/0x390
  [  242.665552] [c0001fe4f430] [c8371828] __blkdev_get+0x358/0x490
  [  242.665669] [c0001fe4f4a0] [c8372b50] blkdev_get+0x1a0/0x4a0
  [  242.665784] [c0001fe4f550] [c8599538] 
device_add_disk+0x4a8/0x500
  [  242.665894] [c0001fe4f600] [d0511cc8] 
virtblk_probe+0x560/0x928 [virtio_blk]
  [  242.665983] [c0001fe4f6c0] [c8687700] 
virtio_dev_probe+0x1d0/0x350
  [  242.666050] [c0001fe4f700] [c8716f30] 
driver_probe_device+0x240/0x540
  [  242.666116] [c0001fe4f790] [c871738c] 
__driver_attach+0x15c/0x160
  [  242.666174] [c0001fe4f810] [c87138ec] 
bus_for_each_dev+0x8c/0xf0
  [  242.666232] [c0001fe4f860] [c87162e4] driver_attach+0x34/0x50
  [  242.666289] [c0001fe4f880] [c8715a78] 
bus_add_driver+0x238/0x380
  [  242.666345] [c0001fe4f910] [c871829c] 
driver_register+0x9c/0x180
  [  242.666403] [c0001fe4f980] [c8686abc] 
register_virtio_driver+0x4c/0x60
  [  242.666470] [c0001fe4f9a0] [d0512114] init+0x84/0xd4 
[virtio_blk]
  [  242.666527] [c0001fe4fa10] [c800dde8] 
do_one_initcall+0x68/0x1d0
  [  242.666584] [c0001fe4fad0] [c8b28e00] do_init_module+0x90/0x244
  [  242.43] [c0001fe4fb60] [c8184794] load_module+0x1614/0x17a0
  [  242.666701] [c0001fe4fd30] [c8184c60] 
SyS_finit_module+0xf0/0x170
  [

[Kernel-packages] [Bug 1703339] Re: Unable to install Ubuntu on the NVMe disk under VMD PCI domain

2017-10-09 Thread Tomasz Majchrzak

The disks under VMD controller are visible in the installer, it is
possible to install the system, however vmd.ko is not added to initrd so
the system cannot boot.

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

Title:
  Unable to install Ubuntu on the NVMe disk under VMD PCI domain

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

Bug description:
  It is not possible to install Ubuntu on the NVMe disk under VMD
  (Volume Management Device) PCI domain. The disk is not visible in the
  installer because VMD module is not available at this stage.

  I'm raising it against kernel package as I have impression VMD module
  must be included in linux-image dpkg package, not linux-image-extra.

  Please also assure VMD module gets included in initramfs by installer
  (if necessary).

  For more information about VMD please see bug 1591806.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-generic 4.10.0.26.28
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   tomasz 1659 F...m pulseaudio
   /dev/snd/controlC0:  tomasz 1659 F pulseaudio
   /dev/snd/timer:  tomasz 1659 f pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jul 10 10:40:20 2017
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2017-07-06 (3 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170702)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 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-26-generic 
root=/dev/mapper/hostname--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.167
  RfKill:
   
  SourcePackage: linux
  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/1703339/+subscriptions

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

[Kernel-packages] [Bug 1542743] Re: Bluetooth: Patch file not found ar3k/AthrBT_0x00000200.dfu

2017-10-09 Thread Pilot6

This DKMS package was never supposed to work on any other kernel but the
4.4.

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

Title:
  Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Since some Versions of Linux Kernel and Ubuntu Releases this problem
  exists.

  I am now running ubuntu 16.04 prerelease and still have the same
  problem.

  Bluetooth does not work with the atheros device on  msi gt 72 2qd
  notebook.

  WORKAROUND FOR [0CF3:3004] DEVICE ONLY with kernel 4.4:

  sudo apt install dkms
  wget 
https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files/btusb-lp1542743-dkms_0.1_all.deb
  sudo dpkg -i btusb-lp1542743-dkms_0.1_all.deb

  FOR KERNEL 4.8 A WORKAROUND DKMS DEB IS

  https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files
  /btusb-lp1542743-dkms_0.2~4.8_all.deb

  dmesg | grep Bluetooth:
  [2.655360] Bluetooth: Core ver 2.21
  [2.655373] Bluetooth: HCI device and connection manager initialized
  [2.655377] Bluetooth: HCI socket layer initialized
  [2.655379] Bluetooth: L2CAP socket layer initialized
  [2.655385] Bluetooth: SCO socket layer initialized
  [6.612790] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [6.612794] Bluetooth: BNEP filters: protocol multicast
  [6.612798] Bluetooth: BNEP socket layer initialized
  [9.016880] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu
  [9.016882] Bluetooth: Loading patch file failed

  hwinfo | grep Bluetooth:
  <6>[6.612790] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    <6>[6.612794] Bluetooth: BNEP filters: protocol multicast
    <6>[6.612798] Bluetooth: BNEP socket layer initialized
    <3>[9.016880] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu
    <3>[9.016882] Bluetooth: Loading patch file failed
  60: USB 00.0: 11500 Bluetooth Device
    Model: "Atheros AR3012 Bluetooth 4.0"
    Device: usb 0x3004 "AR3012 Bluetooth 4.0"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.36-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Sun Feb  7 00:38:04 2016
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  InstallationDate: Installed on 2015-10-24 (105 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: bnep btusb bluetooth
  MachineType: Micro-Star International Co., Ltd. GT72 2QD
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic 
root=UUID=f7880b23-39b5-423a-bdbf-62b111783450 ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2016-02-02 (4 days ago)
  dmi.bios.date: 12/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10I
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10I:bd12/19/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QD:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QD
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  hciconfig:

  rfkill:
   0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no

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

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

[Kernel-packages] [Bug 1542743] Re: Bluetooth: Patch file not found ar3k/AthrBT_0x00000200.dfu

2017-10-09 Thread Adam Ryczkowski

The patch doesn't work for the 4.13 kernel from mainline ppa:

$ cat /var/lib/dkms/btusb-lp1542743/0.2~4.8/build/make.log
DKMS make.log for btusb-lp1542743-0.2~4.8 for kernel 4.13.0-041300-generic 
(x86_64)
pon, 9 paź 2017, 13:00:15 CEST
make: Entering directory '/usr/src/linux-headers-4.13.0-041300-generic'
  AR  /var/lib/dkms/btusb-lp1542743/0.2~4.8/build/built-in.o
  CC [M]  /var/lib/dkms/btusb-lp1542743/0.2~4.8/build/btusb.o
/var/lib/dkms/btusb-lp1542743/0.2~4.8/build/btusb.c: In function 
‘inject_cmd_complete’:
/var/lib/dkms/btusb-lp1542743/0.2~4.8/build/btusb.c:1825:2: warning: 
dereferencing ‘void *’ pointer
  *skb_put(skb, 1) = 0x00;
  ^
/var/lib/dkms/btusb-lp1542743/0.2~4.8/build/btusb.c:1825:2: error: invalid use 
of void expression
/var/lib/dkms/btusb-lp1542743/0.2~4.8/build/btusb.c: In function 
‘alloc_diag_urb’:
/var/lib/dkms/btusb-lp1542743/0.2~4.8/build/btusb.c:2697:2: warning: 
dereferencing ‘void *’ pointer
  *skb_put(skb, 1) = 0xf0;
  ^
/var/lib/dkms/btusb-lp1542743/0.2~4.8/build/btusb.c:2697:2: error: invalid use 
of void expression
/var/lib/dkms/btusb-lp1542743/0.2~4.8/build/btusb.c:2698:2: warning: 
dereferencing ‘void *’ pointer
  *skb_put(skb, 1) = enable;
  ^
/var/lib/dkms/btusb-lp1542743/0.2~4.8/build/btusb.c:2698:2: error: invalid use 
of void expression
scripts/Makefile.build:308: recipe for target 
'/var/lib/dkms/btusb-lp1542743/0.2~4.8/build/btusb.o' failed
make[1]: *** [/var/lib/dkms/btusb-lp1542743/0.2~4.8/build/btusb.o] Error 1
Makefile:1512: recipe for target 
'_module_/var/lib/dkms/btusb-lp1542743/0.2~4.8/build' failed
make: *** [_module_/var/lib/dkms/btusb-lp1542743/0.2~4.8/build] Error 2
make: Leaving directory '/usr/src/linux-headers-4.13.0-041300-generic'

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

Title:
  Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Since some Versions of Linux Kernel and Ubuntu Releases this problem
  exists.

  I am now running ubuntu 16.04 prerelease and still have the same
  problem.

  Bluetooth does not work with the atheros device on  msi gt 72 2qd
  notebook.

  WORKAROUND FOR [0CF3:3004] DEVICE ONLY with kernel 4.4:

  sudo apt install dkms
  wget 
https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files/btusb-lp1542743-dkms_0.1_all.deb
  sudo dpkg -i btusb-lp1542743-dkms_0.1_all.deb

  FOR KERNEL 4.8 A WORKAROUND DKMS DEB IS

  https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files
  /btusb-lp1542743-dkms_0.2~4.8_all.deb

  dmesg | grep Bluetooth:
  [2.655360] Bluetooth: Core ver 2.21
  [2.655373] Bluetooth: HCI device and connection manager initialized
  [2.655377] Bluetooth: HCI socket layer initialized
  [2.655379] Bluetooth: L2CAP socket layer initialized
  [2.655385] Bluetooth: SCO socket layer initialized
  [6.612790] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [6.612794] Bluetooth: BNEP filters: protocol multicast
  [6.612798] Bluetooth: BNEP socket layer initialized
  [9.016880] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu
  [9.016882] Bluetooth: Loading patch file failed

  hwinfo | grep Bluetooth:
  <6>[6.612790] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    <6>[6.612794] Bluetooth: BNEP filters: protocol multicast
    <6>[6.612798] Bluetooth: BNEP socket layer initialized
    <3>[9.016880] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu
    <3>[9.016882] Bluetooth: Loading patch file failed
  60: USB 00.0: 11500 Bluetooth Device
    Model: "Atheros AR3012 Bluetooth 4.0"
    Device: usb 0x3004 "AR3012 Bluetooth 4.0"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.36-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Sun Feb  7 00:38:04 2016
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  InstallationDate: Installed on 2015-10-24 (105 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: bnep btusb bluetooth
  MachineType: Micro-Star International Co., Ltd. GT72 2QD
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic 
root=UUID=f7880b23-39b5-423a-bdbf-62b111783450 ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2016-02-02 (4 days ago)
  dmi.bios.date: 12/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10I
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10

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

This change was made by a bot.

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

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

Title:
  Suspend won't work on Ubuntu 17.10 beta

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my ubuntu gnome 17.04 to ubuntu 17.10.
  When the laptop is suspended, it cpu keeps working, the power light which 
blinks when suspended doesn't blink, it just stays on which means the laptop 
didn't get suspended.

  Also when i wake from this problematic 'suspend' state, wifi icon from
  top bar is missing and issuing reboot from terminal reports andother
  shutdown/reboot operation is already in progress.

  Also wifi cannot be turned on what so ever and the gnome-control-
  center app doesn't open.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anup   1886 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Oct  9 15:57:15 2017
  InstallationDate: Installed on 2017-06-11 (120 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 13d3:3496 IMC Networks 
   Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X556UQK
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed 
root=UUID=6b5e7c24-b6f6-4e8e-9671-030bb98115a5 ro quiet splash zswap.enabled=1 
i915.enable_guc_loading=1 i915.enable_guc_submission=1 intel_pstate=hwp_only 
i915.enable_psr=1 i915.disable_power_well=0 i915.enable_rc6=7 i915.enable_fbc=1 
i915.semaphores=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-08 (0 days ago)
  dmi.bios.date: 03/02/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X556UQK.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X556UQK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX556UQK.309:bd03/02/2017:svnASUSTeKCOMPUTERINC.:pnX556UQK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UQK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X556UQK
  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/1722211/+subscriptions

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

[Kernel-packages] [Bug 1718397] Re: multipath -ll is not showing the disks which are actually multipath

2017-10-09 Thread bugproxy

** Tags removed: bugnameltc-146489 kernel-da-key severity-critical
triage-a

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

Title:
  multipath -ll is not showing the disks which are actually multipath

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

Bug description:
  [Impact]

   * The number of available AIO contexts is severely limited
 on systems with a large number of possible CPUs 
 (e.g., IBM POWER8 processors w/ 20ish cores * 8 threads/core,
 and other multithreaded server-class processors).

   * This prevents application such as multipath/directio checker
 to provide all of the available devices to the system.

   * Other applications which depend on AIO can be affected/limited.

   * The patch fixes how aio increments the number of active contexts
 (seen in /proc/sys/fs/aio-nr) and checks that against the global
 limit (seen in /proc/sys/fs/aio-max-nr).

  [Test Case]

   * A synthetic test-case is attached (io_setup_v2.c) and demonstrated
 (original/patched kernels) in comment #4.

   * Trying to perform multipath discovery in debug/verbose mode
 (i.e., "multipath -v3" command) with sufficient number of 
 individual paths using the "directio" path checker should
 demonstrate the problem/solution as well (i.e., presence or
 not of "io_setup failed" messages).

  [Regression Potential]

   * Note the fix is trivial and has been tested by several users,
 even caused the introduction of a new test-case in "libaio";
 (but that can never be a strong enough reason for no more errors).

   * Applications which use aio with small "nr_events" value as argument
 to "io_setup()" now have access to a much larger number of aio contexts;
 but hopefully those apps are already only requesting what they need,
 not trying to get more and more.

   * Applications which relied in the _incorrect_ behavior of 
'/proc/sys/fs/aio-nr'
 being possibly greater than '/proc/sys/fs/aio-max-nr' might have problems,
 but those apps should be fixed.


  Problem Description
  =
  I am facing this issue for Texan Flash storage 840 disks which are coming 
from coho and salfish adapter

  coho adapter with 840 storage  is 3G disks and salfish adapter with
  840 is 12G disks

  I am able to see those disks in lsblk o/p but not in multipath -ll
  comamnd

  0004:01:00.0 Coho: Saturn-X  U78C9.001.WZS0060-P1-C6 
0x1090fa2a51f8  host10  Online
  0004:01:00.1 Coho: Saturn-X  U78C9.001.WZS0060-P1-C6 
0x1090fa2a51f9  host11  Online

  0005:09:00.0 Sailfish: QLogic 8GBU78C9.001.WZS0060-P1-C9 
0x2124ff787778  host2   Online
  0005:09:00.1 Sailfish: QLogic 8GBU78C9.001.WZS0060-P1-C9 
0x2124ff787779  host4   Online

  root@luckyv1:/dev/disk# multipath -ll | grep "size=3.0G" -B 1
  root@luckyv1:/dev/disk# multipath -ll | grep "size=12G" -B 1
  root@luckyv1:/dev/disk#

  == Comment: #3 - Luciano Chavez  - 2016-09-20 20:22:20 ==
  I edited /etc/multipath.conf and added
  verbosity 6

  to crank up the output and ran multipath -ll and saved it off to a
  text file (attached). All the using the directio checker failed and
  those using the tur checker seem to work.

  Sep 20 20:07:36 | loading //lib/multipath/libcheckdirectio.so checker
  Sep 20 20:07:36 | loading //lib/multipath/libprioconst.so prioritizer
  Sep 20 20:07:36 | Discover device 
/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/block/sdai
  Sep 20 20:07:36 | sdai: udev property ID_WWN whitelisted
  Sep 20 20:07:36 | sdai: not found in pathvec
  Sep 20 20:07:36 | sdai: mask = 0x25
  Sep 20 20:07:36 | sdai: dev_t = 66:32
  Sep 20 20:07:36 | open 
'/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/block/sdai/size'
  Sep 20 20:07:36 | sdai: size = 20971520
  Sep 20 20:07:36 | sdai: vendor = IBM
  Sep 20 20:07:36 | sdai: product = FlashSystem-9840
  Sep 20 20:07:36 | sdai: rev = 1442
  Sep 20 20:07:36 | sdai: h:b:t:l = 3:0:0:0
  Sep 20 20:07:36 | SCSI target 3:0:0 -> FC rport 3:0-2
  Sep 20 20:07:36 | sdai: tgt_node_name = 0x500507605e839800
  Sep 20 20:07:36 | open 
'/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/state'
  Sep 20 20:07:36 | sdai: path state = running
  Sep 20 20:07:36 | sdai: get_state
  Sep 20 20:07:36 | sdai: path_checker = directio (internal default)
  Sep 20 20:07:36 | sdai: checker timeout = 30 ms (internal default)
  Sep 20 20:07:36 | io_setup

[Kernel-packages] [Bug 1722211] [NEW] Suspend won't work on Ubuntu 17.10 beta

2017-10-09 Thread Anup

Public bug reported:

I upgraded my ubuntu gnome 17.04 to ubuntu 17.10.
When the laptop is suspended, it cpu keeps working, the power light which 
blinks when suspended doesn't blink, it just stays on which means the laptop 
didn't get suspended.

Also when i wake from this problematic 'suspend' state, wifi icon from
top bar is missing and issuing reboot from terminal reports andother
shutdown/reboot operation is already in progress.

Also wifi cannot be turned on what so ever and the gnome-control-center
app doesn't open.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-12-generic 4.13.0-12.13
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  anup   1886 F pulseaudio
CurrentDesktop: GNOME
Date: Mon Oct  9 15:57:15 2017
InstallationDate: Installed on 2017-06-11 (120 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 13d3:3496 IMC Networks 
 Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd 
 Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X556UQK
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed 
root=UUID=6b5e7c24-b6f6-4e8e-9671-030bb98115a5 ro quiet splash zswap.enabled=1 
i915.enable_guc_loading=1 i915.enable_guc_submission=1 intel_pstate=hwp_only 
i915.enable_psr=1 i915.disable_power_well=0 i915.enable_rc6=7 i915.enable_fbc=1 
i915.semaphores=1 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-12-generic N/A
 linux-backports-modules-4.13.0-12-generic  N/A
 linux-firmware 1.169
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-10-08 (0 days ago)
dmi.bios.date: 03/02/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X556UQK.309
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X556UQK
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX556UQK.309:bd03/02/2017:svnASUSTeKCOMPUTERINC.:pnX556UQK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UQK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X556UQK
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

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

Title:
  Suspend won't work on Ubuntu 17.10 beta

Status in linux package in Ubuntu:
  New

Bug description:
  I upgraded my ubuntu gnome 17.04 to ubuntu 17.10.
  When the laptop is suspended, it cpu keeps working, the power light which 
blinks when suspended doesn't blink, it just stays on which means the laptop 
didn't get suspended.

  Also when i wake from this problematic 'suspend' state, wifi icon from
  top bar is missing and issuing reboot from terminal reports andother
  shutdown/reboot operation is already in progress.

  Also wifi cannot be turned on what so ever and the gnome-control-
  center app doesn't open.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anup   1886 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Oct  9 15:57:15 2017
  InstallationDate: Installed on 2017-06-11 (120 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 13d3:3496 IMC Networks 
   Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X556UQK
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed 
root=UUID=6b5e7c24-b6f6-4e8e-9671-030bb98115a5 ro quiet

[Kernel-packages] [Bug 1718548] Re: ubuntu-fan autopkgtests are broken against systemd-resolved

I could not see the docker failure when running a local ADT test. So I
added the checking with some additional output to see what is going on.
The latest test failure (at least now it is detected quickly)
http://autopkgtest.ubuntu.com/packages/u/ubuntu-fan/artful/amd64 shows
that the host side is ok (using systemd-resolve --status on the first
default route found returns a sensible forwarder). Also the fact that
the image can be downloaded hints that the host side is good. And the
LXD test is using the same setup (also the same underlay of
10.220.0.0/16) and works.

The difference is that LXD is using the dnsmasq based resolver which the
fan tools set up, while docker is using its own (127.0.0.11) service.
Not sure what the exact environment setup in ADT testing is, but could
docker be affected by the same multiple default route issue which we had
with the LXD tests? I don't think fanatic can do much as dns does not
seem to be something one can influence with network create.

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

Title:
ubuntu-fan autopkgtests are broken against systemd-resolved

Status in ubuntu-fan package in Ubuntu:
In Progress

Bug description:
Now that 17.10 has migrated to netplan+systemd-networkd+systemd-
resolved by default, ubuntu-fan autopkgtests are failing; at least one
reason for this failure is wrong detection of the default network
interface because autopkgtest environments appear for some reason to
be getting multiple default routes:

autopkgtest [20:14:59]: test lxd: [---
Error: either "dev" is duplicate, or "ens2" is a garbage.
II: Auto-init LXD...
LXD has been successfully configured.
II: Creating Fan Bridge...
/usr/sbin/fanatic: .0.0/16: unknown underlay network format
FAIL: Error on enable-fan
autopkgtest [20:15:10]: test lxd: ---]

(https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-artful/artful/amd64/u/ubuntu-
fan/20170916_203221_4f037@/log.gz)

The other part failure appears to be a race with systemd-resolved in
setting up the network inside of docker containers:

autopkgtest [17:25:39]: test docker: [---
Running in the Canonical CI environment
II: Auto-create Fan Bridge...
configuring fan underlay:10.220.0.0/16 overlay:250.0.0.0/8
II: Create docker Fan Network...
configuring docker for underlay:10.220.0.0/16 overlay:250.0.0.0/8 (fan-250
250.4
6.84.0/24)
1c8a03aa50ab88b997c3b3aee88bfa6933b14368f1594db4a800c2ae8d62074f
II: Test docker...
local docker test: pulling container images ...
Using default tag: latest
latest: Pulling from library/ubuntu
d5c6f90da05d: Pulling fs layer
[...]
2b8db33536d4: Pull complete
Digest:
sha256:2b9285d3e340ae9d4297f83fed6a9563493945935fc787e98cc32a69f5687641
Status: Downloaded newer image for ubuntu:latest
local docker test: creating test container ...
5cbdd232b71bc0738f27f1fa3eae4360716bfe3f8cea976874bf6309b1843169
slave: installing ping ...
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease
Temporary failure resolving 'archive.ubuntu.com'
[...]
E: Unable to locate package iputils-ping
slave: installing nc ...
E: Unable to locate package netcat-openbsd
test master: ping test (250.46.84.2) ...
test slave: ping test (250.46.84.1) ...
test slave: ping test ... FAIL
--- transcript start ---
/bin/sh: 108: ping: not found
--- transcript end ---
test slave: short data test (250.46.84.2 -> 250.46.84.1) ...
test master: ping test ... PASS
test master: short data test (250.46.84.1 -> 250.46.84.2) ...
autopkgtest [20:12:19]: ERROR: timed out on command [...]

I've reproduced this problem locally and prepared a partial patch
based on a similar fix to the docker.io package's autopkgtests - but
so far this only fixes races in the lxd test, not in the docker test,
so it needs further investigation.

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

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

[Kernel-packages] [Bug 1715552] Re: VMWare does not start

2017-10-09 Thread AndreK

** Description changed:

  Under Ubuntu 17.10 beta VMWare 12.5.7 cannot be started:
  
  /usr/lib/vmware/bin/vmware-modconfig: Relink `/lib/x86_64-linux-
  gnu/libbsd.so.0' with `/lib/x86_64-linux-gnu/librt.so.1' for IFUNC
  symbol `clock_gettime'
  
  Works under Ubuntu 17.04
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-13-generic 4.12.0-13.14
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  wolf   9336 F pulseaudio
-  /dev/snd/controlC0:  wolf   9336 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  wolf   9336 F pulseaudio
+  /dev/snd/controlC0:  wolf   9336 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 07:53:43 2017
  HibernationDevice: RESUME=UUID=88d69bc7-ac96-42c6-bf6d-5c912964a63b
  InstallationDate: Installed on 2017-09-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-4.12.0-13-generic N/A
-  linux-backports-modules-4.12.0-13-generic  N/A
-  linux-firmware 1.167
+  linux-restricted-modules-4.12.0-13-generic N/A
+  linux-backports-modules-4.12.0-13-generic  N/A
+  linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B33.1706181928
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

Title:
  VMWare does not start

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Under Ubuntu 17.10 beta VMWare 12.5.7 cannot be started:

  /usr/lib/vmware/bin/vmware-modconfig: Relink `/lib/x86_64-linux-
  gnu/libbsd.so.0' with `/lib/x86_64-linux-gnu/librt.so.1' for IFUNC
  symbol `clock_gettime'

  Works under Ubuntu 17.04

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-13-generic 4.12.0-13.14
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wolf   9336 F pulseaudio
   /dev/snd/controlC0:  wolf   9336 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 07:53:43 2017
  HibernationDevice: RESUME=UUID=88d69bc7-ac96-42c6-bf6d-5c912964a63b
  InstallationDate: Installed on 2017-09-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.12.0-13-generic N/A
   linux-backports-modules-4.12.0-13-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B33.1706181928
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1721373] Re: linux: 4.13.0-15.16 -proposed tracker

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

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

Title:
  linux: 4.13.0-15.16 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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.13.0-15.16 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/1721373/+subscriptions

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

[Kernel-packages] [Bug 1697450] Re: Gnome Shell hangs at startup

2017-10-09 Thread Alberto Donato

If I run gnome-shell from the terminal with the latest (4.13.0-12.13)
kernel, the system freezes.

Running apport-collect while running the 4.8 kernel segfaults:

$ sudo apport-collect 1697450
Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: 
Connection refused
Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: 
Connection refused
Segmentation fault (core dumped)


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

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

Title:
  Gnome Shell hangs at startup

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to install from the daily Artful desktop image (20170612).

  After boot, the gnome session hangs at startup, while the "zoom"
  animation is being shown.

  I have an intel card:

  
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])
  Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller
  Flags: bus master, fast devsel, latency 0, IRQ 29
  Memory at f780 (64-bit, non-prefetchable) [size=4M]
  Memory at e000 (64-bit, prefetchable) [size=256M]
  I/O ports at f000 [size=64]
  [virtual] Expansion ROM at 000c [disabled] [size=128K]
  Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
  Capabilities: [d0] Power Management version 2
  Capabilities: [a4] PCI Advanced Features
  Kernel driver in use: i915
  Kernel modules: i915

  
  I'm not sure how to debug this further, but I had similar issues with the 
installer from Zesty as well (see 
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1681846)
  With Artful, at least it gets past the splash screen but then it hangs.

  Note that the system is currently running Yakkety with no issue.

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

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

[Kernel-packages] [Bug 1699772] Re: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic | Regressio

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: python-jpype (Ubuntu)
   Status: New => Confirmed

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

Title:
  linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-
  image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-
  image-3.13.0-121-generic | Regression: many user-space apps crashing

Status in LibreOffice:
  Won't Fix
Status in commons-daemon package in Ubuntu:
  Confirmed
Status in eclipse package in Ubuntu:
  Confirmed
Status in imagej package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in octave package in Ubuntu:
  Confirmed
Status in python-jpype package in Ubuntu:
  Confirmed
Status in rustc package in Ubuntu:
  Confirmed
Status in scilab package in Ubuntu:
  Confirmed
Status in linux package in Debian:
  Confirmed

Bug description:
  Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10)

  linux-image-4.4.0-81-generic appears to contain a regression, probably
  related to the CVE-2017-1000364 fix backport / patch.

  Using this kernel, the Oracle Java browser plugin always crashes
  during stack-related actions on initialization. This means, the plugin
  completely stopped working.

  
  It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to 
CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also 
contains a fix for CVE-2017-1000364.


  uname -a:

  > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06
  UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as
  well as Iceweasel / Firefox/3.5.16 in a chroot.

  Using linux-image-4.4.0-81-generic it crashes in all combinations
  while with both other kernels it works.

  
  I was not able to obtain any detailed crash information from Firefox 51.0.1, 
but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace 
which shows the relation to stack operations performed by the plugin, even 
without proper debug symbols:

  
  > (gdb) bt full
  > #0  0x7fa06d805307 in _expand_stack_to(unsigned char*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #1  0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, 
unsigned char*) ()
  >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #2  0x7fa06d80cf0b in JVM_handle_linux_signal () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #3  0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #4  

  
  I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6.

  
  The crash will be triggered by any applet, for example the test applet at:

  * https://java.com/en/download/installed8.jsp

  
  I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow 
apparently does not allow me to use apport to report this bug:

  > $ LANG= apport-cli linux-image-4.4.0-81-generic
  > 
  > *** Collecting problem information
  > 
  > The collected information can be sent to the developers to improve the
  > application. This might take a few minutes.
  > .
  > 
  > *** Problem in linux-image-4.4.0-81-generic
  > 
  > The problem cannot be reported:
  > 
  > This is not an official KDE package. Please remove any third party package 
and try again.

  If someone can tell me how to get apport working for this package, I
  can use it to collect additional information, but (unfortunately?) the
  problem should be fairly easy to reproduce...

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+subscriptions

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

[Kernel-packages] [Bug 1720042] Re: linux-aws: 4.4.0-1038.47 -proposed tracker

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

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

** Tags removed: block-proposed-xenial

** Tags removed: block-proposed

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

Title:
  linux-aws: 4.4.0-1038.47 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
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 snap-publish series:
  Invalid
Status in Kernel SRU Workflow snap-qa-testing series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-beta series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-edge series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-1038.47 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: 1718149
  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/1720042/+subscriptions

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

[Kernel-packages] [Bug 1718149] Re: linux: 4.4.0-97.120 -proposed tracker

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

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

** Tags removed: block-proposed-xenial

** Tags removed: block-proposed

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

Title:
  linux: 4.4.0-97.120 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
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 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: 1718150,1718151
  derivatives: 1718153,1718154,1718155,1718156,1718157
  -- 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/1718149/+subscriptions

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

[Kernel-packages] [Bug 1718143] Re: linux: 4.10.0-36.40 -proposed tracker

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

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

Title:
  linux: 4.10.0-36.40 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  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 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: 1718145,1718146
  derivatives: 1718147
  -- 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/1718143/+subscriptions

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

[Kernel-packages] [Bug 1718143] Re: linux: 4.10.0-36.40 -proposed tracker

** Tags added: kernel-block-ppa

** Tags removed: kernel-block-ppa
** Tags added: kernel-block-proposed

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

Title:
  linux: 4.10.0-36.40 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  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 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: 1718145,1718146
  derivatives: 1718147
  -- 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/1718143/+subscriptions

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

[Kernel-packages] [Bug 1718149] Re: linux: 4.4.0-97.120 -proposed tracker

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

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

Title:
  linux: 4.4.0-97.120 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  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 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: 1718150,1718151
  derivatives: 1718153,1718154,1718155,1718156,1718157
  -- 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/1718149/+subscriptions

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

[Kernel-packages] [Bug 1720042] Re: linux-aws: 4.4.0-1038.47 -proposed tracker