date:20180523

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

apport-collect 1773010

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

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

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

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

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

Title:
   [18.04] [regression testing] ubuntu_kvm_unit_tests tests failing on
  amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  See for example: http://10.246.72.4/test-
  
results/4.15.0-21.22-generic/ubuntu_kvm_unit_tests-4.15.0-21.22-amd64-index.html

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

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

[Kernel-packages] [Bug 1770916] Re: package crda 3.18-1build1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.2

2018-05-23 Thread Martina Neumayer

I forgot to mention that the package version in Mint is: crda 
(3.13-1ubuntu0.16.04.1) xenial,
but the entire issue is exactly that same as here above described.


** Attachment added: "screenshot_2.png"
   
https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1770916/+attachment/5143512/+files/screenshot_2.png

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

Title:
  package crda 3.18-1build1 failed to install/upgrade: trying to
  overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in
  package wireless-regdb 2015.07.20-1ubuntu1

Status in crda package in Ubuntu:
  Confirmed

Bug description:
  On upgrading 16.04 - >18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: crda 3.18-1build1
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  AptOrdering:
   crda:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May 12 13:51:43 2018
  DpkgTerminalLog:
   Preparing to unpack .../crda_3.18-1build1_amd64.deb ...
   Unpacking crda (3.18-1build1) over (3.13-1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/crda_3.18-1build1_amd64.deb (--unpack):
trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also 
in package wireless-regdb 2015.07.20-1ubuntu1
  DuplicateSignature:
   package:crda:3.18-1build1
   Unpacking crda (3.18-1build1) over (3.13-1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/crda_3.18-1build1_amd64.deb (--unpack):
trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also 
in package wireless-regdb 2015.07.20-1ubuntu1
  ErrorMessage: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', 
which is also in package wireless-regdb 2015.07.20-1ubuntu1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: crda
  Title: package crda 3.18-1build1 failed to install/upgrade: trying to 
overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package 
wireless-regdb 2015.07.20-1ubuntu1
  UpgradeStatus: Upgraded to bionic on 2018-05-12 (0 days ago)

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

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

[Kernel-packages] [Bug 1770916] Re: package crda 3.18-1build1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.2

2018-05-23 Thread Martina Neumayer

And one more screenshot..


** Attachment added: "screenshot_1.png"
   
https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1770916/+attachment/5143513/+files/screenshot_1.png

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

Title:
  package crda 3.18-1build1 failed to install/upgrade: trying to
  overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in
  package wireless-regdb 2015.07.20-1ubuntu1

Status in crda package in Ubuntu:
  Confirmed

Bug description:
  On upgrading 16.04 - >18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: crda 3.18-1build1
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  AptOrdering:
   crda:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May 12 13:51:43 2018
  DpkgTerminalLog:
   Preparing to unpack .../crda_3.18-1build1_amd64.deb ...
   Unpacking crda (3.18-1build1) over (3.13-1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/crda_3.18-1build1_amd64.deb (--unpack):
trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also 
in package wireless-regdb 2015.07.20-1ubuntu1
  DuplicateSignature:
   package:crda:3.18-1build1
   Unpacking crda (3.18-1build1) over (3.13-1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/crda_3.18-1build1_amd64.deb (--unpack):
trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also 
in package wireless-regdb 2015.07.20-1ubuntu1
  ErrorMessage: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', 
which is also in package wireless-regdb 2015.07.20-1ubuntu1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: crda
  Title: package crda 3.18-1build1 failed to install/upgrade: trying to 
overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package 
wireless-regdb 2015.07.20-1ubuntu1
  UpgradeStatus: Upgraded to bionic on 2018-05-12 (0 days ago)

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

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

[Kernel-packages] [Bug 1772991] Re: [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable Nvidia driver on bare metal

I built a Bionic test kernel with the 9 commits posted in the bug description.  
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1772991

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

Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the 
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the 
linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.

Thanks in advance!

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

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

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

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

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

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

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

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

Title:
  [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable
  Nvidia driver on bare metal

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

Bug description:
  == Comment: #0 - Barry B. Arndt  - 2018-05-23 13:40:33 ==
  12 kernel patches have been identified as needed to support Nvidia Volta on 
bare metal.  All are accepted upstream in 4.17.  Three of those are already in 
bionic, leaving a total of 9 remaining commits needed in bionic.  Those 9 
commits are:

  720c84046c26  powerpc/npu-dma.c: Fix crash after __mmu_notifier_register 
failure
  2b74e2a9b39d  powerpc/powernv/npu: Fix deadlock in mmio_invalidate()
  5ee573e8ef03  powerpc/powernv/mce: Don't silently restart the machine
  fb5924fddf9e  powerpc/mm: Flush cache on memory hot(un)plug
  7fd6641de28f  powerpc/powernv/memtrace: Let the arch hotunplug code flush 
cache
  28a5933e8d36  powerpc/powernv/npu: Add lock to prevent race in concurrent 
context init/destroy
  a1409adac748  powerpc/powernv/npu: Prevent overwriting of 
pnv_npu2_init_contex() callback parameters
  d0cf9b561ca9  powerpc/powernv/npu: Do a PID GPU TLB flush when invalidating a 
large address range
  75ecfb49516c  powerpc/mce: Fix a bug where mce loops on memory UE.

  We cherry-picked the commits, and all applied cleanly.  The resultant
  kernel built successfully and loaded.

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

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

[Kernel-packages] [Bug 1685442] Re: Errors: flip_done timed out during boot-up; slow boot

2018-05-23 Thread Bug Watch Updater

** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => 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/1685442

Title:
  Errors:  flip_done timed out  during boot-up; slow boot

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

Bug description:
  I had been running Ubuntu 16.04 LTS on many laptop computers
  (especially Dell D620, D630, E6400) with no problem.

  I created a Live USB with Ubuntu 16.04.2 LTS and tried it on a Dell
  D630.  It was very slow to boot up (about 90 seconds) as opposed to
  the 30-45 seconds it usually takes. For a few seconds there were error
  messages that included the phrase "flip_done timed out".

  When the Ubuntu desktop appeared, the mouse cursor hung for a while,
  but then came back to life. I didn't do much testing from there.  I
  did a Live session with the 16.04.2 LTS  on a different D630 laptop,
  and the same problem occureed.

  I Googled the problem, and found several hits.
  -
  On an Arch forum, someone reported the problem on a Dell D630, like mine. It 
also occured on other laptops:
  https://bbs.archlinux.org/viewtopic.php?id=218581

  The suggestion was that the bug was related to kernel version 4.8.x
  and the 965GM chipset, which is what the D630 has.

  So I tried Ubuntu Mate 16.04.2 on a Dell D620 (with a 945GM chipset) and the 
problem DID NOT occur.
  ---
  For a similar boot-up problem, Ubuntu Forum suggested going back to an 
earlier version of Ubuntu.
  https://ubuntuforums.org/showthread.php?t=2348892

  I tried Ubuntu Mate 16.04.1 (with the 4.4.0-31-generic kernel), and
  the problem did NOT occur.

  So I'm solving the problem for myself by using Ubuntu Mate 16.04.1 LTS rather 
than 16.04.2.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  test   2194 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Dell Inc. Latitude D630
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0KU184
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D630
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  test   2194 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Dell Inc. Latitude D630
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A

[Kernel-packages] [Bug 1764645] Re: Bluetooth not working

2018-05-23 Thread mrcastro

I can confirm it works now, following instructions on #27

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

Title:
  Bluetooth not working

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

Bug description:
  I've installed the Ubuntu Bionic Beta 2 and everything works fine but
  the bluetooth (perfectly working with Xenial). In bluetooth control
  panel the slider is impossible to move to "on".

  1) Ubuntu Release (via 'lsb_release -rd')
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2) Version of package (apt-cache policy gnome-bluetooth)
  gnome-bluetooth:
Installato: 3.28.0-2
Candidato:  3.28.0-2
Tabella versione:
   *** 3.28.0-2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  I expected to switch on the bluetooth.

  4) What happened instead
  Bluetooth won't switch on.

  5) Output of rfkill list is:
  0: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no
  1: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no

  6) Output of lspci -knn | grep Net -A3; lsusb; dmesg | grep -i blue is:
  03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless 
  Network Adapter [168c:0034] (rev 01)
  Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half- 
  size Mini PCIe Card [1a56:2003]
  Kernel driver in use: ath9k
  Kernel modules: ath9k
  04:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit 
  Ethernet [1969:10a1] (rev 10)
  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 04f2:b414 Chicony Electronics Co., Ltd 
  Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc. 
   
  AR3012 Bluetooth 4.0
  Bus 003 Device 002: ID 0b05:17c4 ASUSTek Computer, Inc. 
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [   17.715399] Bluetooth: Core ver 2.22
  [   17.715414] Bluetooth: HCI device and connection manager initialized
  [   17.715416] Bluetooth: HCI socket layer initialized
  [   17.715418] Bluetooth: L2CAP socket layer initialized
  [   17.715422] Bluetooth: SCO socket layer initialized
  [   17.723207] Bluetooth: hci0: don't support firmware rome 0x1102
  [   18.600648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   18.600649] Bluetooth: BNEP filters: protocol multicast
  [   18.600651] Bluetooth: BNEP socket layer initialized

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stormy 1484 F pulseaudio
   /dev/snd/controlC0:  stormy 1484 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 17 08:46:30 2018
  HibernationDevice: RESUME=UUID=3f513ca9-6817-4099-9718-fee68d68ec11
  InstallationDate: Installed on 2018-04-16 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  MachineType: ASUSTeK COMPUTER INC. G750JH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G750JH.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G750JH
  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.:bvrG750JH.206:bd12/02/2013:svnASUSTeKCOMPUTERINC.:pnG750JH:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG750JH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G750JH
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage

[Kernel-packages] [Bug 1772024] Re: linux 4.13.0-42.47 ADT test failure with linux 4.13.0-42.47 (nbd-smoke-test)

2018-05-23 Thread Thadeu Lima de Souza Cascardo

** Patch added: "fixes the bug on bionic"
   
https://bugs.launchpad.net/ubuntu/cosmic/+source/nbd/+bug/1772024/+attachment/5143466/+files/nbd_3.17-2ubuntu1.debdiff

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

Title:
  linux 4.13.0-42.47 ADT test failure with linux 4.13.0-42.47 (nbd-
  smoke-test)

Status in linux package in Ubuntu:
  In Progress
Status in nbd package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  New
Status in nbd source package in Trusty:
  New
Status in linux source package in Xenial:
  New
Status in nbd source package in Xenial:
  New
Status in linux source package in Artful:
  New
Status in nbd source package in Artful:
  New
Status in linux source package in Bionic:
  New
Status in nbd source package in Bionic:
  New
Status in linux source package in Cosmic:
  In Progress
Status in nbd source package in Cosmic:
  In Progress

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/l/linux/20180518_040741_b3b54@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/i386/l/linux/20180518_050911_b3b54@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/l/linux/20180518_040734_b3b54@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/s390x/l/linux/20180518_035527_b3b54@/log.gz

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

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

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

apport information

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

Title:
  Touchpad slows down and then stops working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Cannot find a reason, but sometimes once a day, sometimes twice a day,
  my touchpad starts to work slowly, like jumping, and after a few
  seconds, it completely stops working. At some point, I did something
  with Terminal and it started working, but cannot reproduce it. The
  only thing that seems to be really working is to Suspend laptop and
  come back in Ubuntu (or restart, but that means to close everything +
  it takes more time). While I wrote this text, it seems to have
  recovered by itself, it is working right now, but this is unreliable
  and cannot be used in production (what about stopping it during a
  presentation, cannot suspend in a meeting). Hopefully, it is some
  kernel problem, as I reported kernel package.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 01:15:44 2018
  InstallationDate: Installed on 2018-04-27 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   florin 2029 F...m pulseaudio
   /dev/snd/controlC0:  florin 2029 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=99eb1e80-1ec0-4526-8cff-0691084ec0f8
  InstallationDate: Installed on 2018-04-27 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:5652 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA SATELLITE P50-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=470c0ce8-f352-4f58-977c-af6d3998d302 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2017
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.50
  dmi.board.name: 06F4
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/05/2017:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUFE-001009G6:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE P50-C
  dmi.product.version: PSPUFE-001009G6
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29

2018-05-23 Thread Brett Johnson

This is still a problem in bionic as well.  I just did a clean install
on a workstation which exhibits the problem, but I also have a laptop
which was upgraded from 17.10, which has not ever exhibited the problem.

I've attached lshw output for the two machines (inara is the machine for
which suspend/resume works, vera is the one that doesn't)

** Attachment added: "lshw output for two machines.  "inara" works properly, 
and "vera" suspends (very slowly), but does not ever resume"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/+attachment/5143504/+files/lshw-inara-vera.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/1743094

Title:
  [regression] hibernation (freezes on resume) since 4.13.0-25.29

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

Bug description:
  After hibernating the system and than resuming it the system reboots
  notifying that it is resuming and than stops/freezes. The system does
  not respond to anything (no tty's other notifying textg are
  available).

  
  After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep 
functions as proposed.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jb 1717 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478
  InstallationDate: Installed on 2017-12-10 (34 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: Acer Aspire S3-391
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic 
root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-26-generic N/A
   linux-backports-modules-4.13.0-26-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Hummingbird2
  dmi.board.vendor: Acer
  dmi.board.version: V2.10
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.10
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S3-391
  dmi.product.version: V2.10
  dmi.sys.vendor: Acer

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

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

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

apport information

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

Title:
  Touchpad slows down and then stops working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Cannot find a reason, but sometimes once a day, sometimes twice a day,
  my touchpad starts to work slowly, like jumping, and after a few
  seconds, it completely stops working. At some point, I did something
  with Terminal and it started working, but cannot reproduce it. The
  only thing that seems to be really working is to Suspend laptop and
  come back in Ubuntu (or restart, but that means to close everything +
  it takes more time). While I wrote this text, it seems to have
  recovered by itself, it is working right now, but this is unreliable
  and cannot be used in production (what about stopping it during a
  presentation, cannot suspend in a meeting). Hopefully, it is some
  kernel problem, as I reported kernel package.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 01:15:44 2018
  InstallationDate: Installed on 2018-04-27 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   florin 2029 F...m pulseaudio
   /dev/snd/controlC0:  florin 2029 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=99eb1e80-1ec0-4526-8cff-0691084ec0f8
  InstallationDate: Installed on 2018-04-27 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:5652 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA SATELLITE P50-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=470c0ce8-f352-4f58-977c-af6d3998d302 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2017
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.50
  dmi.board.name: 06F4
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/05/2017:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUFE-001009G6:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE P50-C
  dmi.product.version: PSPUFE-001009G6
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1772760] PulseList.txt

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1772760/+attachment/5143428/+files/PulseList.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/1772760

Title:
  Touchpad slows down and then stops working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Cannot find a reason, but sometimes once a day, sometimes twice a day,
  my touchpad starts to work slowly, like jumping, and after a few
  seconds, it completely stops working. At some point, I did something
  with Terminal and it started working, but cannot reproduce it. The
  only thing that seems to be really working is to Suspend laptop and
  come back in Ubuntu (or restart, but that means to close everything +
  it takes more time). While I wrote this text, it seems to have
  recovered by itself, it is working right now, but this is unreliable
  and cannot be used in production (what about stopping it during a
  presentation, cannot suspend in a meeting). Hopefully, it is some
  kernel problem, as I reported kernel package.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 01:15:44 2018
  InstallationDate: Installed on 2018-04-27 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   florin 2029 F...m pulseaudio
   /dev/snd/controlC0:  florin 2029 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=99eb1e80-1ec0-4526-8cff-0691084ec0f8
  InstallationDate: Installed on 2018-04-27 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:5652 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA SATELLITE P50-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=470c0ce8-f352-4f58-977c-af6d3998d302 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2017
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.50
  dmi.board.name: 06F4
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/05/2017:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUFE-001009G6:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE P50-C
  dmi.product.version: PSPUFE-001009G6
  dmi.sys.vendor: TOSHIBA

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

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

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

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1772760/+attachment/5143429/+files/RfKill.txt

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

Title:
  Touchpad slows down and then stops working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Cannot find a reason, but sometimes once a day, sometimes twice a day,
  my touchpad starts to work slowly, like jumping, and after a few
  seconds, it completely stops working. At some point, I did something
  with Terminal and it started working, but cannot reproduce it. The
  only thing that seems to be really working is to Suspend laptop and
  come back in Ubuntu (or restart, but that means to close everything +
  it takes more time). While I wrote this text, it seems to have
  recovered by itself, it is working right now, but this is unreliable
  and cannot be used in production (what about stopping it during a
  presentation, cannot suspend in a meeting). Hopefully, it is some
  kernel problem, as I reported kernel package.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 01:15:44 2018
  InstallationDate: Installed on 2018-04-27 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   florin 2029 F...m pulseaudio
   /dev/snd/controlC0:  florin 2029 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=99eb1e80-1ec0-4526-8cff-0691084ec0f8
  InstallationDate: Installed on 2018-04-27 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:5652 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA SATELLITE P50-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=470c0ce8-f352-4f58-977c-af6d3998d302 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2017
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.50
  dmi.board.name: 06F4
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/05/2017:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUFE-001009G6:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE P50-C
  dmi.product.version: PSPUFE-001009G6
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1772760] Re: Touchpad slows down and then stops working

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

Title:
  Touchpad slows down and then stops working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Cannot find a reason, but sometimes once a day, sometimes twice a day,
  my touchpad starts to work slowly, like jumping, and after a few
  seconds, it completely stops working. At some point, I did something
  with Terminal and it started working, but cannot reproduce it. The
  only thing that seems to be really working is to Suspend laptop and
  come back in Ubuntu (or restart, but that means to close everything +
  it takes more time). While I wrote this text, it seems to have
  recovered by itself, it is working right now, but this is unreliable
  and cannot be used in production (what about stopping it during a
  presentation, cannot suspend in a meeting). Hopefully, it is some
  kernel problem, as I reported kernel package.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 01:15:44 2018
  InstallationDate: Installed on 2018-04-27 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   florin 2029 F...m pulseaudio
   /dev/snd/controlC0:  florin 2029 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=99eb1e80-1ec0-4526-8cff-0691084ec0f8
  InstallationDate: Installed on 2018-04-27 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:5652 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA SATELLITE P50-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=470c0ce8-f352-4f58-977c-af6d3998d302 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2017
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.50
  dmi.board.name: 06F4
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/05/2017:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUFE-001009G6:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE P50-C
  dmi.product.version: PSPUFE-001009G6
  dmi.sys.vendor: TOSHIBA

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

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

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

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

apport-collect 1773005

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

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

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

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

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

Title:
   [18.04] [regression testing] ubuntu_lxc tests failing on amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  See for example: http://10.246.72.4/test-
  results/4.15.0-21.22-generic/ubuntu_lxc-4.15.0-21.22-amd64-index.html

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

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

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

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

apport-collect 1773002

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

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

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

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

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

Title:
   [18.04] [regression testing] libhugetlbfs tests failing on amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  See for example: http://10.246.72.4/test-
  results/4.15.0-21.22-generic/libhugetlbfs-4.15.0-21.22-amd64-index.html

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

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

[Kernel-packages] [Bug 1773011] [NEW] [18.04] [regression testing] ubuntu_ltp tests failing on amd64

Public bug reported:

See for example: http://10.246.72.4/test-
results/4.15.0-21.22-generic/ubuntu_ltp-4.15.0-21.22-amd64-index.html

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


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

Title:
   [18.04] [regression testing] ubuntu_ltp tests failing on amd64

Status in linux package in Ubuntu:
  New

Bug description:
  See for example: http://10.246.72.4/test-
  results/4.15.0-21.22-generic/ubuntu_ltp-4.15.0-21.22-amd64-index.html

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

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

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

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

apport-collect 1773011

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

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

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

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

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

Title:
   [18.04] [regression testing] ubuntu_ltp tests failing on amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  See for example: http://10.246.72.4/test-
  results/4.15.0-21.22-generic/ubuntu_ltp-4.15.0-21.22-amd64-index.html

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

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

[Kernel-packages] [Bug 1772154] Re: Unstable WiFi adapter Gigabyte GC-WB867D-I

2018-05-23 Thread Gabriele N. Tornetta

As per instructions received, I have tested v4.17-rc6 of the Ubuntu
Linux Kernel (http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc6/)
and the problem still persists.

** Tags added: kernel-bug-exists-upstream

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

