date:20180104

** Description changed:

  [Impact]
  There is a long-standing upstream bug with the ARM64 specific implementation 
of RW locks. The implementation can starve writers under lock contention 
leading to RCU stalls, driver timeouts and general system instability.
  
  [Test Case]
  $ stress-ng --kill 0 -t 300 -v
  
  You'll see the console fill with messages like:
  
  [ 2534.423119] INFO: rcu_sched detected stalls on CPUs/tasks:
  [ 2534.428606]192-...: (1 ticks this GP) idle=b6e/140/0 
softirq=578/578 fqs=6770
  [ 2534.437029](detected by 0, t=15005 jiffies, g=1479, c=1478, q=473)
  [ 2714.623691] INFO: rcu_sched detected stalls on CPUs/tasks:
  [ 2714.629181]192-...: (1 ticks this GP) idle=b6e/140/0 
softirq=578/578 fqs=12819
  [ 2714.637692](detected by 116, t=60058 jiffies, g=1479, c=1478, 
q=1736)
  [ 2747.216955] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[kworker/0:5:1464]
  [ 2775.399061] watchdog: BUG: soft lockup - CPU#13 stuck for 123s! 
[systemd-network:2936]
  
  [Regression Risk]
- TBD
+ The proposed fix for this comprises clean cherry-picks from the v4.15 merge 
window. The code modified for this fix is restricted to x86 & arm64, as they 
are the only Ubuntu architectures that define ARCH_USE_QUEUED_LOCKS. Fix 
verified on a 228 CPU arm64 (ThunderX2) server and regression tested on a 
128-cpu x86 system using stress-ng and locktorture.

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

Title:
  arm64: Unfair rwlock can stall the system

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

Bug description:
  [Impact]
  There is a long-standing upstream bug with the ARM64 specific implementation 
of RW locks. The implementation can starve writers under lock contention 
leading to RCU stalls, driver timeouts and general system instability.

  [Test Case]
  $ stress-ng --kill 0 -t 300 -v

  You'll see the console fill with messages like:

  [ 2534.423119] INFO: rcu_sched detected stalls on CPUs/tasks:
  [ 2534.428606]192-...: (1 ticks this GP) idle=b6e/140/0 
softirq=578/578 fqs=6770
  [ 2534.437029](detected by 0, t=15005 jiffies, g=1479, c=1478, q=473)
  [ 2714.623691] INFO: rcu_sched detected stalls on CPUs/tasks:
  [ 2714.629181]192-...: (1 ticks this GP) idle=b6e/140/0 
softirq=578/578 fqs=12819
  [ 2714.637692](detected by 116, t=60058 jiffies, g=1479, c=1478, 
q=1736)
  [ 2747.216955] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[kworker/0:5:1464]
  [ 2775.399061] watchdog: BUG: soft lockup - CPU#13 stuck for 123s! 
[systemd-network:2936]

  [Regression Risk]
  The proposed fix for this comprises clean cherry-picks from the v4.15 merge 
window. The code modified for this fix is restricted to x86 & arm64, as they 
are the only Ubuntu architectures that define ARCH_USE_QUEUED_LOCKS. Fix 
verified on a 228 CPU arm64 (ThunderX2) server and regression tested on a 
128-cpu x86 system using stress-ng and locktorture.

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

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

[Kernel-packages] [Bug 1737942] Re: linux: 4.10.0-43.47 -proposed tracker

2018-01-04 Thread Steve Beattie

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

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

Title:
  linux: 4.10.0-43.47 -proposed tracker

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

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

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

  backports: 1737944,1737945
  derivatives: 1737946
  -- 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/1737942/+subscriptions

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

[Kernel-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR

2018-01-04 Thread Dimitri John Ledkov

** Summary changed:

- Regression in getaddrinfo(): calls block for much longer on Bionic (compared 
to Xenial)
+ Regression in getaddrinfo(): calls block for much longer on Bionic (compared 
to Xenial), please disable LLMNR

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial), please disable LLMNR

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

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

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

[Kernel-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)

2018-01-04 Thread Dimitri John Ledkov

avahi is zeroconf or IPv4LL, which is RFC 3927; whilst LLMNR is RFC
4795. In many aspects LLMNR is like mdns, yet the two are distinct and
resolve different things quite differently, when inspected closer.


** Changed in: systemd (Ubuntu)
   Status: Confirmed => 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/1739672

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial)

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

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

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

[Kernel-packages] [Bug 1732238] Re: arm64: Unfair rwlock can stall the system

Example showing driver timeouts:

ubuntu@boomer:~$ stress-ng --kill 0 -t 300 -v
stress-ng: debug: [3344] 224 processors online, 224 processors configured
stress-ng: info:  [3344] dispatching hogs: 224 kill
stress-ng: debug: [3344] /sys/devices/system/cpu/cpu0/cache does not exist
stress-ng: info:  [3344] cache allocate: using built-in defaults as unable to 
determine cache details
stress-ng: info:  [3344] cache allocate: default cache size: 2048K
stress-ng: debug: [3344] starting stressors
stress-ng: debug: [3345] stress-ng-kill: started [3345] (instance 0)
stress-ng: debug: [3346] stress-ng-kill: started [3346] (instance 1)
stress-ng: debug: [3347] stress-ng-kill: started [3347] (instance 2)
stress-ng: debug: [3348] stress-ng-kill: started [3348] (instance 3)
stress-ng: debug: [3349] stress-ng-kill: started [3349] (instance 4)
[ 1447.474535] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 1447.480020]  27-...: (66 GPs behind) idle=1ba/140/0 
softirq=3878/3878 fqs=7264 
[ 1447.488363]  136-...: (93 GPs behind) idle=972/140/0 
softirq=2760/2760 fqs=7265 
[ 1447.496788]  (detected by 161, t=15007 jiffies, g=1128, c=1127, q=790)
[ 1451.646152] xhci_hcd :01:04.1: xHCI host controller not responding, 
assume dead
[ 1451.653819] xhci_hcd :01:04.1: HC died; cleaning up
[ 1451.653829] usb 3-1-port1: cannot reset (err = -22)
[ 1451.653832] usb 3-1-port1: cannot reset (err = -22)
[ 1451.653833] usb 3-1-port1: cannot reset (err = -22)
[ 1451.653834] usb 3-1-port1: cannot reset (err = -22)
[ 1451.653835] usb 3-1-port1: cannot reset (err = -22)
[ 1451.653837] usb 3-1-port1: Cannot enable. Maybe the USB cable is bad?
[ 1451.653839] usb 3-1-port1: cannot disable (err = -22)
[ 1451.653848] usb 3-1-port2: cannot reset (err = -22)
[ 1451.653851] usb 3-1-port2: cannot reset (err = -22)
[ 1451.653852] usb 3-1-port2: cannot reset (err = -22)
[ 1451.653854] usb 3-1-port2: cannot reset (err = -22)
[ 1451.653855] usb 3-1-port2: cannot reset (err = -22)
[ 1451.653856] usb 3-1-port2: Cannot enable. Maybe the USB cable is bad?
[ 1451.653858] usb 3-1-port2: cannot disable (err = -22)
[ 1451.653860] usb 3-1-port1: cannot reset (err = -22)
[ 1451.653861] usb 3-1-port1: cannot reset (err = -22)
[ 1451.653862] usb 3-1-port1: cannot reset (err = -22)
[ 1451.653863] usb 3-1-port1: cannot reset (err = -22)
[ 1451.653864] usb 3-1-port1: cannot reset (err = -22)
[ 1451.653865] usb 3-1-port1: Cannot enable. Maybe the USB cable is bad?
[ 1451.653866] usb 3-1-port1: cannot disable (err = -22)
[ 1451.653868] usb 3-1-port2: cannot reset (err = -22)
[ 1451.653870] usb 3-1-port2: cannot reset (err = -22)
[ 1451.653871] usb 3-1-port2: cannot reset (err = -22)
[ 1451.653872] usb 3-1-port2: cannot reset (err = -22)
[ 1451.653873] usb 3-1-port2: cannot reset (err = -22)
[ 1451.653873] usb 3-1-port2: Cannot enable. Maybe the USB cable is bad?
[ 1451.653875] usb 3-1-port2: cannot disable (err = -22)
[ 1451.653876] usb 3-1-port1: cannot reset (err = -22)
[ 1451.653878] usb 3-1-port1: cannot reset (err = -22)
[ 1451.653879] usb 3-1-port1: cannot reset (err = -22)
[ 1451.653880] usb 3-1-port1: cannot reset (err = -22)
[ 1451.653881] usb 3-1-port1: cannot reset (err = -22)
[ 1451.653882] usb 3-1-port1: Cannot enable. Maybe the USB cable is bad?
[ 1451.653883] usb 3-1-port1: cannot disable (err = -22)
[ 1451.653885] usb 3-1-port2: cannot reset (err = -22)
[ 1451.653886] usb 3-1-port2: cannot reset (err = -22)
[ 1451.653887] usb 3-1-port2: cannot reset (err = -22)
[ 1451.653888] usb 3-1-port2: cannot reset (err = -22)
[ 1451.653889] usb 3-1-port2: cannot reset (err = -22)
[ 1451.653890] usb 3-1-port2: Cannot enable. Maybe the USB cable is bad?
[ 1451.653892] usb 3-1-port2: cannot disable (err = -22)
[ 1451.653893] usb 3-1-port1: cannot reset (err = -22)
[ 1451.653895] usb 3-1-port1: cannot reset (err = -22)
[ 1451.653896] usb 3-1-port1: cannot reset (err = -22)
[ 1451.653897] usb 3-1-port1: cannot reset (err = -22)
[ 1451.653898] usb 3-1-port1: cannot reset (err = -22)
[ 1451.653899] usb 3-1-port1: Cannot enable. Maybe the USB cable is bad?
[ 1451.653900] usb 3-1-port1: cannot disable (err = -22)
[ 1451.653902] usb 3-1-port2: cannot reset (err = -22)
[ 1451.653903] usb 3-1-port1: cannot disable (err = -22)
[ 1451.653903] usb 3-1-port2: cannot reset (err = -22)
[ 1451.653905] usb 3-1-port2: cannot reset (err = -22)
[ 1451.653906] usb 3-1-port2: cannot reset (err = -22)
[ 1451.653907] usb 3-1-port2: cannot reset (err = -22)
[ 1451.653908] usb 3-1-port2: Cannot enable. Maybe the USB cable is bad?
[ 1451.653909] usb 3-1-port2: cannot disable (err = -22)
[ 1451.653910] usb 3-1-port2: cannot disable (err = -22)
[ 1451.653920] hub 3-1:1.0: hub_ext_port_status failed (err = -22)
[ 1451.653923] hub 3-1:1.0: hub_ext_port_status failed (err = -22)
[ 1626.734665] INFO: task kworker/u448:0:6 blocked for more than 120 seconds.
[ 1626.741536]   Not tainted 4.13.0-20-generic #23-Ubuntu
[ 1626.747047] "echo 0 >

[Kernel-packages] [Bug 1740175] Re: Ubuntu 17.10 not resuming from suspend, freezing on shut down

2018-01-04 Thread Matt G

So, 'echo freeze | sudo tee /sys/power/state' seems to work quite
smoothly. Is there any reason NOT to use this from here on out instead
of 'systemctl suspend'. Could quite well solve my 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/1740175

Title:
  Ubuntu 17.10 not resuming from suspend, freezing on shut down

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on an Acer Espire with intel microcode running dual boot Xorg
  17.10 using Gnome. I'd say it's usually 50/50 that i'm able to suspend
  and successfully resume. Same goes for shutting down now, where it
  will freeze on the purple Ubuntu screen. When I suspend, the monitor
  will go out but the hard drive will still be running and I have to
  hard power off. Here's a pm-suspend log:

  Initial commandline parameters:
  Fri Dec 22 16:24:14 EST 2017: Running hooks for suspend.
  Running hook /usr/lib/pm-utils/sleep.d/000kernel-change suspend suspend:
  /usr/lib/pm-utils/sleep.d/000kernel-change suspend suspend: success.

  Running hook /usr/lib/pm-utils/sleep.d/000record-status suspend suspend:
  /usr/lib/pm-utils/sleep.d/000record-status suspend suspend: success.

  Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
  Linux qs-ubuntu 4.14.8-041408-generic #201712200555 SMP Wed Dec 20 10:57:38 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  Module  Size  Used by
  msr16384  0
  ccm20480  6
  binfmt_misc20480  1
  nls_iso8859_1  16384  1
  ath3k  20480  0
  uvcvideo   86016  0
  videobuf2_vmalloc  16384  1 uvcvideo
  videobuf2_memops   16384  1 videobuf2_vmalloc
  videobuf2_v4l2 24576  1 uvcvideo
  btusb  45056  0
  btrtl  16384  1 btusb
  videobuf2_core 40960  2 uvcvideo,videobuf2_v4l2
  btbcm  16384  1 btusb
  videodev  176128  3 uvcvideo,videobuf2_core,videobuf2_v4l2
  media  40960  2 uvcvideo,videodev
  cmdlinepart16384  0
  btintel16384  1 btusb
  bluetooth 540672  6 btrtl,btintel,btbcm,ath3k,btusb
  ecdh_generic   24576  1 bluetooth
  intel_spi_platform 16384  0
  intel_spi  20480  1 intel_spi_platform
  spi_nor32768  1 intel_spi
  joydev 20480  0
  mtd57344  4 spi_nor,intel_spi,cmdlinepart
  intel_rapl 20480  0
  x86_pkg_temp_thermal16384  0

  I attached the dmesg.log.

  I'm pretty new to linux, so please let me know if there's another log I 
should get for more details. I upgraded to kernel 4.14.8-041408-generic last 
week, which didn't help.
  ---
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-09-16 (101 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  artful
  Uname: Linux 4.14.8-041408-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to artful on 2017-10-20 (66 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1732238] Re: arm64: Unfair rwlock can stall the system

** Description changed:

  [Impact]
- There is a long-standing upstream bug with the ARM64 specific implementation 
of RW locks. The implementation can starve writers under lock contention 
leading to RCU stalls and general system instability.
+ There is a long-standing upstream bug with the ARM64 specific implementation 
of RW locks. The implementation can starve writers under lock contention 
leading to RCU stalls, driver timeouts and general system instability.
  
  [Test Case]
  $ stress-ng --kill 0 -t 300 -v
  
  You'll see the console fill with messages like:
  
  [ 2534.423119] INFO: rcu_sched detected stalls on CPUs/tasks:
- [ 2534.428606]192-...: (1 ticks this GP) idle=b6e/140/0 
softirq=578/578 fqs=6770 
+ [ 2534.428606]192-...: (1 ticks this GP) idle=b6e/140/0 
softirq=578/578 fqs=6770
  [ 2534.437029](detected by 0, t=15005 jiffies, g=1479, c=1478, q=473)
  [ 2714.623691] INFO: rcu_sched detected stalls on CPUs/tasks:
- [ 2714.629181]192-...: (1 ticks this GP) idle=b6e/140/0 
softirq=578/578 fqs=12819 
+ [ 2714.629181]192-...: (1 ticks this GP) idle=b6e/140/0 
softirq=578/578 fqs=12819
  [ 2714.637692](detected by 116, t=60058 jiffies, g=1479, c=1478, 
q=1736)
  [ 2747.216955] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[kworker/0:5:1464]
  [ 2775.399061] watchdog: BUG: soft lockup - CPU#13 stuck for 123s! 
[systemd-network:2936]
  
  [Regression Risk]
  TBD

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

Title:
  arm64: Unfair rwlock can stall the system

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

Bug description:
  [Impact]
  There is a long-standing upstream bug with the ARM64 specific implementation 
of RW locks. The implementation can starve writers under lock contention 
leading to RCU stalls, driver timeouts and general system instability.

  [Test Case]
  $ stress-ng --kill 0 -t 300 -v

  You'll see the console fill with messages like:

  [ 2534.423119] INFO: rcu_sched detected stalls on CPUs/tasks:
  [ 2534.428606]192-...: (1 ticks this GP) idle=b6e/140/0 
softirq=578/578 fqs=6770
  [ 2534.437029](detected by 0, t=15005 jiffies, g=1479, c=1478, q=473)
  [ 2714.623691] INFO: rcu_sched detected stalls on CPUs/tasks:
  [ 2714.629181]192-...: (1 ticks this GP) idle=b6e/140/0 
softirq=578/578 fqs=12819
  [ 2714.637692](detected by 116, t=60058 jiffies, g=1479, c=1478, 
q=1736)
  [ 2747.216955] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[kworker/0:5:1464]
  [ 2775.399061] watchdog: BUG: soft lockup - CPU#13 stuck for 123s! 
[systemd-network:2936]

  [Regression Risk]
  TBD

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

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

[Kernel-packages] [Bug 1706437] Re: zfs-linux 0.6.5.10-1ubuntu2 ADT test failure with linux 4.13.0-2.3

zfs-linux (0.6.5.11-1ubuntu3) artful; urgency=medium

  * Add 4.13 backported patches from ZFS

 -- Colin Ian King   Wed, 9 Aug 2017 12:57:11
+0100


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

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

Title:
  zfs-linux 0.6.5.10-1ubuntu2 ADT test failure with linux 4.13.0-2.3

Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-bootstrap/artful/amd64/z/zfs-linux/20170725_184030_4a9bf@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-bootstrap/artful/ppc64el/z/zfs-linux/20170725_161556_4a9bf@/log.gz

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

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

[Kernel-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)

2018-01-04 Thread Mike Pontillo

Workaround:

grep -q 'LLMNR=no' /etc/systemd/resolved.conf || \
echo 'LLMNR=no' | sudo tee -a /etc/systemd/resolved.conf
sudo service systemd-networkd restart

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial)

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

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

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

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-01-04 Thread Ben Andersen

