date:20170817

Here's the diff:

diff --git a/sound/usb/quirks.c b/sound/usb/quirks.c
index eb4b9f7a571e..f9b79ad9e579 100644
--- a/sound/usb/quirks.c
+++ b/sound/usb/quirks.c
@@ -1137,6 +1137,7 @@ bool snd_usb_get_sample_rate_quirk(struct snd_usb_audio 
*chip)
case USB_ID(0x045E, 0x0779): /* MS Lifecam HD-3000 */
case USB_ID(0x047F, 0x02F7): /* Plantronics BT-600 */
case USB_ID(0x047F, 0x0415): /* Plantronics BT-300 */
+   case USB_ID(0x047F, 0xC036): /* Plantronics C520-M */
case USB_ID(0x047F, 0xAA05): /* Plantronics DA45 */
case USB_ID(0x04D8, 0xFEEA): /* Benchmark DAC1 Pre */
case USB_ID(0x0556, 0x0014): /* Phoenix Audio TMX320VC */

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

Title:
  Plantronics Blackwire C520-M - Cannot get freq at ep 0x1, 0x81

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Very similar to this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622763

  == the Problem ==
  Listening to sound on a vmware machine, hosted by Ubuntu, the devices 
freezes, and cannot listen to sound anymore, i have to connect/disconnect the 
device. 
  After i disconnect i get the logs:
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.344893] usb 1-1: 1:1: cannot get 
freq at ep 0x81
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.347094] usb 1-1: 2:1: cannot get 
freq at ep 0x1
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.358786] usb 1-1: Warning! 
Unlikely big volume range (=8192), cval->res is probably wrong.
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.358787] usb 1-1: [11] FU 
[Sidetone Playback Volume] ch = 1, val = 0/8192/1
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.641980] input: Plantronics 
Plantronics C520-M as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.3/0003:047F:C036.000F/input/input32
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.702298] plantronics 
0003:047F:C036.000F: input,hiddev0,hidraw2: USB HID v1.11 Device [Plantronics 
Plantronics C520-M] on usb-:00:14.0-1/input3
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.747708] usb 1-1: 2:1: cannot get 
freq at ep 0x1
  Aug  8 13:52:16 tim-lap-143 kernel: [112289.406154] usb 1-1: reset full-speed 
USB device number 19 using xhci_hcd
  Aug  8 13:52:16 tim-lap-143 kernel: [112289.906146] usb 1-1: reset full-speed 
USB device number 19 using xhci_hcd

  = The solution ==

  It is simple, add this USB ID to the
  sound/usb/quirks.c:snd_usb_get_sample_rate_quirk function.

  
  version signature: Ubuntu 4.10.0-28.32-generic 4.10.17

  Thanks!
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   mihai.cin...@3pillar.corp   2208 F...m pulseaudio
   /dev/snd/controlC0:  mihai.cin...@3pillar.corp   2208 F pulseaudio
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=d363a75c-d8a4-467d-a576-a46b3c317861
  InstallationDate: Installed on 2017-06-22 (47 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Precision 3510
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash i915.enable_guc_loading=1 
i915.enable_guc_submission=1 intel_pstate=skylake_hwp i915.enable_psr=1 
i915.disable_power_well=0 i915.enable_rc6=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-28-generic N/A
   linux-backports-modules-4.10.0-28-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-28-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-07-21 (18 days ago)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 05/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.4
  dmi.board.name: 00D283
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.4:bd05/12/2017:svnDellInc.:pnPrecision3510:pvr:rvnDellInc.:rn00D283:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 3510
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1688625] Re: Linux does not recognize the Hantick touchpad as a touchpad and does not enable all the functions

>From the git log, I can see several commits are wrote by Elantech guy...

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

Title:
  Linux does not recognize the Hantick touchpad as a touchpad and does
  not enable all the functions

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  We have laptops with touchpad Hantick, that on Miscrosft Windows work with 
Elan driver.

  Linux does not recognize the Hantick touchpad as a touchpad and does
  not enable all the functions of evdev or libinput.

  Thanks
  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-77-generic 4.4.0-77.98
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  slimbook   1720 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May  5 20:01:33 2017
  HibernationDevice: RESUME=UUID=eef047d2-92ea-4166-a300-7a4de6af1448
  InstallationDate: Installed on 2017-05-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 090c:037c Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) 300k Pixel Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   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: SLIMBOOK KATANA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic.efi.signed 
root=UUID=00a6febb-4980-4147-a2e8-29930aed3d30 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-77-generic N/A
   linux-backports-modules-4.4.0-77-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 16L
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: KATANA
  dmi.board.vendor: SLIMBOOK
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SLIMBOOK
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr16L:bd07/25/2016:svnSLIMBOOK:pnKATANA:pvrTBDbyOEM:rvnSLIMBOOK:rnKATANA:rvrType2-BoardVersion:cvnSLIMBOOK:ct10:cvrChassisVersion:
  dmi.product.name: KATANA
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: SLIMBOOK

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

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

[Kernel-packages] [Bug 1710548] Re: Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04? Logitech C920 Webcam/Zoneminder/Startech

You can check the patch here: https://lkml.org/lkml/2017/8/18/4

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

Title:
  Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04?
  Logitech C920 Webcam/Zoneminder/Startech

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In trying to build a zoneminder server, I think I stumbled on a kernel
  bug. It  seems to have snuck in sometime between 16.04 desktop
  promoted to server, and 17.04 server promoted to desktop.

  The suggestion is that the very popular Nec/Renasas 27xxx2 may need
  "quirk" in the kernel.

  Timeline:

  
  (Scene 1)

  Loaded 16.04 Ubuntu Desktop
  Promoted Desktop to Studio
  Promoted Desktop to Server
  Added Zoneminder
  Needed more cams, added Startech  PEXUSB3S44V NEC/Renesasa 27XXX2 based card 
for more USB channels.
  Everything worked quite well. Some errors in ZM but no DMESG as far as I 
recall. 

  (Scene 2)
  Wiped the drive. 
  Loaded 17.04 Server
  Now getting messages in DMESG complaining of thousands of errors:
  [96415.044917] handle_tx_event: 516 callbacks suppressed
  [96415.044924] xhci_hcd :0c:00.0: WARN Successful completion on short TX: 
needs XHCI_TRUST_TX_LENGTH quirk?

  
  Messages suggest "quirk" is the solution.
  a)Researched usb 3.0 "quirk'
  b)Noticed it's really a "thing" 
  c)Couldn't find recipe for patching kernel for NEC/Renases "quirk" fix. 

  (Scene 3)
  Anecdotes suggest Nec/Renasas firmware is to blame.
  a) Kernel indicates 2024 firmaware
  b) Startech website has 2026 firmware. 
  c) VERY IMPORTANT! WindowCentric GUI instructions do not translate between 
ASCII and HEX. So if your Startech is on channels 9, 10, 11, and 12 from 
perspective of Windows, you must translate into 09, 0A, 0B, and 0C when editing 
runfile for effective firmware update of all 4 controllers. Yes, for the 4 
channel controller, count them: 4. 
  d) Firmware updated. 

  (Scene 4) 
  Rebooted with new Startech/Nec/Renases 2026 firmware. 
  SAME OLD PLETHORA OF ERRORS

  (Scene 5)
  I give up. 

  It may well be worth noting that there are no errors from DMESG until some 
seconds after the first webcam is attached to the Startech.
   
  And I can't overemphasize the fact that I don't think I had any DMESG errors 
under Desktop 16.04 

  I think the file attached represents DMESG immediately before the
  errors start going nuts. My theory is that ZM does lazy polls on
  missing cams but once it gets 'hold if the cam and sucking data the
  quirk bug surfaces.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff  12776 F pulseaudio
   /dev/snd/controlC3:  jeff  12776 F pulseaudio
   /dev/snd/controlC2:  jeff  12776 F pulseaudio
   /dev/snd/controlC1:  jeff  12776 F pulseaudio
  Date: Sun Aug 13 16:48:41 2017
  MachineType: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 mgadrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=UUID=4f802241-4254-4d61-9231-d7e16de36a3d 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:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.2a
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.2a:bd08/31/2015:svnSupermicro:pnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:pvr0123456789:rvnSupermicro:rnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:rvr0123456789:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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

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

[Kernel-packages] [Bug 1658345] Re: Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10

When you rollback to old kernel, does the touchscreen work? Which
version is it? Do you use DKMS for the touchscreen?

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

Title:
  Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 16.10 on my Lenovo Ideapad Flex 4 laptop. Ubuntu does not 
recognize the touchpad (it does recognize the touch screen nicely though). When 
I run xinput -list, I do not see the touchpad. I dual boot with Windows 10, 
which recognizes the touchpad from Elantech. I searched online for days and I 
found Elantech drivers for Ubuntu 14.04, however, I was unable to load older 
versions of Ubuntu on my laptop. Do you expect to support the Elantech touchpad 
in future updates? I attached a screen shot of my xinput -list output. Please 
let me know if you require any additional information. Thank you.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  keary  2345 F pulseaudio
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=dbfec3b4-a8be-406e-9f39-5258c004c656
  InstallationDate: Installed on 2017-01-18 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57fc Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80U3
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed 
root=UUID=5be7438e-36fd-4960-a4cd-2371715adfa2 ro quiet splash i8042.kbdreset=1 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-34-generic N/A
   linux-backports-modules-4.8.0-34-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.8.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2MCN24WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Sofia-F
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J91204WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad FLEX 4-1130
  dmi.modalias: 
dmi:bvnLENOVO:bvr2MCN24WW:bd11/01/2016:svnLENOVO:pn80U3:pvrLenovoideapadFLEX4-1130:rvnLENOVO:rnSofia-F:rvrSDK0J91204WIN:cvnLENOVO:ct10:cvrLenovoideapadFLEX4-1130:
  dmi.product.name: 80U3
  dmi.product.version: Lenovo ideapad FLEX 4-1130
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-18 (181 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.13.0-041300rc1-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-05-07 (73 days ago)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-18 (208 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.13.0-rc5-elan0602 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-05-07 (100 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1658345] Re: Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10

2017-08-17 Thread Keary Parinis

Here is dmesg for 4.13 rc4

** Attachment added: "dmesg_4.13rc4.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658345/+attachment/4934483/+files/dmesg_4.13rc4.txt

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

Title:
  Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 16.10 on my Lenovo Ideapad Flex 4 laptop. Ubuntu does not 
recognize the touchpad (it does recognize the touch screen nicely though). When 
I run xinput -list, I do not see the touchpad. I dual boot with Windows 10, 
which recognizes the touchpad from Elantech. I searched online for days and I 
found Elantech drivers for Ubuntu 14.04, however, I was unable to load older 
versions of Ubuntu on my laptop. Do you expect to support the Elantech touchpad 
in future updates? I attached a screen shot of my xinput -list output. Please 
let me know if you require any additional information. Thank you.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  keary  2345 F pulseaudio
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=dbfec3b4-a8be-406e-9f39-5258c004c656
  InstallationDate: Installed on 2017-01-18 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57fc Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80U3
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed 
root=UUID=5be7438e-36fd-4960-a4cd-2371715adfa2 ro quiet splash i8042.kbdreset=1 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-34-generic N/A
   linux-backports-modules-4.8.0-34-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.8.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2MCN24WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Sofia-F
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J91204WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad FLEX 4-1130
  dmi.modalias: 
dmi:bvnLENOVO:bvr2MCN24WW:bd11/01/2016:svnLENOVO:pn80U3:pvrLenovoideapadFLEX4-1130:rvnLENOVO:rnSofia-F:rvrSDK0J91204WIN:cvnLENOVO:ct10:cvrLenovoideapadFLEX4-1130:
  dmi.product.name: 80U3
  dmi.product.version: Lenovo ideapad FLEX 4-1130
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-18 (181 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.13.0-041300rc1-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-05-07 (73 days ago)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-18 (208 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.13.0-rc5-elan0602 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-05-07 (100 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1658345] Re: Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10

2017-08-17 Thread Keary Parinis

Here is dmesg for v4.13 rc5


** Attachment added: "dmesg_4.13.0_rc5.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658345/+attachment/4934484/+files/dmesg_4.13.0_rc5.txt

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

Title:
  Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 16.10 on my Lenovo Ideapad Flex 4 laptop. Ubuntu does not 
recognize the touchpad (it does recognize the touch screen nicely though). When 
I run xinput -list, I do not see the touchpad. I dual boot with Windows 10, 
which recognizes the touchpad from Elantech. I searched online for days and I 
found Elantech drivers for Ubuntu 14.04, however, I was unable to load older 
versions of Ubuntu on my laptop. Do you expect to support the Elantech touchpad 
in future updates? I attached a screen shot of my xinput -list output. Please 
let me know if you require any additional information. Thank you.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  keary  2345 F pulseaudio
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=dbfec3b4-a8be-406e-9f39-5258c004c656
  InstallationDate: Installed on 2017-01-18 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57fc Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80U3
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed 
root=UUID=5be7438e-36fd-4960-a4cd-2371715adfa2 ro quiet splash i8042.kbdreset=1 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-34-generic N/A
   linux-backports-modules-4.8.0-34-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.8.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2MCN24WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Sofia-F
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J91204WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad FLEX 4-1130
  dmi.modalias: 
dmi:bvnLENOVO:bvr2MCN24WW:bd11/01/2016:svnLENOVO:pn80U3:pvrLenovoideapadFLEX4-1130:rvnLENOVO:rnSofia-F:rvrSDK0J91204WIN:cvnLENOVO:ct10:cvrLenovoideapadFLEX4-1130:
  dmi.product.name: 80U3
  dmi.product.version: Lenovo ideapad FLEX 4-1130
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-18 (181 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.13.0-041300rc1-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-05-07 (73 days ago)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-18 (208 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.13.0-rc5-elan0602 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-05-07 (100 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1635597] Re: Ubuntu16.10:talclp1: Kdump failed with multipath disk

This bug was fixed in the package makedumpfile - 1:1.6.1-2

---
makedumpfile (1:1.6.1-2) sid; urgency=medium

  * d/kernel-postinst-generate-initrd : Add scsi_dh_* modules if in
use so the system can dump a crash when root is on multipath
(LP: #1635597) (Closes: 862411)

  [ dann frazier ]
  * Select appropriate /etc/default/grub.d/kdump-tools.cfg at build time.
A side-effect of this is that kdump-tools is no longer Arch: all.
(Closes: #863858)

 -- Louis Bouchard   Wed, 16 Aug 2017 16:10:01 +0200

** Changed in: makedumpfile (Ubuntu)
   Status: In Progress => 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/1635597

Title:
  Ubuntu16.10:talclp1: Kdump failed with multipath disk

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Invalid
Status in makedumpfile source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in makedumpfile source package in Xenial:
  Confirmed
Status in linux source package in Zesty:
  Invalid
Status in makedumpfile source package in Zesty:
  Confirmed

Bug description:
  Problem  Description
  ==
  On talclp1, I enabled kdump. But kdump failed and it drop to BusyBox.

  root@talclp1:~# echo c> /proc/sysrq-trigger
  [  132.643690] sysrq: SysRq : Trigger a crash
  [  132.643739] Unable to handle kernel paging request for data at address 
0x
  [  132.643745] Faulting instruction address: 0xc05c28f4
  [  132.643749] Oops: Kernel access of bad area, sig: 11 [#1]
  [  132.643753] SMP NR_CPUS=2048 NUMA pSeries
  [  132.643758] Modules linked in: fuse ufs qnx4 hfsplus hfs minix ntfs msdos 
jfs rpadlpar_io rpaphp rpcsec_gss_krb5 nfsv4 dccp_diag cifs nfs dns_resolver 
dccp tcp_diag fscache udp_diag inet_diag unix_diag af_packet_diag netlink_diag 
binfmt_misc xfs libcrc32c pseries_rng rng_core ghash_generic gf128mul 
vmx_crypto sg nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache crc32c_generic btrfs xor raid6_pq 
dm_round_robin sr_mod sd_mod cdrom ses enclosure scsi_transport_sas ibmveth 
crc32c_vpmsum ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath dm_mod
  [  132.643819] CPU: 49 PID: 10174 Comm: bash Not tainted 4.8.0-15-generic 
#16-Ubuntu
  [  132.643824] task: c00111767080 task.stack: c000d82e
  [  132.643828] NIP: c05c28f4 LR: c05c39d8 CTR: 
c05c28c0
  [  132.643832] REGS: c000d82e3990 TRAP: 0300   Not tainted  
(4.8.0-15-generic)
  [  132.643836] MSR: 80009033   CR: 28242422  
XER: 0001
  [  132.643848] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1
  GPR00: c05c39d8 c000d82e3c10 c0f67b00 0063
  GPR04: c0011d04a9b8 c0011d05f7e0 c0047fb0 00015998
  GPR08: 0007 0001  0001
  GPR12: c05c28c0 c7b4b900  2200
  GPR16: 10170dc8 01002b566368 10140f58 100c7570
  GPR20:  1017dd58 10153618 1017b608
  GPR24: 3e87a294 0001 c0ebff60 0004
  GPR28: c0ec0320 0063 c0e72a90 
  [  132.643906] NIP [c05c28f4] sysrq_handle_crash+0x34/0x50
  [  132.643911] LR [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643914] Call Trace:
  [  132.643917] [c000d82e3c10] [c0a245e8] 0xc0a245e8 
(unreliable)
  [  132.643923] [c000d82e3c30] [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643928] [c000d82e3cd0] [c05c4188] 
write_sysrq_trigger+0x78/0xa0
  [  132.643935] [c000d82e3d00] [c03ad770] proc_reg_write+0xb0/0x110
  [  132.643941] [c000d82e3d50] [c030fc3c] __vfs_write+0x6c/0xe0
  [  132.643946] [c000d82e3d90] [c0311144] vfs_write+0xd4/0x240
  [  132.643950] [c000d82e3de0] [c0312e5c] SyS_write+0x6c/0x110
  [  132.643957] [c000d82e3e30] [c00095e0] system_call+0x38/0x108
  [  132.643961] Instruction dump:
  [  132.643963] 38425240 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 
3949ba60
  [  132.643972] 3921 912a 7c0004ac 3940 <992a> 38210020 
e8010010 7c0803a6
  [  132.643981] ---[ end trace eed6bbcd2c3bdfdf ]---
  [  132.646105]
  [  132.646176] Sending IPI to other CPUs
  [  132.647490] IPI complete
  I'm in purgatory
   -> smp_release_cpus()
  spinning_secondaries = 104
   <- smp_release_cpus()
  [2.011346] alg: hash: Test 1 failed for crc32c-vpmsum
  [2.729254] sd 0:2:0:0: [sda] Assuming drive cache: write through

[Kernel-packages] [Bug 1710548] Re: Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04? Logitech C920 Webcam/Zoneminder/Startech

2017-08-17 Thread Jeffrey Miller

Placeholder for DMESG attachment after the fix, sorry: file extension
collision.

** Attachment added: "postfix.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710548/+attachment/4934482/+files/postfix.txt

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

Title:
  Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04?
  Logitech C920 Webcam/Zoneminder/Startech

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In trying to build a zoneminder server, I think I stumbled on a kernel
  bug. It  seems to have snuck in sometime between 16.04 desktop
  promoted to server, and 17.04 server promoted to desktop.

  The suggestion is that the very popular Nec/Renasas 27xxx2 may need
  "quirk" in the kernel.

  Timeline:

  
  (Scene 1)

  Loaded 16.04 Ubuntu Desktop
  Promoted Desktop to Studio
  Promoted Desktop to Server
  Added Zoneminder
  Needed more cams, added Startech  PEXUSB3S44V NEC/Renesasa 27XXX2 based card 
for more USB channels.
  Everything worked quite well. Some errors in ZM but no DMESG as far as I 
recall. 

  (Scene 2)
  Wiped the drive. 
  Loaded 17.04 Server
  Now getting messages in DMESG complaining of thousands of errors:
  [96415.044917] handle_tx_event: 516 callbacks suppressed
  [96415.044924] xhci_hcd :0c:00.0: WARN Successful completion on short TX: 
needs XHCI_TRUST_TX_LENGTH quirk?

  
  Messages suggest "quirk" is the solution.
  a)Researched usb 3.0 "quirk'
  b)Noticed it's really a "thing" 
  c)Couldn't find recipe for patching kernel for NEC/Renases "quirk" fix. 

  (Scene 3)
  Anecdotes suggest Nec/Renasas firmware is to blame.
  a) Kernel indicates 2024 firmaware
  b) Startech website has 2026 firmware. 
  c) VERY IMPORTANT! WindowCentric GUI instructions do not translate between 
ASCII and HEX. So if your Startech is on channels 9, 10, 11, and 12 from 
perspective of Windows, you must translate into 09, 0A, 0B, and 0C when editing 
runfile for effective firmware update of all 4 controllers. Yes, for the 4 
channel controller, count them: 4. 
  d) Firmware updated. 

  (Scene 4) 
  Rebooted with new Startech/Nec/Renases 2026 firmware. 
  SAME OLD PLETHORA OF ERRORS

  (Scene 5)
  I give up. 

  It may well be worth noting that there are no errors from DMESG until some 
seconds after the first webcam is attached to the Startech.
   
  And I can't overemphasize the fact that I don't think I had any DMESG errors 
under Desktop 16.04 

  I think the file attached represents DMESG immediately before the
  errors start going nuts. My theory is that ZM does lazy polls on
  missing cams but once it gets 'hold if the cam and sucking data the
  quirk bug surfaces.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff  12776 F pulseaudio
   /dev/snd/controlC3:  jeff  12776 F pulseaudio
   /dev/snd/controlC2:  jeff  12776 F pulseaudio
   /dev/snd/controlC1:  jeff  12776 F pulseaudio
  Date: Sun Aug 13 16:48:41 2017
  MachineType: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 mgadrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=UUID=4f802241-4254-4d61-9231-d7e16de36a3d 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:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.2a
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.2a:bd08/31/2015:svnSupermicro:pnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:pvr0123456789:rvnSupermicro:rnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:rvr0123456789:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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

[Kernel-packages] [Bug 1710548] Re: Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04? Logitech C920 Webcam/Zoneminder/Startech

2017-08-17 Thread Jeffrey Miller

Placeholder for DMESG attachment after the fix incorporated by  Kai-Heng
Feng in

http://people.canonical.com/~khfeng/linux-
image-4.13.0-rc5+_4.13.0-rc5+-2_amd64.deb

Note well the kernel complaints such as:

[96415.044917] handle_tx_event: 516 callbacks suppressed
[96415.044924] xhci_hcd :0c:00.0: WARN Successful completion on short TX: 
needs XHCI_TRUST_TX_LENGTH quirk?

..are gone.


** Attachment added: "DMESG after fix"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710548/+attachment/4934481/+files/post_fix_linux-image-4.13.0-rc5+_4.13.0-rc5+-2_amd64.deb

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

Title:
  Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04?
  Logitech C920 Webcam/Zoneminder/Startech

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In trying to build a zoneminder server, I think I stumbled on a kernel
  bug. It  seems to have snuck in sometime between 16.04 desktop
  promoted to server, and 17.04 server promoted to desktop.

  The suggestion is that the very popular Nec/Renasas 27xxx2 may need
  "quirk" in the kernel.

  Timeline:

  
  (Scene 1)

  Loaded 16.04 Ubuntu Desktop
  Promoted Desktop to Studio
  Promoted Desktop to Server
  Added Zoneminder
  Needed more cams, added Startech  PEXUSB3S44V NEC/Renesasa 27XXX2 based card 
for more USB channels.
  Everything worked quite well. Some errors in ZM but no DMESG as far as I 
recall. 

  (Scene 2)
  Wiped the drive. 
  Loaded 17.04 Server
  Now getting messages in DMESG complaining of thousands of errors:
  [96415.044917] handle_tx_event: 516 callbacks suppressed
  [96415.044924] xhci_hcd :0c:00.0: WARN Successful completion on short TX: 
needs XHCI_TRUST_TX_LENGTH quirk?

  
  Messages suggest "quirk" is the solution.
  a)Researched usb 3.0 "quirk'
  b)Noticed it's really a "thing" 
  c)Couldn't find recipe for patching kernel for NEC/Renases "quirk" fix. 

  (Scene 3)
  Anecdotes suggest Nec/Renasas firmware is to blame.
  a) Kernel indicates 2024 firmaware
  b) Startech website has 2026 firmware. 
  c) VERY IMPORTANT! WindowCentric GUI instructions do not translate between 
