[Kernel-packages] [Bug 1730895] Re: aio-dio-invalidate-failure test failed with event res -22 on s390x

[Po-Hsu Lin]

** Description changed:

  This bug is for tracking purpose, this is not a regression for current
  cycle as this issue exists for a long time.
+ 
+ It can be reproduced on zVM, zKVM and Ubuntu on LPAR
  
  Steps:
  1. git clone --depth=1 https://github.com/autotest/autotest-client-tests.git
  2. make -C autotest-client-tests/aio_dio_bugs/src
  3. sudo ./autotest-client-tests/aio_dio_bugs/src/aio-dio-invalidate-failure 
poo
  
  Result:
  event res -22
  
  From the code itself, it's expecting a -EIO return value:
- if (event.res == -EIO) {
- printf("invalidation returned -EIO, OK\n");
- exit(0);
- }
+ if (event.res == -EIO) {
+ printf("invalidation returned -EIO, OK\n");
+ exit(0);
+ }
  
  The actual return value is -22, which I think is -EINVAL
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-100-generic 4.4.0-100.123
  ProcVersionSignature: Ubuntu 4.4.0-100.123-generic 4.4.95
  Uname: Linux 4.4.0-100-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
-  
+ 
  Date: Wed Nov  8 01:57:40 2017
  HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
-  
+ 
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
-  linux-restricted-modules-4.4.0-100-generic N/A
-  linux-backports-modules-4.4.0-100-generic  N/A
-  linux-firmware 1.157.13
+  linux-restricted-modules-4.4.0-100-generic N/A
+  linux-backports-modules-4.4.0-100-generic  N/A
+  linux-firmware 1.157.13
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  aio-dio-invalidate-failure test failed with event res -22 on s390x

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This bug is for tracking purpose, this is not a regression for current
  cycle as this issue exists for a long time.

  It can be reproduced on zVM, zKVM and Ubuntu on LPAR

  Steps:
  1. git clone --depth=1 https://github.com/autotest/autotest-client-tests.git
  2. make -C autotest-client-tests/aio_dio_bugs/src
  3. sudo ./autotest-client-tests/aio_dio_bugs/src/aio-dio-invalidate-failure 
poo

  Result:
  event res -22

  From the code itself, it's expecting a -EIO return value:
  if (event.res == -EIO) {
  printf("invalidation returned -EIO, OK\n");
  exit(0);
  }

  The actual return value is -22, which I think is -EINVAL

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-100-generic 4.4.0-100.123
  ProcVersionSignature: Ubuntu 4.4.0-100.123-generic 4.4.95
  Uname: Linux 4.4.0-100-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:

  Date: Wed Nov  8 01:57:40 2017
  HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-100-generic N/A
   

Re: [Kernel-packages] [Bug 1724639] Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

[Kai-Heng Feng]

> On 7 Nov 2017, at 8:09 PM, Gianlo <1724...@bugs.launchpad.net> wrote:
> 
> Hello, 
> same problem with MSI u123H with atom processor, linux 4.13.0-16
> 
> for me GRUB_GFXPAYLOAD_LINUX=text
> doesn't solve the problem
> 
> i have to boot in recovery mode and all works fine

Because recovery mode add “nomodeset” kernel parameter.

Please file an upstream bug, as I mentioned in comment #11.

> 
> -- 
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1724639
> 
> Title:
>  Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen
> 
> Status in linux package in Ubuntu:
>  Confirmed
> Status in openSUSE:
>  Unknown
> 
> Bug description:
>  Installed O.S. on Samsung NC10. Display worked O.K. in text mode so
>  the install went smoothly. When the system is rebooted, however,
>  switching to graphics mode results in the below described screen
>  corruption:-
> 
>  Left  Hand Side 80% of screen black with a blue of white pixels and some 
> blue lines at the top
>  Right Hand Side 20% of screen OK.
> 
>  ProblemType: Bug
>  DistroRelease: Ubuntu 17.10
>  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
>  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>  Uname: Linux 4.13.0-16-generic i686
>  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
> k4.13.0-16-generic.
>  AplayDevices:
>    List of PLAYBACK Hardware Devices 
>   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
>  ApportVersion: 2.20.7-0ubuntu3
>  Architecture: i386
>  ArecordDevices:
>    List of CAPTURE Hardware Devices 
>   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
>  AudioDevicesInUse:
>   USERPID ACCESS COMMAND
>   /dev/snd/controlC0:  ian 918 F pulseaudio
>  Card0.Amixer.info:
>   Card hw:0 'Intel'/'HDA Intel at 0xf034 irq 25'
> Mixer name: 'Realtek ALC272'
> Components: 'HDA:10ec0272,144dca00,0011'
> Controls  : 25
> Simple ctrls  : 12
>  CurrentDesktop: LXDE
>  Date: Wed Oct 18 18:30:15 2017
>  HibernationDevice: RESUME=UUID=c54e130e-6625-4d96-ba75-4efaa6a9da75
>  InstallationDate: Installed on 2017-10-18 (0 days ago)
>  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 
> (20171017.1)
>  MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
>  ProcFB: 0 inteldrmfb
>  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
> root=UUID=d74a58ab-e96e-4531-a2eb-13f0d1610658 ro quiet splash vt.handoff=7
>  RelatedPackageVersions:
>   linux-restricted-modules-4.13.0-16-generic N/A
>   linux-backports-modules-4.13.0-16-generic  N/A
>   linux-firmware 1.169
>  SourcePackage: linux
>  UpgradeStatus: No upgrade log present (probably fresh install)
>  dmi.bios.date: 04/14/2009
>  dmi.bios.vendor: Phoenix Technologies Ltd.
>  dmi.bios.version: 07CA.M002.20090414.KTW
>  dmi.board.name: NC10
>  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
>  dmi.board.version: Not Applicable
>  dmi.chassis.asset.tag: No Asset Tag
>  dmi.chassis.type: 10
>  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
>  dmi.chassis.version: N/A
>  dmi.modalias: 
> dmi:bvnPhoenixTechnologiesLtd.:bvr07CA.M002.20090414.KTW:bd04/14/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
>  dmi.product.name: NC10
>  dmi.product.version: Not Applicable
>  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/+subscriptions

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

Title:
  Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

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

Bug description:
  Installed O.S. on Samsung NC10. Display worked O.K. in text mode so
  the install went smoothly. When the system is rebooted, however,
  switching to graphics mode results in the below described screen
  corruption:-

  Left  Hand Side 80% of screen black with a blue of white pixels and some blue 
lines at the top
  Right Hand Side 20% of screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.7-0ubuntu3
  

[Kernel-packages] [Bug 1730680] Re: Shutdown failure in 17.10 with Nvidia Nouveau Driver

[Kai-Heng Feng]

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

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

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

Title:
  Shutdown failure in 17.10 with Nvidia Nouveau Driver

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

Bug description:
  The following errors display at shutdown. The system never shuts down
  and I must hold down the power key to turn the system off. The
  hardware is a Dell 7559 laptop with Intel / Nvidia Prime Graphics GTX
  960M. The display driver in use is the Nouveau driver.

  wlp5s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardare (-22)
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561]
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561]
  INFO: rcu_sched self-detected stall on CPU
  $3...: (14999 ticks this GP) idle=e6e/14001/0 softirq:55865/55865 
fqs:7490
  $ (t=15000 jiffies g=41392 c=41391 q=3432)
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561]
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561]
  INFO: task systemd-timesyn:305 blocked for more than 120 seconds.
  Tained: G DEL 4.13-0-16-generic $19-ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message
  INFO: task systemd-timesyn:305 blocked for more than 120 seconds.
  Tained: G DEL 4.13-0-16-generic $19-ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561]
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561]
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561]
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561]

  At this point I had to hold down the power key to turn off the system.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  donp   1203 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-11-07 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171009)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 7559
  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.13.0-16-generic 
root=UUID=aa8f7506-7293-4695-a16a-9ecaf014f632 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  wayland-session artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.4
  dmi.board.name: 0H87XC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.4:bd06/08/2017:svnDellInc.:pnInspiron7559:pvr1.2.4:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.2.4
  dmi.sys.vendor: Dell Inc.

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  17.10 freezes on java interaction

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  on 17.04 java apps show a graphical display problem, now hangs all the
  computer

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rogelio1645 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 09:07:15 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e26838c6-6b72-461d-a811-a892d423fac1
  InstallationDate: Installed on 2017-05-04 (187 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. K55A
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-07 (0 days ago)
  dmi.bios.date: 03/13/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K55A.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K55A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK55A.204:bd03/13/2012:svnASUSTeKCOMPUTERINC.:pnK55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K55A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1730188] Re: linux-image-4.4.0-98 kernel panic

[Nagyt]

I got absolutely the same panic as on the screen shot in comment #1
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730188/comments/1)

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

Title:
  linux-image-4.4.0-98 kernel panic

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

Bug description:
  Since updating to linux-image-4.4.0-98-generic 2 days ago, I get a kernel 
panic during boot. With 4.4.0-97 the machine boots fine. Screenshot attached.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jos1929 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=5577332d-7a0a-4c5a-9c10-93a5cd6f5e65
  InstallationDate: Installed on 2013-01-05 (1764 days ago)
  InstallationMedia: This
  Lsusb:
   Bus 002 Device 003: ID 04f2:b34c Chicony Electronics Co., Ltd 
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: wortmann TERRA MOBILE 1512/1712
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic 
root=UUID=b9e9b26b-d84a-494e-921d-31e5e92726eb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-97-generic N/A
   linux-backports-modules-4.4.0-97-generic  N/A
   linux-firmware1.157.13
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.4.0-97-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-08-07 (454 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/22/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: TERRA MOBILE 1512/1712
  dmi.board.vendor: Wortmann AG
  dmi.board.version: V3.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Wortmann AG
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/22/2012:svnwortmann:pnTERRAMOBILE1512/1712:pvrNotApplicable:rvnWortmannAG:rnTERRAMOBILE1512/1712:rvrV3.0:cvnWortmannAG:ct10:cvrN/A:
  dmi.product.name: TERRA MOBILE 1512/1712
  dmi.product.version: Not Applicable
  dmi.sys.vendor: wortmann

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

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

[Kernel-packages] [Bug 1730904] [NEW] 17.10 freezes on java interaction

[Roger Tri]

Public bug reported:

on 17.04 java apps show a graphical display problem, now hangs all the
computer

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  rogelio1645 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  8 09:07:15 2017
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=e26838c6-6b72-461d-a811-a892d423fac1
InstallationDate: Installed on 2017-05-04 (187 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: ASUSTeK COMPUTER INC. K55A
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-16-generic N/A
 linux-backports-modules-4.13.0-16-generic  N/A
 linux-firmware 1.169
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-11-07 (0 days ago)
dmi.bios.date: 03/13/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K55A.204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K55A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK55A.204:bd03/13/2012:svnASUSTeKCOMPUTERINC.:pnK55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: K
dmi.product.name: K55A
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  17.10 freezes on java interaction

Status in linux package in Ubuntu:
  New

Bug description:
  on 17.04 java apps show a graphical display problem, now hangs all the
  computer

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rogelio1645 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 09:07:15 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e26838c6-6b72-461d-a811-a892d423fac1
  InstallationDate: Installed on 2017-05-04 (187 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. K55A
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-07 (0 days ago)
  dmi.bios.date: 03/13/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K55A.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K55A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK55A.204:bd03/13/2012:svnASUSTeKCOMPUTERINC.:pnK55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K55A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1729608] Re: arithmetic expression: expecting primary: " (32-)/4 "

[bsb]

When I configured the network without NetworkManager, the
networking.service wont start. Status showed this error, see reason. My
workaround was to rename the /etc/network/fan to fan.bak to get it
start.

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

Title:
  arithmetic expression: expecting primary: " (32-)/4 "

Status in ubuntu-fan package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I've configured a bridge interface (named vlan0) through interfaces,
  but can't take it up with ifup, since the if-up-script from ubuntu-fan
  aborts with error status

  
  reason:

  # fanctl net start vlan0
  /usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting 
primary: " (32-)/4 "


  As far as I can see the problem is that in cmd_net_up() the line

  
  addr="${addr%/*}"

  cuts the mask from the interface config and passes the pure ip address
  only, but later config_filename() calls width_to_mask(), which tries
  to use the (now missing) mask.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-fan 0.12.6
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Nov  2 14:26:42 2017
  InstallationDate: Installed on 2017-10-24 (9 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-fan
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1730924] Re: Wifi does down "crash" in Surface Pro 4

[Hicks]

** Attachment added: "error.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730924/+attachment/5005818/+files/error.jpg

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

Title:
  Wifi does down "crash" in Surface Pro 4

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Surface Pro 4. The wifi works well in principle, but unfortunately 
it drops every x minutes. The only way to fix it I've found is to reboot the 
computer.
  lsb_release -rd
  Description:Ubuntu 17.10
  Release:17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  predatux   1537 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Nov  8 10:41:26 2017
  HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b
  Lsusb:
   Bus 002 Device 002: ID 045e:090c Microsoft Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. 
   Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface Pro 4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago)
  dmi.bios.date: 02/24/2017
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: 106.1624.768
  dmi.board.name: Surface Pro 4
  dmi.board.vendor: Microsoft Corporation
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 4
  dmi.product.version: D:0B:08F:1C:03P:38
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1730717] Re: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"

[ChristianEhrhardt]

Torkoal (our Jenkins node) was idle atm and Ryan reported he had seen the 
issues there before, so trying there as well.
This is LTS + HWE - Kernel 4.10.0-38-generic, qemu: 1:2.5+dfsg-5ubuntu10

I thought about your case since you seem just to start a lot of them and reboot,
this shouldn't be so much different to:
$ uvt-simplestreams-libvirt --verbose sync --source 
http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=artful
$ for i in {1..30}; do uvt-kvm create --log-console-output --password=ubuntu 
artful-${i}-bug1730717 release=artful arch=amd64 label=daily; done
$ for i in {1..30}; do uvt-kvm wait --insecure artful-${i}-bug1730717; done
$ for i in {1..30}; do uvt-kvm ssh --insecure artful-${i}-bug1730717 "sudo 
reboot"; done
$ sudo grep "soft lockup" /var/log/libvirt/qemu/artful-*-bug1730717.log

But this works for me :-/

Waiting for your feedback if you can trigger the same issue on a non-
busy openstack system (could after all be some openstack magic at work
that makes it behave differently).

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

Title:
  Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck
  for 22s! [systemd:1]"

Status in linux package in Ubuntu:
  Triaged
Status in qemu-kvm package in Ubuntu:
  New
Status in linux source package in Artful:
  Triaged
Status in qemu-kvm source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in qemu-kvm source package in Bionic:
  New