Where can I find 17.10 fixed ISOs? If new ones aren't released I'm sure
more people will install the faulty ones.

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

Title:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

---

Test Case: Fix has been verified by our HWE team on affected hardware.

Regression Potential: Minimal, it's unlikely anyone is actually doing
anything which requires this driver.

---

Affected Machines:

---

Original Description:

Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
reported a corrupted BIOS.

It's not possible to save new settings in BIOS anymore and after
rebooting, the system starts with the old settings.

Moreover (and most important) USB booting is not possible anymore
since USB is not recognized. It's very serious, since our machines do
not have a CDROM.

Lenovo forums at the moment are full of topics regading this issue.

Thank you!!

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

[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10

I built the next test kernel, up to the following commit:
e6108d5475696d0deaf37b59ff704aead9c5a8a7

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

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

Title:
  System hang with Linux kernel 4.13, not with 4.10

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe package in Ubuntu:
  New
Status in linux source package in Artful:
  In Progress
Status in linux-hwe source package in Artful:
  New
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  New

Bug description:
  In doing Ubuntu 17.10 regression testing, we've encountered one
  computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in
  four times when running our cpu_offlining test. This test attempts to
  take all the CPU cores offline except one, then brings them back
  online again. This test ran successfully on boldore with previous
  releases, but with 17.10, the system sometimes (about one in four
  runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but
  when I upgraded the 16.04.3 installation to linux-
  image-4.13.0-16-generic, the problem appeared again, so I'm confident
  this is a problem with the kernel. I'm attaching two files, dmesg-
  output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output
  that appears when running the cpu_offlining test with 4.10.0-38 and
  4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I
  was running "dmesg -w" in a second SSH login; the files are cut-and-
  pasted from that.)

  I initiated this bug report from an Ubuntu 16.04.3 installation
  running a 4.10 kernel; but as I said, this applies to the 4.13 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1
  ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Nov 21 17:36:06 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1740309] Re: user space process hangs when reading partition table of disk

2018-01-04 Thread Andreas Pokorny

I made a mistake - the problem also occurs on 4.12.0-041200-generic 
#201707022031
So the problem was added somewhere between 4.11.12 and 4.12.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/1740309

Title:
  user space process hangs when reading partition table of disk

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  user space process as in parted or fdisk or update-grub2 that read partition 
tables freeze on my system:
  /dev/sda/  GPT disk with efi, swap and ubuntu artful partition
  /dev/sdb  old style partition table with one ext4 partition
  /dev/sdc GPT disk with efi partition, windows 10

  I.e. if I run as root :
  # fdisk -l
  Disk /dev/sda: 232,9 GiB, 250059350016 bytes, 488397168 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disklabel type: gpt
  Disk identifier: 56FF6AB0-076F-483C-890F-EC4B4FAF6313

  DeviceStart   End   Sectors   Size Type
  /dev/sda1  2048   2000895   1998848   976M EFI System
  /dev/sda2   2000896  1383   7999488   3,8G Linux swap
  /dev/sda3  1384 488396799 478396416 228,1G Linux filesystem

  Disk /dev/sdb: 489,1 GiB, 525112713216 bytes, 1025610768 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x2f11f9c4

  Device Boot StartEndSectors  Size Id Type
  /dev/sdb12048 1025609727 1025607680  489G 83 Linux
  <...process hangs here forever...>

  With gdb I stepped through fdisk -l and saw that the call to open 
('dev/sdc'..) never returns.
  --
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D3p:   andreas1807 F...m pulseaudio
   /dev/snd/controlC0:  andreas1807 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=8a7a6077-0a3e-4641-8f15-bd6f09826510
  InstallationDate: Installed on 2017-12-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IwConfig:
   lono wireless extensions.

   enp8s0no wireless extensions.

   enp12s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-image-4.13.0-21-generic 4.13.0-21.24
  PackageArchitecture: amd64
  ProcFB:
   0 radeondrmfb
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=4f18ad67-a4f0-4e03-b061-66615751538e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.1
  RfKill:

  Tags:  artful
  Uname: Linux 4.13.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: EP2C602
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd12/09/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnEP2C602:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-01-04 Thread Hernán Alvarez

Kernel from step 8 unlocked the BIOS on my Compal ZAW70 with Insyde
UEFI.

Thanks to everybody involved on fixing this!

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

Title:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

---

Test Case: Fix has been verified by our HWE team on affected hardware.

Regression Potential: Minimal, it's unlikely anyone is actually doing
anything which requires this driver.

---

Affected Machines:

---

Original Description:

Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
reported a corrupted BIOS.

It's not possible to save new settings in BIOS anymore and after
rebooting, the system starts with the old settings.

Moreover (and most important) USB booting is not possible anymore
since USB is not recognized. It's very serious, since our machines do
not have a CDROM.

Lenovo forums at the moment are full of topics regading this issue.

Thank you!!

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

[Kernel-packages] [Bug 1740309] Re: user space process hangs when reading partition table of disk

2018-01-04 Thread Andreas Pokorny

Besides 4.15.0-041500rc6-generic and 4.13 the problem occurs on:

4.12.14-041214-generic #201709200843 SMP Wed Sep 20 12:46:23 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux

but it did not occur on:
4.4.109-0404109-generic #201801022112 SMP Tue Jan 2 21:13:34 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux
4.10.0-041000-generic #201702191831 SMP Sun Feb 19 23:33:19 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
4.11.12-041112-generic #201707210350 SMP Fri Jul 21 07:53:15 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
4.12.0-041200-generic #201707022031 SMP Mon Jul 3 00:32:52 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux

I will jump through the 4.12 builds tomorrow.

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

Title:
  user space process hangs when reading partition table of disk

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  user space process as in parted or fdisk or update-grub2 that read partition 
tables freeze on my system:
  /dev/sda/  GPT disk with efi, swap and ubuntu artful partition
  /dev/sdb  old style partition table with one ext4 partition
  /dev/sdc GPT disk with efi partition, windows 10

  I.e. if I run as root :
  # fdisk -l
  Disk /dev/sda: 232,9 GiB, 250059350016 bytes, 488397168 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disklabel type: gpt
  Disk identifier: 56FF6AB0-076F-483C-890F-EC4B4FAF6313

  DeviceStart   End   Sectors   Size Type
  /dev/sda1  2048   2000895   1998848   976M EFI System
  /dev/sda2   2000896  1383   7999488   3,8G Linux swap
  /dev/sda3  1384 488396799 478396416 228,1G Linux filesystem

  Disk /dev/sdb: 489,1 GiB, 525112713216 bytes, 1025610768 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x2f11f9c4

  Device Boot StartEndSectors  Size Id Type
  /dev/sdb12048 1025609727 1025607680  489G 83 Linux
  <...process hangs here forever...>

  With gdb I stepped through fdisk -l and saw that the call to open 
('dev/sdc'..) never returns.
  --
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D3p:   andreas1807 F...m pulseaudio
   /dev/snd/controlC0:  andreas1807 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=8a7a6077-0a3e-4641-8f15-bd6f09826510
  InstallationDate: Installed on 2017-12-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IwConfig:
   lono wireless extensions.

   enp8s0no wireless extensions.

   enp12s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-image-4.13.0-21-generic 4.13.0-21.24
  PackageArchitecture: amd64
  ProcFB:
   0 radeondrmfb
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=4f18ad67-a4f0-4e03-b061-66615751538e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.1
  RfKill:

  Tags:  artful
  Uname: Linux 4.13.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: EP2C602
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd12/09/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnEP2C602:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1723680] Re: GPU Hang in Xorg rcs0 drm/i915

2018-01-04 Thread themusicgod1

** Tags added: bionic

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

Title:
  GPU Hang in Xorg rcs0 drm/i915

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Zesty:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  Distributor ID:   Ubuntu
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10
  Codename: artful

  When using linux kernel linux-image-4.13.0-12-generic to linux-
  image-4.13.0-16-generic Xorg fails to start with kernel error messages
  below. Kernel boots and displays messages allows for GUI to enter disk
  encryption key then tries to start Xorg login.  Shows blank screen,
  sometimes part of login dialog.  Then hangs and goes blank usually
  showing the low graphics mode error screen from Xorg and no
  functionality after a while.  Can ctrl+alt+f1 to console.  Using
  linux-image-4.10.0-35-generic everything works as expected.  System
  worked without issue with Ubuntu 17.04

  Kernel error messages:
  [   43.836641] [drm] GPU HANG: ecode 8:0:0x00df, in Xorg [1027], reason: 
Hang on rcs0, action: reset
  [   43.836645] [drm] GPU hangs can indicate a bug anywhere in the entire gfx 
stack, including userspace.
  [   43.836646] [drm] Please file a _new_ bug report on bugs.freedesktop.org 
against DRI -> DRM/Intel
  [   43.836647] [drm] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
  [   43.836648] [drm] The gpu crash dump is required to analyze gpu hangs, so 
please always attach it.
  [   43.836649] [drm] GPU crash dump saved to /sys/class/drm/card0/error
  [   43.836718] drm/i915: Resetting chip after gpu hang
  [   55.812149] drm/i915: Resetting chip after gpu hang
  [   63.840645] drm/i915: Resetting chip after gpu hang
  [   71.836614] drm/i915: Resetting chip after gpu hang
  [   79.836882] drm/i915: Resetting chip after gpu hang
  [   88.828508] drm/i915: Resetting chip after gpu hang

  have tried kernel parameter intel_iommu=off, intel_iommu=igfx_off, 
i915.enable_rc6=0 with no better results.
  lshw, dmesg and card0/error file attached.

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

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

[Kernel-packages] [Bug 1737640] Re: [SRU] /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures

2018-01-04 Thread David Britton

** Changed in: ubuntu-fan (Ubuntu Artful)
   Status: Confirmed => Incomplete

** Changed in: ubuntu-fan (Ubuntu Bionic)
   Status: Confirmed => Incomplete

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

Title:
  [SRU] /usr/sbin/fanctl: arithmetic expression: expecting primary |
  unconfigured interfaces cause ifup failures

Status in juju:
  Invalid
Status in OPNFV:
  Fix Committed
Status in ubuntu-fan package in Ubuntu:
  Incomplete
Status in ubuntu-fan source package in Xenial:
  Fix Released
Status in ubuntu-fan source package in Zesty:
  Confirmed
Status in ubuntu-fan source package in Artful:
  Incomplete
Status in ubuntu-fan source package in Bionic:
  Incomplete

Bug description:
  [Impact]

   * This bug effects anyone deploying LXD with juju on a machine with
  interfaces configured as IP/mask. Since this is a very common use
  case, SRU is needed.

  [Test Case]

   * Detailed process can be seen at https://paste.ubuntu.com/26169937/

  [Regression Potential]

   * Potential for regression is low because of the nature of the error.
  It's just missing a case stanza for interfaces that are defined with
  IP/mask

  [Other Info]

   * Original report:

  I'm seeing this error as the status of multiple containers in my
  deploy:

  http://paste.ubuntu.com/26166720/

  I can't connect to the parent machines anymore either - it seems
  networking is totally hosed on the machines.

  This is with juju 2.3.1.

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

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

[Kernel-packages] [Bug 1740309] Re: user space process hangs when reading partition table of disk

2018-01-04 Thread Andreas Pokorny

The problem still exists with  4.15.0-041500rc6-generic

Prior versions were also affected. I initially suspected faulty
hardware, and for months did not care about the contents of the disks. I
only looked back at the problem when I finally replaced the hard disk.
At least with 4.12 the problem also occurred.

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

Title:
  user space process hangs when reading partition table of disk

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  user space process as in parted or fdisk or update-grub2 that read partition 
tables freeze on my system:
  /dev/sda/  GPT disk with efi, swap and ubuntu artful partition
  /dev/sdb  old style partition table with one ext4 partition
  /dev/sdc GPT disk with efi partition, windows 10

  I.e. if I run as root :
  # fdisk -l
  Disk /dev/sda: 232,9 GiB, 250059350016 bytes, 488397168 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disklabel type: gpt
  Disk identifier: 56FF6AB0-076F-483C-890F-EC4B4FAF6313

  DeviceStart   End   Sectors   Size Type
  /dev/sda1  2048   2000895   1998848   976M EFI System
  /dev/sda2   2000896  1383   7999488   3,8G Linux swap
  /dev/sda3  1384 488396799 478396416 228,1G Linux filesystem

  Disk /dev/sdb: 489,1 GiB, 525112713216 bytes, 1025610768 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x2f11f9c4

  Device Boot StartEndSectors  Size Id Type
  /dev/sdb12048 1025609727 1025607680  489G 83 Linux
  <...process hangs here forever...>

  With gdb I stepped through fdisk -l and saw that the call to open 
('dev/sdc'..) never returns.
  --
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D3p:   andreas1807 F...m pulseaudio
   /dev/snd/controlC0:  andreas1807 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=8a7a6077-0a3e-4641-8f15-bd6f09826510
  InstallationDate: Installed on 2017-12-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IwConfig:
   lono wireless extensions.

   enp8s0no wireless extensions.

   enp12s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-image-4.13.0-21-generic 4.13.0-21.24
  PackageArchitecture: amd64
  ProcFB:
   0 radeondrmfb
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=4f18ad67-a4f0-4e03-b061-66615751538e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.1
  RfKill:

  Tags:  artful
  Uname: Linux 4.13.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: EP2C602
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd12/09/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnEP2C602:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10

2018-01-04 Thread Rod Smith

Joseph, that one also completed six runs with no problems except the
"error -19" messages.

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

Title:
  System hang with Linux kernel 4.13, not with 4.10

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe package in Ubuntu:
  New
Status in linux source package in Artful:
  In Progress
Status in linux-hwe source package in Artful:
  New
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  New

Bug description:
  In doing Ubuntu 17.10 regression testing, we've encountered one
  computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in
  four times when running our cpu_offlining test. This test attempts to
  take all the CPU cores offline except one, then brings them back
  online again. This test ran successfully on boldore with previous
  releases, but with 17.10, the system sometimes (about one in four
  runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but
  when I upgraded the 16.04.3 installation to linux-
  image-4.13.0-16-generic, the problem appeared again, so I'm confident
  this is a problem with the kernel. I'm attaching two files, dmesg-
  output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output
  that appears when running the cpu_offlining test with 4.10.0-38 and
  4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I
  was running "dmesg -w" in a second SSH login; the files are cut-and-
  pasted from that.)

  I initiated this bug report from an Ubuntu 16.04.3 installation
  running a 4.10 kernel; but as I said, this applies to the 4.13 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1
  ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Nov 21 17:36:06 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure

2018-01-04 Thread Bryan

I just ran into this issue (2018-01-04) on Amazon AWS.  The nvme drive was not 
detected on Amazon's Ubunto 16.04.  Fixed after running 
apt-get update
apt-get upgrade
apt-get dist-upgrade
reboot.

dist-upgrade seems to be the key.  lsb_release -a says 16.04.03 now.

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