ASCII and HEX. So if your Startech is on channels 9, 10, 11, and 12 from 
perspective of Windows, you must translate into 09, 0A, 0B, and 0C when editing 
runfile for effective firmware update of all 4 controllers. Yes, for the 4 
channel controller, count them: 4. 
  d) Firmware updated. 

  (Scene 4) 
  Rebooted with new Startech/Nec/Renases 2026 firmware. 
  SAME OLD PLETHORA OF ERRORS

  (Scene 5)
  I give up. 

  It may well be worth noting that there are no errors from DMESG until some 
seconds after the first webcam is attached to the Startech.
   
  And I can't overemphasize the fact that I don't think I had any DMESG errors 
under Desktop 16.04 

  I think the file attached represents DMESG immediately before the
  errors start going nuts. My theory is that ZM does lazy polls on
  missing cams but once it gets 'hold if the cam and sucking data the
  quirk bug surfaces.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff  12776 F pulseaudio
   /dev/snd/controlC3:  jeff  12776 F pulseaudio
   /dev/snd/controlC2:  jeff  12776 F pulseaudio
   /dev/snd/controlC1:  jeff  12776 F pulseaudio
  Date: Sun Aug 13 16:48:41 2017
  MachineType: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 mgadrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=UUID=4f802241-4254-4d61-9231-d7e16de36a3d 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:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.2a
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias:

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

2017-08-17 Thread Brian Murray

Hello Stéphane, or anyone else affected,

Accepted zfs-linux into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/0.6.5.6-0ubuntu18 in a few hours, and then in the -proposed
repository.

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

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

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

** Changed in: zfs-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 zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567557

Title:
  Performance degradation of "zfs clone"

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

Bug description:
  [SRU Justification]

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

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

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

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


  
  --

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

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

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

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

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

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

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

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

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

  [Apr  3 06:42:51.170] Importing image into local store: 
64192037277800298d8c19473c055868e0288b039349b1c6579971fe99fdbac7
  [Apr  3 06:42:52.657] Starting the test
  [Apr  3 06:42:53.994] Started 8 containers in 1.336s
  [Apr  3 06:42:55.521] Started 16

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

apport information

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

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  ?

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

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

[Kernel-packages] [Bug 1710548] Re: Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04? Logitech C920 Webcam/Zoneminder/Startech

2017-08-17 Thread Jeffrey Miller

Dear Kai-Heng Feng,

Sure enough you fixed it. No complaints now.

I'd be very curious to look over the source code changes to improve my
linux-fu.

But that's secondary.

For now I hope an administrator can mark up my bug report to ensure that
the changes you have made get propagated.

Thank you very much for taking my bug report seriously.

-Jeff

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

Title:
Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04?
Logitech C920 Webcam/Zoneminder/Startech

Status in linux package in Ubuntu:
Incomplete

Bug description:
In trying to build a zoneminder server, I think I stumbled on a kernel
bug. It seems to have snuck in sometime between 16.04 desktop
promoted to server, and 17.04 server promoted to desktop.

The suggestion is that the very popular Nec/Renasas 27xxx2 may need
"quirk" in the kernel.

Timeline:

(Scene 1)

Loaded 16.04 Ubuntu Desktop
Promoted Desktop to Studio
Promoted Desktop to Server
Added Zoneminder
Needed more cams, added Startech PEXUSB3S44V NEC/Renesasa 27XXX2 based card
for more USB channels.
Everything worked quite well. Some errors in ZM but no DMESG as far as I
recall.

(Scene 2)
Wiped the drive.
Loaded 17.04 Server
Now getting messages in DMESG complaining of thousands of errors:
[96415.044917] handle_tx_event: 516 callbacks suppressed
[96415.044924] xhci_hcd :0c:00.0: WARN Successful completion on short TX:
needs XHCI_TRUST_TX_LENGTH quirk?

Messages suggest "quirk" is the solution.
a)Researched usb 3.0 "quirk'
b)Noticed it's really a "thing"
c)Couldn't find recipe for patching kernel for NEC/Renases "quirk" fix.

(Scene 3)
Anecdotes suggest Nec/Renasas firmware is to blame.
a) Kernel indicates 2024 firmaware
b) Startech website has 2026 firmware.
c) VERY IMPORTANT! WindowCentric GUI instructions do not translate between
ASCII and HEX. So if your Startech is on channels 9, 10, 11, and 12 from
perspective of Windows, you must translate into 09, 0A, 0B, and 0C when editing
runfile for effective firmware update of all 4 controllers. Yes, for the 4
channel controller, count them: 4.
d) Firmware updated.

(Scene 4)
Rebooted with new Startech/Nec/Renases 2026 firmware.
SAME OLD PLETHORA OF ERRORS

(Scene 5)
I give up.

It may well be worth noting that there are no errors from DMESG until some
seconds after the first webcam is attached to the Startech.

And I can't overemphasize the fact that I don't think I had any DMESG errors
under Desktop 16.04

I think the file attached represents DMESG immediately before the
errors start going nuts. My theory is that ZM does lazy polls on
missing cams but once it gets 'hold if the cam and sucking data the
quirk bug surfaces.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-32-generic 4.10.0-32.36
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jeff 12776 F pulseaudio
/dev/snd/controlC3: jeff 12776 F pulseaudio
/dev/snd/controlC2: jeff 12776 F pulseaudio
/dev/snd/controlC1: jeff 12776 F pulseaudio
Date: Sun Aug 13 16:48:41 2017
MachineType: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
ProcEnviron:
LANGUAGE=en_US
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
0 mgadrmfb
1 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic
root=UUID=4f802241-4254-4d61-9231-d7e16de36a3d 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:
linux-restricted-modules-4.10.0-32-generic N/A
linux-backports-modules-4.10.0-32-generic N/A
linux-firmware 1.164.1
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/31/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3.2a
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
dmi.board.vendor: Supermicro
dmi.board.version: 0123456789
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr3.2a:bd08/31/2015:svnSupermicro:pnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:pvr0123456789:rvnSupermicro:rnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:rvr0123456789:cvnSupermicro:ct17:cvr0123456789:
dmi.product.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
dmi.product.version: 0123456789
dmi.sys.vendor:

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

apport information

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

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  ?

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

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

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

apport information

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

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  ?

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

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

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

apport information

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

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  ?

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

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

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

apport information

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

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  ?

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

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

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

apport information

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

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  ?

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

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

[Kernel-packages] [Bug 1711407] apport information

AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Aug 17 17:27 seq
 crw-rw 1 root audio 116, 33 Aug 17 17:27 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=7356cc51-3c3e-4d0d-bb9c-9d8daf436e5c