Bug description:
  This is impacting us for ubuntu autopkgtests. Eventually the whole
  region ends up dying because each worker is hit by this bug in turn
  and backs off until the next reset (6 hourly).

  17.10 (and bionic) guests are sometimes failing to reboot. When this
  happens, you see the following in the console

    [[0;32m  OK  [0m] Reached target Shutdown.
    [  191.698969] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
    [  219.698438] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
    [  226.702150] INFO: rcu_sched detected stalls on CPUs/tasks:
    [  226.704958] »(detected by 0, t=15002 jiffies, g=5347, c=5346, q=187)
    [  226.706093] All QSes seen, last rcu_sched kthread activity 15002 
(4294949060-4294934058), jiffies_till_next_fqs=1, root ->qsmask 0x0
    [  226.708202] rcu_sched kthread starved for 15002 jiffies! g5347 c5346 
f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0

  One host that exhibits this behaviour was:

    Linux klock 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

  guest running:

    Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version 7.2.0
  (Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
  (Ubuntu 4.13.0-16.19-generic 4.13.4)

  The affected cloud region is running the xenial/Ocata cloud archive,
  so the version of qemu-kvm in there may also be relevant.

  Here's how I reproduced it in lcy01:

    $ for n in {1..30}; do nova boot --flavor m1.small --image 
ubuntu/ubuntu-artful-17.10-amd64-server-20171026.1-disk1.img --key-name 
testbed-`hostname` --nic net-name=net_ues_proposed_migration laney-test${n}; 
done
    $  sudo reboot
    # wait a minute or so for the instances to all reboot
    $ for n in {1..30}; do echo "=== ${n} ==="; nova console-log laney-test${n} 
| tail; done

  On bad instances you'll see the "soft lockup" message - on good it'll
  reboot as normal.

  We've seen good and bad instances on multiple compute hosts - it
  doesn't feel to me like a host problem but rather a race condition
  somewhere that's somehow either triggered or triggered much more often
  by what lcy01 is running. I always saw this on the first reboot -
  never on first boot, and never on n>1th boot. (But if it's a race then
  that might not mean much.)

  I'll attach a bad and a good console-log for reference.

  If you're at Canonical then see internal rt #107135 for some other
  details.

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

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

[Kernel-packages] [Bug 696435] Re: wait-for-root fails to detect nbd root

[Kleber Sacilotto de Souza]

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

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

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


** Tags added: verification-needed-xenial

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

Title:
  wait-for-root fails to detect nbd root

Status in linux package in Ubuntu:
  Fix Released
Status in nbd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Confirmed

Bug description:
  [Impact]
  Kernel does not generate any events when ndb-client connects /dev/nbd0 
devices, therefore it is impossible to monitor/react to the state of /dev/nbd0.

  [Fix]
  Generate change uevent when size of /dev/nbd0 changes

  [Testcase]
  * Start udevadm monitor
  * modprobe nbd
  * use ndb-client to connect something to /dev/nbd0
  * observe that there are change udev events generated on /dev/nbd0 itself

  [Regression Potential]
  There is no change to existing uevents, or their ordering.
  There is now an addition change event which will cause systemd to mark ndb 
devices as ready and trigger appropriate actions

  [Original Bug Report]

  When using an nbd root, wait-for-root blocks for 30 seconds before
  booting continues successfully.

  Using Ubuntu Natty, related packages versions:
  nbd-client 1:2.9.16-6ubuntu1
  initramfs-tools 0.98.1ubuntu9

  The wait-for-root call from /usr/share/initramfs-tools/scripts/local:
   while [ -z "${FSTYPE}" ]; do
    FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30})

    # Run failure hooks, hoping one of them can fix up the system
    # and we can restart the wait loop.  If they all fail, abort
    # and move on to the panic handler and shell.
    if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then
     break
    fi
   done

  I replaced wait-for-root with a sh script that did `set >&2`, here are the 
relevant environment variables at the time wait-for-root was called:
  ROOT='/dev/nbd0'
  ROOTDELAY=''
  ROOTFLAGS=''
  ROOTFSTYPE=''
  nbdroot='192.168.0.1,2011'

  It's probably worth noting that "nbd0: unknown partition table" was
  displayed asynchronously 1-2 seconds after wait-for-root was invoked
  and while it was still waiting. But I tried adding a "sleep 5" as the
  last line of local-top/nbd, so that the nbd message was displayed a
  lot before wait-for-root was called, and it didn't make a difference.
  So I don't think a race condition is involved in this problem.

  Temporarily I'm passing rootdelay=1 in the kernel command line to work
  around the problem.

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1730926

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

Title:
  lxc-test-unpriv test failed on s390x instances

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a POTENTIAL REGRESSION.

  This test has passed with older kernels (4.4.0-98, 4.4.0-97, 4.4.0-96), but 
this time it failed.
  Issue can be seen on zKVM, zVM and Ubuntu on LPAR

  Steps:
  1. Install lxc-tests
  2. Run sudo /usr/bin/lxc-test-unpriv

  Result:
---
mount: wrong fs type, bad option, bad superblock on none,
   missing codepage or helper program, or other error

   In some cases useful info is found in syslog - try
   dmesg | tail or so.
umount: /tmp/tmp.uMnoGYXJSH/ovl_symlink_test/overlayfs: not mounted
/usr/sbin/deluser: The user `lxcunpriv' does not exist.
Path existed
Using image from local cache
Unpacking the rootfs

---
You just created an Ubuntu container (release=xenial, arch=s390x, 
variant=default)

To enable sshd, run: apt-get install openssh-server

For security reason, container images ship without user accounts
and without a root password.

Use lxc-attach or chroot directly into the rootfs to set a root password
or create user accounts.
Name:   c1
State:  RUNNING
PID:5846
CPU use:0.05 seconds
BlkIO use:  0 bytes
Memory use: 10.04 MiB
KMem use:   0 bytes
Link:   vethV2EVRI
 TX bytes:  0 bytes
 RX bytes:  0 bytes
 Total bytes:   0 bytes
Name:   c1
State:  RUNNING
PID:6218
CPU use:0.03 seconds
BlkIO use:  0 bytes
Memory use: 1.50 MiB
KMem use:   0 bytes
Link:   vethA54DMR
 TX bytes:  0 bytes
 RX bytes:  0 bytes
 Total bytes:   0 bytes
Testing containers under different cgroups per subsystem
call to cgmanager_move_pid_main_sync failed: invalid request
c2 is not running
c1 is not running
Removing user `lxcunpriv' ...
Warning: group `lxcunpriv' has no more members.
Done.
FAIL
---

  The mount error (bug 1730915) is not the cause, it looks like the failure was 
caused by:
call to cgmanager_move_pid_main_sync failed: invalid request

  In that shell script, this line account for the error:
  cgm movepid freezer x1 $$

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-100-generic 4.4.0-100.123
  ProcVersionSignature: Ubuntu 4.4.0-100.123-generic 4.4.95
  Uname: Linux 4.4.0-100-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Wed Nov  8 04:39:12 2017
  HibernationDevice: RESUME=UUID=ca468a9c-9563-442c-85c6-6055e800a66e
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=b65b756a-ba4e-4c53-aa32-0db2bdb50bb3 
crashkernel=196M
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-100-generic N/A
   linux-backports-modules-4.4.0-100-generic  N/A
   linux-firmware 1.157.13
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1730926] [NEW] lxc-test-unpriv test failed on s390x instances

[Po-Hsu Lin]

Public bug reported:

This is a POTENTIAL REGRESSION.

This test has passed with older kernels (4.4.0-98, 4.4.0-97, 4.4.0-96), but 
this time it failed.
Issue can be seen on zKVM, zVM and Ubuntu on LPAR

Steps:
1. Install lxc-tests
2. Run sudo /usr/bin/lxc-test-unpriv

Result:
  ---
  mount: wrong fs type, bad option, bad superblock on none,
 missing codepage or helper program, or other error
  
 In some cases useful info is found in syslog - try
 dmesg | tail or so.
  umount: /tmp/tmp.uMnoGYXJSH/ovl_symlink_test/overlayfs: not mounted
  /usr/sbin/deluser: The user `lxcunpriv' does not exist.
  Path existed
  Using image from local cache
  Unpacking the rootfs
  
  ---
  You just created an Ubuntu container (release=xenial, arch=s390x, 
variant=default)
  
  To enable sshd, run: apt-get install openssh-server
  
  For security reason, container images ship without user accounts
  and without a root password.
  
  Use lxc-attach or chroot directly into the rootfs to set a root password
  or create user accounts.
  Name:   c1
  State:  RUNNING
  PID:5846
  CPU use:0.05 seconds
  BlkIO use:  0 bytes
  Memory use: 10.04 MiB
  KMem use:   0 bytes
  Link:   vethV2EVRI
   TX bytes:  0 bytes
   RX bytes:  0 bytes
   Total bytes:   0 bytes
  Name:   c1
  State:  RUNNING
  PID:6218
  CPU use:0.03 seconds
  BlkIO use:  0 bytes
  Memory use: 1.50 MiB
  KMem use:   0 bytes
  Link:   vethA54DMR
   TX bytes:  0 bytes
   RX bytes:  0 bytes
   Total bytes:   0 bytes
  Testing containers under different cgroups per subsystem
  call to cgmanager_move_pid_main_sync failed: invalid request
  c2 is not running
  c1 is not running
  Removing user `lxcunpriv' ...
  Warning: group `lxcunpriv' has no more members.
  Done.
  FAIL
  ---

The mount error (bug 1730915) is not the cause, it looks like the failure was 
caused by:
  call to cgmanager_move_pid_main_sync failed: invalid request

In that shell script, this line account for the error:
cgm movepid freezer x1 $$

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-100-generic 4.4.0-100.123
ProcVersionSignature: Ubuntu 4.4.0-100.123-generic 4.4.95
Uname: Linux 4.4.0-100-generic s390x
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: 
ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not 
found.
Date: Wed Nov  8 04:39:12 2017
HibernationDevice: RESUME=UUID=ca468a9c-9563-442c-85c6-6055e800a66e
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci:
 
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
 
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C
 SHELL=/bin/bash
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=UUID=b65b756a-ba4e-4c53-aa32-0db2bdb50bb3 
crashkernel=196M
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-100-generic N/A
 linux-backports-modules-4.4.0-100-generic  N/A
 linux-firmware 1.157.13
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug package-from-proposed s390x third-party-packages 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/1730926

Title:
  lxc-test-unpriv test failed on s390x instances

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a POTENTIAL REGRESSION.

  This test has passed with older kernels (4.4.0-98, 4.4.0-97, 4.4.0-96), but 
this time it failed.
  Issue can be seen on zKVM, zVM and Ubuntu on LPAR

  Steps:
  1. Install lxc-tests
  2. Run sudo /usr/bin/lxc-test-unpriv

  Result:
---
mount: wrong fs type, bad option, bad superblock on none,
   missing codepage or helper program, or other error

   In some cases useful info is found in syslog - try
   dmesg | tail or so.
umount: /tmp/tmp.uMnoGYXJSH/ovl_symlink_test/overlayfs: not mounted
/usr/sbin/deluser: The user `lxcunpriv' does not exist.
Path existed
Using image from local cache
Unpacking the rootfs

---
You just created an Ubuntu container (release=xenial, arch=s390x, 
variant=default)

To enable sshd, run: apt-get install openssh-server

For security reason, container images ship without user 

Re: [Kernel-packages] [Bug 1730717] Re: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"

[Iain Lane]

On Wed, Nov 08, 2017 at 11:56:02AM -, ChristianEhrhardt wrote:
> Torkoal (our Jenkins node) was idle atm and Ryan reported he had seen the 
> issues there before, so trying there as well.
> This is LTS + HWE - Kernel 4.10.0-38-generic, qemu: 1:2.5+dfsg-5ubuntu10
> 
> I thought about your case since you seem just to start a lot of them and 
> reboot,
> this shouldn't be so much different to:
> $ uvt-simplestreams-libvirt --verbose sync --source 
> http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=artful
> $ for i in {1..30}; do uvt-kvm create --log-console-output --password=ubuntu 
> artful-${i}-bug1730717 release=artful arch=amd64 label=daily; done
> $ for i in {1..30}; do uvt-kvm wait --insecure artful-${i}-bug1730717; done
> $ for i in {1..30}; do uvt-kvm ssh --insecure artful-${i}-bug1730717 "sudo 
> reboot"; done
> $ sudo grep "soft lockup" /var/log/libvirt/qemu/artful-*-bug1730717.log

Sounds like it's similar, but maybe you have to put the system under
load - you might need more instances, or maybe start a whole bunch first
and get them to run something memory intensive before running that same
test again. In the cloud there will be buildds and tests running on the
compute nodes too, as well as these 'empty' instances that I use to
reproduce the problem.

> Waiting for your feedback if you can trigger the same issue on a non-
> busy openstack system (could after all be some openstack magic at work
> that makes it behave differently).

I don't have access to a non busy cloud I'm afraid.

ANYWAY! My results are in. I created an image by booting the stock
artful cloud image and installing the mainline kernel v4.14-rc8
(39dae59d66acd86d1de24294bd2f343fd5e7a625) packages, on lcy01 (the busy
cloud that exhibits this problem).

I started 34 (17 × 2 in two runs - that's all I could squeeze in before
I hit my quota) instances, and they were all good. This isn't definitive
proof, but it looks like that kernel might be good.

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck
  for 22s! [systemd:1]"

Status in linux package in Ubuntu:
  Triaged
Status in qemu-kvm package in Ubuntu:
  New
Status in linux source package in Artful:
  Triaged
Status in qemu-kvm source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in qemu-kvm source package in Bionic:
  New

Bug description:
  This is impacting us for ubuntu autopkgtests. Eventually the whole
  region ends up dying because each worker is hit by this bug in turn
  and backs off until the next reset (6 hourly).

  17.10 (and bionic) guests are sometimes failing to reboot. When this
  happens, you see the following in the console

    [[0;32m  OK  [0m] Reached target Shutdown.
    [  191.698969] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
    [  219.698438] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
    [  226.702150] INFO: rcu_sched detected stalls on CPUs/tasks:
    [  226.704958] »(detected by 0, t=15002 jiffies, g=5347, c=5346, q=187)
    [  226.706093] All QSes seen, last rcu_sched kthread activity 15002 
(4294949060-4294934058), jiffies_till_next_fqs=1, root ->qsmask 0x0
    [  226.708202] rcu_sched kthread starved for 15002 jiffies! g5347 c5346 
f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0

  One host that exhibits this behaviour was:

    Linux klock 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

  guest running:

    Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version 7.2.0
  (Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
  (Ubuntu 4.13.0-16.19-generic 4.13.4)

  The affected cloud region is running the xenial/Ocata cloud archive,
  so the version of qemu-kvm in there may also be relevant.

  Here's how I reproduced it in lcy01:

    $ for n in {1..30}; do nova boot --flavor m1.small --image 
ubuntu/ubuntu-artful-17.10-amd64-server-20171026.1-disk1.img --key-name 
testbed-`hostname` --nic net-name=net_ues_proposed_migration laney-test${n}; 
done
    $  sudo reboot
    # wait a minute or so for the instances to all reboot
    $ for n in {1..30}; do echo "=== ${n} ==="; nova console-log laney-test${n} 
| tail; done

  On bad instances you'll see the "soft lockup" message - on good it'll
  reboot as normal.

  We've seen good and bad instances on multiple compute hosts - it
  doesn't feel to me like a host problem but rather a race condition
  somewhere that's somehow either triggered or triggered much more often
  by what lcy01 is running. I always saw this on the first reboot -

[Kernel-packages] [Bug 1730924] [NEW] Wifi does down "crash" in Surface Pro 4

[Hicks]

Public bug reported:

I have a Surface Pro 4. The wifi works well in principle, but unfortunately it 
drops every x minutes. The only way to fix it I've found is to reboot the 
computer.
lsb_release -rd
Description:Ubuntu 17.10
Release:17.10

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  predatux   1537 F pulseaudio
CurrentDesktop: KDE
Date: Wed Nov  8 10:41:26 2017
HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b
Lsusb:
 Bus 002 Device 002: ID 045e:090c Microsoft Corp. 
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. 
 Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Microsoft Corporation Surface Pro 4
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-16-generic N/A
 linux-backports-modules-4.13.0-16-generic  N/A
 linux-firmware 1.169
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago)
dmi.bios.date: 02/24/2017
dmi.bios.vendor: Microsoft Corporation
dmi.bios.version: 106.1624.768
dmi.board.name: Surface Pro 4
dmi.board.vendor: Microsoft Corporation
dmi.chassis.type: 9
dmi.chassis.vendor: Microsoft Corporation
dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr:
dmi.product.family: Surface
dmi.product.name: Surface Pro 4
dmi.product.version: D:0B:08F:1C:03P:38
dmi.sys.vendor: Microsoft Corporation

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


** Tags: amd64 apport-bug artful

** Attachment added: "version.log"
   
https://bugs.launchpad.net/bugs/1730924/+attachment/5005799/+files/version.log

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

Title:
  Wifi does down "crash" in Surface Pro 4

Status in linux package in Ubuntu:
  New

Bug description:
  I have a Surface Pro 4. The wifi works well in principle, but unfortunately 
it drops every x minutes. The only way to fix it I've found is to reboot the 
computer.
  lsb_release -rd
  Description:Ubuntu 17.10
  Release:17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  predatux   1537 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Nov  8 10:41:26 2017
  HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b
  Lsusb:
   Bus 002 Device 002: ID 045e:090c Microsoft Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. 
   Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface Pro 4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago)
  dmi.bios.date: 02/24/2017
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: 106.1624.768
  dmi.board.name: Surface Pro 4
  dmi.board.vendor: Microsoft Corporation
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 4
  dmi.product.version: D:0B:08F:1C:03P:38
  dmi.sys.vendor: Microsoft Corporation

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Wifi does down "crash" in Surface Pro 4

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Surface Pro 4. The wifi works well in principle, but unfortunately 
it drops every x minutes. The only way to fix it I've found is to reboot the 
computer.
  lsb_release -rd
  Description:Ubuntu 17.10
  Release:17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  predatux   1537 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Nov  8 10:41:26 2017
  HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b
  Lsusb:
   Bus 002 Device 002: ID 045e:090c Microsoft Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. 
   Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface Pro 4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago)
  dmi.bios.date: 02/24/2017
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: 106.1624.768
  dmi.board.name: Surface Pro 4
  dmi.board.vendor: Microsoft Corporation
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 4
  dmi.product.version: D:0B:08F:1C:03P:38
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1730924] Re: Wifi does down "crash" in Surface Pro 4

[Hicks]

Tested with "wicd" too.
Wicd crashes when wifi goes down

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

Title:
  Wifi does down "crash" in Surface Pro 4

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Surface Pro 4. The wifi works well in principle, but unfortunately 
it drops every x minutes. The only way to fix it I've found is to reboot the 
computer.
  lsb_release -rd
  Description:Ubuntu 17.10
  Release:17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  predatux   1537 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Nov  8 10:41:26 2017
  HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b
  Lsusb:
   Bus 002 Device 002: ID 045e:090c Microsoft Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. 
   Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface Pro 4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago)
  dmi.bios.date: 02/24/2017
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: 106.1624.768
  dmi.board.name: Surface Pro 4
  dmi.board.vendor: Microsoft Corporation
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 4
  dmi.product.version: D:0B:08F:1C:03P:38
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1510570] Re: Bluetooth LE pairing fail

[Yuan-Chen Cheng]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

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

** Changed in: oem-priority
   Status: New => Confirmed

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

Title:
  Bluetooth LE pairing fail

Status in OEM Priority Project:
  Confirmed
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Xenial:
  New

Bug description:
  [Impact]

  When the Bluetooth adapter is not powered on it is not possible to use
  it in normal way. We used to have a hack to force powering on by using
  an udev rule but this doe snot work anymore. Luckily the BlueZ has
  introduced "AutoEnable" option that makes the stack power on adapters by
  itself.

  Backporting this to xenial will improve life of the desktop users and
  will not require them to hack the solution on their own. The fix itself
  uses the well known solution to this problem that is floating around
  there for a while.

  The upload fixes the bug by enabling the 'AutoEnable' option in the
  bluetoothd config file.

  [Original Report]

  . 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.

  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used
  instead of udev rules.

  here is a commit with this parameter:
  http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138

  [Test Case]

  Edit the /etc/bluetooth/main.conf and disable the 'AutoEnable' option.
  Remove file 50-bluetooth-hci-auto-poweron.rules located in
  /lib/udev/rules.d. Now reboot the machine. The BT adapter shall be
  powered off now.

  [Regression Potential]

  Cannot think of any

  [Other Info]

  This fix is included in the development release, see:
  http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

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

[Kleber Sacilotto de Souza]

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

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

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


** Tags added: verification-needed-artful

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

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

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

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 1709282] Re: Plantronics Blackwire C520-M - Cannot get freq at ep 0x1, 0x81

[Kleber Sacilotto de Souza]

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

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

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


** Tags added: verification-needed-xenial

** Tags added: verification-needed-zesty

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

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

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

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   : 

[Kernel-packages] [Bug 1726493] Re: linux-aws needs module: nls_utf8

[Kleber Sacilotto de Souza]

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

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

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


** Tags added: verification-needed-xenial

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

Title:
  linux-aws needs module: nls_utf8

Status in linux-aws package in Ubuntu:
  Fix Committed
Status in linux-aws source package in Xenial:
  Fix Committed

Bug description:
  Amazon requests nls_utf8.ko be made available in the main linux-aws
  kernel image package.

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

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

[Cristian Aravena Romero]

Hello,

I'm working with Ubuntu Bionic.

In Ubuntu Bionic is not the version of the kernel needed to test
(prosposed). However, I am testing vmlinuz-4.14.0-041400rc8-generic and
the message no longer appears.

Regards,
--
Cristian

** Attachment added: "dmesg_4.14.0-041400rc8-generic.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708499/+attachment/5005864/+files/dmesg_4.14.0-041400rc8-generic.log

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

Title:
  usb 3-1: 2:1: cannot get freq at ep 0x1

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

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.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   caravena   1838 F...m pulseaudio
   /dev/snd/controlC1:  caravena   1838 F pulseaudio
   /dev/snd/controlC0:  caravena   1838 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-13 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-16-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-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/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.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To 

[Kernel-packages] [Bug 1727856] Re: update ENA driver to 1.3.0K from net-next

[Kleber Sacilotto de Souza]

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

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

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


** Tags added: verification-needed-xenial

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

Title:
  update ENA driver to 1.3.0K from net-next

Status in linux-aws package in Ubuntu:
  Fix Committed
Status in linux-aws source package in Trusty:
  Fix Committed
Status in linux-aws source package in Xenial:
  Fix Committed

Bug description:
  Commits from net-next and mainline to update ENA from 1.2.0k to
  1.3.0K:

  net-next c057c68 MAINTAINERS: change ENA driver maintainers email domain
  net-next 1f4cf93 net: ena: Remove redundant unlikely()
  mainline cd7aea1 net: ena: reduce the severity of some printouts
  mainline 411838e net: ena: fix rare kernel crash when bar memory remap fails
  mainline a59df39 net: ena: fix wrong max Tx/Rx queues on ethtool
  net-next 88aef2f net: ena: improve ENA driver boot time.
  net-next dbeaf1e net: ena: remove legacy suspend suspend/resume support
  net-next 8c5c7ab net: ena: add power management ops to the ENA driver
  net-next 11095fd net: ena: add statistics for missed tx packets
  net-next 58894d5 net: ena: add new admin define for future support of IPv6 RSS
  net-next 046b307 net: ena: increase ena driver version to 1.3.0

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

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

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

[Kleber Sacilotto de Souza]

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

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

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


** Tags added: verification-needed-xenial

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

Title:
  NVMe timeout is too short

Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  New
Status in linux-aws source package in Xenial:
  Fix Committed

Bug description:
  [SRU Justification]

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

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

  [Regression Potential]
  Very limited: only types of module parameters are changing, the patch is 
easily reviewable.

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

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

[Kernel-packages] [Bug 1730717] Re: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"

[ChristianEhrhardt]

Out of the IRC discussions documenting potentially related issues:
- this bug: KVM: Host-Kernel: Xenial-GA, Qemu: Xenial-Ocata, Guest: Bionic
- bug 1722311 KVM: Host-Kernel: Xenial-GA, Qemu: Xenial, Guest: Artful - some 
relation to cache pressure
- bug 1713751 AWS: triggered by Xenial kernel update, supposed fixed but shown 
up again and again
- bug 1655842 Host-Kernel: Xenial-GA, Qemu: Xenial, Guest: Artful - some 
relation to cache pressure
These might after all just run into the same soft lockup symptom, but I thought 
it was worth to mention for thos enot reading the IRC log.

These cases seem to somewhat agree on:
- Recent guest kernel
- Xenial Host kernel
- some memory pressure

To get further I thought some sort of local reproducer for the kernel Team to 
work on easier than needing a full cloud.
But so far I failed at setting such a local case up 
(http://paste.ubuntu.com/25916781/).

Thanks Laney for the openstack based repro description.
@Laney I found it interesting that you essentially only needed to start+reboot.
I assume on the host you had other workload goes on in the background (since it 
is lcy01)?
If you'd have any sort of non-busy but otherwise comparable system - could you 
check to confirm the assumption we have so far that there all is fine?
If yes - then the memory pressure theory gets more likely, if not we can focus 
on simpler reproducers - so we can only win by that check.

Crossing fingers for jsalisbury's hope that 4.14 might already have a
fix.

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

Title:
  Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck
  for 22s! [systemd:1]"

Status in linux package in Ubuntu:
  Triaged
Status in qemu-kvm package in Ubuntu:
  New
Status in linux source package in Artful:
  Triaged
Status in qemu-kvm source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in qemu-kvm source package in Bionic:
  New

Bug description:
  This is impacting us for ubuntu autopkgtests. Eventually the whole
  region ends up dying because each worker is hit by this bug in turn
  and backs off until the next reset (6 hourly).

  17.10 (and bionic) guests are sometimes failing to reboot. When this
  happens, you see the following in the console

    [[0;32m  OK  [0m] Reached target Shutdown.
    [  191.698969] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
    [  219.698438] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
    [  226.702150] INFO: rcu_sched detected stalls on CPUs/tasks:
    [  226.704958] »(detected by 0, t=15002 jiffies, g=5347, c=5346, q=187)
    [  226.706093] All QSes seen, last rcu_sched kthread activity 15002 
(4294949060-4294934058), jiffies_till_next_fqs=1, root ->qsmask 0x0
    [  226.708202] rcu_sched kthread starved for 15002 jiffies! g5347 c5346 
f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0

  One host that exhibits this behaviour was:

    Linux klock 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

  guest running:

    Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version 7.2.0
  (Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
  (Ubuntu 4.13.0-16.19-generic 4.13.4)

  The affected cloud region is running the xenial/Ocata cloud archive,
  so the version of qemu-kvm in there may also be relevant.

  Here's how I reproduced it in lcy01:

    $ for n in {1..30}; do nova boot --flavor m1.small --image 
ubuntu/ubuntu-artful-17.10-amd64-server-20171026.1-disk1.img --key-name 
testbed-`hostname` --nic net-name=net_ues_proposed_migration laney-test${n}; 
done
    $  sudo reboot
    # wait a minute or so for the instances to all reboot
    $ for n in {1..30}; do echo "=== ${n} ==="; nova console-log laney-test${n} 
| tail; done

  On bad instances you'll see the "soft lockup" message - on good it'll
  reboot as normal.

  We've seen good and bad instances on multiple compute hosts - it
  doesn't feel to me like a host problem but rather a race condition
  somewhere that's somehow either triggered or triggered much more often
  by what lcy01 is running. I always saw this on the first reboot -
  never on first boot, and never on n>1th boot. (But if it's a race then
  that might not mean much.)

  I'll attach a bad and a good console-log for reference.

  If you're at Canonical then see internal rt #107135 for some other
  details.

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

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

Re: [Kernel-packages] [Bug 1730717] Re: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"

[Iain Lane]

On Wed, Nov 08, 2017 at 11:08:05AM -, ChristianEhrhardt wrote:
> @Laney I found it interesting that you essentially only needed to 
> start+reboot.
> I assume on the host you had other workload goes on in the background (since 
> it is lcy01)?

I don't have visibility into what else the hosts are doing - I'm just a
client here. But I do know that *I* had other workloads running at the
same time. I assume that there were a lot of buildd jobs too. These
compute nodes are probably loaded most of the time.

> If you'd have any sort of non-busy but otherwise comparable system - could 
> you check to confirm the assumption we have so far that there all is fine?
> If yes - then the memory pressure theory gets more likely, if not we can 
> focus on simpler reproducers - so we can only win by that check.

Afraid not, sorry. I did try on my artful+artful host but didn't
reproduce the problem - it probably wasn't under enough stress anyway.

> Crossing fingers for jsalisbury's hope that 4.14 might already have a
> fix.

Right now I'm trying to build a new cloud image with this kernel that I
can try.

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck
  for 22s! [systemd:1]"

Status in linux package in Ubuntu:
  Triaged
Status in qemu-kvm package in Ubuntu:
  New
Status in linux source package in Artful:
  Triaged
Status in qemu-kvm source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in qemu-kvm source package in Bionic:
  New

Bug description:
  This is impacting us for ubuntu autopkgtests. Eventually the whole
  region ends up dying because each worker is hit by this bug in turn
  and backs off until the next reset (6 hourly).

  17.10 (and bionic) guests are sometimes failing to reboot. When this
  happens, you see the following in the console

    [[0;32m  OK  [0m] Reached target Shutdown.
    [  191.698969] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
    [  219.698438] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
    [  226.702150] INFO: rcu_sched detected stalls on CPUs/tasks:
    [  226.704958] »(detected by 0, t=15002 jiffies, g=5347, c=5346, q=187)
    [  226.706093] All QSes seen, last rcu_sched kthread activity 15002 
(4294949060-4294934058), jiffies_till_next_fqs=1, root ->qsmask 0x0
    [  226.708202] rcu_sched kthread starved for 15002 jiffies! g5347 c5346 
f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0

  One host that exhibits this behaviour was:

    Linux klock 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

  guest running:

    Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version 7.2.0
  (Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
  (Ubuntu 4.13.0-16.19-generic 4.13.4)

  The affected cloud region is running the xenial/Ocata cloud archive,
  so the version of qemu-kvm in there may also be relevant.

  Here's how I reproduced it in lcy01:

    $ for n in {1..30}; do nova boot --flavor m1.small --image 
ubuntu/ubuntu-artful-17.10-amd64-server-20171026.1-disk1.img --key-name 
testbed-`hostname` --nic net-name=net_ues_proposed_migration laney-test${n}; 
done
    $  sudo reboot
    # wait a minute or so for the instances to all reboot
    $ for n in {1..30}; do echo "=== ${n} ==="; nova console-log laney-test${n} 
| tail; done

  On bad instances you'll see the "soft lockup" message - on good it'll
  reboot as normal.

  We've seen good and bad instances on multiple compute hosts - it
  doesn't feel to me like a host problem but rather a race condition
  somewhere that's somehow either triggered or triggered much more often
  by what lcy01 is running. I always saw this on the first reboot -
  never on first boot, and never on n>1th boot. (But if it's a race then
  that might not mean much.)

  I'll attach a bad and a good console-log for reference.

  If you're at Canonical then see internal rt #107135 for some other
  details.

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

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

[Kernel-packages] [Bug 1721065] Re: NULL pointer dereference in tty_write() in kernel 4.4.0-93.116+

[Kleber Sacilotto de Souza]

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

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

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


** Tags added: verification-needed-xenial

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

Title:
  NULL pointer dereference in tty_write() in kernel 4.4.0-93.116+

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

Bug description:
  Sometimes an Ubuntu kernel 4.4.0-93+ panics in the following way:

  [   11.185347] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   11.185778] IP: [] tty_write+0x83/0x2d0
  [   11.186115] PGD 0 
  [   11.186270] Oops:  [#1] SMP 
  [   11.186506] Modules linked in: prl_fs(POE) prl_eth(POE) gpio_ich ppdev 
snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm s
  nd_timer input_leds snd serio_raw soundcore lpc_ich shpchp sbs prl_tg(POE) 
sbshc pvpanic parport_pc parport mac_hid auto
  fs4 psmouse ahci libahci pata_acpi fjes
  [   11.188034] CPU: 0 PID: 1 Comm: systemd Tainted: P   OE   
4.4.0-96-generic #119-Ubuntu
  [   11.188482] Hardware name: Parallels Software International Inc. Parallels 
Virtual Platform/Parallels Virtual Platfor
  m, BIOS 13.1.0 (43104) 09/26/2017
  [   11.189156] task: 88003db8 ti: 88003db88000 task.ti: 
88003db88000
  [   11.189546] RIP: 0010:[]  [] 
tty_write+0x83/0x2d0
  [   11.189964] RSP: :88003db8bcc8  EFLAGS: 00010246
  [   11.190255] RAX:  RBX: 8800392dd800 RCX: 

  [   11.190628] RDX:  RSI:  RDI: 
8800392dd828
  [   11.191002] RBP: 88003db8bd18 R08: 88003db88000 R09: 

  [   11.191398] R10: 005c R11: 00401ce0 R12: 
002f
  [   11.191775] R13: 88003584ae70 R14: 55c8eab15f20 R15: 
88003584ae00
  [   11.192152] FS:  7f649d1418c0() GS:88003de0() 
knlGS:
  [   11.192573] CS:  0010 DS:  ES:  CR0: 80050033
  [   11.192882] CR2:  CR3: 3d3b6000 CR4: 
06f0
  [   11.193264] Stack:
  [   11.193404]   813953ba 88003db8bd08 
813493bd
  [   11.193837]  002f 88003584ae00 55c8eab15f20 
88003584ae70
  [   11.194267]  002f 88003db8bf18 88003db8bd28 
8120f878
  [   11.194700] Call Trace:
  [   11.194884]  [] ? apparmor_file_permission+0x1a/0x20
  [   11.195248]  [] ? security_file_permission+0x3d/0xc0
  [   11.195621]  [] __vfs_write+0x18/0x40
  [   11.195916]  [] vfs_write+0xa9/0x1a0
  [   11.196202]  [] redirected_tty_write+0x60/0xa0
  [   11.196532]  [] ? tty_write+0x2d0/0x2d0
  [   11.196830]  [] do_loop_readv_writev+0x75/0xa0
  [   11.197160]  [] ? tty_write+0x2d0/0x2d0
  [   11.197458]  [] do_readv_writev+0x212/0x230
  [   11.198439]  [] ? do_vfs_ioctl+0x29f/0x490
  [   11.199374]  [] vfs_writev+0x39/0x50
  [   11.200268]  [] SyS_writev+0x59/0xf0
  [   11.201144]  [] ? SyS_ioctl+0x79/0x90
  [   11.202049]  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [   11.202980] Code: 47 02 00 00 48 8b 93 e0 01 00 00 83 e2 02 0f 85 37 02 00 
00 48 83 78 50 00 0f 84 38 02 00 00 48 89 df e8 11 7f 00 00 48 89 45 b0 <48> 8b 
00 48 8b 40 40 48 89 c2 48 89 45 c0 48 c7 c0 fb ff ff ff 
  [   11.208047] RIP  [] tty_write+0x83/0x2d0
  [   11.208942]  RSP 
  [   11.209713] CR2: 
  [   11.210517] ---[ end trace 3b933544655b49b8 ]---
  [   11.335210] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009
  [   11.335210] 
  [   11.337095] Kernel Offset: disabled
  [   11.338184] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009

  The crash occurs here

  1227 static ssize_t tty_write(struct file *file, const char __user *buf,
  [...]
  1243 ld = tty_ldisc_ref_wait(tty);
  1244 if (!ld->ops->write) // <===
  1245 ret = -EIO;
  1246 else
  1247 ret = do_tty_write(ld->ops->write, tty, file, buf, 
count);

  because tty_ldisc_ref_wait() returned NULL.

  It seems the issue has been introduced into 4.4.0-93+ kernels
  by the fix for the bug #1709126: according to the version 4.4.0-93.116
  changelog the patch "tty: Destroy ldisc instance on hangup" 

[Kernel-packages] [Bug 1718388] Re: Fix OpenNSL GPL bugs found by CoverityScan static analysis

[Kleber Sacilotto de Souza]

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

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

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


** Tags added: verification-needed-xenial

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

Title:
  Fix OpenNSL GPL bugs found by CoverityScan static analysis

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

Bug description:
  Static analysis on the ubuntu/opennsl drivers in Xenial have picked up
  various bugs. These need fixing.

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

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

[Kernel-packages] [Bug 1721538] Re: Remove vmbus-rdma driver from Xenial kernel

[Kleber Sacilotto de Souza]

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

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

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


** Tags added: verification-needed-xenial

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

Title:
  Remove vmbus-rdma driver from Xenial kernel

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

Bug description:
  SRU Justification:

  Impact: in order to properly support infiniband for Azure A8/A9,
  H-series, and NC24/NV24 instances, multiple versions of the driver
  must be maintained and userspace must be responsible for selecting the
  correct version of the driver.

  That's already supported in the linux-azure kernel with the userspace
  logic implemented in the Windows Azure Linux Agent. The Xenial kernel
  is carrying a single version of the RDMA which might cause problems if
  the host OS requires a different version of the driver.

  Fix: remove the driver located at "drivers/infiniband/hw/vmbus-rdma/"
  from the Xenial kernel and keep support to it only in linux-azure.

  Testcase: the module "hv_network_direct.ko" should not be included in
  the linux-image or linux-image-extra packages.

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

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

[Kernel-packages] [Bug 1722719] Re: HID: multitouch: Correct ALPS PTP Stick and Touchpad devices ID

[Kleber Sacilotto de Souza]

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

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

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


** Tags added: verification-needed-xenial

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

Title:
  HID: multitouch: Correct ALPS PTP Stick and Touchpad devices ID

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

Bug description:
  [Impact]
  Alps touchpad with ID 0x120A + trackpoint will not be used for mass 
production machines.
  Touchpad 0x120A w/o trackpoint still reports it has a trackpoint, this will 
confuse userspace apps.

  [Fix]
  Reverts commit fcaa4a07d2a4b541e91da7a55d8b3331f96d1865, so 0x120A device is 
no longer a MT_CLS_WIN_8_DUAL device.

  [Test Case]
  Verified on the systems affected with this issue and confirmed that this 
solution works.

  [Regression Potential]
  Minimal.
  This patch is for a single device in a specific driver.

  This bug is used for tracking purposes, please do not triage.

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

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

[Kleber Sacilotto de Souza]

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

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

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


** Tags added: verification-needed-xenial

** Tags added: verification-needed-zesty

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

Title:
  usb 3-1: 2:1: cannot get freq at ep 0x1

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

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.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   caravena   1838 F...m pulseaudio
   /dev/snd/controlC1:  caravena   1838 F pulseaudio
   /dev/snd/controlC0:  caravena   1838 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-13 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-16-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-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/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: 

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

[Kleber Sacilotto de Souza]

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

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

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

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

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

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

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 1708499] Re: usb 3-1: 2:1: cannot get freq at ep 0x1

[Kleber Sacilotto de Souza]

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

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

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


** Tags added: verification-needed-artful

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

Title:
  usb 3-1: 2:1: cannot get freq at ep 0x1

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

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.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   caravena   1838 F...m pulseaudio
   /dev/snd/controlC1:  caravena   1838 F pulseaudio
   /dev/snd/controlC0:  caravena   1838 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-13 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-16-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-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/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: 

[Kernel-packages] [Bug 1708499] Re: usb 3-1: 2:1: cannot get freq at ep 0x1

[Kleber Sacilotto de Souza]

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

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

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

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

Title:
  usb 3-1: 2:1: cannot get freq at ep 0x1

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

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.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   caravena   1838 F...m pulseaudio
   /dev/snd/controlC1:  caravena   1838 F pulseaudio
   /dev/snd/controlC0:  caravena   1838 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-13 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-16-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-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/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: 

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

[mihai]

It solves the problem 99%, in a sense that i still see the error once /
day, but it's not that bad, it doesn't crash every 10 minutes.

-- 
You 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
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  New
Status in linux source package in Artful:
  Fix Committed

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 1422190] Re: phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush

[Alexandros Prekates]

I have the same problem in 
Ubuntu 16.04
4.4.0-34-generic 
Realtek RT2561/RT61 rev B 802.11g driver: rt61pci

I dont know it's a kernel issue only but testing in another distro with 
4.4.13 it'ok.

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

Title:
  phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Log files continually fill up with following error messages every couple of 
seconds, then the wifi fails until reboot :-
  Feb 16 08:33:25 pio kernel: [  261.084034] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Feb 16 08:33:29 pio kernel: [  265.088066] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Feb 16 08:33:31 pio kernel: [  267.096046] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Feb 16 08:33:34 pio kernel: [  270.092043] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Feb 16 08:33:38 pio kernel: [  274.084033] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Feb 16 08:33:39 pio kernel: [  275.092034] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Feb 16 08:33:41 pio kernel: [  277.084036] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Feb 16 08:33:47 pio kernel: [  283.088039] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-45-generic 3.13.0-45.74
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kit284 2791 F pulseaudio
   /dev/snd/controlC2:  kit284 2791 F pulseaudio
  Date: Mon Feb 16 08:47:30 2015
  HibernationDevice: RESUME=UUID=8bc3362d-e136-453f-bb6c-284013a5dd11
  InstallationDate: Installed on 2014-10-01 (137 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: CLEVO D900K
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=7f8ca46f-0efa-4971-b7fc-9b787d5b660f ro quiet splash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-45-generic N/A
   linux-backports-modules-3.13.0-45-generic  N/A
   linux-firmware 1.127.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2005
  dmi.bios.vendor: Phoenix
  dmi.bios.version: 4.06CJ15
  dmi.board.name: D900K
  dmi.board.vendor: CLEVO
  dmi.board.version: VT8341B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvr4.06CJ15:bd12/06/2005:svnCLEVO:pnD900K:pvrVT8341B:rvnCLEVO:rnD900K:rvrVT8341B:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: D900K
  dmi.product.version: VT8341B
  dmi.sys.vendor: CLEVO

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

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

[Kernel-packages] [Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react

[Jeppe Bundsgaard]

I booted into Ubuntu with kernel 4.10.0-37 (the one I used in 17.04), and that 
made my mouse work. 
I had problems with my trackpad as well, and that was solved with the downgrade 
as well. Maybe the two problems are connected? 
See https://bugs.launchpad.net/bugs/1729391

But strangely enough, the keyboard still acts strangely.

sudo evtest, choosing keyboard, gives
Testing ... (interrupt to exit)
Waits for some time, and then from time to time gives:
Event: time 1510147826.272174, >> SYN_DROPPED 
Event: time 1510147826.272174, -- SYN_REPORT 
Event: time 1510147826.272183, type 2 (EV_REL), code 0 (REL_X), value 59
Event: time 1510147826.272183, type 2 (EV_REL), code 1 (REL_Y), value -7
Event: time 1510147826.272183, -- SYN_REPORT 
Event: time 1510147990.111070, type 2 (EV_REL), code 0 (REL_X), value -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/1729389

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5664 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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

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

[Charles]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1730958/+attachment/5005911/+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/1730958

Title:
  nuvoton-cir not working after boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Current setup/failing setup:
  Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu 4.13.0-17.20-generic 4.13.8
  Ubuntu 17.10, 4.13.0-17-generic
  Nuvoton w836x7hg Infrared Remote Transceiver
  Zotac ID42

  Working setup:
  Ubuntu 17.10, 4.4.8-040408-generic

  I'm not able to get the remote working after a normal reboot (using 4.13 
kernel)
  It does actually after a suspend and wake-up, and do a echo 'auto' to 
resources.

  Please find snapshot of dmesg below:

  [   14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input7
  [   14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   14.468526] nuvoton-cir 00:0a: driver has been successfully loaded

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [   66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input13
  [   66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   66.232240] nuvoton-cir 00:0a: driver has been successfully loaded

   suspend/resume

  [  105.890769] nuvoton-cir 00:0a: disabled
  [  106.651982] nuvoton-cir 00:0a: activated

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [  138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [  138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [  138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input17
  [  138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [  138.552256] nuvoton-cir 00:0a: driver has been successfully loaded

  In order to get the device working I need the following in this order:
  * suspend/resume
  * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6
  InstallationDate: Installed on 2014-04-01 (1317 days ago)
  InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 
(20130820)
  MachineType: ZOTAC ZBOX-ID42-BE
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago)
  UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev 
sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B201P010
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID42-BE
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 3
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA:
  dmi.product.family: NA
  dmi.product.name: ZBOX-ID42-BE
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

[Kernel-packages] [Bug 1724912] Re: TSC_DEADLINE incorrectly disabled inside virtual guests

[Dan Streetman]

Previous kernel version:

ubuntu@ip-172-31-9-93:~$ uname -a
Linux ip-172-31-9-93 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
ubuntu@ip-172-31-9-93:~$ dmesg|grep TSC
[ 0.00] tsc: Fast TSC calibration using PIT
[ 0.00] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update 
microcode to version: 0x214 (or later)

-proposed kernel version:

ubuntu@ip-172-31-9-93:~$ uname -a
Linux ip-172-31-9-93 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
ubuntu@ip-172-31-9-93:~$ dmesg|grep TSC
[ 0.00] tsc: Fast TSC calibration using PIT
[ 0.071013] TSC deadline timer enabled


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

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

Title:
  TSC_DEADLINE incorrectly disabled inside virtual guests

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  An upstream commit added Intel cpu model/microcode checks to disable
  TSC_DEADLINE due to cpu errata:

  commit bd9240a18edfbfa72e957fc2ba831cf1f13ea073
  Author: Peter Zijlstra 
  Date: Wed May 31 17:52:03 2017 +0200

  x86/apic: Add TSC_DEADLINE quirk due to errata

  That commit is included in the Ubuntu kernels starting at artful
  v4.13.

  However, most hypervisors virtualize TSC deadline timer (and therefore
  it isn't affected by Intel CPU errata inside the guest), and even if
  any hypervisors directly exposed the hardware TSC deadline timer, the
  guests cannot update CPU microcode and therefore it's the hypervisor's
  job to disable/hide/virtualize the TSC deadline timer from the guest.

  This upstream commit skips the microcode check to disable the TSC
  deadline timer if it detects it's running under a hypervisor:

  commit cc6afe2240298049585e86b1ade85efc8a7f225d
  Author: Paolo Bonzini 
  Date:   Tue Oct 10 12:12:57 2017 +0200

  x86/apic: Silence "FW_BUG TSC_DEADLINE disabled due to Errata" on
  hypervisors

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

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

[Kernel-packages] [Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react

[Jeppe Bundsgaard]

Just installed and loaded into 4.11.0, and now both mouse and keyboard
works. The bug is introduced later than 4.11.0, then.

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5664 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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

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

[Charles]

apport information

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

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

Title:
  nuvoton-cir not working after boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Current setup/failing setup:
  Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu 4.13.0-17.20-generic 4.13.8
  Ubuntu 17.10, 4.13.0-17-generic
  Nuvoton w836x7hg Infrared Remote Transceiver
  Zotac ID42

  Working setup:
  Ubuntu 17.10, 4.4.8-040408-generic

  I'm not able to get the remote working after a normal reboot (using 4.13 
kernel)
  It does actually after a suspend and wake-up, and do a echo 'auto' to 
resources.

  Please find snapshot of dmesg below:

  [   14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input7
  [   14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   14.468526] nuvoton-cir 00:0a: driver has been successfully loaded

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [   66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input13
  [   66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   66.232240] nuvoton-cir 00:0a: driver has been successfully loaded

   suspend/resume

  [  105.890769] nuvoton-cir 00:0a: disabled
  [  106.651982] nuvoton-cir 00:0a: activated

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [  138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [  138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [  138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input17
  [  138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [  138.552256] nuvoton-cir 00:0a: driver has been successfully loaded

  In order to get the device working I need the following in this order:
  * suspend/resume
  * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6
  InstallationDate: Installed on 2014-04-01 (1317 days ago)
  InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 
(20130820)
  MachineType: ZOTAC ZBOX-ID42-BE
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago)
  UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev 
sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B201P010
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID42-BE
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 3
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA:
  dmi.product.family: NA
  dmi.product.name: 

[Kernel-packages] [Bug 1730958] Re: nuvoton-cir not working after boot

[Ubuntu Kernel Bot]

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

Title:
  nuvoton-cir not working after boot

Status in linux package in Ubuntu:
  New

Bug description:
  Current setup/failing setup:
  Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu 4.13.0-17.20-generic 4.13.8
  Ubuntu 17.10, 4.13.0-17-generic
  Nuvoton w836x7hg Infrared Remote Transceiver
  Zotac ID42

  Working setup:
  Ubuntu 17.10, 4.4.8-040408-generic

  I'm not able to get the remote working after a normal reboot (using 4.13 
kernel)
  It does actually after a suspend and wake-up, and do a echo 'auto' to 
resources.

  Please find snapshot of dmesg below:

  [   14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input7
  [   14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   14.468526] nuvoton-cir 00:0a: driver has been successfully loaded

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [   66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input13
  [   66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   66.232240] nuvoton-cir 00:0a: driver has been successfully loaded

   suspend/resume

  [  105.890769] nuvoton-cir 00:0a: disabled
  [  106.651982] nuvoton-cir 00:0a: activated

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [  138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [  138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [  138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input17
  [  138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [  138.552256] nuvoton-cir 00:0a: driver has been successfully loaded

  In order to get the device working I need the following in this order:
  * suspend/resume
  * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources

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

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

[Kernel-packages] [Bug 1722702] Re: libvirt - vnc port selection regression with newer kernels

[ChristianEhrhardt]

Test from [2] in c #8.


4.13.0-16-generic
gcc bind-collision.c && ./a.out
bind: Address already in use
AF_INET check failed.
$ gcc -D CHECK_IPV6 bind-collision.c && ./a.out
AF_INET6 success
AF_INET success
$ gcc bind-collision.c && ./a.out
AF_INET success

>From proposed:
4.13.0-17-generic
$ gcc bind-collision.c && ./a.out
AF_INET success

=> verified

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

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

Title:
  libvirt - vnc port selection regression with newer kernels

Status in libvirt package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed
Status in libvirt source package in Artful:
  Confirmed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  SRU Justification:

  Impact: Bug appears in linux-image-4.11.x kernels on 16.04.3.
  4.8.x and 4.10.x are okay.

  When libvirtd is restarted on Kernel 4.11.0-x-generic or above , it
  loses all information regarding existing port bindings and is unable
  to correctly re-identify vnc ports that currently in use. libvirt
  attempts to bind to an existing port and fails.

  instance-000a6096.log:2017-10-09T01:42:16.017220Z
  qemu-system-x86_64: -vnc 0.0.0.0:0: Failed to start VNC server: Failed to 
listen on socket: Address already in use

  Fairly certain this is the same bug reported, and patched in
  kernel-4.13.4-200.fc26 for Fedora
  https://bugzilla.redhat.com/show_bug.cgi?id=1432684

  Fix: Cherry picking a set of 3 patches (merged as the same set by
  David Miller) from upstream Linux.

  Testcase: Restart of libvirt.

  Risk for Regressions: Looking at the changes those 3 patches
  introduce, the delta is minimal and makes sense with respect to the
  explanations given in the commit message. Overall risk should be low.

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

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

[Kernel-packages] [Bug 1730550] Re: e1000e in 4.4.0-97-generic breaks 82574L under heavy load.

[Joseph Salisbury]

Yes, I was trying to see if just one commit fixed the bug.  It's always
best to introduce the least number of commits to fix a bug in a stable
release.

I'll build another test kernel with the other commit as well and post it
shortly.

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

Title:
  e1000e in 4.4.0-97-generic breaks 82574L under heavy load.

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

Bug description:
  This issue was first reported on the netdev email list by Lennart Sorensen:
  https://www.mail-archive.com/netdev@vger.kernel.org/msg178170.html

  Commit 16ecba59bc333d6282ee057fb02339f77a880beb causes link drops on
  the 82574L under heavy load.

  "Unfortunately this commit changed the driver to assume
  that the Other Causes interrupt can only mean link state change and
  hence sets the flag that (unfortunately) means both link is down and link
  state should be checked.  Since this now happens 3000 times per second,
  the chances of it happening while the watchdog_task is checking the link
  state becomes pretty high, and it if does happen to coincice, then the
  watchdog_task will reset the adapter, which causes a real loss of link."

  A fix for this issue was accepted into the net-next branch, along with
  other e1000e/igb patches:
  https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-
  next.git/commit/?id=f44dea3421b47d355a835e9cfcc59ca7318575a9

  The original reported experienced this issue on a Supermicro X7SPA-
  HF-D525 server board. We see this issue on many servers running X9DBL-
  1F server boards. Both boards use the Intel 82574L for the network
  interfaces.  We see messages like this under heavy load:

  [Nov 6 15:42] e1000e: eth0 NIC Link is Down
  [  +0.001670] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [Nov 6 16:10] e1000e: eth0 NIC Link is Down
  [  +0.008505] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [Nov 7 00:49] e1000e: eth0 NIC Link is Down
  [  +2.235111] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx

  We have confirmed that the connected switch sees the link drops also,
  to these are not false alarms from the e1000e driver.

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

  I could not cleanly apply the net-next patch to 4.4.0 so I tested with just 
the following cherry picked changes on the latest 4.4.0 kernel source package.
  https://patchwork.ozlabs.org/patch/823942/
  https://patchwork.ozlabs.org/patch/823945/
  https://patchwork.ozlabs.org/patch/823940/
  https://patchwork.ozlabs.org/patch/823941/
  https://patchwork.ozlabs.org/patch/823939/

  Although it's my understanding the first two are the critical ones for
  the race condition. I have been running with the patches e1000e kernel
  driver, under network load for 7 days and I no longer see the network
  interface drops.

  Could we pull these changes into the Ubuntu 4.4.0 kernel ?

  Thanks
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 19 07:34 seq
   crw-rw 1 root audio 116, 33 Jul 19 07:34 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=49ca52b8-cf08-4485-b296-0dffb098e557
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Supermicro X9DBL-3F/X9DBL-iF
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 
root=UUID=957d7126-5452-4606-942d-1d58adbeb253 ro net.ifnames=0 biosdevname=0 
quiet splash nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-83-generic N/A
   linux-backports-modules-4.4.0-83-generic  N/A
   linux-firmware1.157.11
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-83-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to xenial on 2016-12-05 (337 days ago)
  

[Kernel-packages] [Bug 1730970] [NEW] TouchPad Stopped Working

[James]

Public bug reported:

Release:
  Description: Ubuntu 16.04.3 LTS
  Release: 16.04
  version_signature: Ubuntu 4.4.0-98.121-generic 4.4.90

Issue: |
  I recently did and update (sudo apt-get update / sudo apt-get upgrade).  A 
few days later I did a 
  reboot and my touchpad stopped working.  The touchpad does not appear to show 
in devices (cat 
  /proc/bus/input/devices), but my external usb mouse does.  Perhaps a recent 
update in the kernel
  has caused this issue.

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


** Tags: touchpad xenial

** Attachment added: "dmesg"
   https://bugs.launchpad.net/bugs/1730970/+attachment/5005897/+files/dmesg

** Tags added: touchpad

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

Title:
  TouchPad Stopped Working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Release:
Description: Ubuntu 16.04.3 LTS
Release: 16.04
version_signature: Ubuntu 4.4.0-98.121-generic 4.4.90

  Issue: |
I recently did and update (sudo apt-get update / sudo apt-get upgrade).  A 
few days later I did a 
reboot and my touchpad stopped working.  The touchpad does not appear to 
show in devices (cat 
/proc/bus/input/devices), but my external usb mouse does.  Perhaps a recent 
update in the kernel
has caused this issue.

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

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

[Kernel-packages] [Bug 1727662] Re: [Lenovo ThinkPad T450s] Issues after docking and locking: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

[Christopher M. Penalver]

Alexander Kops, to advise, if you can't reproduce in drm-tip, still
report it as per their instructions as it's reproducible in mainline
(i.e. upstream 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/1727662

Title:
  [Lenovo ThinkPad T450s] Issues after docking and locking:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

Status in linux package in Ubuntu:
  Triaged

Bug description:
  What happens is after I dock my laptop into a Lenovo ThinkPad Ultra Dock Type 
40A2 20V, lock it via clicking the lock icon, and wait ~30 minutes, one of the 
following three things happen ~50% of the time when I come back to unlock it:
  * Most of the time the computer is found shut down.
  * Sometimes the notebook screen flickers weirdly and one of the two external 
monitors show pixelation.
  * The notebook screen shows the lock screen but is completely frozen. 
Occasionally unlocking works.

  I have two external monitors attached to the docking station.

  When I dock my laptop, the battery indicator does recognize its
  charging.

  I've not seen this issue when:
  1) With the laptop in the dock, while actively using the laptop.
  2) With the laptop out of the dock and no external monitors present.

  This bug started after upgrading from Ubtuntu 17.04 to Ubuntu 17.10.

  Using or not using the following kernel parameter didn't change anything:
  i915.enable_rc6=0

  PC temperatures are normal as per lm-sensors.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  akops  3337 F pulseaudio
   /dev/snd/controlC0:  akops  3337 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:44:11 2017
  HibernationDevice: RESUME=/dev/mapper/system-swap_1
  MachineType: LENOVO 20BWS2YL00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency 
root=/dev/mapper/system-root ro quiet splash i915.enable_rc6=0 
crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-lowlatency N/A
   linux-backports-modules-4.13.0-16-lowlatency  N/A
   linux-firmware1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago)
  dmi.bios.date: 07/08/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET51WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS2YL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BWS2YL00:pvrThinkPadT450s:rvnLENOVO:rn20BWS2YL00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS2YL00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1730550] Re: e1000e in 4.4.0-97-generic breaks 82574L under heavy load.

[Joseph Salisbury]

I built a v2 Xenial test kernel.  This test kernel has both commits
19110cfbb34 and 4aea7a5c5.

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1730550/

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

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

Title:
  e1000e in 4.4.0-97-generic breaks 82574L under heavy load.

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

Bug description:
  This issue was first reported on the netdev email list by Lennart Sorensen:
  https://www.mail-archive.com/netdev@vger.kernel.org/msg178170.html

  Commit 16ecba59bc333d6282ee057fb02339f77a880beb causes link drops on
  the 82574L under heavy load.

  "Unfortunately this commit changed the driver to assume
  that the Other Causes interrupt can only mean link state change and
  hence sets the flag that (unfortunately) means both link is down and link
  state should be checked.  Since this now happens 3000 times per second,
  the chances of it happening while the watchdog_task is checking the link
  state becomes pretty high, and it if does happen to coincice, then the
  watchdog_task will reset the adapter, which causes a real loss of link."

  A fix for this issue was accepted into the net-next branch, along with
  other e1000e/igb patches:
  https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-
  next.git/commit/?id=f44dea3421b47d355a835e9cfcc59ca7318575a9

  The original reported experienced this issue on a Supermicro X7SPA-
  HF-D525 server board. We see this issue on many servers running X9DBL-
  1F server boards. Both boards use the Intel 82574L for the network
  interfaces.  We see messages like this under heavy load:

  [Nov 6 15:42] e1000e: eth0 NIC Link is Down
  [  +0.001670] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [Nov 6 16:10] e1000e: eth0 NIC Link is Down
  [  +0.008505] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [Nov 7 00:49] e1000e: eth0 NIC Link is Down
  [  +2.235111] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx

  We have confirmed that the connected switch sees the link drops also,
  to these are not false alarms from the e1000e driver.

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

  I could not cleanly apply the net-next patch to 4.4.0 so I tested with just 
the following cherry picked changes on the latest 4.4.0 kernel source package.
  https://patchwork.ozlabs.org/patch/823942/
  https://patchwork.ozlabs.org/patch/823945/
  https://patchwork.ozlabs.org/patch/823940/
  https://patchwork.ozlabs.org/patch/823941/
  https://patchwork.ozlabs.org/patch/823939/

  Although it's my understanding the first two are the critical ones for
  the race condition. I have been running with the patches e1000e kernel
  driver, under network load for 7 days and I no longer see the network
  interface drops.

  Could we pull these changes into the Ubuntu 4.4.0 kernel ?

  Thanks
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 19 07:34 seq
   crw-rw 1 root audio 116, 33 Jul 19 07:34 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=49ca52b8-cf08-4485-b296-0dffb098e557
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Supermicro X9DBL-3F/X9DBL-iF
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 
root=UUID=957d7126-5452-4606-942d-1d58adbeb253 ro net.ifnames=0 biosdevname=0 
quiet splash nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-83-generic N/A
   linux-backports-modules-4.4.0-83-generic  N/A
   linux-firmware1.157.11
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-83-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to xenial on 2016-12-05 (337 days 

[Kernel-packages] [Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task

[Joseph Salisbury]

Thanks for the info and the bisect work, Stefan!


I built an Artful test kernel with a revert of commit 909657615d9b.  This test 
kernel can be downloaded from:

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

Can you test that kernel and report back if it has the bug or not?

With this test kernel, you need to install both the linux-image and
linux-image-extra .deb packages.

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

Title:
  Unable to handle kernel NULL pointer dereference at
  isci_task_abort_task

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  So I just upgrade from zesty zapus to artful aardvark. At boot, right
  after I enter my drive encryption password, it kernel panics with the
  above message.

  It doesn't even get far enough along in the boot process for syslog to
  log this panic, so the only info I have is a photo of the panic.

  In short, I can't boot using the latest artful aardvark kernel, and I
  have to boot with the latest zesty zapus kernel.

  :~$ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  linux-image-4.13.0-16-generic

  I expect this isn't normal and I should be able to boot with the new
  kernel, which I can't.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lost   2071 F pulseaudio
   /dev/snd/controlC2:  lost   2071 F pulseaudio
   /dev/snd/controlC0:  lost   2071 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct 23 12:52:20 2017
  HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6
  InstallationDate: Installed on 2016-11-01 (355 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 11361Q0
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.169
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago)
  dmi.bios.date: 09/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A3KT57AUS
  dmi.board.name: LENOVO
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: 573921
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE:
  dmi.product.name: 11361Q0
  dmi.product.version: ThinkStation C30
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1724612] Re: x86/apic: Update TSC_DEADLINE quirk with additional SKX stepping

[Dan Streetman]

Previous kernel version:

ubuntu@ip-172-31-9-93:~$ uname -a
Linux ip-172-31-9-93 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
ubuntu@ip-172-31-9-93:~$ dmesg|grep TSC
[0.00] tsc: Fast TSC calibration using PIT
[0.00] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please 
update microcode to version: 0x214 (or later)


-proposed kernel version:

ubuntu@ip-172-31-9-93:~$ uname -a
Linux ip-172-31-9-93 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
ubuntu@ip-172-31-9-93:~$ dmesg|grep TSC
[0.00] tsc: Fast TSC calibration using PIT
[0.071013] TSC deadline timer enabled


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

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

Title:
  x86/apic: Update TSC_DEADLINE quirk with additional SKX stepping

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

Bug description:
  An upstream commit added Intel cpu model/microcode checks to disable
  TSC_DEADLINE due to cpu errata:

  commit bd9240a18edfbfa72e957fc2ba831cf1f13ea073
  Author: Peter Zijlstra 
  Date:   Wed May 31 17:52:03 2017 +0200

  x86/apic: Add TSC_DEADLINE quirk due to errata

  
  That commit is included in the Ubuntu kernels starting at artful v4.13.  
However, the commit includes a check for Skylake Xeons, but the microcode 
update version number differs based on Skylake Xeon stepping, so an additional 
commit is required to correctly check the microcode level of both stepping 3 
and stepping 4 Skylake Xeons, and disable/enable TSC_DEADLINE appropriately.

  Upstream commit that corrects the check is:

  commit 616dd5872e52493863b0202632703eebd51243dc
  Author: Len Brown 
  Date:   Wed Oct 11 17:16:04 2017 -0400

  x86/apic: Update TSC_DEADLINE quirk with additional SKX stepping

  
  Without the additional commit, Skylake Xeon stepping-3 cpus with the fixed 
microcode version will incorrectly have their TSC_DEADLINE disabled.

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

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

[Kernel-packages] [Bug 1730958] Re: nuvoton-cir not working after boot

[Charles]

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

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

Title:
  nuvoton-cir not working after boot

Status in linux package in Ubuntu:
  New

Bug description:
  Current setup/failing setup:
  Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu 4.13.0-17.20-generic 4.13.8
  Ubuntu 17.10, 4.13.0-17-generic
  Nuvoton w836x7hg Infrared Remote Transceiver
  Zotac ID42

  Working setup:
  Ubuntu 17.10, 4.4.8-040408-generic

  I'm not able to get the remote working after a normal reboot (using 4.13 
kernel)
  It does actually after a suspend and wake-up, and do a echo 'auto' to 
resources.

  Please find snapshot of dmesg below:

  [   14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input7
  [   14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   14.468526] nuvoton-cir 00:0a: driver has been successfully loaded

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [   66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input13
  [   66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   66.232240] nuvoton-cir 00:0a: driver has been successfully loaded

   suspend/resume

  [  105.890769] nuvoton-cir 00:0a: disabled
  [  106.651982] nuvoton-cir 00:0a: activated

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [  138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [  138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [  138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input17
  [  138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [  138.552256] nuvoton-cir 00:0a: driver has been successfully loaded

  In order to get the device working I need the following in this order:
  * suspend/resume
  * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources

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

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

[Kernel-packages] [Bug 1730958] [NEW] nuvoton-cir not working after boot

[Charles]

Public bug reported:

Current setup/failing setup:
Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
Ubuntu 4.13.0-17.20-generic 4.13.8
Ubuntu 17.10, 4.13.0-17-generic
Nuvoton w836x7hg Infrared Remote Transceiver
Zotac ID42

Working setup:
Ubuntu 17.10, 4.4.8-040408-generic

I'm not able to get the remote working after a normal reboot (using 4.13 kernel)
It does actually after a suspend and wake-up, and do a echo 'auto' to resources.

Please find snapshot of dmesg below:

[   14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
[   14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
[   14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input7
[   14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered 
at minor = 0
[   14.468526] nuvoton-cir 00:0a: driver has been successfully loaded


modprobe -r nuvoton-cir
echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
modprobe nuvoton-cir


[   66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
[   66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
[   66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input13
[   66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered 
at minor = 0
[   66.232240] nuvoton-cir 00:0a: driver has been successfully loaded

 suspend/resume

[  105.890769] nuvoton-cir 00:0a: disabled
[  106.651982] nuvoton-cir 00:0a: activated


modprobe -r nuvoton-cir
echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
modprobe nuvoton-cir


[  138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
[  138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
[  138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input17
[  138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered 
at minor = 0
[  138.552256] nuvoton-cir 00:0a: driver has been successfully loaded

In order to get the device working I need the following in this order:
* suspend/resume
* echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources

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

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

Title:
  nuvoton-cir not working after boot

Status in linux package in Ubuntu:
  New

Bug description:
  Current setup/failing setup:
  Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu 4.13.0-17.20-generic 4.13.8
  Ubuntu 17.10, 4.13.0-17-generic
  Nuvoton w836x7hg Infrared Remote Transceiver
  Zotac ID42

  Working setup:
  Ubuntu 17.10, 4.4.8-040408-generic

  I'm not able to get the remote working after a normal reboot (using 4.13 
kernel)
  It does actually after a suspend and wake-up, and do a echo 'auto' to 
resources.

  Please find snapshot of dmesg below:

  [   14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input7
  [   14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   14.468526] nuvoton-cir 00:0a: driver has been successfully loaded

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [   66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input13
  [   66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   66.232240] nuvoton-cir 00:0a: driver has been successfully loaded

   suspend/resume

  [  105.890769] nuvoton-cir 00:0a: disabled
  [  106.651982] nuvoton-cir 00:0a: activated

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [  138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [  138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [  138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input17
  [  138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [  138.552256] 

[Kernel-packages] [Bug 1730596] Re: s390/mm: fix write access check in gup_huge_pmd()

[Frank Heimes]

** Changed in: ubuntu-z-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/1730596

Title:
  s390/mm: fix write access check in gup_huge_pmd()

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  The check for the _SEGMENT_ENTRY_PROTECT bit in gup_huge_pmd() is the
  wrong way around. It must not be set for write==1, and not be checked for
  write==0. Fix this similar to how it was fixed for ptes long time ago in
  commit 25591b0 ("[S390] fix get_user_pages_fast").

  One impact of this bug would be unnecessarily using the gup slow path for
  write==0 on r/w mappings. A potentially more severe impact would be that
  gup_huge_pmd() will succeed for write==1 on r/o mappings.

  Addl information

  Problem: The check for the _SEGMENT_ENTRY_PROTECT bit in
gup_huge_pmd() is the wrong way around. It must not be set
for write==1, and not be checked for write==0. Allowing
write==1 with protection bit set, instead of breaking out
to the slow path, will result in a missing faultin_page()
to clear the protection bit (for valid writable mappings),
and the async I/O write operation will fail to write to
such a mapping.
  Solution: Fix it by correctly checking the protection bit like it is
also done in gup_pte_range() and gup_huge_pud().
  Reproduction: Async I/O workload on buffers that are mapped as transparent
hugepages.
  Upstream-ID:  ba385c0594e723d41790ecfb12c610e6f90c7785

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

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

[Kernel-packages] [Bug 1730596] Re: s390/mm: fix write access check in gup_huge_pmd()

[Joseph Salisbury]

I built Xenial, Zesty and Artful test kernels with commit
ba385c0594e723d.  The test kernels can be downloaded from:


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

Can you test these kernels to see if they resolve this bug?  If they do,
I'll submit an SRU request.

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

** Also affects: linux (Ubuntu Bionic)
   Importance: Critical
 Assignee: Skipper Bug Screeners (skipper-screen-team)
   Status: Triaged

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

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

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

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

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

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

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

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => Joseph Salisbury 
(jsalisbury)

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Zesty)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  s390/mm: fix write access check in gup_huge_pmd()

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  The check for the _SEGMENT_ENTRY_PROTECT bit in gup_huge_pmd() is the
  wrong way around. It must not be set for write==1, and not be checked for
  write==0. Fix this similar to how it was fixed for ptes long time ago in
  commit 25591b0 ("[S390] fix get_user_pages_fast").

  One impact of this bug would be unnecessarily using the gup slow path for
  write==0 on r/w mappings. A potentially more severe impact would be that
  gup_huge_pmd() will succeed for write==1 on r/o mappings.

  Addl information

  Problem: The check for the _SEGMENT_ENTRY_PROTECT bit in
gup_huge_pmd() is the wrong way around. It must not be set
for write==1, and not be checked for write==0. Allowing
write==1 with protection bit set, instead of breaking out
to the slow path, will result in a missing faultin_page()
to clear the protection bit (for valid writable mappings),
and the async I/O write operation will fail to write to
such a mapping.
  Solution: Fix it by correctly checking the protection bit like it is
also done in gup_pte_range() and gup_huge_pud().
  Reproduction: Async I/O workload on buffers that are mapped as transparent
hugepages.
  Upstream-ID:  ba385c0594e723d41790ecfb12c610e6f90c7785

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

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

[Kernel-packages] [Bug 1730926] Re: lxc-test-unpriv test failed on s390x instances

[Joseph Salisbury]

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

** Tags added: kernel-da-key

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

Title:
  lxc-test-unpriv test failed on s390x instances

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a POTENTIAL REGRESSION.

  This test has passed with older kernels (4.4.0-98, 4.4.0-97, 4.4.0-96), but 
this time it failed.
  Issue can be seen on zKVM, zVM and Ubuntu on LPAR

  Steps:
  1. Install lxc-tests
  2. Run sudo /usr/bin/lxc-test-unpriv

  Result:
---
mount: wrong fs type, bad option, bad superblock on none,
   missing codepage or helper program, or other error

   In some cases useful info is found in syslog - try
   dmesg | tail or so.
umount: /tmp/tmp.uMnoGYXJSH/ovl_symlink_test/overlayfs: not mounted
/usr/sbin/deluser: The user `lxcunpriv' does not exist.
Path existed
Using image from local cache
Unpacking the rootfs

---
You just created an Ubuntu container (release=xenial, arch=s390x, 
variant=default)

To enable sshd, run: apt-get install openssh-server

For security reason, container images ship without user accounts
and without a root password.

Use lxc-attach or chroot directly into the rootfs to set a root password
or create user accounts.
Name:   c1
State:  RUNNING
PID:5846
CPU use:0.05 seconds
BlkIO use:  0 bytes
Memory use: 10.04 MiB
KMem use:   0 bytes
Link:   vethV2EVRI
 TX bytes:  0 bytes
 RX bytes:  0 bytes
 Total bytes:   0 bytes
Name:   c1
State:  RUNNING
PID:6218
CPU use:0.03 seconds
BlkIO use:  0 bytes
Memory use: 1.50 MiB
KMem use:   0 bytes
Link:   vethA54DMR
 TX bytes:  0 bytes
 RX bytes:  0 bytes
 Total bytes:   0 bytes
Testing containers under different cgroups per subsystem
call to cgmanager_move_pid_main_sync failed: invalid request
c2 is not running
c1 is not running
Removing user `lxcunpriv' ...
Warning: group `lxcunpriv' has no more members.
Done.
FAIL
---

  The mount error (bug 1730915) is not the cause, it looks like the failure was 
caused by:
call to cgmanager_move_pid_main_sync failed: invalid request

  In that shell script, this line account for the error:
  cgm movepid freezer x1 $$

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-100-generic 4.4.0-100.123
  ProcVersionSignature: Ubuntu 4.4.0-100.123-generic 4.4.95
  Uname: Linux 4.4.0-100-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Wed Nov  8 04:39:12 2017
  HibernationDevice: RESUME=UUID=ca468a9c-9563-442c-85c6-6055e800a66e
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=b65b756a-ba4e-4c53-aa32-0db2bdb50bb3 
crashkernel=196M
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-100-generic N/A
   linux-backports-modules-4.4.0-100-generic  N/A
   linux-firmware 1.157.13
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[mihai]

oops, ignore my last comment, i did not enable propose, i am upgrading
now to 4.10.0-39, and will let you know.

-- 
You 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
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  New
Status in linux source package in Artful:
  Fix Committed

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 1730970] Missing required logs.