Title:
  nvme drive probe failure

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  After upgrading from linux-image-4.4.0-38-generic to proposed update
  linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg
  shows a probe failure.

  On the previous kernel version everything is working as expected.
  ->%-
  [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 
R1.12.0.SR.2 for D3417-B1x   04/01/2016
  [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme]
  [1.005484]  0286 b6c91251 880fe6e8bce0 
813f1f83
  [1.005800]  880fe02150f0 c90006a7c000 880fe6e8bd00 
8106bdff
  [1.006117]  880fe02150f0 880fe0215258 880fe6e8bd10 
8106be3c
  [1.006433] Call Trace:
  [1.006509]  [] dump_stack+0x63/0x90
  [1.006589]  [] iounmap.part.1+0x7f/0x90
  [1.006668]  [] iounmap+0x2c/0x30
  [1.006770]  [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme]
  [1.007048]  [] nvme_remove+0xce/0xe0 [nvme]
  [1.007140]  [] pci_device_remove+0x39/0xc0
  [1.007220]  [] __device_release_driver+0xa1/0x150
  [1.007301]  [] device_release_driver+0x23/0x30
  [1.007382]  [] pci_stop_bus_device+0x8a/0xa0
  [1.007462]  [] 
pci_stop_and_remove_bus_device_locked+0x1a/0x30
  [1.007559]  [] nvme_remove_dead_ctrl_work+0x3c/0x50 
[nvme]
  [1.007642]  [] process_one_work+0x165/0x480
  [1.007722]  [] worker_thread+0x4b/0x4c0
  [1.007801]  [] ? process_one_work+0x480/0x480
  [1.007881]  [] kthread+0xd8/0xf0
  [1.007959]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008041]  [] ret_from_fork+0x3f/0x70
  [1.008120]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008222] Trying to free nonexistent resource 

  [1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 
(timer)
  [1.008281] Trying to free nonexistent resource 

  [1.008282] nvme :02:00.0: Removing after probe failure
  [1.008645] Trying to free nonexistent resource 

  [1.027213] iounmap: bad address c90006ae
  [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic 
#59-Ubuntu
  -%<-

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

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

[Kernel-packages] [Bug 1581799] Re: radeon driver hangs : nothing else that static effect on display

2018-01-04 Thread magowiz

upstream bug : https://bugs.freedesktop.org/show_bug.cgi?id=104497

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

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

Title:
  radeon driver hangs : nothing else that static effect on display

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hi,
  since upgrade from ubuntu 15.10 to 16.04 I was unable to use mine videocard 
due to drop support of fglrx driver (that was working) and due to radeon 
opensource driver not working with my VGA.

  Mine video card:
  $ lspci -nn | grep VGA
  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Sumo [Radeon HD 6410D] [1002:9645]

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

  I'll attach further files (dmesg.log , version.log, lspci-vnvn.log) .
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   magowiz4930 F...m pulseaudio
   /dev/snd/pcmC0D0p:   magowiz4930 F...m pulseaudio
   /dev/snd/controlC0:  magowiz4930 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=472405e9-ecbe-44ee-9931-9eedcc0a759a
  InstallationDate: Installed on 2012-01-03 (1615 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=acd61f09-2fc9-4a54-bf0b-23f0a297d2e4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-26 (40 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  _MarkForUpload: True
  dmi.bios.date: 12/09/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1003
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F1A55-M LE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1003:bd12/09/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF1A55-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1737640] Re: [SRU] /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures

2018-01-04 Thread Andreas Hasenack

I mean, I can see the error in netplan systems like artful, but maybe
the impact there is different and local to ubuntu-fan only:

root@04-57:~# fanctl up -a
/usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting 
primary: " (32-)/4 "

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

Title:
  [SRU] /usr/sbin/fanctl: arithmetic expression: expecting primary |
  unconfigured interfaces cause ifup failures

Status in juju:
  Invalid
Status in OPNFV:
  Fix Committed
Status in ubuntu-fan package in Ubuntu:
  Confirmed
Status in ubuntu-fan source package in Xenial:
  Fix Released
Status in ubuntu-fan source package in Zesty:
  Confirmed
Status in ubuntu-fan source package in Artful:
  Confirmed
Status in ubuntu-fan source package in Bionic:
  Confirmed

Bug description:
  [Impact]

   * This bug effects anyone deploying LXD with juju on a machine with
  interfaces configured as IP/mask. Since this is a very common use
  case, SRU is needed.

  [Test Case]

   * Detailed process can be seen at https://paste.ubuntu.com/26169937/

  [Regression Potential]

   * Potential for regression is low because of the nature of the error.
  It's just missing a case stanza for interfaces that are defined with
  IP/mask

  [Other Info]

   * Original report:

  I'm seeing this error as the status of multiple containers in my
  deploy:

  http://paste.ubuntu.com/26166720/

  I can't connect to the parent machines anymore either - it seems
  networking is totally hosed on the machines.

  This is with juju 2.3.1.

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

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

[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10

The bisect should only require testing about 2 or 3 more kernels.

I built the next test kernel, up to the following commit:
aa0998e265482fd260b188dea8c03e7dd7c83c72

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

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

Title:
  System hang with Linux kernel 4.13, not with 4.10

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe package in Ubuntu:
  New
Status in linux source package in Artful:
  In Progress
Status in linux-hwe source package in Artful:
  New
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  New

Bug description:
  In doing Ubuntu 17.10 regression testing, we've encountered one
  computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in
  four times when running our cpu_offlining test. This test attempts to
  take all the CPU cores offline except one, then brings them back
  online again. This test ran successfully on boldore with previous
  releases, but with 17.10, the system sometimes (about one in four
  runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but
  when I upgraded the 16.04.3 installation to linux-
  image-4.13.0-16-generic, the problem appeared again, so I'm confident
  this is a problem with the kernel. I'm attaching two files, dmesg-
  output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output
  that appears when running the cpu_offlining test with 4.10.0-38 and
  4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I
  was running "dmesg -w" in a second SSH login; the files are cut-and-
  pasted from that.)

  I initiated this bug report from an Ubuntu 16.04.3 installation
  running a 4.10 kernel; but as I said, this applies to the 4.13 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1
  ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Nov 21 17:36:06 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1737640] Re: [SRU] /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures

2018-01-04 Thread Andreas Hasenack

I can see that ubuntu-fan in zesty, artful and bionic needs this patch,
but I can't determine if it's actually hit by this bug.

artful, for example, will use netplan in a fresh install, not e-n-i. Are
these releases really affected by this bug?

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

Title:
  [SRU] /usr/sbin/fanctl: arithmetic expression: expecting primary |
  unconfigured interfaces cause ifup failures

Status in juju:
  Invalid
Status in OPNFV:
  Fix Committed
Status in ubuntu-fan package in Ubuntu:
  Confirmed
Status in ubuntu-fan source package in Xenial:
  Fix Released
Status in ubuntu-fan source package in Zesty:
  Confirmed
Status in ubuntu-fan source package in Artful:
  Confirmed
Status in ubuntu-fan source package in Bionic:
  Confirmed

Bug description:
  [Impact]

   * This bug effects anyone deploying LXD with juju on a machine with
  interfaces configured as IP/mask. Since this is a very common use
  case, SRU is needed.

  [Test Case]

   * Detailed process can be seen at https://paste.ubuntu.com/26169937/

  [Regression Potential]

   * Potential for regression is low because of the nature of the error.
  It's just missing a case stanza for interfaces that are defined with
  IP/mask

  [Other Info]

   * Original report:

  I'm seeing this error as the status of multiple containers in my
  deploy:

  http://paste.ubuntu.com/26166720/

  I can't connect to the parent machines anymore either - it seems
  networking is totally hosed on the machines.

  This is with juju 2.3.1.

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

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

[Kernel-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)

** Tags removed: 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/1739672

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial)

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

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

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

[Kernel-packages] [Bug 1740316] Re: EDAC sbridge: Failed to register device with error -19

2018-01-04 Thread Fawzi Masri

one more observation with 4.15.  it does hang on shutdown.
if i do shutdown -h now or shutdown -r now, the system does not reboot.
it stops at [ ok ] Reached target shutdown.  At which time my server fans kicks 
in like mad, so i manually cold boot it but i never waited for it more than 
5 min.  whether it would stop if i have waited longer, i don't know, but did 
not want to risk it considering how loud my fans were.

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

Title:
  EDAC sbridge: Failed to register device with error -19

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This resembles an error with same title except for error -22.

  I am not savy enough to know if it is the same or different. But since
  it is happening in linux version that is supposedly fixed i thought i
  report it.

  here is some info:
  1- This shows up on loading Ubuntu... repeatable always.
  2- exact error:
  [8.89..] EDAC sbridge: some needed devices are missing
  [8.89..] EDAC sbridge: Couldn't find mci handler
  [8.89..] EDAC sbridge: Couldn't find mci handler
  [8.89..] EDAC sbridge: Failed to register device with error -19
  [FAILED] Failed to start Network Manager Wait Online.
  see 'systemctl status NetworkManager-wait-online.service' for details.
  [] A Start Job is running for Raise network interfaces (38s / 5min 5s)...

  3- Hardware: HP Proliant DL380 with 4 gigabit Ethernet ports
  2x E52620 cpus
  32Gig RAM

  4- OS: Ubuntu 17.10.  however, this is an update from an installed 17.04.
  sudo lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 17.10
  Release:17.10
  Codename:   artful

  
  5- Linux:uname -r
  4.13.0-21-generic

  
  6-  Boot: sudo cat /boot/config-4.13.0-21-generic | grep EDAC
  CONFIG_EDAC_ATOMIC_SCRUB=y
  CONFIG_EDAC_SUPPORT=y
  CONFIG_EDAC=y
  # CONFIG_EDAC_LEGACY_SYSFS is not set
  # CONFIG_EDAC_DEBUG is not set
  CONFIG_EDAC_DECODE_MCE=m
  # CONFIG_EDAC_GHES is not set
  CONFIG_EDAC_AMD64=m
  # CONFIG_EDAC_AMD64_ERROR_INJECTION is not set
  CONFIG_EDAC_E752X=m
  CONFIG_EDAC_I82975X=m
  CONFIG_EDAC_I3000=m
  CONFIG_EDAC_I3200=m
  CONFIG_EDAC_IE31200=m
  CONFIG_EDAC_X38=m
  CONFIG_EDAC_I5400=m
  CONFIG_EDAC_I7CORE=m
  CONFIG_EDAC_I5000=m
  CONFIG_EDAC_I5100=m
  CONFIG_EDAC_I7300=m
  CONFIG_EDAC_SBRIDGE=m
  CONFIG_EDAC_SKX=m
  CONFIG_EDAC_PND2=m

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-21-generic 4.13.0-21.24
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Dec 27 14:37:48 2017
  InstallationDate: Installed on 2017-09-29 (89 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: HP ProLiant DL380 Gen9
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=1d02ee8d-fa4b-4287-991b-8a67bbf54cbf ro quiet intel_iommu=on
  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.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-12-23 (4 days ago)
  dmi.bios.date: 09/13/2016
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL380 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd09/13/2016:svnHP:pnProLiantDL380Gen9:pvr:rvnHP:rnProLiantDL380Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL380 Gen9
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel oops destroying interfaces on i386

I'm attempting to reproduce the bug.  However, I get a hang when I run the 
following:
$ autopkgtest-buildvm-ubuntu-cloud -a i386 -r artful -s 10G

Attached is a screen shot of the hang.  It seems to be trying to boot
the image.

** Attachment added: "hang.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+attachment/5031209/+files/hang.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/1736390

Title:
  openvswitch: kernel oops destroying interfaces on i386

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

Bug description:
  Reproducable on bionic using the autopkgtest's from openvswitch on
  i386:

  [   41.420568] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   41.421000] IP: igmp_group_dropped+0x21/0x220
  [   41.421246] *pdpt = 1d62c001 *pde =  

  [   41.421659] Oops:  [#1] SMP
  [   41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass 
input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg 
mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse 
virtio_blk virtio_net pata_acpi floppy
  [   41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW   
4.13.0-18-generic #21-Ubuntu
  [   41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [   41.424849] Workqueue: netns cleanup_net
  [   41.425071] task: db8fba80 task.stack: dba1
  [   41.425346] EIP: igmp_group_dropped+0x21/0x220
  [   41.425656] EFLAGS: 00010202 CPU: 0
  [   41.425864] EAX:  EBX: dd726360 ECX: dba11e6c EDX: 0002
  [   41.426335] ESI:  EDI: dd4db500 EBP: dba11dcc ESP: dba11d94
  [   41.426687]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   41.426990] CR0: 80050033 CR2:  CR3: 1e6d6d60 CR4: 06f0
  [   41.427340] Call Trace:
  [   41.427485]  ? __wake_up+0x36/0x40
  [   41.427680]  ip_mc_down+0x27/0x90
  [   41.427869]  inetdev_event+0x398/0x4e0
  [   41.428082]  ? skb_dequeue+0x5b/0x70
  [   41.428286]  ? wireless_nlevent_flush+0x4c/0x90
  [   41.428541]  notifier_call_chain+0x4e/0x70
  [   41.428772]  raw_notifier_call_chain+0x11/0x20
  [   41.429023]  call_netdevice_notifiers_info+0x2a/0x60
  [   41.429301]  dev_close_many+0x9d/0xe0
  [   41.429509]  rollback_registered_many+0xd7/0x380
  [   41.429768]  unregister_netdevice_many.part.102+0x10/0x80
  [   41.430075]  default_device_exit_batch+0x134/0x160
  [   41.430344]  ? do_wait_intr_irq+0x80/0x80
  [   41.430650]  ops_exit_list.isra.8+0x4d/0x60
  [   41.430886]  cleanup_net+0x18e/0x260
  [   41.431090]  process_one_work+0x1a0/0x390
  [   41.431317]  worker_thread+0x37/0x450
  [   41.431525]  kthread+0xf3/0x110
  [   41.431714]  ? process_one_work+0x390/0x390
  [   41.431941]  ? kthread_create_on_node+0x20/0x20
  [   41.432187]  ret_from_fork+0x19/0x24
  [   41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 
56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 
8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00
  [   41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94
  [   41.433750] CR2: 
  [   41.433961] ---[ end trace 595db54cab84070c ]---

  
  system then becomes unresponsive; no further interfaces can be created.

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

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

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel oops destroying interfaces on i386

Also, I'm trying to run this on a VM instead of bare hardware.  Could
that be an 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/1736390

Title:
  openvswitch: kernel oops destroying interfaces on i386

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

Bug description:
  Reproducable on bionic using the autopkgtest's from openvswitch on
  i386:

  [   41.420568] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   41.421000] IP: igmp_group_dropped+0x21/0x220
  [   41.421246] *pdpt = 1d62c001 *pde =  

  [   41.421659] Oops:  [#1] SMP
  [   41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass 
input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg 
mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse 
virtio_blk virtio_net pata_acpi floppy
  [   41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW   
4.13.0-18-generic #21-Ubuntu
  [   41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [   41.424849] Workqueue: netns cleanup_net
  [   41.425071] task: db8fba80 task.stack: dba1
  [   41.425346] EIP: igmp_group_dropped+0x21/0x220
  [   41.425656] EFLAGS: 00010202 CPU: 0
  [   41.425864] EAX:  EBX: dd726360 ECX: dba11e6c EDX: 0002
  [   41.426335] ESI:  EDI: dd4db500 EBP: dba11dcc ESP: dba11d94
  [   41.426687]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   41.426990] CR0: 80050033 CR2:  CR3: 1e6d6d60 CR4: 06f0
  [   41.427340] Call Trace:
  [   41.427485]  ? __wake_up+0x36/0x40
  [   41.427680]  ip_mc_down+0x27/0x90
  [   41.427869]  inetdev_event+0x398/0x4e0
  [   41.428082]  ? skb_dequeue+0x5b/0x70
  [   41.428286]  ? wireless_nlevent_flush+0x4c/0x90
  [   41.428541]  notifier_call_chain+0x4e/0x70
  [   41.428772]  raw_notifier_call_chain+0x11/0x20
  [   41.429023]  call_netdevice_notifiers_info+0x2a/0x60
  [   41.429301]  dev_close_many+0x9d/0xe0
  [   41.429509]  rollback_registered_many+0xd7/0x380
  [   41.429768]  unregister_netdevice_many.part.102+0x10/0x80
  [   41.430075]  default_device_exit_batch+0x134/0x160
  [   41.430344]  ? do_wait_intr_irq+0x80/0x80
  [   41.430650]  ops_exit_list.isra.8+0x4d/0x60
  [   41.430886]  cleanup_net+0x18e/0x260
  [   41.431090]  process_one_work+0x1a0/0x390
  [   41.431317]  worker_thread+0x37/0x450
  [   41.431525]  kthread+0xf3/0x110
  [   41.431714]  ? process_one_work+0x390/0x390
  [   41.431941]  ? kthread_create_on_node+0x20/0x20
  [   41.432187]  ret_from_fork+0x19/0x24
  [   41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 
56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 
8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00
  [   41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94
  [   41.433750] CR2: 
  [   41.433961] ---[ end trace 595db54cab84070c ]---

  
  system then becomes unresponsive; no further interfaces can be created.

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

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

[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10

2018-01-04 Thread Rod Smith

Thanks, Joseph. My break was good; I hope yours was, too!

That latest version you posted completed half a dozen runs of the test
script without incident, aside from the "error -19" messages.

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

Title:
  System hang with Linux kernel 4.13, not with 4.10

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe package in Ubuntu:
  New
Status in linux source package in Artful:
  In Progress
Status in linux-hwe source package in Artful:
  New
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  New

Bug description:
  In doing Ubuntu 17.10 regression testing, we've encountered one
  computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in
  four times when running our cpu_offlining test. This test attempts to
  take all the CPU cores offline except one, then brings them back
  online again. This test ran successfully on boldore with previous
  releases, but with 17.10, the system sometimes (about one in four
  runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but
  when I upgraded the 16.04.3 installation to linux-
  image-4.13.0-16-generic, the problem appeared again, so I'm confident
  this is a problem with the kernel. I'm attaching two files, dmesg-
  output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output
  that appears when running the cpu_offlining test with 4.10.0-38 and
  4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I
  was running "dmesg -w" in a second SSH login; the files are cut-and-
  pasted from that.)

  I initiated this bug report from an Ubuntu 16.04.3 installation
  running a 4.10 kernel; but as I said, this applies to the 4.13 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1
  ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Nov 21 17:36:06 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-01-04 Thread Sachin Anand

Some automatic updates came which I installed and now I am able to
access and change settings of BIOS. Also it is recognising bootable USB
drive(with Windows OS). Have not yet changed from Ubuntu, later will
see. Thank you guys for working things out. "Lenovo Y500 45Q"

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

Title:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

---

Test Case: Fix has been verified by our HWE team on affected hardware.

Regression Potential: Minimal, it's unlikely anyone is actually doing
anything which requires this driver.

---

Affected Machines:

---

Original Description:

Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
reported a corrupted BIOS.

It's not possible to save new settings in BIOS anymore and after
rebooting, the system starts with the old settings.

Moreover (and most important) USB booting is not possible anymore
since USB is not recognized. It's very serious, since our machines do
not have a CDROM.

Lenovo forums at the moment are full of topics regading this issue.

Thank you!!

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

[Kernel-packages] [Bug 1740316] Re: EDAC sbridge: Failed to register device with error -19

2018-01-04 Thread Fawzi Masri

'kernel-fixed-upstream'

To answer your questions:
1- I noticed this error after i upgraded from Ubuntu 17.04 to 17.10... namely 
because my server did not boot properly. The reason for it not booting properly 
was not related to this, as i later found out so i cannot guarantee that 
this error was not present in Ubuntu 17.04.  But it is worth trying to see if 
this error require your attention. It has to do with Ethernet interfaces 
dedicated to guest VMs.  i will submit a different report on it.

2- i tested v4.15 per your request.  i tested both -generic and -lowlatency, 
both were successful.  However, there is one error that shows up during boot.  
maybe it is related to something else.
[FAILED] Failed to start AppArmor initialization.
See ' sudo systemctl status apparmor.service'
Here is that output:
● apparmor.service - AppArmor initialization
   Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Thu 2018-01-04 10:48:43 PST; 3min 
45s ago
 Docs: man:apparmor(7)
   http://wiki.apparmor.net/
  Process: 1198 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)
 Main PID: 1198 (code=exited, status=123)

Jan 04 10:48:43 kds-vh-srvr apparmor[1198]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor in 
/etc/apparmor.d
Jan 04 10:48:43 kds-vh-srvr apparmor[1198]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
Jan 04 10:48:43 kds-vh-srvr apparmor[1198]: AppArmor parser error for 
/etc/apparmor.d/usr.bin.webbrowser-app in 
/etc/apparmor.d/usr.bin.webbrowser-app a
Jan 04 10:48:43 kds-vh-srvr apparmor[1198]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor in 
/etc/apparmor.d
Jan 04 10:48:43 kds-vh-srvr apparmor[1198]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
Jan 04 10:48:43 kds-vh-srvr apparmor[1198]:...fail!
Jan 04 10:48:43 kds-vh-srvr systemd[1]: apparmor.service: Main process exited, 
code=exited, status=123/n/a
Jan 04 10:48:43 kds-vh-srvr systemd[1]: Failed to start AppArmor initialization.
Jan 04 10:48:43 kds-vh-srvr systemd[1]: apparmor.service: Unit entered failed 
state.
Jan 04 10:48:43 kds-vh-srvr systemd[1]: apparmor.service: Failed with result 
'exit-code'.
lines 1-18/18 (END)

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

Title:
  EDAC sbridge: Failed to register device with error -19

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This resembles an error with same title except for error -22.

  I am not savy enough to know if it is the same or different. But since
  it is happening in linux version that is supposedly fixed i thought i
  report it.

  here is some info:
  1- This shows up on loading Ubuntu... repeatable always.
  2- exact error:
  [8.89..] EDAC sbridge: some needed devices are missing
  [8.89..] EDAC sbridge: Couldn't find mci handler
  [8.89..] EDAC sbridge: Couldn't find mci handler
  [8.89..] EDAC sbridge: Failed to register device with error -19
  [FAILED] Failed to start Network Manager Wait Online.
  see 'systemctl status NetworkManager-wait-online.service' for details.
  [] A Start Job is running for Raise network interfaces (38s / 5min 5s)...

  3- Hardware: HP Proliant DL380 with 4 gigabit Ethernet ports
  2x E52620 cpus
  32Gig RAM

  4- OS: Ubuntu 17.10.  however, this is an update from an installed 17.04.
  sudo lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 17.10
  Release:17.10
  Codename:   artful

  
  5- Linux:uname -r
  4.13.0-21-generic

  
  6-  Boot: sudo cat /boot/config-4.13.0-21-generic | grep EDAC
  CONFIG_EDAC_ATOMIC_SCRUB=y
  CONFIG_EDAC_SUPPORT=y
  CONFIG_EDAC=y
  # CONFIG_EDAC_LEGACY_SYSFS is not set
  # CONFIG_EDAC_DEBUG is not set
  CONFIG_EDAC_DECODE_MCE=m
  # CONFIG_EDAC_GHES is not set
  CONFIG_EDAC_AMD64=m
  # CONFIG_EDAC_AMD64_ERROR_INJECTION is not set
  CONFIG_EDAC_E752X=m
  CONFIG_EDAC_I82975X=m
  CONFIG_EDAC_I3000=m
  CONFIG_EDAC_I3200=m
  CONFIG_EDAC_IE31200=m
  CONFIG_EDAC_X38=m
  CONFIG_EDAC_I5400=m
  CONFIG_EDAC_I7CORE=m
  CONFIG_EDAC_I5000=m
  CONFIG_EDAC_I5100=m
  CONFIG_EDAC_I7300=m
  CONFIG_EDAC_SBRIDGE=m
  CONFIG_EDAC_SKX=m
  CONFIG_EDAC_PND2=m

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-21-generic 4.13.0-21.24
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Dec 27 14:37:48 2017
  InstallationDate: Installed on 2017-09-29 (89 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: HP ProLiant

[Kernel-packages] [Bug 1740316] Re: EDAC sbridge: Failed to register device with error -19

2018-01-04 Thread Fawzi Masri

one question, which version should i be using , -generic or -lowlatency?

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

Title:
  EDAC sbridge: Failed to register device with error -19

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This resembles an error with same title except for error -22.

  I am not savy enough to know if it is the same or different. But since
  it is happening in linux version that is supposedly fixed i thought i
  report it.

  here is some info:
  1- This shows up on loading Ubuntu... repeatable always.
  2- exact error:
  [8.89..] EDAC sbridge: some needed devices are missing
  [8.89..] EDAC sbridge: Couldn't find mci handler
  [8.89..] EDAC sbridge: Couldn't find mci handler
  [8.89..] EDAC sbridge: Failed to register device with error -19
  [FAILED] Failed to start Network Manager Wait Online.
  see 'systemctl status NetworkManager-wait-online.service' for details.
  [] A Start Job is running for Raise network interfaces (38s / 5min 5s)...

  3- Hardware: HP Proliant DL380 with 4 gigabit Ethernet ports
  2x E52620 cpus
  32Gig RAM

  4- OS: Ubuntu 17.10.  however, this is an update from an installed 17.04.
  sudo lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 17.10
  Release:17.10
  Codename:   artful

  
  5- Linux:uname -r
  4.13.0-21-generic

  
  6-  Boot: sudo cat /boot/config-4.13.0-21-generic | grep EDAC
  CONFIG_EDAC_ATOMIC_SCRUB=y
  CONFIG_EDAC_SUPPORT=y
  CONFIG_EDAC=y
  # CONFIG_EDAC_LEGACY_SYSFS is not set
  # CONFIG_EDAC_DEBUG is not set
  CONFIG_EDAC_DECODE_MCE=m
  # CONFIG_EDAC_GHES is not set
  CONFIG_EDAC_AMD64=m
  # CONFIG_EDAC_AMD64_ERROR_INJECTION is not set
  CONFIG_EDAC_E752X=m
  CONFIG_EDAC_I82975X=m
  CONFIG_EDAC_I3000=m
  CONFIG_EDAC_I3200=m
  CONFIG_EDAC_IE31200=m
  CONFIG_EDAC_X38=m
  CONFIG_EDAC_I5400=m
  CONFIG_EDAC_I7CORE=m
  CONFIG_EDAC_I5000=m
  CONFIG_EDAC_I5100=m
  CONFIG_EDAC_I7300=m
  CONFIG_EDAC_SBRIDGE=m
  CONFIG_EDAC_SKX=m
  CONFIG_EDAC_PND2=m

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-21-generic 4.13.0-21.24
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Dec 27 14:37:48 2017
  InstallationDate: Installed on 2017-09-29 (89 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: HP ProLiant DL380 Gen9
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=1d02ee8d-fa4b-4287-991b-8a67bbf54cbf ro quiet intel_iommu=on
  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.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-12-23 (4 days ago)
  dmi.bios.date: 09/13/2016
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL380 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd09/13/2016:svnHP:pnProLiantDL380Gen9:pvr:rvnHP:rnProLiantDL380Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL380 Gen9
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://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 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

On Thu, Jan 04, 2018 at 05:55:05PM -, Paul wrote:
> Hi, I've seen the solution that Anthony posted and I'm grateful, but I
> have a few questions.

> 1/ If it's as simple as updating/replacing the kernel, why hasn't this
> fix been rolled out as a system/software update?

A kernel has been rolled out as an update in artful-updates which no longer
triggers this issue. The kernel changes that enable on-line recovery of
affected systems are still being evaluated for their correctness, based in
part on feedback here in this bug; they also rely on keeping the spi driver
enabled in the kernel, which carries risk of misconfiguring systems of other
users who have not yet been affected.

The plan for addressing this bug is:

- protect not-yet-affected users from installing the triggering kernel,
through providing a fixed kernel in artful-updates and discouraging use
of the existing 17.10 images (done)
- provide updated 17.10 images for all flavors which include a fixed
kernel.
- provide kernel packages to affected users that enable online recovery
where possible.
- provide documentation to assist users who no longer have Ubuntu installed
in recovering their system with the aid of a second computer.

> 3/ a/ Has the download been updated with a non-broken kernel? b/ This
> debacle has allowed a lot of system degradation to take place on my
> system to the point that I need to reinstall 17.10, this doesn't seem to
> be a possibility right now, or am I wrong?

I do not know what "system degradation" you refer to that would be related
to this bug and would warrant a reinstallation. If you need to reinstall
currently, the supported path is to install either Ubuntu 16.04 LTS or
Ubuntu 17.04 and upgrade.

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

Title:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

---

Test Case: Fix has been verified by our HWE team on affected hardware.

Regression Potential: Minimal, it's unlikely anyone is actually doing
anything which requires this driver.

---

Affected Machines:

---

Affected serial flash

[Kernel-packages] [Bug 1740906] Re: package linux-image-4.13.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

2018-01-04 Thread axt

What a cruel editor. The 1st is 1 line:

sudo sed -i 's/GRUB_CMDLINE_LINUX=""/GRUB_CMDLINE_LINUX="forcepae"/g'
/etc/default/grub

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

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Fresh install Lubuntu 17.10 desktop i386.  Dell Latitude D600.
  Defaults on install except having to "forcepae" on boot.  "apt --fix-
  broken install" gives the following errors -

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following additional packages will be installed:
linux-image-4.13.0-21-generic
  Suggested packages:
fdutils linux-doc-4.13.0 | linux-source-4.13.0 linux-tools
  The following NEW packages will be installed:
linux-image-4.13.0-21-generic
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  88 not fully installed or removed.
  Need to get 19.3 MB of archives.
  After this operation, 50.7 MB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://us.archive.ubuntu.com/ubuntu artful-updates/main i386 
linux-image-4.13.0-21-generic i386 4.13.0-21.24 [19.3 MB]
  Fetched 19.3 MB in 4s (4,423 kB/s)
  (Reading database ... 146408 files and directories currently installed.)
  Preparing to unpack .../linux-image-4.13.0-21-generic_4.13.0-21.24_i386.deb 
...
  This kernel does not support a non-PAE CPU.
  dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.13.0-21-generic_4.13.0-21.24_i386.deb 
(--unpack):
   subprocess new pre-installation script returned error exit status 1
  Examining /etc/kernel/postrm.d .
  run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.13.0-21-generic 
/boot/vmlinuz-4.13.0-21-generic
  run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.13.0-21-generic 
/boot/vmlinuz-4.13.0-21-generic
  Errors were encountered while processing:
   /var/cache/apt/archives/linux-image-4.13.0-21-generic_4.13.0-21.24_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-21-generic (not installed)
  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.
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tcs1104 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with STAC9750,51 at irq 5'
 Mixer name : 'SigmaTel STAC9750,51'
 Components : 'AC97a:83847650'
 Controls  : 39
 Simple ctrls  : 24
  Date: Tue Jan  2 09:18:38 2018
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=40d082d2-6dec-4a8f-b207-0f43ebe8a43e
  InstallationDate: Installed on 2018-01-02 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Dell Computer Corporation Latitude D600
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=9a6ff044-01b0-4d97-8198-9c3a200e9f5a ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.13.0-21-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2003
  dmi.bios.vendor: Dell Computer Corporation
  dmi.bios.version: A05
  dmi.board.name: 03U652
  dmi.board.vendor: Dell Computer Corporation
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Computer Corporation

[Kernel-packages] [Bug 1740906] Re: package linux-image-4.13.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

2018-01-04 Thread axt

@Joseph Salisbury

No. That alone can _not_ solve the problem.

When starting the stick or the DVD, the option must be set before _and_
after the double dash:

" forcepae -- forcepae"


@Wesley Keener, execute this commands:

sudo sed -i 's/GRUB_CMDLINE_LINUX=""/GRUB_CMDLINE_LINUX="forcepae"/g' 
/etc/default/grub
sudo update-grub
sudo reboot
sudo apt-get -f install
sudo apt-get update && sudo apt-get dist-upgrade

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

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Fresh install Lubuntu 17.10 desktop i386.  Dell Latitude D600.
  Defaults on install except having to "forcepae" on boot.  "apt --fix-
  broken install" gives the following errors -

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following additional packages will be installed:
linux-image-4.13.0-21-generic
  Suggested packages:
fdutils linux-doc-4.13.0 | linux-source-4.13.0 linux-tools
  The following NEW packages will be installed:
linux-image-4.13.0-21-generic
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  88 not fully installed or removed.
  Need to get 19.3 MB of archives.
  After this operation, 50.7 MB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://us.archive.ubuntu.com/ubuntu artful-updates/main i386 
linux-image-4.13.0-21-generic i386 4.13.0-21.24 [19.3 MB]
  Fetched 19.3 MB in 4s (4,423 kB/s)
  (Reading database ... 146408 files and directories currently installed.)
  Preparing to unpack .../linux-image-4.13.0-21-generic_4.13.0-21.24_i386.deb 
...
  This kernel does not support a non-PAE CPU.
  dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.13.0-21-generic_4.13.0-21.24_i386.deb 
(--unpack):
   subprocess new pre-installation script returned error exit status 1
  Examining /etc/kernel/postrm.d .
  run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.13.0-21-generic 
/boot/vmlinuz-4.13.0-21-generic
  run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.13.0-21-generic 
/boot/vmlinuz-4.13.0-21-generic
  Errors were encountered while processing:
   /var/cache/apt/archives/linux-image-4.13.0-21-generic_4.13.0-21.24_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-21-generic (not installed)
  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.
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tcs1104 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with STAC9750,51 at irq 5'
 Mixer name : 'SigmaTel STAC9750,51'
 Components : 'AC97a:83847650'
 Controls  : 39
 Simple ctrls  : 24
  Date: Tue Jan  2 09:18:38 2018
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=40d082d2-6dec-4a8f-b207-0f43ebe8a43e
  InstallationDate: Installed on 2018-01-02 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Dell Computer Corporation Latitude D600
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=9a6ff044-01b0-4d97-8198-9c3a200e9f5a ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.13.0-21-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: No

[Kernel-packages] [Bug 1689980] Re: AACRAID for power9 platform

2018-01-04 Thread bugproxy

** Tags added: bugnameltc-155096 severity-high

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

Title:
  AACRAID for power9 platform

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

Bug description:
  SRU Justification

  Impact: Various issues found during integration of Microsemi adapters
  on Power 8 and Power 9 systems.

  Fix: Update the aacraid driver to version 50834 by cherry picking
  patches from upstream and from linux-next.

  Test case: Updated driver has been tested by IBM on Power systems and
  regression tested by Microsemi on other platforms.

  Regression potential: Changes (aside from trivial typo fixes) are
  limited to aacraid driver, so there's no regression potential outside
  of this driver. Regression testing has been done by Microsemi on
  relevant platforms.

  ---

  Hello team,
  It seems Microsemi team has requested to backport few AACRAID driver patches 
for Power 9 platform for 17.04 and 16.04.3 kernel.

  Hi Narinder,

  We have submitted a handful of critical fixes for the AACRAID driver
  on to the kernel.org, targeting 4.11. These patches are bug fixes and
  our customer IBM is expecting these patches to go into the 16.04.3
  release, for to use with the Power9 platforms.

  Can you please let me know if these patches will be backported by your
  kernel team on to the upcoming 16.04.3? Do you also have a schedule in
  place for 16.04.3 release?

  Thanks,
  Gana

  Below are the patch details.

  Subject: [PATCH V2 00/19] aacraid: Patchset with reset rework and misc
  fixes

  This patchset primarily focuses on tweaking and hardening the
  controller reset support for both ARC and HBA1000 devices. Now the
  driver can only reset the controller thru eh reset. Included a srb
  memory fix and pci dma allocation fix.

  Changes in V2:
   - Corrected heading and description for srb memory patch and removed stray
     comment.
   - Removed incorrect up function call and cleared fib wait flag after call
     to down interruptible in the ioctl return on ctrl reset patch.
   - Added review acknowledgements by David Carroll thank you Dave for
     finding the above issues in the above 2 patches.

  Raghava Aditya Renukunta (19):
  [SCSI] aacraid: Remove __GFP_DMA for raw srb memory
  [SCSI] aacraid: Fix DMAR issues with  iommu=pt
  [SCSI] aacraid: Added 32 and 64 queue depth for arc natives
  [SCSI] aacraid: Set correct Queue Depth for HBA1000 RAW disks
  [SCSI] aacraid: Remove reset support from check_health
  [SCSI] aacraid: Change wait time for fib completion
  [SCSI] aacraid: Log count info of scsi cmds before reset
  [SCSI] aacraid: Print ctrl status before eh reset
  [SCSI] aacraid: Using single reset mask for IOP reset
  [SCSI] aacraid: Rework IOP reset
  [SCSI] aacraid: Add periodic checks to see IOP reset status
  [SCSI] aacraid: Rework SOFT reset code
  [SCSI] aacraid: Rework aac_src_restart
  [SCSI] aacraid: Use correct function to get ctrl health
  [SCSI] aacraid: Make sure ioctl returns on controller reset
  [SCSI] aacraid: Enable ctrl reset for both hba and arc
  [SCSI] aacraid: Add reset debugging statements
  [SCSI] aacraid: Remove reference to Series-9
  [SCSI] aacraid: Update driver version to 50834

  drivers/scsi/aacraid/aachba.c   |  17 ++-
  drivers/scsi/aacraid/aacraid.h  |  22 +++-
  drivers/scsi/aacraid/commctrl.c |  15 ++-
  drivers/scsi/aacraid/comminit.c |  18 +---
  drivers/scsi/aacraid/commsup.c  |  78 +++---
  drivers/scsi/aacraid/linit.c| 232 
  drivers/scsi/aacraid/src.c  | 136 +--

   7 files changed, 298 insertions(+), 220 deletions(-)

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

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

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel oops destroying interfaces on i386

I tried to build a test kernel with the patch set from Cong mentioned in
comment #18.  However, there was a build failure due to some missing
prereq commits.  I also had to backport many of the patches, since they
were not clean cherry picks.

Per comment 16, the bug did not start happening until the 4.13 kernel
was introduced to Artful.  We may want to look for a commit to revert
instead of Congs patch set, since it may not pass all the SRU
requirements.


I'll create a VM and see if I can reproduce the bug.  If I can, I'll bisect 
down the offending commit in 4.13.  

Just to confirm, this is only happening on the i386 server release?

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

Title:
  openvswitch: kernel oops destroying interfaces on i386

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

Bug description:
  Reproducable on bionic using the autopkgtest's from openvswitch on
  i386:

  [   41.420568] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   41.421000] IP: igmp_group_dropped+0x21/0x220
  [   41.421246] *pdpt = 1d62c001 *pde =  

  [   41.421659] Oops:  [#1] SMP
  [   41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass 
input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg 
mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse 
virtio_blk virtio_net pata_acpi floppy
  [   41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW   
4.13.0-18-generic #21-Ubuntu
  [   41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [   41.424849] Workqueue: netns cleanup_net
  [   41.425071] task: db8fba80 task.stack: dba1
  [   41.425346] EIP: igmp_group_dropped+0x21/0x220
  [   41.425656] EFLAGS: 00010202 CPU: 0
  [   41.425864] EAX:  EBX: dd726360 ECX: dba11e6c EDX: 0002
  [   41.426335] ESI:  EDI: dd4db500 EBP: dba11dcc ESP: dba11d94
  [   41.426687]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   41.426990] CR0: 80050033 CR2:  CR3: 1e6d6d60 CR4: 06f0
  [   41.427340] Call Trace:
  [   41.427485]  ? __wake_up+0x36/0x40
  [   41.427680]  ip_mc_down+0x27/0x90
  [   41.427869]  inetdev_event+0x398/0x4e0
  [   41.428082]  ? skb_dequeue+0x5b/0x70
  [   41.428286]  ? wireless_nlevent_flush+0x4c/0x90
  [   41.428541]  notifier_call_chain+0x4e/0x70
  [   41.428772]  raw_notifier_call_chain+0x11/0x20
  [   41.429023]  call_netdevice_notifiers_info+0x2a/0x60
  [   41.429301]  dev_close_many+0x9d/0xe0
  [   41.429509]  rollback_registered_many+0xd7/0x380
  [   41.429768]  unregister_netdevice_many.part.102+0x10/0x80
  [   41.430075]  default_device_exit_batch+0x134/0x160
  [   41.430344]  ? do_wait_intr_irq+0x80/0x80
  [   41.430650]  ops_exit_list.isra.8+0x4d/0x60
  [   41.430886]  cleanup_net+0x18e/0x260
  [   41.431090]  process_one_work+0x1a0/0x390
  [   41.431317]  worker_thread+0x37/0x450
  [   41.431525]  kthread+0xf3/0x110
  [   41.431714]  ? process_one_work+0x390/0x390
  [   41.431941]  ? kthread_create_on_node+0x20/0x20
  [   41.432187]  ret_from_fork+0x19/0x24
  [   41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 
56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 
8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00
  [   41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94
  [   41.433750] CR2: 
  [   41.433961] ---[ end trace 595db54cab84070c ]---

  
  system then becomes unresponsive; no further interfaces can be created.

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

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

[Kernel-packages] [Bug 1733194] Re: kernel NULL pointer dereference in iwlmvm iwl_mvm_enable_txq

2018-01-04 Thread Bartosz Kwitniewski

Just a note, I have the same problem with Intel® Wireless-AC 3168
(firmware version 29.541020.0 op_mode iwlmvm) on Gentoo
linux-4.14.8-gentoo-r1 in AP mode (802.11n).

Sometimes kernel only shows warnings from 
drivers/net/wireless/intel/iwlwifi/mvm/tx.c:1363:
-
case TX_STATUS_FAIL_DEST_PS:
/* the FW should have stopped the queue and not
 * return this status
 */
WARN_ON(1);
info->flags |= IEEE80211_TX_STAT_TX_FILTERED;
break;
-
2018-01-03T21:16:51+01:00 [warning] kernel: [ cut here ]
2018-01-03T21:16:51+01:00 [warning] kernel: WARNING: CPU: 2 PID: 81 at 
drivers/net/wireless/intel/iwlwifi/mvm/tx.c:1363 iwl_mvm_rx_tx_cmd+0x361/0x610
2018-01-03T21:16:51+01:00 [warning] kernel: Modules linked in: rtl8812au(O)
2018-01-03T21:16:51+01:00 [warning] kernel: CPU: 2 PID: 81 Comm: 
irq/123-iwlwifi Tainted: GW  O4.14.8-gentoo-r1 #1
2018-01-03T21:16:51+01:00 [warning] kernel: Hardware name:  
/NUC6CAYB, BIOS AYAPLCEL.86A.0041.2017.0825.1152 08/25/2017
2018-01-03T21:16:51+01:00 [warning] kernel: task: 9ea3f473 task.stack: 
b5034027
2018-01-03T21:16:51+01:00 [warning] kernel: RIP: 
0010:iwl_mvm_rx_tx_cmd+0x361/0x610
2018-01-03T21:16:51+01:00 [warning] kernel: RSP: 0018:b50340273cb8 EFLAGS: 
00010246
2018-01-03T21:16:51+01:00 [warning] kernel: RAX: 0088 RBX: 
9ea3d6107700 RCX: 00031040
2018-01-03T21:16:51+01:00 [warning] kernel: RDX: 0003103f RSI: 
9ea3ffd20dc0 RDI: 9ea3f45ed200
2018-01-03T21:16:51+01:00 [warning] kernel: RBP: b50340273d38 R08: 
00020dc0 R09: b74e5b5d
2018-01-03T21:16:51+01:00 [warning] kernel: R10: 9ea3d6107730 R11: 
b737b110 R12: 9ea3f40f9388
2018-01-03T21:16:51+01:00 [warning] kernel: R13: d000 R14: 
9ea3d6107700 R15: 9ea3e1e93000
2018-01-03T21:16:51+01:00 [warning] kernel: FS:  () 
GS:9ea3ffd0() knlGS:
2018-01-03T21:16:51+01:00 [warning] kernel: CS:  0010 DS:  ES:  CR0: 
80050033
2018-01-03T21:16:51+01:00 [warning] kernel: CR2: 7ed717e8eee0 CR3: 
00023fe09000 CR4: 003406e0
2018-01-03T21:16:51+01:00 [warning] kernel: Call Trace:
2018-01-03T21:16:51+01:00 [warning] kernel:  iwl_mvm_rx_common+0x181/0x2b0
2018-01-03T21:16:51+01:00 [warning] kernel:  iwl_mvm_rx+0x6b/0x80
2018-01-03T21:16:51+01:00 [warning] kernel:  iwl_pcie_rx_handle+0x2ee/0x860
2018-01-03T21:16:51+01:00 [warning] kernel:  iwl_pcie_irq_handler+0x18d/0x6c0
2018-01-03T21:16:51+01:00 [warning] kernel:  ? irq_forced_thread_fn+0x80/0x80
2018-01-03T21:16:51+01:00 [warning] kernel:  irq_thread_fn+0x2a/0x60
2018-01-03T21:16:51+01:00 [warning] kernel:  irq_thread+0x149/0x1b0
2018-01-03T21:16:51+01:00 [warning] kernel:  ? __schedule+0x1c6/0x4f0
2018-01-03T21:16:51+01:00 [warning] kernel:  ? wake_threads_waitq+0x40/0x40
2018-01-03T21:16:51+01:00 [warning] kernel:  kthread+0x106/0x140
2018-01-03T21:16:51+01:00 [warning] kernel:  ? irq_thread_dtor+0xb0/0xb0
2018-01-03T21:16:51+01:00 [warning] kernel:  ? kthread_create_on_node+0x70/0x70
2018-01-03T21:16:51+01:00 [warning] kernel:  ret_from_fork+0x22/0x30
2018-01-03T21:16:51+01:00 [warning] kernel: Code: 00 49 c7 42 20 00 00 00 00 0f 
84 b6 fe ff ff 0f 87 98 fe ff ff 66 83 7d b2 01 77 08 41 81 4e 28 00 02 00 00 
31 db e9 9f fe ff ff <0f> ff 31 db 41 81 4e 28 00 01 00 00 e9 8e fe ff ff 49 8b 
86 c8 
2018-01-03T21:16:51+01:00 [warning] kernel: ---[ end trace 0b4f679a324845ac ]---


And here is the crash itself:
-
2018-01-04T18:03:16+01:00 [alert] kernel: BUG: unable to handle kernel NULL 
pointer dereference at 0070
2018-01-04T18:03:16+01:00 [alert] kernel: IP: 
iwl_trans_pcie_txq_enable+0x6b/0x410
2018-01-04T18:03:16+01:00 [info] kernel: PGD 0 P4D 0 
2018-01-04T18:03:16+01:00 [warning] kernel: Oops: 0002 [#1] SMP
2018-01-04T18:03:16+01:00 [warning] kernel: Modules linked in: rtl8812au(O)
2018-01-04T18:03:16+01:00 [warning] kernel: CPU: 1 PID: 30588 Comm: kworker/1:2 
Tainted: GW  O4.14.8-gentoo-r1 #1
2018-01-04T18:03:16+01:00 [warning] kernel: Hardware name:  
/NUC6CAYB, BIOS AYAPLCEL.86A.0041.2017.0825.1152 08/25/2017
2018-01-04T18:03:16+01:00 [warning] kernel: Workqueue: events 
iwl_mvm_add_new_dqa_stream_wk
2018-01-04T18:03:16+01:00 [warning] kernel: task: 9ea3f5b08000 task.stack: 
b50340894000
2018-01-04T18:03:16+01:00 [warning] kernel: RIP: 
0010:iwl_trans_pcie_txq_enable+0x6b/0x410
2018-01-04T18:03:16+01:00 [warning] kernel: RSP: 0018:b50340897bf8 EFLAGS: 
00010246
2018-01-04T18:03:16+01:00 [warning] kernel: RAX: 03e8 RBX: 
001f RCX: 
2018-01-04T18:03:16+01:00 [warning] kernel: RDX: 0fa3 RSI: 
001f RDI: 2710
2018-01-04T18:03:16+01:00 [warning] kernel: RBP: b50340897c60 R08: 
2710 R09: 0001

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-01-04 Thread Paul

Hi, I've seen the solution that Anthony posted and I'm grateful, but I
have a few questions.

1/ If it's as simple as updating/replacing the kernel, why hasn't this
fix been rolled out as a system/software update?

2/ When is it likely to roll out as an update?

3/ a/ Has the download been updated with a non-broken kernel? b/ This
debacle has allowed a lot of system degradation to take place on my
system to the point that I need to reinstall 17.10, this doesn't seem to
be a possibility right now, or am I wrong?

4/ What changes have been implemented over at AskUbuntu to ensure that
users like myself who a/ test pre-release software are able to be
supported and b/ Do not have issues such as a report of a broken bios
dismissed/deleted before they're investigated adequately and escalated
and thus stem the issue ballooning into an issue of this magnitude in
the future?

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

Title:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

---

Test Case: Fix has been verified by our HWE team on affected hardware.

Regression Potential: Minimal, it's unlikely anyone is actually doing
anything which requires this driver.

---

Affected Machines:

---

Original Description:

Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
reported a corrupted BIOS.

It's not possible to save new settings in BIOS anymore and after
rebooting, the system starts with the old settings.

Moreover (and most important) USB booting is not possible anymore
since USB is not recognized. It's very serious, since our

[Kernel-packages] [Bug 1739891] Re: hisi_sas: Add ATA command support for SMR disks

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

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

Title:
  hisi_sas: Add ATA command support for SMR disks

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

Bug description:
  [Impact]
  SATA SMR disks are not supported.

  [Test Case]
  Connect and use a SATA SMR disk

  [Regression Risk]
  The fix is restricted to a single driver, adding only new command support, 
mitigating the regression risk of previous commands.

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

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

[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10

I hope you had a good holiday, Rod.  I started up the bisect again.

I built the next test kernel, up to the following commit:
9ebf47f152918cce0caaa9c2767656635fbf59e4

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

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

Title:
  System hang with Linux kernel 4.13, not with 4.10

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe package in Ubuntu:
  New
Status in linux source package in Artful:
  In Progress
Status in linux-hwe source package in Artful:
  New
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  New

Bug description:
  In doing Ubuntu 17.10 regression testing, we've encountered one
  computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in
  four times when running our cpu_offlining test. This test attempts to
  take all the CPU cores offline except one, then brings them back
  online again. This test ran successfully on boldore with previous
  releases, but with 17.10, the system sometimes (about one in four
  runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but
  when I upgraded the 16.04.3 installation to linux-
  image-4.13.0-16-generic, the problem appeared again, so I'm confident
  this is a problem with the kernel. I'm attaching two files, dmesg-
  output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output
  that appears when running the cpu_offlining test with 4.10.0-38 and
  4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I
  was running "dmesg -w" in a second SSH login; the files are cut-and-
  pasted from that.)

  I initiated this bug report from an Ubuntu 16.04.3 installation
  running a 4.10 kernel; but as I said, this applies to the 4.13 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1
  ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Nov 21 17:36:06 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)

2018-01-04 Thread Mike Pontillo

Interesting; the first thing I tried when triaging this was to edit
/etc/nsswitch.conf as follows:

# hosts:  files mdns4_minimal [NOTFOUND=return] dns myhostname
hosts:  files dns

... to eliminate the possibility that it was multicast DNS causing the
slowdown. But it appears I'm behind the times. ;-) (And didn't this only
affect the .local domain?)

Does this mean there are now two subsystems responsible for link-local
address resolution? (avahi and systemd-resolved?)

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial)

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

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

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

[Kernel-packages] [Bug 1693842] Re: USB 3.0 Disk Drive Not Recognized.

2018-01-04 Thread Pablo

Hi again,

I forgot to comment that this issue also appear in Debian 9 (my other
PC)...

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

Title:
  USB 3.0 Disk Drive Not Recognized.

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  WD My Passport 2T USB 3.0 Disk Drive.
  External Plugable 7 port USB 3.0 hub.

  When I connect the WD drive to the external USB 3.0 hub it is not recognized.
  The drive led blinks one time and it is not in dmesg or in the output of 
lsusb.

  > sudo lsusb -v causes the drive led to blink several times and it is
  recognized.

  With Autosuspend good for this device, long access applications like dump 
fail.
  After 'sudo lsusb -v' and starting dump, it seems normal for some 20 minutes 
and then dump asks for operator intervention.  Looking at dmesg the drive 
(initially sdf) was disconnected and reconnected as sdg.

    Bad  Autosuspend for USB device xHCI Host Controller [usb6]

  seems to correct this behavior but not the initial connection problem.

  Some discussion and testing in bug 1242321.

  If I connect the drive to a USB 3.0 port on the motherboard, it is
  recognized.

  There is no problem with an Plugable 7-port USB 2.0 hub.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-78-generic 4.4.0-78.99
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tomdean3698 F pulseaudio
   /dev/snd/controlC0:  tomdean3698 F pulseaudio
  Date: Fri May 26 09:05:20 2017
  HibernationDevice: RESUME=UUID=8c377624-f972-4b2b-9364-832f70b2a67a
  InstallationDate: Installed on 2016-05-15 (375 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.

   eno1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=47d8903b-afb2-4432-bc92-b1f4e30209ef ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware1.157.8
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79 PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4801:bd07/25/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1740828] Re: USB devices are detected but not working

2018-01-04 Thread Karl Kastner

Maybe, as automatic updates are enabled this is not certain. I did not
experience the same problem recently. The mainline kernel does not
install on my machine:

dpkg -i *
(Reading database ... 1028499 files and directories currently installed.)
Preparing to unpack 
linux-headers-4.15.0-041500rc6_4.15.0-041500rc6.201712312330_all.deb ...
Unpacking linux-headers-4.15.0-041500rc6 (4.15.0-041500rc6.201712312330) over 
(4.15.0-041500rc6.201712312330) ...
Preparing to unpack 
linux-headers-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330_amd64.deb 
...
Unpacking linux-headers-4.15.0-041500rc6-generic 
(4.15.0-041500rc6.201712312330) over (4.15.0-041500rc6.201712312330) ...
Preparing to unpack 
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330_amd64.deb ...
Done.
Unpacking linux-image-4.15.0-041500rc6-generic (4.15.0-041500rc6.201712312330) 
over (4.15.0-041500rc6.201712312330) ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 
4.15.0-041500rc6-generic /boot/vmlinuz-4.15.0-041500rc6-generic
run-parts: executing /etc/kernel/postrm.d/zz-extlinux 4.15.0-041500rc6-generic 
/boot/vmlinuz-4.15.0-041500rc6-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 
4.15.0-041500rc6-generic /boot/vmlinuz-4.15.0-041500rc6-generic
Setting up linux-headers-4.15.0-041500rc6 (4.15.0-041500rc6.201712312330) ...
Setting up linux-headers-4.15.0-041500rc6-generic 
(4.15.0-041500rc6.201712312330) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 
4.15.0-041500rc6-generic /boot/vmlinuz-4.15.0-041500rc6-generic
ERROR (dkms apport): binary package for evdi: 1.2.65 not found
Error! Bad return status for module build on kernel: 4.15.0-041500rc6-generic 
(x86_64)
Consult /var/lib/dkms/evdi/1.2.65/build/make.log for more information.

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

Title:
  USB devices are detected but not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  USB mouse, keyboard and memory sticks are detected, but not working
  with kernel 4.10.0-37-generic. They how up in lsusb, but moving the
  mouse or typing does not result in any reaction on my laptop. No
  /dev/sdx devices is created for the memory stick. Internal touch pad
  and keyboard of the laptop are working.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-37-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.8
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0:  pia2806 F pulseaudio
   /dev/snd/controlC1:  pia2806 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Jan  2 09:40:23 2018
  InstallationDate: Installed on 2015-11-05 (788 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Notebook W230SS
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=2329e937-a4e4-4efc-a999-c0fa7d44c92b ro uveau.modeset=0 
acpi_enforce_resources=lax nosplash uveau.modeset=0 acpi_enforce_resources=lax 
acpi_enforce_resources=lax
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.164.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-10-16 (78 days ago)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Kernel-packages] [Bug 1693842] Re: USB 3.0 Disk Drive Not Recognized.

2018-01-04 Thread Pablo

Hi,

I have a USB 3.0 Disk 2TB (WD Elements).

When I plug in a 2.0 USB Port the disk is recognized, but when I plug in
a 3.0 USB Port the disk is not recognized and the dmesg not show
anything.

This is the exit of command "sudo lsusb":

Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 062a:4101 Creative Labs Wireless Keyboard/Mouse
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

This is the exit of command "lsusb -v -d 1d6b:0003":

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   3.00
  bDeviceClass9 Hub
  bDeviceSubClass 0 Unused
  bDeviceProtocol 3 
  bMaxPacketSize0 9
  idVendor   0x1d6b Linux Foundation
  idProduct  0x0003 3.0 root hub
  bcdDevice4.04
  iManufacturer   3 Linux 4.4.0-103-generic xhci-hcd
  iProduct2 xHCI Host Controller
  iSerial 1 :00:14.0
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   31
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0xe0
  Self Powered
  Remote Wakeup
MaxPower0mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 9 Hub
  bInterfaceSubClass  0 Unused
  bInterfaceProtocol  0 Full speed (or root) hub
  iInterface  0 
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0004  1x 4 bytes
bInterval  12
bMaxBurst   0
Hub Descriptor:
  bLength  12
  bDescriptorType  42
  nNbrPorts 2
  wHubCharacteristic 0x000a
No power switching (usb 1.0)
Per-port overcurrent protection
  bPwrOn2PwrGood   10 * 2 milli seconds
  bHubContrCurrent  0 milli Ampere
  bHubDecLat  0.0 micro seconds
  wHubDelay 0 nano seconds
  DeviceRemovable0x00
 Hub Port Status:
   Port 1: .02a0 5Gbps power Rx.Detect
   Port 2: .02a0 5Gbps power Rx.Detect
Binary Object Store Descriptor:
  bLength 5
  bDescriptorType15
  wTotalLength   15
  bNumDeviceCaps  1
  SuperSpeed USB Device Capability:
bLength10
bDescriptorType16
bDevCapabilityType  3
bmAttributes 0x02
  Latency Tolerance Messages (LTM) Supported
wSpeedsSupported   0x0008
  Device can operate at SuperSpeed (5Gbps)
bFunctionalitySupport   3
  Lowest fully-functional device speed is SuperSpeed (5Gbps)
bU1DevExitLat  10 micro seconds
bU2DevExitLat 512 micro seconds
Device Status: 0x0001
  Self Powered

This is the exit of command "uname -a":

Linux WorkStation 4.4.0-103-generic #126-Ubuntu SMP Mon Dec 4 16:23:28
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

This is the exit of command "cat /etc/os-release":

NAME="Ubuntu"
VERSION="16.04.3 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.3 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/;
SUPPORT_URL="http://help.ubuntu.com/;
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

I don't understand what's the problem...

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

Title:
  USB 3.0 Disk Drive Not Recognized.

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  WD My Passport 2T USB 3.0 Disk Drive.
  External Plugable 7 port USB 3.0 hub.

  When I connect the WD drive to the external USB 3.0 hub it is not recognized.
  The drive led blinks one time and it is not in dmesg or in the output of 
lsusb.

  > sudo lsusb -v causes the drive led to blink several times and it is
  recognized.

  With Autosuspend good for this device, long access applications like dump 
fail.
  After 'sudo lsusb -v' and starting dump, it seems normal for some 20 minutes 
and then dump asks for operator intervention.  Looking at dmesg the drive 
(initially sdf) was disconnected and reconnected as sdg.

    Bad  Autosuspend for USB device xHCI Host

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-01-04 Thread Martin Kucmercik

FOR USERS WITH ACTIVE BASH LINE
Hello after a long loong long struggle and learning and with the above
patch

http://people.canonical.com/~ypwong/lp1734147/linux-
image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb

I successfully restored UEFI BIOS on Lenovo B50-80.

The only solution working for me, if I hadn't played with windows efi boot
manager:
First I installed Ubuntu 16.04 in Oracle Virtual Box on Windows PC on a flash
drive
- must be at least 16GB.
I had to forbid creating any virtual disks.
Assigned live CD from iso and then simply attached Flash drive.
It was better on Windows than Live Linux.

After successful install on USB Flash drive, I plugged the Flash drive to the
affected Lenovo. From
minimal Bash-line I found the grub.cfg location on USB. usually - ls
(hd0,XY)/boot/grub
I used the configfile command - configfile (hd0,msdos1)/boot/grub/grub.cfg -
in my case.
Grub 2.02 started without hesitation and allowed me to pick to run Ubuntu 16.04
on the USB drive.

Booted in the system I did all the necessary updates
sudo apt update
sudo apt upgrade

I also used boot-repair, that allowed me to see grub graphical interface
straightaway
after reboot. But I think this is not necessary.

I did not use ukuu for a kernel upgrade, I just simply used wget command.
Nice inspiration is here:
http://sourcedigit.com/22874-update-linux-kernel-4-14-rc7-ubuntu-systems/

UEFI BIOS started to work only after the last upgrade which you can find here
in this forum,
and allowed me to change anything permanently after exit.

Then I was able to boot any bootable CD or USB Drive. However I did
Lenovo One key recovery, which magically started to work after UEFI BIOS was
unlocked.

Good luck for those still struggling.

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

Title:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

---

Test Case: Fix has been verified by our HWE team on affected hardware.

Regression Potential: Minimal, it's unlikely anyone is actually doing
anything which requires this driver.

---

Affected Machines:

[Kernel-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)

2018-01-04 Thread Dimitri John Ledkov

$ time systemd-resolve -p dns not-a-real-hostname
not-a-real-hostname: resolve call failed: No appropriate name servers or 
networks for name found

real0m0.003s
user0m0.000s
sys 0m0.004s

$ time systemd-resolve -p llmnr not-a-real-hostname
not-a-real-hostname: resolve call failed: All attempts to contact name servers 
or networks failed

real0m0.850s
user0m0.000s
sys 0m0.004s

$ time systemd-resolve -p llmnr-ipv4 not-a-real-hostname
not-a-real-hostname: resolve call failed: All attempts to contact name servers 
or networks failed

real0m0.820s
user0m0.000s
sys 0m0.000s

$ time systemd-resolve -p llmnr-ipv6 not-a-real-hostname
not-a-real-hostname: resolve call failed: All attempts to contact name servers 
or networks failed

real0m0.750s
user0m0.000s
sys 0m0.000s

$ time systemd-resolve not-a-real-hostname
not-a-real-hostname: resolve call failed: All attempts to contact name servers 
or networks failed

real0m0.712s
user0m0.004s
sys 0m0.000s

The dns resolution from systemd-resolve is fast; the llmnr one is not.
We currently have llmnr resolution enabled by default. ...it's a
feature?!

What is the usecase of resolving things that do not exist? Surely we
optimise for the fact that most resolutions will succeed, from
performance point of view. The first result retrieved, is returned back.

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial)

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

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

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

[Kernel-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)

> The dns resolution from systemd-resolve is fast; the llmnr one is not.
> We currently have llmnr resolution enabled by default. ...it's a feature?!

It is not a feature for a local DNS resolver to be doing llmnr under the
hood by default.  Please disable this.

> What is the use case of resolving things that do not exist?

DNS search paths.
User typoed the name and shouldn't have to wait 10 seconds for the response.

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial)

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

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

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

[Kernel-packages] [Bug 1740923] Re: package linux-image-4.13.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

2018-01-04 Thread Carsten Lange

Problem occurs on Pentium M with PAE bug.
Solved by adding forcepae to grub and grub-update. After that sudo apt-get 
install -f worked.
Before this update forcepae was not needed.

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

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  standard system update after first install of lubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-21-generic (not installed)
  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.
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  red 862 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with Cx20468-31 at irq 10'
 Mixer name : 'Conexant Cx20468-31'
 Components : 'AC97a:43585430'
 Controls  : 24
 Simple ctrls  : 16
  Date: Tue Jan  2 20:09:24 2018
  DuplicateSignature:
   package:linux-image-4.13.0-21-generic:(not installed)
   Preparing to unpack 
.../71-linux-image-4.13.0-21-generic_4.13.0-21.24_i386.deb ...
   This kernel does not support a non-PAE CPU.
   dpkg: error processing archive 
/tmp/apt-dpkg-install-UematV/71-linux-image-4.13.0-21-generic_4.13.0-21.24_i386.deb
 (--unpack):
subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=c3bdf7d5-b131-4b28-8b11-ad45372208c2
  InstallationDate: Installed on 2018-01-02 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Acer TravelMate 4000
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=c553c403-6d68-4bee-af31-1b6dc83b7391 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: "/root/Error: 
command ['which', 'python'] failed with exit code 1:": "/root/Error: command 
['which', 'python'] failed with exit code 1:", unpackaged
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.13.0-21-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2004
  dmi.bios.vendor: ACER
  dmi.bios.version: 3A10
  dmi.board.name: TravelMate 4000
  dmi.board.vendor: Acer
  dmi.board.version: Rev 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Rev.1
  dmi.modalias: 
dmi:bvnACER:bvr3A10:bd10/12/2004:svnAcer:pnTravelMate4000:pvrRev1:rvnAcer:rnTravelMate4000:rvrRev1.0:cvnAcer:ct10:cvrRev.1:
  dmi.product.name: TravelMate 4000
  dmi.product.version: Rev 1
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)

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

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial)

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

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

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

2018-01-04 Thread Roger Tri

the problem persist on new kernel
Linux rogelio-K55A 4.15.0-041500rc6-generic #201712312330 SMP Sun Dec 31 
23:31:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  17.10 freezes every hour ramdomly

Status in linux package in Ubuntu:
  Incomplete

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:
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 1737640] Re: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures

2018-01-04 Thread Ante Karamatić

** Description changed:

+ [Impact]
+ 
+  * This bug effects anyone deploying LXD with juju on a machine with
+ unconfigured interfaces. Since this is a very common use case, SRU is
+ needed.
+ 
+ [Test Case]
+ 
+  * Detailed process can be seen at https://paste.ubuntu.com/26169937/
+ 
+ [Regression Potential]
+ 
+  * Potential for regression is low because of the nature of the error.
+ It's just missing a case stanza for interfaces that are defined with
+ IP/mask
+ 
+ [Other Info]
+  
+  * Original report:
+ 
  I'm seeing this error as the status of multiple containers in my deploy:
  
  http://paste.ubuntu.com/26166720/
  
  I can't connect to the parent machines anymore either - it seems
  networking is totally hosed on the machines.
  
  This is with juju 2.3.1.

** Summary changed:

- /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured 
interfaces cause ifup failures
+ [SRU] /usr/sbin/fanctl: arithmetic expression: expecting primary | 
unconfigured interfaces cause ifup failures

** Description changed:

  [Impact]
  
-  * This bug effects anyone deploying LXD with juju on a machine with
- unconfigured interfaces. Since this is a very common use case, SRU is
- needed.
+  * This bug effects anyone deploying LXD with juju on a machine with
+ interfaces configured as IP/mask. Since this is a very common use case,
+ SRU is needed.
  
  [Test Case]
  
-  * Detailed process can be seen at https://paste.ubuntu.com/26169937/
+  * Detailed process can be seen at https://paste.ubuntu.com/26169937/
  
  [Regression Potential]
  
-  * Potential for regression is low because of the nature of the error.
+  * Potential for regression is low because of the nature of the error.
  It's just missing a case stanza for interfaces that are defined with
  IP/mask
  
  [Other Info]
-  
-  * Original report:
+ 
+  * Original report:
  
  I'm seeing this error as the status of multiple containers in my deploy:
  
  http://paste.ubuntu.com/26166720/
  
  I can't connect to the parent machines anymore either - it seems
  networking is totally hosed on the machines.
  
  This is with juju 2.3.1.

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

Title:
  [SRU] /usr/sbin/fanctl: arithmetic expression: expecting primary |
  unconfigured interfaces cause ifup failures

Status in juju:
  Invalid
Status in OPNFV:
  Fix Committed
Status in ubuntu-fan package in Ubuntu:
  Confirmed
Status in ubuntu-fan source package in Xenial:
  Fix Released
Status in ubuntu-fan source package in Zesty:
  Confirmed
Status in ubuntu-fan source package in Artful:
  Confirmed
Status in ubuntu-fan source package in Bionic:
  Confirmed

Bug description:
  [Impact]

   * This bug effects anyone deploying LXD with juju on a machine with
  interfaces configured as IP/mask. Since this is a very common use
  case, SRU is needed.

  [Test Case]

   * Detailed process can be seen at https://paste.ubuntu.com/26169937/

  [Regression Potential]

   * Potential for regression is low because of the nature of the error.
  It's just missing a case stanza for interfaces that are defined with
  IP/mask

  [Other Info]

   * Original report:

  I'm seeing this error as the status of multiple containers in my
  deploy:

  http://paste.ubuntu.com/26166720/

  I can't connect to the parent machines anymore either - it seems
  networking is totally hosed on the machines.

  This is with juju 2.3.1.

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

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

[Kernel-packages] [Bug 1731031] Re: Kernel Oops with 17.10

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

** This bug has been marked a duplicate of bug 1734327
   Kernel panic on a nfsroot system

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

Title:
  Kernel Oops with 17.10

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

Bug description:
  have captured dmesg just before oops

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Nov  8 20:41:14 2017
  DistUpgraded: 2017-11-07 01:49:14,657 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: kubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.10.0-38-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller 
[106b:011a]
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1762): WARNING **: Failed to 
load user image: Failed to open file '/home/hmeyer/.face': No such file or 
directory
  MachineType: Apple Inc. MacBookPro11,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=fbc61d79-8b51-4801-8e2b-175ff6daa14f ro quiet splash apparmor=0 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-11-07 (1 days ago)
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B17.1602221718
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B17.1602221718:bd02/22/2016:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro11,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Nov  8 20:39:06 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2
  xserver.video_driver: modeset

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

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

[Kernel-packages] [Bug 1737640] Re: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures

2018-01-04 Thread Łukasz Zemczak

As per earlier arrangements, I have published the package as-is as per
the provided test feedback in comments. It's a one-off exception, bionic
and other series will be prepared ASAP.

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

Title:
  /usr/sbin/fanctl: arithmetic expression: expecting primary |
  unconfigured interfaces cause ifup failures

Status in juju:
  Invalid
Status in OPNFV:
  Fix Committed
Status in ubuntu-fan package in Ubuntu:
  Confirmed
Status in ubuntu-fan source package in Xenial:
  Fix Released
Status in ubuntu-fan source package in Zesty:
  Confirmed
Status in ubuntu-fan source package in Artful:
  Confirmed
Status in ubuntu-fan source package in Bionic:
  Confirmed

Bug description:
  I'm seeing this error as the status of multiple containers in my
  deploy:

  http://paste.ubuntu.com/26166720/

  I can't connect to the parent machines anymore either - it seems
  networking is totally hosed on the machines.

  This is with juju 2.3.1.

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

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

[Kernel-packages] [Bug 1737640] Re: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures

2018-01-04 Thread David Britton

** Changed in: ubuntu-fan (Ubuntu Zesty)
 Assignee: (unassigned) => Andreas Hasenack (ahasenack)

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

Title:
  /usr/sbin/fanctl: arithmetic expression: expecting primary |
  unconfigured interfaces cause ifup failures

Status in juju:
  Invalid
Status in OPNFV:
  Fix Committed
Status in ubuntu-fan package in Ubuntu:
  Confirmed
Status in ubuntu-fan source package in Xenial:
  Fix Released
Status in ubuntu-fan source package in Zesty:
  Confirmed
Status in ubuntu-fan source package in Artful:
  Confirmed
Status in ubuntu-fan source package in Bionic:
  Confirmed

Bug description:
  I'm seeing this error as the status of multiple containers in my
  deploy:

  http://paste.ubuntu.com/26166720/

  I can't connect to the parent machines anymore either - it seems
  networking is totally hosed on the machines.

  This is with juju 2.3.1.

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

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

[Kernel-packages] [Bug 1737640] Re: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures

2018-01-04 Thread David Britton

** Changed in: ubuntu-fan (Ubuntu Xenial)
 Assignee: (unassigned) => Andreas Hasenack (ahasenack)

** Changed in: ubuntu-fan (Ubuntu Artful)
 Assignee: (unassigned) => Andreas Hasenack (ahasenack)

** Changed in: ubuntu-fan (Ubuntu Bionic)
 Assignee: Stefan Bader (smb) => Andreas Hasenack (ahasenack)

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

Title:
  /usr/sbin/fanctl: arithmetic expression: expecting primary |
  unconfigured interfaces cause ifup failures

Status in juju:
  Invalid
Status in OPNFV:
  Fix Committed
Status in ubuntu-fan package in Ubuntu:
  Confirmed
Status in ubuntu-fan source package in Xenial:
  Fix Released
Status in ubuntu-fan source package in Zesty:
  Confirmed
Status in ubuntu-fan source package in Artful:
  Confirmed
Status in ubuntu-fan source package in Bionic:
  Confirmed

Bug description:
  I'm seeing this error as the status of multiple containers in my
  deploy:

  http://paste.ubuntu.com/26166720/

  I can't connect to the parent machines anymore either - it seems
  networking is totally hosed on the machines.

  This is with juju 2.3.1.

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

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

[Kernel-packages] [Bug 1737640] Update Released

2018-01-04 Thread Łukasz Zemczak

The verification of the Stable Release Update for ubuntu-fan has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  /usr/sbin/fanctl: arithmetic expression: expecting primary |
  unconfigured interfaces cause ifup failures

Status in juju:
  Invalid
Status in OPNFV:
  Fix Committed
Status in ubuntu-fan package in Ubuntu:
  Confirmed
Status in ubuntu-fan source package in Xenial:
  Fix Released
Status in ubuntu-fan source package in Zesty:
  Confirmed
Status in ubuntu-fan source package in Artful:
  Confirmed
Status in ubuntu-fan source package in Bionic:
  Confirmed

Bug description:
  I'm seeing this error as the status of multiple containers in my
  deploy:

  http://paste.ubuntu.com/26166720/

  I can't connect to the parent machines anymore either - it seems
  networking is totally hosed on the machines.

  This is with juju 2.3.1.

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

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

[Kernel-packages] [Bug 1737640] Re: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures

2018-01-04 Thread Launchpad Bug Tracker

This bug was fixed in the package ubuntu-fan - 0.12.8~16.04.2

---
ubuntu-fan (0.12.8~16.04.2) xenial; urgency=medium

  * fanctl: fix config_filename when the interface does not have a width
(LP: #1737640)

 -- Andy Whitcroft   Tue, 12 Dec 2017 15:34:26 +

** Changed in: ubuntu-fan (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  /usr/sbin/fanctl: arithmetic expression: expecting primary |
  unconfigured interfaces cause ifup failures

Status in juju:
  Invalid
Status in OPNFV:
  Fix Committed
Status in ubuntu-fan package in Ubuntu:
  Confirmed
Status in ubuntu-fan source package in Xenial:
  Fix Released
Status in ubuntu-fan source package in Zesty:
  Confirmed
Status in ubuntu-fan source package in Artful:
  Confirmed
Status in ubuntu-fan source package in Bionic:
  Confirmed

Bug description:
  I'm seeing this error as the status of multiple containers in my
  deploy:

  http://paste.ubuntu.com/26166720/

  I can't connect to the parent machines anymore either - it seems
  networking is totally hosed on the machines.

  This is with juju 2.3.1.

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

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

[Kernel-packages] [Bug 1740906] Re: package linux-image-4.13.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"

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

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Fresh install Lubuntu 17.10 desktop i386.  Dell Latitude D600.
  Defaults on install except having to "forcepae" on boot.  "apt --fix-
  broken install" gives the following errors -

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following additional packages will be installed:
linux-image-4.13.0-21-generic
  Suggested packages:
fdutils linux-doc-4.13.0 | linux-source-4.13.0 linux-tools
  The following NEW packages will be installed:
linux-image-4.13.0-21-generic
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  88 not fully installed or removed.
  Need to get 19.3 MB of archives.
  After this operation, 50.7 MB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://us.archive.ubuntu.com/ubuntu artful-updates/main i386 
linux-image-4.13.0-21-generic i386 4.13.0-21.24 [19.3 MB]
  Fetched 19.3 MB in 4s (4,423 kB/s)
  (Reading database ... 146408 files and directories currently installed.)
  Preparing to unpack .../linux-image-4.13.0-21-generic_4.13.0-21.24_i386.deb 
...
  This kernel does not support a non-PAE CPU.
  dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.13.0-21-generic_4.13.0-21.24_i386.deb 
(--unpack):
   subprocess new pre-installation script returned error exit status 1
  Examining /etc/kernel/postrm.d .
  run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.13.0-21-generic 
/boot/vmlinuz-4.13.0-21-generic
  run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.13.0-21-generic 
/boot/vmlinuz-4.13.0-21-generic
  Errors were encountered while processing:
   /var/cache/apt/archives/linux-image-4.13.0-21-generic_4.13.0-21.24_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-21-generic (not installed)
  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.
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tcs1104 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with STAC9750,51 at irq 5'
 Mixer name : 'SigmaTel STAC9750,51'
 Components : 'AC97a:83847650'
 Controls  : 39
 Simple ctrls  : 24
  Date: Tue Jan  2 09:18:38 2018
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=40d082d2-6dec-4a8f-b207-0f43ebe8a43e
  InstallationDate: Installed on 2018-01-02 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Dell Computer Corporation Latitude D600
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=9a6ff044-01b0-4d97-8198-9c3a200e9f5a ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.13.0-21-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

[Kernel-packages] [Bug 1740923] Re: package linux-image-4.13.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"

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

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

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  standard system update after first install of lubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-21-generic (not installed)
  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.
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  red 862 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with Cx20468-31 at irq 10'
 Mixer name : 'Conexant Cx20468-31'
 Components : 'AC97a:43585430'
 Controls  : 24
 Simple ctrls  : 16
  Date: Tue Jan  2 20:09:24 2018
  DuplicateSignature:
   package:linux-image-4.13.0-21-generic:(not installed)
   Preparing to unpack 
.../71-linux-image-4.13.0-21-generic_4.13.0-21.24_i386.deb ...
   This kernel does not support a non-PAE CPU.
   dpkg: error processing archive 
/tmp/apt-dpkg-install-UematV/71-linux-image-4.13.0-21-generic_4.13.0-21.24_i386.deb
 (--unpack):
subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=c3bdf7d5-b131-4b28-8b11-ad45372208c2
  InstallationDate: Installed on 2018-01-02 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Acer TravelMate 4000
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=c553c403-6d68-4bee-af31-1b6dc83b7391 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: "/root/Error: 
command ['which', 'python'] failed with exit code 1:": "/root/Error: command 
['which', 'python'] failed with exit code 1:", unpackaged
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.13.0-21-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2004
  dmi.bios.vendor: ACER
  dmi.bios.version: 3A10
  dmi.board.name: TravelMate 4000
  dmi.board.vendor: Acer
  dmi.board.version: Rev 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Rev.1
  dmi.modalias: 
dmi:bvnACER:bvr3A10:bd10/12/2004:svnAcer:pnTravelMate4000:pvrRev1:rvnAcer:rnTravelMate4000:rvrRev1.0:cvnAcer:ct10:cvrRev.1:
  dmi.product.name: TravelMate 4000
  dmi.product.version: Rev 1
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1741084] Re: rtsx_pci needs to be manually loaded for Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader [10ec:5229]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.15 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.15-rc6

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

** Tags added: kernel-da-key zesty

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

Title:
  rtsx_pci needs to be manually loaded for Realtek Semiconductor Co.,
  Ltd. RTS5229 PCI Express Card Reader [10ec:5229]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A friend's card reader in his ThinkPad L430 [10ec:5229] was not
  automatically recognized in 4.10.0-40-generic (amd64) on 16.04. He had
  to manually load the rtsx_pci module.

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

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

[Kernel-packages] [Bug 1741042] Re: ubuntu 17.00 kernel freeze

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.15 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.15-rc6

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

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

Title:
  ubuntu 17.00 kernel freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My laptop hangs frequently, with a high cpu comsumption, don't react to 
Ctrl-Alt-whatever, only way to restart is hardware or fn-alt-print screen-B
  any other fn-alt-print screen combination doesn't works.
  I don't know how to trace what's wrong, or what component can be responsible.
  I have tried several X-servers, I have tried to disable hardware nvidia 
acceleration, etc. with no success

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-22-generic 4.13.0-22.25
  ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
  Uname: Linux 4.13.0-22-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rogelio2095 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Jan  3 13:37:36 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e26838c6-6b72-461d-a811-a892d423fac1
  InstallationDate: Installed on 2017-05-04 (244 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-22-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-22-generic N/A
   linux-backports-modules-4.13.0-22-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1741042/+subscriptions

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

[Kernel-packages] [Bug 1740991] Re: Ubuntu 16.04.3 LTS touchpad not work (asus x454L)

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.15 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.15-rc6

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

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

Title:
  Ubuntu 16.04.3 LTS touchpad not work (asus x454L)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have installed Ubuntu 16.04.3 LTS two time on my ASUS x454L laptop
  both time laptop touchpad not work at all. i applied many method
  nothing does work .

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

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

[Kernel-packages] [Bug 1741103] Re: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [gsd-clipboard:1445]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.15 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.15-rc6

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [gsd-clipboard:1445]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  starting system

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1027 F pulseaudio
piero  1387 F pulseaudio
  Date: Wed Jan  3 19:19:44 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=83c593ac-9ab2-404e-b14f-1e0c3064bd8a
  InstallationDate: Installed on 2018-01-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IwConfig:
   lono wireless extensions.
   
   enp0s15   no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=f0dd0298-1769-46a0-9988-d4d0e94a27e1 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [gsd-clipboard:1445]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS P5N-MX ACPI BIOS Revision 0903
  dmi.board.name: P5N-MX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-MXACPIBIOSRevision0903:bd07/07/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-MX:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1741167] Re: Mainline kernel 4.14.11 not booting on Lenovo X220

Can you see if the 4.15-rc6 kernel has the same issue:
 http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc6

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

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

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

Title:
  Mainline kernel 4.14.11 not booting on Lenovo X220

Status in linux package in Ubuntu:
  Triaged

Bug description:
  With Ubuntu 16.04.3 LTS (Xenial Xerus), Ubuntu mainline kernel 4.14.10
  or 4.14.11 for arch i386 does not boot on Lenovo Thinkpad X220. After
  GRUB message 'loading initrd' screen is cleared and machine restarts
  BIOS. Nothing is written to screen or system log.

  Mainline kernels up to 4.14.9 for arch i386 works fine.

  Booting same machine with mainline kernel 4.14.11 for arch amd64 works
  fine.

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

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

[Kernel-packages] [Bug 1741080] Re: cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped

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

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

Title:
  cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been dropped

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

Bug description:
  Hello,

  dmesg:
  [  141.782347] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been 
dropped
  [  142.828101] usbcore: registered new interface driver usbserial
  [  142.828159] usbcore: registered new interface driver usbserial_generic
  [  142.828207] usbserial: USB Serial support registered for generic
  [  142.840302] usbcore: registered new interface driver option
  [  142.840350] usbserial: USB Serial support registered for GSM modem (1-port)
  [  146.863549] cdc_ether 3-2:1.0 enx0c5b8f279a64: kevent 12 may have been 
dropped

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.14.0-13-generic 4.14.0-13.15
  ProcVersionSignature: Ubuntu 4.14.0-13.15-generic 4.14.7
  Uname: Linux 4.14.0-13-generic x86_64
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1740 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  3 13:13:02 2018
  InstallationDate: Installed on 2017-10-13 (82 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.14.0-13-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.14.0-13-generic N/A
   linux-backports-modules-4.14.0-13-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  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 manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1741080/+subscriptions

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

[Kernel-packages] [Bug 1741206] Re: QCA Rome bluetooth failed to work after applying reset-resume quirk

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

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

Title:
  QCA Rome bluetooth failed to work after applying reset-resume quirk

Status in linux package in Ubuntu:
  Triaged

Bug description:
  == SRU Justification ==
  [Impact]
  Some QCA ROME bluetooth devices does not work after runtime suspend/resume 
after SRU LP: #1734020.

  [Fix]
  The commit let btusb reset at second time it resume, i.e. btusb_open(). The 
btusb stops working because the reset happens *after* btusb_open(). The reset 
should be done at hub port initialization, before btusb_probe().

  Revert the bad commit and use the reset-resume quirk in USB core
  stack.

  [Test]
  Cherry-picked the commit into Artful/OEM kernel and the issue is fixed.

  [Regression Potential]
  Low. This is limited to QCA Rome, also verified by the original quirk author.

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

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

[Kernel-packages] [Bug 1741264] Re: Touchpad (Elan !?) not detected on Asus Zenbook UX32VD after new install

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.15 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.15-rc6

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

Title:
  Touchpad (Elan  !?) not detected on Asus Zenbook UX32VD after new
  install

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I've a fresh installed Ubuntu 16.04 on an Asus Zenbook UX32VD laptop.
  The touchpad does not work at all. It is not even listed in xinput.
  I'm not sure about the manufacturer but I think it is Elan

  I've tested with fresh install of Ubuntu 16.04.3 LTS
  I've also tested with live USB of Ubuntu 17.10, 14.04 LTS

  An USB connected mouse works perfectly.

  Thank you for your time
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2288/fd/17: Stale file handle
   Cannot stat file /proc/2288/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2208 F pulseaudio
  CasperVersion: 1.380
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/preseed/hostname.seed noprompt boot=casper 
iso-scan/filename=/hostname-17.04-desktop-amd64.iso quiet --
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  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-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  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/1741264/+subscriptions

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

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-01-04 Thread edenbar

Hi...same problem...i format hdd after see the problem ...no boot from
any usb...or pxe or cd..ni ubuntu ...no windows...pls help...

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

Title:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

---

Test Case: Fix has been verified by our HWE team on affected hardware.

Regression Potential: Minimal, it's unlikely anyone is actually doing
anything which requires this driver.

---

Affected Machines:

---

Original Description:

Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
reported a corrupted BIOS.

It's not possible to save new settings in BIOS anymore and after
rebooting, the system starts with the old settings.

Moreover (and most important) USB booting is not possible anymore
since USB is not recognized. It's very serious, since our machines do
not have a CDROM.

Lenovo forums at the moment are full of topics regading this issue.

Thank you!!

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

[Kernel-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)

2018-01-04 Thread Blake Rouse

** Changed in: systemd (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/1739672

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial)

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

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

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

[Kernel-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

2018-01-04 Thread Rafael David Tinoco

The scsi/iscsi team has accepted by fix proposal and merged the patch
for 4.16 merge window:

https://www.mail-archive.com/open-iscsi@googlegroups.com/msg10111.html

I'll propose the cherry-pick as SRU for Ubuntu kernels as soon as it is
merged.

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in linux package in Ubuntu:
  In Progress
Status in open-iscsi package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in open-iscsi source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in open-iscsi source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in open-iscsi source package in Artful:
  In Progress

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

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

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

[Kernel-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)

2018-01-04 Thread Blake Rouse

$ systemd-resolve --status
Global
  DNSSEC NTA: 10.in-addr.arpa
  16.172.in-addr.arpa
  168.192.in-addr.arpa
  17.172.in-addr.arpa
  18.172.in-addr.arpa
  19.172.in-addr.arpa
  20.172.in-addr.arpa
  21.172.in-addr.arpa
  22.172.in-addr.arpa
  23.172.in-addr.arpa
  24.172.in-addr.arpa
  25.172.in-addr.arpa
  26.172.in-addr.arpa
  27.172.in-addr.arpa
  28.172.in-addr.arpa
  29.172.in-addr.arpa
  30.172.in-addr.arpa
  31.172.in-addr.arpa
  corp
  d.f.ip6.arpa
  home
  internal
  intranet
  lan
  local
  private
  test

Link 8 (vethJWPPL8)
  Current Scopes: LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

Link 4 (lxdbr0)
  Current Scopes: LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

Link 3 (eno1)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 192.168.1.1

Link 2 (enp4s0)
  Current Scopes: none
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial)

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

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

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

[Kernel-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)

2018-01-04 Thread Blake Rouse

The issue is with the systemd resolver not with glibc.

With systemd-resolve IP in /etc/resolv.conf:

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 127.0.0.53

$ time ./test not-a-hostname
Trying to resolve: not-a-hostname
getaddrinfo errno: No such file or directory
getaddrinfo() return value: -2 (Name or service not known)

real0m10.076s
user0m0.001s
sys 0m0.000s


Without systemd-resolve in /etc/resolv.conf. I changed it to point to my local 
DNS server directly.

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
#nameserver 127.0.0.53
nameserver 192.168.1.1

$ time ./test not-a-hostname
Trying to resolve: not-a-hostname
getaddrinfo errno: No such file or directory
getaddrinfo() return value: -2 (Name or service not known)

real0m0.097s
user0m0.001s
sys 0m0.000s


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

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial)

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

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

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

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-01-04 Thread olekcz

Again, as Fabio mentioned
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/comments/452

What can we do if we have no way of running linux ? With possibility to
boot into Windows ONLY ?

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

Title:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

---

Test Case: Fix has been verified by our HWE team on affected hardware.

Regression Potential: Minimal, it's unlikely anyone is actually doing
anything which requires this driver.

---

Affected Machines:

---

Original Description:

Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
reported a corrupted BIOS.

It's not possible to save new settings in BIOS anymore and after
rebooting, the system starts with the old settings.

Moreover (and most important) USB booting is not possible anymore
since USB is not recognized. It's very serious, since our machines do
not have a CDROM.

Lenovo forums at the moment are full of topics regading this issue.

Thank you!!

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

[Kernel-packages] [Bug 1668105] Re: xhci_hcd module turns off usb host controller on boot

2018-01-04 Thread raffraffraff

Update: I've compiled the 4.13.19 kernel without USB 3 support (in the
hope that it would fall back to the USB 2 module - it doesn't - you end
up with no keyboard or trackpad). If you're running a system that has a
BIOS, and it allows you to turn off USB 3.0 support, that seems to be
the only option. Otherwise it appears that you're stuck with
intermittent USB. It sucks that MacBooks don't have ethernet... I'm
using a shared wifi AP even though I have a gigabit cable on my desk :(

There's a ton of USB 3.0 kernel bug tickets on launchpad, and in most
cases they end up expiring due to lack of updates. This one will likely
go the same way.

If ANYONE with a MacBook has managed to get it to work without USB 3.0
in the kernel, post here or PM me.

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

Title:
xhci_hcd module turns off usb host controller on boot

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

Bug description:
So we know this xhci_kcd was always shit in that it turns off the
console usb keyboard for long running computers and that it on abrupt
termination of Linux puts usb in a 12x slower mode. It is buggy, it
was always buggy, and its getting worse.

With Linux 4.8.0-37, this crappy software decides to halt the host
controller on boot, ie. turn off the console keyboard preventing any
boot. I cannot think of any situation where anyone would want their
host controller halted.

This is MacBook Pro 2015. So, it's already broken in UEFI-grub as it
always was, ie. every key press takes 8 seconds, but you only need
two, so you can boot in 16 s.

I tried to disable the xhci_kcd crap by using kernel parameter
noxhci_port_switch or modprobe.blacklist=xhci_hcd neither which works.

Because it has crap in UEFI, the computer will not boot any external
hard drive or usb fob. The only thing that works is Apple rescue that
gets rid of the xhci garbage, and the boot os x immediately after
that.

So the log output
xhci_hcd :00:14.0: Timeout while waiting for setup device command
xhci_hcd :00:14.0: xHCI host not responding to stop endpoint command.
- and a bit later:
xhci_hcd :00:14.0: Assuming host is dying, halting host.
xhci_hcd :00:14.0: HC died; cleaning up

This clown programming of Linux has to stop. Why would anyone ever want their
host controller halted?
---
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: foxyboy5662 F pulseaudio
/dev/snd/controlC0: foxyboy5662 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 16.10
HibernationDevice: RESUME=/dev/mapper/C89-SWAP
MachineType: Apple Inc. MacBookPro12,1
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic
root=/dev/mapper/C89-RFS ro i915.enable_rc6=0
ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
RelatedPackageVersions:
linux-restricted-modules-4.8.0-39-generic N/A
linux-backports-modules-4.8.0-39-generic N/A
linux-firmware1.161.1
Tags: yakkety
Uname: Linux 4.8.0-39-generic x86_64
UpgradeStatus: Upgraded to yakkety on 2016-11-16 (108 days ago)
UserGroups: adm docker libvirt libvirtd sudo
_MarkForUpload: True
dmi.bios.date: 10/26/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP121.88Z.0167.B15.1510261437
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.B15.1510261437:bd10/26/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.

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

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-01-04 Thread Jeremy Keiper

Lenovo Flex 3-1130 also fixed by step 8 in the description. Thank you
all!

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

Title:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

---

Test Case: Fix has been verified by our HWE team on affected hardware.

Regression Potential: Minimal, it's unlikely anyone is actually doing
anything which requires this driver.

---

Affected Machines:

---

Original Description:

Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
reported a corrupted BIOS.

It's not possible to save new settings in BIOS anymore and after
rebooting, the system starts with the old settings.

Moreover (and most important) USB booting is not possible anymore
since USB is not recognized. It's very serious, since our machines do
not have a CDROM.

Lenovo forums at the moment are full of topics regading this issue.

Thank you!!

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

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

apport information

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

Title:
  Touchpad (Elan  !?) not detected on Asus Zenbook UX32VD after new
  install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I've a fresh installed Ubuntu 16.04 on an Asus Zenbook UX32VD laptop.
  The touchpad does not work at all. It is not even listed in xinput.
  I'm not sure about the manufacturer but I think it is Elan

  I've tested with fresh install of Ubuntu 16.04.3 LTS
  I've also tested with live USB of Ubuntu 17.10, 14.04 LTS

  An USB connected mouse works perfectly.

  Thank you for your time
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2288/fd/17: Stale file handle
   Cannot stat file /proc/2288/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2208 F pulseaudio
  CasperVersion: 1.380
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/preseed/hostname.seed noprompt boot=casper 
iso-scan/filename=/hostname-17.04-desktop-amd64.iso quiet --
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  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-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  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/1741264/+subscriptions

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

[Kernel-packages] [Bug 1741264] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1741264/+attachment/5031049/+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/1741264

Title:
  Touchpad (Elan  !?) not detected on Asus Zenbook UX32VD after new
  install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I've a fresh installed Ubuntu 16.04 on an Asus Zenbook UX32VD laptop.
  The touchpad does not work at all. It is not even listed in xinput.
  I'm not sure about the manufacturer but I think it is Elan

  I've tested with fresh install of Ubuntu 16.04.3 LTS
  I've also tested with live USB of Ubuntu 17.10, 14.04 LTS

  An USB connected mouse works perfectly.

  Thank you for your time
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2288/fd/17: Stale file handle
   Cannot stat file /proc/2288/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2208 F pulseaudio
  CasperVersion: 1.380
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/preseed/hostname.seed noprompt boot=casper 
iso-scan/filename=/hostname-17.04-desktop-amd64.iso quiet --
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  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-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  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/1741264/+subscriptions

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

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

apport information

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

Title:
  Touchpad (Elan  !?) not detected on Asus Zenbook UX32VD after new
  install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I've a fresh installed Ubuntu 16.04 on an Asus Zenbook UX32VD laptop.
  The touchpad does not work at all. It is not even listed in xinput.
  I'm not sure about the manufacturer but I think it is Elan

  I've tested with fresh install of Ubuntu 16.04.3 LTS
  I've also tested with live USB of Ubuntu 17.10, 14.04 LTS

  An USB connected mouse works perfectly.

  Thank you for your time
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2288/fd/17: Stale file handle
   Cannot stat file /proc/2288/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2208 F pulseaudio
  CasperVersion: 1.380
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/preseed/hostname.seed noprompt boot=casper 
iso-scan/filename=/hostname-17.04-desktop-amd64.iso quiet --
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  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-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  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/1741264/+subscriptions

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

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

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1741264/+attachment/5031056/+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/1741264

Title:
  Touchpad (Elan  !?) not detected on Asus Zenbook UX32VD after new
  install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I've a fresh installed Ubuntu 16.04 on an Asus Zenbook UX32VD laptop.
  The touchpad does not work at all. It is not even listed in xinput.
  I'm not sure about the manufacturer but I think it is Elan

  I've tested with fresh install of Ubuntu 16.04.3 LTS
  I've also tested with live USB of Ubuntu 17.10, 14.04 LTS

  An USB connected mouse works perfectly.

  Thank you for your time
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2288/fd/17: Stale file handle
   Cannot stat file /proc/2288/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2208 F pulseaudio
  CasperVersion: 1.380
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/preseed/hostname.seed noprompt boot=casper 
iso-scan/filename=/hostname-17.04-desktop-amd64.iso quiet --
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  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-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  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/1741264/+subscriptions

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

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

apport information

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

Title:
  Touchpad (Elan  !?) not detected on Asus Zenbook UX32VD after new
  install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I've a fresh installed Ubuntu 16.04 on an Asus Zenbook UX32VD laptop.
  The touchpad does not work at all. It is not even listed in xinput.
  I'm not sure about the manufacturer but I think it is Elan

  I've tested with fresh install of Ubuntu 16.04.3 LTS
  I've also tested with live USB of Ubuntu 17.10, 14.04 LTS

  An USB connected mouse works perfectly.

  Thank you for your time
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2288/fd/17: Stale file handle
   Cannot stat file /proc/2288/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2208 F pulseaudio
  CasperVersion: 1.380
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/preseed/hostname.seed noprompt boot=casper 
iso-scan/filename=/hostname-17.04-desktop-amd64.iso quiet --
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  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-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  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/1741264/+subscriptions

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

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

apport information

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

Title:
  Touchpad (Elan  !?) not detected on Asus Zenbook UX32VD after new
  install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I've a fresh installed Ubuntu 16.04 on an Asus Zenbook UX32VD laptop.
  The touchpad does not work at all. It is not even listed in xinput.
  I'm not sure about the manufacturer but I think it is Elan

  I've tested with fresh install of Ubuntu 16.04.3 LTS
  I've also tested with live USB of Ubuntu 17.10, 14.04 LTS

  An USB connected mouse works perfectly.

  Thank you for your time
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2288/fd/17: Stale file handle
   Cannot stat file /proc/2288/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2208 F pulseaudio
  CasperVersion: 1.380
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/preseed/hostname.seed noprompt boot=casper 
iso-scan/filename=/hostname-17.04-desktop-amd64.iso quiet --
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  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-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  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/1741264/+subscriptions

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

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

apport information

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

Title:
  Touchpad (Elan  !?) not detected on Asus Zenbook UX32VD after new
  install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I've a fresh installed Ubuntu 16.04 on an Asus Zenbook UX32VD laptop.
  The touchpad does not work at all. It is not even listed in xinput.
  I'm not sure about the manufacturer but I think it is Elan

  I've tested with fresh install of Ubuntu 16.04.3 LTS
  I've also tested with live USB of Ubuntu 17.10, 14.04 LTS

  An USB connected mouse works perfectly.

  Thank you for your time
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2288/fd/17: Stale file handle
   Cannot stat file /proc/2288/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2208 F pulseaudio
  CasperVersion: 1.380
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/preseed/hostname.seed noprompt boot=casper 
iso-scan/filename=/hostname-17.04-desktop-amd64.iso quiet --
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  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-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  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/1741264/+subscriptions

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

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

apport information

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

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

Title:
  Touchpad (Elan  !?) not detected on Asus Zenbook UX32VD after new
  install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I've a fresh installed Ubuntu 16.04 on an Asus Zenbook UX32VD laptop.
  The touchpad does not work at all. It is not even listed in xinput.
  I'm not sure about the manufacturer but I think it is Elan

  I've tested with fresh install of Ubuntu 16.04.3 LTS
  I've also tested with live USB of Ubuntu 17.10, 14.04 LTS

  An USB connected mouse works perfectly.

  Thank you for your time
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2288/fd/17: Stale file handle
   Cannot stat file /proc/2288/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2208 F pulseaudio
  CasperVersion: 1.380
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/preseed/hostname.seed noprompt boot=casper 
iso-scan/filename=/hostname-17.04-desktop-amd64.iso quiet --
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  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-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  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/1741264/+subscriptions

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

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

apport information

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

Title:
  Touchpad (Elan  !?) not detected on Asus Zenbook UX32VD after new
  install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I've a fresh installed Ubuntu 16.04 on an Asus Zenbook UX32VD laptop.
  The touchpad does not work at all. It is not even listed in xinput.
  I'm not sure about the manufacturer but I think it is Elan

  I've tested with fresh install of Ubuntu 16.04.3 LTS
  I've also tested with live USB of Ubuntu 17.10, 14.04 LTS

  An USB connected mouse works perfectly.

  Thank you for your time
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2288/fd/17: Stale file handle
   Cannot stat file /proc/2288/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2208 F pulseaudio
  CasperVersion: 1.380
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/preseed/hostname.seed noprompt boot=casper 
iso-scan/filename=/hostname-17.04-desktop-amd64.iso quiet --
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  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-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  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/1741264/+subscriptions

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

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

apport information

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

Title:
  Touchpad (Elan  !?) not detected on Asus Zenbook UX32VD after new
  install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I've a fresh installed Ubuntu 16.04 on an Asus Zenbook UX32VD laptop.
  The touchpad does not work at all. It is not even listed in xinput.
  I'm not sure about the manufacturer but I think it is Elan

  I've tested with fresh install of Ubuntu 16.04.3 LTS
  I've also tested with live USB of Ubuntu 17.10, 14.04 LTS

  An USB connected mouse works perfectly.

  Thank you for your time
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2288/fd/17: Stale file handle
   Cannot stat file /proc/2288/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2208 F pulseaudio
  CasperVersion: 1.380
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/preseed/hostname.seed noprompt boot=casper 
iso-scan/filename=/hostname-17.04-desktop-amd64.iso quiet --
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  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-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  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/1741264/+subscriptions

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

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

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1741264/+attachment/5031052/+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/1741264

Title:
  Touchpad (Elan  !?) not detected on Asus Zenbook UX32VD after new
  install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I've a fresh installed Ubuntu 16.04 on an Asus Zenbook UX32VD laptop.
  The touchpad does not work at all. It is not even listed in xinput.
  I'm not sure about the manufacturer but I think it is Elan

  I've tested with fresh install of Ubuntu 16.04.3 LTS
  I've also tested with live USB of Ubuntu 17.10, 14.04 LTS

  An USB connected mouse works perfectly.

  Thank you for your time
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2288/fd/17: Stale file handle
   Cannot stat file /proc/2288/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2208 F pulseaudio
  CasperVersion: 1.380
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/preseed/hostname.seed noprompt boot=casper 
iso-scan/filename=/hostname-17.04-desktop-amd64.iso quiet --
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  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-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  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/1741264/+subscriptions

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

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

apport information

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

Title:
  Touchpad (Elan  !?) not detected on Asus Zenbook UX32VD after new
  install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I've a fresh installed Ubuntu 16.04 on an Asus Zenbook UX32VD laptop.
  The touchpad does not work at all. It is not even listed in xinput.
  I'm not sure about the manufacturer but I think it is Elan

  I've tested with fresh install of Ubuntu 16.04.3 LTS
  I've also tested with live USB of Ubuntu 17.10, 14.04 LTS

  An USB connected mouse works perfectly.

  Thank you for your time
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2288/fd/17: Stale file handle
   Cannot stat file /proc/2288/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2208 F pulseaudio
  CasperVersion: 1.380
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/preseed/hostname.seed noprompt boot=casper 
iso-scan/filename=/hostname-17.04-desktop-amd64.iso quiet --
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  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-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  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/1741264/+subscriptions

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

[Kernel-packages] [Bug 1741264] Re: Touchpad (Elan !?) not detected on Asus Zenbook UX32VD after new install

** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741264/+attachment/5031060/+files/Xorg.0.log

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

Title:
  Touchpad (Elan  !?) not detected on Asus Zenbook UX32VD after new
  install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I've a fresh installed Ubuntu 16.04 on an Asus Zenbook UX32VD laptop.
  The touchpad does not work at all. It is not even listed in xinput.
  I'm not sure about the manufacturer but I think it is Elan

  I've tested with fresh install of Ubuntu 16.04.3 LTS
  I've also tested with live USB of Ubuntu 17.10, 14.04 LTS

  An USB connected mouse works perfectly.

  Thank you for your time
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2288/fd/17: Stale file handle
   Cannot stat file /proc/2288/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2208 F pulseaudio
  CasperVersion: 1.380
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/preseed/hostname.seed noprompt boot=casper 
iso-scan/filename=/hostname-17.04-desktop-amd64.iso quiet --
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  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-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  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/1741264/+subscriptions

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

[Kernel-packages] [Bug 1741264] AlsaInfo.txt

apport information

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

Title:
  Touchpad (Elan  !?) not detected on Asus Zenbook UX32VD after new
  install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I've a fresh installed Ubuntu 16.04 on an Asus Zenbook UX32VD laptop.
  The touchpad does not work at all. It is not even listed in xinput.
  I'm not sure about the manufacturer but I think it is Elan

  I've tested with fresh install of Ubuntu 16.04.3 LTS
  I've also tested with live USB of Ubuntu 17.10, 14.04 LTS

  An USB connected mouse works perfectly.

  Thank you for your time
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2288/fd/17: Stale file handle
   Cannot stat file /proc/2288/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2208 F pulseaudio
  CasperVersion: 1.380
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/preseed/hostname.seed noprompt boot=casper 
iso-scan/filename=/hostname-17.04-desktop-amd64.iso quiet --
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  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-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  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/1741264/+subscriptions

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

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