InstallationDate: Installed on 2016-09-20 (331 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
IwConfig: Error: [Errno 2] No such file or directory
MachineType: Dell Inc. PowerEdge R710
Package: linux (not installed)
PciMultimedia:
 
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-14-generic 
root=UUID=35a35d02-8a6c-402f-86c5-c39085c81bd3 ro
ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
RelatedPackageVersions:
 linux-restricted-modules-4.11.0-14-generic N/A
 linux-backports-modules-4.11.0-14-generic  N/A
 linux-firmware 1.157.11
RfKill: Error: [Errno 2] No such file or directory
Tags:  xenial
Uname: Linux 4.11.0-14-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
_MarkForUpload: True
dmi.bios.date: 07/23/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 6.4.0
dmi.board.name: 00NH4P
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr6.4.0:bd07/23/2013:svnDellInc.:pnPowerEdgeR710:pvr:rvnDellInc.:rn00NH4P:rvrA00:cvnDellInc.:ct23:cvr:
dmi.product.name: PowerEdge R710
dmi.sys.vendor: Dell 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/1711407

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  ?

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

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

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

apport information

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

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  ?

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

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

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

apport information

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

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  ?

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

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

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

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1711407/+attachment/4934476/+files/ProcCpuinfoMinimal.txt

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  ?

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

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

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

apport information

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

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  ?

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

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

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

apport information

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

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  ?

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

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

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename:   xenial

cat /etc/apt/sources.list.d/docker.list
deb [arch=amd64] https://apt.dockerproject.org/repo ubuntu-xenial main
# deb-src [arch=amd64] https://apt.dockerproject.org/repo ubuntu-xenial main

cat /etc/apt/sources.list.d/runner_gitlab-ci-multi-runner.list
# this file was generated by packages.gitlab.com for
# the repository at https://packages.gitlab.com/runner/gitlab-ci-multi-runner

deb https://packages.gitlab.com/runner/gitlab-ci-multi-runner/ubuntu/ xenial 
main
deb-src https://packages.gitlab.com/runner/gitlab-ci-multi-runner/ubuntu/ 
xenial main


dpkg -l | grep gitlab
ii  gitlab-ci-multi-runner   9.4.2  
amd64GitLab Runner

dpkg -l | grep docker
ii  docker-engine17.05.0~ce-0~ubuntu-xenial 
amd64Docker: the open-source application container engine

Seems to only occur when running docker with privileged inside of
gitlab-runner. On "close" of the docker container, the process fails
with the following:

Aug 17 17:53:04 WIS-DOCKERPHY kernel: [ 1579.245473] unregister_netdevice: 
waiting for lo to become free. Usage count = 1
Aug 17 17:53:15 WIS-DOCKERPHY kernel: [ 1589.356182] unregister_netdevice: 
waiting for lo to become free. Usage count = 1
Aug 17 17:53:25 WIS-DOCKERPHY kernel: [ 1599.466898] unregister_netdevice: 
waiting for lo to become free. Usage count = 1
Aug 17 17:53:35 WIS-DOCKERPHY kernel: [ 1609.577597] unregister_netdevice: 
waiting for lo to become free. Usage count = 1
Aug 17 17:53:45 WIS-DOCKERPHY kernel: [ 1619.692335] unregister_netdevice: 
waiting for lo to become free. Usage count = 1
Aug 17 17:53:54 WIS-DOCKERPHY dockerd[18386]: 
time="2017-08-17T17:53:54.994924776-05:00" level=error msg="containerd: start 
container" error="containerd: container did not start before the specified 
timeout" id=2ef6677cc840f3597e5b38024cfb337856adfaccdcc1a2739f78413979c0fa2b
Aug 17 17:53:54 WIS-DOCKERPHY dockerd[18386]: 
time="2017-08-17T17:53:54.995769254-05:00" level=error msg="Create container 
failed with error: containerd: container did not start before the specified 
timeout"
Aug 17 17:53:55 WIS-DOCKERPHY kernel: [ 1629.366310] docker0: port 
1(veth9f03d7e) entered disabled state
Aug 17 17:53:55 WIS-DOCKERPHY kernel: [ 1629.367889] device veth9f03d7e left 
promiscuous mode
Aug 17 17:53:55 WIS-DOCKERPHY kernel: [ 1629.367891] docker0: port 
1(veth9f03d7e) entered disabled state
Aug 17 17:53:55 WIS-DOCKERPHY kernel: [ 1629.449744] auplink[25254]: segfault 
at 7ffdd8ddb0d8 ip 7facdfff1579 sp 7ffdd8ddb0e0 error 6 in 
libc-2.23.so[7facdfef8000+1c]
Aug 17 17:53:55 WIS-DOCKERPHY dockerd[18386]: 
time="2017-08-17T17:53:55.215290996-05:00" level=warning msg="Couldn't run 
auplink before unmount 
/var/lib/docker/aufs/mnt/90bdc718c5e518ef7b03df0e1769ab4638642ad0e847a38dbf16c6e600783f00:
 signal: segmentation fault (core dumped)"
Aug 17 17:53:55 WIS-DOCKERPHY dockerd[18386]: 
time="2017-08-17T17:53:55.215372764-05:00" level=error msg="Error unmounting 
container 2ef6677cc840f3597e5b38024cfb337856adfaccdcc1a2739f78413979c0fa2b: 
device or resource busy"
Aug 17 17:53:55 WIS-DOCKERPHY dockerd[18386]: 
time="2017-08-17T17:53:55.243281045-05:00" level=error msg="Handler for POST 
/v1.18/containers/2ef6677cc840f3597e5b38024cfb337856adfaccdcc1a2739f78413979c0fa2b/start
 returned error: containerd: container did not start before the specified 
timeout"
Aug 17 17:53:55 WIS-DOCKERPHY kernel: [ 1629.862984] unregister_netdevice: 
waiting for lo to become free. Usage count = 1
Aug 17 17:54:05 WIS-DOCKERPHY kernel: [ 1640.005751] unregister_netdevice: 
waiting for lo to become free. Usage count = 1
Aug 17 17:54:15 WIS-DOCKERPHY kernel: [ 1650.084470] unregister_netdevice: 
waiting for lo to become free. Usage count = 1
Aug 17 17:54:25 WIS-DOCKERPHY dockerd[18386]: 
time="2017-08-17T17:54:25.123304254-05:00" level=error msg="containerd: start 
container" error="containerd: container did not start before the specified 
timeout" id=891adb44118b9114d73a600748e52160a250ec0dd7f94a7ad1fc2352d492252d
Aug 17 17:54:25 WIS-DOCKERPHY dockerd[18386]: 
time="2017-08-17T17:54:25.124077481-05:00" level=error msg="Create container 
failed with error: containerd: container did not start before the specified 
timeout"
Aug 17 17:54:25 WIS-DOCKERPHY kernel: [ 1659.490959] docker0: port 
2(vetha61fb77) entered disabled state
Aug 17 17:54:25 WIS-DOCKERPHY kernel: [ 1659.492532] device vetha61fb77 left 
promiscuous mode
Aug 17 17:54:25 WIS-DOCKERPHY kernel: [ 1659.492534] docker0: port 
2(vetha61fb77) entered disabled state
Aug 17 17:54:25 WIS-DOCKERPHY dockerd[18386]: 
time="2017-08-17T17:54:25.249728323-05:00" level=error msg="Error unmounting 
container 891adb44118b9114d73a600748e52160a250ec0dd7f94a7ad1fc2352d492252d: 
device or resource busy"
Aug 17 17:54:25 WIS-DOCKERPHY dockerd[18386]:

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

2017-08-17 Thread Colin Ian King

** Summary changed:

- accessing /dev/hvc1 with stress-ng on Ubuntu xenia causes crash
+ accessing /dev/hvc1 with stress-ng on Ubuntu xenial causes crash

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

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

Status in linux package in Ubuntu:
  In Progress

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

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

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

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

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

2017-08-17 Thread Corey Schuhen

The issue appears solve for me with 4.10.0-33 on zesty. I assume that an
open invitation for anybody to change the tag to verified.

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

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

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

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

Bug description:
  [SRU Justification]

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

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

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

  ---

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

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

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

  Here are the relevant kernel log messages:

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

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

Title:
  package linux-image-4.4.0-92-generic 4.4.0-92.115 failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Me informa de que hay un error de sistema

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jose   1739 F pulseaudio
  Date: Thu Aug 17 21:24:25 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=1fb26a3c-6544-436c-b8bf-1cef6a6b218a
  InstallationDate: Installed on 2015-06-19 (790 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Acer Veriton M275
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=bb88fb12-634d-479e-b5b7-f278409a0031 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.12
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-92-generic 4.4.0-92.115 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: 09/02/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: P01-C1L
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Veriton M275
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAcer:bvrP01-C1L:bd09/02/2011:svnAcer:pnVeritonM275:pvr:rvnAcer:rnVeritonM275:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Veriton M275
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 315762] ☑omg curious case

2017-08-17 Thread ixzel

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

Hello,

I've  just lately found  one interested circumstance about the products
we  discussed last time, just take  a  look  http://rond-
umme.nl/forward_n.php?5c5d

Good wishes, Glenda Callaway

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

Title:
  when finishing the instalation of updated data, instalation halts and
  the windows message appears with following "Failed: E:
  /var/cache/apt/archives/linux-
  image-2.6.27-7-generic_2.6.27-7.16_i386.deb: impossível criar ligação
  de backup de './boot/vmlinuz-2.6.27-7-generic' antes de instalar nova
  versão".

Status in linux package in Ubuntu:
  New

Bug description:
  E: /var/cache/apt/archives/linux-
  image-2.6.27-7-generic_2.6.27-7.16_i386.deb: impossível criar ligação
  de backup de './boot/vmlinuz-2.6.27-7-generic' antes de instalar nova
  versão

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 8.10
  LsUsb:
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 002: ID 1307:0163 Transcend Information, Inc. 512MB USB Flash 
Drive
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  NonfreeKernelModules: nvidia
  Package: linux-image-2.6.27-9-generic 2.6.27-9.19
  ProcCmdLine: root=UUID=3836-A19B loop=/hostname/disks/root.disk ro 
ROOTFLAGS=sync quiet splash
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.27-9.19-generic
  SourcePackage: linux

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

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

[Kernel-packages] [Bug 1711454] Re: package linux-image-4.4.0-92-generic 4.4.0-92.115 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2017-08-17 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/1711454

Title:
  package linux-image-4.4.0-92-generic 4.4.0-92.115 failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  New

Bug description:
  Me informa de que hay un error de sistema

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jose   1739 F pulseaudio
  Date: Thu Aug 17 21:24:25 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=1fb26a3c-6544-436c-b8bf-1cef6a6b218a
  InstallationDate: Installed on 2015-06-19 (790 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Acer Veriton M275
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=bb88fb12-634d-479e-b5b7-f278409a0031 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.12
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-92-generic 4.4.0-92.115 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: 09/02/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: P01-C1L
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Veriton M275
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAcer:bvrP01-C1L:bd09/02/2011:svnAcer:pnVeritonM275:pvr:rvnAcer:rnVeritonM275:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Veriton M275
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1711454] [NEW] package linux-image-4.4.0-92-generic 4.4.0-92.115 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2017-08-17 Thread mariocan

Public bug reported:

Me informa de que hay un error de sistema

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-92-generic 4.4.0-92.115
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic i686
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jose   1739 F pulseaudio
Date: Thu Aug 17 21:24:25 2017
ErrorMessage: subprocess new pre-installation script returned error exit status 
128
HibernationDevice: RESUME=UUID=1fb26a3c-6544-436c-b8bf-1cef6a6b218a
InstallationDate: Installed on 2015-06-19 (790 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1)
IwConfig:
 lono wireless extensions.
 
 eth0  no wireless extensions.
MachineType: Acer Veriton M275
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=bb88fb12-634d-479e-b5b7-f278409a0031 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.12
RfKill:
 
SourcePackage: linux
Title: package linux-image-4.4.0-92-generic 4.4.0-92.115 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: 09/02/2011
dmi.bios.vendor: Acer
dmi.bios.version: P01-C1L
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: Veriton M275
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: 
dmi:bvnAcer:bvrP01-C1L:bd09/02/2011:svnAcer:pnVeritonM275:pvr:rvnAcer:rnVeritonM275:rvr:cvnAcer:ct3:cvr:
dmi.product.name: Veriton M275
dmi.sys.vendor: Acer

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


** Tags: apport-package i386 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/1711454

Title:
  package linux-image-4.4.0-92-generic 4.4.0-92.115 failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  New

Bug description:
  Me informa de que hay un error de sistema

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jose   1739 F pulseaudio
  Date: Thu Aug 17 21:24:25 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=1fb26a3c-6544-436c-b8bf-1cef6a6b218a
  InstallationDate: Installed on 2015-06-19 (790 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Acer Veriton M275
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=bb88fb12-634d-479e-b5b7-f278409a0031 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.12
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-92-generic 4.4.0-92.115 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: 09/02/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: P01-C1L
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Veriton M275
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAcer:bvrP01-C1L:bd09/02/2011:svnAcer:pnVeritonM275:pvr:rvnAcer:rnVeritonM275:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Veriton M275
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1710671] Re: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 6

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 6

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  i realy dont now way this is giving me a problem, i can't install any
  other .deb file.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1
  ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
  Uname: Linux 4.4.0-91-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Mon Aug 14 08:56:29 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 6
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: bcmwl
  Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 6
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

--- Comment From jhop...@us.ibm.com 2017-08-17 15:11 EDT---
I believe Puvi verified the PMC5 issue is fixed with this build, although it 
hit a stability issue which is being addressed in bug 157728 (Canonical 
Launchpad bug 1711104 ).

Puvi, is that correct?   If so I will mark this one verified..

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

Title:
  Ubuntu 16.04.03: perf tool does not count pm_run_inst_cmpl with rcode
  on POWER9 DD2.0

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

Bug description:
  ---Problem Description---
  Unable to count pm_run_inst_cmpl using perf tool on boston dd2.0

  root@isvbos3:~# perf stat -e r500fa,r600f4 -a  sleep 1

   Performance counter stats for 'system wide':

   r500fa   
   8,162,912  r600f4
  

 1.001562716 seconds time elapsed
   
  ---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
   
  Machine Type = p9 dd2.0 

  ---Steps to Reproduce---
   root@isvbos3:~# perf stat -e r500fa,r600f4 -a  sleep 1

   Performance counter stats for 'system wide':

   r500fa   
   8,162,912  r600f4
  

 1.001562716 seconds time elapsed

   
  > Also we need this upstream fix 8c218578fcbbbdb10416c8614658bf32e3bf1655 in
  > the distro.

  $ git log 8c218578fcbbbdb10416c8614658 -1
  commit 8c218578fcbbbdb10416c8614658bf32e3bf1655
  Author: Madhavan Srinivasan 
  Date:   Fri May 26 13:38:27 2017 +0530

  powerpc/perf: Fix Power9 test_adder fields
  
  Commit 8d911904f3ce4 ('powerpc/perf: Add restrictions to PMC5 in power9 
DD1')
  was added to restrict the use of PMC5 in Power9 DD1. Intention was to 
disable
  the use of PMC5 using raw event code. But instead of updating the
  power9_isa207_pmu structure (used on DD1), the commit incorrectly updated 
the
  power9_pmu structure. Fix it.
  
  Fixes: 8d911904f3ce ("powerpc/perf: Add restrictions to PMC5 in power9 
DD1")
  Reported-by: Shriya 
  Signed-off-by: Madhavan Srinivasan 
  Tested-by: Shriya 
  Signed-off-by: Michael Ellerman 

  $ git describe --contains 8c218578fcbbbdb
  v4.12-rc7~9^2~13
  $ 

  Commit 8c218578fc is available with kernel 4.12-rc7 afterwards.

  I don't see this fix in the Ubuntu 16.04.3 Zesty tree (the P9 hwe
  kernel, 4.10 based).

  Need to mirror to Canonical to request they pull in:
  8c218578fcbbbdb10416c8614658bf32e3bf1655

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

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

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

2017-08-17 Thread Colin Ian King

Device is OK with 4.12, however, with 4.12 we get another issue:

[ 3996.652718] INFO: rcu_sched self-detected stall on CPU
[ 3996.652730]  23-...: (1 GPs behind) idle=73a/142/0 
softirq=5179/5179 fqs=2475 
[ 3996.652735]   (t=5250 jiffies g=6889 c=6888 q=189)
[ 3996.652748] Task dump for CPU 23:
[ 3996.652749] kopald  S0   975  2 0x0804
[ 3996.652752] Call Trace:
[ 3996.652759] [c00fefafb0b0] [c0135a24] sched_show_task+0xd4/0x150 
(unreliable)
[ 3996.652763] [c00fefafb120] [c0c36b3c] 
rcu_dump_cpu_stacks+0xd0/0x134
[ 3996.652767] [c00fefafb170] [c01867a0] 
rcu_check_callbacks+0x8a0/0xb10
[ 3996.652769] [c00fefafb2a0] [c0192958] 
update_process_times+0x48/0x90
[ 3996.652773] [c00fefafb2d0] [c01a9f60] 
tick_sched_handle.isra.8+0x30/0xb0
[ 3996.652775] [c00fefafb300] [c01aa044] tick_sched_timer+0x64/0xd0
[ 3996.652778] [c00fefafb340] [c0193424] 
__hrtimer_run_queues+0x144/0x370
[ 3996.652780] [c00fefafb3c0] [c019449c] 
hrtimer_interrupt+0xfc/0x350
[ 3996.652784] [c00fefafb490] [c0024658] 
__timer_interrupt+0x88/0x250
[ 3996.652787] [c00fefafb4e0] [c0024a30] timer_interrupt+0x90/0xe0
[ 3996.652791] [c00fefafb510] [c000b6e0] 
restore_check_irq_replay+0x54/0x70
[ 3996.652795] --- interrupt: 901 at arch_local_irq_restore+0x74/0x90
   LR = arch_local_irq_restore+0x74/0x90
[ 3996.652797] [c00fefafb800] [c0194530] 
hrtimer_interrupt+0x190/0x350 (unreliable)
[ 3996.652801] [c00fefafb820] [c0c3298c] __do_softirq+0xcc/0x41c
[ 3996.652804] [c00fefafb900] [c00fafa8] irq_exit+0xe8/0x120
[ 3996.652807] [c00fefafb920] [c0024a34] timer_interrupt+0x94/0xe0
[ 3996.652810] [c00fefafb950] [c000b6e0] 
restore_check_irq_replay+0x54/0x70
[ 3996.652815] --- interrupt: 901 at lock_timer_base+0x70/0x100
   LR = schedule_timeout+0x334/0x420
[ 3996.652817] [c00fefafbc40] [0001] 0x1 (unreliable)
[ 3996.652821] [c00fefafbca0] [c0c30a14] 
schedule_timeout+0x334/0x420
[ 3996.652824] [c00fefafbd80] [c0095bf0] kopald+0x90/0xe0
[ 3996.652827] [c00fefafbdc0] [c01214cc] kthread+0x1ac/0x1c0
[ 3996.652831] [c00fefafbe30] [c000b2e8] 
ret_from_kernel_thread+0x5c/0x74
[ 4000.060643] NMI watchdog: BUG: soft lockup - CPU#23 stuck for 23s! 
[kopald:975]
[ 4000.060653] Modules linked in: kvm_hv kvm_pr kvm cuse userio hci_vhci 
bluetooth ecdh_generic uhid hid vhost_net vhost tap snd_seq snd_seq_device 
snd_timer snd soundcore powernv_op_panel uio_pdrv_genirq ipmi_powernv 
ipmi_devintf powernv_rng leds_powernv ibmpowernv vmx_crypto ipmi_msghandler uio 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear dm_round_robin ses enclosure scsi_transport_sas 
crct10dif_vpmsum crc32c_vpmsum tg3 ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua 
dm_multipath
[ 4000.060735] CPU: 23 PID: 975 Comm: kopald Not tainted 4.12.0-11-generic #12
[ 4000.060737] task: c00fefa5b800 task.stack: c00fefaf8000
[ 4000.060739] NIP: c00165f4 LR: c00165f4 CTR: c0024200
[ 4000.060740] REGS: c00fefafb580 TRAP: 0901   Not tainted  
(4.12.0-11-generic)
[ 4000.060741] MSR: 90009033 
[ 4000.060748]   CR: 28000224  XER: 2000
[ 4000.060749] CFAR: c0024a30 SOFTE: 1 
   GPR00: c0c3298c c00fefafb800 c15a8e00 
0900 
   GPR04: c00fffac0400  01f4024e 
c00fefa5b800 
   GPR08:  c00fefaf8000  
0005 
   GPR12: c00920b8 cfacf180 
[ 4000.060764] NIP [c00165f4] arch_local_irq_restore+0x74/0x90
[ 4000.060766] LR [c00165f4] arch_local_irq_restore+0x74/0x90
[ 4000.060767] Call Trace:
[ 4000.060769] [c00fefafb800] [c0194530] 
hrtimer_interrupt+0x190/0x350 (unreliable)
[ 4000.060773] [c00fefafb820] [c0c3298c] __do_softirq+0xcc/0x41c
[ 4000.060776] [c00fefafb900] [c00fafa8] irq_exit+0xe8/0x120
[ 4000.060779] [c00fefafb920] [c0024a34] timer_interrupt+0x94/0xe0
[ 4000.060782] [c00fefafb950] [c000b6e0] 
restore_check_irq_replay+0x54/0x70
[ 4000.060787] --- interrupt: 901 at lock_timer_base+0x70/0x100
   LR = schedule_timeout+0x334/0x420
[ 4000.060788] [c00fefafbc40] [0001] 0x1 (unreliable)
[ 4000.060791] [c00fefafbca0] [c0c30a14] 
schedule_timeout+0x334/0x420
[ 4000.060795] [c00fefafbd80] [c0095bf0] kopald+0x90/0xe0
[ 4000.060798] [c00fefafbdc0] [c01214cc] kthread+0x1ac/0x1c0
[ 4000.060801] [c00fefafbe30] [c000b2e8]

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

--- Comment From dougm...@us.ibm.com 2017-08-17 15:03 EDT---
I have started a test run using the binary kernel proposed, and will see if 
there is evidence of the problem. Results will be available tomorrow.

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

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

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

Bug description:
  ---Problem Description---
  When running stress test, sometimes seeing IO hung in dmesg or seeing "Host 
adapter abort request" error.

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

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

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

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

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

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

  Tests are running again, will see what happens next.

  Update from JIRA:

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

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

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

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

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

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

  Some notes on reproduce this. I have been using the github release of
  HTX, built using the following steps:

  1. apt install make gcc g++ git libncurses5-dev libcxl-dev libdapl-dev 
(others may be required)
  2. git clone https://github.com/open-power/HTX
  3. cd HTX
  4. make
  5. make deb

  Then install the resulting "htxubuntu.deb" package.

  Note, HTX will not test disks that have a filesystem or OS installed,
  so there must be at least two disks made available to HTX by clearing
  any previous data. A partition table is optional, in my testing I have
  none.

  Also, it may be desirable to run HTX somewhere other

[Kernel-packages] [Bug 1674568] Re: depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic: No such file or directory

2017-08-17 Thread Julian Andres Klode

Apparently you have the kernel installed but somehow deleted all its
modules.

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

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

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

Title:
  depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic:
  No such file or directory

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Please affect that report to the real package; i've chosen apt by
  default as i've no idea about the faulty one.

  Doing some daily upgrades as usual, and have seen that curious error
  while setting 'initramfs':

  Setting up linux-firmware (1.164) ...
  update-initramfs: Generating /boot/initrd.img-4.10.0-14-generic
  update-initramfs: Generating /boot/initrd.img-4.10.0-13-generic
  update-initramfs: Generating /boot/initrd.img-4.8.0-25-generic
  WARNING: missing /lib/modules/4.8.0-25-generic
  Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic: No 
such file or directory
  depmod: FATAL: could not search modules: No such file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_B55FjX/lib/modules/4.8.0-25-generic/modules.order: No such 
file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_B55FjX/lib/modules/4.8.0-25-generic/modules.builtin: No 
such file or directory
  update-initramfs: Generating /boot/initrd.img-4.8.0-0-generic
  WARNING: missing /lib/modules/4.8.0-0-generic
  Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/4.8.0-0-generic: No such 
file or directory
  depmod: FATAL: could not search modules: No such file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_1ESFuC/lib/modules/4.8.0-0-generic/modules.order: No such 
file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_1ESFuC/lib/modules/4.8.0-0-generic/modules.builtin: No 
such file or directory

  That ZZ installation indeed only has 4.10 kernels installed, and is
  often checked for cleaning (autoremove/bleachbit). Packages are always
  purged when removed.

  So i wonder why and which process/script has left a crappy /boot/ list
  of initrd.img-4.8* to produce the errors above.

  oem@u64:~$ ls -la /boot/
  total 142448
  drwxr-xr-x  4 root root 4096 Mar 21 06:24 .
  drwxr-xr-x 24 root root 4096 Mar 20 19:13 ..
  -rw-r--r--  1 root root  1442575 Mar  9 14:16 abi-4.10.0-13-generic
  -rw-r--r--  1 root root  1442782 Mar  9 21:30 abi-4.10.0-14-generic
  -rw-r--r--  1 root root   204890 Mar  9 14:16 config-4.10.0-13-generic
  -rw-r--r--  1 root root   204890 Mar  9 21:30 config-4.10.0-14-generic
  drwxr-xr-x  3 root root 4096 Mar 20  2016 efi
  drwxr-xr-x  5 root root 4096 Mar 20 19:17 grub
  -rw-r--r--  1 root root 49676849 Mar 21 06:24 initrd.img-4.10.0-13-generic
  -rw-r--r--  1 root root 49672961 Mar 21 06:23 initrd.img-4.10.0-14-generic
  -rw-r--r--  1 root root 10017268 Mar 21 06:24 initrd.img-4.8.0-0-generic
  -rw-r--r--  1 root root 10017066 Mar 21 06:24 initrd.img-4.8.0-25-generic
  -rw-r--r--  1 root root   182704 Jan 28  2016 memtest86+.bin
  -rw-r--r--  1 root root   184380 Jan 28  2016 memtest86+.elf
  -rw-r--r--  1 root root   184840 Jan 28  2016 memtest86+_multiboot.bin
  -rw---  1 root root  3715891 Mar  9 14:16 System.map-4.10.0-13-generic
  -rw---  1 root root  3716749 Mar  9 21:30 System.map-4.10.0-14-generic
  -rw---  1 root root  7558928 Mar  9 14:16 vmlinuz-4.10.0-13-generic
  -rw---  1 root root  7563024 Mar  9 21:30 vmlinuz-4.10.0-14-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-firmware 1.164
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar 21 06:28:04 2017
  Dependencies:

  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1674568] [NEW] depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic: No such file or directory

You have been subscribed to a public bug:

Please affect that report to the real package; i've chosen apt by
default as i've no idea about the faulty one.

Doing some daily upgrades as usual, and have seen that curious error
while setting 'initramfs':

Setting up linux-firmware (1.164) ...
update-initramfs: Generating /boot/initrd.img-4.10.0-14-generic
update-initramfs: Generating /boot/initrd.img-4.10.0-13-generic
update-initramfs: Generating /boot/initrd.img-4.8.0-25-generic
WARNING: missing /lib/modules/4.8.0-25-generic
Ensure all necessary drivers are built into the linux image!
depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic: No such 
file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod: WARNING: could not open 
/var/tmp/mkinitramfs_B55FjX/lib/modules/4.8.0-25-generic/modules.order: No such 
file or directory
depmod: WARNING: could not open 
/var/tmp/mkinitramfs_B55FjX/lib/modules/4.8.0-25-generic/modules.builtin: No 
such file or directory
update-initramfs: Generating /boot/initrd.img-4.8.0-0-generic
WARNING: missing /lib/modules/4.8.0-0-generic
Ensure all necessary drivers are built into the linux image!
depmod: ERROR: could not open directory /lib/modules/4.8.0-0-generic: No such 
file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod: WARNING: could not open 
/var/tmp/mkinitramfs_1ESFuC/lib/modules/4.8.0-0-generic/modules.order: No such 
file or directory
depmod: WARNING: could not open 
/var/tmp/mkinitramfs_1ESFuC/lib/modules/4.8.0-0-generic/modules.builtin: No 
such file or directory

That ZZ installation indeed only has 4.10 kernels installed, and is
often checked for cleaning (autoremove/bleachbit). Packages are always
purged when removed.

So i wonder why and which process/script has left a crappy /boot/ list
of initrd.img-4.8* to produce the errors above.

oem@u64:~$ ls -la /boot/
total 142448
drwxr-xr-x  4 root root 4096 Mar 21 06:24 .
drwxr-xr-x 24 root root 4096 Mar 20 19:13 ..
-rw-r--r--  1 root root  1442575 Mar  9 14:16 abi-4.10.0-13-generic
-rw-r--r--  1 root root  1442782 Mar  9 21:30 abi-4.10.0-14-generic
-rw-r--r--  1 root root   204890 Mar  9 14:16 config-4.10.0-13-generic
-rw-r--r--  1 root root   204890 Mar  9 21:30 config-4.10.0-14-generic
drwxr-xr-x  3 root root 4096 Mar 20  2016 efi
drwxr-xr-x  5 root root 4096 Mar 20 19:17 grub
-rw-r--r--  1 root root 49676849 Mar 21 06:24 initrd.img-4.10.0-13-generic
-rw-r--r--  1 root root 49672961 Mar 21 06:23 initrd.img-4.10.0-14-generic
-rw-r--r--  1 root root 10017268 Mar 21 06:24 initrd.img-4.8.0-0-generic
-rw-r--r--  1 root root 10017066 Mar 21 06:24 initrd.img-4.8.0-25-generic
-rw-r--r--  1 root root   182704 Jan 28  2016 memtest86+.bin
-rw-r--r--  1 root root   184380 Jan 28  2016 memtest86+.elf
-rw-r--r--  1 root root   184840 Jan 28  2016 memtest86+_multiboot.bin
-rw---  1 root root  3715891 Mar  9 14:16 System.map-4.10.0-13-generic
-rw---  1 root root  3716749 Mar  9 21:30 System.map-4.10.0-14-generic
-rw---  1 root root  7558928 Mar  9 14:16 vmlinuz-4.10.0-13-generic
-rw---  1 root root  7563024 Mar  9 21:30 vmlinuz-4.10.0-14-generic

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-firmware 1.164
ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
Uname: Linux 4.10.0-14-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Mar 21 06:28:04 2017
Dependencies:

PackageArchitecture: all
SourcePackage: linux-firmware
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug zesty
-- 
depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic: No such 
file or directory
https://bugs.launchpad.net/bugs/1674568
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1704903] Re: Hisilicon D05 onboard fibre NIC link indicator LEDs don't work