[Ubuntu Kernel Bot]

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

apport-collect 1730970

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

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

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

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

** Tags added: 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/1730970

Title:
  TouchPad Stopped Working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Release:
Description: Ubuntu 16.04.3 LTS
Release: 16.04
version_signature: Ubuntu 4.4.0-98.121-generic 4.4.90

  Issue: |
I recently did and update (sudo apt-get update / sudo apt-get upgrade).  A 
few days later I did a 
reboot and my touchpad stopped working.  The touchpad does not appear to 
show in devices (cat 
/proc/bus/input/devices), but my external usb mouse does.  Perhaps a recent 
update in the kernel
has caused this issue.

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

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

[Kernel-packages] [Bug 1730596] Re: s390/mm: fix write access check in gup_huge_pmd()

[Frank Heimes]

raising the importance to critical (after discussing with IBM)

** Changed in: ubuntu-z-systems
   Importance: High => Critical

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

Title:
  s390/mm: fix write access check in gup_huge_pmd()

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

Bug description:
  The check for the _SEGMENT_ENTRY_PROTECT bit in gup_huge_pmd() is the
  wrong way around. It must not be set for write==1, and not be checked for
  write==0. Fix this similar to how it was fixed for ptes long time ago in
  commit 25591b0 ("[S390] fix get_user_pages_fast").

  One impact of this bug would be unnecessarily using the gup slow path for
  write==0 on r/w mappings. A potentially more severe impact would be that
  gup_huge_pmd() will succeed for write==1 on r/o mappings.

  Addl information

  Problem: The check for the _SEGMENT_ENTRY_PROTECT bit in