Title:
  Unstable WiFi adapter Gigabyte GC-WB867D-I

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The WiFi adapter Gigabyte GC-WB867D-I is quite unstable on Ubuntu
  18.04. I do not have data relative to previous versions of Ubuntu
  since this PCIe card is part of a new build that has had 18.04 as the
  first installed version.

  The reason why I can point the finger at the Linux kernel is that the
  card seems to work reliably well on Windows 10 (no packet loss when
  pinging the local router). On Ubuntu 18.04, the card's behaviour seems
  very correlated to the signal strength and exhibits a threshold
  phenomenon. With the antenna placed in an obstacle-free area, some
  ping packets are occasionally lost. But when some objects are placed
  near the antenna (e.g. a phone), the packet loss can get up to 90%.
  Under the very same conditions, the packet loss on Windows is exactly
  0 (and the RTT never gets above 500ms).

  I have disabled the WiFi power saving (changed from 2 to 3) but that
  didn't fix the problem. It seems that restarting the NetworkManager
  service helps for a bit, but after a while the problem resurfaces.

  The card in question has onboard USB Bluetooth and is pretty much an
  M.2 to PCIe x1 adapter for an Intel Wifi adapter. The relevant output
  of lspci is

  03:00.0 Network controller: Intel Corporation Wireless 8265 / 8275
  (rev 78)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 19 10:32:00 2018
  InstallationDate: Installed on 2018-04-29 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D7p:   gabriele   1893 F...m pulseaudio
   /dev/snd/controlC1:  gabriele   1893 F pulseaudio
   /dev/snd/controlC0:  gabriele   1893 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=d2390d6b-2bc3-41bb-b385-3dd8921a36e2
  InstallationDate: Installed on 2018-04-29 (22 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=2e79827f-410a-4aba-ab8f-e278ca6e7aa3 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: B360M Pro4
  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.10:bd03/07/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB360MPro4: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/1772154/+subscriptions

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

[Kernel-packages] [Bug 1767857] Re: Kernel 4.4.0-122 Breaks qemu-system-x86

2018-05-23 Thread Skipper

qemu-system-x86 broken when running kernel 4.4.0-127 as well - same
result (black screen displays and qemu-system-x86 runs at 100% cpu
indefinitely).

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

Title:
  Kernel 4.4.0-122 Breaks qemu-system-x86

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Fully updated xubuntu 16.04 running kernel 4.4.0-122 breaks qemu-
  system-x86: black screen displays and qemu-system-x86 runs at 100% cpu
  indefinitely. Boot the same system with kernel 4.4.0-119 and qemu-
  system-x86 works fine running a Windows 10 VM.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu-system-x86 1:2.5+dfsg-5ubuntu10.25
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic i686
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sun Apr 29 15:58:25 2018
  InstallationDate: Installed on 2014-04-29 (1460 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0   394 2  0.0 [kvm-irqfd-clean]
  MachineType: Dell Inc. Inspiron 518
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic 
root=UUID=7cffb293-c044-4b2c-8343-dc50fd16db97 ro --verbose nosplash 
nmi_watchdog=0
  SourcePackage: qemu
  UpgradeStatus: Upgraded to xenial on 2016-08-10 (627 days ago)
  dmi.bios.date: 03/30/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.8
  dmi.board.name: 0K068D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.8:bd03/30/2009:svnDellInc.:pnInspiron518:pvr00:rvnDellInc.:rn0K068D:rvrA00:cvnDellInc.:ct3:cvrOEM:
  dmi.product.name: Inspiron 518
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1660887] Free $5 for both of us...easy and helpful to me!

2018-05-23 Thread Lehel Kovach

Cash App is like Venmo…but better.  I need the cash.  Install the app and send 
me your $5 if you are charitable lol.  Feel free to uninstall it if you don’t 
like the app.  But it would help me out.
Thanks!

Try Cash App using my code and we’ll each get $5! TPJSDJB
https://cash.me/app/TPJSDJB

Sent from Mail for
Windows 10

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

Title:
  package linux-base 4.0ubuntu1 failed to install/upgrade: trying to
  overwrite '/usr/bin/perf', which is also in package linux-tools-common
  4.4.0-59.80

Status in linux-base package in Ubuntu:
  Confirmed

Bug description:
  asdf

  ProblemType: Package
  DistroRelease: Kali 2016.2
  Package: linux-base 4.5
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sun Jan 29 20:56:53 2017
  Dependencies:
   
  ErrorMessage: trying to overwrite '/usr/bin/perf', which is also in package 
linux-tools-common 4.4.0-59.80
  InstallationDate: Installed on 2016-09-30 (123 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.15kali1
   apt  1.2.15ubuntu0.2
  SourcePackage: linux-base
  Title: package linux-base 4.0ubuntu1 failed to install/upgrade: trying to 
overwrite '/usr/bin/perf', which is also in package linux-tools-common 
4.4.0-59.80
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1772775] Re: 4.4.0-127.153 generates many "sit: non-ECT" messages

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

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

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

** Changed in: linux (Ubuntu Xenial)
   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/1772775

Title:
  4.4.0-127.153 generates many "sit: non-ECT" messages

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

Bug description:
  Since deploying linux-image-4.4.0-127-generic (4.4.0-127.153) on a
  Xenial VM with a sit tunnel, I get such messages:

  May 22 10:49:38 gw kernel: [   68.121601] sit: non-ECT from 0.0.0.0
  with TOS=0x5

  Those are logged quite often:

  # grep -cF 'sit: non-ECT' /var/log/syslog
  9108

  Reverting to linux-image-4.4.0-124-generic (4.4.0-124.148) fixes the
  issue.

  # lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04
  # apt-cache policy linux-image-4.4.0-127-generic
  linux-image-4.4.0-127-generic:
Installed: 4.4.0-127.153
Candidate: 4.4.0-127.153
Version table:
   *** 4.4.0-127.153 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-127-generic 4.4.0-127.153
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 20:08 seq
   crw-rw 1 root audio 116, 33 May 22 20:08 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  Date: Tue May 22 21:18:45 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic 
root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro console=ttyS0 net.ifnames=0 
kaslr vsyscall=none nmi_watchdog=0 possible_cpus=1 pti=on nr_cpus=1
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-127-generic N/A
   linux-backports-modules-4.4.0-127-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.5
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.5
  dmi.sys.vendor: QEMU
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 21:33 seq
   crw-rw 1 root audio 116, 33 May 22 21:33 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro kaslr net.ifnames=0 
nmi_watchdog=0 nr_cpus=1 pti=on console=ttyS0 vsyscall=none
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-124-generic N/A
   linux-backports-modules-4.4.0-124-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-124-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor:

[Kernel-packages] [Bug 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29

2018-05-23 Thread Brett Johnson

Hmm, in a somewhat disheartening turn of events, I thought I'd try
installing the nvidia proprietary driver on my workstation (that's what
I had installed on 16.04, when suspend/resume worked).  ...And now,
suspend/resume works perfectly (and quickly) on the workstation.  So
maybe this is a nouveau bug?  Is everyone else having problems using
nvidia graphics hardware with the nouveau driver?

** Also affects: xserver-xorg-video-nouveau (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [regression] hibernation (freezes on resume) since 4.13.0-25.29

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New
Status in linux source package in Artful:
  Confirmed

Bug description:
  After hibernating the system and than resuming it the system reboots
  notifying that it is resuming and than stops/freezes. The system does
  not respond to anything (no tty's other notifying textg are
  available).

  
  After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep 
functions as proposed.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jb 1717 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478
  InstallationDate: Installed on 2017-12-10 (34 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: Acer Aspire S3-391
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic 
root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-26-generic N/A
   linux-backports-modules-4.13.0-26-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Hummingbird2
  dmi.board.vendor: Acer
  dmi.board.version: V2.10
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.10
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S3-391
  dmi.product.version: V2.10
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1772024] Re: linux 4.13.0-42.47 ADT test failure with linux 4.13.0-42.47 (nbd-smoke-test)

2018-05-23 Thread Thadeu Lima de Souza Cascardo

Package did not apply patches from debian/patches/, added --with quilt
to dh call on debian/rules, fixing this.

** Patch removed: "fixes the bug on cosmic"
   
https://bugs.launchpad.net/ubuntu/cosmic/+source/nbd/+bug/1772024/+attachment/5143466/+files/nbd_3.17-2ubuntu1.debdiff

** Patch added: "really fixes bug on cosmic"
   
https://bugs.launchpad.net/ubuntu/cosmic/+source/nbd/+bug/1772024/+attachment/5143515/+files/nbd_3.17-2ubuntu1.debdiff

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

Title:
  linux 4.13.0-42.47 ADT test failure with linux 4.13.0-42.47 (nbd-
  smoke-test)

Status in linux package in Ubuntu:
  In Progress
Status in nbd package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  New
Status in nbd source package in Trusty:
  New
Status in linux source package in Xenial:
  New
Status in nbd source package in Xenial:
  New
Status in linux source package in Artful:
  New
Status in nbd source package in Artful:
  New
Status in linux source package in Bionic:
  New
Status in nbd source package in Bionic:
  New
Status in linux source package in Cosmic:
  In Progress
Status in nbd source package in Cosmic:
  In Progress

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/l/linux/20180518_040741_b3b54@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/i386/l/linux/20180518_050911_b3b54@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/l/linux/20180518_040734_b3b54@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/s390x/l/linux/20180518_035527_b3b54@/log.gz

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

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

[Kernel-packages] [Bug 1768431] Re: Request to revert SAUCE patches in the 18.04 SRU and update with upstream version

What type or errors are you seeing?  Can you post them?  You need to
install the packages in this order:

linux-modules-4.15.0-20-generic_4.15.0-20.22~lp1768431DiffPatched_ppc64el.deb
linux-modules-extra-4.15.0-20-generic_4.15.0-20.22~lp1768431DiffPatched_ppc64el.deb
linux-image-unsigned-4.15.0-20-generic_4.15.0-20.22~lp1768431DiffPatched_ppc64el.deb

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

Title:
  Request to revert SAUCE patches in the 18.04 SRU and update with
  upstream version

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

Bug description:
  == Comment: #0 - UMA KRISHNAN  - 2018-04-30 14:41:30 ==
  ---Problem Description---
  Request to revert SAUCE patches from 18.04 and apply the patches from 
next/master.

  Below set of cxlflash patches were submitted to Canonical after they
  were sent to the community. Based on review comments, there has been
  minor changes from that version. This BZ is to request reverting those
  SAUCE patches with the ones that are queued in next/master tree for
  4.18.

  - SAUCE: cxlflash: Preserve number of interrupts for master contexts
  - SAUCE: cxlflash: Avoid clobbering context control register value
  - SAUCE: cxlflash: Add argument identifier names
  - SAUCE: cxlflash: Introduce OCXL backend
  - SAUCE: cxlflash: Hardware AFU for OCXL
  - SAUCE: cxlflash: Read host function configuration
  - SAUCE: cxlflash: Setup function acTag range
  - SAUCE: cxlflash: Read host AFU configuration
  - SAUCE: cxlflash: Setup AFU acTag range
  - SAUCE: cxlflash: Setup AFU PASID
  - SAUCE: cxlflash: Adapter context support for OCXL
  - SAUCE: cxlflash: Use IDR to manage adapter contexts
  - SAUCE: cxlflash: Support adapter file descriptors for OCXL
  - SAUCE: cxlflash: Support adapter context discovery
  - SAUCE: cxlflash: Support image reload policy modification
  - SAUCE: cxlflash: MMIO map the AFU
  - SAUCE: cxlflash: Support starting an adapter context
  - SAUCE: cxlflash: Support process specific mappings
  - SAUCE: cxlflash: Support AFU state toggling
  - SAUCE: cxlflash: Support reading adapter VPD data
  - SAUCE: cxlflash: Setup function OCXL link
  - SAUCE: cxlflash: Setup OCXL transaction layer
  - SAUCE: cxlflash: Support process element lifecycle
  - SAUCE: cxlflash: Support AFU interrupt management
  - SAUCE: cxlflash: Support AFU interrupt mapping and registration
  - SAUCE: cxlflash: Support starting user contexts
  - SAUCE: cxlflash: Support adapter context polling
  - SAUCE: cxlflash: Support adapter context reading
  - SAUCE: cxlflash: Support adapter context mmap and release
  - SAUCE: cxlflash: Support file descriptor mapping
  - SAUCE: cxlflash: Introduce object handle fop
  - SAUCE: cxlflash: Setup LISNs for user contexts
  - SAUCE: cxlflash: Setup LISNs for master contexts
  - SAUCE: cxlflash: Update synchronous interrupt status bits
  - SAUCE: cxlflash: Introduce OCXL context state machine
  - SAUCE: cxlflash: Register for translation errors
  - SAUCE: cxlflash: Support AFU reset
  - SAUCE: cxlflash: Enable OCXL operations

  Also, there are 3 additional patches added to end of this series that we 
would like to request being pulled into the SRU stream. These 3 patches address 
bug fixes.
  The commit ids for the patches queued in next/master tree are,

  768999d6b1eadc6a13b1fba1886f1708f433d82b scsi: cxlflash: Preserve number of 
interrupts for master contexts
  6c2b116dd38e3fbda10c3e3d5ac80ea7442e4f4d scsi: cxlflash: Avoid clobbering 
context control register value
  fcace1d5e11f518c6f91dd245fa1ac37393b47d3 scsi: cxlflash: Add argument 
identifier names
  863dbdc0552f8bc100df48bb231089c382b89004 scsi: cxlflash: Introduce OCXL 
backend
  f2180daa83950ff8183f70b1b78d67cb13fd90b2 scsi: cxlflash: Hardware AFU for OCXL
  1042535633554592d7d95a9cf83d2940803689e0 scsi: cxlflash: Read host function 
configuration
  ba84823a8b448207659753ae4f9c8b956923bada scsi: cxlflash: Setup function acTag 
range
  f55ced2dcd00ab257a2bb25eee619b75cda24817 scsi: cxlflash: Read host AFU 
configuration
  c5a8fec11278e245136c7f696c914269c58a6000 scsi: cxlflash: Setup AFU acTag range
  b42d68d728a63337bcb7860b59e6458946d94a84 scsi: cxlflash: Setup AFU PASID
  de25ec59a75802584aac97aed05fd94094dbbb58 scsi: cxlflash: Adapter context 
support for OCXL
  a76fc993e399f54b37f46107a31e817c779f2b82 scsi: cxlflash: Use IDR to manage 
adapter contexts
  09f35da5fe218baf73f7b4efd281e2c19490512c scsi: cxlflash: Support adapter file 
descriptors for OCXL
  17f9335bc59c1cf8f93617eee137e745abd71a3f scsi: cxlflash: Support adapter 
context discovery
  a5cfe355f23d4410d69af0e5b196b095463a0b4b scsi: cxlflash: Support image reload 
policy modification
  0c62e7c091a4e0a01a7c6027fe719625ab2f521e scsi: cxlflash: MMIO map the AFU

[Kernel-packages] [Bug 1768005] Re: bluetooth

2018-05-23 Thread Christopher M. Penalver

** Summary changed:

- bluethoot
+ bluetooth

** Package changed: xorg (Ubuntu) => bluez (Ubuntu)

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

Title:
  bluetooth

Status in bluez package in Ubuntu:
  New

Bug description:
  I can't find my bluetooth phone on my camputer and also the camputer
  didn't appair oon it

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-40.45~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-40-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Apr 30 13:42:22 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:80df]
  InstallationDate: Installed on 2018-04-12 (17 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: HP HP ENVY Notebook
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-40-generic.efi.signed 
root=UUID=13a48f70-07e8-4e27-8c9c-40d77359e72d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/18/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.34
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80DF
  dmi.board.vendor: HP
  dmi.board.version: 87.59
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.34:bd02/18/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80DF:rvr87.59:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Apr 30 13:38:43 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

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

apport information

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

Title:
  Touchpad slows down and then stops working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Cannot find a reason, but sometimes once a day, sometimes twice a day,
  my touchpad starts to work slowly, like jumping, and after a few
  seconds, it completely stops working. At some point, I did something
  with Terminal and it started working, but cannot reproduce it. The
  only thing that seems to be really working is to Suspend laptop and
  come back in Ubuntu (or restart, but that means to close everything +
  it takes more time). While I wrote this text, it seems to have
  recovered by itself, it is working right now, but this is unreliable
  and cannot be used in production (what about stopping it during a
  presentation, cannot suspend in a meeting). Hopefully, it is some
  kernel problem, as I reported kernel package.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 01:15:44 2018
  InstallationDate: Installed on 2018-04-27 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   florin 2029 F...m pulseaudio
   /dev/snd/controlC0:  florin 2029 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=99eb1e80-1ec0-4526-8cff-0691084ec0f8
  InstallationDate: Installed on 2018-04-27 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:5652 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA SATELLITE P50-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=470c0ce8-f352-4f58-977c-af6d3998d302 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2017
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.50
  dmi.board.name: 06F4
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/05/2017:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUFE-001009G6:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE P50-C
  dmi.product.version: PSPUFE-001009G6
  dmi.sys.vendor: TOSHIBA

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

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

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

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1772760/+attachment/5143425/+files/ProcEnviron.txt

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

Title:
  Touchpad slows down and then stops working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Cannot find a reason, but sometimes once a day, sometimes twice a day,
  my touchpad starts to work slowly, like jumping, and after a few
  seconds, it completely stops working. At some point, I did something
  with Terminal and it started working, but cannot reproduce it. The
  only thing that seems to be really working is to Suspend laptop and
  come back in Ubuntu (or restart, but that means to close everything +
  it takes more time). While I wrote this text, it seems to have
  recovered by itself, it is working right now, but this is unreliable
  and cannot be used in production (what about stopping it during a
  presentation, cannot suspend in a meeting). Hopefully, it is some
  kernel problem, as I reported kernel package.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 01:15:44 2018
  InstallationDate: Installed on 2018-04-27 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   florin 2029 F...m pulseaudio
   /dev/snd/controlC0:  florin 2029 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=99eb1e80-1ec0-4526-8cff-0691084ec0f8
  InstallationDate: Installed on 2018-04-27 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:5652 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA SATELLITE P50-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=470c0ce8-f352-4f58-977c-af6d3998d302 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2017
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.50
  dmi.board.name: 06F4
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/05/2017:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUFE-001009G6:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE P50-C
  dmi.product.version: PSPUFE-001009G6
  dmi.sys.vendor: TOSHIBA

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

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

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

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1772760/+attachment/5143431/+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/1772760

Title:
  Touchpad slows down and then stops working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Cannot find a reason, but sometimes once a day, sometimes twice a day,
  my touchpad starts to work slowly, like jumping, and after a few
  seconds, it completely stops working. At some point, I did something
  with Terminal and it started working, but cannot reproduce it. The
  only thing that seems to be really working is to Suspend laptop and
  come back in Ubuntu (or restart, but that means to close everything +
  it takes more time). While I wrote this text, it seems to have
  recovered by itself, it is working right now, but this is unreliable
  and cannot be used in production (what about stopping it during a
  presentation, cannot suspend in a meeting). Hopefully, it is some
  kernel problem, as I reported kernel package.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 01:15:44 2018
  InstallationDate: Installed on 2018-04-27 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   florin 2029 F...m pulseaudio
   /dev/snd/controlC0:  florin 2029 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=99eb1e80-1ec0-4526-8cff-0691084ec0f8
  InstallationDate: Installed on 2018-04-27 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:5652 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA SATELLITE P50-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=470c0ce8-f352-4f58-977c-af6d3998d302 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2017
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.50
  dmi.board.name: 06F4
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/05/2017:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUFE-001009G6:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE P50-C
  dmi.product.version: PSPUFE-001009G6
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1773001] Re: [18.04] [regression testing] ubuntu_bpf_jit test failing on amd64

I was looking at an old kernel version. This test is no longer failing
in 4.15.0-21.22. Closing as INVALID.

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

Title:
   [18.04] [regression testing] ubuntu_bpf_jit test failing on amd64

Status in linux package in Ubuntu:
  Invalid

Bug description:
  See for example: http://10.246.72.4/test-
  results/4.15.0-7.8-generic/ubuntu_bpf_jit-4.15.0-7.8-amd64-index.html

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

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

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

apport information

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

Title:
  Touchpad slows down and then stops working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Cannot find a reason, but sometimes once a day, sometimes twice a day,
  my touchpad starts to work slowly, like jumping, and after a few
  seconds, it completely stops working. At some point, I did something
  with Terminal and it started working, but cannot reproduce it. The
  only thing that seems to be really working is to Suspend laptop and
  come back in Ubuntu (or restart, but that means to close everything +
  it takes more time). While I wrote this text, it seems to have
  recovered by itself, it is working right now, but this is unreliable
  and cannot be used in production (what about stopping it during a
  presentation, cannot suspend in a meeting). Hopefully, it is some
  kernel problem, as I reported kernel package.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 01:15:44 2018
  InstallationDate: Installed on 2018-04-27 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   florin 2029 F...m pulseaudio
   /dev/snd/controlC0:  florin 2029 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=99eb1e80-1ec0-4526-8cff-0691084ec0f8
  InstallationDate: Installed on 2018-04-27 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:5652 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA SATELLITE P50-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=470c0ce8-f352-4f58-977c-af6d3998d302 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2017
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.50
  dmi.board.name: 06F4
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/05/2017:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUFE-001009G6:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE P50-C
  dmi.product.version: PSPUFE-001009G6
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1772760] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1772760/+attachment/5143421/+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/1772760

Title:
  Touchpad slows down and then stops working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Cannot find a reason, but sometimes once a day, sometimes twice a day,
  my touchpad starts to work slowly, like jumping, and after a few
  seconds, it completely stops working. At some point, I did something
  with Terminal and it started working, but cannot reproduce it. The
  only thing that seems to be really working is to Suspend laptop and
  come back in Ubuntu (or restart, but that means to close everything +
  it takes more time). While I wrote this text, it seems to have
  recovered by itself, it is working right now, but this is unreliable
  and cannot be used in production (what about stopping it during a
  presentation, cannot suspend in a meeting). Hopefully, it is some
  kernel problem, as I reported kernel package.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 01:15:44 2018
  InstallationDate: Installed on 2018-04-27 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   florin 2029 F...m pulseaudio
   /dev/snd/controlC0:  florin 2029 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=99eb1e80-1ec0-4526-8cff-0691084ec0f8
  InstallationDate: Installed on 2018-04-27 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:5652 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA SATELLITE P50-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=470c0ce8-f352-4f58-977c-af6d3998d302 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2017
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.50
  dmi.board.name: 06F4
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/05/2017:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUFE-001009G6:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE P50-C
  dmi.product.version: PSPUFE-001009G6
  dmi.sys.vendor: TOSHIBA

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

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

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

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

apport-collect 1773001

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

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

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

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

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

Title:
   [18.04] [regression testing] ubuntu_bpf_jit test failing on amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  See for example: http://10.246.72.4/test-
  results/4.15.0-7.8-generic/ubuntu_bpf_jit-4.15.0-7.8-amd64-index.html

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

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

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

apport information

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

Title:
  Touchpad slows down and then stops working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Cannot find a reason, but sometimes once a day, sometimes twice a day,
  my touchpad starts to work slowly, like jumping, and after a few
  seconds, it completely stops working. At some point, I did something
  with Terminal and it started working, but cannot reproduce it. The
  only thing that seems to be really working is to Suspend laptop and
  come back in Ubuntu (or restart, but that means to close everything +
  it takes more time). While I wrote this text, it seems to have
  recovered by itself, it is working right now, but this is unreliable
  and cannot be used in production (what about stopping it during a
  presentation, cannot suspend in a meeting). Hopefully, it is some
  kernel problem, as I reported kernel package.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 01:15:44 2018
  InstallationDate: Installed on 2018-04-27 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   florin 2029 F...m pulseaudio
   /dev/snd/controlC0:  florin 2029 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=99eb1e80-1ec0-4526-8cff-0691084ec0f8
  InstallationDate: Installed on 2018-04-27 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:5652 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA SATELLITE P50-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=470c0ce8-f352-4f58-977c-af6d3998d302 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2017
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.50
  dmi.board.name: 06F4
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/05/2017:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUFE-001009G6:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE P50-C
  dmi.product.version: PSPUFE-001009G6
  dmi.sys.vendor: TOSHIBA

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

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

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

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

apport-collect 1773000

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

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

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

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

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

Title:
  [18.04] [regression testing] ubuntu_bpf tests failing on amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For example:  http://10.246.72.4/test-
  results/4.15.0-21.22-generic/ubuntu_bpf-4.15.0-21.22-amd64-index.html

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

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

[Kernel-packages] [Bug 1772760] Re: Touchpad slows down and then stops working

apport information

** Tags added: apport-collected

** Description changed:

  Cannot find a reason, but sometimes once a day, sometimes twice a day,
  my touchpad starts to work slowly, like jumping, and after a few
  seconds, it completely stops working. At some point, I did something
  with Terminal and it started working, but cannot reproduce it. The only
  thing that seems to be really working is to Suspend laptop and come back
  in Ubuntu (or restart, but that means to close everything + it takes
  more time). While I wrote this text, it seems to have recovered by
  itself, it is working right now, but this is unreliable and cannot be
  used in production (what about stopping it during a presentation, cannot
  suspend in a meeting). Hopefully, it is some kernel problem, as I
  reported kernel package.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 01:15:44 2018
  InstallationDate: Installed on 2018-04-27 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ApportVersion: 2.20.9-0ubuntu7
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC0D0p:   florin 2029 F...m pulseaudio
+  /dev/snd/controlC0:  florin 2029 F pulseaudio
+ CurrentDesktop: communitheme:ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ HibernationDevice: RESUME=UUID=99eb1e80-1ec0-4526-8cff-0691084ec0f8
+ InstallationDate: Installed on 2018-04-27 (26 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 002: ID 13d3:5652 IMC Networks 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: TOSHIBA SATELLITE P50-C
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=470c0ce8-f352-4f58-977c-af6d3998d302 ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-22-generic N/A
+  linux-backports-modules-4.15.0-22-generic  N/A
+  linux-firmware 1.173
+ Tags:  bionic
+ Uname: Linux 4.15.0-22-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 07/05/2017
+ dmi.bios.vendor: INSYDE Corp.
+ dmi.bios.version: 1.50
+ dmi.board.name: 06F4
+ dmi.board.vendor: FF50
+ dmi.board.version: Type2 - Board Version
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: OEM Chassis ManuFacturer
+ dmi.chassis.version: OEM Chassis Version
+ dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/05/2017:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUFE-001009G6:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
+ dmi.product.family: Type1Family
+ dmi.product.name: SATELLITE P50-C
+ dmi.product.version: PSPUFE-001009G6
+ dmi.sys.vendor: TOSHIBA

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

Title:
  Touchpad slows down and then stops working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Cannot find a reason, but sometimes once a day, sometimes twice a day,
  my touchpad starts to work slowly, like jumping, and after a few
  seconds, it completely stops working. At some point, I did something
  with Terminal and it started working, but cannot reproduce it. The
  only thing that seems to be really working is to Suspend laptop and
  come back in Ubuntu (or restart, but that means to close everything +
  it takes more time). While I wrote this text, it seems to have
  recovered by itself, it is working right now, but this is unreliable
  and cannot be used in production (what about stopping it during a
  presentation, cannot suspend in a meeting). Hopefully, it is some
  kernel problem, as I reported kernel package.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 01:15:44 2018
  InstallationDate: Installed on 2018-04-27 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed

[Kernel-packages] [Bug 1773001] [NEW] [18.04] [regression testing] ubuntu_bpf_jit test failing on amd64

Public bug reported:

See for example: http://10.246.72.4/test-
results/4.15.0-7.8-generic/ubuntu_bpf_jit-4.15.0-7.8-amd64-index.html

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


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

Title:
   [18.04] [regression testing] ubuntu_bpf_jit test failing on amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  See for example: http://10.246.72.4/test-
  results/4.15.0-7.8-generic/ubuntu_bpf_jit-4.15.0-7.8-amd64-index.html

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

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

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

apport information

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

Title:
  Touchpad slows down and then stops working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Cannot find a reason, but sometimes once a day, sometimes twice a day,
  my touchpad starts to work slowly, like jumping, and after a few
  seconds, it completely stops working. At some point, I did something
  with Terminal and it started working, but cannot reproduce it. The
  only thing that seems to be really working is to Suspend laptop and
  come back in Ubuntu (or restart, but that means to close everything +
  it takes more time). While I wrote this text, it seems to have
  recovered by itself, it is working right now, but this is unreliable
  and cannot be used in production (what about stopping it during a
  presentation, cannot suspend in a meeting). Hopefully, it is some
  kernel problem, as I reported kernel package.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 01:15:44 2018
  InstallationDate: Installed on 2018-04-27 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   florin 2029 F...m pulseaudio
   /dev/snd/controlC0:  florin 2029 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=99eb1e80-1ec0-4526-8cff-0691084ec0f8
  InstallationDate: Installed on 2018-04-27 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:5652 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA SATELLITE P50-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=470c0ce8-f352-4f58-977c-af6d3998d302 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2017
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.50
  dmi.board.name: 06F4
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/05/2017:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUFE-001009G6:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE P50-C
  dmi.product.version: PSPUFE-001009G6
  dmi.sys.vendor: TOSHIBA

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

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

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

apport information

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

Title:
  Touchpad slows down and then stops working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Cannot find a reason, but sometimes once a day, sometimes twice a day,
  my touchpad starts to work slowly, like jumping, and after a few
  seconds, it completely stops working. At some point, I did something
  with Terminal and it started working, but cannot reproduce it. The
  only thing that seems to be really working is to Suspend laptop and
  come back in Ubuntu (or restart, but that means to close everything +
  it takes more time). While I wrote this text, it seems to have
  recovered by itself, it is working right now, but this is unreliable
  and cannot be used in production (what about stopping it during a
  presentation, cannot suspend in a meeting). Hopefully, it is some
  kernel problem, as I reported kernel package.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 01:15:44 2018
  InstallationDate: Installed on 2018-04-27 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   florin 2029 F...m pulseaudio
   /dev/snd/controlC0:  florin 2029 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=99eb1e80-1ec0-4526-8cff-0691084ec0f8
  InstallationDate: Installed on 2018-04-27 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:5652 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA SATELLITE P50-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=470c0ce8-f352-4f58-977c-af6d3998d302 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2017
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.50
  dmi.board.name: 06F4
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/05/2017:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUFE-001009G6:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE P50-C
  dmi.product.version: PSPUFE-001009G6
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1773005] [NEW] [18.04] [regression testing] ubuntu_lxc tests failing on amd64

Public bug reported:

See for example: http://10.246.72.4/test-
results/4.15.0-21.22-generic/ubuntu_lxc-4.15.0-21.22-amd64-index.html

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


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

Title:
   [18.04] [regression testing] ubuntu_lxc tests failing on amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  See for example: http://10.246.72.4/test-
  results/4.15.0-21.22-generic/ubuntu_lxc-4.15.0-21.22-amd64-index.html

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

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

[Kernel-packages] [Bug 1772024] Re: linux 4.13.0-42.47 ADT test failure with linux 4.13.0-42.47 (nbd-smoke-test)

2018-05-23 Thread Thadeu Lima de Souza Cascardo

** Also affects: nbd (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Also affects: nbd (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

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

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

** Also affects: nbd (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

** Also affects: nbd (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: nbd (Ubuntu Cosmic)
Milestone: None => ubuntu-18.06

** Changed in: nbd (Ubuntu Cosmic)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

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

Title:
  linux 4.13.0-42.47 ADT test failure with linux 4.13.0-42.47 (nbd-
  smoke-test)

Status in linux package in Ubuntu:
  In Progress
Status in nbd package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  New
Status in nbd source package in Trusty:
  New
Status in linux source package in Xenial:
  New
Status in nbd source package in Xenial:
  New
Status in linux source package in Artful:
  New
Status in nbd source package in Artful:
  New
Status in linux source package in Bionic:
  New
Status in nbd source package in Bionic:
  New
Status in linux source package in Cosmic:
  In Progress
Status in nbd source package in Cosmic:
  In Progress

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/l/linux/20180518_040741_b3b54@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/i386/l/linux/20180518_050911_b3b54@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/l/linux/20180518_040734_b3b54@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/s390x/l/linux/20180518_035527_b3b54@/log.gz

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

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

[Kernel-packages] [Bug 1773002] Re: [18.04] [regression testing] libhugetlbfs tests failing on amd64

** Description changed:

  See for example: http://10.246.72.4/test-
- results/4.15.0-5.6-generic/libhugetlbfs-4.15.0-5.6-amd64-index.html
+ results/4.15.0-21.22-generic/libhugetlbfs-4.15.0-21.22-amd64-index.html

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

Title:
   [18.04] [regression testing] libhugetlbfs tests failing on amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  See for example: http://10.246.72.4/test-
  results/4.15.0-21.22-generic/libhugetlbfs-4.15.0-21.22-amd64-index.html

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

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

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

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1772760/+attachment/5143427/+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/1772760

Title:
  Touchpad slows down and then stops working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Cannot find a reason, but sometimes once a day, sometimes twice a day,
  my touchpad starts to work slowly, like jumping, and after a few
  seconds, it completely stops working. At some point, I did something
  with Terminal and it started working, but cannot reproduce it. The
  only thing that seems to be really working is to Suspend laptop and
  come back in Ubuntu (or restart, but that means to close everything +
  it takes more time). While I wrote this text, it seems to have
  recovered by itself, it is working right now, but this is unreliable
  and cannot be used in production (what about stopping it during a
  presentation, cannot suspend in a meeting). Hopefully, it is some
  kernel problem, as I reported kernel package.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 01:15:44 2018
  InstallationDate: Installed on 2018-04-27 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   florin 2029 F...m pulseaudio
   /dev/snd/controlC0:  florin 2029 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=99eb1e80-1ec0-4526-8cff-0691084ec0f8
  InstallationDate: Installed on 2018-04-27 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:5652 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA SATELLITE P50-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=470c0ce8-f352-4f58-977c-af6d3998d302 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2017
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.50
  dmi.board.name: 06F4
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/05/2017:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUFE-001009G6:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE P50-C
  dmi.product.version: PSPUFE-001009G6
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1773000] Re: [18.04] [regression testing] ubuntu_bpf tests failing on amd64

** Description changed:

  For example:  http://10.246.72.4/test-
- results/4.15.0-7.8-generic/ubuntu_bpf-4.15.0-7.8-amd64-index.html
+ results/4.15.0-21.22-generic/ubuntu_bpf-4.15.0-21.22-amd64-index.html

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

Title:
  [18.04] [regression testing] ubuntu_bpf tests failing on amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For example:  http://10.246.72.4/test-
  results/4.15.0-21.22-generic/ubuntu_bpf-4.15.0-21.22-amd64-index.html

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

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

[Kernel-packages] [Bug 1773010] [NEW] [18.04] [regression testing] ubuntu_kvm_unit_tests tests failing on amd64

Public bug reported:

See for example: http://10.246.72.4/test-
results/4.15.0-21.22-generic/ubuntu_kvm_unit_tests-4.15.0-21.22-amd64-index.html

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


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

Title:
   [18.04] [regression testing] ubuntu_kvm_unit_tests tests failing on
  amd64

Status in linux package in Ubuntu:
  New

Bug description:
  See for example: http://10.246.72.4/test-
  
results/4.15.0-21.22-generic/ubuntu_kvm_unit_tests-4.15.0-21.22-amd64-index.html

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

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

[Kernel-packages] [Bug 1772775] Re: 4.4.0-127.153 generates many "sit: non-ECT" messages

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

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

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

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

Title:
  4.4.0-127.153 generates many "sit: non-ECT" messages

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

Bug description:
  Since deploying linux-image-4.4.0-127-generic (4.4.0-127.153) on a
  Xenial VM with a sit tunnel, I get such messages:

  May 22 10:49:38 gw kernel: [   68.121601] sit: non-ECT from 0.0.0.0
  with TOS=0x5

  Those are logged quite often:

  # grep -cF 'sit: non-ECT' /var/log/syslog
  9108

  Reverting to linux-image-4.4.0-124-generic (4.4.0-124.148) fixes the
  issue.

  # lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04
  # apt-cache policy linux-image-4.4.0-127-generic
  linux-image-4.4.0-127-generic:
Installed: 4.4.0-127.153
Candidate: 4.4.0-127.153
Version table:
   *** 4.4.0-127.153 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-127-generic 4.4.0-127.153
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 20:08 seq
   crw-rw 1 root audio 116, 33 May 22 20:08 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  Date: Tue May 22 21:18:45 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic 
root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro console=ttyS0 net.ifnames=0 
kaslr vsyscall=none nmi_watchdog=0 possible_cpus=1 pti=on nr_cpus=1
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-127-generic N/A
   linux-backports-modules-4.4.0-127-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.5
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.5
  dmi.sys.vendor: QEMU
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 21:33 seq
   crw-rw 1 root audio 116, 33 May 22 21:33 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro kaslr net.ifnames=0 
nmi_watchdog=0 nr_cpus=1 pti=on console=ttyS0 vsyscall=none
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-124-generic N/A
   linux-backports-modules-4.4.0-124-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-124-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version:

[Kernel-packages] [Bug 1773000] [NEW] [18.04] [regression testing] ubuntu_bpf tests failing on amd64

Public bug reported:

For example:  http://10.246.72.4/test-
results/4.15.0-7.8-generic/ubuntu_bpf-4.15.0-7.8-amd64-index.html

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


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

Title:
  [18.04] [regression testing] ubuntu_bpf tests failing on amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For example:  http://10.246.72.4/test-
  results/4.15.0-7.8-generic/ubuntu_bpf-4.15.0-7.8-amd64-index.html

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

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

[Kernel-packages] [Bug 1773002] [NEW] [18.04] [regression testing] libhugetlbfs tests failing on amd64

Public bug reported:

See for example: http://10.246.72.4/test-
results/4.15.0-5.6-generic/libhugetlbfs-4.15.0-5.6-amd64-index.html

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


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

Title:
   [18.04] [regression testing] libhugetlbfs tests failing on amd64

Status in linux package in Ubuntu:
  New

Bug description:
  See for example: http://10.246.72.4/test-
  results/4.15.0-5.6-generic/libhugetlbfs-4.15.0-5.6-amd64-index.html

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

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

[Kernel-packages] [Bug 1770916] Re: package crda 3.18-1build1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.2

2018-05-23 Thread Martina Neumayer

Confirmed. Affects also Mint Mate 18.3 x64.

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

Title:
  package crda 3.18-1build1 failed to install/upgrade: trying to
  overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in
  package wireless-regdb 2015.07.20-1ubuntu1

Status in crda package in Ubuntu:
  Confirmed

Bug description:
  On upgrading 16.04 - >18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: crda 3.18-1build1
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  AptOrdering:
   crda:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May 12 13:51:43 2018
  DpkgTerminalLog:
   Preparing to unpack .../crda_3.18-1build1_amd64.deb ...
   Unpacking crda (3.18-1build1) over (3.13-1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/crda_3.18-1build1_amd64.deb (--unpack):
trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also 
in package wireless-regdb 2015.07.20-1ubuntu1
  DuplicateSignature:
   package:crda:3.18-1build1
   Unpacking crda (3.18-1build1) over (3.13-1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/crda_3.18-1build1_amd64.deb (--unpack):
trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also 
in package wireless-regdb 2015.07.20-1ubuntu1
  ErrorMessage: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', 
which is also in package wireless-regdb 2015.07.20-1ubuntu1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: crda
  Title: package crda 3.18-1build1 failed to install/upgrade: trying to 
overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package 
wireless-regdb 2015.07.20-1ubuntu1
  UpgradeStatus: Upgraded to bionic on 2018-05-12 (0 days ago)

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

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

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

2018-05-23 Thread bugproxy

--- Comment From ukri...@us.ibm.com 2018-05-23 17:21 EDT---
I'm getting errors while installing the given packages. Do I need to upgrade my 
box with a specific release ? Please let me know.

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

Title:
  Request to revert SAUCE patches in the 18.04 SRU and update with
  upstream version

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

Bug description:
  == Comment: #0 - UMA KRISHNAN  - 2018-04-30 14:41:30 ==
  ---Problem Description---
  Request to revert SAUCE patches from 18.04 and apply the patches from 
next/master.

  Below set of cxlflash patches were submitted to Canonical after they
  were sent to the community. Based on review comments, there has been
  minor changes from that version. This BZ is to request reverting those
  SAUCE patches with the ones that are queued in next/master tree for
  4.18.

  - SAUCE: cxlflash: Preserve number of interrupts for master contexts
  - SAUCE: cxlflash: Avoid clobbering context control register value
  - SAUCE: cxlflash: Add argument identifier names
  - SAUCE: cxlflash: Introduce OCXL backend
  - SAUCE: cxlflash: Hardware AFU for OCXL
  - SAUCE: cxlflash: Read host function configuration
  - SAUCE: cxlflash: Setup function acTag range
  - SAUCE: cxlflash: Read host AFU configuration
  - SAUCE: cxlflash: Setup AFU acTag range
  - SAUCE: cxlflash: Setup AFU PASID
  - SAUCE: cxlflash: Adapter context support for OCXL
  - SAUCE: cxlflash: Use IDR to manage adapter contexts
  - SAUCE: cxlflash: Support adapter file descriptors for OCXL
  - SAUCE: cxlflash: Support adapter context discovery
  - SAUCE: cxlflash: Support image reload policy modification
  - SAUCE: cxlflash: MMIO map the AFU
  - SAUCE: cxlflash: Support starting an adapter context
  - SAUCE: cxlflash: Support process specific mappings
  - SAUCE: cxlflash: Support AFU state toggling
  - SAUCE: cxlflash: Support reading adapter VPD data
  - SAUCE: cxlflash: Setup function OCXL link
  - SAUCE: cxlflash: Setup OCXL transaction layer
  - SAUCE: cxlflash: Support process element lifecycle
  - SAUCE: cxlflash: Support AFU interrupt management
  - SAUCE: cxlflash: Support AFU interrupt mapping and registration
  - SAUCE: cxlflash: Support starting user contexts
  - SAUCE: cxlflash: Support adapter context polling
  - SAUCE: cxlflash: Support adapter context reading
  - SAUCE: cxlflash: Support adapter context mmap and release
  - SAUCE: cxlflash: Support file descriptor mapping
  - SAUCE: cxlflash: Introduce object handle fop
  - SAUCE: cxlflash: Setup LISNs for user contexts
  - SAUCE: cxlflash: Setup LISNs for master contexts
  - SAUCE: cxlflash: Update synchronous interrupt status bits
  - SAUCE: cxlflash: Introduce OCXL context state machine
  - SAUCE: cxlflash: Register for translation errors
  - SAUCE: cxlflash: Support AFU reset
  - SAUCE: cxlflash: Enable OCXL operations

  Also, there are 3 additional patches added to end of this series that we 
would like to request being pulled into the SRU stream. These 3 patches address 
bug fixes.
  The commit ids for the patches queued in next/master tree are,

  768999d6b1eadc6a13b1fba1886f1708f433d82b scsi: cxlflash: Preserve number of 
interrupts for master contexts
  6c2b116dd38e3fbda10c3e3d5ac80ea7442e4f4d scsi: cxlflash: Avoid clobbering 
context control register value
  fcace1d5e11f518c6f91dd245fa1ac37393b47d3 scsi: cxlflash: Add argument 
identifier names
  863dbdc0552f8bc100df48bb231089c382b89004 scsi: cxlflash: Introduce OCXL 
backend
  f2180daa83950ff8183f70b1b78d67cb13fd90b2 scsi: cxlflash: Hardware AFU for OCXL
  1042535633554592d7d95a9cf83d2940803689e0 scsi: cxlflash: Read host function 
configuration
  ba84823a8b448207659753ae4f9c8b956923bada scsi: cxlflash: Setup function acTag 
range
  f55ced2dcd00ab257a2bb25eee619b75cda24817 scsi: cxlflash: Read host AFU 
configuration
  c5a8fec11278e245136c7f696c914269c58a6000 scsi: cxlflash: Setup AFU acTag range
  b42d68d728a63337bcb7860b59e6458946d94a84 scsi: cxlflash: Setup AFU PASID
  de25ec59a75802584aac97aed05fd94094dbbb58 scsi: cxlflash: Adapter context 
support for OCXL
  a76fc993e399f54b37f46107a31e817c779f2b82 scsi: cxlflash: Use IDR to manage 
adapter contexts
  09f35da5fe218baf73f7b4efd281e2c19490512c scsi: cxlflash: Support adapter file 
descriptors for OCXL
  17f9335bc59c1cf8f93617eee137e745abd71a3f scsi: cxlflash: Support adapter 
context discovery
  a5cfe355f23d4410d69af0e5b196b095463a0b4b scsi: cxlflash: Support image reload 
policy modification
  0c62e7c091a4e0a01a7c6027fe719625ab2f521e scsi: cxlflash: MMIO map the AFU
  f39bab766ea4f0b3d5888fdd7d66babd7bef3966 scsi: cxlflash: Support starting an 
adapter context
  bef2014e8bd6391988b588acb969b48133072f17 scsi: cxlflash: Support process

[Kernel-packages] [Bug 1772024] Re: linux 4.13.0-42.47 ADT test failure with linux 4.13.0-42.47 (nbd-smoke-test)

2018-05-23 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  linux 4.13.0-42.47 ADT test failure with linux 4.13.0-42.47 (nbd-
  smoke-test)

Status in linux package in Ubuntu:
  In Progress
Status in nbd package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  New
Status in nbd source package in Trusty:
  New
Status in linux source package in Xenial:
  New
Status in nbd source package in Xenial:
  New
Status in linux source package in Artful:
  New
Status in nbd source package in Artful:
  New
Status in linux source package in Bionic:
  New
Status in nbd source package in Bionic:
  New
Status in linux source package in Cosmic:
  In Progress
Status in nbd source package in Cosmic:
  In Progress

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/l/linux/20180518_040741_b3b54@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/i386/l/linux/20180518_050911_b3b54@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/l/linux/20180518_040734_b3b54@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/s390x/l/linux/20180518_035527_b3b54@/log.gz

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

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

[Kernel-packages] [Bug 1768005] [NEW] bluetooth

You have been subscribed to a public bug:

I can't find my bluetooth phone on my camputer and also the camputer
didn't appair oon it

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-40.45~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-40-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Apr 30 13:42:22 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:80df]
InstallationDate: Installed on 2018-04-12 (17 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
MachineType: HP HP ENVY Notebook
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-40-generic.efi.signed 
root=UUID=13a48f70-07e8-4e27-8c9c-40d77359e72d ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/18/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.34
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 80DF
dmi.board.vendor: HP
dmi.board.version: 87.59
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.34:bd02/18/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80DF:rvr87.59:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
dmi.product.name: HP ENVY Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Mon Apr 30 13:38:43 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial
-- 
bluetooth
https://bugs.launchpad.net/bugs/1768005
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to bluez in Ubuntu.

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

[Kernel-packages] [Bug 1773024] [NEW] Errors at boot

2018-05-23 Thread Thibault

Public bug reported:

LOGS DMESG:

[0.048089] ACPI: Added _OSI(Module Device)
[0.048090] ACPI: Added _OSI(Processor Device)
[0.048091] ACPI: Added _OSI(3.0 _SCP Extensions)
[0.048091] ACPI: Added _OSI(Processor Aggregator Device)
[0.049587] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
[0.049598] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
[0.049607] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
[0.049615] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
[0.049676] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
[0.049684] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
[0.049692] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
[0.049700] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
[0.049760] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
[0.049768] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
[0.049776] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
[0.049783] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
[0.049843] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
[0.049851] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
[0.049859] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
[0.049867] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
[0.049925] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
[0.049933] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
[0.049941] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
[0.049948] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
[0.050008] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
[0.050016] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
[0.050024] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
[0.050032] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
[0.050091] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
[0.050099] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
[0.050107] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
[0.050115] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
[0.050173] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
[0.050181] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
[0.050190] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
[0.050198] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
[0.050258] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
[0.050267] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
[0.050274] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
[0.050282] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
[0.050342] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
[0.050350] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
[0.050357] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
[0.050365] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
[0.054169] ACPI: Interpreter enabled
[0.054188] ACPI: (supports S0 S3 S4 S5)
[0.054189] ACPI: Using IOAPIC for interrupt routing
[0.054269] PCI: Using host bridge windows from ACPI; if necessary, use 
"pci=nocrs" and report a bug
[0.054425] ACPI: Enabled 5 GPEs in block 00 to 1F
[0.057299] ACPI: PCI Root Bridge [PCI0] (domain  [bus 00-ff])
[0.057304] acpi PNP0A03:00: _OSC: OS supports

[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake

2018-05-23 Thread Hans de Goede

Olivier, thank you excellent work. I've mailed the upstream developers
and the author of the patch of which the older version fixes things.

Kai-Heng, can you perhaps do a test Ubuntu kernel build with the patch
from comment 158, then other users with different (but similar) model
laptops can test and hopefully confirm that this fixes things for them
too.  Note I don't believe that this is the proper fix, but it will be
good to have confirmation that this fixes things for others too.

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

Title:
  Touchpad stops working after reboot on Apollo Lake

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

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

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

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

[Kernel-packages] [Bug 1483416] [NEW] laptop keybord light (more\less) shortcuts don't work

You have been subscribed to a public bug:

Samsug Series7 laptop NP730UE-S01PL keybord light (more\less) shortcuts
fn+F10\F11 don't work

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: compiz-core 1:0.9.12.1+15.10.20150627.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.18-0ubuntu5
Architecture: amd64
CasperVersion: 1.362
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Aug 10 21:22:58 2015
DistUpgraded: Fresh install
DistroCodename: wily
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd Device [144d:c0e8]
LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150808)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 730U3E/740U3E
ProcEnviron:
 PATH=(custom, no user)
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
SourcePackage: compiz
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/26/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P07ABW.065.140226.dg
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP730U3E-S01PL
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SEC_SW_REVISION_1234567890ABCD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP07ABW.065.140226.dg:bd02/26/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn730U3E/740U3E:pvrP07ABW:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP730U3E-S01PL:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: 730U3E/740U3E
dmi.product.version: P07ABW
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz 1:0.9.12.1+15.10.20150627.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.62-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Mon Aug 10 21:05:18 2015
xserver.configfile: default
xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id4931 
 vendor CMN
xserver.version: 2:1.17.2-1ubuntu3

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu wily
-- 
laptop keybord light (more\less) shortcuts don't work
https://bugs.launchpad.net/bugs/1483416
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1768526] Re: Include nfp driver in linux-modules

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

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

Title:
  Include nfp driver in linux-modules

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  SRU Justification:
  --

  [Impact]

   * Currently the driver for Netronome Agilio SmartNICs, nfp.ko, is included 
in linux-moudles-extra.
     An implication of this is that on minimal installs, where the 
linux-modules but not linux-modules-extra
     packages are available, the nfp.ko module cannot be installed. In 
particular this means the driver for
     any VFs of Netronome Agilio SmartNICs which have been made available to 
guests using PCI pass-through
     cannot be used by those guests if they have installed using Canonical 
cloud images, a likely scenario.

     In contrast the driver for the i40e is provided in the linux-modules 
package and thus guests can
     access their VFs in the scenario described above.

     Thus we do not believe it is unreasonable to request that nfp.ko be 
included in linux-modules rather
     than linux-modules-extras. And we believe that this warrants SRU inclusion 
as it is the difference between
     users-of guests being able to use Netronome Agilio SmartNICs and not be 
able to use them.

     This is a packaging update request and included no request to change the 
kernel source code,
     thus no backports are requred.

  [Test Case]

   * Install system using Canonical cloud images

   * Observer that
  /lib/modules/*/kernel/drivers/net/ethernet/netronome/nfp/nfp.ko is
  missing;

   * If an Netronome Agilio SmartNIC device is present, via PCI pass-through or 
otherwise,
     that the nfp driver is not loaded and no netdevs are present for the 
Netronome Agilio SmartNIC.

  [Regression Potential]

   * Any bugs present in the nfp.ko will now be exposted to guests. However as 
the same nfp.ko driver binary
     is already included in and available on installs that have access to 
linux-modules-extra, this does not
     seem an unreasonable burden.

  [Other Info]

   * None

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

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

[Kernel-packages] [Bug 1767490] Re: Add d-i support for Huawei NICs

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

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

** Description changed:

  [Impact]
  The hinic driver isn't included in the installer, so it isn't possible to use 
Huawei NICs for network installs.
  
  [Test Case]
  Boot d-i on a system with a Huawei PCIe card. Proceed to the network 
configuration screen, and see if that NIC is displayed.
  
+ [Fix]
+ Adding the module to the nic-modules list for d-i.
+ 
  [Regression Risk]
  Including a new driver is a common practice that should have minimal 
regression risk.

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

Title:
  Add d-i support for Huawei NICs

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  The hinic driver isn't included in the installer, so it isn't possible to use 
Huawei NICs for network installs.

  [Test Case]
  Boot d-i on a system with a Huawei PCIe card. Proceed to the network 
configuration screen, and see if that NIC is displayed.

  [Fix]
  Adding the module to the nic-modules list for d-i.

  [Regression Risk]
  Including a new driver is a common practice that should have minimal 
regression risk.

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

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

[Kernel-packages] [Bug 1746474] Re: unregister_netdevice: waiting for eth0 to become free. Usage count = 5

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

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

Title:
  unregister_netdevice: waiting for eth0 to become free. Usage count = 5

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

Bug description:
  == SRU Justification ==
  Commit 52df157f17e5 introduced a regression in v4.13-rc1.  This regression
  causes a stack trace to occur when tearing down an LXD container.  The process
  hangs with the following message:

  "unregister_netdevice: waiting for eth0 to become free. Usage count =
  5"

  This regression is fixed by commit 510c321b5571, which is in mainline as of
  v4.16-rc7.  The fix is needed in Artful and Bionic.  However, Artful needs
  a prereq commit, so it's SRU request will be sent separately.

  
  == Fix ==
  510c321b5571 ("xfrm: reuse uncached_list to track xdsts")

  == Regression Potential ==
  Low.  This commit is to fix a current regression.

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


  This occurs when tearing down an LXD container.

  LXD monitor process hangs with the following stack:

  $ sudo cat /proc/27043/stack
  [] msleep+0x2e/0x40
  [] netdev_run_todo+0x11f/0x310
  [] rtnetlink_rcv+0x2d/0x30
  [] netlink_unicast+0x18c/0x240
  [] netlink_sendmsg+0x2dd/0x3c0
  [] sock_sendmsg+0x38/0x50
  [] ___sys_sendmsg+0x2e3/0x2f0
  [] __sys_sendmsg+0x54/0x90
  [] SyS_sendmsg+0x12/0x20
  [] do_syscall_64+0x5b/0xc0
  [] entry_SYSCALL64_slow_path+0x8/0x8
  [] 0x

  Issue submitted to LXD as well ([1]), though as indicated there, it
  seems to be a kernel bug.

  [1] https://github.com/lxc/lxd/issues/4208

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Wed Jan 31 11:42:59 2018
  InstallationDate: Installed on 2016-11-09 (447 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  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/1746474/+subscriptions

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

[Kernel-packages] [Bug 1771620] Re: Hang on network interface removal in Xen virtual machine

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

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

Title:
Hang on network interface removal in Xen virtual machine

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

Bug description:

== SRU Justification ==
Upstream commit 5b5971df3bc2 introduced a regression in v4.15-rc2. This
regression causes a hang on network interface removal in Xen virtual machine.

This regression is fixed by commit c2d2e6738a209 in v4.16-rc4.

== Fix ==
c2d2e6738a20 ("xen-netfront: Fix hang on device removal")

== Regression Potential ==
Low. Fixes a current regression and specific to Xen.

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

On a hosting platform running Xen hypervisor, in a virtual machine
with Ubuntu 18.04 system and the default kernel from Ubuntu, I try to
detach a virtual network interface. On the Xen side, the virtual
interface is removed from the VM but the kernel still has the
interface. Then a couple of minutes afterwards, the kernel log show
this kernel trace:

INFO: task xenwatch:108 blocked for more than 120 seconds.
Tainted: GW4.15.0-20-generic #21-Ubuntu
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
xenwatchD0 108 2 0x8000
Call Trace:
__schedule+0x297/0x8b0
schedule+0x2c/0x80
xennet_remove+0xda/0x1c0
? wait_woken+0x80/0x80
xenbus_dev_remove+0x54/0xa0
device_release_driver_internal+0x15b/0x220
device_release_driver+0x12/0x20
bus_remove_device+0xec/0x160
? xenbus_otherend_changed+0x110/0x110
device_del+0x13d/0x360
? xenbus_otherend_changed+0x110/0x110
? xenbus_otherend_changed+0x110/0x110
device_unregister+0x1a/0x60
xenbus_dev_changed+0xa3/0x1e0
? xenwatch_thread+0xcc/0x160
frontend_changed+0x21/0x50
xenwatch_thread+0xc4/0x160
? wait_woken+0x80/0x80
kthread+0x121/0x140
? find_watch+0x40/0x40
? kthread_create_worker_on_cpu+0x70/0x70
ret_from_fork+0x35/0x40

In the git repository of Linux, the commit
c2d2e6738a209f0f9dffa2dc8e7292fc45360d61 (xen-netfront: Fix hang on
device removal)

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c2d2e6738a209f0f9dffa2dc8e7292fc45360d61
seems to be related to this situation.

I rebuilded the Ubuntu kernel from the package source and applied this
patch. Once the VM has booted with the new kernel, I was able to
remove network interface without hangs from the kernel.

I also booted the VM with the Ubuntu kernel 4.13.0-42-generic and was
able to remove the network interface with success.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-20-generic 4.15.0-20.21
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May 16 16:36:06 2018
ProcEnviron:
TERM=rxvt-unicode
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed
UpgradeStatus: No upgrade log present (probably fresh install)

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

--
Mailing list: https://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 1772682] Re: No sound for Dell Inspiron 5758

2018-05-23 Thread Andrew

Hello,

I did not manage to boot 18.04 by usb driver. Some problems in the BIOS
configuration arose.
Please, tell me BIOS setting in this case.

P.S. Note, I tried to boot via Legacy optiion.

Andrew.

On Wed, May 23, 2018 at 11:22 AM, Po-Hsu Lin 
wrote:

> Hi Andrew,
>
> Ubuntu 14.04 Trusty was released in 2014 Apr., which is relatively old
> to your system (probably released in mid-2015) so it's Wifi driver and
> the sound card driver might not be available.
>
> I would recommend you to give 18.04 Bionic a try, you can just test it
> with a LiveUSB.
>
> (Marking this bug as Incomplete base on Joseph's request in comment#2)
>
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1772682
>
> Title:
>   No sound for Dell Inspiron 5758
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I have Dell Inspiron 5758 with UBUNTU 14.04 LTS.have
>
>
>   I tried to update system but the computer did not finish updating, and
> informed me that there is no internet connection, while the connection was
> OK.
>   As a result, I still  have not been any sound in the computer.
>
>
>   Sincerely yours, Andrew.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 14.04
>   Package: linux-image-3.13.0-147-generic 3.13.0-147.196
>   ProcVersionSignature: Ubuntu 3.13.0-147.196-generic 3.13.11-ckt39
>   Uname: Linux 3.13.0-147-generic x86_64
>   ApportVersion: 2.14.1-0ubuntu3.23
>   Architecture: amd64
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
> '/dev/snd/timer'] failed with exit code 1:
>   CRDA:
>country RU:
> (2402 - 2482 @ 40), (N/A, 20)
> (5735 - 5835 @ 20), (N/A, 30)
>   Date: Tue May 22 19:03:51 2018
>   DistributionChannelDescriptor:
># This is a distribution channel descriptor
># For more information see http://wiki.ubuntu.com/
> DistributionChannelDescriptor
>canonical-oem-somerville-trusty-amd64-20140620-0
>   HibernationDevice: RESUME=UUID=e4298f48-6ba8-489f-b77c-bdb717a22436
>   InstallationDate: Installed on 2016-01-25 (848 days ago)
>   InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary
> 20140620-04:25
>   MachineType: Dell Inc. Inspiron 5758
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-147-generic
> root=UUID=63a6a91d-fec3-47ee-982b-7dd7b57320f1 ro quiet splash
> radeon.modeset=0 nouveau.modeset=0 vt.handoff=7
>   PulseList:
>Error: command ['pacmd', 'list'] failed with exit code 1: Home
> directory not accessible: Permission denied
>No PulseAudio daemon running, or not running as session daemon.
>   RelatedPackageVersions:
>linux-restricted-modules-3.13.0-147-generic N/A
>linux-backports-modules-3.13.0-147-generic  N/A
>linux-firmware  1.127.24
>   SourcePackage: linux
>   StagingDrivers: rts5139
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 11/06/2015
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A07
>   dmi.board.name: 09CGRW
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/06/2015:svnDellInc.:
> pnInspiron5758:pvr01:rvnDellInc.:rn09CGRW:rvrA00:cvnDellInc.:ct9:cvr:
>   dmi.product.name: Inspiron 5758
>   dmi.product.version: 01
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1772682/+subscriptions
>

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

Title:
  No sound for Dell Inspiron 5758

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have Dell Inspiron 5758 with UBUNTU 14.04 LTS.have

  
  I tried to update system but the computer did not finish updating, and 
informed me that there is no internet connection, while the connection was OK. 
  As a result, I still  have not been any sound in the computer. 

  
  Sincerely yours, Andrew.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-147-generic 3.13.0-147.196
  ProcVersionSignature: Ubuntu 3.13.0-147.196-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-147-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA:
   country RU:
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  Date: Tue May 22 19:03:51 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  HibernationDevice:

[Kernel-packages] [Bug 1772859] [NEW] Network Manager is not able to manage the devices on Ubuntu 18.04

2018-05-23 Thread bugproxy

Public bug reported:

NetworkManager is not able to manage the devices on latest Ubuntu(18.04)
 
---uname output---
Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 s390x 
s390x s390x GNU/Linux
 
Machine Type = z14 s390 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
 1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4).
2. Configure a network device and login to the partition through ssh.
3. Now you can see the following output
root@(none):~# nmcli d s
DEVICE  TYPE  STATE  CONNECTION
eth0ethernet  unmanaged  --
eth1ethernet  unmanaged  --
lo  loopback  unmanaged  --
 
Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el 
s390x 
 
The userspace tool has the following bit modes: 64-bit 

Userspace rpm: NetworkManager --version 1.10.4

Userspace tool obtained from project website:  na 
 

Some more information about the issue:

Network device has been configured manually after the image is up from Support 
Element(SE):
- znetconf -a 
- cat /sys/bus/ccwgroup/drivers/qeth//if_name
- ifconfig   netmask 255.255.255.0
- route add default gw  
- SSH service has been configured

This helped us to login to the Lpar. In Lpar
- output of znetconf -c
Device IDs TypeCard Type  CHPID Drv. Name   
  State

-
0.0.1a80,0.0.1a81,0.0.1a82 1731/01 OSD_10GIG A8 qeth eth0   
  online
0.0.1810,0.0.1811,0.0.1812 1731/01 OSD_1000  D0 qeth eth1   
  online

- output of nmcli c s
root@(none):~# nmcli c s
NAME  UUID  TYPE  DEVICE

- output of nmcli d s
root@(none):~# nmcli d s
DEVICE  TYPE  STATE  CONNECTION
eth0ethernet  unmanaged  --
eth1ethernet  unmanaged  --
lo  loopback  unmanaged  --

* The above output shows that devices are not managed by nmcli

After some investigation we found couple of suggestions like
1. Ubuntu(version <17.04): Creating an empty 
file(/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) and 
restarting NM,
   solved the issue.
   
2. Ubuntu(version 17.10): Copying the said 
file(10-globally-managed-devices.conf) from /usr/lib to /etc/ and modifying the 
   "unmanaged-devices" to none, resolved the issue.

* link for reference: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1638842

For the latest version(18.04), none of the above solutions worked.

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


** Tags: architecture-all bugnameltc-168090 severity-critical 
targetmilestone-inin---

** Tags added: architecture-all bugnameltc-168090 severity-critical
targetmilestone-inin---

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

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

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

Title:
  Network Manager is not able to manage the devices on Ubuntu 18.04

Status in linux package in Ubuntu:
  New

Bug description:
  NetworkManager is not able to manage the devices on latest Ubuntu(18.04)
   
  ---uname output---
  Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 
s390x s390x s390x GNU/Linux
   
  Machine Type = z14 s390 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4).
  2. Configure a network device and login to the partition through ssh.
  3. Now you can see the following output
  root@(none):~# nmcli d s
  DEVICE  TYPE  STATE  CONNECTION
  eth0ethernet  unmanaged  --
  eth1ethernet  unmanaged  --
  lo  loopback  unmanaged  --
   
  Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el 
s390x 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: NetworkManager --version 1.10.4

  Userspace tool obtained from project website:  na 
   

  Some more information about the issue:

  Network device has been configured manually after the image is up from 
Support Element(SE):
  - znetconf -a 
  - cat /sys/bus/ccwgroup/drivers/qeth//if_name
  - ifconfig   netmask 255.255.255.0
  - route add default gw  
  - SSH service has been configured
  
  This helped us to login to the Lpar. In Lpar
  - output of znetconf -c
  Device IDs TypeCard Type  CHPID Drv. Name 
State

[Kernel-packages] [Bug 1764194] Re: Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

2018-05-23 Thread Claudio Castelpietra

Hi everybody.
I have Ubuntu 18.04 in dual-boot with Windows 10.
With Windows, I downloaded and executed/installed Bios version 1.2.3 from Dell 
support site.
Now Ubuntu 18.04 is back to work.
I hope this helps someone.

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

Title:
  Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

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

Bug description:
  == SRU Justification ==
  This bug causes a Dell Latitude 5490/5590 with BIOS update 1.1.9 to get a
  black screen at boot. Specifying 'nomodeset' on the kernel command line works
  around the problem.

  Intel resolved the problem in upstream commit a3520b8992e5.  This commit
  is now in mainline as of 4.17.rc2.  It has also been cc'd to upstream
  stable.

  
  == Fix ==
  a3520b8992e5 ("drm/i915/bios: filter out invalid DDC pins from VBT child 
devices")

  == Regression Potential ==
  Low.  This commit was also cc'd to upstream stable, so it recieved
  additional upstream review.


  
  Description:Ubuntu 16.04.4 LTS
  Release:16.04

  Ubuntu 16.04.4 LTS was installed to some Dell Latitude 5490 & 5590
  laptops, originally running BIOS version 1.0.8. The install media and
  the installed OS was running linux-generic-hwe kernel 4.13.0.

  After upgrading BIOS to latest version 1.1.9, the kernel no longer
  boots: right after loading the i915 drm driver, the screen goes black,
  and the machine can only be reset or power cycled. This is true for
  both the installation media, and the OS instance previously installed
  to the disk and updated to the latest hwe kernel 4.13.0-38.

  Specifying 'nomodeset' on the kernel command line works around the
  problem by disabling the i915 drm driver functionality. In that case,
  several display driver function are obviously missing (eg GLX &
  xrandr).

  The problem manifested itself even when using the drm upstream latest 
git-head version. A custom built kernel was used to provide logs for this 
upstream bug report:
  https://bugs.freedesktop.org/show_bug.cgi?id=105549

  The upstream Intel developers provided a patch, which was successfully tested 
by both the original reporter and me.
  https://patchwork.freedesktop.org/patch/216371/
  
https://github.com/freedesktop/drm-tip/commit/f212bf9abe5de9f938fecea7df07046e74052dde

  I backported this fix to ubuntu-xenial hwe git-head, and tested the
  result successfully. I'd like this fix to be added to the ubuntu-
  xenial linux-generic-hwe kernel.

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

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

[Kernel-packages] [Bug 1765977] Re: HiSilicon HNS NIC names are truncated in /proc/interrupts

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

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

Title:
  HiSilicon HNS NIC names are truncated in /proc/interrupts

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

Bug description:
  [Impact]
  HiSilicon HNS NIC names are truncated in /proc/interrupts, making it 
difficult for an admin to associate activity among adapters in the system.

  [Test Case]
  $ grep enahisic2i0-tx /proc/interrupts | sed 's/.* //'
  Without the fix:
enahisic2i0-tx0
enahisic2i0-tx1
[...]
enahisic2i0-tx8
enahisic2i0-tx9
enahisic2i0-tx1
enahisic2i0-tx1
enahisic2i0-tx1
enahisic2i0-tx1
enahisic2i0-tx1
enahisic2i0-tx1
  With the fix:
enahisic2i0-tx0
enahisic2i0-tx1
enahisic2i0-tx2
[...]
enahisic2i0-tx8
enahisic2i0-tx9
enahisic2i0-tx10
enahisic2i0-tx11
enahisic2i0-tx12
enahisic2i0-tx13
enahisic2i0-tx14
enahisic2i0-tx15

  [Regression Risk]
  Upstream patch, restricted to a single driver for a system we can directly 
test.

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

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

[Kernel-packages] [Bug 1768971] Re: Warnings/hang during error handling of SATA disks on SAS controller

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

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

Title:
  Warnings/hang during error handling of SATA disks on SAS controller

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

Bug description:
  [Impact]
  When a SATA device, attached to a SAS controller, begins generating errors 
(e.g. device failing, or someone yanked it), the SAS error handling will 
complete, but may leave zombie ATA commands that never get properly 
processed/freed. This can cause some ugly messages on the console, and 
eventually leads to a system hang-up.

  WARNING: CPU: 0 PID: 28512 at drivers/ata/libata-eh.c:4037
  ata_eh_finish+0xb4/0xcc
  CPU: 0 PID: 28512 Comm: kworker/u32:2 Tainted: G W  OE 4.14.0#1
  ..
  Call trace:
  [] ata_eh_finish+0xb4/0xcc
  [] ata_do_eh+0xc4/0xd8
  [] ata_std_error_handler+0x44/0x8c
  [] ata_scsi_port_error_handler+0x480/0x694
  [] async_sas_ata_eh+0x4c/0x80
  [] async_run_entry_fn+0x4c/0x170
  [] process_one_work+0x144/0x390
  [] worker_thread+0x144/0x418
  [] kthread+0x10c/0x138
  [] ret_from_fork+0x10/0x18

  [Test Case]
  I don't have a reliable reproducer for this, but one possible test is to yank 
an active/hotpluggable SATA disk from its controller and see if the above 
symptoms occur.

  [Fix] 
  The solution here is to call into libata to have it process the remaining 
commands, allowing us to free up the zombie commands, preventing the leak and 
eventual starvation.

  [Regression Risk]
  This is a clean cherry-pick from upstream, so any regressions should have 
upstream support. As of this writing, there are no changesets in linux-next 
marked as Fixing this commit, implying that upstream has not yet found/fixed 
any bugs related to it.

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

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

[Kernel-packages] [Bug 1764982] Re: [bionic] machine stuck and bonding not working well when nvmet_rdma module is loaded

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

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

Title:
  [bionic] machine stuck and bonding not working well when nvmet_rdma
  module is loaded

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

Bug description:

  == SRU Justification ==
  This bug causes the machine to get stuck and bonding to not work when
  the nvmet_rdma module is loaded.

  Both of these commits are in mainline as of v4.17-rc1.

  == Fixes ==
  a3dd7d0022c3 ("nvmet-rdma: Don't flush system_wq by default during 
remove_one")
  9bad0404ecd7 ("nvme-rdma: Don't flush delete_wq by default during remove_one")

  == Regression Potential ==
  Low.  Limited to nvme driver and tested by Mellanox.

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


  
  == Original Bug Description ==

  Hi
  Machine stuck after unregistering bonding interface when the nvmet_rdma 
module is loading.

  scenario:

   # modprobe nvmet_rdma
   # modprobe -r bonding
   # modprobe bonding  -v mode=1 miimon=100 fail_over_mac=0
   # ifdown eth4
   # ifdown eth5
   # ip addr add 15.209.12.173/8 dev bond0
   # ip link set bond0 up
   # echo +eth5 > /sys/class/net/bond0/bonding/slaves
   # echo +eth4 > /sys/class/net/bond0/bonding/slaves
   # echo -eth4 > /sys/class/net/bond0/bonding/slaves
   # echo -eth5 > /sys/class/net/bond0/bonding/slaves
   # echo -bond0 > /sys/class/net/bonding_masters

  dmesg:

  kernel: [78348.225556] bond0 (unregistering): Released all slaves
  kernel: [78358.339631] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78368.419621] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78378.499615] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78388.579625] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78398.659613] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78408.739655] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78418.819634] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78428.899642] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78438.979614] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78449.059619] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78459.139626] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78469.219623] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78479.299619] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78489.379620] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78499.459623] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78509.539631] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2
  kernel: [78519.619629] unregister_netdevice: waiting for bond0 to become 
free. Usage count = 2

  The following upstream commits that fix this issue

  commit a3dd7d0022c347207ae931c753a6dc3e6e8fcbc1
  Author: Max Gurtovoy 
  Date:   Wed Feb 28 13:12:38 2018 +0200

  nvmet-rdma: Don't flush system_wq by default during remove_one

  The .remove_one function is called for any ib_device removal.
  In case the removed device has no reference in our driver, there
  is no need to flush the system work queue.

  Reviewed-by: Israel Rukshin 
  Signed-off-by: Max Gurtovoy 
  Reviewed-by: Sagi Grimberg 
  Signed-off-by: Keith Busch 
  Signed-off-by: Jens Axboe 

  diff --git a/drivers/nvme/target/rdma.c b/drivers/nvme/target/rdma.c
  index aa8068f..a59263d 100644
  --- a/drivers/nvme/target/rdma.c
  +++ b/drivers/nvme/target/rdma.c
  @@ -1469,8 +1469,25 @@ static struct nvmet_fabrics_ops nvmet_rdma_ops = {
   static void nvmet_rdma_remove_one(struct ib_device *ib_device, void 
*client_data)
   {
  struct nvmet_rdma_queue *queue, *tmp;
  + struct nvmet_rdma_device *ndev;
  + bool found = false;
  +
  + mutex_lock(_list_mutex);
  + list_for_each_entry(ndev, _list, entry) {
  + if (ndev->device == ib_device) {
  + found = true;
  + break;
  + }
  + }
  + mutex_unlock(_list_mutex);
  +
  + if (!found)
  + return;

  -   /* Device is being removed, delete all queues using this device */
  + /*
  +  *

[Kernel-packages] [Bug 1770003] Re: qla2xxx: Fix page fault at kmem_cache_alloc_node()

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

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

Title:
  qla2xxx: Fix page fault at kmem_cache_alloc_node()

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

Bug description:
  == SRU Justification ==
  IBM is requesting these nine patches to be SRU'd to Bionic.  IBM found
  that the current Bionic kernel contains a problem related to qla2xxx
  driver which causes the following:

  [   66.295233] Unable to handle kernel paging request for data at address 
0x8882f6ed90e9151a
  [   66.295297] Faulting instruction address: 0xc038a110
  cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
  pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
  lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
  sp: c692f8d0
     msr: 90009033
     dar: 8882f6ed90e9151a
    current = 0xc698fd00
    paca= 0xcfab7000   softe: 0irq_happened: 0x01
  pid   = 1762, comm = systemd-journal
  Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 
4.15.0-20.21-generic 4.15.20)
  enter ? for help
  [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
  [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
  [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
  [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
  [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
  [c692fe30] c000b184 system_call+0x58/0x6c
  --- Exception: c00 (System Call) at 74826f6fa9c4
  SP (75dc5510) is in userspace

  We were able to get rid of this problem cherry picking some of the
  upstream patches. Do you think they might fit in the SRU criteria?

  The commit ids are below and they were easily cherry picked.

  eaf75d1815dad230dac2f1e8f1dc0349b2d50071: scsi: qla2xxx: Fix double free bug 
after firmware timeout
  6d67492764b39ad6efb6822816ad73dc141752f4: scsi: qla2xxx: Prevent relogin 
trigger from sending too many commands
  7ac0c332f96bb9688560726f5e80c097ed8de59a: scsi: qla2xxx: Fix warning in 
qla2x00_async_iocb_timeout()
  045d6ea200af794ba15515984cff63787a7fc3c0: scsi: qla2xxx: Don't call 
dma_free_coherent with IRQ disabled.
  1ae634eb28533b82f9777a47c1ade44cb8c0182b: scsi: qla2xxx: Serialize session 
free in qlt_free_session_done
  d8630bb95f46ea118dede63bd75533faa64f9612: scsi: qla2xxx: Serialize session 
deletion by using work_lock
  Requries: 1c6cacf4ea6c04a58a0e3057f5ed60c24a4ffeff ('scsi: qla2xxx: 
Fixup locking for session deletion')
  94cff6e114df56d0df74cdabe3481df38d9b0c1e: scsi: qla2xxx: Remove unused 
argument from qlt_schedule_sess_for_dele?
  9cd883f07a54e5301d51e259acd250bb035996be: scsi: qla2xxx: Fix session cleanup 
for N2N


  == Regression Potential ==
  Medium.  There are nine patches in this pull request.  They are not specific 
to a
  paticular arch, but they are specific to qla2xxx.

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

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

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

[Kernel-packages] [Bug 1772038] Re: ubuntu/xubuntu 18.04 kernel crash during install.

** Attachment added: "Screen picture after kernel crash"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772038/+attachment/5143246/+files/2018-05-23%2003.21.31.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/1772038

Title:
  ubuntu/xubuntu 18.04 kernel crash during install.

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  I've been trying to install ubuntu 18.04, but the system crashes with a 
kernel panic and thus won't run. So how do I report this bug?
  The system passes all memory tests and runs 17.10 with no problems, but will 
not run 18.04

  There is very little data gathering that I can do, as the system will
  not boot, not even into text mode.

  PS. This back door way of creating a bug report is very poor when
  dealing with systems that don't run.

  The steps required to reproduce this bug are:
  1) download Ubuntu and/or Xubuntu
  2) burn the installation image to a dvd
  3) insert dvd into target computer
  4) power on target computer
  5) wait a couple of seconds
  6) Stare at frozen screen saying Kernel panic
  7) Go back to step 1

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

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

[Kernel-packages] [Bug 1772038] Re: ubuntu/xubuntu 18.04 kernel crash during install.

After reviewing both screen shots I see that I miss read the timestamps
in the first image, so the crash on my second machine has higher
timestamp numbers NOT lower ones. Opps!

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

Title:
  ubuntu/xubuntu 18.04 kernel crash during install.

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  I've been trying to install ubuntu 18.04, but the system crashes with a 
kernel panic and thus won't run. So how do I report this bug?
  The system passes all memory tests and runs 17.10 with no problems, but will 
not run 18.04

  There is very little data gathering that I can do, as the system will
  not boot, not even into text mode.

  PS. This back door way of creating a bug report is very poor when
  dealing with systems that don't run.

  The steps required to reproduce this bug are:
  1) download Ubuntu and/or Xubuntu
  2) burn the installation image to a dvd
  3) insert dvd into target computer
  4) power on target computer
  5) wait a couple of seconds
  6) Stare at frozen screen saying Kernel panic
  7) Go back to step 1

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

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

[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode

2018-05-23 Thread Zhanglei Mao

In #18, 4.13 should replaced with 4.4.0-116 which used by 16.04.4 ISO.

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

Title:
  Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI
  boot mode

Status in linux package in Ubuntu:
  Triaged
Status in install-package source package in Bionic:
  New
Status in linux source package in Bionic:
  Triaged

Bug description:
  For all(as I know) Huawei servers, the vga adapter are embed in the
  iBMC chips. Those server can install from ISO manually for 16.04.4 and
  screen display normally. But for 18.04 ( tested both for daily and
  final beta)version, the install screen is blur. One of tested server
  is Huawei 2855 v5, the certification link for 16.04 are
  https://certification.ubuntu.com/hardware/201707-25596/.

  Below are key difference of dmesg. It seems might related with DRM.

  18.04 install screen is blur 
  dmesg
  ...
  [2.039009] fb0: EFI VGA frame buffer device
  ...
  [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [4.191435] [drm] No driver support for vblank timestamp query.
  [4.209338] checking generic (9000 30) vs hw (0 0)
  [4.209384] fbcon: hibmcdrmfb (fb1) is primary device
  [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63
  ...
  [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device
  [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on 
minor 0
  ...
  [5.636624] vga16fb: initializing
  [5.636627] vga16fb: mapped to 0x48a7a1d2
  [5.636630] checking generic (9000 30) vs hw (a 1)
  [5.636676] fb2: VGA16 VGA frame buffer device
  ...

  16.04.4 install screen is fine (no screen blur)
  dmesg
  ...
  [2.000419] fb0: EFI VGA frame buffer device
  
  [8.795065] vga16fb: initializing
  [8.795068] vga16fb: mapped to 0x880a
  [8.795071] checking generic (9800 30) vs hw (a 1)
  [8.795121] fb1: VGA16 VGA frame buffer device
  ...

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

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

[Kernel-packages] [Bug 1769730] Re: Some PCIe errors not surfaced through rasdaemon

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

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

Title:
  Some PCIe errors not surfaced through rasdaemon

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

Bug description:
  [Impact]
  The APEI (ACPI Platform Error Interface) interface is supposed to report PCIe 
errors to the AER (Advanced Error Reporting) driver, which surfaces them to 
userspace. However, we're currently only reporting "recoverable" errors and not 
errors of other types (e.g. correctable), thus hiding signs of faulty hardware 
from the user.

  [Test Case]
  $ sudo apt install rasdaemon
  # On a system that supports ACPI EINJ (dmesg | grep "ACPI: EINJ"), use the 
attached script to inject a correctable PCIe error.
  $ sudo ras-mc-ctl --errors
  # There should be an entry for the injected error, as shown below:
  No Memory errors.

  PCIe AER events:
  1 2018-05-07 17:55:46 + Fatal error: Receiver Error

  No Extlog errors.

  No MCE errors.

  [Fix]
  There is a 2-patch upstream fix that addresses this issue and cleanly 
cherry-picks into Ubuntu. The solution is to not artficially limit which PCIe 
errors are reported down to the AER driver to those that are recoverable.

  [Regression Risk]
  Above test was ran on x86 & ARM platforms to mitigate regression risk.

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

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

[Kernel-packages] [Bug 1772038] Re: ubuntu/xubuntu 18.04 kernel crash during install.

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

Title:
  ubuntu/xubuntu 18.04 kernel crash during install.

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  I've been trying to install ubuntu 18.04, but the system crashes with a 
kernel panic and thus won't run. So how do I report this bug?
  The system passes all memory tests and runs 17.10 with no problems, but will 
not run 18.04

  There is very little data gathering that I can do, as the system will
  not boot, not even into text mode.

  PS. This back door way of creating a bug report is very poor when
  dealing with systems that don't run.

  The steps required to reproduce this bug are:
  1) download Ubuntu and/or Xubuntu
  2) burn the installation image to a dvd
  3) insert dvd into target computer
  4) power on target computer
  5) wait a couple of seconds
  6) Stare at frozen screen saying Kernel panic
  7) Go back to step 1

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

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

[Kernel-packages] [Bug 1772038] Re: ubuntu/xubuntu 18.04 kernel crash during install.

OK, I've had time to try the latest kernel from the daily-live/current
directory called 'cosmic' and it does the same thing. I've tried it on
my second machine and like I said earlier it has the same results but
the timestamps are lower. I'll post a new picture of the screen results.

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

Title:
  ubuntu/xubuntu 18.04 kernel crash during install.

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  I've been trying to install ubuntu 18.04, but the system crashes with a 
kernel panic and thus won't run. So how do I report this bug?
  The system passes all memory tests and runs 17.10 with no problems, but will 
not run 18.04

  There is very little data gathering that I can do, as the system will
  not boot, not even into text mode.

  PS. This back door way of creating a bug report is very poor when
  dealing with systems that don't run.

  The steps required to reproduce this bug are:
  1) download Ubuntu and/or Xubuntu
  2) burn the installation image to a dvd
  3) insert dvd into target computer
  4) power on target computer
  5) wait a couple of seconds
  6) Stare at frozen screen saying Kernel panic
  7) Go back to step 1

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

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

[Kernel-packages] [Bug 1772682] Re: No sound for Dell Inspiron 5758

2018-05-23 Thread Po-Hsu Lin

Hi Andrew,

Ubuntu 14.04 Trusty was released in 2014 Apr., which is relatively old
to your system (probably released in mid-2015) so it's Wifi driver and
the sound card driver might not be available.

I would recommend you to give 18.04 Bionic a try, you can just test it
with a LiveUSB.

(Marking this bug as Incomplete base on Joseph's request in comment#2)

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

Title:
  No sound for Dell Inspiron 5758

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have Dell Inspiron 5758 with UBUNTU 14.04 LTS.have

  
  I tried to update system but the computer did not finish updating, and 
informed me that there is no internet connection, while the connection was OK. 
  As a result, I still  have not been any sound in the computer. 

  
  Sincerely yours, Andrew.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-147-generic 3.13.0-147.196
  ProcVersionSignature: Ubuntu 3.13.0-147.196-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-147-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA:
   country RU:
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  Date: Tue May 22 19:03:51 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  HibernationDevice: RESUME=UUID=e4298f48-6ba8-489f-b77c-bdb717a22436
  InstallationDate: Installed on 2016-01-25 (848 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. Inspiron 5758
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-147-generic 
root=UUID=63a6a91d-fec3-47ee-982b-7dd7b57320f1 ro quiet splash radeon.modeset=0 
nouveau.modeset=0 vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-147-generic N/A
   linux-backports-modules-3.13.0-147-generic  N/A
   linux-firmware  1.127.24
  SourcePackage: linux
  StagingDrivers: rts5139
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 09CGRW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/06/2015:svnDellInc.:pnInspiron5758:pvr01:rvnDellInc.:rn09CGRW:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5758
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1772682] Re: No sound

2018-05-23 Thread Andrew

Dear Joseph,

Which the build (from BUILD.LOG.amd64

 in v4.17-rc6) should me run?

Andrew.

On Tue, May 22, 2018 at 7:23 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:

> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.17 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.17-rc6
>
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Medium
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1772682
>
> Title:
>   No sound
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I have Dell Inspiron 5758 with UBUNTU 14.04 LTS.have
>
>
>   I tried to update system but the computer did not finish updating, and
> informed me that there is no internet connection, while the connection was
> OK.
>   As a result, I still  have not been any sound in the computer.
>
>
>   Sincerely yours, Andrew.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 14.04
>   Package: linux-image-3.13.0-147-generic 3.13.0-147.196
>   ProcVersionSignature: Ubuntu 3.13.0-147.196-generic 3.13.11-ckt39
>   Uname: Linux 3.13.0-147-generic x86_64
>   ApportVersion: 2.14.1-0ubuntu3.23
>   Architecture: amd64
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
> '/dev/snd/timer'] failed with exit code 1:
>   CRDA:
>country RU:
> (2402 - 2482 @ 40), (N/A, 20)
> (5735 - 5835 @ 20), (N/A, 30)
>   Date: Tue May 22 19:03:51 2018
>   DistributionChannelDescriptor:
># This is a distribution channel descriptor
># For more information see http://wiki.ubuntu.com/
> DistributionChannelDescriptor
>canonical-oem-somerville-trusty-amd64-20140620-0
>   HibernationDevice: RESUME=UUID=e4298f48-6ba8-489f-b77c-bdb717a22436
>   InstallationDate: Installed on 2016-01-25 (848 days ago)
>   InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary
> 20140620-04:25
>   MachineType: Dell Inc. Inspiron 5758
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-147-generic
> root=UUID=63a6a91d-fec3-47ee-982b-7dd7b57320f1 ro quiet splash
> radeon.modeset=0 nouveau.modeset=0 vt.handoff=7
>   PulseList:
>Error: command ['pacmd', 'list'] failed with exit code 1: Home
> directory not accessible: Permission denied
>No PulseAudio daemon running, or not running as session daemon.
>   RelatedPackageVersions:
>linux-restricted-modules-3.13.0-147-generic N/A
>linux-backports-modules-3.13.0-147-generic  N/A
>linux-firmware  1.127.24
>   SourcePackage: linux
>   StagingDrivers: rts5139
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 11/06/2015
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A07
>   dmi.board.name: 09CGRW
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/06/2015:svnDellInc.:
> pnInspiron5758:pvr01:rvnDellInc.:rn09CGRW:rvrA00:cvnDellInc.:ct9:cvr:
>   dmi.product.name: Inspiron 5758
>   dmi.product.version: 01
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1772682/+subscriptions
>

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

Title:
  No sound for Dell Inspiron 5758

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Dell Inspiron 5758 with UBUNTU 14.04 LTS.have

  
  I tried to update system but the computer did not finish updating, and 
informed me that there is no internet connection, while the connection was OK. 
  As a result, I still  have not been any sound in the computer. 

  
  Sincerely yours, Andrew.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-147-generic 3.13.0-147.196
  ProcVersionSignature: Ubuntu 3.13.0-147.196-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-147-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA:
   country RU:
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  Date: Tue May 22 19:03:51 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see

[Kernel-packages] [Bug 1768974] Re: Several hisi_sas bug fixes

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

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

Title:
  Several hisi_sas bug fixes

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

Bug description:
  [Impact]
  Several issues have been fixed upstream in the hisi_sas driver:
   - Driver may configure the wrong signal attenuation setting
   - Driver may not negotiate the correct max link rate supported by the phy
   - phy must be disabled before trying to change its link rate
   - Internal abort timeout doesn't take into account link negotiation time
   - Driver returns incorrect values to upper levels

  [Test Case]
  Regression testing on D05 and D06 systems, which have different versions of 
this controller.

  [Regression Risk]
  Code changes are restricted to the hisi_sas driver, and the HisSilicon D05 
and D06 are the only two boards Ubuntu supports that use this driver. Explicit 
testing on these two boards should mitigate the regression risk.

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

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

[Kernel-packages] [Bug 1413440] Re: USB stops working after a while (xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command)

2018-05-23 Thread Volodymyr Shymanskyi

Lenovo IdeaPad 720s (i5-8250U), the same issue.

On resume, I get:
[  213.347656] usb 1-7: device descriptor read/64, error -110

➜  ~ lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
|__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
|__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
|__ Port 7: Dev 5, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 7: Dev 5, If 1, Class=Wireless, Driver=btusb, 12M

This way, i was getting my BT adapter disconnected.
But also I was experiencing a USB3 flash drive reconnecting unexpectedly during 
normal operation (no sleep/resume).

'pci=nomsi iommu=soft' helped, at least for now.

➜  ~ lsb_release -a  
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04 LTS
Release:18.04
Codename:   bionic
➜  ~ uname -a  
Linux vshymanskyy-720S 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 
2018 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/1413440

Title:
  USB stops working after a while (xhci_hcd :00:14.0: Timeout while
  waiting for setup device command)

Status in System76:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On my laptop the kernel will sometimes drop the USB hub. After this,
  the laptop doesn't recognise any device plugged in to the USB ports -
  plugging and unplugging any device I've tried into any of the USB
  ports produces no response, not even dmesg entries.

  Strangely this also applies to bluetooth - it no longer works once USB
  has dropped (possibly the module is hung of the bus internally).

  Once this has happened only a reboot fixes it; I've not managed to
  find any combination of module unload/reload or suspend cycles to
  reinitialise things correctly.

  Relevant snippet of dmesg:
  [48830.625057] xhci_hcd :00:14.0: Timeout while waiting for setup device 
command
  [48838.079718] xhci_hcd :00:14.0: Stopped the command ring failed, maybe 
the host is dead
  [48838.079742] xhci_hcd :00:14.0: Abort command ring failed
  [48838.079746] xhci_hcd :00:14.0: HC died; cleaning up
  [48838.079770] xhci_hcd :00:14.0: Timeout while waiting for setup device 
command
  [48838.079806] sched: RT throttling activated
  [48838.079981] usb 1-1: USB disconnect, device number 16
  [48838.079985] usb 1-1.2: USB disconnect, device number 18
  [48838.079987] usb 1-1.2.3: USB disconnect, device number 19
  [48838.080285] usb 1-1.2.4: USB disconnect, device number 20
  [48838.111892] usb 1-1.4: USB disconnect, device number 17
  [48838.191292] usb 1-4: USB disconnect, device number 6
  [48838.267550] usb 1-10: USB disconnect, device number 8
  [48838.282968] usb 2-1: device not accepting address 8, error -62
  [48838.282983] usb 2-1: USB disconnect, device number 8
  [48838.282986] usb 2-1.2: USB disconnect, device number 9

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-9-generic 3.18.0-9.10
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  4255 F pulseaudio
   /dev/snd/controlC0:  chris  4255 F pulseaudio
  CRDA:
   country AU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 40), (3, 23), (N/A)
(5250 - 5330 @ 40), (3, 23), (0 ms), DFS
(5735 - 5835 @ 40), (3, 30), (N/A)
  CurrentDesktop: Unity
  Date: Thu Jan 22 12:59:27 2015
  InstallationDate: Installed on 2013-08-06 (533 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System76, Inc. Galago UltraPro
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic.efi.signed 
root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 
init=/lib/systemd/systemd break=mount
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.141
  RfKill:
   1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2013-08-06 (533 days ago)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Galago UltraPro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: galu1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76,

[Kernel-packages] [Bug 1772859] [NEW] Network Manager is not able to manage the devices on Ubuntu 18.04

You have been subscribed to a public bug:

NetworkManager is not able to manage the devices on latest Ubuntu(18.04)
 
---uname output---
Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 s390x 
s390x s390x GNU/Linux
 
Machine Type = z14 s390 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
 1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4).
2. Configure a network device and login to the partition through ssh.
3. Now you can see the following output
root@(none):~# nmcli d s
DEVICE  TYPE  STATE  CONNECTION
eth0ethernet  unmanaged  --
eth1ethernet  unmanaged  --
lo  loopback  unmanaged  --
 
Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el 
s390x 
 
The userspace tool has the following bit modes: 64-bit 

Userspace rpm: NetworkManager --version 1.10.4

Userspace tool obtained from project website:  na 
 

Some more information about the issue:

Network device has been configured manually after the image is up from Support 
Element(SE):
- znetconf -a 
- cat /sys/bus/ccwgroup/drivers/qeth//if_name
- ifconfig   netmask 255.255.255.0
- route add default gw  
- SSH service has been configured

This helped us to login to the Lpar. In Lpar
- output of znetconf -c
Device IDs TypeCard Type  CHPID Drv. Name   
  State

-
0.0.1a80,0.0.1a81,0.0.1a82 1731/01 OSD_10GIG A8 qeth eth0   
  online
0.0.1810,0.0.1811,0.0.1812 1731/01 OSD_1000  D0 qeth eth1   
  online

- output of nmcli c s
root@(none):~# nmcli c s
NAME  UUID  TYPE  DEVICE

- output of nmcli d s
root@(none):~# nmcli d s
DEVICE  TYPE  STATE  CONNECTION
eth0ethernet  unmanaged  --
eth1ethernet  unmanaged  --
lo  loopback  unmanaged  --

* The above output shows that devices are not managed by nmcli

After some investigation we found couple of suggestions like
1. Ubuntu(version <17.04): Creating an empty 
file(/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) and 
restarting NM,
   solved the issue.
   
2. Ubuntu(version 17.10): Copying the said 
file(10-globally-managed-devices.conf) from /usr/lib to /etc/ and modifying the 
   "unmanaged-devices" to none, resolved the issue.

* link for reference: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1638842

For the latest version(18.04), none of the above solutions worked.

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


** Tags: architecture-all bugnameltc-168090 severity-critical 
targetmilestone-inin---
-- 
Network Manager is not able to manage the devices on Ubuntu 18.04
https://bugs.launchpad.net/bugs/1772859
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1483416] Re: laptop keybord light (more\less) shortcuts don't work

2018-05-23 Thread Timo Aaltonen

that's a kernel bug,  and you provided no info.. could be fixed by now

** Package changed: xserver-xorg-input-keyboard (Ubuntu) => linux
(Ubuntu)

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

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

Title:
  laptop keybord light (more\less) shortcuts don't work

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Samsug Series7 laptop NP730UE-S01PL keybord light (more\less)
  shortcuts  fn+F10\F11 don't work

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: compiz-core 1:0.9.12.1+15.10.20150627.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  CasperVersion: 1.362
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Aug 10 21:22:58 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Device [144d:c0e8]
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150808)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 730U3E/740U3E
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  SourcePackage: compiz
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P07ABW.065.140226.dg
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP730U3E-S01PL
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP07ABW.065.140226.dg:bd02/26/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn730U3E/740U3E:pvrP07ABW:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP730U3E-S01PL:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 730U3E/740U3E
  dmi.product.version: P07ABW
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.12.1+15.10.20150627.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.62-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Mon Aug 10 21:05:18 2015
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4931 
   vendor CMN
  xserver.version: 2:1.17.2-1ubuntu3

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

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

[Kernel-packages] [Bug 1764194] Re: Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

2018-05-23 Thread Claudio Castelpietra

Sorry, how can I undo the "fix released" status?

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

Title:
  Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

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

Bug description:
  == SRU Justification ==
  This bug causes a Dell Latitude 5490/5590 with BIOS update 1.1.9 to get a
  black screen at boot. Specifying 'nomodeset' on the kernel command line works
  around the problem.

  Intel resolved the problem in upstream commit a3520b8992e5.  This commit
  is now in mainline as of 4.17.rc2.  It has also been cc'd to upstream
  stable.

  
  == Fix ==
  a3520b8992e5 ("drm/i915/bios: filter out invalid DDC pins from VBT child 
devices")

  == Regression Potential ==
  Low.  This commit was also cc'd to upstream stable, so it recieved
  additional upstream review.


  
  Description:Ubuntu 16.04.4 LTS
  Release:16.04

  Ubuntu 16.04.4 LTS was installed to some Dell Latitude 5490 & 5590
  laptops, originally running BIOS version 1.0.8. The install media and
  the installed OS was running linux-generic-hwe kernel 4.13.0.

  After upgrading BIOS to latest version 1.1.9, the kernel no longer
  boots: right after loading the i915 drm driver, the screen goes black,
  and the machine can only be reset or power cycled. This is true for
  both the installation media, and the OS instance previously installed
  to the disk and updated to the latest hwe kernel 4.13.0-38.

  Specifying 'nomodeset' on the kernel command line works around the
  problem by disabling the i915 drm driver functionality. In that case,
  several display driver function are obviously missing (eg GLX &
  xrandr).

  The problem manifested itself even when using the drm upstream latest 
git-head version. A custom built kernel was used to provide logs for this 
upstream bug report:
  https://bugs.freedesktop.org/show_bug.cgi?id=105549

  The upstream Intel developers provided a patch, which was successfully tested 
by both the original reporter and me.
  https://patchwork.freedesktop.org/patch/216371/
  
https://github.com/freedesktop/drm-tip/commit/f212bf9abe5de9f938fecea7df07046e74052dde

  I backported this fix to ubuntu-xenial hwe git-head, and tested the
  result successfully. I'd like this fix to be added to the ubuntu-
  xenial linux-generic-hwe kernel.

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

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

[Kernel-packages] [Bug 1771679] Re: Kernel panic on boot (m1.small in cn-north-1)

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

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

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

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

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

Title:
  Kernel panic on boot (m1.small in cn-north-1)

Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux-aws source package in Bionic:
  In Progress

Bug description:
  We're observing the following panic on boot when trying to boot an
  m1.small in cn-north-1 (which is a region in AWS China):

  [2.271681] Hardware name: Xen HVM domU, BIOS 3.4.3.amazon 11/11/2016
  [2.271681] RIP: 0010:__xen_evtchn_do_upcall+0x24/0x80
  [2.271681] RSP: :8e21aa003ea0 EFLAGS: 00010046
  [2.271681] RAX: 9dd82920 RBX: ff20 RCX: 
8728b34e
  [2.271681] RDX: 8e21a3252800 RSI: 8e21a724e000 RDI: 
001c
  [2.271681] RBP: 8e21aa003eb8 R08: 9ea05040 R09: 

  [2.271681] R10: 8e21aa003f28 R11:  R12: 
0001
  [2.271681] R13:  R14: 0022 R15: 
8e21a3246900
  [2.271681] FS:  () GS:8e21aa00() 
knlGS:
  [2.271681] CS:  0010 DS:  ES:  CR0: 80050033
  [2.271681] CR2: ff20 CR3: 0b80a000 CR4: 
06f0
  [2.271681] Call Trace:
  [2.271681]  
  [2.271681]  xen_hvm_evtchn_do_upcall+0xe/0x10
  [2.271681]  do_hvm_evtchn_intr+0xe/0x20
  [2.271681]  __handle_irq_event_percpu+0x44/0x1a0
  [2.271681]  handle_irq_event_percpu+0x32/0x80
  [2.271681]  handle_irq_event+0x3b/0x60
  [2.271681]  handle_fasteoi_irq+0x75/0x130
  [2.271681]  handle_irq+0x20/0x30
  [2.271681]  do_IRQ+0x46/0xd0
  [2.271681]  common_interrupt+0x84/0x84
  [2.271681]  
  [2.271681] RIP: 0010:native_safe_halt+0x6/0x10
  [2.271681] RSP: :9ea03e28 EFLAGS: 0246 ORIG_RAX: 
ffdd
  [2.271681] RAX: 9e12fba0 RBX:  RCX: 

  [2.271681] RDX:  RSI:  RDI: 

  [2.271681] RBP: 9ea03e28 R08: 0002 R09: 
9ea03e18
  [2.271681] R10: 9ea03da0 R11: eb8a1d25 R12: 

  [2.271681] R13:  R14:  R15: 

  [2.271681]  ? __cpuidle_text_start+0x8/0x8
  [2.271681]  default_idle+0x20/0x100
  [2.271681]  arch_cpu_idle+0x15/0x20
  [2.271681]  default_idle_call+0x23/0x30
  [2.271681]  do_idle+0x17f/0x1b0
  [2.271681]  cpu_startup_entry+0x73/0x80
  [2.271681]  rest_init+0xae/0xb0
  [2.271681]  start_kernel+0x4dc/0x4fd
  [2.271681]  x86_64_start_reservations+0x24/0x26
  [2.271681]  x86_64_start_kernel+0x74/0x77
  [2.271681]  secondary_startup_64+0xa5/0xb0
  [2.271681] Code: 1f 84 00 00 00 00 00 66 66 66 66 90 55 48 89 e5 41 55 41 
54 53 65 48 8b 1d 92 dc 29 62 41 bc 01 00 00 00 65 44 8b 2d 8c 8c 29 62  03 
00 44 89 e0 65 0f c1 05 2e 96 2a 62 85 c0 75 3b 48 8b 05 
  [2.271681] RIP: __xen_evtchn_do_upcall+0x24/0x80 RSP: 8e21aa003ea0
  [2.271681] CR2: ff20
  [2.271681] ---[ end trace 956d0f4244642614 ]---
  [2.271681] Kernel panic - not syncing: Fatal exception in interrupt

  I've attached the full console log.

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

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

[Kernel-packages] [Bug 1768898] Re: smp_call_function_single/many core hangs with stop4 alone

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

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

Title:
  smp_call_function_single/many core hangs with stop4 alone

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

Bug description:
  == SRU Justification ==
  IBM reports that this bug occurs with stop4 which results in soft lockups/rcu 
stalls.
  This is a kernel synchronization issue leading to a dead lock.

  This bug was introduced by commit 7bc54b652f13 in v4.8-rc1.  This
  regression is fixed by mainline commit c0f7f5b6c6910.

  == Fix ==
  c0f7f5b6c6910 ("cpufreq: powernv: Fix hardlockup due to synchronous smp_call 
in timer interrupt")

  == Regression Potential ==
  Low. Fixes current regression.  Cc'd to upstream stable, so it has had
  additon upstream review.

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


  Recently we discovered this bug occurs just alone with stop4 which
  results in soft lockups/rcu stalls.

  ```
  root@ltc-boston125:~# [15523.619395] systemd[1]: systemd-journald.service: 
Processes still around after final SIGKILL. Entering failed mode.
  [15523.619508] systemd[1]: systemd-journald.service: Failed with result 
'timeout'.
  [15523.619769] systemd[1]: Failed to start Journal Service.
  [15523.620618] systemd[1]: systemd-journald.service: Service has no hold-off 
time, scheduling restart.
  [15523.620774] systemd[1]: systemd-journald.service: Scheduled restart job, 
restart counter is at 21.
  [15523.621462] systemd[1]: Stopped Journal Service.
  [15523.621635] systemd[1]: systemd-journald.service: Found left-over process 
1561 (systemd-journal) in control group while starting unit. Ignoring.
  [15523.621756] systemd[1]: This usually indicates unclean termination of a 
previous run, or service implementation deficiencies.
  [15523.621888] systemd[1]: systemd-journald.service: Found left-over process 
69060 (systemd-journal) in control group while starting unit. Ignoring.
  [15523.622029] systemd[1]: This usually indica[15541.629904] INFO: rcu_sched 
self-detected stall on CPU
  [15541.629958]60-: (2 GPs behind) idle=146/142/0 
softirq=300022/300022 fqs=999069
  [15541.630046] (t=2415546 jiffies g=184827 c=184826 q=57111)
  [15541.630101] NMI backtrace for cpu 60
  [15541.630135] CPU: 60 PID: 4810 Comm: tlbie_test Tainted: G L   
4.15.0-15-generic #16-Ubuntu
  [15541.630207] Call Trace:
  [15541.630232] [c000201a1da96b00] [c0ceb35c] dump_stack+0xb0/0xf4 
(unreliable)
  [15541.630298] [c000201a1da96b40] [c0cf4d48] 
nmi_cpu_backtrace+0x1f8/0x200
  [15541.630363] [c000201a1da96bd0] [c0cf4ee8] 
nmi_trigger_cpumask_backtrace+0x198/0x1f0
  [15541.630429] [c000201a1da96c60] [c002f2d8] 
arch_trigger_cpumask_backtrace+0x28/0x40
  [15541.630495] [c000201a1da96c80] [c01a913c] 
rcu_dump_cpu_stacks+0xf4/0x158
  [15541.630560] [c000201a1da96cd0] [c01a81e8] 
rcu_check_callbacks+0x8e8/0xb40
  [15541.630625] [c000201a1da96e00] [c01b64a8] 
update_process_times+0x48/0x90
  [15541.630689] [c000201a1da96e30] [c01ce1f4] 
tick_sched_handle.isra.5+0x34/0xd0
  [15541.630753] [c000201a1da96e60] [c01ce2f0] 
tick_sched_timer+0x60/0xe0
  [15541.630818] [c000201a1da96ea0] [c01b7054] 
__hrtimer_run_queues+0x144/0x370
  [15541.630883] [c000201a1da96f20] [c01b7fac] 
hrtimer_interrupt+0xfc/0x350
  [15541.630948] [c000201a1da96ff0] [c00248f0] 
__timer_interrupt+0x90/0x260
  [15541.631013] [c000201a1da97040] [c0024d08] timer_interrupt+0x98/0xe0
  [15541.631069] [c000201a1da97070] [c0009014] 
decrementer_common+0x114/0x120
  [15541.631135] --- interrupt: 901 at smp_call_function_single+0x134/0x180
  [15541.631135] LR = smp_call_function_single+0x110/0x180
  [15541.631230] [c000201a1da973d0] [c01d55e0] 
smp_call_function_any+0x180/0x250
  [15541.631294] [c000201a1da97430] [c0acd3e8] 
gpstate_timer_handler+0x1e8/0x580
  [15541.631359] [c000201a1da974e0] [c01b46b0] call_timer_fn+0x50/0x1c0
  [15541.631433] [c000201a1da97560] [c01b4958] expire_timers+0x138/0x1f0
  [15541.631488] [c000201a1da975d0] [c01b4bf8] 
run_timer_softirq+0x1e8/0x270
  [15541.631553] [c000201a1da97670] [c0d0d6c8] __do_softirq+0x158/0x3e4
  [15541.631608] [c000201a1da97750] [c0114be8] irq_exit+0xe8/0x120
  [15541.631663] [c000201a1da97770] [c0024d0c] timer_interrupt+0x9c/0xe0
  [15541.631718] [c000201a1da977a0] [c0009014] 
decrementer_common+0x114/0x120
  [15541.631784] --- interrupt: 901 at smp_call_function_many+0x330/0x450
  [15541.631784]

[Kernel-packages] [Bug 1770770] Re: Switch Build-Depends: transfig to fig2dev

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

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

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

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

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

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

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

Title:
  Switch Build-Depends: transfig to fig2dev

Status in linux package in Ubuntu:
  In Progress
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux-oem package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux source package in Bionic:
  In Progress
Status in linux-aws source package in Bionic:
  Fix Committed
Status in linux-azure source package in Bionic:
  Fix Committed
Status in linux-gcp source package in Bionic:
  Fix Committed
Status in linux-kvm source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  New
Status in linux-raspi2 source package in Bionic:
  New

Bug description:
  [SRU Justification]

  == Impact ==
  We are still depending on a transitional package for transfig.  Switch to the 
real package fig2dev.  This is contributing to NBS in cosmic but is also valid 
in bionic.  We need to bear in mind it is _not_ valid in xenial.

  == Fix ==
  Change the dependency from transfig into fig2dev in the source package 
control file(s).

  == Testcase ==
  This is a build dependency for the architecture independent part, so 
successful build of amd64 is the testing.

  == Regression Potential ==
  Minimal, this affects only build and even there only generating documentation 
files.

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

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

[Kernel-packages] [Bug 1771344] Re: Fix enabling bridge MMIO windows

2018-05-23 Thread Andrew Cloke

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

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

Title:
  Fix enabling bridge MMIO windows

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

Bug description:
  == Comment: #0 - Breno Leitao  
  On boot we save the configuration space of PCIe bridges. We do this so
  when we get an EEH event and everything gets reset that we can restore
  them.
  
  Unfortunately we save this state before we've enabled the MMIO space
  on the bridges. Hence if we have to reset the bridge when we come back
  MMIO is not enabled and we end up taking an PE freeze when the driver
  starts accessing again.
  
  This patch forces the memory/MMIO and bus mastering on when restoring
  bridges on EEH. Ideally we'd do this correctly by saving the
  configuration space writes later, but that will have to come later in
  a larger EEH rewrite. For now we have this simple fix.
  
  The original bug can be triggered on a boston machine by doing:
   echo 0x8000 > 
/sys/kernel/debug/powerpc/PCI0001/err_injct_outbound
  On boston, this PHB has a PCIe switch on it.  Without this patch,
  you'll see two EEH events, 1 expected and 1 the failure we are fixing
  here. The second EEH event causes the anything under the PHB to
  disappear (i.e. the i40e eth).
  
  With this patch, only 1 EEH event occurs and devices properly recover.

  This is commit id 13a83eac373c49c0a081cbcd137e79210fe78acd and should
  be part of Ubuntu 18.04 kernel.

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

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

[Kernel-packages] [Bug 1768948] Re: Hotplugging a SATA disk into a SAS controller may cause crash

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

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

Title:
  Hotplugging a SATA disk into a SAS controller may cause crash

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

Bug description:
  [Impact]
  Hotplugging a SATA disk into a SAS controller may trigger a NULL pointer 
dereference, leading to a crash:

  [ 2366.923208] Unable to handle kernel NULL pointer dereference
  at virtual address 07b8
  ...
  [ 2368.766334] Call trace:
  [ 2368.781712] [] sas_find_dev_by_rphy+0x48/0x118
  [ 2368.800394] [] sas_target_alloc+0x28/0x98
  [ 2368.817975] [] scsi_alloc_target+0x248/0x308
  [ 2368.835570] [] __scsi_add_device+0xb8/0x160
  [ 2368.853034] [] ata_scsi_scan_host+0x190/0x230
  [ 2368.871614] [] ata_scsi_hotplug+0xc8/0xe8
  [ 2368.889152] [] process_one_work+0x164/0x438
  [ 2368.908003] [] worker_thread+0x144/0x4b0
  [ 2368.924613] [] kthread+0xfc/0x110

  [Test Case]
  Unplug a SATA disk from a SAS controller and insert a new SATA disk in its 
place.

  [Fix]
  The ATA_PFLAG_SCSI_HOTPLUG flag is what causes libsas to attempt to handle 
hot add/remove. However, for ata devices on a SAS controller, this should be 
handled by libata. The solution is to not set this flag for ATA devices on a 
SAS controller.

  [Regression Risk]
  The fix is a clean cherry-pick from upstream that is tagged for stable. No 
subsequent patches in linux-next have a "Fixes:" marker referencing this patch, 
suggesting no regressions have been found since its introduction.

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

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

[Kernel-packages] [Bug 1767927] Re: ISST-LTE:pKVM:Ubuntu1804: rcu_sched self-detected stall on CPU follow by CPU ATTEMPT TO RE-ENTER FIRMWARE!

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

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

Title:
  ISST-LTE:pKVM:Ubuntu1804: rcu_sched self-detected stall on CPU follow
  by CPU ATTEMPT TO RE-ENTER FIRMWARE!

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == Comment: #0 - Application Cdeadmin  -
  2018-03-20 14:10:53 ==

  
  == Comment: #1 - Application Cdeadmin  - 2018-03-20 
14:10:54 ==
  == Comment: #2 - Application Cdeadmin  - 2018-03-20 
14:10:56 ==
  --- Comment From dougmill-ibm 2018-03-20 13:51:47 EDT ---
  This problem is not tied to a Linux distro. It will be fixed in firmware, as 
I understand it. Let us close any redundant issues for this same problem. Mark 
them as duplicate.

  == Comment: #3 - Application Cdeadmin  - 2018-03-20 
15:50:54 ==
  --- Comment From mzipse 2018-03-20 15:44:26 EDT ---
  @stewart-ibm @svaidy , I need to you take a first look.  The stop fixes that 
Vaidy had previously highlighted in a recent note are included in the 3/15 PNOR.

  == Comment: #5 - Application Cdeadmin  - 2018-04-04 
16:10:56 ==
  --- Comment From haochanh 2018-04-04 16:04:07 EDT ---
  We update to 0330, bmc=1.18, then we hit bug 1134. Currently we are running 
with disable stop5 but still see the watchdog: hard lockup.
  After 2 hours of test run, I am seeing the "Watchdog: Lockup' and "became 
unstuck"
  
  [Wed Apr  4 13:38:25 2018] Watchdog CPU:42 Hard LOCKUP
  [Wed Apr  4 13:38:25 2018] Modules linked in: vhost_net vhost macvtap macvlan 
tap xfs xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter 
rpcsec_gss_krb5 nfsv4 nfs fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) 
ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload 
esp4 xfrm_algo mlx5_fpga_tools(OE) mlx5_ib(OE) mlx5_core(OE) mlxfw(OE) cxl 
pnv_php mlx4_en(OE) mlx4_ib(OE) ib_core(OE) mlx4_core(OE) devlink 
mlx_compat(OE) kvm_hv kvm binfmt_misc dm_service_time dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua input_leds joydev mac_hid idt_89hpesx ipmi_powernv
  [Wed Apr  4 13:38:25 2018]  vmx_crypto ipmi_devintf at24 ofpart 
uio_pdrv_genirq cmdlinepart uio powernv_flash ipmi_msghandler mtd 
crct10dif_vpmsum opal_prd ibmpowernv nfsd sch_fq_codel auth_rpcgss nfs_acl 
lockd grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress 
raid6_pq ses enclosure scsi_transport_sas hid_generic usbhid hid lpfc ast 
i2c_algo_bit ttm drm_kms_helper nvmet_fc syscopyarea sysfillrect nvmet 
sysimgblt fb_sys_fops nvme_fc nvme_fabrics crc32c_vpmsum drm i40e 
scsi_transport_fc aacraid [last unloaded: mlxfw]
  [Wed Apr  4 13:38:25 2018] CPU: 42 PID: 0 Comm: swapper/42 Tainted: G 
  OE4.15.0-12-generic #13
  [Wed Apr  4 13:38:25 2018] NIP:  c00a3ca4 LR: c00a3ca4 CTR: 
c0008000
  [Wed Apr  4 13:38:25 2018] REGS: c00ff596fc40 TRAP: 0100   Tainted: G 
  OE (4.15.0-12-generic)
  [Wed Apr  4 13:38:25 2018] MSR:  90001033   CR: 
24004482  XER: 2004
  [Wed Apr  4 13:38:25 2018] CFAR: c00ff596fda0 SOFTE: 42
 GPR00: c00a3ca4 c00ff596fda0 
c16eb200 c00ff596fc40
 GPR04: b0001033 c00a3690 
24004484 000ffa45
 GPR08: 0001 c0d10ed8 
00ff 
 GPR12: 90121033 c7a3ce00 
c00ff596ff90 
 GPR16:  c0047840 
c0047810 c11b5380
 GPR20: 0800 c1722484 
002a 
 GPR24: 00a8 0007 
 0007
 GPR28: c161d270 c00ffb666fd8 
c161d528 0007
  [Wed Apr  4 13:38:25 2018] NIP [c00a3ca4] power9_idle_type+0x24/0x40
  [Wed Apr  4 13:38:25 2018] LR [c00a3ca4] power9_idle_type+0x24/0x40
  [Wed Apr  4 13:38:25 2018] Call Trace:
  [Wed Apr  4 13:38:25 2018] [c00ff596fda0] [c00a3ca4] 
power9_idle_type+0x24/0x40 (unreliable)
  [Wed Apr  4 13:38:25 2018] [c00ff596fdc0] [c0ad1240] 
stop_loop+0x40/0x5c
  [Wed Apr  4 13:38:25 2018] [c00ff596fdf0]

[Kernel-packages] [Bug 1765564] Re: fsnotify: Fix fsnotify_mark_connector race

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

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

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

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

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

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

Title:
  fsnotify: Fix fsnotify_mark_connector race

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Invalid
Status in linux-azure package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Invalid
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Committed
Status in linux-azure source package in Artful:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-azure source package in Bionic:
  Fix Released

Bug description:
  On Azure we have had sporadic cases of soft lockups in fsnotify that
  may very well be mitigated by the following fix. The LKML thread is
  "kernel panics with 4.14.X".

  This should be applied to 4.13 and 4.15 versions of the linux-azure
  kernel, and possibly the 4.15 generic kernel in bionic as well.

  -

  fsnotify() acquires a reference to a fsnotify_mark_connector through
  the SRCU-protected pointer to_tell->i_fsnotify_marks. However, it
  appears that no precautions are taken in fsnotify_put_mark() to
  ensure that fsnotify() drops its reference to this
  fsnotify_mark_connector before assigning a value to its 'destroy_next'
  field. This can result in fsnotify_put_mark() assigning a value
  to a connector's 'destroy_next' field right before fsnotify() tries to
  traverse the linked list referenced by the connector's 'list' field.
  Since these two fields are members of the same union, this behavior
  results in a kernel panic.

  This issue is resolved by moving the connector's 'destroy_next' field
  into the object pointer union. This should work since the object pointer
  access is protected by both a spinlock and the value of the 'flags'
  field, and the 'flags' field is cleared while holding the spinlock in
  fsnotify_put_mark() before 'destroy_next' is updated. It shouldn't be
  possible for another thread to accidentally read from the object pointer
  after the 'destroy_next' field is updated.

  The offending behavior here is extremely unlikely; since
  fsnotify_put_mark() removes references to a connector (specifically,
  it ensures that the connector is unreachable from the inode it was
  formerly attached to) before updating its 'destroy_next' field, a
  sizeable chunk of code in fsnotify_put_mark() has to execute in the
  short window between when fsnotify() acquires the connector reference
  and saves the value of its 'list' field. On the HEAD kernel, I've only
  been able to reproduce this by inserting a udelay(1) in fsnotify().
  However, I've been able to reproduce this issue without inserting a
  udelay(1) anywhere on older unmodified release kernels, so I believe
  it's worth fixing at HEAD.

  References: https://bugzilla.kernel.org/show_bug.cgi?id=199437
  Fixes: 08991e83b7286635167bab40927665a90fb00d81
  CC: sta...@vger.kernel.org
  Signed-off-by: Robert Kolchmeyer 
  Signed-off-by: Jan Kara 

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

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

[Kernel-packages] [Bug 1770770] Re: Switch Build-Depends: transfig to fig2dev

** Description changed:

- We are still depending on a transitional package for transfig.  Switch
- to the real package fig2dev.  This is contributing to NBS in cosmic but
- is also valid in bionic.  We need to bear in mind it is _not_ valid in
- xenial.
+ [SRU Justification]
+ 
+ == Impact ==
+ We are still depending on a transitional package for transfig.  Switch to the 
real package fig2dev.  This is contributing to NBS in cosmic but is also valid 
in bionic.  We need to bear in mind it is _not_ valid in xenial.
+ 
+ == Fix ==
+ Change the dependency from transfig into fig2dev in the source package 
control file(s).
+ 
+ == Testcase ==
+ This is a build dependency for the architecture independent part, so 
successful build of amd64 is the testing.
+ 
+ == Regression Potential ==
+ Minimal, this affects only build and even there only generating documentation 
files.

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

** Changed in: linux-aws (Ubuntu Bionic)
   Status: New => Fix Committed

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

** Changed in: linux-azure (Ubuntu Bionic)
   Status: New => Fix Committed

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

** Changed in: linux-gcp (Ubuntu Bionic)
   Status: New => Fix Committed

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

** Changed in: linux-kvm (Ubuntu Bionic)
   Status: New => Fix Committed

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

** Changed in: linux-oem (Ubuntu Bionic)
   Status: New => Fix Committed

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

** Changed in: linux-raspi2 (Ubuntu Bionic)
   Status: New => Fix Committed

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

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

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

Title:
  Switch Build-Depends: transfig to fig2dev

Status in linux package in Ubuntu:
  In Progress
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux-oem package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-aws source package in Bionic:
  Fix Committed
Status in linux-azure source package in Bionic:
  Fix Committed
Status in linux-gcp source package in Bionic:
  Fix Committed
Status in linux-kvm source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Committed
Status in linux-raspi2 source package in Bionic:
  Fix Committed

Bug description:
  [SRU Justification]

  == Impact ==
  We are still depending on a transitional package for transfig.  Switch to the 
real package fig2dev.  This is contributing to NBS in cosmic but is also valid 
in bionic.  We need to bear in mind it is _not_ valid in xenial.

  == Fix ==
  Change the dependency from transfig into fig2dev in the source package 
control file(s).

  == Testcase ==
  This is a build dependency for the architecture independent part, so 
successful build of amd64 is the testing.

  == Regression Potential ==
  Minimal, this affects only build and even there only generating documentation 
files.

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

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

[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake

2018-05-23 Thread David Franko

Oliver & Hans, thank you!

After reverting that patch and applying the other one + resolving the 
conflicts, i can confirm it works  on 4.17.0-rc6 (chuwi lapbook air).
Movement, tap, scroll, left and right button.

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

Title:
  Touchpad stops working after reboot on Apollo Lake

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

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

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

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

[Kernel-packages] [Bug 1770849] Re: Ubuntu 18.04 kernel crashed while in degraded mode

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

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

Title:
  Ubuntu 18.04 kernel crashed while in degraded mode

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

Bug description:
  == SRU Justification ==
  IBM reports a kernel crash with Bionic while in degraded mode(Degraded
  cores).

  IBM created a patch to resolve this bug and has submitted it upstream:
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2018-May/172835.html

  The patch has not landed in mainline as of yet, so it is being submitted
  as a SAUCE patch.

  == Fix ==
  UBUNTU: SAUCE: powerpc/perf: Fix memory allocation for core-imc based on 
num_possible_cpus()

  == Regression Potential ==
  Low.  Limited to powerpc.

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

  kernel crash

  The system is going down NOW!
  Sent SIGTERM to all processes
  Sent SIGKILL to all processes
  [   64.713154] kexec_core: Starting new kernel
  [  156.281504630,5] OPAL: Switch to big-endian OS
  [  158.440263459,5] OPAL: Switch to little-endian OS
  [1.889211] Unable to handle kernel paging request for data at address 
0x678e549df9e2878c
  [1.889289] Faulting instruction address: 0xc038aa30
  [1.889344] Oops: Kernel access of bad area, sig: 11 [#1]
  [1.889386] LE SMP NR_CPUS=2048 NUMA PowerNV
  [1.889432] Modules linked in:
  [1.889468] CPU: 3 PID: 1 Comm: swapper/0 Not tainted 4.15.0-20-generic 
#21-Ubuntu
  [1.889545] NIP:  c038aa30 LR: c038aa1c CTR: 

  [1.889608] REGS: c03fed193840 TRAP: 0380   Not tainted  
(4.15.0-20-generic)
  [1.889670] MSR:  90009033   CR: 28000884 
 XER: 2004
  [1.889742] CFAR: c0016e1c SOFTE: 1
  [1.889742] GPR00: c038a914 c03fed193ac0 c16eae00 
0001
  [1.889742] GPR04: c03fd754c7f8 002c 0001 
002b
  [1.889742] GPR08: 678e549df9e28874   
fffe
  [1.889742] GPR12: 28000888 cfa82100 c000d3b8 

  [1.889742] GPR16:    

  [1.889742] GPR20:    
a78e54a22eb64f8c
  [1.889742] GPR24: c03fd754c800 678e549df9e2878c 0300 
c02bd05c
  [1.889742] GPR28: c03fed01ea00 014080c0 c03fd754c800 
c03fed01ea00
  [1.890286] NIP [c038aa30] kmem_cache_alloc_trace+0x2d0/0x330
  [1.890340] LR [c038aa1c] kmem_cache_alloc_trace+0x2bc/0x330
  [1.890391] Call Trace:
  [1.890416] [c03fed193ac0] [c038a914] 
kmem_cache_alloc_trace+0x1b4/0x330 (unreliable)
  [1.890491] [c03fed193b30] [c02bd05c] pmu_dev_alloc+0x3c/0x170
  [1.890547] [c03fed193bb0] [c10e3210] 
perf_event_sysfs_init+0x8c/0xf0
  [1.890611] [c03fed193c40] [c000d144] 
do_one_initcall+0x64/0x1d0
  [1.890676] [c03fed193d00] [c10b4400] 
kernel_init_freeable+0x280/0x374
  [1.890740] [c03fed193dc0] [c000d3d4] kernel_init+0x24/0x160
  [1.890795] [c03fed193e30] [c000b528] 
ret_from_kernel_thread+0x5c/0xb4
  [1.890857] Instruction dump:
  [1.890909] 7c97ba78 fb210038 38a50001 7f19ba78 fb29 f8aa 4bc8c3f1 
6000
  [1.890978] 7fb8b840 419e0028 e93f0022 e91f0140 <7d59482a> 7d394a14 
7d4a4278 7fa95040
  [1.891050] ---[ end trace 41b3fe7a827f3888 ]---
  [2.900027]
  [3.900175] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b
  [3.900175]
  [4.71868[  175.340944355,5] OPAL: Reboot request...
  2] Rebooting in 10 seconds..

  This fix is needed to resolve the crash

  https://lists.ozlabs.org/pipermail/linuxppc-dev/2018-May/172835.html

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

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

[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension

Please test the kernel here, it fixes the issue for me:
https://people.canonical.com/~khfeng/lp1752772-r8169-intx/

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

Title:
  r8169 ethernet card don't work after returning from suspension

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have noticed that the network stopped working on my desktop after
  I've suspended the system and woke it up. On dmesg there are messages
  like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity: 
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:
   
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
 Mixer name : 'VIA VT1818S'
 Components : 'HDA:11060440,18492818,0010'
 Controls  : 40
 Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 7
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined
 Playback channels: Mono
 Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:
   
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  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:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE: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/1752772/+subscriptions

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

[Kernel-packages] [Bug 1768103] Re: Lancer A0 Asic HBA's won't boot with 18.04

2018-05-23 Thread Vinay Kumar

root@ubuntu18-04:~# uname -a
Linux ubuntu18-04 4.15.0-20-generic #21~lp1768103 SMP Thu May 3 22:29:48 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
root@ubuntu18-04:~#

I think we have booted to correct kernel.

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

Title:
  Lancer A0 Asic HBA's won't boot with 18.04

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

Bug description:
  
  We have discovered that an early asic model (A0) of our 16/32GB HBA's doesn't 
boot with the lpfc driver in Ubuntu 18.04.   

  After further review and discussion, this has been deemed a low risk
  issue since early A0 HBA's were only ever shipped to OEMs for test
  purposes.  These cards were never shipped to end customers.   We have
  been working to replace those cards whenever we discover them.

  We'll leave it up to Canonical to decide whether they want to pull
  this in this single patch to an 18.04 subsequent update.

  Symptom: Ubuntu 18.04 with lpfc driver 12.0.0.0 they can't see LPe16002-M6 
but can see LPe16002B-M6
  Resolution: new lpfc driver patch update. 

  scsi: lpfc: Fix WQ/CQ creation for older asic's.
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=4.18/scsi-queue=83fae8ca4ae09403bfb99542f1aaa292c06cb111

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

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

[Kernel-packages] [Bug 1761751] Re: Black screen on 18.04 + AMD RX460

2018-05-23 Thread semreh

Problem persists in kernel 4.16.11

#uname -r
4.16.11-041611-generic

#ls /sys/class/drm
card0  card0-eDP-1  card0-HDMI-A-1  renderD128  ttm  version

#dmesg | grep drm
[1.783188] [drm] radeon kernel modesetting enabled.
[1.784832] fb: switching to radeondrmfb from EFI VGA
[1.831813] [drm] amdgpu kernel modesetting enabled.
[1.840215] [drm] initializing kernel modesetting (KAVERI 0x1002:0x130A 
0x17AA:0x3988 0x00).
[1.840237] [drm] register mmio base: 0xF0B0
[1.840239] [drm] register mmio size: 262144
[1.865264] [drm] BIOS signature incorrect 0 0
[1.865367] [drm] vm size is 64 GB, 2 levels, block size is 10-bit, fragment 
size is 9-bit
[1.865387] [drm] Detected VRAM RAM=1024M, BAR=1024M
[1.865390] [drm] RAM width 64bits UNKNOWN
[1.865779] [drm] amdgpu: 1024M of VRAM memory ready
[1.865783] [drm] amdgpu: 3072M of GTT memory ready.
[1.865807] [drm] GART: num cpu pages 262144, num gpu pages 262144
[1.865894] [drm] PCIE GART of 1024M enabled (table at 0x00F40004).
[1.866040] [drm] Internal thermal controller without fan control
[1.866046] [drm] amdgpu: dpm initialized
[1.867349] [drm] Found UVD firmware Version: 1.55 Family ID: 9
[1.867789] [drm] Found VCE firmware Version: 50.10 Binary ID: 2
[1.869984] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector 
ObjectID from Adapter Service for connector index:3! type 0 expected 3
[1.870074] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector 
ObjectID from Adapter Service for connector index:4! type 0 expected 3
[1.870200] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector 
ObjectID from Adapter Service for connector index:5! type 0 expected 3
[1.870309] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector 
ObjectID from Adapter Service for connector index:6! type 0 expected 3
[1.884255] [drm] Display Core initialized with v3.1.27!
[1.891240] [drm] SADs count is: -2, don't need to read it
[1.891668] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[1.891674] [drm] Driver supports precise vblank timestamp query.
[1.910078] [drm] UVD initialized successfully.
[2.02] [drm] VCE initialized successfully.
[2.056074] [drm] fb mappable at 0xA042A000
[2.056083] [drm] vram apper at 0xA000
[2.056087] [drm] size 8294400
[2.056090] [drm] fb depth is 24
[2.056093] [drm]pitch is 7680
[2.056218] fbcon: amdgpudrmfb (fb0) is primary device
[2.113975] amdgpu :00:01.0: fb0: amdgpudrmfb frame buffer device
[2.130285] [drm] Initialized amdgpu 3.23.0 20150101 for :00:01.0 on 
minor 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/1761751

Title:
  Black screen on 18.04 + AMD RX460

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

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

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

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

[Kernel-packages] [Bug 1772671] Re: Kernel produces empty lines in /proc/PID/status

2018-05-23 Thread Hajo Locke

Hello,

i installed v4.17-rc6 and this problem seems fixed, no emtpy line in 
/proc/PID/status, but i also miss the line Speculation_Store_Bypass which was 
existing in 4.4.0-127-generic #153-Ubuntu
So may be this is fixed because meltdown/spectre patches are not applied? Iam 
not sure, so i hesitate to set tag kernel-fixed-upstream.
What do you think?

For information: I could not install linux-
headers-4.17.0-041700rc6-generic, there is a dependency to libssl1.1
which is not available currently for xenial.

Thanks

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

Title:
  Kernel produces empty lines in /proc/PID/status

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

Bug description:
  Hello,

  after running updates today to linux-
  image-4.4.0-127-generic_4.4.0-127.153 and rebooting i noticed that
  iotop is not working any more. Reason are empty lines in
  /proc/PID/status, which confuse iotop (and me)

  In new view there is an empy line between Seccomp and
  Speculation_Store_Bypass:

  
  Seccomp:0

  Speculation_Store_Bypass:   vulnerable
  
  Speculation_Store_Bypass seems to be new in /proc/PID/status, may be a 
relation to spectre/meltdown patches.

  iotop is first application which is failing here, but iam afraid of
  more.

  Thanks

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

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

[Kernel-packages] [Bug 1766940] [NEW] Wifi interface does often not show up after reboot

You have been subscribed to a public bug:

Since i got a new laptop (ThinkPad L580) and installed Kubuntu 16.04.4
LTS with kernel 4.13.0-38-generic, i sometimes had to reboot so that the
wifi interface showed up. Once it showed up it worked continuously for
hours without an issue. When the update came to kernel
4.13.0-39-generic, it got worse. Now i have to reboot at least 5 times
until my wifi interface shows up. Once it shows up it works continuously
like on the previous kernel for the whole session but on next reboot the
interface is missing again. It seems random whether the interface is
loaded (or found) when booting. Don't know if this is an kernel issue
but since it got lot worse right after the latest kernel update i assume
so. Wired connections are working well without any issues.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Apr 25 19:16:23 2018
InstallationDate: Installed on 2018-04-16 (9 days ago)
InstallationMedia: Kubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kubuntu xenial
-- 
Wifi interface does often not show up after reboot
https://bugs.launchpad.net/bugs/1766940
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1771188] Re: Ubuntu 18.04 System hangs when logging in or rebooting. Shutdown reboots instead. Suspend wakes after suspending.

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

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

Title:
  Ubuntu 18.04 System hangs when logging in or rebooting.  Shutdown
  reboots instead.  Suspend wakes after suspending.

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Originally I thought the system had crashed when logging in or
  shutdown.  But it turns out it's hanging for about 60-90 seconds.
  When shutting down system will reboot instead.

  lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  uname -a
  Linux bridge 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Clean install.
  Shutting down system reboots instead.
  Suspends does not stay suspended.
  Login and shutdown hangs for a long time (60-90 seconds)

  
  Seeing these in logs.

  [  197.300273] [ cut here ]
  [  197.300274] nouveau :01:00.0: timeout
  [  197.300336] WARNING: CPU: 5 PID: 1938 at 
/build/linux-5s7Xkn/linux-4.15.0/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:207
 gf100_vmm_flush_+0x15c/0x1a0 [nouveau]
  [  197.300336] Modules linked in: msr thunderbolt cmac bnep nouveau ttm arc4 
uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core 
videodev btusb btrtl media btbcm btintel bluetooth ecdh_generic nls_iso8859_1 
ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 
nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG 
xt_limit xt_tcpudp xt_addrtype snd_hda_codec_hdmi hid_multitouch 
snd_hda_codec_realtek dell_smbios_wmi snd_hda_codec_generic dell_wmi 
dell_wmi_descriptor intel_wmi_thunderbolt wmi_bmof mxm_wmi dell_laptop 
dell_smbios_smm dell_smbios dcdbas nf_conntrack_ipv4 nf_defrag_ipv4 
snd_hda_intel xt_conntrack dell_smm_hwmon snd_hda_codec snd_hda_core intel_rapl 
snd_hwdep x86_pkg_temp_thermal intel_powerclamp coretemp snd_pcm kvm_intel kvm 
snd_seq_midi
  [  197.300373]  snd_seq_midi_event irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc snd_rawmidi ath10k_pci snd_seq ath10k_core aesni_intel 
snd_seq_device ath aes_x86_64 snd_timer crypto_simd glue_helper cryptd 
intel_cstate intel_rapl_perf ip6table_filter mac80211 ip6_tables snd 
nf_conntrack_netbios_ns nf_conntrack_broadcast input_leds joydev nf_nat_ftp 
nf_nat serio_raw cfg80211 idma64 rtsx_pci_ms virt_dma nf_conntrack_ftp memstick 
soundcore nf_conntrack mei_me intel_lpss_pci processor_thermal_device 
intel_pch_thermal shpchp mei intel_lpss intel_soc_dts_iosf libcrc32c wmi 
mac_hid int3403_thermal int340x_thermal_zone int3400_thermal intel_hid 
acpi_thermal_rel acpi_pad tpm_crb sparse_keymap sch_fq_codel parport_pc ppdev 
lp parport iptable_filter ip_tables x_tables autofs4 i915 rtsx_pci_sdmmc
  [  197.300397]  i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt 
nvme fb_sys_fops psmouse drm nvme_core rtsx_pci ahci libahci i2c_hid hid video
  [  197.300403] CPU: 5 PID: 1938 Comm: Xorg Tainted: GW
4.15.0-20-generic #21-Ubuntu
  [  197.300404] Hardware name: Dell Inc. XPS 15 9560/05FFDN, BIOS 1.9.4 
04/23/2018
  [  197.300420] RIP: 0010:gf100_vmm_flush_+0x15c/0x1a0 [nouveau]
  [  197.300420] RSP: :b8c0847e7750 EFLAGS: 00010286
  [  197.300421] RAX:  RBX: 980259b63e20 RCX: 
0006
  [  197.300422] RDX: 0007 RSI: 0086 RDI: 
98027e556490
  [  197.300422] RBP: b8c0847e7788 R08: 0001 R09: 
0b9f
  [  197.300423] R10: c0c6c6d0 R11:  R12: 
980258b66c00
  [  197.300423] R13: 98024e9b8d80 R14: 002d78c6d8c0 R15: 
980257106600
  [  197.300424] FS:  7fcbd5229600() GS:98027e54() 
knlGS:
  [  197.300425] CS:  0010 DS:  ES:  CR0: 80050033
  [  197.300426] CR2: 7fcbcb1ed000 CR3: 00085a34c004 CR4: 
003606e0
  [  197.300426] Call Trace:
  [  197.300442]  gp100_vmm_flush+0x17/0x20 [nouveau]
  [  197.300456]  nvkm_vmm_iter.constprop.13+0x2e5/0x880 [nouveau]
  [  197.300470]  ? gp100_vmm_pgt_dma+0x220/0x220 [nouveau]
  [  197.300483]  ? nvkm_vmm_map_choose+0xb0/0xb0 [nouveau]
  [  197.300496]  nvkm_vmm_map+0x21e/0x400 [nouveau]
  [  197.300508]  ? gp100_vmm_pgt_dma+0x220/0x220 [nouveau]
  [  197.300521]  nvkm_vram_map+0x57/0x80 [nouveau]
  [  197.300533]  gf100_mem_map+0xf8/0x180 [nouveau]
  [  197.300546]  nvkm_umem_map+0x6b/0x100 [nouveau]
  [  197.300556]  nvkm_object_map+0x1a/0x30 [nouveau]
  [  197.300565]  nvkm_ioctl_map+0x78/0xe0 [nouveau]
  [  197.300573]  nvkm_ioctl+0x11d/0x280 [nouveau]
  [  197.300590]  nvkm_client_ioctl+0x12/0x20 [nouveau]
  [  197.300597]  nvif_object_ioctl+0x47/0x50 [nouveau]
  [  197.300605]

[Kernel-packages] [Bug 1772154] Re: Unstable WiFi adapter Gigabyte GC-WB867D-I

Can you also try latest firmware, iwlwifi-8265-36.ucode in [1]?

[1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/tree/

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

Title:
  Unstable WiFi adapter Gigabyte GC-WB867D-I

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The WiFi adapter Gigabyte GC-WB867D-I is quite unstable on Ubuntu
  18.04. I do not have data relative to previous versions of Ubuntu
  since this PCIe card is part of a new build that has had 18.04 as the
  first installed version.

  The reason why I can point the finger at the Linux kernel is that the
  card seems to work reliably well on Windows 10 (no packet loss when
  pinging the local router). On Ubuntu 18.04, the card's behaviour seems
  very correlated to the signal strength and exhibits a threshold
  phenomenon. With the antenna placed in an obstacle-free area, some
  ping packets are occasionally lost. But when some objects are placed
  near the antenna (e.g. a phone), the packet loss can get up to 90%.
  Under the very same conditions, the packet loss on Windows is exactly
  0 (and the RTT never gets above 500ms).

  I have disabled the WiFi power saving (changed from 2 to 3) but that
  didn't fix the problem. It seems that restarting the NetworkManager
  service helps for a bit, but after a while the problem resurfaces.

  The card in question has onboard USB Bluetooth and is pretty much an
  M.2 to PCIe x1 adapter for an Intel Wifi adapter. The relevant output
  of lspci is

  03:00.0 Network controller: Intel Corporation Wireless 8265 / 8275
  (rev 78)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 19 10:32:00 2018
  InstallationDate: Installed on 2018-04-29 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D7p:   gabriele   1893 F...m pulseaudio
   /dev/snd/controlC1:  gabriele   1893 F pulseaudio
   /dev/snd/controlC0:  gabriele   1893 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=d2390d6b-2bc3-41bb-b385-3dd8921a36e2
  InstallationDate: Installed on 2018-04-29 (22 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=2e79827f-410a-4aba-ab8f-e278ca6e7aa3 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: B360M Pro4
  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.10:bd03/07/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB360MPro4: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/1772154/+subscriptions

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

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

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

apport-collect 1771188

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

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

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

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

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

Title:
  Ubuntu 18.04 System hangs when logging in or rebooting.  Shutdown
  reboots instead.  Suspend wakes after suspending.

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Originally I thought the system had crashed when logging in or
  shutdown.  But it turns out it's hanging for about 60-90 seconds.
  When shutting down system will reboot instead.

  lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  uname -a
  Linux bridge 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Clean install.
  Shutting down system reboots instead.
  Suspends does not stay suspended.
  Login and shutdown hangs for a long time (60-90 seconds)

  
  Seeing these in logs.

  [  197.300273] [ cut here ]
  [  197.300274] nouveau :01:00.0: timeout
  [  197.300336] WARNING: CPU: 5 PID: 1938 at 
/build/linux-5s7Xkn/linux-4.15.0/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:207
 gf100_vmm_flush_+0x15c/0x1a0 [nouveau]
  [  197.300336] Modules linked in: msr thunderbolt cmac bnep nouveau ttm arc4 
uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core 
videodev btusb btrtl media btbcm btintel bluetooth ecdh_generic nls_iso8859_1 
ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 
nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG 
xt_limit xt_tcpudp xt_addrtype snd_hda_codec_hdmi hid_multitouch 
snd_hda_codec_realtek dell_smbios_wmi snd_hda_codec_generic dell_wmi 
dell_wmi_descriptor intel_wmi_thunderbolt wmi_bmof mxm_wmi dell_laptop 
dell_smbios_smm dell_smbios dcdbas nf_conntrack_ipv4 nf_defrag_ipv4 
snd_hda_intel xt_conntrack dell_smm_hwmon snd_hda_codec snd_hda_core intel_rapl 
snd_hwdep x86_pkg_temp_thermal intel_powerclamp coretemp snd_pcm kvm_intel kvm 
snd_seq_midi
  [  197.300373]  snd_seq_midi_event irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc snd_rawmidi ath10k_pci snd_seq ath10k_core aesni_intel 
snd_seq_device ath aes_x86_64 snd_timer crypto_simd glue_helper cryptd 
intel_cstate intel_rapl_perf ip6table_filter mac80211 ip6_tables snd 
nf_conntrack_netbios_ns nf_conntrack_broadcast input_leds joydev nf_nat_ftp 
nf_nat serio_raw cfg80211 idma64 rtsx_pci_ms virt_dma nf_conntrack_ftp memstick 
soundcore nf_conntrack mei_me intel_lpss_pci processor_thermal_device 
intel_pch_thermal shpchp mei intel_lpss intel_soc_dts_iosf libcrc32c wmi 
mac_hid int3403_thermal int340x_thermal_zone int3400_thermal intel_hid 
acpi_thermal_rel acpi_pad tpm_crb sparse_keymap sch_fq_codel parport_pc ppdev 
lp parport iptable_filter ip_tables x_tables autofs4 i915 rtsx_pci_sdmmc
  [  197.300397]  i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt 
nvme fb_sys_fops psmouse drm nvme_core rtsx_pci ahci libahci i2c_hid hid video
  [  197.300403] CPU: 5 PID: 1938 Comm: Xorg Tainted: GW
4.15.0-20-generic #21-Ubuntu
  [  197.300404] Hardware name: Dell Inc. XPS 15 9560/05FFDN, BIOS 1.9.4 
04/23/2018
  [  197.300420] RIP: 0010:gf100_vmm_flush_+0x15c/0x1a0 [nouveau]
  [  197.300420] RSP: :b8c0847e7750 EFLAGS: 00010286
  [  197.300421] RAX:  RBX: 980259b63e20 RCX: 
0006
  [  197.300422] RDX: 0007 RSI: 0086 RDI: 
98027e556490
  [  197.300422] RBP: b8c0847e7788 R08: 0001 R09: 
0b9f
  [  197.300423] R10: c0c6c6d0 R11:  R12: 
980258b66c00
  [  197.300423] R13: 98024e9b8d80 R14: 002d78c6d8c0 R15: 
980257106600
  [  197.300424] FS:  7fcbd5229600() GS:98027e54() 
knlGS:
  [  197.300425] CS:  0010 DS:  ES:  CR0: 80050033
  [  197.300426] CR2: 7fcbcb1ed000 CR3: 00085a34c004 CR4: 
003606e0
  [  197.300426] Call Trace:
  [  197.300442]  gp100_vmm_flush+0x17/0x20 [nouveau]
  [  197.300456]  nvkm_vmm_iter.constprop.13+0x2e5/0x880 [nouveau]
  [  197.300470]  ? gp100_vmm_pgt_dma+0x220/0x220 [nouveau]
  [  197.300483]  ? nvkm_vmm_map_choose+0xb0/0xb0 [nouveau]
  [  197.300496]

[Kernel-packages] [Bug 1772934] Re: linux-gcp: 4.15.0-1009.9 -proposed tracker

** Summary changed:

- linux-gcp:  -proposed tracker
+ linux-gcp: 4.15.0-1009.9 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

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

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

Title:
  linux-gcp: 4.15.0-1009.9 -proposed tracker

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

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

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

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

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

[Kernel-packages] [Bug 1772682] Re: No sound for Dell Inspiron 5758