2017-08-17 Thread dann frazier

Verified w/ remote eyes:

 dannf: OK, both are moved, but I don't see link lights yet.
 rodsmith: ok - lemme bring them up
 dannf: OK, link lights are on.
 rodsmith: hot damn! thanks rodsmith!
 dannf: Green plus blinking amber.

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

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

Title:
  Hisilicon D05 onboard fibre NIC link indicator LEDs don't work

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

Bug description:
  [Impact]
  There are 4 onboard NICs on the HiSilicon D05 board. Each has LEDs that 
indicate link. While the LEDs work for the 1st & 2nd NICs, they do not light up 
for the 3rd & 4th (fibre).

  [Test Case]
  Connect the 3rd & 4th (fibre) NICs to a switch, bring those interface up & 
down using ip link set dev  down/up and check that the LED accurate 
reflects the state.

  [Regression Risk]
  The fix is localized to a driver that is specific to a HiSilicon SoC. 
Regression risk is mitigated by testing on that system (boot, toggle link)

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

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

[Kernel-packages] [Bug 1688625] Re: Linux does not recognize the Hantick touchpad as a touchpad and does not enable all the functions

2017-08-17 Thread slimbook

Thanks @kaihengfeng
Neither Hantik nor Elan support Linux, we have already consulted with them.
We have the same computers with 2 different touchpad. We can assemble the 
orders with Cypress touchpad and Hantik touchpad (Synaptics does not 
manufacture in the correct size of these cases)

Your solution solved other bug opened, but partialy. 
Can you read my last response?
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1650788

Thank you very much

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

Title:
  Linux does not recognize the Hantick touchpad as a touchpad and does
  not enable all the functions

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  We have laptops with touchpad Hantick, that on Miscrosft Windows work with 
Elan driver.

  Linux does not recognize the Hantick touchpad as a touchpad and does
  not enable all the functions of evdev or libinput.

  Thanks
  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-77-generic 4.4.0-77.98
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  slimbook   1720 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May  5 20:01:33 2017
  HibernationDevice: RESUME=UUID=eef047d2-92ea-4166-a300-7a4de6af1448
  InstallationDate: Installed on 2017-05-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 090c:037c Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) 300k Pixel Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   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: SLIMBOOK KATANA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic.efi.signed 
root=UUID=00a6febb-4980-4147-a2e8-29930aed3d30 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-77-generic N/A
   linux-backports-modules-4.4.0-77-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 16L
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: KATANA
  dmi.board.vendor: SLIMBOOK
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SLIMBOOK
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr16L:bd07/25/2016:svnSLIMBOOK:pnKATANA:pvrTBDbyOEM:rvnSLIMBOOK:rnKATANA:rvrType2-BoardVersion:cvnSLIMBOOK:ct10:cvrChassisVersion:
  dmi.product.name: KATANA
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: SLIMBOOK

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

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

[Kernel-packages] [Bug 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count

2017-08-17 Thread Dan Streetman

Since this bug has been long-since marked 'fix released', I opened a new
bug 1711407.  Let's all please use that one for continued discussion of
this problem.

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

Title:
  unregister_netdevice: waiting for lo to become free. Usage count

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  Confirmed
Status in linux source package in Vivid:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

  Users of kernels that utilize NFS may see the following messages when
  shutting down and starting containers:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  Setup multiple containers in parallel to mount and NFS share, create
  some traffic and shutdown. Eventually you will see the kernel message.

  Dave's script here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403152/comments/24

  [Fix]
  commit de84d89030fa4efa44c02c96c8b4a8176042c4ff upstream

  --

  I currently running trusty latest patches and i get on these hardware
  and software:

  Ubuntu 3.13.0-43.72-generic 3.13.11.11

  processor : 7
  vendor_id : GenuineIntel
  cpu family: 6
  model : 77
  model name: Intel(R) Atom(TM) CPU  C2758  @ 2.40GHz
  stepping  : 8
  microcode : 0x11d
  cpu MHz   : 2400.000
  cache size: 1024 KB
  physical id   : 0
  siblings  : 8
  core id   : 7
  cpu cores : 8
  apicid: 14
  initial apicid: 14
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 11
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm 
sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch 
arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
  bogomips  : 4799.48
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 36 bits physical, 48 bits virtual
  power management:

  somehow reproducable the subjected error, and lxc is working still but
  not more managable until a reboot.

  managable means every command hangs.

  I saw there are alot of bugs but they seams to relate to older version
  and are closed, so i decided to file a new one?

  I run alot of machine with trusty an lxc containers but only these kind of 
machines produces these errors, all
  other don't show these odd behavior.

  thx in advance

  meno

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

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

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

2017-08-17 Thread Dan Streetman

Can anyone experiencing this issue please provide details such as:

-what release are you using (trusty/xenial/zesty)?

-what kernel version are you using?

-do you have specific steps to reproduce the problem?

** Description changed:

  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported here
  instead of that bug.
+ 
+ --
+ 
+ [Impact]
+ 
+ When shutting down and starting containers the container network
+ namespace may experience a dst reference counting leak which results in
+ this message repeated in the logs:
+ 
+ unregister_netdevice: waiting for lo to become free. Usage count = 1
+ 
+ This can cause issues when trying to create net network namespace and
+ thus block a user from creating new containers.
+ 
+ [Test Case]
+ 
+ ?

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

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

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  In Progress

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  ?

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

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

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

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1711407

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

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

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

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

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  In Progress

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  ?

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

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

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

This change was made by a bot.

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

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

Title:
  regression: UI terribly slow or not usable in linux kernel 4.4.0-92

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Recently after running a bunch of upgrades, including the kernel, my
  system became terribly slow. At one time after a successful login,
  opening Chrome Browser, which is usually really fast to open, took
  more than 10 minutes to open. After that I tried to even login and the
  system never left from the login screen.

  I decided to hard-reset my computer and booted instead with the
  previous available Kernel version. (Version 4,4,0-91) and everything
  works fine.

  In summary:
  Linux Kernel 4.4.0-91-generic and everything before it works fine.
  Linux Kernel 4.4.0-92-generic makes my computer unusable.

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

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

[Kernel-packages] [Bug 1711407] [NEW] unregister_netdevice: waiting for lo to become free

2017-08-17 Thread Dan Streetman

Public bug reported:

This is a "continuation" of bug 1403152, as that bug has been marked
"fix released" and recent reports of failure may (or may not) be a new
bug.  Any further reports of the problem should please be reported here
instead of that bug.

--

[Impact]

When shutting down and starting containers the container network
namespace may experience a dst reference counting leak which results in
this message repeated in the logs:

unregister_netdevice: waiting for lo to become free. Usage count = 1

This can cause issues when trying to create net network namespace and
thus block a user from creating new containers.

[Test Case]

?

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  In Progress

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  ?

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

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

[Kernel-packages] [Bug 1708399] Re: kernel panic -not syncing: Fatal exception: panic_on_oops

2017-08-17 Thread Frank Heimes

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1709282] Re: Plantronics Blackwire C520-M - Cannot get freq at ep 0x1, 0x81

I did not have enough time to test, because its my work laptop, and vmware was 
slow, and had the sound lagging - might be due to the i915 modules, they were 
missing for 4.13, and it seemed vmware modules need more patching. Much more 
stable on 4.10.
Can you please tell me what was changed? So i can modify in my 4.10 kernel and 
recompile.

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

Title:
  Plantronics Blackwire C520-M - Cannot get freq at ep 0x1, 0x81

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Very similar to this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622763

  == the Problem ==
  Listening to sound on a vmware machine, hosted by Ubuntu, the devices 
freezes, and cannot listen to sound anymore, i have to connect/disconnect the 
device. 
  After i disconnect i get the logs:
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.344893] usb 1-1: 1:1: cannot get 
freq at ep 0x81
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.347094] usb 1-1: 2:1: cannot get 
freq at ep 0x1
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.358786] usb 1-1: Warning! 
Unlikely big volume range (=8192), cval->res is probably wrong.
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.358787] usb 1-1: [11] FU 
[Sidetone Playback Volume] ch = 1, val = 0/8192/1
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.641980] input: Plantronics 
Plantronics C520-M as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.3/0003:047F:C036.000F/input/input32
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.702298] plantronics 
0003:047F:C036.000F: input,hiddev0,hidraw2: USB HID v1.11 Device [Plantronics 
Plantronics C520-M] on usb-:00:14.0-1/input3
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.747708] usb 1-1: 2:1: cannot get 
freq at ep 0x1
  Aug  8 13:52:16 tim-lap-143 kernel: [112289.406154] usb 1-1: reset full-speed 
USB device number 19 using xhci_hcd
  Aug  8 13:52:16 tim-lap-143 kernel: [112289.906146] usb 1-1: reset full-speed 
USB device number 19 using xhci_hcd

  = The solution ==

  It is simple, add this USB ID to the
  sound/usb/quirks.c:snd_usb_get_sample_rate_quirk function.

  
  version signature: Ubuntu 4.10.0-28.32-generic 4.10.17

  Thanks!
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   mihai.cin...@3pillar.corp   2208 F...m pulseaudio
   /dev/snd/controlC0:  mihai.cin...@3pillar.corp   2208 F pulseaudio
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=d363a75c-d8a4-467d-a576-a46b3c317861
  InstallationDate: Installed on 2017-06-22 (47 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Precision 3510
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash i915.enable_guc_loading=1 
i915.enable_guc_submission=1 intel_pstate=skylake_hwp i915.enable_psr=1 
i915.disable_power_well=0 i915.enable_rc6=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-28-generic N/A
   linux-backports-modules-4.10.0-28-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-28-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-07-21 (18 days ago)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 05/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.4
  dmi.board.name: 00D283
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.4:bd05/12/2017:svnDellInc.:pnPrecision3510:pvr:rvnDellInc.:rn00D283:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 3510
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1711396] Re: regression: UI terribly slow or not usable in linux kernel 4.4.0-92

** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)

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

Title:
  regression: UI terribly slow or not usable in linux kernel 4.4.0-92

Status in linux package in Ubuntu:
  New

Bug description:
  Recently after running a bunch of upgrades, including the kernel, my
  system became terribly slow. At one time after a successful login,
  opening Chrome Browser, which is usually really fast to open, took
  more than 10 minutes to open. After that I tried to even login and the
  system never left from the login screen.

  I decided to hard-reset my computer and booted instead with the
  previous available Kernel version. (Version 4,4,0-91) and everything
  works fine.

  In summary:
  Linux Kernel 4.4.0-91-generic and everything before it works fine.
  Linux Kernel 4.4.0-92-generic makes my computer unusable.

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

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

[Kernel-packages] [Bug 1711400] [NEW] Update firmware for 4.12 linux-hwe-edge kernel

2017-08-17 Thread Seth Forshee

Public bug reported:

Add and update firmware files as necessary to support a 4.12-based
kernel in the xenial linux-hwe-edge package.

** Affects: linux-firmware (Ubuntu)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: Invalid

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

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

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

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

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

** Changed in: linux-firmware (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  Update firmware for 4.12 linux-hwe-edge kernel

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

Bug description:
  Add and update firmware files as necessary to support a 4.12-based
  kernel in the xenial linux-hwe-edge package.

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

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

[Kernel-packages] [Bug 1711401] [NEW] accessing /dev/hvc1 with stress-ng on Ubuntu xenia causes crash

2017-08-17 Thread Colin Ian King

Public bug reported:

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

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

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Colin Ian King (colin-king)
 Status: In Progress

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

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

Status in linux package in Ubuntu:
  In Progress

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

  [ 2096.476610] hvc_open: request_irq failed with rc -16.
  [ 2096.476634] Unable to handle kernel paging request for data at address 
0x00a8
  [ 2096.476641] Faulting instruction address: 0xc0b0d8a4
  [ 2096.476647] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 2096.476650] SMP NR_CPUS=2048 NUMA PowerNV
  [ 2096.476657] Modules linked in: kvm_hv kvm_pr kvm cuse userio hci_vhci 
bluetooth uhid hid vhost_net vhost macvtap macvlan snd_seq snd_seq_device 
snd_timer snd soundcore ipmi_powernv ipmi_msghandler vmx_crypto leds_powernv 
uio_pdrv_genirq uio powernv_rng ibmpowernv ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0

[Kernel-packages] [Bug 1688625] Re: Linux does not recognize the Hantick touchpad as a touchpad and does not enable all the functions

Well, then you probably need to ask Hantick or Elan for their support.

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

Title:
  Linux does not recognize the Hantick touchpad as a touchpad and does
  not enable all the functions

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  We have laptops with touchpad Hantick, that on Miscrosft Windows work with 
Elan driver.

  Linux does not recognize the Hantick touchpad as a touchpad and does
  not enable all the functions of evdev or libinput.

  Thanks
  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-77-generic 4.4.0-77.98
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  slimbook   1720 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May  5 20:01:33 2017
  HibernationDevice: RESUME=UUID=eef047d2-92ea-4166-a300-7a4de6af1448
  InstallationDate: Installed on 2017-05-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 090c:037c Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) 300k Pixel Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   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: SLIMBOOK KATANA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic.efi.signed 
root=UUID=00a6febb-4980-4147-a2e8-29930aed3d30 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-77-generic N/A
   linux-backports-modules-4.4.0-77-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 16L
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: KATANA
  dmi.board.vendor: SLIMBOOK
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SLIMBOOK
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr16L:bd07/25/2016:svnSLIMBOOK:pnKATANA:pvrTBDbyOEM:rvnSLIMBOOK:rnKATANA:rvrType2-BoardVersion:cvnSLIMBOOK:ct10:cvrChassisVersion:
  dmi.product.name: KATANA
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: SLIMBOOK

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

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

[Kernel-packages] [Bug 1711396] Re: regression: UI terribly slow or not usable in linux kernel 4.4.0-92

** Attachment added: "uname-a.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1711396/+attachment/4934294/+files/uname-a.log

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

Title:
  regression: UI terribly slow or not usable in linux kernel 4.4.0-92

Status in linux-meta package in Ubuntu:
  New

Bug description:
  Recently after running a bunch of upgrades, including the kernel, my
  system became terribly slow. At one time after a successful login,
  opening Chrome Browser, which is usually really fast to open, took
  more than 10 minutes to open. After that I tried to even login and the
  system never left from the login screen.

  I decided to hard-reset my computer and booted instead with the
  previous available Kernel version. (Version 4,4,0-91) and everything
  works fine.

  In summary:
  Linux Kernel 4.4.0-91-generic and everything before it works fine.
  Linux Kernel 4.4.0-92-generic makes my computer unusable.

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

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

[Kernel-packages] [Bug 1709282] Re: Plantronics Blackwire C520-M - Cannot get freq at ep 0x1, 0x81

So the bug is gone, right?

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

Title:
  Plantronics Blackwire C520-M - Cannot get freq at ep 0x1, 0x81

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Very similar to this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622763

  == the Problem ==
  Listening to sound on a vmware machine, hosted by Ubuntu, the devices 
freezes, and cannot listen to sound anymore, i have to connect/disconnect the 
device. 
  After i disconnect i get the logs:
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.344893] usb 1-1: 1:1: cannot get 
freq at ep 0x81
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.347094] usb 1-1: 2:1: cannot get 
freq at ep 0x1
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.358786] usb 1-1: Warning! 
Unlikely big volume range (=8192), cval->res is probably wrong.
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.358787] usb 1-1: [11] FU 
[Sidetone Playback Volume] ch = 1, val = 0/8192/1
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.641980] input: Plantronics 
Plantronics C520-M as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.3/0003:047F:C036.000F/input/input32
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.702298] plantronics 
0003:047F:C036.000F: input,hiddev0,hidraw2: USB HID v1.11 Device [Plantronics 
Plantronics C520-M] on usb-:00:14.0-1/input3
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.747708] usb 1-1: 2:1: cannot get 
freq at ep 0x1
  Aug  8 13:52:16 tim-lap-143 kernel: [112289.406154] usb 1-1: reset full-speed 
USB device number 19 using xhci_hcd
  Aug  8 13:52:16 tim-lap-143 kernel: [112289.906146] usb 1-1: reset full-speed 
USB device number 19 using xhci_hcd

  = The solution ==

  It is simple, add this USB ID to the
  sound/usb/quirks.c:snd_usb_get_sample_rate_quirk function.

  
  version signature: Ubuntu 4.10.0-28.32-generic 4.10.17

  Thanks!
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   mihai.cin...@3pillar.corp   2208 F...m pulseaudio
   /dev/snd/controlC0:  mihai.cin...@3pillar.corp   2208 F pulseaudio
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=d363a75c-d8a4-467d-a576-a46b3c317861
  InstallationDate: Installed on 2017-06-22 (47 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Precision 3510
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash i915.enable_guc_loading=1 
i915.enable_guc_submission=1 intel_pstate=skylake_hwp i915.enable_psr=1 
i915.disable_power_well=0 i915.enable_rc6=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-28-generic N/A
   linux-backports-modules-4.10.0-28-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-28-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-07-21 (18 days ago)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 05/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.4
  dmi.board.name: 00D283
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.4:bd05/12/2017:svnDellInc.:pnPrecision3510:pvr:rvnDellInc.:rn00D283:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 3510
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1711396] Re: regression: UI terribly slow or not usable in linux kernel 4.4.0-92

Attachments where generated in the working configuration (4.4.0-91)

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

Title:
  regression: UI terribly slow or not usable in linux kernel 4.4.0-92

Status in linux-meta package in Ubuntu:
  New

Bug description:
  Recently after running a bunch of upgrades, including the kernel, my
  system became terribly slow. At one time after a successful login,
  opening Chrome Browser, which is usually really fast to open, took
  more than 10 minutes to open. After that I tried to even login and the
  system never left from the login screen.

  I decided to hard-reset my computer and booted instead with the
  previous available Kernel version. (Version 4,4,0-91) and everything
  works fine.

  In summary:
  Linux Kernel 4.4.0-91-generic and everything before it works fine.
  Linux Kernel 4.4.0-92-generic makes my computer unusable.

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

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

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

--- Comment From h.carst...@de.ibm.com 2017-08-17 11:37 EDT---
Comment on attachment 119988
tlb test patch

We will provide two new patches, since this patch solves only part of
the problem. Therefore marking this patch as obsolete.

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

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

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

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

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

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

[Kernel-packages] [Bug 1711396] Re: regression: UI terribly slow or not usable in linux kernel 4.4.0-92

** Attachment added: "lsb_release-a.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1711396/+attachment/4934285/+files/lsb_release-a.log

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

Title:
  regression: UI terribly slow or not usable in linux kernel 4.4.0-92

Status in linux-meta package in Ubuntu:
  New

Bug description:
  Recently after running a bunch of upgrades, including the kernel, my
  system became terribly slow. At one time after a successful login,
  opening Chrome Browser, which is usually really fast to open, took
  more than 10 minutes to open. After that I tried to even login and the
  system never left from the login screen.

  I decided to hard-reset my computer and booted instead with the
  previous available Kernel version. (Version 4,4,0-91) and everything
  works fine.

  In summary:
  Linux Kernel 4.4.0-91-generic and everything before it works fine.
  Linux Kernel 4.4.0-92-generic makes my computer unusable.

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

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

[Kernel-packages] [Bug 1711396] Re: regression: UI terribly slow or not usable in linux kernel 4.4.0-92

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

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

Title:
  regression: UI terribly slow or not usable in linux kernel 4.4.0-92

Status in linux-meta package in Ubuntu:
  New