gup_huge_pmd() is the wrong way around. It must not be set
for write==1, and not be checked for write==0. Allowing
write==1 with protection bit set, instead of breaking out
to the slow path, will result in a missing faultin_page()
to clear the protection bit (for valid writable mappings),
and the async I/O write operation will fail to write to
such a mapping.
  Solution: Fix it by correctly checking the protection bit like it is
also done in gup_pte_range() and gup_huge_pud().
  Reproduction: Async I/O workload on buffers that are mapped as transparent
hugepages.
  Upstream-ID:  ba385c0594e723d41790ecfb12c610e6f90c7785

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1730958

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

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

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

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

** Tags added: artful

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

Title:
  nuvoton-cir not working after boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Current setup/failing setup:
  Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu 4.13.0-17.20-generic 4.13.8
  Ubuntu 17.10, 4.13.0-17-generic
  Nuvoton w836x7hg Infrared Remote Transceiver
  Zotac ID42

  Working setup:
  Ubuntu 17.10, 4.4.8-040408-generic

  I'm not able to get the remote working after a normal reboot (using 4.13 
kernel)
  It does actually after a suspend and wake-up, and do a echo 'auto' to 
resources.

  Please find snapshot of dmesg below:

  [   14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input7
  [   14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   14.468526] nuvoton-cir 00:0a: driver has been successfully loaded

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [   66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input13
  [   66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   66.232240] nuvoton-cir 00:0a: driver has been successfully loaded

   suspend/resume

  [  105.890769] nuvoton-cir 00:0a: disabled
  [  106.651982] nuvoton-cir 00:0a: activated

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [  138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [  138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [  138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input17
  [  138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [  138.552256] nuvoton-cir 00:0a: driver has been successfully loaded

  In order to get the device working I need the following in this order:
  * suspend/resume
  * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources

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

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

[Kernel-packages] [Bug 1730970] Re: TouchPad Stopped Working

[James]

devices output

** Attachment added: "devices"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730970/+attachment/5005898/+files/devices

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

Title:
  TouchPad Stopped Working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Release:
Description: Ubuntu 16.04.3 LTS
Release: 16.04
version_signature: Ubuntu 4.4.0-98.121-generic 4.4.90

  Issue: |
I recently did and update (sudo apt-get update / sudo apt-get upgrade).  A 
few days later I did a 
reboot and my touchpad stopped working.  The touchpad does not appear to 
show in devices (cat 
/proc/bus/input/devices), but my external usb mouse does.  Perhaps a recent 
update in the kernel
has caused this issue.

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

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

[Kernel-packages] [Bug 1729391] Re: Trackpad stops responding after suspend

[Jeppe Bundsgaard]

I installed 4.11.0, and the problem re-appears. So the bug was
introduced between 4.10.0-37 and 4.11.0.

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

Title:
  Trackpad stops responding after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, the trackpad
  stops working after suspend (it actually works for a few seconds, then
  doesn't react). I can still use the touch screen.

  Please tell me which log-files to upload.

  Thanks

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

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

[Kernel-packages] [Bug 1730958] RfKill.txt

[Charles]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1730958/+attachment/5005913/+files/RfKill.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/1730958

Title:
  nuvoton-cir not working after boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Current setup/failing setup:
  Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu 4.13.0-17.20-generic 4.13.8
  Ubuntu 17.10, 4.13.0-17-generic
  Nuvoton w836x7hg Infrared Remote Transceiver
  Zotac ID42

  Working setup:
  Ubuntu 17.10, 4.4.8-040408-generic

  I'm not able to get the remote working after a normal reboot (using 4.13 
kernel)
  It does actually after a suspend and wake-up, and do a echo 'auto' to 
resources.

  Please find snapshot of dmesg below:

  [   14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input7
  [   14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   14.468526] nuvoton-cir 00:0a: driver has been successfully loaded

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [   66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input13
  [   66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   66.232240] nuvoton-cir 00:0a: driver has been successfully loaded

   suspend/resume

  [  105.890769] nuvoton-cir 00:0a: disabled
  [  106.651982] nuvoton-cir 00:0a: activated

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [  138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [  138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [  138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input17
  [  138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [  138.552256] nuvoton-cir 00:0a: driver has been successfully loaded

  In order to get the device working I need the following in this order:
  * suspend/resume
  * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6
  InstallationDate: Installed on 2014-04-01 (1317 days ago)
  InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 
(20130820)
  MachineType: ZOTAC ZBOX-ID42-BE
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago)
  UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev 
sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B201P010
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID42-BE
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 3
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA:
  dmi.product.family: NA
  dmi.product.name: ZBOX-ID42-BE
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

To manage 

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

[Charles]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1730958/+attachment/5005914/+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/1730958

Title:
  nuvoton-cir not working after boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Current setup/failing setup:
  Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu 4.13.0-17.20-generic 4.13.8
  Ubuntu 17.10, 4.13.0-17-generic
  Nuvoton w836x7hg Infrared Remote Transceiver
  Zotac ID42

  Working setup:
  Ubuntu 17.10, 4.4.8-040408-generic

  I'm not able to get the remote working after a normal reboot (using 4.13 
kernel)
  It does actually after a suspend and wake-up, and do a echo 'auto' to 
resources.

  Please find snapshot of dmesg below:

  [   14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input7
  [   14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   14.468526] nuvoton-cir 00:0a: driver has been successfully loaded

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [   66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input13
  [   66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   66.232240] nuvoton-cir 00:0a: driver has been successfully loaded

   suspend/resume

  [  105.890769] nuvoton-cir 00:0a: disabled
  [  106.651982] nuvoton-cir 00:0a: activated

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [  138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [  138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [  138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input17
  [  138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [  138.552256] nuvoton-cir 00:0a: driver has been successfully loaded

  In order to get the device working I need the following in this order:
  * suspend/resume
  * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6
  InstallationDate: Installed on 2014-04-01 (1317 days ago)
  InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 
(20130820)
  MachineType: ZOTAC ZBOX-ID42-BE
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago)
  UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev 
sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B201P010
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID42-BE
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 3
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA:
  dmi.product.family: NA
  dmi.product.name: ZBOX-ID42-BE
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

To manage 

[Kernel-packages] [Bug 1730958] Re: nuvoton-cir not working after boot

[Charles]

apport information

** Tags added: apport-collected

** Description changed:

  Current setup/failing setup:
  Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu 4.13.0-17.20-generic 4.13.8
  Ubuntu 17.10, 4.13.0-17-generic
  Nuvoton w836x7hg Infrared Remote Transceiver
  Zotac ID42
  
  Working setup:
  Ubuntu 17.10, 4.4.8-040408-generic
  
  I'm not able to get the remote working after a normal reboot (using 4.13 
kernel)
  It does actually after a suspend and wake-up, and do a echo 'auto' to 
resources.
  
  Please find snapshot of dmesg below:
  
  [   14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input7
  [   14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   14.468526] nuvoton-cir 00:0a: driver has been successfully loaded
  
  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  
  
  [   66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input13
  [   66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   66.232240] nuvoton-cir 00:0a: driver has been successfully loaded
  
   suspend/resume
  
  [  105.890769] nuvoton-cir 00:0a: disabled
  [  106.651982] nuvoton-cir 00:0a: activated
  
  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  
  
  [  138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [  138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [  138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input17
  [  138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [  138.552256] nuvoton-cir 00:0a: driver has been successfully loaded
  
  In order to get the device working I need the following in this order:
  * suspend/resume
  * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3.1
+ Architecture: amd64
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ DistroRelease: Ubuntu 17.10
+ HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6
+ InstallationDate: Installed on 2014-04-01 (1317 days ago)
+ InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 
(20130820)
+ MachineType: ZOTAC ZBOX-ID42-BE
+ NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcFB: 0 VESA VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
+ 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.13.0-17-generic N/A
+  linux-backports-modules-4.13.0-17-generic  N/A
+  linux-firmware 1.169
+ Tags:  artful
+ Uname: Linux 4.13.0-17-generic x86_64
+ UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago)
+ UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev 
sambashare sudo video
+ _MarkForUpload: True
+ dmi.bios.date: 05/03/2013
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: B201P010
+ dmi.board.asset.tag: NA
+ dmi.board.name: ZBOX-ID42-BE
+ dmi.board.vendor: ZOTAC
+ dmi.board.version: XX
+ dmi.chassis.asset.tag: NA
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: NA
+ dmi.chassis.version: NA
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA:
+ dmi.product.family: NA
+ dmi.product.name: ZBOX-ID42-BE
+ dmi.product.version: XX
+ dmi.sys.vendor: ZOTAC

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1730958/+attachment/5005901/+files/AlsaInfo.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/1730958

Title:
  nuvoton-cir not working after 

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

[Charles]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1730958/+attachment/5005902/+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/1730958

Title:
  nuvoton-cir not working after boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Current setup/failing setup:
  Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu 4.13.0-17.20-generic 4.13.8
  Ubuntu 17.10, 4.13.0-17-generic
  Nuvoton w836x7hg Infrared Remote Transceiver
  Zotac ID42

  Working setup:
  Ubuntu 17.10, 4.4.8-040408-generic

  I'm not able to get the remote working after a normal reboot (using 4.13 
kernel)
  It does actually after a suspend and wake-up, and do a echo 'auto' to 
resources.

  Please find snapshot of dmesg below:

  [   14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input7
  [   14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   14.468526] nuvoton-cir 00:0a: driver has been successfully loaded

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [   66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input13
  [   66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   66.232240] nuvoton-cir 00:0a: driver has been successfully loaded

   suspend/resume

  [  105.890769] nuvoton-cir 00:0a: disabled
  [  106.651982] nuvoton-cir 00:0a: activated

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [  138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [  138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [  138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input17
  [  138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [  138.552256] nuvoton-cir 00:0a: driver has been successfully loaded

  In order to get the device working I need the following in this order:
  * suspend/resume
  * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6
  InstallationDate: Installed on 2014-04-01 (1317 days ago)
  InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 
(20130820)
  MachineType: ZOTAC ZBOX-ID42-BE
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago)
  UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev 
sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B201P010
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID42-BE
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 3
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA:
  dmi.product.family: NA
  dmi.product.name: ZBOX-ID42-BE
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

To manage 

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

[Charles]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1730958/+attachment/5005903/+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/1730958

Title:
  nuvoton-cir not working after boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Current setup/failing setup:
  Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu 4.13.0-17.20-generic 4.13.8
  Ubuntu 17.10, 4.13.0-17-generic
  Nuvoton w836x7hg Infrared Remote Transceiver
  Zotac ID42

  Working setup:
  Ubuntu 17.10, 4.4.8-040408-generic

  I'm not able to get the remote working after a normal reboot (using 4.13 
kernel)
  It does actually after a suspend and wake-up, and do a echo 'auto' to 
resources.

  Please find snapshot of dmesg below:

  [   14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input7
  [   14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   14.468526] nuvoton-cir 00:0a: driver has been successfully loaded

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [   66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input13
  [   66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   66.232240] nuvoton-cir 00:0a: driver has been successfully loaded

   suspend/resume

  [  105.890769] nuvoton-cir 00:0a: disabled
  [  106.651982] nuvoton-cir 00:0a: activated

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [  138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [  138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [  138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input17
  [  138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [  138.552256] nuvoton-cir 00:0a: driver has been successfully loaded

  In order to get the device working I need the following in this order:
  * suspend/resume
  * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6
  InstallationDate: Installed on 2014-04-01 (1317 days ago)
  InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 
(20130820)
  MachineType: ZOTAC ZBOX-ID42-BE
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago)
  UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev 
sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B201P010
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID42-BE
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 3
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA:
  dmi.product.family: NA
  dmi.product.name: ZBOX-ID42-BE
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

To 

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

[Charles]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1730958/+attachment/5005906/+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/1730958

Title:
  nuvoton-cir not working after boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Current setup/failing setup:
  Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu 4.13.0-17.20-generic 4.13.8
  Ubuntu 17.10, 4.13.0-17-generic
  Nuvoton w836x7hg Infrared Remote Transceiver
  Zotac ID42

  Working setup:
  Ubuntu 17.10, 4.4.8-040408-generic

  I'm not able to get the remote working after a normal reboot (using 4.13 
kernel)
  It does actually after a suspend and wake-up, and do a echo 'auto' to 
resources.

  Please find snapshot of dmesg below:

  [   14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input7
  [   14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   14.468526] nuvoton-cir 00:0a: driver has been successfully loaded

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [   66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input13
  [   66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   66.232240] nuvoton-cir 00:0a: driver has been successfully loaded

   suspend/resume

  [  105.890769] nuvoton-cir 00:0a: disabled
  [  106.651982] nuvoton-cir 00:0a: activated

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [  138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [  138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [  138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input17
  [  138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [  138.552256] nuvoton-cir 00:0a: driver has been successfully loaded

  In order to get the device working I need the following in this order:
  * suspend/resume
  * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6
  InstallationDate: Installed on 2014-04-01 (1317 days ago)
  InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 
(20130820)
  MachineType: ZOTAC ZBOX-ID42-BE
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago)
  UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev 
sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B201P010
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID42-BE
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 3
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA:
  dmi.product.family: NA
  dmi.product.name: ZBOX-ID42-BE
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

To manage 

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

[Charles]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1730958/+attachment/5005905/+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/1730958

Title:
  nuvoton-cir not working after boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Current setup/failing setup:
  Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu 4.13.0-17.20-generic 4.13.8
  Ubuntu 17.10, 4.13.0-17-generic
  Nuvoton w836x7hg Infrared Remote Transceiver
  Zotac ID42

  Working setup:
  Ubuntu 17.10, 4.4.8-040408-generic

  I'm not able to get the remote working after a normal reboot (using 4.13 
kernel)
  It does actually after a suspend and wake-up, and do a echo 'auto' to 
resources.

  Please find snapshot of dmesg below:

  [   14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input7
  [   14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   14.468526] nuvoton-cir 00:0a: driver has been successfully loaded

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [   66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input13
  [   66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   66.232240] nuvoton-cir 00:0a: driver has been successfully loaded

   suspend/resume

  [  105.890769] nuvoton-cir 00:0a: disabled
  [  106.651982] nuvoton-cir 00:0a: activated

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [  138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [  138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [  138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input17
  [  138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [  138.552256] nuvoton-cir 00:0a: driver has been successfully loaded

  In order to get the device working I need the following in this order:
  * suspend/resume
  * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6
  InstallationDate: Installed on 2014-04-01 (1317 days ago)
  InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 
(20130820)
  MachineType: ZOTAC ZBOX-ID42-BE
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago)
  UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev 
sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B201P010
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID42-BE
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 3
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA:
  dmi.product.family: NA
  dmi.product.name: ZBOX-ID42-BE
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

[Kernel-packages] [Bug 1730958] ProcEnviron.txt

[Charles]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1730958/+attachment/5005910/+files/ProcEnviron.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/1730958

Title:
  nuvoton-cir not working after boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Current setup/failing setup:
  Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu 4.13.0-17.20-generic 4.13.8
  Ubuntu 17.10, 4.13.0-17-generic
  Nuvoton w836x7hg Infrared Remote Transceiver
  Zotac ID42

  Working setup:
  Ubuntu 17.10, 4.4.8-040408-generic

  I'm not able to get the remote working after a normal reboot (using 4.13 
kernel)
  It does actually after a suspend and wake-up, and do a echo 'auto' to 
resources.

  Please find snapshot of dmesg below:

  [   14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input7
  [   14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   14.468526] nuvoton-cir 00:0a: driver has been successfully loaded

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [   66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input13
  [   66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   66.232240] nuvoton-cir 00:0a: driver has been successfully loaded

   suspend/resume

  [  105.890769] nuvoton-cir 00:0a: disabled
  [  106.651982] nuvoton-cir 00:0a: activated

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [  138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [  138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [  138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input17
  [  138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [  138.552256] nuvoton-cir 00:0a: driver has been successfully loaded

  In order to get the device working I need the following in this order:
  * suspend/resume
  * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6
  InstallationDate: Installed on 2014-04-01 (1317 days ago)
  InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 
(20130820)
  MachineType: ZOTAC ZBOX-ID42-BE
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago)
  UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev 
sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B201P010
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID42-BE
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 3
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA:
  dmi.product.family: NA
  dmi.product.name: ZBOX-ID42-BE
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

To 

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

[Charles]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1730958/+attachment/5005908/+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/1730958

Title:
  nuvoton-cir not working after boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Current setup/failing setup:
  Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu 4.13.0-17.20-generic 4.13.8
  Ubuntu 17.10, 4.13.0-17-generic
  Nuvoton w836x7hg Infrared Remote Transceiver
  Zotac ID42

  Working setup:
  Ubuntu 17.10, 4.4.8-040408-generic

  I'm not able to get the remote working after a normal reboot (using 4.13 
kernel)
  It does actually after a suspend and wake-up, and do a echo 'auto' to 
resources.

  Please find snapshot of dmesg below:

  [   14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input7
  [   14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   14.468526] nuvoton-cir 00:0a: driver has been successfully loaded

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [   66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input13
  [   66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   66.232240] nuvoton-cir 00:0a: driver has been successfully loaded

   suspend/resume

  [  105.890769] nuvoton-cir 00:0a: disabled
  [  106.651982] nuvoton-cir 00:0a: activated

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [  138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [  138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [  138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input17
  [  138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [  138.552256] nuvoton-cir 00:0a: driver has been successfully loaded

  In order to get the device working I need the following in this order:
  * suspend/resume
  * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6
  InstallationDate: Installed on 2014-04-01 (1317 days ago)
  InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 
(20130820)
  MachineType: ZOTAC ZBOX-ID42-BE
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago)
  UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev 
sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B201P010
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID42-BE
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 3
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA:
  dmi.product.family: NA
  dmi.product.name: ZBOX-ID42-BE
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

To 

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

[Charles]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1730958/+attachment/5005909/+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/1730958

Title:
  nuvoton-cir not working after boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Current setup/failing setup:
  Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu 4.13.0-17.20-generic 4.13.8
  Ubuntu 17.10, 4.13.0-17-generic
  Nuvoton w836x7hg Infrared Remote Transceiver
  Zotac ID42

  Working setup:
  Ubuntu 17.10, 4.4.8-040408-generic

  I'm not able to get the remote working after a normal reboot (using 4.13 
kernel)
  It does actually after a suspend and wake-up, and do a echo 'auto' to 
resources.

  Please find snapshot of dmesg below:

  [   14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input7
  [   14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   14.468526] nuvoton-cir 00:0a: driver has been successfully loaded

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [   66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input13
  [   66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   66.232240] nuvoton-cir 00:0a: driver has been successfully loaded

   suspend/resume

  [  105.890769] nuvoton-cir 00:0a: disabled
  [  106.651982] nuvoton-cir 00:0a: activated

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [  138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [  138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [  138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input17
  [  138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [  138.552256] nuvoton-cir 00:0a: driver has been successfully loaded

  In order to get the device working I need the following in this order:
  * suspend/resume
  * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6
  InstallationDate: Installed on 2014-04-01 (1317 days ago)
  InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 
(20130820)
  MachineType: ZOTAC ZBOX-ID42-BE
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago)
  UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev 
sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B201P010
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID42-BE
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 3
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA:
  dmi.product.family: NA
  dmi.product.name: ZBOX-ID42-BE
  dmi.product.version: XX
  

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

[Charles]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1730958/+attachment/5005907/+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/1730958

Title:
  nuvoton-cir not working after boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Current setup/failing setup:
  Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu 4.13.0-17.20-generic 4.13.8
  Ubuntu 17.10, 4.13.0-17-generic
  Nuvoton w836x7hg Infrared Remote Transceiver
  Zotac ID42

  Working setup:
  Ubuntu 17.10, 4.4.8-040408-generic

  I'm not able to get the remote working after a normal reboot (using 4.13 
kernel)
  It does actually after a suspend and wake-up, and do a echo 'auto' to 
resources.

  Please find snapshot of dmesg below:

  [   14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input7
  [   14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   14.468526] nuvoton-cir 00:0a: driver has been successfully loaded

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [   66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input13
  [   66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   66.232240] nuvoton-cir 00:0a: driver has been successfully loaded

   suspend/resume

  [  105.890769] nuvoton-cir 00:0a: disabled
  [  106.651982] nuvoton-cir 00:0a: activated

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [  138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [  138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [  138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input17
  [  138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [  138.552256] nuvoton-cir 00:0a: driver has been successfully loaded

  In order to get the device working I need the following in this order:
  * suspend/resume
  * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6
  InstallationDate: Installed on 2014-04-01 (1317 days ago)
  InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 
(20130820)
  MachineType: ZOTAC ZBOX-ID42-BE
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago)
  UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev 
sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B201P010
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID42-BE
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 3
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA:
  dmi.product.family: NA
  dmi.product.name: ZBOX-ID42-BE
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

To manage 

[Kernel-packages] [Bug 1730717] Re: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"

[Joseph Salisbury]

@Laney, thanks for testing the mainline kernel.  It's promising that a
fix might be in that kernel.  The time consuming part will be
identifying what commit in that kernel is the actual fix.  We could
perform a "Reverse" kernel bisect, which would required testing 12 or so
test kernels.  However, it sounds like to set up a reproducer is time
consuming as well.

The easiest thing to try next would be to test the latest upstream 4.13
stable kernels.  It's possible the fix that is in 4.14-rc8 was also cc'd
to upstream stable and made it's way into 4.13 thorough the normal
stable update process.

If possible to test, the latest 4.13 upstream kernel is 4.13.12 and is 
available here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13.12/

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

Title:
  Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck
  for 22s! [systemd:1]"

Status in linux package in Ubuntu:
  Triaged
Status in qemu-kvm package in Ubuntu:
  New
Status in linux source package in Artful:
  Triaged
Status in qemu-kvm source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in qemu-kvm source package in Bionic:
  New

Bug description:
  This is impacting us for ubuntu autopkgtests. Eventually the whole
  region ends up dying because each worker is hit by this bug in turn
  and backs off until the next reset (6 hourly).

  17.10 (and bionic) guests are sometimes failing to reboot. When this
  happens, you see the following in the console

    [[0;32m  OK  [0m] Reached target Shutdown.
    [  191.698969] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
    [  219.698438] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
    [  226.702150] INFO: rcu_sched detected stalls on CPUs/tasks:
    [  226.704958] »(detected by 0, t=15002 jiffies, g=5347, c=5346, q=187)
    [  226.706093] All QSes seen, last rcu_sched kthread activity 15002 
(4294949060-4294934058), jiffies_till_next_fqs=1, root ->qsmask 0x0
    [  226.708202] rcu_sched kthread starved for 15002 jiffies! g5347 c5346 
f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0

  One host that exhibits this behaviour was:

    Linux klock 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

  guest running:

    Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version 7.2.0
  (Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
  (Ubuntu 4.13.0-16.19-generic 4.13.4)

  The affected cloud region is running the xenial/Ocata cloud archive,
  so the version of qemu-kvm in there may also be relevant.

  Here's how I reproduced it in lcy01:

    $ for n in {1..30}; do nova boot --flavor m1.small --image 
ubuntu/ubuntu-artful-17.10-amd64-server-20171026.1-disk1.img --key-name 
testbed-`hostname` --nic net-name=net_ues_proposed_migration laney-test${n}; 
done
    $  sudo reboot
    # wait a minute or so for the instances to all reboot
    $ for n in {1..30}; do echo "=== ${n} ==="; nova console-log laney-test${n} 
| tail; done

  On bad instances you'll see the "soft lockup" message - on good it'll
  reboot as normal.

  We've seen good and bad instances on multiple compute hosts - it
  doesn't feel to me like a host problem but rather a race condition
  somewhere that's somehow either triggered or triggered much more often
  by what lcy01 is running. I always saw this on the first reboot -
  never on first boot, and never on n>1th boot. (But if it's a race then
  that might not mean much.)

  I'll attach a bad and a good console-log for reference.

  If you're at Canonical then see internal rt #107135 for some other
  details.

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

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

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

[Charles]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1730958/+attachment/5005912/+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/1730958

Title:
  nuvoton-cir not working after boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Current setup/failing setup:
  Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu 4.13.0-17.20-generic 4.13.8
  Ubuntu 17.10, 4.13.0-17-generic
  Nuvoton w836x7hg Infrared Remote Transceiver
  Zotac ID42

  Working setup:
  Ubuntu 17.10, 4.4.8-040408-generic

  I'm not able to get the remote working after a normal reboot (using 4.13 
kernel)
  It does actually after a suspend and wake-up, and do a echo 'auto' to 
resources.

  Please find snapshot of dmesg below:

  [   14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input7
  [   14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   14.468526] nuvoton-cir 00:0a: driver has been successfully loaded

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [   66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input13
  [   66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   66.232240] nuvoton-cir 00:0a: driver has been successfully loaded

   suspend/resume

  [  105.890769] nuvoton-cir 00:0a: disabled
  [  106.651982] nuvoton-cir 00:0a: activated

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [  138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [  138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [  138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input17
  [  138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [  138.552256] nuvoton-cir 00:0a: driver has been successfully loaded

  In order to get the device working I need the following in this order:
  * suspend/resume
  * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6
  InstallationDate: Installed on 2014-04-01 (1317 days ago)
  InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 
(20130820)
  MachineType: ZOTAC ZBOX-ID42-BE
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago)
  UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev 
sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B201P010
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID42-BE
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 3
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA:
  dmi.product.family: NA
  dmi.product.name: ZBOX-ID42-BE
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

To 

[Kernel-packages] [Bug 1730958] IwConfig.txt

[Charles]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1730958/+attachment/5005904/+files/IwConfig.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/1730958

Title:
  nuvoton-cir not working after boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Current setup/failing setup:
  Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  Ubuntu 4.13.0-17.20-generic 4.13.8
  Ubuntu 17.10, 4.13.0-17-generic
  Nuvoton w836x7hg Infrared Remote Transceiver
  Zotac ID42

  Working setup:
  Ubuntu 17.10, 4.4.8-040408-generic

  I'm not able to get the remote working after a normal reboot (using 4.13 
kernel)
  It does actually after a suspend and wake-up, and do a echo 'auto' to 
resources.

  Please find snapshot of dmesg below:

  [   14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input7
  [   14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   14.468526] nuvoton-cir 00:0a: driver has been successfully loaded

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [   66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [   66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [   66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input13
  [   66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [   66.232240] nuvoton-cir 00:0a: driver has been successfully loaded

   suspend/resume

  [  105.890769] nuvoton-cir 00:0a: disabled
  [  106.651982] nuvoton-cir 00:0a: activated

  
  modprobe -r nuvoton-cir
  echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  modprobe nuvoton-cir
  

  [  138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 
0x33
  [  138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0
  [  138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as 
/devices/pnp0/00:0a/rc/rc0/input17
  [  138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) 
registered at minor = 0
  [  138.552256] nuvoton-cir 00:0a: driver has been successfully loaded

  In order to get the device working I need the following in this order:
  * suspend/resume
  * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6
  InstallationDate: Installed on 2014-04-01 (1317 days ago)
  InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 
(20130820)
  MachineType: ZOTAC ZBOX-ID42-BE
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago)
  UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev 
sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B201P010
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID42-BE
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 3
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA:
  dmi.product.family: NA
  dmi.product.name: ZBOX-ID42-BE
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

To manage 

[Kernel-packages] [Bug 1730596] Re: s390/mm: fix write access check in gup_huge_pmd()

[Joseph Salisbury]

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

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

** Tags removed: kernel-da-key
** Tags added: kernel-key

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

Title:
  s390/mm: fix write access check in gup_huge_pmd()

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  Triaged

Bug description:
  The check for the _SEGMENT_ENTRY_PROTECT bit in gup_huge_pmd() is the
  wrong way around. It must not be set for write==1, and not be checked for
  write==0. Fix this similar to how it was fixed for ptes long time ago in
  commit 25591b0 ("[S390] fix get_user_pages_fast").

  One impact of this bug would be unnecessarily using the gup slow path for
  write==0 on r/w mappings. A potentially more severe impact would be that
  gup_huge_pmd() will succeed for write==1 on r/o mappings.

  Addl information

  Problem: The check for the _SEGMENT_ENTRY_PROTECT bit in
gup_huge_pmd() is the wrong way around. It must not be set
for write==1, and not be checked for write==0. Allowing
write==1 with protection bit set, instead of breaking out
to the slow path, will result in a missing faultin_page()
to clear the protection bit (for valid writable mappings),
and the async I/O write operation will fail to write to
such a mapping.
  Solution: Fix it by correctly checking the protection bit like it is
also done in gup_pte_range() and gup_huge_pud().
  Reproduction: Async I/O workload on buffers that are mapped as transparent
hugepages.
  Upstream-ID:  ba385c0594e723d41790ecfb12c610e6f90c7785

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

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

[Kernel-packages] [Bug 1730505] Re: [MacBookPro12, 1] SD Card Reader not working

[Christopher M. Penalver]

** This bug is no longer a duplicate of bug 1531653
   Macbook Pro Retina 11,1 SD Card Reader Doesn't Work

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

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

** Description changed:

- Related bug to this one: bug #1531653
+ My SD card reader doesn't work.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-98-generic 4.4.0-98.121
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  jhodapp4369 F pulseaudio
-  /dev/snd/pcmC1D0p:   jhodapp4369 F...m pulseaudio
-  /dev/snd/controlC1:  jhodapp4369 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  jhodapp4369 F pulseaudio
+  /dev/snd/pcmC1D0p:   jhodapp4369 F...m pulseaudio
+  /dev/snd/controlC1:  jhodapp4369 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov  6 15:23:15 2017
  HibernationDevice: RESUME=UUID=a9029808-b026-4ab1-808a-d0058e8f30b6
  InstallationDate: Installed on 2015-08-02 (827 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 004: ID 05ac:0273 Apple, Inc. 
-  Bus 001 Device 003: ID 05ac:8290 Apple, Inc. 
-  Bus 001 Device 011: ID 05ac:12a8 Apple, Inc. iPhone5/5C/5S/6
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 05ac:0273 Apple, Inc.
+  Bus 001 Device 003: ID 05ac:8290 Apple, Inc.
+  Bus 001 Device 011: ID 05ac:12a8 Apple, Inc. iPhone5/5C/5S/6
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=8d74649d-74b5-4276-a1fe-275341c3578c ro libata.force=noncq quiet 
splash acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-4.4.0-98-generic N/A
-  linux-backports-modules-4.4.0-98-generic  N/A
-  linux-firmware1.157.13
+  linux-restricted-modules-4.4.0-98-generic N/A
+  linux-backports-modules-4.4.0-98-generic  N/A
+  linux-firmware1.157.13
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B07.1506051617
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B07.1506051617:bd06/05/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

Title:
  [MacBookPro12,1] SD Card Reader not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My SD card reader doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-98-generic 4.4.0-98.121
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jhodapp4369 F pulseaudio
   /dev/snd/pcmC1D0p:   jhodapp4369 F...m pulseaudio
   /dev/snd/controlC1:  jhodapp4369 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov  6 15:23:15 2017
  HibernationDevice: RESUME=UUID=a9029808-b026-4ab1-808a-d0058e8f30b6
  InstallationDate: Installed on 2015-08-02 (827 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05ac:0273 Apple, Inc.
   Bus 001 Device 003: ID 05ac:8290 Apple, Inc.
   Bus 001 Device 011: ID 05ac:12a8 Apple, Inc. iPhone5/5C/5S/6
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=8d74649d-74b5-4276-a1fe-275341c3578c ro libata.force=noncq quiet 
splash acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.157.13
  

Re: [Kernel-packages] [Bug 1730717] Re: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"

[Iain Lane]

On Wed, Nov 08, 2017 at 03:16:29PM -, Joseph Salisbury wrote:
> @Laney, thanks for testing the mainline kernel.  It's promising that a
> fix might be in that kernel.  The time consuming part will be
> identifying what commit in that kernel is the actual fix.  We could
> perform a "Reverse" kernel bisect, which would required testing 12 or so
> test kernels.  However, it sounds like to set up a reproducer is time
> consuming as well.
> 
> The easiest thing to try next would be to test the latest upstream 4.13
> stable kernels.  It's possible the fix that is in 4.14-rc8 was also cc'd
> to upstream stable and made it's way into 4.13 thorough the normal
> stable update process.
> 
> If possible to test, the latest 4.13 upstream kernel is 4.13.12 and is 
> available here:
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13.12/

20 instances, all good.

Maybe I should try one that we think is 'bad' to confirm that the way
I'm doing this is actually capable of reproducing the issue? If you
think that's sensible, could you recommend me a kernel to try?

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck
  for 22s! [systemd:1]"

Status in linux package in Ubuntu:
  Triaged
Status in qemu-kvm package in Ubuntu:
  New
Status in linux source package in Artful:
  Triaged
Status in qemu-kvm source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in qemu-kvm source package in Bionic:
  New

Bug description:
  This is impacting us for ubuntu autopkgtests. Eventually the whole
  region ends up dying because each worker is hit by this bug in turn
  and backs off until the next reset (6 hourly).

  17.10 (and bionic) guests are sometimes failing to reboot. When this
  happens, you see the following in the console

    [[0;32m  OK  [0m] Reached target Shutdown.
    [  191.698969] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
    [  219.698438] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
    [  226.702150] INFO: rcu_sched detected stalls on CPUs/tasks:
    [  226.704958] »(detected by 0, t=15002 jiffies, g=5347, c=5346, q=187)
    [  226.706093] All QSes seen, last rcu_sched kthread activity 15002 
(4294949060-4294934058), jiffies_till_next_fqs=1, root ->qsmask 0x0
    [  226.708202] rcu_sched kthread starved for 15002 jiffies! g5347 c5346 
f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0

  One host that exhibits this behaviour was:

    Linux klock 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

  guest running:

    Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version 7.2.0
  (Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
  (Ubuntu 4.13.0-16.19-generic 4.13.4)

  The affected cloud region is running the xenial/Ocata cloud archive,
  so the version of qemu-kvm in there may also be relevant.

  Here's how I reproduced it in lcy01:

    $ for n in {1..30}; do nova boot --flavor m1.small --image 
ubuntu/ubuntu-artful-17.10-amd64-server-20171026.1-disk1.img --key-name 
testbed-`hostname` --nic net-name=net_ues_proposed_migration laney-test${n}; 
done
    $  sudo reboot
    # wait a minute or so for the instances to all reboot
    $ for n in {1..30}; do echo "=== ${n} ==="; nova console-log laney-test${n} 
| tail; done

  On bad instances you'll see the "soft lockup" message - on good it'll
  reboot as normal.

  We've seen good and bad instances on multiple compute hosts - it
  doesn't feel to me like a host problem but rather a race condition
  somewhere that's somehow either triggered or triggered much more often
  by what lcy01 is running. I always saw this on the first reboot -
  never on first boot, and never on n>1th boot. (But if it's a race then
  that might not mean much.)

  I'll attach a bad and a good console-log for reference.

  If you're at Canonical then see internal rt #107135 for some other
  details.

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

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

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

[bugproxy]

--- Comment From hasri...@in.ibm.com 2017-11-08 11:21 EDT---
(In reply to comment #16)
>
> Does this bug still happen on Artful with the latest updates?

Oh, somehow missed the above comment..

# ./check tests/generic/445
FSTYP -- ext4
PLATFORM  -- Linux/ppc64le ltcalpine-lp9 4.13.0-16-generic
MKFS_OPTIONS  -- /dev/loop1
MOUNT_OPTIONS -- -o acl,user_xattr /dev/loop1 /mnt/scratch

generic/445  0s
Ran: generic/445
Passed all 1 tests

Test passed with latest artful kernel. Issue is resolved.

Thanks,
Harish

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

Title:
  xfstest sanity checks 17 fails on  data-hole-data inside page

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

Bug description:
  Problem Description
  
  xfstests fails with Metadata corruption at leaf on ext4 filesystem

  Environment
  --
  Kernel Build:  4.12.1-041201-generic
  System Name : ltc-test-ci2
  Model  : 8247-22L
  Platform:  PowerNV ( P8 )
  Issue observed in P9 also.

  Uname output
  ---
  # uname -a
  Linux ltc-test-ci2 4.12.1-041201-generic #201707121132 SMP Wed Jul 12 
17:03:25 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

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

  generic/445  [failed, exit status 1] - output mismatch (see 
/root/harish/xfstests-dev/results//generic/445.out.bad)
  --- tests/generic/445.out   2017-07-13 06:04:36.244322946 -0400
  +++ /root/harish/xfstests-dev/results//generic/445.out.bad  2017-07-14 
02:49:06.540352923 -0400
  @@ -1,2 +1,3 @@
   QA output created by 445
  -Silence is golden
  +seek sanity check failed!
  +(see /root/harish/xfstests-dev/results//generic/445.full for details)
  ...
  (Run 'diff -u tests/generic/445.out 
/root/harish/xfstests-dev/results//generic/445.out.bad'  to see the entire diff)

  
  Nothing observed in dmesg.

  Full log is attached.

  Note: Issue is also observed on distro kernel - 4.11.0-10-generic.

  It needs to have two disks you run the test on. Make sure you create
  those directories before running the test.

  # cat local.config
  export TEST_DEV=/dev/loop0
  export TEST_DIR=/mnt/test
  export SCRATCH_DEV=/dev/loop1
  export SCRATCH_MNT=/mnt/scratch

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

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

Re: [Kernel-packages] [Bug 1730480] Re: Problem after 17.04 to 17.10 upgrade

[G. Herrick]

Hi

Thank you for taking an interest in this. I am sorry, but the testing
you suggest seems to be too complicated for me.

However, I have watched the Grub boot up carefully - it scrolls past
quickly - but I have spotted, before the Recovery Menu, a line that I
think reads, in part,...  DM:RADEON_INIT [RADEON] ERROR . 

I can use the computer as it is, and will wait for the next linux
upgrade, and let you know what happens.

Thanks again,

George Herrick.

---

On Tue, 07 Nov 2017 21:32:54 -
Joseph Salisbury  wrote:

> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.14 kernel[0].
> 
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
> 
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
> 
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".
> 
> 
> Thanks in advance.
> 
> [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc8
> 
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Medium
> 
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Incomplete
>

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

Title:
  Problem after 17.04 to 17.10 upgrade

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Problem after 17.04 to 17.10 upgrade - seven days ago.
  I have to boot using Grub, in recovery mode. System works ok. During power 
down, I get -
  A Stop Job is Running for Session C3 of User GDM - which waits for 1 minute 
30 - and then proceeds to finish.
  System is an AMD64, with graphics on the motherboard. I will search for more 
detail if necessary.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gherrick   1646 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=26031761-8323-4a7b-85b2-0dc3fbcdb852
  InstallationDate: Installed on 2016-05-05 (551 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-MA74GMT-S2
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=f2bc2165-9cb7-467c-a941-8e5ae02ee038 ro recovery nomodeset
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill:
   
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F10
  dmi.board.name: GA-MA74GMT-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd08/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA74GMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA74GMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA74GMT-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1730904] Re: 17.10 freezes every hour ramdomly

[Roger Tri]

** Summary changed:

- 17.10 freezes on java interaction
+ 17.10 freezes every hour ramdomly

** Description changed:

- on 17.04 java apps show a graphical display problem, now hangs all the
- computer
+ on 17.04 I had frequent errors reported, now hangs all the computer,
+ please some workaround or way back to 17.04
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  rogelio1645 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  rogelio1645 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 09:07:15 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e26838c6-6b72-461d-a811-a892d423fac1
  InstallationDate: Installed on 2017-05-04 (187 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. K55A
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=es_ES.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=es_ES.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-4.13.0-16-generic N/A
-  linux-backports-modules-4.13.0-16-generic  N/A
-  linux-firmware 1.169
+  linux-restricted-modules-4.13.0-16-generic N/A
+  linux-backports-modules-4.13.0-16-generic  N/A
+  linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-07 (0 days ago)
  dmi.bios.date: 03/13/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K55A.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K55A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK55A.204:bd03/13/2012:svnASUSTeKCOMPUTERINC.:pnK55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K55A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER 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/1730904

Title:
  17.10 freezes every hour ramdomly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  on 17.04 I had frequent errors reported, now hangs all the computer,
  please some workaround or way back to 17.04

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rogelio1645 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 09:07:15 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e26838c6-6b72-461d-a811-a892d423fac1
  InstallationDate: Installed on 2017-05-04 (187 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. K55A
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-07 (0 days ago)
  dmi.bios.date: 03/13/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K55A.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K55A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK55A.204:bd03/13/2012:svnASUSTeKCOMPUTERINC.:pnK55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K55A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:

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

[Ubuntu Kernel Bot]

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

apport-collect 1730321

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

Title:
  Ubuntu VM is not detecting the disks connected to Availa beach
  (LSI/Avago)  in Pass Thru mode

Status in linux package in Ubuntu:
  Incomplete
Status in xubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  Below is my setup details:
   
  C240 M4 24HDD server with AVB card (FW 24.12.1-0048) and Boot SSDs.
  Installed ESXi 6.0U1b in the boot SSD in AHCI mode.
  Updated the latest ESXi Native driver on this. (VMWare-Native-6.610.17.00)
  Created a VM and Installed Ubuntu 14.04.04.
  AVB card has one RAID1 VD, one JBOD and all other UG drives.
  Assigned the AVB controller as a Pass thorugh to ESXi host.
  Added AVB controller as a Pass through device to the Ubuntu VM.
  Updated the /etc/vmware/passthru.map file with the device ID and vendor ID of 
AVB card.
  Updated the Ubuntu VM with the latest MR driver 06.810

  I want to run some IOs to the disks connected to the AVB card from Ubuntu VM. 
But I am unable to see the disks from the VM.
  I am seeing so many call traces in the console related to megaraid_sas and 
see the attached screenshots of the same.

  Avago is able to reproduce the issue in their lab and see the attached
  email thread on this discussion.

  Note : The same scenario is working fine with Ubuntu 12.x series
  VM's.This issue is occurring both Ubuntu 14.x.x and 16.x.x series
  guest operating systems.

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

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

[Kernel-packages] [Bug 1730596] Re: s390/mm: fix write access check in gup_huge_pmd()

[Frank Heimes]

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

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

Title:
  s390/mm: fix write access check in gup_huge_pmd()

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  The check for the _SEGMENT_ENTRY_PROTECT bit in gup_huge_pmd() is the
  wrong way around. It must not be set for write==1, and not be checked for
  write==0. Fix this similar to how it was fixed for ptes long time ago in
  commit 25591b0 ("[S390] fix get_user_pages_fast").

  One impact of this bug would be unnecessarily using the gup slow path for
  write==0 on r/w mappings. A potentially more severe impact would be that
  gup_huge_pmd() will succeed for write==1 on r/o mappings.

  Addl information

  Problem: The check for the _SEGMENT_ENTRY_PROTECT bit in
gup_huge_pmd() is the wrong way around. It must not be set
for write==1, and not be checked for write==0. Allowing
write==1 with protection bit set, instead of breaking out
to the slow path, will result in a missing faultin_page()
to clear the protection bit (for valid writable mappings),
and the async I/O write operation will fail to write to
such a mapping.
  Solution: Fix it by correctly checking the protection bit like it is
also done in gup_pte_range() and gup_huge_pud().
  Reproduction: Async I/O workload on buffers that are mapped as transparent
hugepages.
  Upstream-ID:  ba385c0594e723d41790ecfb12c610e6f90c7785

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

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

[Kernel-packages] [Bug 1728927] Re: linux: 4.13.0-17.20 -proposed tracker

[Brad Figg]

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

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

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

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

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1728930,1728935,1728937
  derivatives: 1730611
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Monday, 06. November 2017 10:32 UTC
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase-changed:Wednesday, 08. November 2017 17:01 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1728930,1728935,1728937
  derivatives: 1730611
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-stable-phase-changed:Wednesday, 08. November 2017 17:01 UTC
- kernel-stable-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 4.13.0-17.20 -proposed tracker

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

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

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

  backports: 1728930,1728935,1728937
  derivatives: 1730611
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1730321] Re: Ubuntu VM is not detecting the disks connected to Availa beach (LSI/Avago) in Pass Thru mode

[Samantha Jian-Pielak]

Hi BP, 
14.04.4 is end of life, please provide test results on ubuntu versions that 
aren't end of life yet. 

Please provide the information of the LSI card.

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

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

** Changed in: xubuntu-meta (Ubuntu)
   Status: New => Confirmed

** Changed in: xubuntu-meta (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/1730321

Title:
  Ubuntu VM is not detecting the disks connected to Availa beach
  (LSI/Avago)  in Pass Thru mode

Status in linux package in Ubuntu:
  Incomplete
Status in xubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  Below is my setup details:
   
  C240 M4 24HDD server with AVB card (FW 24.12.1-0048) and Boot SSDs.
  Installed ESXi 6.0U1b in the boot SSD in AHCI mode.
  Updated the latest ESXi Native driver on this. (VMWare-Native-6.610.17.00)
  Created a VM and Installed Ubuntu 14.04.04.
  AVB card has one RAID1 VD, one JBOD and all other UG drives.
  Assigned the AVB controller as a Pass thorugh to ESXi host.
  Added AVB controller as a Pass through device to the Ubuntu VM.
  Updated the /etc/vmware/passthru.map file with the device ID and vendor ID of 
AVB card.
  Updated the Ubuntu VM with the latest MR driver 06.810

  I want to run some IOs to the disks connected to the AVB card from Ubuntu VM. 
But I am unable to see the disks from the VM.
  I am seeing so many call traces in the console related to megaraid_sas and 
see the attached screenshots of the same.

  Avago is able to reproduce the issue in their lab and see the attached
  email thread on this discussion.

  Note : The same scenario is working fine with Ubuntu 12.x series
  VM's.This issue is occurring both Ubuntu 14.x.x and 16.x.x series
  guest operating systems.

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

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

[Kernel-packages] [Bug 1720930] Re: wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)

[Michael Kim]

I too am having this problem with a fresh install of 17.10 onto a ASUS
GL753 laptop. I tried both fixes above: updated to 4.13.12 and the
workaround in #17 (editing grub). System will still neither restart nor
power down without hanging.

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

Title:
  wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware
  (-22)

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

Bug description:
  When running artful on a new Zenbook Pro (uses Intel Wireless 8265), I
  get a hung shutdown with the message "wlp3s0: failed to remove key (1,
  ff:ff:ff:ff:ff:ff) from hardware (-22)". The kernel is also trying to
  load firmware versions that do not exist on the system i.e. versions
  33 then 32 of the firmware. It then seems to load version 31 of the
  firmware. Wireless features seem to work normally. The issues are just
  at shutdown time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dylan  1621 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Oct  3 06:12:13 2017
  HibernationDevice: RESUME=UUID=2b6908b4-d463-4170-9be5-556145c71a0e
  InstallationDate: Installed on 2017-10-02 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5755 IMC Networks 
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX550VE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=aa3dfd29-caf8-4882-906e-1b31b672d2c2 ro quiet splash threadirqs 
acpi_osi=! acpi_osi=Linux acpi_backlight=native vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550VE.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550VE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX550VE.300:bd06/05/2017:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX550VE
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1730596] Re: s390/mm: fix write access check in gup_huge_pmd()

[Joseph Salisbury]

This commit is already in Artful and Bionic master-next, so testing of
Xenial and Zesty is the most important.

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

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

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

Title:
  s390/mm: fix write access check in gup_huge_pmd()

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  The check for the _SEGMENT_ENTRY_PROTECT bit in gup_huge_pmd() is the
  wrong way around. It must not be set for write==1, and not be checked for
  write==0. Fix this similar to how it was fixed for ptes long time ago in
  commit 25591b0 ("[S390] fix get_user_pages_fast").

  One impact of this bug would be unnecessarily using the gup slow path for
  write==0 on r/w mappings. A potentially more severe impact would be that
  gup_huge_pmd() will succeed for write==1 on r/o mappings.

  Addl information

  Problem: The check for the _SEGMENT_ENTRY_PROTECT bit in
gup_huge_pmd() is the wrong way around. It must not be set
for write==1, and not be checked for write==0. Allowing
write==1 with protection bit set, instead of breaking out
to the slow path, will result in a missing faultin_page()
to clear the protection bit (for valid writable mappings),
and the async I/O write operation will fail to write to
such a mapping.
  Solution: Fix it by correctly checking the protection bit like it is
also done in gup_pte_range() and gup_huge_pud().
  Reproduction: Async I/O workload on buffers that are mapped as transparent
hugepages.
  Upstream-ID:  ba385c0594e723d41790ecfb12c610e6f90c7785

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

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

[Kernel-packages] [Bug 1730321] Re: Ubuntu VM is not detecting the disks connected to Availa beach (LSI/Avago) in Pass Thru mode

[Samantha Jian-Pielak]

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

Title:
  Ubuntu VM is not detecting the disks connected to Availa beach
  (LSI/Avago)  in Pass Thru mode

Status in linux package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  Below is my setup details:
   
  C240 M4 24HDD server with AVB card (FW 24.12.1-0048) and Boot SSDs.
  Installed ESXi 6.0U1b in the boot SSD in AHCI mode.
  Updated the latest ESXi Native driver on this. (VMWare-Native-6.610.17.00)
  Created a VM and Installed Ubuntu 14.04.04.
  AVB card has one RAID1 VD, one JBOD and all other UG drives.
  Assigned the AVB controller as a Pass thorugh to ESXi host.
  Added AVB controller as a Pass through device to the Ubuntu VM.
  Updated the /etc/vmware/passthru.map file with the device ID and vendor ID of 
AVB card.
  Updated the Ubuntu VM with the latest MR driver 06.810

  I want to run some IOs to the disks connected to the AVB card from Ubuntu VM. 
But I am unable to see the disks from the VM.
  I am seeing so many call traces in the console related to megaraid_sas and 
see the attached screenshots of the same.

  Avago is able to reproduce the issue in their lab and see the attached
  email thread on this discussion.

  Note : The same scenario is working fine with Ubuntu 12.x series
  VM's.This issue is occurring both Ubuntu 14.x.x and 16.x.x series
  guest operating systems.

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

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

[Kernel-packages] [Bug 1709738] Re: xfstest sanity checks 17 fails on data-hole-data inside page

[Joseph Salisbury]

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

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

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

Title:
  xfstest sanity checks 17 fails on  data-hole-data inside page

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

Bug description:
  Problem Description
  
  xfstests fails with Metadata corruption at leaf on ext4 filesystem

  Environment
  --
  Kernel Build:  4.12.1-041201-generic
  System Name : ltc-test-ci2
  Model  : 8247-22L
  Platform:  PowerNV ( P8 )
  Issue observed in P9 also.

  Uname output
  ---
  # uname -a
  Linux ltc-test-ci2 4.12.1-041201-generic #201707121132 SMP Wed Jul 12 
17:03:25 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

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

  generic/445  [failed, exit status 1] - output mismatch (see 
/root/harish/xfstests-dev/results//generic/445.out.bad)
  --- tests/generic/445.out   2017-07-13 06:04:36.244322946 -0400
  +++ /root/harish/xfstests-dev/results//generic/445.out.bad  2017-07-14 
02:49:06.540352923 -0400
  @@ -1,2 +1,3 @@
   QA output created by 445
  -Silence is golden
  +seek sanity check failed!
  +(see /root/harish/xfstests-dev/results//generic/445.full for details)
  ...
  (Run 'diff -u tests/generic/445.out 
/root/harish/xfstests-dev/results//generic/445.out.bad'  to see the entire diff)

  
  Nothing observed in dmesg.

  Full log is attached.

  Note: Issue is also observed on distro kernel - 4.11.0-10-generic.

  It needs to have two disks you run the test on. Make sure you create
  those directories before running the test.

  # cat local.config
  export TEST_DEV=/dev/loop0
  export TEST_DIR=/mnt/test
  export SCRATCH_DEV=/dev/loop1
  export SCRATCH_MNT=/mnt/scratch

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

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

[Kernel-packages] [Bug 1726493] Re: linux-aws needs module: nls_utf8

[Kamal Mostafa]

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

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

Title:
  linux-aws needs module: nls_utf8

Status in linux-aws package in Ubuntu:
  Fix Committed
Status in linux-aws source package in Xenial:
  Fix Committed

Bug description:
  Amazon requests nls_utf8.ko be made available in the main linux-aws
  kernel image package.

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

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

[Kernel-packages] [Bug 1727856] Re: update ENA driver to 1.3.0K from net-next

[Kamal Mostafa]

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

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

Title:
  update ENA driver to 1.3.0K from net-next

Status in linux-aws package in Ubuntu:
  Fix Committed
Status in linux-aws source package in Trusty:
  Fix Committed
Status in linux-aws source package in Xenial:
  Fix Committed

Bug description:
  Commits from net-next and mainline to update ENA from 1.2.0k to
  1.3.0K:

  net-next c057c68 MAINTAINERS: change ENA driver maintainers email domain
  net-next 1f4cf93 net: ena: Remove redundant unlikely()
  mainline cd7aea1 net: ena: reduce the severity of some printouts
  mainline 411838e net: ena: fix rare kernel crash when bar memory remap fails
  mainline a59df39 net: ena: fix wrong max Tx/Rx queues on ethtool
  net-next 88aef2f net: ena: improve ENA driver boot time.
  net-next dbeaf1e net: ena: remove legacy suspend suspend/resume support
  net-next 8c5c7ab net: ena: add power management ops to the ENA driver
  net-next 11095fd net: ena: add statistics for missed tx packets
  net-next 58894d5 net: ena: add new admin define for future support of IPv6 RSS
  net-next 046b307 net: ena: increase ena driver version to 1.3.0

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

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

[Kernel-packages] [Bug 1723913] Re: [Artful] Support headset mode for DELL WYSE

[Kleber Sacilotto de Souza]

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

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

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


** Tags added: verification-needed-artful

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

Title:
  [Artful] Support headset mode for DELL WYSE

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

Bug description:
  Enable headset mode support for WYSE(0x080c) platform.

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

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

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

[Kleber Sacilotto de Souza]

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

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

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

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

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

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

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

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

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

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

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


  -- Problem Description --

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

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

  Some additional debugfs emulated instruction counters are added also.

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

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

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

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

[Kernel-packages] [Bug 1724117] Re: thunderx2 ahci errata workaround needs additional delays

[Kleber Sacilotto de Souza]

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

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

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


** Tags added: verification-needed-artful

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

Title:
  thunderx2 ahci errata workaround needs additional delays

Status in linux package in Ubuntu:
  Won't Fix
Status in linux source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  Early ThunderX silicon may hang when initializing the SATA controller.

  [Test Case]
  This was found in a reboot loop.

  The latest ThunderX2 firmware (3.1) enables hardware error interrupts and
  when the reset fix fails, we get a hang with the print:
  [   14.839308] sd 1:0:0:0: [sdb] 468862128 512-byte logical blocks: (240 
GB/224 GiB)
  [   14.846796] sd 1:0:0:0: [sdb] 4096-byte physical blocks
  [   14.852036] sd 1:0:0:0: [sdb] Write Protect is off
  [   14.856843] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
  [   14.866022] ata2.00: Enabling discard_zeroes_data

  *** NBU BAR Error 0x1e25c ***
   AddrLo 0x1d80180 AddrHi 0x0

  [Regression Risk]
  The fix is only compiled in on arm64, and only activated at runtime on this 
specific revision of silicon, so regression risk will be limited to a single 
platform that is only being distributed for development purposes.

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

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

[Kernel-packages] [Bug 1722702] Re: libvirt - vnc port selection regression with newer kernels

[Kleber Sacilotto de Souza]

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

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

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


** Tags added: verification-needed-artful

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

Title:
  libvirt - vnc port selection regression with newer kernels

Status in libvirt package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed
Status in libvirt source package in Artful:
  Confirmed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  SRU Justification:

  Impact: Bug appears in linux-image-4.11.x kernels on 16.04.3.
  4.8.x and 4.10.x are okay.

  When libvirtd is restarted on Kernel 4.11.0-x-generic or above , it
  loses all information regarding existing port bindings and is unable
  to correctly re-identify vnc ports that currently in use. libvirt
  attempts to bind to an existing port and fails.

  instance-000a6096.log:2017-10-09T01:42:16.017220Z
  qemu-system-x86_64: -vnc 0.0.0.0:0: Failed to start VNC server: Failed to 
listen on socket: Address already in use

  Fairly certain this is the same bug reported, and patched in
  kernel-4.13.4-200.fc26 for Fedora
  https://bugzilla.redhat.com/show_bug.cgi?id=1432684

  Fix: Cherry picking a set of 3 patches (merged as the same set by
  David Miller) from upstream Linux.

  Testcase: Restart of libvirt.

  Risk for Regressions: Looking at the changes those 3 patches
  introduce, the delta is minimal and makes sense with respect to the
  explanations given in the commit message. Overall risk should be low.

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

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

[Kernel-packages] [Bug 1724912] Re: TSC_DEADLINE incorrectly disabled inside virtual guests

[Kleber Sacilotto de Souza]

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

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

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


** Tags added: verification-needed-artful

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

Title:
  TSC_DEADLINE incorrectly disabled inside virtual guests

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  An upstream commit added Intel cpu model/microcode checks to disable
  TSC_DEADLINE due to cpu errata:

  commit bd9240a18edfbfa72e957fc2ba831cf1f13ea073
  Author: Peter Zijlstra 
  Date: Wed May 31 17:52:03 2017 +0200

  x86/apic: Add TSC_DEADLINE quirk due to errata

  That commit is included in the Ubuntu kernels starting at artful
  v4.13.

  However, most hypervisors virtualize TSC deadline timer (and therefore
  it isn't affected by Intel CPU errata inside the guest), and even if
  any hypervisors directly exposed the hardware TSC deadline timer, the
  guests cannot update CPU microcode and therefore it's the hypervisor's
  job to disable/hide/virtualize the TSC deadline timer from the guest.

  This upstream commit skips the microcode check to disable the TSC
  deadline timer if it detects it's running under a hypervisor:

  commit cc6afe2240298049585e86b1ade85efc8a7f225d
  Author: Paolo Bonzini 
  Date:   Tue Oct 10 12:12:57 2017 +0200

  x86/apic: Silence "FW_BUG TSC_DEADLINE disabled due to Errata" on
  hypervisors

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

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

[Kernel-packages] [Bug 1723916] Re: [Artful] Add support for Dell/Wyse 3040 audio codec

[Kleber Sacilotto de Souza]

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

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

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


** Tags added: verification-needed-artful

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

Title:
  [Artful] Add support for Dell/Wyse 3040 audio codec

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

Bug description:
  The rt5760 on Wyse 3040 requires some extra code to work.

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

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

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

[Kleber Sacilotto de Souza]

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

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

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


** Tags added: verification-needed-zesty

** Tags added: verification-needed-artful

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

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

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

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

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

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

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

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


  -- Problem Description --

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

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

  Some additional debugfs emulated instruction counters are added also.

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

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

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

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

[Kernel-packages] [Bug 1723986] Re: Touchpad and TrackPoint Dose Not Work on Lenovo X1C6 and X280

[Kleber Sacilotto de Souza]

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

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

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


** Tags added: verification-needed-artful

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

Title:
  Touchpad and TrackPoint Dose Not Work on Lenovo X1C6 and X280

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

Bug description:
  Synaptics devices on Lenovo X1C6 and X280 can not work via PS/2 mode, it show:
  [   11.366996] psmouse serio1: synaptics: Touchpad model: 1, fw: 9.16, id: 
0x1e2a1, caps: 0xf001a3/0x940300/0x12e800/0x50, board id: 3382, fw id: 
2629663
  [   11.367002] psmouse serio1: synaptics: serio: Synaptics pass-through port 
at isa0060/serio1/input0
  [   11.781876] psmouse serio2: Failed to reset mouse on synaptics-pt/serio0
  [   30.390508] psmouse serio2: Failed to deactivate mouse on 
synaptics-pt/serio0
  [   30.862260] psmouse serio2: Failed to enable mouse on synaptics-pt/serio0

  Enable SMBus mode on these devices will make them work.

  Cherrypick 3 patches from patchwork as sauce patches on Ubuntu Artful
  kernel.

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

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

[Kernel-packages] [Bug 1723915] Re: [Artful] Some Dell Monitors Doesn't Work Well with Dell/Wyse 3040

[Kleber Sacilotto de Souza]

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

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

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


** Tags added: verification-needed-artful

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

Title:
  [Artful] Some Dell Monitors Doesn't Work Well with Dell/Wyse 3040

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

Bug description:
  Dell Wyse 3040 box with Cherry Trail shows a blank monitor output and
  other display issues (eg. flickering after changing resolution) with a
  certain Dell DP monitors (E-series).

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

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

[Kernel-packages] [Bug 1724612] Re: x86/apic: Update TSC_DEADLINE quirk with additional SKX stepping

[Kleber Sacilotto de Souza]

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

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

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


** Tags added: verification-needed-artful

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

Title:
  x86/apic: Update TSC_DEADLINE quirk with additional SKX stepping

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

Bug description:
  An upstream commit added Intel cpu model/microcode checks to disable
  TSC_DEADLINE due to cpu errata:

  commit bd9240a18edfbfa72e957fc2ba831cf1f13ea073
  Author: Peter Zijlstra 
  Date:   Wed May 31 17:52:03 2017 +0200

  x86/apic: Add TSC_DEADLINE quirk due to errata

  
  That commit is included in the Ubuntu kernels starting at artful v4.13.  
However, the commit includes a check for Skylake Xeons, but the microcode 
update version number differs based on Skylake Xeon stepping, so an additional 
commit is required to correctly check the microcode level of both stepping 3 
and stepping 4 Skylake Xeons, and disable/enable TSC_DEADLINE appropriately.

  Upstream commit that corrects the check is:

  commit 616dd5872e52493863b0202632703eebd51243dc
  Author: Len Brown 
  Date:   Wed Oct 11 17:16:04 2017 -0400

  x86/apic: Update TSC_DEADLINE quirk with additional SKX stepping

  
  Without the additional commit, Skylake Xeon stepping-3 cpus with the fixed 
microcode version will incorrectly have their TSC_DEADLINE disabled.

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

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

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

[Joseph Salisbury]

SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2017-November/088109.html

** Description changed:

+ 
+ == SRU Justification ==
+ This bug is fixed by commit 00dab8187e18.  The commit updates the hvc
+ driver to use the OPAL irqchip if made available by the running firmware.
+ If it is not present, the driver falls back to the existing OPAL event 
number.   
+ 
+ Commit 00dab8187e18 was added to mainline is v4.8-rc1, so it is not needed in 
+ releases newer than Xenial.  The commit is a clean cherry pick in Xenial.
+ 
+ 
+ == Fix ==
+ commit 00dab8187e182da41122f66c207707b192509df4
+ Author: Sam Mendoza-Jonas 
+ Date:   Mon Jul 11 13:38:58 2016 +1000
+ 
+ tty/hvc: Use opal irqchip interface if available
+ 
+ 
+ == Regression Potential ==
+ This change is specific to the hvc driver and has been in mainline since 
v4.8-rc1
+ without any issues reported.
+ 
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug 
reporter.
+ The bug reporter states the test kernel resolved the bug.
+ 
+ 
  ---Problem Description---
  Please backport console irq patch .
  
  commit 00dab8187e182da41122f66c207707b192509df4
  Author: Sam Mendoza-Jonas 
  Date:   Mon Jul 11 13:38:58 2016 +1000
  
- tty/hvc: Use opal irqchip interface if available
- 
- Update the hvc driver to use the OPAL irqchip if made available by the
- running firmware. If it is not present, the driver falls back to the
- existing OPAL event number.
- 
- Signed-off-by: Samuel Mendoza-Jonas 
- Signed-off-by: Michael Ellerman 
+ tty/hvc: Use opal irqchip interface if available
+ 
+ Update the hvc driver to use the OPAL irqchip if made available by the
+ running firmware. If it is not present, the driver falls back to the
+ existing OPAL event number.
+ 
+ Signed-off-by: Samuel Mendoza-Jonas 
+ Signed-off-by: Michael Ellerman 
  
  ---uname output---
  Linux tul217p1 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:23:01 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
-  
- Machine Type = FSP based PowerNV system 
-  
+ 
+ Machine Type = FSP based PowerNV system
+ 
  Canonical,
  
  We need this patch in 16.04 GA 4.4 kernel. This fix will avoid the
  following error:
  
  Oct 19 22:15:07 tul217p1 kernel: sched: RT throttling activated
  Oct 19 22:15:49 tul217p1 kernel: INFO: rcu_sched self-detected stall on CPU
  Oct 19 22:15:49 tul217p1 kernel:21-...: (85 GPs behind) 
idle=d29/142/0 softirq=26316/26316 fqs=4417
  Oct 19 22:15:49 tul217p1 kernel: (t=5250 jiffies g=30019 c=30018 
q=20591)
  Oct 19 22:15:49 tul217p1 kernel: Call Trace:
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f110] [c00fcbe0] 
sched_show_task+0xe0/0x180 (unreliable)
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f180] [c013fcf4] 
rcu_dump_cpu_stacks+0xe4/0x150
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f1d0] [c0145424] 
rcu_check_callbacks+0x6b4/0x9b0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f300] [c014d288] 
update_process_times+0x58/0xa0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f330] [c01649b8] 
tick_sched_handle.isra.6+0x48/0xe0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f370] [c0164ab4] 
tick_sched_timer+0x64/0xd0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f3b0] [c014dd54] 
__hrtimer_run_queues+0x124/0x450
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f440] [c014ed7c] 
hrtimer_interrupt+0xec/0x2c0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f500] [c001f5fc] 
__timer_interrupt+0x8c/0x290
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f550] [c001f9b0] 
timer_interrupt+0xa0/0xe0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f580] [c00099d8] 
restore_check_irq_replay+0x54/0x70
  Oct 19 22:15:49 tul217p1 kernel: --- interrupt: 901 at 
arch_local_irq_restore+0x74/0x90
-  LR = arch_local_irq_restore+0x74/0x90
+  LR = arch_local_irq_restore+0x74/0x90
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f870] [7fff] 
0x7fff (unreliable)
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f890] [c00bf808] 
__do_softirq+0xd8/0x3e0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f980] [c00bfd88] 
irq_exit+0xc8/0x100
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f9a0] [c001f9b4] 
timer_interrupt+0xa4/0xe0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f9d0] [c00099d8] 
restore_check_irq_replay+0x54/0x70
  Oct 19 22:15:49 tul217p1 kernel: --- interrupt: 901 at 
irq_work_queue+0x60/0xd0
-  LR = irq_work_queue+0xa4/0xd0
+  LR = irq_work_queue+0xa4/0xd0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0fcc0]