Bug description:
  Recently after running a bunch of upgrades, including the kernel, my
  system became terribly slow. At one time after a successful login,
  opening Chrome Browser, which is usually really fast to open, took
  more than 10 minutes to open. After that I tried to even login and the
  system never left from the login screen.

  I decided to hard-reset my computer and booted instead with the
  previous available Kernel version. (Version 4,4,0-91) and everything
  works fine.

  In summary:
  Linux Kernel 4.4.0-91-generic and everything before it works fine.
  Linux Kernel 4.4.0-92-generic makes my computer unusable.

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

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

[Kernel-packages] [Bug 1711396] Re: regression: UI terribly slow or not usable in linux kernel 4.4.0-92

** Attachment added: "lshw-C-display.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1711396/+attachment/4934296/+files/lshw-C-display.log

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

Title:
  regression: UI terribly slow or not usable in linux kernel 4.4.0-92

Status in linux-meta package in Ubuntu:
  New

Bug description:
  Recently after running a bunch of upgrades, including the kernel, my
  system became terribly slow. At one time after a successful login,
  opening Chrome Browser, which is usually really fast to open, took
  more than 10 minutes to open. After that I tried to even login and the
  system never left from the login screen.

  I decided to hard-reset my computer and booted instead with the
  previous available Kernel version. (Version 4,4,0-91) and everything
  works fine.

  In summary:
  Linux Kernel 4.4.0-91-generic and everything before it works fine.
  Linux Kernel 4.4.0-92-generic makes my computer unusable.

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

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

[Kernel-packages] [Bug 1711396] Re: regression: UI terribly slow or not usable in linux kernel 4.4.0-92

** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1711396/+attachment/4934295/+files/version.log

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

Title:
  regression: UI terribly slow or not usable in linux kernel 4.4.0-92

Status in linux-meta package in Ubuntu:
  New

Bug description:
  Recently after running a bunch of upgrades, including the kernel, my
  system became terribly slow. At one time after a successful login,
  opening Chrome Browser, which is usually really fast to open, took
  more than 10 minutes to open. After that I tried to even login and the
  system never left from the login screen.

  I decided to hard-reset my computer and booted instead with the
  previous available Kernel version. (Version 4,4,0-91) and everything
  works fine.

  In summary:
  Linux Kernel 4.4.0-91-generic and everything before it works fine.
  Linux Kernel 4.4.0-92-generic makes my computer unusable.

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

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

[Kernel-packages] [Bug 1711396] Re: regression: UI terribly slow or not usable in linux kernel 4.4.0-92

** Attachment added: "dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1711396/+attachment/4934299/+files/dmesg.log

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

Title:
  regression: UI terribly slow or not usable in linux kernel 4.4.0-92

Status in linux-meta package in Ubuntu:
  New

Bug description:
  Recently after running a bunch of upgrades, including the kernel, my
  system became terribly slow. At one time after a successful login,
  opening Chrome Browser, which is usually really fast to open, took
  more than 10 minutes to open. After that I tried to even login and the
  system never left from the login screen.

  I decided to hard-reset my computer and booted instead with the
  previous available Kernel version. (Version 4,4,0-91) and everything
  works fine.

  In summary:
  Linux Kernel 4.4.0-91-generic and everything before it works fine.
  Linux Kernel 4.4.0-92-generic makes my computer unusable.

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

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

[Kernel-packages] [Bug 1711396] [NEW] regression: UI terribly slow or not usable in linux kernel 4.4.0-92

Public bug reported:

Recently after running a bunch of upgrades, including the kernel, my
system became terribly slow. At one time after a successful login,
opening Chrome Browser, which is usually really fast to open, took more
than 10 minutes to open. After that I tried to even login and the system
never left from the login screen.

I decided to hard-reset my computer and booted instead with the previous
available Kernel version. (Version 4,4,0-91) and everything works fine.

In summary:
Linux Kernel 4.4.0-91-generic and everything before it works fine.
Linux Kernel 4.4.0-92-generic makes my computer unusable.

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

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

Title:
  regression: UI terribly slow or not usable in linux kernel 4.4.0-92

Status in linux-meta package in Ubuntu:
  New

Bug description:
  Recently after running a bunch of upgrades, including the kernel, my
  system became terribly slow. At one time after a successful login,
  opening Chrome Browser, which is usually really fast to open, took
  more than 10 minutes to open. After that I tried to even login and the
  system never left from the login screen.

  I decided to hard-reset my computer and booted instead with the
  previous available Kernel version. (Version 4,4,0-91) and everything
  works fine.

  In summary:
  Linux Kernel 4.4.0-91-generic and everything before it works fine.
  Linux Kernel 4.4.0-92-generic makes my computer unusable.

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

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

[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89

2017-08-17 Thread Kleber Sacilotto de Souza

Xenial kernel 4.4.0-92.115 had a quick fix for the issue, which was to
revert the patch that introduced the regression ("netfilter: synproxy:
fix conntrackd interaction"). The kernel build that's in -proposed
(currently 4.4.0-93.116) reapplies this patch and applies on top the
proper fix found upstream ("netfilter: nf_ct_ext: fix possible panic
after nf_ct_extend_unregister").

Could someone please verify if the kernel in -proposed really fixes the
issue?

Thank you.

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

Title:
  Creating conntrack entry failure with kernel 4.4.0-89

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Released

Bug description:
  The functional job failure rate is at 100%. Every time some test gets
  stuck and job is killed after timeout.

  logstash query:
  
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
  %22gate-neutron-dsvm-functional-ubuntu-
  
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22

  2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
  dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
  15261 Killed  timeout -s 9 ${REMAINING_TIME}m bash -c
  "source $WORKSPACE/devstack-gate/functions.sh && $cmd"

  There are a few test executors left, which means there are more tests
  stuck:

  stack15468 15445 15468  0.0  0.0   328   796 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpDTLPoX
  stack15469 15468 15469  1.5  1.8 139332 150008 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
  stack15470 15445 15470  0.0  0.0   328   700 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpICNqRQ
  stack15471 15470 15471  1.6  2.0 152056 164812 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
  stack15474 15445 15474  0.0  0.0   328   792 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpe646Tl
  stack15475 15474 15475  1.6  1.9 149972 162516 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
  stack15476 15445 15476  0.0  0.0   328   804 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpv2ovhz
  stack15477 15476 15477  1.2  1.8 136760 149160 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
  stack15478 15445 15478  0.0  0.0   328   712 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpDqXE8S
  stack15479 15478 15479  1.5  1.9 148784 161004 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
  stack15480 15445 15480  0.0  0.0   328   804 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpTmmShS
  stack15482 15480 15482  1.6  1.9 148856 161516 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS

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

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

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

2017-08-17 Thread Frank Heimes

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

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

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

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

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

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

  vhost: cache used event for better performance

  --

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1711283] Re: few kernel selftest failed on Ubuntu 17.10

2017-08-17 Thread Frank Heimes

** Package changed: kernel-package (Ubuntu) => linux (Ubuntu)

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

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

Title:
  few kernel selftest failed on Ubuntu 17.10

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

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-01 05:11:09 ==
  Problem Description
  
  Few kernel selftest failed on Ubuntu 17.10

  Environment
  --
  Kernel Build:  4.11.0-10-generic
  System Name : ltc-test-ci2
  Model  : 8247-22L
  Platform:  PowerNV ( P8 )

  Uname output
  ---
  # uname -a
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Get kernel source using apt source
  2. Start powerpc specific tests

  The following FAILS are observed.
  selftests:  cycles_test [FAIL]
  selftests:  cycles_with_freeze_test [FAIL]
  selftests:  pmc56_overflow_test [FAIL]
  selftests:  ebb_vs_cpu_event_test [FAIL]
  selftests:  cpu_event_vs_ebb_test [FAIL]
  selftests:  task_event_vs_ebb_test [FAIL]
  selftests:  multi_ebb_procs_test [FAIL]
  selftests:  multi_counter_test [FAIL]
  selftests:  pmae_handling_test [FAIL]
  selftests:  close_clears_pmcc_test [FAIL]
  selftests:  instruction_count_test [FAIL]
  selftests:  ebb_on_willing_child_test [FAIL]
  selftests:  back_to_back_ebbs_test [FAIL]
  selftests:  lost_exception_test [FAIL]
  selftests:  cycles_with_mmcr2_test [FAIL]
  selftests:  tm-vmxcopy [FAIL]

  Full run log is attached.

  == Comment: #5 - Harish Sriram  - 2017-08-08 03:33:36 ==
  With the latest ubuntu mainline kernel 4.13-rc4 from 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc4/, I see following 
additional failures

  selftests:  ptrace-gpr [FAIL]
  selftests:  ptrace-tm-gpr [FAIL]
  selftests:  ptrace-tm-spd-gpr [FAIL]

  # uname -a
  Linux ltc-test-ci2 4.13.0-041300rc4-generic #201708062231 SMP Mon Aug 7 
03:29:19 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Thanks,
  Harish

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

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

[Kernel-packages] [Bug 1711283] [NEW] few kernel selftest failed on Ubuntu 17.10

You have been subscribed to a public bug:

== Comment: #0 - Harish Sriram  - 2017-08-01 05:11:09 ==
Problem Description

Few kernel selftest failed on Ubuntu 17.10

Environment
--
Kernel Build:  4.11.0-10-generic
System Name : ltc-test-ci2
Model  : 8247-22L
Platform:  PowerNV ( P8 )

Uname output
---
# uname -a
Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux

Steps to reproduce:

1. Get kernel source using apt source
2. Start powerpc specific tests

The following FAILS are observed.
selftests:  cycles_test [FAIL]
selftests:  cycles_with_freeze_test [FAIL]
selftests:  pmc56_overflow_test [FAIL]
selftests:  ebb_vs_cpu_event_test [FAIL]
selftests:  cpu_event_vs_ebb_test [FAIL]
selftests:  task_event_vs_ebb_test [FAIL]
selftests:  multi_ebb_procs_test [FAIL]
selftests:  multi_counter_test [FAIL]
selftests:  pmae_handling_test [FAIL]
selftests:  close_clears_pmcc_test [FAIL]
selftests:  instruction_count_test [FAIL]
selftests:  ebb_on_willing_child_test [FAIL]
selftests:  back_to_back_ebbs_test [FAIL]
selftests:  lost_exception_test [FAIL]
selftests:  cycles_with_mmcr2_test [FAIL]
selftests:  tm-vmxcopy [FAIL]

Full run log is attached.

== Comment: #5 - Harish Sriram  - 2017-08-08 03:33:36 ==
With the latest ubuntu mainline kernel 4.13-rc4 from 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc4/, I see following 
additional failures

selftests:  ptrace-gpr [FAIL]
selftests:  ptrace-tm-gpr [FAIL]
selftests:  ptrace-tm-spd-gpr [FAIL]

# uname -a
Linux ltc-test-ci2 4.13.0-041300rc4-generic #201708062231 SMP Mon Aug 7 
03:29:19 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

Thanks,
Harish

** Affects: ubuntu-power-systems
 Importance: High
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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


** Tags: architecture-ppc64le bugnameltc-157168 kernel-da-key severity-high 
targetmilestone-inin---
-- 
few kernel selftest failed on Ubuntu 17.10
https://bugs.launchpad.net/bugs/1711283
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

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

2017-08-17 Thread Joseph Salisbury

** Tags added: kernel-da-key

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

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

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

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

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

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

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

  vhost: cache used event for better performance

  --

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1711368] Re: Artful update to v4.12.8 stable release

2017-08-17 Thread Andy Whitcroft

Applying v4.12.8, applied as below:

  Linux 4.12.8
  MIPS: Octeon: Fix broken EDAC driver.
  Revert "MIPS: Don't unnecessarily include kmalloc.h into ."
  MIPS: DEC: Fix an int-handler.S CPU_DADDI_WORKAROUNDS regression
  pinctrl: meson-gxl: Add missing GPIODV_18 pin entry
  pinctrl: meson-gxbb: Add missing GPIODV_18 pin entry
  pinctrl: samsung: Remove bogus irq_[un]mask from resource management
  pinctrl: uniphier: fix WARN_ON() of pingroups dump on LD20
  pinctrl: uniphier: fix WARN_ON() of pingroups dump on LD11
  pinctrl: intel: merrifield: Correct UART pin lists
  pinctrl: sunxi: add a missing function of A10/A20 pinctrl driver
  pinctrl: cherryview: Add Setzer models to the Chromebook DMI quirk
  pnfs/blocklayout: require 64-bit sector_t
  iio: adc: vf610_adc: Fix VALT selection value for REFSEL bits
  xhci: Reset Renesas uPD72020x USB controller for 32-bit DMA issue
  PCI: Add pci_reset_function_locked()
  PCI: Remove __pci_dev_reset() and pci_dev_reset()
  PCI: Protect pci_error_handlers->reset_notify() usage with device_lock()
  usb:xhci:Add quirk for Certain failing HP keyboard on reset after resume
  usb: quirks: Add no-lpm quirk for Moshi USB to Ethernet Adapter
  usb: core: unlink urbs from the tail of the endpoint's urb_list
  USB: Check for dropped connection before switching to full speed
  usb: renesas_usbhs: Fix UGCTRL2 value for R-Car Gen3
  usb: gadget: udc: renesas_usb3: Fix usb_gadget_giveback_request() calling
  block: Make blk_mq_delay_kick_requeue_list() rerun the queue at a quiet time
  firmware: avoid invalid fallback aborts by using killable wait
  firmware: fix batched requests - send wake up on failure on direct lookups
  firmware: fix batched requests - wake all waiters
  uas: Add US_FL_IGNORE_RESIDUE for Initio Corporation INIC-3069
  staging: comedi: comedi_fops: do not call blocking ops when !TASK_RUNNING
  iio: adc: Revert "axp288: Drop bogus AXP288_ADC_TS_PIN_CTRL register 
modifications"
  iio: light: tsl2563: use correct event code
  iio: pressure: st_pressure_core: disable multiread by default for LPS22HB
  iio: accel: bmc150: Always restore device to normal mode after suspend-resume
  iio: accel: st_accel: add SPI-3wire support
  iio: aspeed-adc: wait for initial sequence.
  staging:iio:resolver:ad2s1210 fix negative IIO_ANGL_VEL read
  USB: hcd: Mark secondary HCD as dead if the primary one died
  usb: musb: fix tx fifo flush handling again
  USB: serial: pl2303: add new ATEN device id
  USB: serial: cp210x: add support for Qivicon USB ZigBee dongle
  USB: serial: option: add D-Link DWM-222 device ID
  drm/i915: Fix out-of-bounds array access in bdw_load_gamma_lut
  drm/etnaviv: Fix off-by-one error in reloc checking
  drm/bridge: tc358767: fix probe without attached output node
  nfs/flexfiles: fix leak of nfs4_ff_ds_version arrays
  mmc: mmc: correct the logic for setting HS400ES signal voltage
  nand: fix wrong default oob layout for small pages using soft ecc
  i2c: designware: Some broken DSTDs use 1MiHz instead of 1MHz
  fuse: initialize the flock flag in fuse_file on allocation
  target: Fix node_acl demo-mode + uncached dynamic shutdown regression
  usb-storage: fix deadlock involving host lock and scsi_done
  iscsi-target: Fix iscsi_np reset hung task during parallel delete
  iscsi-target: fix memory leak in iscsit_setup_text_cmd()
  mtd: nand: Declare tBERS, tR and tPROG as u64 to avoid integer overflow
  mtd: nand: Fix timing setup for NANDs that do not support SET FEATURES
  mtd: nand: atmel: Fix DT backward compatibility in pmecc.c
  pinctrl: armada-37xx: Fix number of pin in south bridge
  xfs: Fix leak of discard bio
  xtensa: don't limit csum_partial export by CONFIG_NET
  xtensa: mm/cache: add missing EXPORT_SYMBOLs
  xtensa: fix cache aliasing handling code for WT cache
  futex: Remove unnecessary warning from get_futex_key
  mm: fix list corruptions on shmem shrinklist
  mm: ratelimit PFNs busy info message

Dropped (already applied):

  powerpc: Fix /proc/cpuinfo revision for POWER9 DD2

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

Title:
  Artful update to v4.12.8 stable release

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Apply stable release v4.12.8.

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

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

[Kernel-packages] [Bug 1711368] [NEW] Artful update to v4.12.8 stable release

2017-08-17 Thread Andy Whitcroft

Public bug reported:

Apply stable release v4.12.8.

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Andy Whitcroft (apw)
 Status: In Progress

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Andy Whitcroft (apw)

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

Title:
  Artful update to v4.12.8 stable release

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Apply stable release v4.12.8.

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

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

[Kernel-packages] [Bug 1711056] Re: Backport more recent Broadcom bnxt_en driver

2017-08-17 Thread Juerg Haefliger

Test packages: http://people.canonical.com/~juergh/review/lp1711056/


** Description changed:

- We need to support newer Broadcom NetXtreme NICs than what the current
- bnxt_en driver can handle.
+ [Impact]
  
- The plan is to provide a separate driver module called bnxt_en_bpo which
- is a backported driver from Broadcom. This driver will be modified to
- only support the new NICs that the current kernel driver does not
- support.
+ The current Xenial bnxt_en driver only supports a limited (old) set of
+ Broadcom NICs. We want to support newer NICs in Xenial without adding
+ risk for existing users.
+ 
+ The plan is to provide a separate driver called bnxt_en_bpo which is a
+ backported driver from Broadcom. This driver will be modified to only
+ support the new NICs that the current kernel driver does not support so
+ that they both can co-exist.
+ 
+ In other words, NICs that used to be supported by Xenial will still be
+ managed by the current (unmodified) bnxt_en driver. Newer NICs will be
+ managed by the new bnxt_en_bpo driver.
+ 
+ [Test Case]
+ 
+ Due to the unavailability of Broadcom HW, the only test that was run was
+ to manually load both the bnxt_en and bnxt_en_bpo module to ensure that
+ they can co-exist.
+ 
+ [Regression Potential]
+ 
+ There should be no regression potential, since the current driver is not
+ modified and the new driver only loads for NICs that are not handled by
+ the current driver.

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

Title:
  Backport more recent Broadcom bnxt_en driver

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

Bug description:
  [Impact]

  The current Xenial bnxt_en driver only supports a limited (old) set of
  Broadcom NICs. We want to support newer NICs in Xenial without adding
  risk for existing users.

  The plan is to provide a separate driver called bnxt_en_bpo which is a
  backported driver from Broadcom. This driver will be modified to only
  support the new NICs that the current kernel driver does not support
  so that they both can co-exist.

  In other words, NICs that used to be supported by Xenial will still be
  managed by the current (unmodified) bnxt_en driver. Newer NICs will be
  managed by the new bnxt_en_bpo driver.

  [Test Case]

  Due to the unavailability of Broadcom HW, the only test that was run
  was to manually load both the bnxt_en and bnxt_en_bpo module to ensure
  that they can co-exist.

  [Regression Potential]

  There should be no regression potential, since the current driver is
  not modified and the new driver only loads for NICs that are not
  handled by the current driver.

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

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

[Kernel-packages] [Bug 1711009] Re: jfs filesystem is crashy, multiple panic and I/O errors

2017-08-17 Thread Mathieu Trudel-Lapierre

I can't run apport-collect in that environment, but this is trivial to
reproduce in any ppc64el qemu VM. Just use JFS as the filesystem for the
root partition.

I can provide scripts to help setting up the VM.

** Changed in: linux (Ubuntu)
   Status: Triaged => 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/1711009

Title:
  jfs filesystem is crashy, multiple panic and I/O errors

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

Bug description:
  Loading initial ramdisk ...
  OF stdout device is: /vdevice/vty@7100
  Preparing to boot Linux version 4.11.0-13-generic (buildd@bos01-ppc64el-022) 
(gcc version 6.4.0 20170724 (Ubuntu 6.4.0-2ubuntu1) ) #19-Ubuntu SMP Thu Aug 3 
15:11:49 UTC 2017 (Ubuntu 4.11.0-13.19-generic 4.11.12)
  Detected machine type: 0101
  command line: BOOT_IMAGE=/boot/vmlinux-4.11.0-13-generic 
root=UUID=8c6162e8-9bb1-4171-a901-30e001222a14 ro splash quiet
  Max number of cores passed to firmware: 2048 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0762
alloc_top: 3000
alloc_top_hi : 00078000
rmo_top  : 3000
ram_top  : 00078000
  instantiating rtas at 0x2fff... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x0763 -> 0x076309e6
  Device tree struct  0x0764 -> 0x0765
  Quiescing Open Firmware ...
  Booting Linux via __start() @ 0x0200 ...
   -> smp_release_cpus()
  spinning_secondaries = 7
   <- smp_release_cpus()
  Linux ppc64le

  
  Got multiple instances of panics, on artful:

  [   11.772333] ERROR: (device dm-3): dtSearch [jfs]: stack overrun!
  [   11.772333] 
  [   11.772384] bn = 0, index = 0
  [   11.772408] bn = 4307af, index = 0
  [   11.772432] bn = 0, index = 0
  [   11.772456] bn = 4307af, index = 0
  [   11.772493] bn = 0, index = 0
  [   11.772537] bn = 4307af, index = 0
  [   11.772573] bn = 0, index = 0
  [   11.772599] bn = c0077b994800, index = 0
  /sbin/init: error while loading shared libraries: liblz4.so.1: cannot open 
shared object file: Input/output error
  [   11.772964] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x7f00
  [   11.772964] 
  [   11.773043] CPU: 2 PID: 1 Comm: init Not tainted 4.11.0-13-generic 
#19-Ubuntu
  [   11.773102] Call Trace:
  [   11.773167] [c0077e10bc30] [c0b831bc] dump_stack+0xb0/0xf0 
(unreliable)
  [   11.773243] [c0077e10bc70] [c0b7fbc8] panic+0x144/0x318
  [   11.773311] [c0077e10bd00] [c00ea5b8] do_exit+0xc98/0xca0
  [   11.773373] [c0077e10bdd0] [c00ea690] do_group_exit+0x60/0x100
  [   11.773424] [c0077e10be10] [c00ea754] SyS_exit_group+0x24/0x30
  [   11.773470] [c0077e10be30] [c000b184] system_call+0x38/0xe0
  [   11.775434] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x7f00
  [   11.775434] 

  And also:

  [   12.338435] Unable to handle kernel paging request for data at address 
0x
  [   12.338754] Faulting instruction address: 0xd43be02c
  [   12.338951] Oops: Kernel access of bad area, sig: 11 [#1]
  [   12.338998] SMP NR_CPUS=2048 
  [   12.338999] NUMA 
  [   12.339053] pSeries
  [   12.339166] Modules linked in: ip_tables x_tables autofs4 jfs 
dm_service_time ibmveth ibmvscsi crc32c_vpmsum scsi_dh_emc scsi_dh_rdac 
scsi_dh_alua dm_multipath
  [   12.339305] CPU: 2 PID: 2135 Comm: tty Not tainted 4.11.0-13-generic 
#19-Ubuntu
  [   12.339441] task: c5562c00 task.stack: c6f78000
  [   12.339512] NIP: d43be02c LR: d43bdfbc CTR: 
c01458f0
  [   12.339614] REGS: c6f7b4b0 TRAP: 0300   Not tainted  
(4.11.0-13-generic)
  [   12.339707] MSR: 8280b033 
  [   12.339714]   CR: 44008244  XER: 
  [   12.339822] CFAR: 3fff9aa23f14 DAR:  DSISR: 4000 
SOFTE: 1 
  [   12.339822] GPR00: d43bdfbc c6f7b730 d43d8c90 
c00778e765f8 
  [   12.339822] GPR04: d43cf770 d43d2b58 05f1 
 
  [   12.339822] GPR08:  0038102d 0012 
d43ca6e0 
  [   12.339822] GPR12: c01458f0 cfb81200  
 
  [   12.339822] GPR16: c0077b8c81d8 c0077b8c80c8 c00778e91200 
c0077b8c8300 
  [   12.339822] GPR20: c6f7ba30 c00778e911fe c00778c38800 
c6f7b950 
  [   12.339822] GPR24: 0012 0012  
d43d2b38 
  [   12.339822] GPR28:

[Kernel-packages] [Bug 1711009] Re: jfs filesystem is crashy, multiple panic and I/O errors

2017-08-17 Thread Seth Forshee

Note too that we now have a 4.12 kernel in artful-release, so you might
give that a spin.

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

Title:
  jfs filesystem is crashy, multiple panic and I/O errors

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

Bug description:
  Loading initial ramdisk ...
  OF stdout device is: /vdevice/vty@7100
  Preparing to boot Linux version 4.11.0-13-generic (buildd@bos01-ppc64el-022) 
(gcc version 6.4.0 20170724 (Ubuntu 6.4.0-2ubuntu1) ) #19-Ubuntu SMP Thu Aug 3 
15:11:49 UTC 2017 (Ubuntu 4.11.0-13.19-generic 4.11.12)
  Detected machine type: 0101
  command line: BOOT_IMAGE=/boot/vmlinux-4.11.0-13-generic 
root=UUID=8c6162e8-9bb1-4171-a901-30e001222a14 ro splash quiet
  Max number of cores passed to firmware: 2048 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0762
alloc_top: 3000
alloc_top_hi : 00078000
rmo_top  : 3000
ram_top  : 00078000
  instantiating rtas at 0x2fff... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x0763 -> 0x076309e6
  Device tree struct  0x0764 -> 0x0765
  Quiescing Open Firmware ...
  Booting Linux via __start() @ 0x0200 ...
   -> smp_release_cpus()
  spinning_secondaries = 7
   <- smp_release_cpus()
  Linux ppc64le

  
  Got multiple instances of panics, on artful:

  [   11.772333] ERROR: (device dm-3): dtSearch [jfs]: stack overrun!
  [   11.772333] 
  [   11.772384] bn = 0, index = 0
  [   11.772408] bn = 4307af, index = 0
  [   11.772432] bn = 0, index = 0
  [   11.772456] bn = 4307af, index = 0
  [   11.772493] bn = 0, index = 0
  [   11.772537] bn = 4307af, index = 0
  [   11.772573] bn = 0, index = 0
  [   11.772599] bn = c0077b994800, index = 0
  /sbin/init: error while loading shared libraries: liblz4.so.1: cannot open 
shared object file: Input/output error
  [   11.772964] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x7f00
  [   11.772964] 
  [   11.773043] CPU: 2 PID: 1 Comm: init Not tainted 4.11.0-13-generic 
#19-Ubuntu
  [   11.773102] Call Trace:
  [   11.773167] [c0077e10bc30] [c0b831bc] dump_stack+0xb0/0xf0 
(unreliable)
  [   11.773243] [c0077e10bc70] [c0b7fbc8] panic+0x144/0x318
  [   11.773311] [c0077e10bd00] [c00ea5b8] do_exit+0xc98/0xca0
  [   11.773373] [c0077e10bdd0] [c00ea690] do_group_exit+0x60/0x100
  [   11.773424] [c0077e10be10] [c00ea754] SyS_exit_group+0x24/0x30
  [   11.773470] [c0077e10be30] [c000b184] system_call+0x38/0xe0
  [   11.775434] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x7f00
  [   11.775434] 

  And also:

  [   12.338435] Unable to handle kernel paging request for data at address 
0x
  [   12.338754] Faulting instruction address: 0xd43be02c
  [   12.338951] Oops: Kernel access of bad area, sig: 11 [#1]
  [   12.338998] SMP NR_CPUS=2048 
  [   12.338999] NUMA 
  [   12.339053] pSeries
  [   12.339166] Modules linked in: ip_tables x_tables autofs4 jfs 
dm_service_time ibmveth ibmvscsi crc32c_vpmsum scsi_dh_emc scsi_dh_rdac 
scsi_dh_alua dm_multipath
  [   12.339305] CPU: 2 PID: 2135 Comm: tty Not tainted 4.11.0-13-generic 
#19-Ubuntu
  [   12.339441] task: c5562c00 task.stack: c6f78000
  [   12.339512] NIP: d43be02c LR: d43bdfbc CTR: 
c01458f0
  [   12.339614] REGS: c6f7b4b0 TRAP: 0300   Not tainted  
(4.11.0-13-generic)
  [   12.339707] MSR: 8280b033 
  [   12.339714]   CR: 44008244  XER: 
  [   12.339822] CFAR: 3fff9aa23f14 DAR:  DSISR: 4000 
SOFTE: 1 
  [   12.339822] GPR00: d43bdfbc c6f7b730 d43d8c90 
c00778e765f8 
  [   12.339822] GPR04: d43cf770 d43d2b58 05f1 
 
  [   12.339822] GPR08:  0038102d 0012 
d43ca6e0 
  [   12.339822] GPR12: c01458f0 cfb81200  
 
  [   12.339822] GPR16: c0077b8c81d8 c0077b8c80c8 c00778e91200 
c0077b8c8300 
  [   12.339822] GPR20: c6f7ba30 c00778e911fe c00778c38800 
c6f7b950 
  [   12.339822] GPR24: 0012 0012  
d43d2b38 
  [   12.339822] GPR28: 1000 f1ddf440 c0076b096480 
c00778e765b8 
  [   12.340436] NIP [d43be02c] __get_metapage+0x204/0x6b0 [jfs]
  [   12.340541] LR [d43bdfbc]

[Kernel-packages] [Bug 1388786] Re: TCP stale transfer with erroneous SACK information

2017-08-17 Thread Guru Evi

This can be fixed by turning off TCP sequence reordering on the Cisco
appliance. Please note this also affects your Mac, BSD and Windows
machines. You can turn off SACK on your host if you don't care about
performance.

This feature was enabled by Cisco to protect Windows 95 hosts from TCP
sequence prediction attacks (yeah, don't fix the problem, just break the
network). However Cisco doesn't translate the SACK ranges it has
modified the sequences for so your host gets back the 'wrong' range in
the SACK response and simply ignores it because it doesn't match
anything it sent.

https://supportforums.cisco.com/document/48551/single-tcp-flow-
performance-firewall-services-module-fwsm

** Changed in: linux (Ubuntu)
   Status: In Progress => 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/1388786

Title:
  TCP stale transfer with erroneous SACK information

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Cisco PIX/FWSM changes TCP sequence numbers but doesn't change numbers
  in SACK TCP options.

  When this erroneous information comes to Linux server there is some
  corruption in TCP stack in some circunstances with CUBIC TCP
  congestion algorithm and transfer stales.

  Problem can be reproduced in Ubuntu Server 14.04 when a Cisco FWSM is
  changing sequence numbers (default configuration) and a big file
  (30MB, for example) is being transfered.

  Can be solved deactivating SACK:
  sysctl -w net.ipv4.tcp_sack=0

  We have solved it also with this configuration:
  sysctl -w net.ipv4.tcp_congestion_control=reno
  sysctl -w net.ipv4.tcp_frto=1
  sysctl -w net.ipv4.tcp_early_retrans=1

  We can also fix  it by changing firewall configuration.

  Find attached a wireshark capture where you can see at 16613 frame how
  client requests segment 853521869 and server (158.42.250.128) resends
  again a previous segment for 87 seconds until it stops transfer.

  Thanks

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

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

[Kernel-packages] [Bug 1711298] Re: Artful: 4.12.0-11.12: Boot panic in vlv2_plat_configure_clock+0x3b/0xa0

2017-08-17 Thread Seth Forshee

This is a staging driver that can only be built into the kernel, and
it's unconditionally registering a platform device for physical hw that
may not be present. That is a bad behavior, so I've disabled this option
until the driver is in better shape.

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

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

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

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

Title:
  Artful: 4.12.0-11.12: Boot panic in
  vlv2_plat_configure_clock+0x3b/0xa0

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Environment: Xen PV guest (64bit)

  The 4.11.0-10 kernel did still boot. But after upgrading to the
  4.12.0-11 kernel the following panic is observed:

  [1.262361] device-mapper: uevent: version 1.0.3
  [1.262465] device-mapper: ioctl: 4.35.0-ioctl (2016-06-23) initialised: 
dm-de...@redhat.com
  [1.262581] ledtrig-cpu: registered to indicate activity on CPUs
  [1.262696] BUG: unable to handle kernel paging request at c90040635060
  [1.262719] IP: vlv2_plat_configure_clock+0x3b/0xa0
  [1.262731] PGD ff805067 
  [1.262732] P4D ff805067 
  [1.262742] PUD fa93c067 
  [1.262752] PMD fa352067 
  [1.262761] PTE 0
  [1.262771] 
  [1.262790] Oops:  [#1] SMP
  [1.262801] Modules linked in:
  [1.262814] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.12.0-11-generic 
#12-Ubuntu
  [1.262825] task: 8800fa39aa80 task.stack: c90040628000
  [1.262833] RIP: e030:vlv2_plat_configure_clock+0x3b/0xa0
  [1.262840] RSP: e02b:c9004062bb58 EFLAGS: 00010246
  [1.262847] RAX:  RBX: c90040635060 RCX: 
02523fff
  [1.262855] RDX: 8800fa39aa80 RSI: 0002 RDI: 
81ff7340
  [1.262862] RBP: c9004062bb68 R08: 0067 R09: 
fff13000
  [1.262870] R10: 7ff0 R11: 3000 R12: 
0002
  [1.262877] R13:  R14:  R15: 

  [1.262890] FS:  () GS:8800fac8() 
knlGS:
  [1.262902] CS:  e033 DS:  ES:  CR0: 80050033
  [1.262908] CR2: c90040635060 CR3: 01e09000 CR4: 
0660
  [1.262917] Call Trace:
  [1.262926]  vlv2_plat_clk_probe+0x3f/0x70
  [1.262936]  platform_drv_probe+0x3b/0xa0
  [1.262944]  driver_probe_device+0x2ff/0x450
  [1.262952]  __device_attach_driver+0x83/0x100
  [1.262959]  ? __driver_attach+0xe0/0xe0
  [1.262967]  bus_for_each_drv+0x69/0xb0
  [1.262974]  __device_attach+0xdd/0x160
  [1.262982]  device_initial_probe+0x13/0x20
  [1.262989]  bus_probe_device+0x92/0xa0
  [1.262997]  device_add+0x451/0x690
  [1.263003]  platform_device_add+0x10d/0x270
  [1.263012]  ? set_debug_rodata+0x17/0x17
  [1.263019]  platform_device_register_full+0xfe/0x110
  [1.263029]  ? vlv2_plat_clk_init+0x19/0x19
  [1.263036]  vlv2_plat_clk_init+0x48/0x82
  [1.263044]  do_one_initcall+0x50/0x1a0
  [1.263052]  kernel_init_freeable+0x1bd/0x25f
  [1.263060]  ? rest_init+0x80/0x80
  [1.263067]  kernel_init+0xe/0x100
  [1.263074]  ret_from_fork+0x25/0x30
  [1.263081] Code: 47 83 fe 02 41 89 f4 77 67 48 8b 05 00 1b d9 00 48 85 c0 
74 48 c1 e7 02 48 63 ff 48 8d 1c 38 48 c7 c7 40 73 ff 81 e8 35 b5 16 00 <8b> 03 
83 e0 fc 44 09 e0 89 03 48 c7 c7 40 73 ff 81 e8 5f af 16 
  [1.263138] RIP: vlv2_plat_configure_clock+0x3b/0xa0 RSP: c9004062bb58
  [1.263145] CR2: c90040635060
  [1.263157] ---[ end trace e3dd450c61676c8a ]---
  [1.263177] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009

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

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

[Kernel-packages] [Bug 1709889] Patch with 3 patches plus debugging

--- Comment on attachment From dougm...@us.ibm.com 2017-08-17 08:44 
EDT---


Here is the patch from my latest run, containing the three proposed patches, 
getting delays > 40 minutes.

** Attachment added: "Patch with 3 patches plus debugging"
   
https://bugs.launchpad.net/bugs/1709889/+attachment/4934188/+files/fix-patch-3

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

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

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

Bug description:
  ---Problem Description---
  When running stress test, sometimes seeing IO hung in dmesg or seeing "Host 
adapter abort request" error.

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

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

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

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

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

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

  Tests are running again, will see what happens next.

  Update from JIRA:

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

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

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

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

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

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

  Some notes on reproduce this. I have been using the github release of
  HTX, built using the following steps:

  1. apt install make gcc g++ git libncurses5-dev libcxl-dev libdapl-dev 
(others may be required)
  2. git clone https://github.com/open-power/HTX
  3. cd HTX
  4. make
  5. make deb

  Then install the resulting "htxubuntu.deb" package.

  Note, HTX will not test disks that have a filesystem or OS installed,
  so there must be at least two disks made available to HTX by clearing
  any previous data.

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

--- Comment From dougm...@us.ibm.com 2017-08-17 08:42 EDT---
Those three patches, at least in the kernel I am running, actually make things 
worse. The characteristics have changed, in what appears to be a general 
slow-down of disk I/O (it took over 12 hours to hit the first set of sever 
stalls), but the delays - when they do occur - or much worse. I saw I/Os 
getting delayed for over 40 minutes.

I have double-checked that the patches are installed. But in spite of
having the patch for the delay length
(5be6b75610cefd1e21b98a218211922c2feb6e08) the behavior is back to what
I was seeing before that patch alone.

I'm attaching the combined diff of the changes I made to the kernel.
Note, the only difference between the "worse" run and the previous
"better" one was the addition of these two patches:

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

Which I can't explain, as I don't see how either of those should have
made this worse.

Maybe I need the actual source for your test kernel so I can add my
debug-monitoring code and run. With 40-minute delays the debug-
monitoring code is technically not needed, as HTX will complain. But if,
as I was seeing on the previous kernel, the delays are below 10 minutes
then HTX will never notice and there will be no obvious indication of
the more subtle issue.

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

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

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

Bug description:
  ---Problem Description---
  When running stress test, sometimes seeing IO hung in dmesg or seeing "Host 
adapter abort request" error.

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

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

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

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

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

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

  Tests are running again, will see what happens next.

  Update from JIRA:

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

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

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

  So,

[Kernel-packages] [Bug 1708499] Re: usb 3-1: 2:1: cannot get freq at ep 0x1

2017-08-17 Thread Cristian Aravena Romero

Hello Kai-Heng Feng,

The error message no longer appears.

Regards,
--
Cristian

** Attachment added: "dmesg_4.13.0-6.7-generic_4.13.0-rc5.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708499/+attachment/4934184/+files/dmesg_4.13.0-6.7-generic_4.13.0-rc5.txt

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

Title:
  usb 3-1: 2:1: cannot get freq at ep 0x1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  dmesg:
  [   74.344674] usb 3-1: 2:1: cannot get freq at ep 0x1
  [  138.403001] usb 3-1: 2:1: cannot get freq at ep 0x1
  [  247.864869] usb 3-1: 2:1: cannot get freq at ep 0x1

  Regards,
  --
  Cristian

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

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

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

[Kernel-packages] [Bug 1709282] Re: Plantronics Blackwire C520-M - Cannot get freq at ep 0x1, 0x81

Found a fix for vmware, https://communities.vmware.com/message/2688967 , but 
it's still unstable, complains it cannot allocate memory.
Rebooting in the previous kernel for the moment.
Thank you for now, Kai!

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

Title:
  Plantronics Blackwire C520-M - Cannot get freq at ep 0x1, 0x81

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Very similar to this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622763

  == the Problem ==
  Listening to sound on a vmware machine, hosted by Ubuntu, the devices 
freezes, and cannot listen to sound anymore, i have to connect/disconnect the 
device. 
  After i disconnect i get the logs:
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.344893] usb 1-1: 1:1: cannot get 
freq at ep 0x81
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.347094] usb 1-1: 2:1: cannot get 
freq at ep 0x1
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.358786] usb 1-1: Warning! 
Unlikely big volume range (=8192), cval->res is probably wrong.
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.358787] usb 1-1: [11] FU 
[Sidetone Playback Volume] ch = 1, val = 0/8192/1
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.641980] input: Plantronics 
Plantronics C520-M as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.3/0003:047F:C036.000F/input/input32
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.702298] plantronics 
0003:047F:C036.000F: input,hiddev0,hidraw2: USB HID v1.11 Device [Plantronics 
Plantronics C520-M] on usb-:00:14.0-1/input3
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.747708] usb 1-1: 2:1: cannot get 
freq at ep 0x1
  Aug  8 13:52:16 tim-lap-143 kernel: [112289.406154] usb 1-1: reset full-speed 
USB device number 19 using xhci_hcd
  Aug  8 13:52:16 tim-lap-143 kernel: [112289.906146] usb 1-1: reset full-speed 
USB device number 19 using xhci_hcd

  = The solution ==

  It is simple, add this USB ID to the
  sound/usb/quirks.c:snd_usb_get_sample_rate_quirk function.

  
  version signature: Ubuntu 4.10.0-28.32-generic 4.10.17

  Thanks!
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   mihai.cin...@3pillar.corp   2208 F...m pulseaudio
   /dev/snd/controlC0:  mihai.cin...@3pillar.corp   2208 F pulseaudio
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=d363a75c-d8a4-467d-a576-a46b3c317861
  InstallationDate: Installed on 2017-06-22 (47 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Precision 3510
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash i915.enable_guc_loading=1 
i915.enable_guc_submission=1 intel_pstate=skylake_hwp i915.enable_psr=1 
i915.disable_power_well=0 i915.enable_rc6=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-28-generic N/A
   linux-backports-modules-4.10.0-28-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-28-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-07-21 (18 days ago)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 05/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.4
  dmi.board.name: 00D283
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.4:bd05/12/2017:svnDellInc.:pnPrecision3510:pvr:rvnDellInc.:rn00D283:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 3510
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1711056] Re: Backport more recent Broadcom bnxt_en driver

2017-08-17 Thread Stefan Bader

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

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

Title:
  Backport more recent Broadcom bnxt_en driver

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

Bug description:
  We need to support newer Broadcom NetXtreme NICs than what the current
  bnxt_en driver can handle.

  The plan is to provide a separate driver module called bnxt_en_bpo
  which is a backported driver from Broadcom. This driver will be
  modified to only support the new NICs that the current kernel driver
  does not support.

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

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

[Kernel-packages] [Bug 1709282] Re: Plantronics Blackwire C520-M - Cannot get freq at ep 0x1, 0x81

Booted, but can't get to compile vmnet for VmWare on this kernel:( 
Can I apply the patch on 4.10 ? i can recompile it on my 17.04.


 from /tmp/modconfig-PuDRpn/vmnet-only/bridge.c:25:
./arch/x86/include/asm/atomic.h:89:29: note: expected ‘atomic_t * {aka struct 
 *}’ but argument is of type ‘refcount_t * {aka struct 
refcount_struct *}’
 static __always_inline void atomic_inc(atomic_t *v)
 ^~
cc1: some warnings being treated as errors
scripts/Makefile.build:302: recipe for target 
'/tmp/modconfig-PuDRpn/vmnet-only/bridge.o' failed
make[2]: *** [/tmp/modconfig-PuDRpn/vmnet-only/bridge.o] Error 1
Makefile:1545: recipe for target '_module_/tmp/modconfig-PuDRpn/vmnet-only' 
failed
make[1]: *** [_module_/tmp/modconfig-PuDRpn/vmnet-only] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-6-generic'
Makefile:120: recipe for target 'vmnet.ko' failed
make: *** [vmnet.ko] Error 2
make: Leaving directory '/tmp/modconfig-PuDRpn/vmnet-only'

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

Title:
  Plantronics Blackwire C520-M - Cannot get freq at ep 0x1, 0x81

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Very similar to this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622763

  == the Problem ==
  Listening to sound on a vmware machine, hosted by Ubuntu, the devices 
freezes, and cannot listen to sound anymore, i have to connect/disconnect the 
device. 
  After i disconnect i get the logs:
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.344893] usb 1-1: 1:1: cannot get 
freq at ep 0x81
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.347094] usb 1-1: 2:1: cannot get 
freq at ep 0x1
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.358786] usb 1-1: Warning! 
Unlikely big volume range (=8192), cval->res is probably wrong.
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.358787] usb 1-1: [11] FU 
[Sidetone Playback Volume] ch = 1, val = 0/8192/1
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.641980] input: Plantronics 
Plantronics C520-M as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.3/0003:047F:C036.000F/input/input32
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.702298] plantronics 
0003:047F:C036.000F: input,hiddev0,hidraw2: USB HID v1.11 Device [Plantronics 
Plantronics C520-M] on usb-:00:14.0-1/input3
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.747708] usb 1-1: 2:1: cannot get 
freq at ep 0x1
  Aug  8 13:52:16 tim-lap-143 kernel: [112289.406154] usb 1-1: reset full-speed 
USB device number 19 using xhci_hcd
  Aug  8 13:52:16 tim-lap-143 kernel: [112289.906146] usb 1-1: reset full-speed 
USB device number 19 using xhci_hcd

  = The solution ==

  It is simple, add this USB ID to the
  sound/usb/quirks.c:snd_usb_get_sample_rate_quirk function.

  
  version signature: Ubuntu 4.10.0-28.32-generic 4.10.17

  Thanks!
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   mihai.cin...@3pillar.corp   2208 F...m pulseaudio
   /dev/snd/controlC0:  mihai.cin...@3pillar.corp   2208 F pulseaudio
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=d363a75c-d8a4-467d-a576-a46b3c317861
  InstallationDate: Installed on 2017-06-22 (47 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Precision 3510
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash i915.enable_guc_loading=1 
i915.enable_guc_submission=1 intel_pstate=skylake_hwp i915.enable_psr=1 
i915.disable_power_well=0 i915.enable_rc6=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-28-generic N/A
   linux-backports-modules-4.10.0-28-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-28-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-07-21 (18 days ago)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 05/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.4
  dmi.board.name: 00D283
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.4:bd05/12/2017:svnDellInc.:pnPrecision3510:pvr:rvnDellInc.:rn00D283:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 3510
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing

[Kernel-packages] [Bug 1709282] Re: Plantronics Blackwire C520-M - Cannot get freq at ep 0x1, 0x81

Loading it now & rebooting,
Thank you Kai!

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

Title:
  Plantronics Blackwire C520-M - Cannot get freq at ep 0x1, 0x81

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Very similar to this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622763

  == the Problem ==
  Listening to sound on a vmware machine, hosted by Ubuntu, the devices 
freezes, and cannot listen to sound anymore, i have to connect/disconnect the 
device. 
  After i disconnect i get the logs:
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.344893] usb 1-1: 1:1: cannot get 
freq at ep 0x81
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.347094] usb 1-1: 2:1: cannot get 
freq at ep 0x1
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.358786] usb 1-1: Warning! 
Unlikely big volume range (=8192), cval->res is probably wrong.
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.358787] usb 1-1: [11] FU 
[Sidetone Playback Volume] ch = 1, val = 0/8192/1
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.641980] input: Plantronics 
Plantronics C520-M as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.3/0003:047F:C036.000F/input/input32
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.702298] plantronics 
0003:047F:C036.000F: input,hiddev0,hidraw2: USB HID v1.11 Device [Plantronics 
Plantronics C520-M] on usb-:00:14.0-1/input3
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.747708] usb 1-1: 2:1: cannot get 
freq at ep 0x1
  Aug  8 13:52:16 tim-lap-143 kernel: [112289.406154] usb 1-1: reset full-speed 
USB device number 19 using xhci_hcd
  Aug  8 13:52:16 tim-lap-143 kernel: [112289.906146] usb 1-1: reset full-speed 
USB device number 19 using xhci_hcd

  = The solution ==

  It is simple, add this USB ID to the
  sound/usb/quirks.c:snd_usb_get_sample_rate_quirk function.

  
  version signature: Ubuntu 4.10.0-28.32-generic 4.10.17

  Thanks!
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   mihai.cin...@3pillar.corp   2208 F...m pulseaudio
   /dev/snd/controlC0:  mihai.cin...@3pillar.corp   2208 F pulseaudio
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=d363a75c-d8a4-467d-a576-a46b3c317861
  InstallationDate: Installed on 2017-06-22 (47 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Precision 3510
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash i915.enable_guc_loading=1 
i915.enable_guc_submission=1 intel_pstate=skylake_hwp i915.enable_psr=1 
i915.disable_power_well=0 i915.enable_rc6=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-28-generic N/A
   linux-backports-modules-4.10.0-28-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-28-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-07-21 (18 days ago)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 05/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.4
  dmi.board.name: 00D283
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.4:bd05/12/2017:svnDellInc.:pnPrecision3510:pvr:rvnDellInc.:rn00D283:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 3510
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1711299] Re: ubuntu_bpf test failed to build on s390x system

2017-08-17 Thread Po-Hsu Lin

Some on-going discussion found upstream:

http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1459347.html
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1468498.html
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1468604.html

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

Title:
  ubuntu_bpf test failed to build on s390x system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With the Zesty source tree:

  $ make
  gcc -Wall -O2 -I../../../../usr/includetest_verifier.c   -o test_verifier
  In file included from test_verifier.c:23:0:
  /usr/include/linux/bpf_perf_event.h:14:17: error: field 'regs' has incomplete 
type
struct pt_regs regs;
   ^~~~
  : recipe for target 'test_verifier' failed
  make: *** [test_verifier] Error 1

  This issue can be reproduced on Artful tree and Linus' tree (commit
  ac9a40905) as well.

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

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

[Kernel-packages] [Bug 1688625] Re: Linux does not recognize the Hantick touchpad as a touchpad and does not enable all the functions

2017-08-17 Thread slimbook

Do, and the pointer is crazy.
:(

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

Title:
  Linux does not recognize the Hantick touchpad as a touchpad and does
  not enable all the functions

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  We have laptops with touchpad Hantick, that on Miscrosft Windows work with 
Elan driver.

  Linux does not recognize the Hantick touchpad as a touchpad and does
  not enable all the functions of evdev or libinput.

  Thanks
  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-77-generic 4.4.0-77.98
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  slimbook   1720 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May  5 20:01:33 2017
  HibernationDevice: RESUME=UUID=eef047d2-92ea-4166-a300-7a4de6af1448
  InstallationDate: Installed on 2017-05-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 090c:037c Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) 300k Pixel Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   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: SLIMBOOK KATANA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic.efi.signed 
root=UUID=00a6febb-4980-4147-a2e8-29930aed3d30 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-77-generic N/A
   linux-backports-modules-4.4.0-77-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 16L
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: KATANA
  dmi.board.vendor: SLIMBOOK
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SLIMBOOK
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr16L:bd07/25/2016:svnSLIMBOOK:pnKATANA:pvrTBDbyOEM:rvnSLIMBOOK:rnKATANA:rvrType2-BoardVersion:cvnSLIMBOOK:ct10:cvrChassisVersion:
  dmi.product.name: KATANA
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: SLIMBOOK

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

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

[Kernel-packages] [Bug 1708499] Re: usb 3-1: 2:1: cannot get freq at ep 0x1

Try kernel here:
http://people.canonical.com/~khfeng/plantronics/

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

Title:
  usb 3-1: 2:1: cannot get freq at ep 0x1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  dmesg:
  [   74.344674] usb 3-1: 2:1: cannot get freq at ep 0x1
  [  138.403001] usb 3-1: 2:1: cannot get freq at ep 0x1
  [  247.864869] usb 3-1: 2:1: cannot get freq at ep 0x1

  Regards,
  --
  Cristian

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

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

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

[Kernel-packages] [Bug 1709282] Re: Plantronics Blackwire C520-M - Cannot get freq at ep 0x1, 0x81

Try kernel here:
http://people.canonical.com/~khfeng/plantronics/

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

Title:
  Plantronics Blackwire C520-M - Cannot get freq at ep 0x1, 0x81

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Very similar to this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622763

  == the Problem ==
  Listening to sound on a vmware machine, hosted by Ubuntu, the devices 
freezes, and cannot listen to sound anymore, i have to connect/disconnect the 
device. 
  After i disconnect i get the logs:
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.344893] usb 1-1: 1:1: cannot get 
freq at ep 0x81
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.347094] usb 1-1: 2:1: cannot get 
freq at ep 0x1
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.358786] usb 1-1: Warning! 
Unlikely big volume range (=8192), cval->res is probably wrong.
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.358787] usb 1-1: [11] FU 
[Sidetone Playback Volume] ch = 1, val = 0/8192/1
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.641980] input: Plantronics 
Plantronics C520-M as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.3/0003:047F:C036.000F/input/input32
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.702298] plantronics 
0003:047F:C036.000F: input,hiddev0,hidraw2: USB HID v1.11 Device [Plantronics 
Plantronics C520-M] on usb-:00:14.0-1/input3
  Aug  8 13:52:05 tim-lap-143 kernel: [112278.747708] usb 1-1: 2:1: cannot get 
freq at ep 0x1
  Aug  8 13:52:16 tim-lap-143 kernel: [112289.406154] usb 1-1: reset full-speed 
USB device number 19 using xhci_hcd
  Aug  8 13:52:16 tim-lap-143 kernel: [112289.906146] usb 1-1: reset full-speed 
USB device number 19 using xhci_hcd

  = The solution ==

  It is simple, add this USB ID to the
  sound/usb/quirks.c:snd_usb_get_sample_rate_quirk function.

  
  version signature: Ubuntu 4.10.0-28.32-generic 4.10.17

  Thanks!
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   mihai.cin...@3pillar.corp   2208 F...m pulseaudio
   /dev/snd/controlC0:  mihai.cin...@3pillar.corp   2208 F pulseaudio
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=d363a75c-d8a4-467d-a576-a46b3c317861
  InstallationDate: Installed on 2017-06-22 (47 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Precision 3510
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash i915.enable_guc_loading=1 
i915.enable_guc_submission=1 intel_pstate=skylake_hwp i915.enable_psr=1 
i915.disable_power_well=0 i915.enable_rc6=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-28-generic N/A
   linux-backports-modules-4.10.0-28-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-28-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-07-21 (18 days ago)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 05/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.4
  dmi.board.name: 00D283
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.4:bd05/12/2017:svnDellInc.:pnPrecision3510:pvr:rvnDellInc.:rn00D283:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 3510
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1711096] Re: dma-buf: performance issue when looking up the fence status

2017-08-17 Thread Alvin Huan

** Description changed:

  SRU Request:
  
  [Impact]
  When a timeout of zero is specified, the caller is only interested in
  the fence status.
  
  In the current implementation, dma_fence_default_wait will always call
  schedule_timeout() at least once for an unsignaled fence. This adds a
  significant overhead to a fence status query.
  
  Avoid this overhead by returning early if a zero timeout is specified.
  
  [Test Case]
  1) Install the new kernel
  
- 2)
+ 2) Download amdgpu-pro-17.30-465504.tar.xz from http://support.amd.com
+ /en-us/kb-articles/Pages/AMDGPU-PRO-Driver-for-Linux-Release-Notes.aspx,
+ and follow the install guide to install the driver on Ubuntu 16.04.3
+ 
+ 3) Install Unigine Heaven to get performance score
+ 
+ 4) Rmeove DKMS, remove this patch
+ 
http://git.amd.com:8080/gitweb?p=brahma/ec/linux.git;a=commit;h=8586edda6677b90f3971919f3c6babbbec4b5b8c
+ from DKMS source code, and install DKMS
+ 
+ 5) re-run the benchmark, and check if there's any obvious performance
+ drop.
  
  [Regression Potential]
  Low, the patch is very small, and it is already available upstream.
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=03c0c5f6641533f5fc14bf4e76d2304197402552

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

Title:
  dma-buf: performance issue when looking up the fence status

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

Bug description:
  SRU Request:

  [Impact]
  When a timeout of zero is specified, the caller is only interested in
  the fence status.

  In the current implementation, dma_fence_default_wait will always call
  schedule_timeout() at least once for an unsignaled fence. This adds a
  significant overhead to a fence status query.

  Avoid this overhead by returning early if a zero timeout is specified.

  [Test Case]
  1) Install the new kernel

  2) Download amdgpu-pro-17.30-465504.tar.xz from http://support.amd.com
  /en-us/kb-articles/Pages/AMDGPU-PRO-Driver-for-Linux-Release-
  Notes.aspx, and follow the install guide to install the driver on
  Ubuntu 16.04.3

  3) Install Unigine Heaven to get performance score

  4) Rmeove DKMS, remove this patch
  
http://git.amd.com:8080/gitweb?p=brahma/ec/linux.git;a=commit;h=8586edda6677b90f3971919f3c6babbbec4b5b8c
  from DKMS source code, and install DKMS

  5) re-run the benchmark, and check if there's any obvious performance
  drop.

  [Regression Potential]
  Low, the patch is very small, and it is already available upstream.

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=03c0c5f6641533f5fc14bf4e76d2304197402552

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

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

[Kernel-packages] [Bug 1688625] Re: Linux does not recognize the Hantick touchpad as a touchpad and does not enable all the functions

Try this:
$ sudo sh -c 'echo -n "elantech" > /sys/bus/serio/devices/serio2/protocol

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

Title:
  Linux does not recognize the Hantick touchpad as a touchpad and does
  not enable all the functions

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  We have laptops with touchpad Hantick, that on Miscrosft Windows work with 
Elan driver.

  Linux does not recognize the Hantick touchpad as a touchpad and does
  not enable all the functions of evdev or libinput.

  Thanks
  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-77-generic 4.4.0-77.98
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  slimbook   1720 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May  5 20:01:33 2017
  HibernationDevice: RESUME=UUID=eef047d2-92ea-4166-a300-7a4de6af1448
  InstallationDate: Installed on 2017-05-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 090c:037c Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) 300k Pixel Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   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: SLIMBOOK KATANA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic.efi.signed 
root=UUID=00a6febb-4980-4147-a2e8-29930aed3d30 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-77-generic N/A
   linux-backports-modules-4.4.0-77-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 16L
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: KATANA
  dmi.board.vendor: SLIMBOOK
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SLIMBOOK
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr16L:bd07/25/2016:svnSLIMBOOK:pnKATANA:pvrTBDbyOEM:rvnSLIMBOOK:rnKATANA:rvrType2-BoardVersion:cvnSLIMBOOK:ct10:cvrChassisVersion:
  dmi.product.name: KATANA
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: SLIMBOOK

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

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

[Kernel-packages] [Bug 1707887] Re: Failed to build libhugetlbfs-2.20 from source on 4.4 / 3.13 Trusty ARM64

2017-08-17 Thread Po-Hsu Lin

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

Title:
  Failed to build libhugetlbfs-2.20 from source on 4.4 / 3.13 Trusty
  ARM64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It will fail to build libhugetlbfs verison 2.20 for SRU regression-
  test on 3.13 ARM64

  It's ok on 4.10 / 4.4 ARM64, but not 4.4.0-88.111~14.04.1 and
  3.13.0-126.175 ARM64

  Looks like it's failing with:
  LD64 (hugelink_rw test) obj64/linkhuge_rw
  /usr/bin/ld: final link failed: File truncated

  This is not a regression. As this issue has been seen before.

  Complete make log:
  $ make
 VERSION
  version string: 2.20
 CC64 obj64/elflink.o
 AS64 obj64/sys-aarch64elf.o
 CC64 obj64/hugeutils.o
 CC64 obj64/version.o
 CC64 obj64/init.o
 CC64 obj64/morecore.o
 CC64 obj64/debug.o
 CC64 obj64/alloc.o
 CC64 obj64/shm.o
 CC64 obj64/kernel-features.o
 LD64 (shared) obj64/libhugetlbfs.so
 AR64 obj64/libhugetlbfs.a
 CC64 obj64/init_privutils.o
 LD64 (shared) obj64/libhugetlbfs_privutils.so
 CCHOST obj/init_privutils.o
 CCHOST obj/debug.o
 CCHOST obj/hugeutils.o
 CCHOST obj/kernel-features.o
 ARHOST obj/libhugetlbfs_privutils.a
 CC64 obj64/gethugepagesize.o
 CC64 obj64/testutils.o
 CC64 obj64/libtestutils.o
 LD64 (lib test) obj64/gethugepagesize
 CC64 obj64/test_root.o
 LD64 (lib test) obj64/test_root
 CC64 obj64/find_path.o
 LD64 (lib test) obj64/find_path
 CC64 obj64/unlinked_fd.o
 LD64 (lib test) obj64/unlinked_fd
 CC64 obj64/misalign.o
 LD64 (lib test) obj64/misalign
 CC64 obj64/readback.o
 LD64 (lib test) obj64/readback
 CC64 obj64/truncate.o
 LD64 (lib test) obj64/truncate
 CC64 obj64/shared.o
 LD64 (lib test) obj64/shared
 CC64 obj64/private.o
 LD64 (lib test) obj64/private
 CC64 obj64/fork-cow.o
 LD64 (lib test) obj64/fork-cow
 CC64 obj64/empty_mounts.o
 LD64 (lib test) obj64/empty_mounts
 CC64 obj64/large_mounts.o
 LD64 (lib test) obj64/large_mounts
 CC64 obj64/meminfo_nohuge.o
 LD64 (lib test) obj64/meminfo_nohuge
 CC64 obj64/ptrace-write-hugepage.o
 LD64 (lib test) obj64/ptrace-write-hugepage
 CC64 obj64/icache-hygiene.o
  icache-hygiene.c: In function ‘test_once’:
  icache-hygiene.c:158:11: warning: ignoring return value of ‘ftruncate’, 
declared with attribute warn_unused_result [-Wunused-result]
ftruncate(fd, 0);
 ^
  icache-hygiene.c:162:12: warning: ignoring return value of ‘ftruncate’, 
declared with attribute warn_unused_result [-Wunused-result]
 ftruncate(fd, 0);
  ^
  icache-hygiene.c:171:11: warning: ignoring return value of ‘ftruncate’, 
declared with attribute warn_unused_result [-Wunused-result]
ftruncate(fd, hpage_size);
 ^
  icache-hygiene.c:177:11: warning: ignoring return value of ‘ftruncate’, 
declared with attribute warn_unused_result [-Wunused-result]
ftruncate(fd, 0);
 ^
 LD64 (lib test) obj64/icache-hygiene
 CC64 obj64/slbpacaflush.o
 LD64 (lib test) obj64/slbpacaflush
 CC64 obj64/chunk-overcommit.o
 LD64 (lib test) obj64/chunk-overcommit
 CC64 obj64/mprotect.o
 LD64 (lib test) obj64/mprotect
 CC64 obj64/alloc-instantiate-race.o
  alloc-instantiate-race.c: In function ‘thread_racer’:
  alloc-instantiate-race.c:114:6: warning: variable ‘rc’ set but not used 
[-Wunused-but-set-variable]
int rc;
^
 LD64 (lib test) obj64/alloc-instantiate-race
 CC64 obj64/mlock.o
 LD64 (lib test) obj64/mlock
 CC64 obj64/truncate_reserve_wraparound.o
 LD64 (lib test) obj64/truncate_reserve_wraparound
 CC64 obj64/truncate_sigbus_versus_oom.o
 LD64 (lib test) obj64/truncate_sigbus_versus_oom
 CC64 obj64/map_high_truncate_2.o
 LD64 (lib test) obj64/map_high_truncate_2
 CC64 obj64/truncate_above_4GB.o
 LD64 (lib test) obj64/truncate_above_4GB
 CC64 obj64/direct.o
 LD64 (lib test) obj64/direct
 CC64 obj64/misaligned_offset.o
 LD64 (lib test) obj64/misaligned_offset
 CC64 obj64/brk_near_huge.o
 LD64 (lib test) obj64/brk_near_huge
 CC64 obj64/task-size-overrun.o
 LD64 (lib test) obj64/task-size-overrun
 CC64 obj64/stack_grow_into_huge.o
 LD64 (lib test) obj64/stack_grow_into_huge
 CC64 obj64/counters.o
 LD64 (lib test) obj64/counters
 CC64 obj64/quota.o
 LD64 (lib test) obj64/quota

[Kernel-packages] [Bug 1711098] Re: AMD RV platforms with SNPS 3.1 USB controller stop responding (S3 issue)

2017-08-17 Thread Alvin Huan

** Description changed:

  SRU Request:
  
  [Impact]
  AMD RV platforms with SNPS 3.1 USB controllers will stop responding because 
of an RTL bug.
  
- This workaround fixes S3 on these platforms:
+ This workaround fixes S3 on RV platform with a USB keyboard
  
  [Test Case]
  1) Install the new kernel
  
- 2)
+ 2) Run pm-suspend
+ 
+ 3) Press any key to wake up the system
  
  [Regression Potential]
  Low, the patch is very small, and it is already available upstream.
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/usb/host
  /xhci-hub.c?h=v4.13-rc2=28a2369f7d72ece55089f33e7d7b9c1223673cc3

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

Title:
  AMD RV platforms with SNPS 3.1 USB controller stop responding (S3
  issue)

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

Bug description:
  SRU Request:

  [Impact]
  AMD RV platforms with SNPS 3.1 USB controllers will stop responding because 
of an RTL bug.

  This workaround fixes S3 on RV platform with a USB keyboard

  [Test Case]
  1) Install the new kernel

  2) Run pm-suspend

  3) Press any key to wake up the system

  [Regression Potential]
  Low, the patch is very small, and it is already available upstream.

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/usb/host
  /xhci-hub.c?h=v4.13-rc2=28a2369f7d72ece55089f33e7d7b9c1223673cc3

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

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

[Kernel-packages] [Bug 1711299] Re: ubuntu_bpf test failed to build on s390x system

2017-08-17 Thread Po-Hsu Lin

>From upstream commits, there are some commits that make it looks like
this test should be able to run on s390x:

bpf: fix selftest/bpf/test_pkt_md_access on s390x

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

Title:
  ubuntu_bpf test failed to build on s390x system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With the Zesty source tree:

  $ make
  gcc -Wall -O2 -I../../../../usr/includetest_verifier.c   -o test_verifier
  In file included from test_verifier.c:23:0:
  /usr/include/linux/bpf_perf_event.h:14:17: error: field 'regs' has incomplete 
type
struct pt_regs regs;
   ^~~~
  : recipe for target 'test_verifier' failed
  make: *** [test_verifier] Error 1

  This issue can be reproduced on Artful tree and Linus' tree (commit
  ac9a40905) as well.

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

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

[Kernel-packages] [Bug 1710548] Re: Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04? Logitech C920 Webcam/Zoneminder/Startech

Here you go:

http://people.canonical.com/~khfeng/linux-
image-4.13.0-rc5+_4.13.0-rc5+-2_amd64.deb

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

Title:
  Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04?
  Logitech C920 Webcam/Zoneminder/Startech

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In trying to build a zoneminder server, I think I stumbled on a kernel
  bug. It  seems to have snuck in sometime between 16.04 desktop
  promoted to server, and 17.04 server promoted to desktop.

  The suggestion is that the very popular Nec/Renasas 27xxx2 may need
  "quirk" in the kernel.

  Timeline:

  
  (Scene 1)

  Loaded 16.04 Ubuntu Desktop
  Promoted Desktop to Studio
  Promoted Desktop to Server
  Added Zoneminder
  Needed more cams, added Startech  PEXUSB3S44V NEC/Renesasa 27XXX2 based card 
for more USB channels.
  Everything worked quite well. Some errors in ZM but no DMESG as far as I 
recall. 

  (Scene 2)
  Wiped the drive. 
  Loaded 17.04 Server
  Now getting messages in DMESG complaining of thousands of errors:
  [96415.044917] handle_tx_event: 516 callbacks suppressed
  [96415.044924] xhci_hcd :0c:00.0: WARN Successful completion on short TX: 
needs XHCI_TRUST_TX_LENGTH quirk?

  
  Messages suggest "quirk" is the solution.
  a)Researched usb 3.0 "quirk'
  b)Noticed it's really a "thing" 
  c)Couldn't find recipe for patching kernel for NEC/Renases "quirk" fix. 

  (Scene 3)
  Anecdotes suggest Nec/Renasas firmware is to blame.
  a) Kernel indicates 2024 firmaware
  b) Startech website has 2026 firmware. 
  c) VERY IMPORTANT! WindowCentric GUI instructions do not translate between 
ASCII and HEX. So if your Startech is on channels 9, 10, 11, and 12 from 
perspective of Windows, you must translate into 09, 0A, 0B, and 0C when editing 
runfile for effective firmware update of all 4 controllers. Yes, for the 4 
channel controller, count them: 4. 
  d) Firmware updated. 

  (Scene 4) 
  Rebooted with new Startech/Nec/Renases 2026 firmware. 
  SAME OLD PLETHORA OF ERRORS

  (Scene 5)
  I give up. 

  It may well be worth noting that there are no errors from DMESG until some 
seconds after the first webcam is attached to the Startech.
   
  And I can't overemphasize the fact that I don't think I had any DMESG errors 
under Desktop 16.04 

  I think the file attached represents DMESG immediately before the
  errors start going nuts. My theory is that ZM does lazy polls on
  missing cams but once it gets 'hold if the cam and sucking data the
  quirk bug surfaces.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff  12776 F pulseaudio
   /dev/snd/controlC3:  jeff  12776 F pulseaudio
   /dev/snd/controlC2:  jeff  12776 F pulseaudio
   /dev/snd/controlC1:  jeff  12776 F pulseaudio
  Date: Sun Aug 13 16:48:41 2017
  MachineType: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 mgadrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=UUID=4f802241-4254-4d61-9231-d7e16de36a3d 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:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.2a
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.2a:bd08/31/2015:svnSupermicro:pnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:pvr0123456789:rvnSupermicro:rnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:rvr0123456789:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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

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

[Kernel-packages] [Bug 1686019] Re: Ubuntu 16.04.3: Qemu fails on P9

2017-08-17 Thread Kleber Sacilotto de Souza

Hi IBM,

Please note that as of now the fixes for this issue have been applied on
Artful (4.11 based) kernel only.

The latest submission to the kernel-team mailing-list of this patchset
(v4) still needs to reviewed and applied to the Zesty kernel tree (4.10
based) before they are available on zesty/linux and xenial/linux-hwe
kernels.

Thank you.

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

Title:
  Ubuntu 16.04.3: Qemu fails on P9

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

Bug description:
  Trying to start KVM on Ubuntu 16.04.3 with QEMU from dgibson 2.10
  tree[1], I see the following error when trying to boot a 17.04 image.

  8000 DISK : "QEMU QEMU HARDDISK2.5+"
  Populating /pci@8002000
  No NVRAM common partition, re-initializing...
  Scanning USB 
  Using default console: /vdevice/vty@7100
   ted RAM kernel at 40 (17995b0 bytes) C08FF
Welcome to Open Firmware

Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
This program and the accompanying materials are made available
under the terms of the BSD License available at
http://www.opensource.org/licenses/bsd-license.php

  Booting from memory...
  OF stdout device is: /vdevice/vty@7100
  Preparing to boot Linux version 4.10.0-19-generic (buildd@bos01-ppc64el-009) 
(gcc version 6.3.0 20170321 (Ubuntu 6.3.0-10ubuntu1) ) #21-Ubuntu SMP Thu Apr 6 
17:03:05 UTC 2017 (Ubuntu 4.10.0-19.21-generic 4.10.8)
  Detected machine type: 0101
  command line: debug initcall_debug udbg-immortal console=/dev/hvc0
  Max number of cores passed to firmware: 2048 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 01bb
alloc_top: 1000
alloc_top_hi : 8000
rmo_top  : 1000
ram_top  : 8000
  instantiating rtas at 0x0daf... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x041c -> 0x041c09fd
  Device tree struct  0x041d -> 0x041e
  Quiescing Open Firmware ...
  Booting Linux via __start() @ 0x0040 ...

  
  I tried to add some debug options as "debug initcall_debug udbg-immortal 
console=/dev/hvc0" but no luck. 

  [1] https://github.com/dgibson/qemu.git branch ppc-for-2.10
   
  ---uname output---
  4.10.0-19

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

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

[Kernel-packages] [Bug 1686019] Re: Ubuntu 16.04.3: Qemu fails on P9

2017-08-17 Thread Kleber Sacilotto de Souza

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

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

Title:
  Ubuntu 16.04.3: Qemu fails on P9

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

Bug description:
  Trying to start KVM on Ubuntu 16.04.3 with QEMU from dgibson 2.10
  tree[1], I see the following error when trying to boot a 17.04 image.

  8000 DISK : "QEMU QEMU HARDDISK2.5+"
  Populating /pci@8002000
  No NVRAM common partition, re-initializing...
  Scanning USB 
  Using default console: /vdevice/vty@7100
   ted RAM kernel at 40 (17995b0 bytes) C08FF
Welcome to Open Firmware

Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
This program and the accompanying materials are made available
under the terms of the BSD License available at
http://www.opensource.org/licenses/bsd-license.php

  Booting from memory...
  OF stdout device is: /vdevice/vty@7100
  Preparing to boot Linux version 4.10.0-19-generic (buildd@bos01-ppc64el-009) 
(gcc version 6.3.0 20170321 (Ubuntu 6.3.0-10ubuntu1) ) #21-Ubuntu SMP Thu Apr 6 
17:03:05 UTC 2017 (Ubuntu 4.10.0-19.21-generic 4.10.8)
  Detected machine type: 0101
  command line: debug initcall_debug udbg-immortal console=/dev/hvc0
  Max number of cores passed to firmware: 2048 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 01bb
alloc_top: 1000
alloc_top_hi : 8000
rmo_top  : 1000
ram_top  : 8000
  instantiating rtas at 0x0daf... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x041c -> 0x041c09fd
  Device tree struct  0x041d -> 0x041e
  Quiescing Open Firmware ...
  Booting Linux via __start() @ 0x0040 ...

  
  I tried to add some debug options as "debug initcall_debug udbg-immortal 
console=/dev/hvc0" but no luck. 

  [1] https://github.com/dgibson/qemu.git branch ppc-for-2.10
   
  ---uname output---
  4.10.0-19

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

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

[Kernel-packages] [Bug 1710517] Re: Enable EFI stub for raspi2 kernels

2017-08-17 Thread Adam Smith

->Confirmed.  The title says it all really.  I'm on xenial at the
moment.

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

Title:
  Enable EFI stub for raspi2 kernels

Status in linux package in Ubuntu:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  U-boot is now able to emulate UEFI and this is used by openSUSE to
  boot the raspberry pi [1].

  I would like to use this technique to load grub2.  However, according
  to [2] new versions of grub2 require a 32 bit kernel to be built with
  EFI stub enabled.

  I have successfully used this U-boot/grub2 combination to boot a
  generic aarch64 Ubuntu kernel on my pi3 [3].  It works well and would
  be a huge improvement if this could be brought to arm 32 bit.


  [1]
  https://www.suse.com/docrep/documents/a1f0ledpbe/UEFI%20on%20Top%20of
  %20U-Boot.pdf

  [2] https://wiki.linaro.org/LEG/Engineering/Kernel/GRUB

  [3] https://lists.ubuntu.com/archives/lubuntu-
  users/2017-August/011613.html

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

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

[Kernel-packages] [Bug 1706598] Re: Update bluez to 5.46 in artful

This bug was fixed in the package bluez - 5.46-0ubuntu1

---
bluez (5.46-0ubuntu1) artful; urgency=medium

  [ Konrad Zapałowicz ]
  * New upstream version (lp: #1706598)

  [ Daniel van Vugt ]
  * debian/control:
- update the vcs information

 -- Simon Fels   Wed, 19 Jul 2017 11:46:21
+0200

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

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

Title:
  Update bluez to 5.46 in artful

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  The new bluez version is being packaged for artful

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

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

[Kernel-packages] [Bug 1708875] Re: mute microphone button not working

2017-08-17 Thread Robert Orzanna

Please forget my previous comment. Found the solution to restoring the
file:

# Find the package that provides the file:
orschiro@x230:~$ dpkg -S /lib/udev/hwdb.d/60-keyboard.hwdb

# Reinstall package:
orschiro@x230:~$ sudo apt install --reinstall udev

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

Title:
  mute microphone button not working

Status in ubuntu-mate:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in mate-settings-daemon package in Ubuntu:
  Triaged

Bug description:
  I don't remember if that button ever worked in previous releases but
  on my X230 pressing this button doesn't mute the microphone.

  Anyone else with the same problem?

  Attached the button I am referring to.

  To the contrary, the button to mute the audio works.
  --- 
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  orschiro   1354 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=2f35eaaf-14d7-4156-9029-eb60bff76095
  InstallationDate: Installed on 2017-08-05 (10 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 
(20170725.1)
  MachineType: LENOVO 23352CG
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-11-generic 
root=/dev/mapper/fedora-root ro quiet splash acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  RelatedPackageVersions:
   linux-restricted-modules-4.12.0-11-generic N/A
   linux-backports-modules-4.12.0-11-generic  N/A
   linux-firmware 1.167
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8188eu
  Tags:  artful staging
  Uname: Linux 4.12.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA8WW (2.68 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23352CG
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA8WW(2.68):bd04/19/2017:svnLENOVO:pn23352CG:pvrThinkPadX230:rvnLENOVO:rn23352CG:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 23352CG
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1708875/+subscriptions

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

[Kernel-packages] [Bug 1708875] Re: mute microphone button not working

This should do:
$ sudo apt --reinstall install udev

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

Title:
  mute microphone button not working

Status in ubuntu-mate:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in mate-settings-daemon package in Ubuntu:
  Triaged

Bug description:
  I don't remember if that button ever worked in previous releases but
  on my X230 pressing this button doesn't mute the microphone.

  Anyone else with the same problem?

  Attached the button I am referring to.

  To the contrary, the button to mute the audio works.
  --- 
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  orschiro   1354 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=2f35eaaf-14d7-4156-9029-eb60bff76095
  InstallationDate: Installed on 2017-08-05 (10 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 
(20170725.1)
  MachineType: LENOVO 23352CG
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-11-generic 
root=/dev/mapper/fedora-root ro quiet splash acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  RelatedPackageVersions:
   linux-restricted-modules-4.12.0-11-generic N/A
   linux-backports-modules-4.12.0-11-generic  N/A
   linux-firmware 1.167
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8188eu
  Tags:  artful staging
  Uname: Linux 4.12.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA8WW (2.68 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23352CG
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA8WW(2.68):bd04/19/2017:svnLENOVO:pn23352CG:pvrThinkPadX230:rvnLENOVO:rn23352CG:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 23352CG
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1708875/+subscriptions

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

[Kernel-packages] [Bug 1708875] Re: mute microphone button not working

2017-08-17 Thread Martin Wimpress

** Changed in: mate-settings-daemon (Ubuntu)
   Status: New => Triaged

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

Title:
  mute microphone button not working

Status in ubuntu-mate:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in mate-settings-daemon package in Ubuntu:
  Triaged

Bug description:
  I don't remember if that button ever worked in previous releases but
  on my X230 pressing this button doesn't mute the microphone.

  Anyone else with the same problem?

  Attached the button I am referring to.

  To the contrary, the button to mute the audio works.
  --- 
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  orschiro   1354 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=2f35eaaf-14d7-4156-9029-eb60bff76095
  InstallationDate: Installed on 2017-08-05 (10 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 
(20170725.1)
  MachineType: LENOVO 23352CG
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-11-generic 
root=/dev/mapper/fedora-root ro quiet splash acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  RelatedPackageVersions:
   linux-restricted-modules-4.12.0-11-generic N/A
   linux-backports-modules-4.12.0-11-generic  N/A
   linux-firmware 1.167
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8188eu
  Tags:  artful staging
  Uname: Linux 4.12.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA8WW (2.68 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23352CG
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA8WW(2.68):bd04/19/2017:svnLENOVO:pn23352CG:pvrThinkPadX230:rvnLENOVO:rn23352CG:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 23352CG
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1708875/+subscriptions

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

[Kernel-packages] [Bug 1708875] Re: mute microphone button not working

2017-08-17 Thread Robert Orzanna

Thanks for your help on this, Kai!

How can I now restore my original file?

I forgot to create a backup.

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

Title:
  mute microphone button not working

Status in ubuntu-mate:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in mate-settings-daemon package in Ubuntu:
  Triaged

Bug description:
  I don't remember if that button ever worked in previous releases but
  on my X230 pressing this button doesn't mute the microphone.

  Anyone else with the same problem?

  Attached the button I am referring to.

  To the contrary, the button to mute the audio works.
  --- 
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  orschiro   1354 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=2f35eaaf-14d7-4156-9029-eb60bff76095
  InstallationDate: Installed on 2017-08-05 (10 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 
(20170725.1)
  MachineType: LENOVO 23352CG
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-11-generic 
root=/dev/mapper/fedora-root ro quiet splash acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  RelatedPackageVersions:
   linux-restricted-modules-4.12.0-11-generic N/A
   linux-backports-modules-4.12.0-11-generic  N/A
   linux-firmware 1.167
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8188eu
  Tags:  artful staging
  Uname: Linux 4.12.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA8WW (2.68 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23352CG
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA8WW(2.68):bd04/19/2017:svnLENOVO:pn23352CG:pvrThinkPadX230:rvnLENOVO:rn23352CG:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 23352CG
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1708875/+subscriptions

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

2017-08-17 Thread Trent Nelson

Will this be making its way to a release build?

-- 
You 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:
  Confirmed

Bug description:
  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 1684054] Re: [LTCTest][Opal][FW860.20] HMI recoverable errors failed to recover and system goes to dump state.