date:20190510

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Touchpad and wifi don't

Status in linux package in Ubuntu:
  Expired

Bug description:
  I can't use my touchpad at all and the wifi doesn't work. I tried a
  lot of tutorials but any of them work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  patricio   1561 F pulseaudio
   /dev/snd/controlC0:  patricio   1561 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  7 22:28:14 2019
  InstallationDate: Installed on 2019-01-05 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   enp1s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: TOSHIBA Satellite L45D-C
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=4224aaec-f1b1-49b5-ba77-b3fdf73c1608 ro i8042.reset quiet splash 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 5.00
  dmi.board.asset.tag: *
  dmi.board.name: ACWAE
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: *
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr5.00:bd08/12/2015:svnTOSHIBA:pnSatelliteL45D-C:pvrPSKYNU-006NC1:rvnTOSHIBA:rnACWAE:rvr1.00:cvnTOSHIBA:ct10:cvr*:
  dmi.product.family: *
  dmi.product.name: Satellite L45D-C
  dmi.product.version: PSKYNU-006NC1
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1810130] Re: ic2-HTIX5288

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  ic2-HTIX5288

Status in linux package in Ubuntu:
  Expired

Bug description:
  touchpad not working

  Ubuntu Disco Dingo (development branch)

  WINBOOK 13

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  docmint2172 F pulseaudio
   /dev/snd/controlC1:  docmint2172 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 31 00:55:26 2018
  InstallationDate: Installed on 2018-12-30 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181230)
  MachineType: AXDIA International GmbH WINBOOK 13
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=ea66942b-3d65-4c18-a99e-d02e31358a42 ro recovery nomodeset 
i8042.nomux=1 i8042.reset
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2017
  dmi.bios.vendor: WINBOOK 13
  dmi.bios.version: 1.6
  dmi.board.asset.tag: Default string
  dmi.board.name: K132
  dmi.board.vendor: AXDIA International GmbH
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnWINBOOK13:bvr1.6:bd11/27/2017:svnAXDIAInternationalGmbH:pnWINBOOK13:pvrDefaultstring:rvnAXDIAInternationalGmbH:rnK132:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Notebook
  dmi.product.name: WINBOOK 13
  dmi.product.sku: WINBOOK13-K132-02
  dmi.product.version: Default string
  dmi.sys.vendor: AXDIA International GmbH

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

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

[Kernel-packages] [Bug 1812631] Re: touchpad not working at all

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  touchpad not working at all

Status in linux package in Ubuntu:
  Expired

Bug description:
  I've installed Ubuntu 18.10 on my Toshiba Satellite but doesn't work
  at all, I've tried to fix it without success

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-13-generic 4.18.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jacopo 2337 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 21 11:10:12 2019
  InstallationDate: Installed on 2018-11-14 (67 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: TOSHIBA SATELLITE L50-A-161
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=667b06fb-abbf-4ef1-8656-b3893f3cae89 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.20
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VG10F
  dmi.board.vendor: Intel
  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.20:bd05/15/2013:svnTOSHIBA:pnSATELLITEL50-A-161:pvrPSKJNE-03E00MIT:rvnIntel:rnVG10F:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE L50-A-161
  dmi.product.sku: PSKJNE
  dmi.product.version: PSKJNE-03E00MIT
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1816036] Re: Sound Card not detected.

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Sound Card not detected.

Status in linux package in Ubuntu:
  Expired

Bug description:
  sound card doesnt work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 15 18:06:17 2019
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1018:1006  
   Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: I-Life Digital Technologies LLC ZED AIR
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=8e451b7e-1777-4606-a6af-3218b2a90d72 ro quiet splash 
hid.ignore_special_drivers=1 vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: ilife.Wi314.NANNEBN09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZED AIR
  dmi.board.vendor: I-Life Digital Technologies LLC
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrilife.Wi314.NANNEBN09:bd08/20/2016:svnI-LifeDigitalTechnologiesLLC:pnZEDAIR:pvrV1.00.01:rvnI-LifeDigitalTechnologiesLLC:rnZEDAIR:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: 10.1 Tablet PC
  dmi.product.name: ZED AIR
  dmi.product.version: V1.00.01
  dmi.sys.vendor: I-Life Digital Technologies LLC

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

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

[Kernel-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

2019-05-10 Thread Hui Wang

Then edit /etc/pulse/client.conf, change the line "; extra-arguments =
--log-target=syslog" to "extra-arguments = - --log-
target=file:/tmp/a.txt".

reboot.

you will find the /tmp/a.txt, this is the pulseaaudio log, let us try to
find some clues from the log.

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  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-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1828568] Re: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic

Ah, you mean nomodeset. I have tried that now with both 18.04 and 19.04
with success. Both live USBs are stable for at least 10 minutes.

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

Title:
  Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless
  acpi=off and noapic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Booting an Ubuntu 18.04.2 LTS amd64 installer USB on a Clevo P650RE3
  results in a hang shortly after the desktop is presented, unless
  acpi=off and noapic (or nolapic) are given as kernel boot parameters.
  The same installer runs without issue on other machines and the 16.04
  installer runs without issue on the P650RE3.

  Without passing acpi=off and noapic, a desktop comes up and a terminal
  can be obtained, but keystrokes and mouse clicks are not responded to
  after a small number of seconds. The mouse pointer continues to move
  with trackpad input.

  With careful timing I was able to obtain, uname, dmidecode and (an
  empty) lspci output. I was not able to obtain any /proc/acpi
  information, but do have dmesg. These are all attached. With acpi=off
  and noapic, I can get lspci and dmidecode output, but obviously no
  /proc/acpi. In this case the lspci output is not impty and dmidecode
  is identical to the failing case.

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

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

[Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

2019-05-10 Thread Adrian S.

The issue persists on 19.04.

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in sddm package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in sddm source package in Bionic:
  Confirmed
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

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

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

[Kernel-packages] [Bug 1828568] Re: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic

What magic is required to get into safe graphic mode from the Disco live
USB? (normal boot on that version fails in the same way)

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

Title:
  Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless
  acpi=off and noapic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Booting an Ubuntu 18.04.2 LTS amd64 installer USB on a Clevo P650RE3
  results in a hang shortly after the desktop is presented, unless
  acpi=off and noapic (or nolapic) are given as kernel boot parameters.
  The same installer runs without issue on other machines and the 16.04
  installer runs without issue on the P650RE3.

  Without passing acpi=off and noapic, a desktop comes up and a terminal
  can be obtained, but keystrokes and mouse clicks are not responded to
  after a small number of seconds. The mouse pointer continues to move
  with trackpad input.

  With careful timing I was able to obtain, uname, dmidecode and (an
  empty) lspci output. I was not able to obtain any /proc/acpi
  information, but do have dmesg. These are all attached. With acpi=off
  and noapic, I can get lspci and dmidecode output, but obviously no
  /proc/acpi. In this case the lspci output is not impty and dmidecode
  is identical to the failing case.

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

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

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

--- Comment From leona...@ibm.com 2019-05-10 19:54 EDT---
Hello Juerg,

As this complete list was suggested by Paul, I think he may be the best
person to show the context of the patch series.

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

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

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

[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

2019-05-10 Thread Steve Beattie

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

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

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

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

Title:
  [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

Status in intel:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  This is a bug.

  Test Environment:

  Repro Steps:

  1. Boot up guest using: -cpu Cascadelake-Server

  [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive
  if=virtio,id=hd,file=/home/x/x,format=qcow2  -m 4096 -smp 4 -cpu
  Cascadelake-Server -serial stdio

  char device redirected to /dev/pts/3 (label serial0)

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  2. To check CPU ID related to features[FEAT_7_0_EDX]
  ：CPUID_7_0_EDX_ARCH_CAPABILITIES

  Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be
  1.

  Actual Result:

  Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b
  ecx=0x0818 edx=0xbc00  (EDX bit 29=1)

  Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9
  ecx=0x0818 edx=0x8400 (EDX bit 29=0)

  Commit:2bdb76c015df7125783d8394d6339d181cb5bc30

  Target Kerned: 5.1
  Target Release: 19.10

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

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

[Kernel-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

2019-05-10 Thread Adrian Mariano

I rebooted, ran pactl list cards, ran alsa force reload, then re-ran the
pactl command.  Results was as you predicted.  The pactl outputs before
and after appear below.

Here's the before output:

Card #0
Name: alsa_card.pci-_01_00.1
Driver: module-alsa-card.c
Owner Module: 5
Properties:
alsa.card = "1"
alsa.card_name = "HDA NVidia"
alsa.long_card_name = "HDA NVidia at 0xfe08 irq 17"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:01:00.1"
sysfs.path = 
"/devices/pci:00/:00:01.0/:01:00.1/sound/card1"
device.bus = "pci"
device.vendor.id = "10de"
device.vendor.name = "NVIDIA Corporation"
device.product.id = "0fbc"
device.string = "1"
device.description = "HDA NVidia"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
Profiles:
output:hdmi-stereo: Digital Stereo (HDMI) Output (sinks: 1, 
sources: 0, priority: 5900, available: no)
output:hdmi-surround: Digital Surround 5.1 (HDMI) Output 
(sinks: 1, sources: 0, priority: 800, available: no)
output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output 
(sinks: 1, sources: 0, priority: 800, available: no)
output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output 
(sinks: 1, sources: 0, priority: 5700, available: yes)
output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output 
(sinks: 1, sources: 0, priority: 5700, available: no)
output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) 
Output (sinks: 1, sources: 0, priority: 600, available: no)
output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) 
Output (sinks: 1, sources: 0, priority: 600, available: no)
off: Off (sinks: 0, sources: 0, priority: 0, available: yes)
Active Profile: off
Ports:
hdmi-output-0: HDMI / DisplayPort (priority: 5900, latency 
offset: 0 usec, not available)
Properties:
device.icon_name = "video-display"
Part of profile(s): output:hdmi-stereo, 
output:hdmi-surround, output:hdmi-surround71
hdmi-output-1: HDMI / DisplayPort 2 (priority: 5800, latency 
offset: 0 usec, available)
Properties:
device.icon_name = "video-display"
device.product.name = "DELL U2715H
 "
Part of profile(s): output:hdmi-stereo-extra1
hdmi-output-2: HDMI / DisplayPort 3 (priority: 5700, latency 
offset: 0 usec, not available)
Properties:
device.icon_name = "video-display"
Part of profile(s): output:hdmi-stereo-extra2, 
output:hdmi-surround-extra2, output:hdmi-surround71-extra2


---

Here is the after output:

Card #0
Name: alsa_card.pci-_01_00.1
Driver: module-alsa-card.c
Owner Module: 5
Properties:
alsa.card = "1"
alsa.card_name = "HDA NVidia"
alsa.long_card_name = "HDA NVidia at 0xfe08 irq 17"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:01:00.1"
sysfs.path = 
"/devices/pci:00/:00:01.0/:01:00.1/sound/card1"
device.bus = "pci"
device.vendor.id = "10de"
device.vendor.name = "NVIDIA Corporation"
device.product.id = "0fbc"
device.string = "1"
device.description = "HDA NVidia"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
Profiles:
output:hdmi-stereo: Digital Stereo (HDMI) Output (sinks: 1, 
sources: 0, priority: 5900, available: no)
output:hdmi-surround: Digital Surround 5.1 (HDMI) Output 
(sinks: 1, sources: 0, priority: 800, available: no)
output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output 
(sinks: 1, sources: 0, priority: 800, available: no)
output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output 
(sinks: 1, sources: 0, priority: 5700, available: yes)
output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output 
(sinks: 1, sources: 0, priority: 5700, available: no)
output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) 
Output (sinks: 1, sources: 0, priority: 600, available: no)
output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) 
Output (sinks: 1, sources: 0, priority: 600, available: no)
off:

[Kernel-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

2019-05-10 Thread Adrian Mariano

The before file was attached to the last comment.  Here's the after file
from pactl.

** Attachment added: "postforce"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+attachment/5263010/+files/postforce

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  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-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

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

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

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

This change was made by a bot.

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

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

Title:
  bionic i386 kernel crashes in memory pressure situations

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The linux-image-4.15.0-49-generic (currently in bionic-proposed) can
  be made to crash in a kvm guest with memory pressure. The reproducer
  used is to attempt to run netbeans with openjdk-8-jre installed as the
  only jvm. It will fail to run, and when it fails, it also causes
  gnome-shell to crash. After 3 to 5 repeats of this, the kernel will
  crash with the following oops in dmesg:

  [  545.926175] rfkill: input handler enabled
  [  546.117550] [ cut here ]
  [  546.117552] kernel BUG at 
/build/linux-S9wgEU/linux-4.15.0/arch/x86/mm/fault.c:268!
  [  546.117564] invalid opcode:  [#1] SMP PTI
  [  546.117565] Modules linked in: snd_hda_codec_generic snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep snd_pcm kvm_intel kvm snd_seq_midi 
snd_seq_midi_e
  vent snd_rawmidi irqbypass snd_seq snd_seq_device input_leds joydev snd_timer 
serio_raw snd soundcore qemu_fw_cfg mac_hid binfmt_misc sch_fq_codel ib_iser r
  dma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 
btrfs zstd_compress r
  aid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid crc32_pc
  lmul pcbc qxl ttm drm_kms_helper syscopyarea aesni_intel aes_i586 sysfillrect 
sysimgblt crypto_simd cryptd fb_sys_fops psmouse virtio_blk virtio_net floppy
  drm pata_acpi i2c_piix4
  [  546.117600] CPU: 0 PID: 1335 Comm: Xorg Not tainted 4.15.0-49-generic 
#53-Ubuntu
  [  546.117600] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [  546.117618] EIP: vmalloc_fault+0x229/0x240
  [  546.117618] EFLAGS: 00010086 CPU: 0
  [  546.117619] EAX: 026c EBX: c3e20c50 ECX: f8eb EDX: 
  [  546.117620] ESI: f140 EDI: f800 EBP: eddc1934 ESP: eddc1918
  [  546.117621]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [  546.117621] CR0: 80050033 CR2: f140 CR3: 25f16000 CR4: 001406f0
  [  546.117624] Call Trace:
  [  546.117637]  ? kvm_async_pf_task_wait+0x1b0/0x1b0
  [  546.117638]  __do_page_fault+0x39d/0x510
  [  546.117640]  ? kvm_async_pf_task_wait+0x1b0/0x1b0
  [  546.117641]  do_page_fault+0x27/0xf0
  [  546.117644]  ? kvm_async_pf_task_wait+0x1b0/0x1b0
  [  546.117645]  do_async_page_fault+0x55/0x90
  [  546.117655]  common_exception+0x130/0x136
  [  546.117659] EIP: qxl_image_init+0x338/0x390 [qxl]
  [  546.117659] EFLAGS: 00010286 CPU: 0
  [  546.117660] EAX: fffbb000 EBX: 0fec ECX: fffbb014 EDX: 0030
  [  546.117661] ESI: f140 EDI: fffbb018 EBP: eddc1a18 ESP: eddc19e4
  [  546.117661]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [  546.117663]  ? ioremap_nocache+0x12/0x20
  [  546.117665]  qxl_draw_dirty_fb+0x1cd/0x3d0 [qxl]
  [  546.117668]  qxl_primary_atomic_update+0x159/0x2c0 [qxl]
  [  546.117680]  drm_atomic_helper_commit_planes+0xe8/0x240 [drm_kms_helper]
  [  546.117684]  drm_atomic_helper_commit_tail+0x23/0x50 [drm_kms_helper]
  [  546.117688]  commit_tail+0x5d/0x60 [drm_kms_helper]
  [  546.117691]  drm_atomic_helper_commit+0xf7/0x100 [drm_kms_helper]
  [  546.117695]  ? drm_atomic_helper_setup_commit+0x3f0/0x3f0 [drm_kms_helper]
  [  546.117715]  drm_atomic_commit+0x3f/0x50 [drm]
  [  546.117719]  restore_fbdev_mode_atomic+0x16b/0x1c0 [drm_kms_helper]
  [  546.117723]  restore_fbdev_mode+0x2c/0x150 [drm_kms_helper]
  [  546.117725]  ? _cond_resched+0x17/0x40
  [  546.117729]  drm_fb_helper_restore_fbdev_mode_unlocked.part.32+0x21/0x70 
[drm_kms_helper]
  [  546.117732]  drm_fb_helper_set_par+0x45/0x80 [drm_kms_helper]
  [  546.117743]  fb_set_var+0x1a9/0x440
  [  546.117750]  ? wakeup_preempt_entity+0x73/0x80
  [  546.117752]  ? check_preempt_wakeup+0x108/0x230
  [  546.117753]  ? check_cfs_rq_runtime+0x70/0x70
  [  546.117755]  ? check_preempt_curr+0x27/0x80
  [  546.117757]  ? ttwu_do_wakeup+0x17/0x190
  [  546.117760]  fbcon_blank+0x29e/0x370
  [  546.117772]  ? __switch_to_asm+0x27/0x4c
  [  546.117774]  ? fbcon_cursor+0x1b0/0x1b0
  [  546.117782]  do_unblank_screen+0xaa/0x1b0
  [  546.117784]  vt_ioctl+0x4e3/0x11e0
  [  546.117786]  ? complete_change_console+0xe0/0xe0
  [  546.117788]  tty_ioctl+0xec/0x910
  [  546.117793]  ? jbd2_journal_stop+0xd7/0x3e0
  [  546.117797]  ? ext4_free_inode+0x3c7/0x560
  [  546.117798]  ? ext4_free_inode+0x1f2/0x560
  [  546.117812]  ? intel_pmu_lbr_init_atom+0x46/0x50
  [  546.117819]  ? call_rcu_sched+0x14/0x20
  [  546.117821]  ? tty_vhangup+0x20/0x20
  [  546.117826]  do_vfs_ioctl+0x93/0x6b0
  [  546.117831]  ? destroy_inode+0x34/0x60

[Kernel-packages] [Bug 1828632] Re: bionic i386 kernel crashes in memory pressure situations

2019-05-10 Thread Steve Beattie

In discussing this with Tyler Hicks, he noted that is a somewhat similar
i386 PTI failure report:
https://lore.kernel.org/lkml/14206a19d597881b2490eb3fea47ee97be17ca93.ca...@sympatico.ca/
and that the response to it needs fixes from the tip/x86/mm branch. Is
it possible that the bionic PTI i386 backports are missing some
additional fixes?

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

Title:
  bionic i386 kernel crashes in memory pressure situations

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The linux-image-4.15.0-49-generic (currently in bionic-proposed) can
  be made to crash in a kvm guest with memory pressure. The reproducer
  used is to attempt to run netbeans with openjdk-8-jre installed as the
  only jvm. It will fail to run, and when it fails, it also causes
  gnome-shell to crash. After 3 to 5 repeats of this, the kernel will
  crash with the following oops in dmesg:

  [  545.926175] rfkill: input handler enabled
  [  546.117550] [ cut here ]
  [  546.117552] kernel BUG at 
/build/linux-S9wgEU/linux-4.15.0/arch/x86/mm/fault.c:268!
  [  546.117564] invalid opcode:  [#1] SMP PTI
  [  546.117565] Modules linked in: snd_hda_codec_generic snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep snd_pcm kvm_intel kvm snd_seq_midi 
snd_seq_midi_e
  vent snd_rawmidi irqbypass snd_seq snd_seq_device input_leds joydev snd_timer 
serio_raw snd soundcore qemu_fw_cfg mac_hid binfmt_misc sch_fq_codel ib_iser r
  dma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 
btrfs zstd_compress r
  aid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid crc32_pc
  lmul pcbc qxl ttm drm_kms_helper syscopyarea aesni_intel aes_i586 sysfillrect 
sysimgblt crypto_simd cryptd fb_sys_fops psmouse virtio_blk virtio_net floppy
  drm pata_acpi i2c_piix4
  [  546.117600] CPU: 0 PID: 1335 Comm: Xorg Not tainted 4.15.0-49-generic 
#53-Ubuntu
  [  546.117600] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [  546.117618] EIP: vmalloc_fault+0x229/0x240
  [  546.117618] EFLAGS: 00010086 CPU: 0
  [  546.117619] EAX: 026c EBX: c3e20c50 ECX: f8eb EDX: 
  [  546.117620] ESI: f140 EDI: f800 EBP: eddc1934 ESP: eddc1918
  [  546.117621]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [  546.117621] CR0: 80050033 CR2: f140 CR3: 25f16000 CR4: 001406f0
  [  546.117624] Call Trace:
  [  546.117637]  ? kvm_async_pf_task_wait+0x1b0/0x1b0
  [  546.117638]  __do_page_fault+0x39d/0x510
  [  546.117640]  ? kvm_async_pf_task_wait+0x1b0/0x1b0
  [  546.117641]  do_page_fault+0x27/0xf0
  [  546.117644]  ? kvm_async_pf_task_wait+0x1b0/0x1b0
  [  546.117645]  do_async_page_fault+0x55/0x90
  [  546.117655]  common_exception+0x130/0x136
  [  546.117659] EIP: qxl_image_init+0x338/0x390 [qxl]
  [  546.117659] EFLAGS: 00010286 CPU: 0
  [  546.117660] EAX: fffbb000 EBX: 0fec ECX: fffbb014 EDX: 0030
  [  546.117661] ESI: f140 EDI: fffbb018 EBP: eddc1a18 ESP: eddc19e4
  [  546.117661]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [  546.117663]  ? ioremap_nocache+0x12/0x20
  [  546.117665]  qxl_draw_dirty_fb+0x1cd/0x3d0 [qxl]
  [  546.117668]  qxl_primary_atomic_update+0x159/0x2c0 [qxl]
  [  546.117680]  drm_atomic_helper_commit_planes+0xe8/0x240 [drm_kms_helper]
  [  546.117684]  drm_atomic_helper_commit_tail+0x23/0x50 [drm_kms_helper]
  [  546.117688]  commit_tail+0x5d/0x60 [drm_kms_helper]
  [  546.117691]  drm_atomic_helper_commit+0xf7/0x100 [drm_kms_helper]
  [  546.117695]  ? drm_atomic_helper_setup_commit+0x3f0/0x3f0 [drm_kms_helper]
  [  546.117715]  drm_atomic_commit+0x3f/0x50 [drm]
  [  546.117719]  restore_fbdev_mode_atomic+0x16b/0x1c0 [drm_kms_helper]
  [  546.117723]  restore_fbdev_mode+0x2c/0x150 [drm_kms_helper]
  [  546.117725]  ? _cond_resched+0x17/0x40
  [  546.117729]  drm_fb_helper_restore_fbdev_mode_unlocked.part.32+0x21/0x70 
[drm_kms_helper]
  [  546.117732]  drm_fb_helper_set_par+0x45/0x80 [drm_kms_helper]
  [  546.117743]  fb_set_var+0x1a9/0x440
  [  546.117750]  ? wakeup_preempt_entity+0x73/0x80
  [  546.117752]  ? check_preempt_wakeup+0x108/0x230
  [  546.117753]  ? check_cfs_rq_runtime+0x70/0x70
  [  546.117755]  ? check_preempt_curr+0x27/0x80
  [  546.117757]  ? ttwu_do_wakeup+0x17/0x190
  [  546.117760]  fbcon_blank+0x29e/0x370
  [  546.117772]  ? __switch_to_asm+0x27/0x4c
  [  546.117774]  ? fbcon_cursor+0x1b0/0x1b0
  [  546.117782]  do_unblank_screen+0xaa/0x1b0
  [  546.117784]  vt_ioctl+0x4e3/0x11e0
  [  546.117786]  ? complete_change_console+0xe0/0xe0
  [  546.117788]  tty_ioctl+0xec/0x910
  [  546.117793]  ? jbd2_journal_stop+0xd7/0x3e0
  [  546.117797]  ? ext4_free_inode+0x3c7/0x560
  [  546.117798]  ?

[Kernel-packages] [Bug 1828632] [NEW] bionic i386 kernel crashes in memory pressure situations

2019-05-10 Thread Steve Beattie

Public bug reported:

The linux-image-4.15.0-49-generic (currently in bionic-proposed) can be
made to crash in a kvm guest with memory pressure. The reproducer used
is to attempt to run netbeans with openjdk-8-jre installed as the only
jvm. It will fail to run, and when it fails, it also causes gnome-shell
to crash. After 3 to 5 repeats of this, the kernel will crash with the
following oops in dmesg:

[  545.926175] rfkill: input handler enabled
[  546.117550] [ cut here ]
[  546.117552] kernel BUG at 
/build/linux-S9wgEU/linux-4.15.0/arch/x86/mm/fault.c:268!
[  546.117564] invalid opcode:  [#1] SMP PTI
[  546.117565] Modules linked in: snd_hda_codec_generic snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep snd_pcm kvm_intel kvm snd_seq_midi 
snd_seq_midi_e
vent snd_rawmidi irqbypass snd_seq snd_seq_device input_leds joydev snd_timer 
serio_raw snd soundcore qemu_fw_cfg mac_hid binfmt_misc sch_fq_codel ib_iser r
dma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress r
aid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid crc32_pc
lmul pcbc qxl ttm drm_kms_helper syscopyarea aesni_intel aes_i586 sysfillrect 
sysimgblt crypto_simd cryptd fb_sys_fops psmouse virtio_blk virtio_net floppy
drm pata_acpi i2c_piix4
[  546.117600] CPU: 0 PID: 1335 Comm: Xorg Not tainted 4.15.0-49-generic 
#53-Ubuntu
[  546.117600] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
[  546.117618] EIP: vmalloc_fault+0x229/0x240
[  546.117618] EFLAGS: 00010086 CPU: 0
[  546.117619] EAX: 026c EBX: c3e20c50 ECX: f8eb EDX: 
[  546.117620] ESI: f140 EDI: f800 EBP: eddc1934 ESP: eddc1918
[  546.117621]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[  546.117621] CR0: 80050033 CR2: f140 CR3: 25f16000 CR4: 001406f0
[  546.117624] Call Trace:
[  546.117637]  ? kvm_async_pf_task_wait+0x1b0/0x1b0
[  546.117638]  __do_page_fault+0x39d/0x510
[  546.117640]  ? kvm_async_pf_task_wait+0x1b0/0x1b0
[  546.117641]  do_page_fault+0x27/0xf0
[  546.117644]  ? kvm_async_pf_task_wait+0x1b0/0x1b0
[  546.117645]  do_async_page_fault+0x55/0x90
[  546.117655]  common_exception+0x130/0x136
[  546.117659] EIP: qxl_image_init+0x338/0x390 [qxl]
[  546.117659] EFLAGS: 00010286 CPU: 0
[  546.117660] EAX: fffbb000 EBX: 0fec ECX: fffbb014 EDX: 0030
[  546.117661] ESI: f140 EDI: fffbb018 EBP: eddc1a18 ESP: eddc19e4
[  546.117661]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[  546.117663]  ? ioremap_nocache+0x12/0x20
[  546.117665]  qxl_draw_dirty_fb+0x1cd/0x3d0 [qxl]
[  546.117668]  qxl_primary_atomic_update+0x159/0x2c0 [qxl]
[  546.117680]  drm_atomic_helper_commit_planes+0xe8/0x240 [drm_kms_helper]
[  546.117684]  drm_atomic_helper_commit_tail+0x23/0x50 [drm_kms_helper]
[  546.117688]  commit_tail+0x5d/0x60 [drm_kms_helper]
[  546.117691]  drm_atomic_helper_commit+0xf7/0x100 [drm_kms_helper]
[  546.117695]  ? drm_atomic_helper_setup_commit+0x3f0/0x3f0 [drm_kms_helper]
[  546.117715]  drm_atomic_commit+0x3f/0x50 [drm]
[  546.117719]  restore_fbdev_mode_atomic+0x16b/0x1c0 [drm_kms_helper]
[  546.117723]  restore_fbdev_mode+0x2c/0x150 [drm_kms_helper]
[  546.117725]  ? _cond_resched+0x17/0x40
[  546.117729]  drm_fb_helper_restore_fbdev_mode_unlocked.part.32+0x21/0x70 
[drm_kms_helper]
[  546.117732]  drm_fb_helper_set_par+0x45/0x80 [drm_kms_helper]
[  546.117743]  fb_set_var+0x1a9/0x440
[  546.117750]  ? wakeup_preempt_entity+0x73/0x80
[  546.117752]  ? check_preempt_wakeup+0x108/0x230
[  546.117753]  ? check_cfs_rq_runtime+0x70/0x70
[  546.117755]  ? check_preempt_curr+0x27/0x80
[  546.117757]  ? ttwu_do_wakeup+0x17/0x190
[  546.117760]  fbcon_blank+0x29e/0x370
[  546.117772]  ? __switch_to_asm+0x27/0x4c
[  546.117774]  ? fbcon_cursor+0x1b0/0x1b0
[  546.117782]  do_unblank_screen+0xaa/0x1b0
[  546.117784]  vt_ioctl+0x4e3/0x11e0
[  546.117786]  ? complete_change_console+0xe0/0xe0
[  546.117788]  tty_ioctl+0xec/0x910
[  546.117793]  ? jbd2_journal_stop+0xd7/0x3e0
[  546.117797]  ? ext4_free_inode+0x3c7/0x560
[  546.117798]  ? ext4_free_inode+0x1f2/0x560
[  546.117812]  ? intel_pmu_lbr_init_atom+0x46/0x50
[  546.117819]  ? call_rcu_sched+0x14/0x20
[  546.117821]  ? tty_vhangup+0x20/0x20
[  546.117826]  do_vfs_ioctl+0x93/0x6b0
[  546.117831]  ? destroy_inode+0x34/0x60
[  546.117833]  ? __raw_callee_save___pv_queued_spin_unlock+0x9/0x10
[  546.117834]  ? putname+0x47/0x60
[  546.117836]  ? __fdget+0x12/0x20
[  546.117840]  ? SyS_epoll_ctl+0x5b/0x990
[  546.117841]  ? putname+0x47/0x60
[  546.117844]  ? do_unlinkat+0x7f/0x2c0
[  546.117846]  SyS_ioctl+0x58/0x70
[  546.117848]  do_fast_syscall_32+0x7f/0x1e0
[  546.117850]  entry_SYSENTER_32+0x6b/0xbe
[  546.117860] EIP: 0xb7f9fd09
[  546.117861] EFLAGS: 00200296 CPU: 0
[  546.117861] EAX: ffda EBX: 000b ECX: 4b3a

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

--- Comment From mranw...@us.ibm.com 2019-05-10 17:33 EDT---
>From the opal-utils package can you try:  sudo opal-gard list?  I think if 
>there's something there you can use opal-gard show to get more details.

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

Title:
  Unable to put offline CPU back online on Bionic/B-hwe-edge P9

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

Bug description:
  You will see these CPUs in offline state after boot.

  ubuntu@baltar:~$ cat /sys/devices/system/cpu/offline
  156-159

  ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu156/online
  1
  tee: /sys/devices/system/cpu/cpu156/online: Invalid argument
  ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu157/online
  1
  tee: /sys/devices/system/cpu/cpu157/online: Invalid argument
  ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu158/online
  1
  tee: /sys/devices/system/cpu/cpu158/online: Invalid argument
  ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu159/online
  1
  tee: /sys/devices/system/cpu/cpu159/online: Invalid argument

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-14-generic 5.0.0-14.15~18.04.1+signed1
  ProcVersionSignature: Ubuntu 5.0.0-14.15~18.04.1-generic 5.0.6
  Uname: Linux 5.0.0-14-generic ppc64le
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: ppc64el
  Date: Thu May  2 06:46:36 2019
  ProcLoadAvg: 0.00 0.00 0.00 1/1298 6496
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 5.0.0-14-generic (buildd@bos02-ppc64el-014) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #15~18.04.1-Ubuntu SMP Thu Apr 25 
18:55:27 UTC 2019
  SourcePackage: linux-signed-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 40
  cpu_coreson: Number of cores online = 39
  cpu_dscr: DSCR is 16
  cpu_freq:
   min: 2.862 GHz (cpu 79)
   max: 2.945 GHz (cpu 81)
   avg: 2.903 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=4

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

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

[Kernel-packages] [Bug 1783906] Re: Linux 4.15 and onwards fails to initialize some hard drives

2019-05-10 Thread David Milburn

Ok thanks, please look at this some more, I will try to get back with
you soon.

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

Title:
  Linux 4.15 and onwards fails to initialize some hard drives

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

Bug description:
  I have two hard drives, the main hard drive is a TOSHIBA DT01ACA200
  the second backup hard drive is a Western Digital WD5003AZEX. I
  installed lubuntu 18.04.1 on the Toshiba HDD and it boots just fine,
  the issue is with the second hard drive, when installing the WD HDD
  wouldn't even come as an option to install, and after boot the WD HDD
  still wouldn't come up, this is the dmesg with the stock kernel (4.15)
  https://paste.ubuntu.com/p/kpxh94v2SK/

  ata6 is the WD HDD that refuses to work. The messages:
  [  302.107650] ata6: SError: { CommWake 10B8B Dispar DevExch }
  [  302.107658] ata6: hard resetting link
  [  307.860291] ata6: link is slow to respond, please be patient (ready=0)
  [  312.120898] ata6: COMRESET failed (errno=-16)
  [  363.445120] INFO: task kworker/u8:5:201 blocked for more than 120 seconds.
  [  363.445131]   Not tainted 4.15.0-29-generic #31-Ubuntu
  [  363.445135] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.445140] kworker/u8:5D0   201  2 0x8000
  [  363.445155] Workqueue: events_unbound async_run_entry_fn
  [  363.445157] Call Trace:
  [  363.445171]  __schedule+0x291/0x8a0
  [  363.445177]  schedule+0x2c/0x80
  [  363.445182]  ata_port_wait_eh+0x7c/0xf0
  [  363.445186]  ? wait_woken+0x80/0x80
  [  363.445189]  ata_port_probe+0x28/0x40
  [  363.445192]  async_port_probe+0x2e/0x52
  [  363.445196]  async_run_entry_fn+0x3c/0x150
  [  363.445199]  process_one_work+0x1de/0x410
  [  363.445203]  worker_thread+0x32/0x410
  [  363.445207]  kthread+0x121/0x140
  [  363.445210]  ? process_one_work+0x410/0x410
  [  363.445214]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  363.445218]  ret_from_fork+0x22/0x40

  Repeat constantly. Also when I try to turn off the computer, the
  computer seem to freeze, the lights of the keyboard and mouse turn off
  and the computer just stay on.

  I tried Tiny Core 9.0 which has linux 4.14.10, and i didn't had this
  issue, i also installed linux 4.14 on this lubuntu 18.04 using Ukuu
  Kernel Update Utility. And with this kernel version, or any previous
  version the WD HDD does work again. Here's a dmesg of lubuntu 18.04
  with linux 4.14 and the WD HDD finally coming up at the end:
  https://paste.ubuntu.com/p/Gd3cGFbjTJ/

  Also tried with with linux 4.17 but the WD HDD would also refuse to
  work on this version. Here's another dmesg with this version:
  https://paste.ubuntu.com/p/PmNn96vZZv/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-29-generic 4.15.0-29.31
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-29-generic.
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  testtest756 F pulseaudio
   /dev/snd/controlC1:  testtest756 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'NVidia_1'/'HDA NVidia at 0xfe02 irq 22'
 Mixer name : 'Realtek ALC1200'
 Components : 'HDA:10ec0888,10ec,00100101 
HDA:10de0002,10de0101,0010'
 Controls  : 56
 Simple ctrls  : 21
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xfcffc000 irq 16'
 Mixer name : 'Nvidia GPU 42 HDMI/DP'
 Components : 'HDA:10de0042,38422651,00100100'
 Controls  : 21
 Simple ctrls  : 3
  CurrentDesktop: LXDE
  Date: Thu Jul 26 17:10:58 2018
  HibernationDevice: RESUME=UUID=17e70869-516d-4b63-b900-e92e3c4b73b6
  InstallationDate: Installed on 2018-07-26 (0 days ago)
  InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: 113 1
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=71cf0a32-7827-49be-a2c0-cd50a72c26a1 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: 113-M2-E113
  dmi.board.vendor: EVGA
  dmi.board.version: 1
  dmi.chassis.asset.tag: Unknow
  dmi.chassis.type: 3
  dmi.chassis.vendor: EVGA

[Kernel-packages] [Bug 1828578] Re: dell xps 9570 wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS

Does any of the linux-firmware supports these killer wifi driver ?
http://mirrors.edge.kernel.org/ubuntu/pool/main/l/linux-firmware/

Issue:- Intermittently reconnection / sometime freezing issue. Mostly
seeing this in home network.

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

Title:
  dell xps 9570 wifi reconnection issue followed by freeze + Ubuntu
  18.04.2 LTS

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello Team,

  Env - Dell XPS 9570
Ubuntu 18.04.2 , HWE kernel

  We are facing intermittently wifi reconnection issue on Ubuntu 18.04.
  Software upgrade is up-to date. Also some time we facing freezing
  issue due to this hard reset required to make machine back to normal.

  Please let me know if there are any known issue with this particular
  model on 18.04 ? Please let me know.

  Thanks
  Jay

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

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

[Kernel-packages] [Bug 1828578] Re: dell xps 9570 wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS

Does this kernel supports  Killer 1435, 1435s and 1535 wireless cards ?

>> linux-image-generic-hwe-18.04  = 4.18.0.17.67

Or support for this wifi cards available in 5.x kernel, please specify.

Note:- As per killer networking, they haven't mentioned about 18.04 
https://support.killernetworking.com/knowledge-base/installing-the-killer-1535-1525-1435-in-ubuntu-debian/
 

Please confirm which linux-firmware supports this driver?

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

Title:
  dell xps 9570 wifi reconnection issue followed by freeze + Ubuntu
  18.04.2 LTS

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello Team,

  Env - Dell XPS 9570
Ubuntu 18.04.2 , HWE kernel

  We are facing intermittently wifi reconnection issue on Ubuntu 18.04.
  Software upgrade is up-to date. Also some time we facing freezing
  issue due to this hard reset required to make machine back to normal.

  Please let me know if there are any known issue with this particular
  model on 18.04 ? Please let me know.

  Thanks
  Jay

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

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

[Kernel-packages] [Bug 1828597] Re: KDump boot fails with nr_cpus=1

Okay, let's consider this option on makedumpfile side. I'll test it and
provide a test package by next week.

Cascardo.

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

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

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

** Changed in: makedumpfile (Ubuntu Eoan)
 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 kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1828597

Title:
  KDump boot fails with nr_cpus=1

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  Confirmed
Status in kexec-tools source package in Cosmic:
  Invalid
Status in linux source package in Cosmic:
  Confirmed
Status in makedumpfile source package in Cosmic:
  New
Status in kexec-tools source package in Disco:
  Invalid
Status in linux source package in Disco:
  Confirmed
Status in makedumpfile source package in Disco:
  New
Status in kexec-tools source package in Eoan:
  Invalid
Status in linux source package in Eoan:
  Confirmed
Status in makedumpfile source package in Eoan:
  Confirmed

Bug description:
  == Comment: #0 - Hari Krishna Bathini  - 2019-05-10 06:38:21 ==

  ---Problem Description---
  kdump boots fails in some environments when nr_cpus=1 is passed 
   
  ---uname output---
  na
   
  Machine Type = na 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. configure kdump
  2. trigger crash on non-boot cpu

  Expected result:
  Capture dump and reboot

  Actual result:
  Hang in early kdump boot process after crash
   
  Userspace tool common name: kdump-tools 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: kdump-tools

  Userspace tool obtained from project website:  na

  == Comment: #1 - Hari Krishna Bathini - 2019-05-10 06:45:46 ==
  Launchpad bug 1560552 added "nr_cpus=1" support on ppc64 though
  this change never made it upstream as maintainer has a few apprehensions..

  With 4.18 kernels, this change is dropped on Ubuntu kernels too.
  With nr_cpus=1 support in kernel, kdump-tools was also updated to
  use "nr_cpsu=1" by default instead of "maxcpus=1" (see launchpad
  bug 1568952). This kdump-tools change has to be reverted to make
  it consist with the kernel change. Note that "nr_cpus=1 change had
  a issues in kdump guest environment even with "nr_cpus=1" support
  for kdump in kernel. So, even not withstanding the kernel revert, it is
  better to default to "maxcpus=1" on all kernel versions. So, please
  revert the kdump-tools fix that went in with launchpad bug 1568952

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

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

[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

2019-05-10 Thread pragyansri.pa...@intel.com

List of commits needed to enable ARCH_CAPABILITIES:

Kernel:
commit 2bdb76c015df7125783d8394d6339d181cb5bc30
Author: Xiaoyao Li 
Date:   Fri Mar 8 15:57:20 2019 +0800
kvm/x86: Move MSR_IA32_ARCH_CAPABILITIES to array emulated_msrs
 
QEMU:
 
commit 014018e19b3c54dd1bf5072bc912ceffea40abe8
Author: Eduardo Habkost 
Date:   Fri Jan 25 20:06:06 2019 -0200
   i386: Make arch_capabilities migratable
 
commit 485b1d256bcb0874bcde0223727c159b6837e6f8
Author: Eduardo Habkost 
Date:   Fri Jan 25 20:06:05 2019 -0200
   i386: kvm: Disable arch_capabilities if MSR can't be set
 
commit b0a1980384fc265d91de7e09aa5fe531a69e6288
Author: Tao Xu 
Date:   Thu Dec 27 10:43:03 2018 +0800
   i386: Update stepping of Cascadelake-Server
 
commit aec5e9c3a94cf8b7920f59bef69a6f426092c4a0
Author: Bandan Das 
Date:   Sun Nov 25 23:17:28 2018 -0500
   kvm: Use KVM_GET_MSR_INDEX_LIST for MSR_IA32_ARCH_CAPABILITIES support
 
commit 07585923485952bf4cb7da563c9f91fecc85d09c
Author: Robert Hoo 
Date:   Mon Oct 15 12:47:24 2018 +0800
   x86: Data structure changes to support MSR based features
 
commit f57bceb6ab5163ddd6c41ff4344ab8cf28a9c63d
Author: Robert Hoo 
Date:   Mon Oct 15 12:47:23 2018 +0800
   kvm: Add support to KVM_GET_MSR_FEATURE_INDEX_LIST and KVM_GET_MSRS system 
ioctl
 
commit d86f963694df27f11b3681ffd225c9362de1b634
Author: Robert Hoo 
Date:   Mon Oct 15 12:47:25 2018 +0800
   x86: define a new MSR based feature word – FEATURE_WORDS_ARCH_CAPABILITIES
 
commit c7a88b52f62b30c04158eeb07f73e3f72221b6a8
Author: Tao Xu 
Date:   Wed Sep 19 11:11:22 2018 +0800
   i386: Add new model of Cascadelake-Server
 
commit 3fc7c73139d2d38ae80c3b0bc963b1ac1555924c
Author: Robert Hoo 
Date:   Thu Jul 5 17:09:55 2018 +0800
   i386: Add CPUID bit and feature words for IA32_ARCH_CAPABILITIES MSR
 
commit 8a11c62da9146dd89aee98947e6bd831e65a970d
Author: Robert Hoo 
Date:   Thu Jul 5 17:09:58 2018 +0800
   i386: Add new CPU model Icelake-{Server,Client}
 
commit 8c80c99fcceabd0708a5a83f08577e778c9419f5
Author: Robert Hoo 
Date:   Thu Jul 5 17:09:54 2018 +0800
   i386: Add new MSR indices for IA32_PRED_CMD and IA32_ARCH_CAPABILITIES

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

Title:
  [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

Status in intel:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a bug.

  Test Environment:

  Repro Steps:

  1. Boot up guest using: -cpu Cascadelake-Server

  [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive
  if=virtio,id=hd,file=/home/x/x,format=qcow2  -m 4096 -smp 4 -cpu
  Cascadelake-Server -serial stdio

  char device redirected to /dev/pts/3 (label serial0)

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  2. To check CPU ID related to features[FEAT_7_0_EDX]
  ：CPUID_7_0_EDX_ARCH_CAPABILITIES

  Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be
  1.

  Actual Result:

  Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b
  ecx=0x0818 edx=0xbc00  (EDX bit 29=1)

  Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9
  ecx=0x0818 edx=0x8400 (EDX bit 29=0)

  Commit:2bdb76c015df7125783d8394d6339d181cb5bc30

  Target Kerned: 5.1
  Target Release: 19.10

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

-- 
Mailing list: https://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 1785715] Re: ubuntu hynix ssd I/O Errors after some minutes

2019-05-10 Thread Revisor

Sorry, i forgot to report back. Thank you for asking.

No, i got my SSD replaced by a new one and now it is all good.
Seems like it has been a hardware-related problem.

Am 10.05.2019 um 17:26 schrieb Kai-Heng Feng:
> Do you still see this bug?
>

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

Title:
  ubuntu hynix ssd I/O Errors after some minutes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Maybe similar to Bug 1678184
  Im working on ubuntu 18.04 (with Kernel 4.15.0-29-generic) on a dell XPS 
15-9560
  After 20 - 180 Minutes the graphical interface hangs up (i can switch 
workspaces, but not much else) and entering commands like "ls" yields bash: 
input/output error
  Reboot is impossible via the command or the button. Short click on power 
button gives me a TTY like view prompting errors for nvme0 ext4 file system 
errors (i will post more exact text on next hangup)

  The hangups appear randomly, but often during shutting the lid or plugging in 
power cable, which makes me thing it might be something with ssd power states.
  For that reason i added grub parameters like 
"nvme_core.default_ps_max_latency_us=3000" (see Bug 1678184) and ended up fully 
disabling APST by setting it to 0, but the bug still occured.

  sudo nvme id-ctrl /dev/nvme0 yields:
  NVME Identify Controller:
  vid : 0x1c5c
  ssvid   : 0x1c5c
  sn  : EJ75N621210105PBR   
  mn  : PC300 NVMe SK hynix 1TB 
  fr  : 20005A00
  rab : 1
  ieee: ace42e
  cmic: 0
  mdts: 5
  cntlid  : 0
  ver : 10200
  rtd3r   : 90f560
  rtd3e   : ea60
  oaes: 0
  ctratt  : 0
  oacs: 0x16
  acl : 3
  aerl: 3
  frmw: 0x16
  lpa : 0x2
  elpe: 254
  npss: 4
  avscc   : 0x1
  apsta   : 0x1
  wctemp  : 361
  cctemp  : 363
  mtfa: 0
  hmpre   : 0
  hmmin   : 0
  tnvmcap : 0
  unvmcap : 0
  rpmbs   : 0
  edstt   : 60
  dsto: 1
  fwug: 0
  kas : 0
  hctma   : 0
  mntmt   : 0
  mxtmt   : 0
  sanicap : 0
  hmminds : 0
  hmmaxd  : 0
  sqes: 0x66
  cqes: 0x44
  maxcmd  : 0
  nn  : 1
  oncs: 0x1e
  fuses   : 0
  fna : 0
  vwc : 0x1
  awun: 255
  awupf   : 0
  nvscc   : 1
  acwu: 0
  sgls: 0
  subnqn  : 
  ioccsz  : 0
  iorcsz  : 0
  icdoff  : 0
  ctrattr : 0
  msdbd   : 0
  ps0 : mp:5.87W operational enlat:5 exlat:5 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
  ps1 : mp:2.40W operational enlat:30 exlat:30 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
  ps2 : mp:1.90W operational enlat:100 exlat:100 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
  ps3 : mp:0.1000W non-operational enlat:1000 exlat:1000 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
  ps4 : mp:0.0060W non-operational enlat:1000 exlat:5000 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-

  
  sudo nvme get-feature -f 0x0c -H /dev/nvme0 yields:
  get-feature:0xc (Autonomous Power State Transition), Current value:
Autonomous Power State Transition Enable (APSTE): Disabled
Auto PST Entries.
Entry[ 0]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 1]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
... and so on ...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  revisor1593 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1bc0493d-0592-40d4-b0f4-938fbe12a990
  InstallationDate: Installed on 2018-07-12 (25 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 003: ID 04f3:24a1 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=70377f6e-8c1c-4316-bded-c738410879ab ro quiet splash 
nvme_core.default_ps_max_latency_us=0 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux

[Kernel-packages] [Bug 1828592] Re: Duplicate entry Exec and Path in scripts.

2019-05-10 Thread J.G.

Removed symbolic links: 
/usr/share/pykaraoke/fonts/DejaVuSans.ttf
/usr/share/pykaraoke/fonts/DejaVuSansCondensed.ttf
/usr/share/pykaraoke/fonts/DejaVuSansCondensed-Bold.ttf

Copyed instead fonts in /usr/share/pykaraoke/fonts/

Works fine.


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

** Summary changed:

- Duplicate entry Exec and Path in scripts. 
+ pykaraoke wont read fonts

** Changed in: pykaraoke (Ubuntu)
   Status: Incomplete => Fix Committed

** Changed in: pykaraoke (Ubuntu)
   Status: Fix Committed => Opinion

** Changed in: pykaraoke (Ubuntu)
 Assignee: (unassigned) => J.G. (j.gorski)

** Summary changed:

- pykaraoke wont read fonts
+ pykaraoke won't read fonts

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

Title:
  pykaraoke won't read fonts

Status in pykaraoke package in Ubuntu:
  Opinion

Bug description:
  Dear,
  i was making a executable icon for pykaraoke_mini.py downloaded from 
github.com.
  I noticed that in order to make executable work i was needed to put both full 
path to python executable in Exec variable and Path variable. In oder case the 
executable doesnt work.

  Example:
  [Desktop Entry]
  Name=pyKaraoke mini
  Version=0.75
  Exec=~/pykaraoke-master/pykaraoke_mini.py
  Terminal=false
  Type=Application
  Path=~/pykaraoke-master/

  I was questioning it, because the pykaraoke deb packet seems to be not 
working.
  The reason that pykaraoke doesn't want to play karaoke (.kar and .mid files) 
is when i run it from terminal it gives me error message:

  
  unable to read font filename

  so i guessed that python also can't find the path to the fonts used in
  playing karaoke files in pykaraoke binary.

  I maked a test by editing pykaraoke_mini.py lines:
  font = pygame.font.Font(os.path.join(manager.FontPath, 
"DejaVuSansCondensed-Bold.ttf"), 12)

  self.thinFont = pygame.font.Font(os.path.join(manager.FontPath,
  "DejaVuSansCondensed.ttf"),

  self.boldFont = pygame.font.Font(os.path.join(manager.FontPath,
  "DejaVuSansCondensed-Bold.ttf"), fontSize)

  self.titleFont = pygame.font.Font(os.path.join(manager.FontPath,
  "DejaVuSansCondensed-Bold.ttf"), fontSize)

  and

  self.subtitleFont = pygame.font.Font(os.path.join(manager.FontPath,
  "DejaVuSansCondensed.ttf"), fontSize)

  by putting a full path to the selected fonts, by example:
  manager.FontPath, 
"/usr/share/fonts/truetype/dejavu/DejaVuSansCondensed-Bold.ttf"

  and pykaraoke_mini.py executed with no errors, but it didn't want to
  play again because i think there are needed to be full paths entered
  in other portions of the code, in order to make pykaraoke function
  properly.

  So i maked a conclusion that this is a linux bug.

  Am i right or wrong?

  Thank you,
  greetings,
  Igor

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

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

[Kernel-packages] [Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600

2019-05-10 Thread Timo Jyrinki

Being fixed in upstream
https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-
next-5.2=2e26ccb119bde03584be53406bbd22e711b0d6e6

Maybe a candidate for SRUs too after the fix hits eoan (19.10).

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

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

Title:
  ubuntu 18.04 flickering screen with Radeon X1600

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

Bug description:
  my laptop: HP Compaq nx9420
  my grafic card: 
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller])

  attachment:
  the bug-apport-file

  Description:
  I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode;
  -> as soon as the kernel-module radeon.ko is loaded the screen starts 
flickering
  when starting the grafic-mode the flickering continues; so the screen is 
unusable.

  when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the 
screen does not flicker
  but the resolution is limited to 1400x1050 (instead of natural 1680x1050)
  so I can not use this as work-around

  when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157)
  the screen is o.k. NO flickering in textmode, nice grafic, NO flickering 
  xrandr tells: 1680x1050 60.1

  so I must stay on old ubuntu 14.04.05 ???

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

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

[Kernel-packages] [Bug 1828597] Re: KDump boot fails with nr_cpus=1

2019-05-10 Thread Frank Heimes

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

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

Title:
  KDump boot fails with nr_cpus=1

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in kexec-tools source package in Cosmic:
  Invalid
Status in linux source package in Cosmic:
  Confirmed
Status in kexec-tools source package in Disco:
  Invalid
Status in linux source package in Disco:
  Confirmed
Status in kexec-tools source package in Eoan:
  Invalid
Status in linux source package in Eoan:
  Confirmed

Bug description:
  == Comment: #0 - Hari Krishna Bathini  - 2019-05-10 06:38:21 ==

  ---Problem Description---
  kdump boots fails in some environments when nr_cpus=1 is passed 
   
  ---uname output---
  na
   
  Machine Type = na 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. configure kdump
  2. trigger crash on non-boot cpu

  Expected result:
  Capture dump and reboot

  Actual result:
  Hang in early kdump boot process after crash
   
  Userspace tool common name: kdump-tools 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: kdump-tools

  Userspace tool obtained from project website:  na

  == Comment: #1 - Hari Krishna Bathini - 2019-05-10 06:45:46 ==
  Launchpad bug 1560552 added "nr_cpus=1" support on ppc64 though
  this change never made it upstream as maintainer has a few apprehensions..

  With 4.18 kernels, this change is dropped on Ubuntu kernels too.
  With nr_cpus=1 support in kernel, kdump-tools was also updated to
  use "nr_cpsu=1" by default instead of "maxcpus=1" (see launchpad
  bug 1568952). This kdump-tools change has to be reverted to make
  it consist with the kernel change. Note that "nr_cpus=1 change had
  a issues in kdump guest environment even with "nr_cpus=1" support
  for kdump in kernel. So, even not withstanding the kernel revert, it is
  better to default to "maxcpus=1" on all kernel versions. So, please
  revert the kdump-tools fix that went in with launchpad bug 1568952

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

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

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

--- Comment From hbath...@in.ibm.com 2019-05-10 13:25 EDT---
Right, Cascardo.

nr_cpus=1 for KDump case has never worked before on ppc64. Mahesh
tried fixing it but the maintainer had a few apprensions and rightly so.
This fix doesn't work in all cases. Say, KVM host (baremetal with SMT off)..

So, to start with, "nr_cpus=1" as default parameter instead of "maxcpus=1"
for KDump kernel on ppc64, even with the kernel fix from Mahes was not a
good idea, as it was not something that works always...

IMHO, with no alternate and foolproof way to fix this in discussion yet, we can
save the "nr_cpus=1" option as default for another day and stick with
"maxcpus=1" for now. That was the intention behind this bug..

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

Title:
  KDump boot fails with nr_cpus=1

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in kexec-tools source package in Cosmic:
  Invalid
Status in linux source package in Cosmic:
  Confirmed
Status in kexec-tools source package in Disco:
  Invalid
Status in linux source package in Disco:
  Confirmed
Status in kexec-tools source package in Eoan:
  Invalid
Status in linux source package in Eoan:
  Confirmed

Bug description:
  == Comment: #0 - Hari Krishna Bathini  - 2019-05-10 06:38:21 ==

  ---Problem Description---
  kdump boots fails in some environments when nr_cpus=1 is passed 
   
  ---uname output---
  na
   
  Machine Type = na 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. configure kdump
  2. trigger crash on non-boot cpu

  Expected result:
  Capture dump and reboot

  Actual result:
  Hang in early kdump boot process after crash
   
  Userspace tool common name: kdump-tools 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: kdump-tools

  Userspace tool obtained from project website:  na

  == Comment: #1 - Hari Krishna Bathini - 2019-05-10 06:45:46 ==
  Launchpad bug 1560552 added "nr_cpus=1" support on ppc64 though
  this change never made it upstream as maintainer has a few apprehensions..

  With 4.18 kernels, this change is dropped on Ubuntu kernels too.
  With nr_cpus=1 support in kernel, kdump-tools was also updated to
  use "nr_cpsu=1" by default instead of "maxcpus=1" (see launchpad
  bug 1568952). This kdump-tools change has to be reverted to make
  it consist with the kernel change. Note that "nr_cpus=1 change had
  a issues in kdump guest environment even with "nr_cpus=1" support
  for kdump in kernel. So, even not withstanding the kernel revert, it is
  better to default to "maxcpus=1" on all kernel versions. So, please
  revert the kdump-tools fix that went in with launchpad bug 1568952

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

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

[Kernel-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

It goes back to xenial. I think I found the cause on systemd, will test
a fix and report back soon.

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

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in udisks2 package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  New
Status in udisks2 source package in Bionic:
  New
Status in linux source package in Disco:
  New
Status in systemd source package in Disco:
  New
Status in udisks2 source package in Disco:
  New
Status in linux source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  New
Status in udisks2 source package in Eoan:
  New

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

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

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

[Kernel-packages] [Bug 1828596] Re: kdump fails when crash is triggered after DLPAR cpu add operation

I will start working on an upload to eoan by next week. I should have
something for you to test early in the week.

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

** Changed in: kexec-tools (Ubuntu)
   Status: New => Invalid

** Changed in: makedumpfile (Ubuntu)
 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 makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1828596

Title:
  kdump fails when crash is triggered after DLPAR cpu add operation

Status in The Ubuntu-power-systems project:
  New
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 ==
  ---Problem Description---
  kdump fails when crash is triggered after CPU add operation.
   
  Machine Type = na 
   
  ---System Hang---
   Crashed in early boot process of kdump kernel after crash

  Had to issue system reset from HMC to reclaim
   
  ---Steps to Reproduce---
   1. Configure kdump.
  2. Add cpu from HMC.
  3. Trigger crash.
  4. Machine hangs after crash as below:

  ---
  [169250.213166] IPI complete
  [169250.234331] kexec: Starting switchover sequence.
  I'm in purgatory
   --- STRUCK HERE ---
   
  ---uname output---
  na
   
  ---Debugger---
  A debugger is not configured

  == Comment: #1 - Hari Krishna Bathini  - 2019-05-10 05:56:46 ==
  The problem is, kexec udev rule to restart kdump-tools service - when a core 
is added,
  is not being triggered. The old DT created by kexec (before the core is added)
  is being used by KDump Kernel. So, when system crashes on a thread from
  the added core(s), KDump kernel is failing to get the 'boot_cpuid' and
  eventually failing to boot..

  == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 ==
  The udev rule when CPU is added is not triggered because ppc64 does not
  eject add/remove event when a CPU is hot added/removed. It only ejects
  online/offline event to user space when CPU is hot added/removed.

  So, the below udev rules are never triggered when needed:

  SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"
  SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

  Also, with how CPU hot add & remove are handled in ppc64, a udev trigger
  to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU
  hot add case by updating the udev rule and drop the udev rule meant for CPU
  hot remove in the kdump udev rules file:

  
  SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

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

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

[Kernel-packages] [Bug 1828597] Re: KDump boot fails with nr_cpus=1

This is really a bug on the kernel, after and including 4.18.

This is due to a patch that we have been carrying since forever, and
when the involved code changed a lot from 4.15 to 4.18, the patch was
dropped, as it couldn't be easily fixed up.

Even before that happened, I tried to upstream the patch, resending it
to the mailing list, but PPC maintainers wanted something different. The
original author resent with some modifications, but maintainers wouldn't
still apply it. As far as I remember, that patchset doesn't apply
anymore after the referred changes.

I have tried to work on a different solution, considering the new code
base, but didn't have much time to get a working solution.

Cascardo.

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

** Also affects: kexec-tools (Ubuntu Disco)
   Importance: Undecided
   Status: New

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

** Also affects: kexec-tools (Ubuntu Eoan)
   Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
   Status: New

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

** Also affects: kexec-tools (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

** Changed in: kexec-tools (Ubuntu Eoan)
   Status: New => Invalid

** Changed in: kexec-tools (Ubuntu Disco)
   Status: New => Invalid

** Changed in: kexec-tools (Ubuntu Cosmic)
   Status: New => Invalid

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

Title:
  KDump boot fails with nr_cpus=1

Status in The Ubuntu-power-systems project:
  New
Status in kexec-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in kexec-tools source package in Cosmic:
  Invalid
Status in linux source package in Cosmic:
  Confirmed
Status in kexec-tools source package in Disco:
  Invalid
Status in linux source package in Disco:
  Confirmed
Status in kexec-tools source package in Eoan:
  Invalid
Status in linux source package in Eoan:
  Confirmed

Bug description:
  == Comment: #0 - Hari Krishna Bathini  - 2019-05-10 06:38:21 ==

  ---Problem Description---
  kdump boots fails in some environments when nr_cpus=1 is passed 
   
  ---uname output---
  na
   
  Machine Type = na 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. configure kdump
  2. trigger crash on non-boot cpu

  Expected result:
  Capture dump and reboot

  Actual result:
  Hang in early kdump boot process after crash
   
  Userspace tool common name: kdump-tools 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: kdump-tools

  Userspace tool obtained from project website:  na

  == Comment: #1 - Hari Krishna Bathini - 2019-05-10 06:45:46 ==
  Launchpad bug 1560552 added "nr_cpus=1" support on ppc64 though
  this change never made it upstream as maintainer has a few apprehensions..

  With 4.18 kernels, this change is dropped on Ubuntu kernels too.
  With nr_cpus=1 support in kernel, kdump-tools was also updated to
  use "nr_cpsu=1" by default instead of "maxcpus=1" (see launchpad
  bug 1568952). This kdump-tools change has to be reverted to make
  it consist with the kernel change. Note that "nr_cpus=1 change had
  a issues in kdump guest environment even with "nr_cpus=1" support
  for kdump in kernel. So, even not withstanding the kernel revert, it is
  better to default to "maxcpus=1" on all kernel versions. So, please
  revert the kdump-tools fix that went in with launchpad bug 1568952

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

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

[Kernel-packages] [Bug 1828596] Re: kdump fails when crash is triggered after DLPAR cpu add operation

2019-05-10 Thread Andrew Cloke

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: ubuntu-power-systems
   Importance: Undecided => High

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

Title:
  kdump fails when crash is triggered after DLPAR cpu add operation

Status in The Ubuntu-power-systems project:
  New
Status in kexec-tools package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 ==
  ---Problem Description---
  kdump fails when crash is triggered after CPU add operation.
   
  Machine Type = na 
   
  ---System Hang---
   Crashed in early boot process of kdump kernel after crash

  Had to issue system reset from HMC to reclaim
   
  ---Steps to Reproduce---
   1. Configure kdump.
  2. Add cpu from HMC.
  3. Trigger crash.
  4. Machine hangs after crash as below:

  ---
  [169250.213166] IPI complete
  [169250.234331] kexec: Starting switchover sequence.
  I'm in purgatory
   --- STRUCK HERE ---
   
  ---uname output---
  na
   
  ---Debugger---
  A debugger is not configured

  == Comment: #1 - Hari Krishna Bathini  - 2019-05-10 05:56:46 ==
  The problem is, kexec udev rule to restart kdump-tools service - when a core 
is added,
  is not being triggered. The old DT created by kexec (before the core is added)
  is being used by KDump Kernel. So, when system crashes on a thread from
  the added core(s), KDump kernel is failing to get the 'boot_cpuid' and
  eventually failing to boot..

  == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 ==
  The udev rule when CPU is added is not triggered because ppc64 does not
  eject add/remove event when a CPU is hot added/removed. It only ejects
  online/offline event to user space when CPU is hot added/removed.

  So, the below udev rules are never triggered when needed:

  SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"
  SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

  Also, with how CPU hot add & remove are handled in ppc64, a udev trigger
  to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU
  hot add case by updating the udev rule and drop the udev rule meant for CPU
  hot remove in the kdump udev rules file:

  
  SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

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

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

[Kernel-packages] [Bug 1828597] Re: KDump boot fails with nr_cpus=1

2019-05-10 Thread Andrew Cloke

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: ubuntu-power-systems
   Importance: Undecided => High

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

Title:
  KDump boot fails with nr_cpus=1

Status in The Ubuntu-power-systems project:
  New
Status in kexec-tools package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Hari Krishna Bathini  - 2019-05-10 06:38:21 ==

  ---Problem Description---
  kdump boots fails in some environments when nr_cpus=1 is passed 
   
  ---uname output---
  na
   
  Machine Type = na 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. configure kdump
  2. trigger crash on non-boot cpu

  Expected result:
  Capture dump and reboot

  Actual result:
  Hang in early kdump boot process after crash
   
  Userspace tool common name: kdump-tools 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: kdump-tools

  Userspace tool obtained from project website:  na

  == Comment: #1 - Hari Krishna Bathini - 2019-05-10 06:45:46 ==
  Launchpad bug 1560552 added "nr_cpus=1" support on ppc64 though
  this change never made it upstream as maintainer has a few apprehensions..

  With 4.18 kernels, this change is dropped on Ubuntu kernels too.
  With nr_cpus=1 support in kernel, kdump-tools was also updated to
  use "nr_cpsu=1" by default instead of "maxcpus=1" (see launchpad
  bug 1568952). This kdump-tools change has to be reverted to make
  it consist with the kernel change. Note that "nr_cpus=1 change had
  a issues in kdump guest environment even with "nr_cpus=1" support
  for kdump in kernel. So, even not withstanding the kernel revert, it is
  better to default to "maxcpus=1" on all kernel versions. So, please
  revert the kdump-tools fix that went in with launchpad bug 1568952

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

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

[Kernel-packages] [Bug 1828604] Re: Lenovo T490S and X390 GM do not have Firefox.App store install errors out

** Package changed: linux (Ubuntu) => snapd (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/1828604

Title:
  Lenovo T490S and X390 GM do not have Firefox.App store install errors
  out

Status in snapd package in Ubuntu:
  New

Bug description:
  The new GM Images for T490S and X390 do not have Firefox preinstalled.
  When I try to install from the Appstore, it errors out "Firefox : too
  early for operation, device not yet seeded or device model not
  acknowledged."

  If I install using apt-get install firefox it seemed to install fine.

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

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

[Kernel-packages] [Bug 1828604] [NEW] Lenovo T490S and X390 GM do not have Firefox.App store install errors out

2019-05-10 Thread Vamshee Paduru

Public bug reported:

The new GM Images for T490S and X390 do not have Firefox preinstalled.
When I try to install from the Appstore, it errors out "Firefox : too
early for operation, device not yet seeded or device model not
acknowledged."

If I install using apt-get install firefox it seemed to install fine.

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

Title:
  Lenovo T490S and X390 GM do not have Firefox.App store install errors
  out

Status in linux package in Ubuntu:
  New

Bug description:
  The new GM Images for T490S and X390 do not have Firefox preinstalled.
  When I try to install from the Appstore, it errors out "Firefox : too
  early for operation, device not yet seeded or device model not
  acknowledged."

  If I install using apt-get install firefox it seemed to install fine.

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

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

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

--- Comment From hbath...@in.ibm.com 2019-05-10 11:40 EDT---
(In reply to comment #53)
[...]

> bionic? I know newer kernels may have regressed when crashing from the
> non-boot CPU, which should affect 4.18 kernels and later, but not 4.15.

Raised launchpad bug 1828597 to follow-up on this..

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore':
  Bad address when trying to dump vmcore

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in makedumpfile source package in Xenial:
  New
Status in linux source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Invalid
Status in makedumpfile source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Invalid
Status in makedumpfile source package in Disco:
  Fix Released

Bug description:
  [Impact]
  After a DLPAR memory/CPU add/remove operation, kdump tools need to be 
restarted or else kdump tools will fail to capture the crash. 

  [Test]

  == Comment: #0 - Ping Tian Han  - 2017-01-09 02:51:00 ==
  ---Problem Description---
  Vmcore cannot be saved when triggering bug 150353 on roselp4:

  Copying data   : [  2.0 %] \/usr/sbin/kdump-config: line 
591:  5502 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [  512.833872] kdump-tools[5450]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [  573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad 
address
  [  573.605717] kdump-tools[5450]:  * kdump-tools: failed to save vmcore in 
/var/crash/201701090223
  [  573.765417] kdump-tools[5450]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701090223/dmesg.201701090223
  [  574.285506] kdump-tools[5450]: The kernel version is not supported.
  [  574.285672] kdump-tools[5450]: The makedumpfile operation may be 
incomplete.
  [  574.285767] kdump-tools[5450]: The dmesg log is saved to 
/var/crash/201701090223/dmesg.201701090223.
  [  574.305422] kdump-tools[5450]: makedumpfile Completed.
  [  574.315363] kdump-tools[5450]:  * kdump-tools: saved dmesg content in 
/var/crash/201701090223
  [  574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600
  [  574.705384] kdump-tools[5450]: Rebooting.
   Stopping ifup for ib0...
  [  OK  ] Stopped ifup for ib0.
  [ 1008.579897] reboot: Restarting system

  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie
  Mitsuyoshi/carri...@us.ibm.com

  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = lpar

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. config kdump on roselp4
  2. try to trigger bug 150353

  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan  -
  2017-01-10 02:42:25 ==

  root@roselp4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic 
root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet 
crashkernel=384M-:512M

  root@roselp4:~# dmesg | grep Reser
  [0.00] Reserving 512MB of memory at 128MB for crashkernel (System 
RAM: 21760MB)

  [Regression Potential]
  The fix applies to makedumpfile, and could impact dump capture.

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

-- 
Mailing list: https://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 1828564] Re: Update brcmfmac43455-sdio for rpi3b+/a+

2019-05-10 Thread Seth Forshee

On Fri, May 10, 2019 at 03:19:01PM -, Jonathan Cave wrote:
> Thanks for the info, I wasn't aware of what policy was for firmware.

It's the same as for the rest of the distro.

> As far as I can tell this firmware is all non-free, for example it
> appears to come from this repo https://github.com/RPi-Distro/firmware-
> nonfree and be in a non-free package in debian:
> https://packages.debian.org/sid/firmware-brcm80211. You would have to
> let me know what constitutes upstream for linux-firmware.

This is upstream:

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/

There are updates to brcmfmac firmware files since bionic, but I'm not
sure which specific files raspi2 uses.

> At this time I'm just investigating why we see regular failures on some
> of our devices when attempting to connect to APs in our certification
> lab, but haven't been able to identify any cause or solid reproduction
> scenario as yet. Given I spotted this information I thought I would
> raise it in case it was an omission.

We've had repeated requests for raspi2 firmware files, but most of the
time there isn't a clear license for distribution.

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

Title:
  Update brcmfmac43455-sdio for rpi3b+/a+

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  The firmware identified is used on Raspberry Pi devices that are
  reference devices for Ubuntu Core. The firmware currently carried in
  Bionic is quite old:

  brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Mar  1 2015
  07:29:38 version 7.45.18 (r538002) FWID 01-6a2c8ad4

  For comparison Raspbian has:

  brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Feb 27 2018
  03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04

  Could the newer firmware be made available in bionic updates?

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

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

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

--- Comment From hbath...@in.ibm.com 2019-05-10 11:32 EDT---
(In reply to comment #55)
> (In reply to comment #53)
> [...]
> > could proceed with the SRU, and open a new bug to fix the CPU hotplug case,
> > if there is one.
>
> Raised bug 177551 to follow-up on the problem in CPU hot-add case which

Bug 1828596 is the corresponding launchpad bug..

> is currently being screened internally. Will update the launchpad bug number
> once we have it..

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore':
  Bad address when trying to dump vmcore

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in makedumpfile source package in Xenial:
  New
Status in linux source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Invalid
Status in makedumpfile source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Invalid
Status in makedumpfile source package in Disco:
  Fix Released

Bug description:
  [Impact]
  After a DLPAR memory/CPU add/remove operation, kdump tools need to be 
restarted or else kdump tools will fail to capture the crash. 

  [Test]

  == Comment: #0 - Ping Tian Han  - 2017-01-09 02:51:00 ==
  ---Problem Description---
  Vmcore cannot be saved when triggering bug 150353 on roselp4:

  Copying data   : [  2.0 %] \/usr/sbin/kdump-config: line 
591:  5502 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [  512.833872] kdump-tools[5450]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [  573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad 
address
  [  573.605717] kdump-tools[5450]:  * kdump-tools: failed to save vmcore in 
/var/crash/201701090223
  [  573.765417] kdump-tools[5450]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701090223/dmesg.201701090223
  [  574.285506] kdump-tools[5450]: The kernel version is not supported.
  [  574.285672] kdump-tools[5450]: The makedumpfile operation may be 
incomplete.
  [  574.285767] kdump-tools[5450]: The dmesg log is saved to 
/var/crash/201701090223/dmesg.201701090223.
  [  574.305422] kdump-tools[5450]: makedumpfile Completed.
  [  574.315363] kdump-tools[5450]:  * kdump-tools: saved dmesg content in 
/var/crash/201701090223
  [  574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600
  [  574.705384] kdump-tools[5450]: Rebooting.
   Stopping ifup for ib0...
  [  OK  ] Stopped ifup for ib0.
  [ 1008.579897] reboot: Restarting system

  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie
  Mitsuyoshi/carri...@us.ibm.com

  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = lpar

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. config kdump on roselp4
  2. try to trigger bug 150353

  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan  -
  2017-01-10 02:42:25 ==

  root@roselp4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic 
root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet 
crashkernel=384M-:512M

  root@roselp4:~# dmesg | grep Reser
  [0.00] Reserving 512MB of memory at 128MB for crashkernel (System 
RAM: 21760MB)

  [Regression Potential]
  The fix applies to makedumpfile, and could impact dump capture.

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

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

[Kernel-packages] [Bug 1828568] Re: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic

Please try Safe Graphics mode in Disco live USB.

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

Title:
  Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless
  acpi=off and noapic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Booting an Ubuntu 18.04.2 LTS amd64 installer USB on a Clevo P650RE3
  results in a hang shortly after the desktop is presented, unless
  acpi=off and noapic (or nolapic) are given as kernel boot parameters.
  The same installer runs without issue on other machines and the 16.04
  installer runs without issue on the P650RE3.

  Without passing acpi=off and noapic, a desktop comes up and a terminal
  can be obtained, but keystrokes and mouse clicks are not responded to
  after a small number of seconds. The mouse pointer continues to move
  with trackpad input.

  With careful timing I was able to obtain, uname, dmidecode and (an
  empty) lspci output. I was not able to obtain any /proc/acpi
  information, but do have dmesg. These are all attached. With acpi=off
  and noapic, I can get lspci and dmidecode output, but obviously no
  /proc/acpi. In this case the lspci output is not impty and dmidecode
  is identical to the failing case.

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

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

[Kernel-packages] [Bug 1827335] Re: Unable to put offline CPU back online on Bionic/B-hwe-edge P9

2019-05-10 Thread Manoj Iyer

== From the BMC web UI ==

Sensor Readings => Select a sensor type category: All Sensors:
CPU Core Func 48Processor disabled


== In dmesg ==
[0.00] CPU maps initialized for 4 threads per core

[0.021044] smp: Bringing up secondary CPUs ...
[0.704642] smp: Brought up 2 nodes, 156 CPUs
[0.704709] numa: Node 0 CPUs: 0-79
[0.704773] numa: Node 8 CPUs: 80-155

== Result ==
Looks like exactly 4 threads are missing between 155 and 159 which corresponds 
to the disabled Core as reported by firmware. BMC logs does not give me any 
reason for why a core was disabled (may be a bad core?)... May be someone @IBM 
could tell me if there was a firmware command to get that information?

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

Title:
  Unable to put offline CPU back online on Bionic/B-hwe-edge P9

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

Bug description:
  You will see these CPUs in offline state after boot.

  ubuntu@baltar:~$ cat /sys/devices/system/cpu/offline
  156-159

  ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu156/online
  1
  tee: /sys/devices/system/cpu/cpu156/online: Invalid argument
  ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu157/online
  1
  tee: /sys/devices/system/cpu/cpu157/online: Invalid argument
  ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu158/online
  1
  tee: /sys/devices/system/cpu/cpu158/online: Invalid argument
  ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu159/online
  1
  tee: /sys/devices/system/cpu/cpu159/online: Invalid argument

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-14-generic 5.0.0-14.15~18.04.1+signed1
  ProcVersionSignature: Ubuntu 5.0.0-14.15~18.04.1-generic 5.0.6
  Uname: Linux 5.0.0-14-generic ppc64le
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: ppc64el
  Date: Thu May  2 06:46:36 2019
  ProcLoadAvg: 0.00 0.00 0.00 1/1298 6496
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 5.0.0-14-generic (buildd@bos02-ppc64el-014) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #15~18.04.1-Ubuntu SMP Thu Apr 25 
18:55:27 UTC 2019
  SourcePackage: linux-signed-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 40
  cpu_coreson: Number of cores online = 39
  cpu_dscr: DSCR is 16
  cpu_freq:
   min: 2.862 GHz (cpu 79)
   max: 2.945 GHz (cpu 81)
   avg: 2.903 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=4

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

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

[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while

2019-05-10 Thread CiaranM

In case this is useful: updating the Dell XPS 15 9560 BIOS to 0.1.14.2
and Dell TB16 dock and component firmware (packaged as version 1.0.2)
seems to have resolved this for me. It's been a week and I haven't seen
the issue since: previously, I was seeing it around once per day. I've
been unable to trigger it by e.g. connecting various USB devices (USB-A
storage &/or network adaptor, USB-C HDMI adaptor) to every port on the
dock and laptop. I have two Dell U2715H monitors connected via one mini-
DP to DP cable, daisy chained to the second monitor, and a few USB
storage devices occasionally connected to the docking station's USB-A
ports.

I'm running on Linux kernel version 5.0.10 under Arch Linux
(5.0.10-arch1-1-ARCH). I had to boot into Windows and run the update
several (6?) times to successfully update all the various components
shown on the docking station. I *think* the Multi Stream Transport (MST)
firmware 3.12.002 is the fix. This firmware is still marked as "State:
testing" on the Linux Vendor Firmware Service
(https://fwupd.org/lvfs/device/com.dell.mst0a52c8c7.firmware).

Laptop BIOS 0.1.14.2 is not on LVFS and was also not offered via Dell
Command Update: I had to visit Dell's support site to download it.
However, that download now seems to have been removed from their site:
https://www.dell.com/support/home/uk/en/ukbsdt1/product-
support/product/xps-15-9560-laptop/drivers

```
~ 
➜ fwupdmgr get-topology○├─ XPS 9560 Thunderbolt Controller   
3695fe182ca17c53702255daf8b4f73612bd0d2b
├─ XPS 15 9560 System Firmware   
f4b6e3af5b4bf8ad1f2ed2922b76df457271
├─ Dell TB16 
84edf044a6b53037732cfc7591b65a8d36384cc9
│ ├─ Dell Thunderbolt Cable  
b75fc95a2b3a77f2fc6895c651a92fd9c0a23be3
│ ├─ Dell Thunderbolt Dock   
8a0e9a12b51f3e5f328df1feb145d18f88aebccf
│ ├─ Dell TB16 Thunderbolt Cable 
f8194a42320518472a2e67c1d89018c7a5219841
│ ├─ Dell TB16 Port Controller 1 
b3fa3dc04e3450450bb17910417562e5b6cf69d0
│ └─ Dell TB16 Port Controller 2 
4bcf1477575b55912993240dd1edd8b0ebb6d491
├─ Unifying Receiver 
fb1a5fd6e7d8cbf5d5a2ba7df68aee106ce41027
└─ PM961 NVMe SAMSUNG 1024GB 
04e17fcf7d3de91da49a163ffe4907855c3648be

~ 
➜ fwupdmgr update -v   
No upgrades for XPS 9560 Thunderbolt Controller, current is 21.00: 21.00=same
No upgrades for XPS 15 9560 System Firmware, current is 0.1.14.2: 
0.1.12.1=older, 0.1.11.0=older, 0.1.10.1=older, 0.1.9.4=older, 0.1.7.1=older, 
0.1.6.2=older, 0.1.5.0=older, 0.1.4.0=older, 0.1.3.4=older, 0.1.3.3=older, 
0.1.2.4=older, 0.1.1.3=older, 0.1.0.3=older
ignoring XPS 15 9560 TPM 2.0 [cc2b222929056ab3e9a208df9f86b7d9a74ae514] as not 
updatable
No upgrades for Unifying Receiver, current is RQR12.08_B0030: 
RQR12.08_B0030=same, RQR12.07_B0029=older

~ 
➜
```

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

Title:
  USB over thunderbolt turns off every once in a while

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using a USB hub in the Dell TB16 (240W) connected to a Dell
  Precision 5520 using Thunderbolt 3.

  Every so often (can be several times in an hour if I'm really unlucky,
  some days it is less of a problem), the USB hub disconnects from the
  computer and the devices connected to it lose power and stop
  responding.

  disconnecting and reconnecting the USB cables has no effect. I can
  restore functionality by instructing the xhci_hcd driver to unbind
  from the USB 3.0 Host Controller in the dock and to rebind to it using
  the commands:

  echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind
  echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind

  Here's the dmesg output when the USB hub disconnects:

  279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15
  [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop 
endpoint command.
  [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, 
assume dead
  [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108
  [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up
  [279283.07] usb 3-1.5: Failed to suspend device, error -22
  [279283.022234] usb 3-1: USB disconnect, device number 2
  [279283.022235] usb 3-1.1: USB disconnect, device number 3
  [279283.022236] usb 3-1.1.1: USB disconnect, device number 5
  [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8
  [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11
  [279283.022326] usb 4-1: USB disconnect, device number 2
  [279283.022328] usb 4-1.1: USB disconnect, device number 3
  [279283.022329] usb 4-1.1.1: USB disconnect, device number 5
  [279283.022998] usb 4-1.2: USB disconnect, device number 4
  [279283.191217] usb 3-1.1.1.5: USB

[Kernel-packages] [Bug 1785715] Re: ubuntu hynix ssd I/O Errors after some minutes

Do you still see this bug?

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

Title:
  ubuntu hynix ssd I/O Errors after some minutes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Maybe similar to Bug 1678184
  Im working on ubuntu 18.04 (with Kernel 4.15.0-29-generic) on a dell XPS 
15-9560
  After 20 - 180 Minutes the graphical interface hangs up (i can switch 
workspaces, but not much else) and entering commands like "ls" yields bash: 
input/output error
  Reboot is impossible via the command or the button. Short click on power 
button gives me a TTY like view prompting errors for nvme0 ext4 file system 
errors (i will post more exact text on next hangup)

  The hangups appear randomly, but often during shutting the lid or plugging in 
power cable, which makes me thing it might be something with ssd power states.
  For that reason i added grub parameters like 
"nvme_core.default_ps_max_latency_us=3000" (see Bug 1678184) and ended up fully 
disabling APST by setting it to 0, but the bug still occured.

  sudo nvme id-ctrl /dev/nvme0 yields:
  NVME Identify Controller:
  vid : 0x1c5c
  ssvid   : 0x1c5c
  sn  : EJ75N621210105PBR   
  mn  : PC300 NVMe SK hynix 1TB 
  fr  : 20005A00
  rab : 1
  ieee: ace42e
  cmic: 0
  mdts: 5
  cntlid  : 0
  ver : 10200
  rtd3r   : 90f560
  rtd3e   : ea60
  oaes: 0
  ctratt  : 0
  oacs: 0x16
  acl : 3
  aerl: 3
  frmw: 0x16
  lpa : 0x2
  elpe: 254
  npss: 4
  avscc   : 0x1
  apsta   : 0x1
  wctemp  : 361
  cctemp  : 363
  mtfa: 0
  hmpre   : 0
  hmmin   : 0
  tnvmcap : 0
  unvmcap : 0
  rpmbs   : 0
  edstt   : 60
  dsto: 1
  fwug: 0
  kas : 0
  hctma   : 0
  mntmt   : 0
  mxtmt   : 0
  sanicap : 0
  hmminds : 0
  hmmaxd  : 0
  sqes: 0x66
  cqes: 0x44
  maxcmd  : 0
  nn  : 1
  oncs: 0x1e
  fuses   : 0
  fna : 0
  vwc : 0x1
  awun: 255
  awupf   : 0
  nvscc   : 1
  acwu: 0
  sgls: 0
  subnqn  : 
  ioccsz  : 0
  iorcsz  : 0
  icdoff  : 0
  ctrattr : 0
  msdbd   : 0
  ps0 : mp:5.87W operational enlat:5 exlat:5 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
  ps1 : mp:2.40W operational enlat:30 exlat:30 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
  ps2 : mp:1.90W operational enlat:100 exlat:100 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
  ps3 : mp:0.1000W non-operational enlat:1000 exlat:1000 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
  ps4 : mp:0.0060W non-operational enlat:1000 exlat:5000 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-

  
  sudo nvme get-feature -f 0x0c -H /dev/nvme0 yields:
  get-feature:0xc (Autonomous Power State Transition), Current value:
Autonomous Power State Transition Enable (APSTE): Disabled
Auto PST Entries.
Entry[ 0]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 1]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
... and so on ...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  revisor1593 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1bc0493d-0592-40d4-b0f4-938fbe12a990
  InstallationDate: Installed on 2018-07-12 (25 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 003: ID 04f3:24a1 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=70377f6e-8c1c-4316-bded-c738410879ab ro quiet splash 
nvme_core.default_ps_max_latency_us=0 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-29-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/2018
  dmi.bios.vendor: Dell Inc.

[Kernel-packages] [Bug 1828578] Re: dell xps 9570 wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS

This wifi drop and freeze issue happens only in home wifi networks. Not
on home networks.

I came to notice this
https://www.dell.com/support/article/it/it/itbsdt1/sln306440/xps-13-9360
-ubuntu-killer-wireless-n1535-manuale-aggiornamento-firmware?lang=it
here they manually adding the wifi firmware. I will try this later.
Before that latest 18.04.2 LTS wifi inbuild driver doesn't supports this
Dell XPS 9570 wifi driver? Please confirm.

I will share the required logs in next update

May I know what about Ubuntu 16.04 LTS, does this driver included or not
?

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

Title:
  dell xps 9570 wifi reconnection issue followed by freeze + Ubuntu
  18.04.2 LTS

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello Team,

  Env - Dell XPS 9570
Ubuntu 18.04.2 , HWE kernel

  We are facing intermittently wifi reconnection issue on Ubuntu 18.04.
  Software upgrade is up-to date. Also some time we facing freezing
  issue due to this hard reset required to make machine back to normal.

  Please let me know if there are any known issue with this particular
  model on 18.04 ? Please let me know.

  Thanks
  Jay

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

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

[Kernel-packages] [Bug 1828597] [NEW] KDump boot fails with nr_cpus=1

Public bug reported:

== Comment: #0 - Hari Krishna Bathini  - 2019-05-10 06:38:21 ==

---Problem Description---
kdump boots fails in some environments when nr_cpus=1 is passed 
 
---uname output---
na
 
Machine Type = na 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
 1. configure kdump
2. trigger crash on non-boot cpu

Expected result:
Capture dump and reboot

Actual result:
Hang in early kdump boot process after crash
 
Userspace tool common name: kdump-tools 
 
The userspace tool has the following bit modes: 64-bit 

Userspace rpm: kdump-tools

Userspace tool obtained from project website:  na

== Comment: #1 - Hari Krishna Bathini - 2019-05-10 06:45:46 ==
Launchpad bug 1560552 added "nr_cpus=1" support on ppc64 though
this change never made it upstream as maintainer has a few apprehensions..

With 4.18 kernels, this change is dropped on Ubuntu kernels too.
With nr_cpus=1 support in kernel, kdump-tools was also updated to
use "nr_cpsu=1" by default instead of "maxcpus=1" (see launchpad
bug 1568952). This kdump-tools change has to be reverted to make
it consist with the kernel change. Note that "nr_cpus=1 change had
a issues in kdump guest environment even with "nr_cpus=1" support
for kdump in kernel. So, even not withstanding the kernel revert, it is
better to default to "maxcpus=1" on all kernel versions. So, please
revert the kdump-tools fix that went in with launchpad bug 1568952

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


** Tags: architecture-ppc64le bugnameltc-177552 severity-high 
targetmilestone-inin---

** Tags added: architecture-ppc64le bugnameltc-177552 severity-high
targetmilestone-inin---

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

** Package changed: ubuntu => kexec-tools (Ubuntu)

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

Title:
  KDump boot fails with nr_cpus=1

Status in kexec-tools package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Hari Krishna Bathini  - 2019-05-10 06:38:21 ==

  ---Problem Description---
  kdump boots fails in some environments when nr_cpus=1 is passed 
   
  ---uname output---
  na
   
  Machine Type = na 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. configure kdump
  2. trigger crash on non-boot cpu

  Expected result:
  Capture dump and reboot

  Actual result:
  Hang in early kdump boot process after crash
   
  Userspace tool common name: kdump-tools 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: kdump-tools

  Userspace tool obtained from project website:  na

  == Comment: #1 - Hari Krishna Bathini - 2019-05-10 06:45:46 ==
  Launchpad bug 1560552 added "nr_cpus=1" support on ppc64 though
  this change never made it upstream as maintainer has a few apprehensions..

  With 4.18 kernels, this change is dropped on Ubuntu kernels too.
  With nr_cpus=1 support in kernel, kdump-tools was also updated to
  use "nr_cpsu=1" by default instead of "maxcpus=1" (see launchpad
  bug 1568952). This kdump-tools change has to be reverted to make
  it consist with the kernel change. Note that "nr_cpus=1 change had
  a issues in kdump guest environment even with "nr_cpus=1" support
  for kdump in kernel. So, even not withstanding the kernel revert, it is
  better to default to "maxcpus=1" on all kernel versions. So, please
  revert the kdump-tools fix that went in with launchpad bug 1568952

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

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

[Kernel-packages] [Bug 1828596] [NEW] kdump fails when crash is triggered after DLPAR cpu add operation

Public bug reported:

== Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 ==
---Problem Description---
kdump fails when crash is triggered after CPU add operation.
 
Machine Type = na 
 
---System Hang---
 Crashed in early boot process of kdump kernel after crash

Had to issue system reset from HMC to reclaim
 
---Steps to Reproduce---
 1. Configure kdump.
2. Add cpu from HMC.
3. Trigger crash.
4. Machine hangs after crash as below:

---
[169250.213166] IPI complete
[169250.234331] kexec: Starting switchover sequence.
I'm in purgatory
 --- STRUCK HERE ---
 
---uname output---
na
 
---Debugger---
A debugger is not configured

== Comment: #1 - Hari Krishna Bathini  - 2019-05-10 05:56:46 ==
The problem is, kexec udev rule to restart kdump-tools service - when a core is 
added,
is not being triggered. The old DT created by kexec (before the core is added)
is being used by KDump Kernel. So, when system crashes on a thread from
the added core(s), KDump kernel is failing to get the 'boot_cpuid' and
eventually failing to boot..

== Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 ==
The udev rule when CPU is added is not triggered because ppc64 does not
eject add/remove event when a CPU is hot added/removed. It only ejects
online/offline event to user space when CPU is hot added/removed.

So, the below udev rules are never triggered when needed:

SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"
SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

Also, with how CPU hot add & remove are handled in ppc64, a udev trigger
to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU
hot add case by updating the udev rule and drop the udev rule meant for CPU
hot remove in the kdump udev rules file:


SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

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


** Tags: architecture-ppc64le bugnameltc-177551 severity-high 
targetmilestone-inin---

** Tags added: architecture-ppc64le bugnameltc-177551 severity-high
targetmilestone-inin---

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

** Package changed: ubuntu => kexec-tools (Ubuntu)

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

Title:
  kdump fails when crash is triggered after DLPAR cpu add operation

Status in kexec-tools package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 ==
  ---Problem Description---
  kdump fails when crash is triggered after CPU add operation.
   
  Machine Type = na 
   
  ---System Hang---
   Crashed in early boot process of kdump kernel after crash

  Had to issue system reset from HMC to reclaim
   
  ---Steps to Reproduce---
   1. Configure kdump.
  2. Add cpu from HMC.
  3. Trigger crash.
  4. Machine hangs after crash as below:

  ---
  [169250.213166] IPI complete
  [169250.234331] kexec: Starting switchover sequence.
  I'm in purgatory
   --- STRUCK HERE ---
   
  ---uname output---
  na
   
  ---Debugger---
  A debugger is not configured

  == Comment: #1 - Hari Krishna Bathini  - 2019-05-10 05:56:46 ==
  The problem is, kexec udev rule to restart kdump-tools service - when a core 
is added,
  is not being triggered. The old DT created by kexec (before the core is added)
  is being used by KDump Kernel. So, when system crashes on a thread from
  the added core(s), KDump kernel is failing to get the 'boot_cpuid' and
  eventually failing to boot..

  == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 ==
  The udev rule when CPU is added is not triggered because ppc64 does not
  eject add/remove event when a CPU is hot added/removed. It only ejects
  online/offline event to user space when CPU is hot added/removed.

  So, the below udev rules are never triggered when needed:

  SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"
  SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

  Also, with how CPU hot add & remove are handled in ppc64, a udev trigger
  to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU
  hot add case by updating the udev rule and drop the udev rule meant for CPU
  hot remove in the kdump udev rules file:

  
  SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

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

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

[Kernel-packages] [Bug 1828564] Re: Update brcmfmac43455-sdio for rpi3b+/a+

2019-05-10 Thread Jonathan Cave

Thanks for the info, I wasn't aware of what policy was for firmware.

As far as I can tell this firmware is all non-free, for example it
appears to come from this repo https://github.com/RPi-Distro/firmware-
nonfree and be in a non-free package in debian:
https://packages.debian.org/sid/firmware-brcm80211. You would have to
let me know what constitutes upstream for linux-firmware.

At this time I'm just investigating why we see regular failures on some
of our devices when attempting to connect to APs in our certification
lab, but haven't been able to identify any cause or solid reproduction
scenario as yet. Given I spotted this information I thought I would
raise it in case it was an omission.

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

Title:
  Update brcmfmac43455-sdio for rpi3b+/a+

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  The firmware identified is used on Raspberry Pi devices that are
  reference devices for Ubuntu Core. The firmware currently carried in
  Bionic is quite old:

  brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Mar  1 2015
  07:29:38 version 7.45.18 (r538002) FWID 01-6a2c8ad4

  For comparison Raspbian has:

  brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Feb 27 2018
  03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04

  Could the newer firmware be made available in bionic updates?

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

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

[Kernel-packages] [Bug 1828131] Re: Qemu causes system hang

2019-05-10 Thread Avi Eis

Yes, had the same issue on 418.

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

Title:
  Qemu causes system hang

Status in nvidia-graphics-drivers-418 package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to use https://virt-manager.org/ / QEMU. I migrated over a
  Ubuntu Guest from Virtualbox, added it to virt-manager, and launch. It
  opens the window, then the system freezes.

  I don't know if it's a bug in QEMU, libvirt, or virt-manager, or
  nvidia. Nvidia is working fine otherwise, Version: 430.09.

  This is easily reproduced every time I try starting a qemu machine, so
  I can run any diagnostics while this happens if that helps.

  This is from journalctl at the time of the freeze:

  May 07 19:35:52 ap /usr/lib/gdm3/gdm-x-session[3400]: (EE) NVIDIA(0): The 
NVIDIA X driver has encountered an error; attempting to
  May 07 19:35:52 ap /usr/lib/gdm3/gdm-x-session[3400]: (EE) NVIDIA(0): 
recover...
  May 07 19:35:52 ap kernel: NVRM: GPU at PCI::01:00: 
GPU-d9fbb72e-29cb-d4db-ad8f-af242c1a6c15
  May 07 19:35:52 ap kernel: NVRM: Xid (PCI::01:00): 13, Graphics 
Exception: Class 0x0 Subchannel 0x0 Mismatch
  May 07 19:35:52 ap kernel: NVRM: Xid (PCI::01:00): 13, Graphics 
Exception: ESR 0x4041b0=0x20
  May 07 19:35:52 ap kernel: NVRM: Xid (PCI::01:00): 13, Graphics 
Exception: ESR 0x404000=0x8002
  May 07 19:35:52 ap kernel: NVRM: Xid (PCI::01:00): 13, Graphics 
Exception: ChID 0008, Class 902d, Offset 0860, Data 
  May 07 19:35:52 ap kernel: NVRM: Xid (PCI::01:00): 32, Channel ID 
0008 intr 0200
  May 07 19:35:52 ap kernel: NVRM: Xid (PCI::01:00): 31, Ch 0009, intr 
5000. MMU Fault: ENGINE CE0 HUBCLIENT_CE0 faulted @ 0x1_005a. Fault is 
of type FAULT_PTE ACCESS_TYPE_READ
  May 07 19:35:52 ap /usr/lib/gdm3/gdm-x-session[3400]: (II) NVIDIA(0): Error 
recovery was successful.
  May 07 19:35:52 ap /usr/lib/gdm3/gdm-x-session[3400]: (EE) NVIDIA(0): The 
NVIDIA X driver has encountered an error; attempting to
  May 07 19:35:52 ap /usr/lib/gdm3/gdm-x-session[3400]: (EE) NVIDIA(0): 
recover...
  May 07 19:35:52 ap kernel: NVRM: Xid (PCI::01:00): 32, Channel ID 
000b intr 0200
  May 07 19:36:03 ap kernel: Asynchronous wait on fence 
NVIDIA:nvidia.prime:10ad97 timed out (hint:intel_atomic_commit_ready+0x0/0x50 
[i915])
  May 07 19:36:21 ap libvirtd[1863]: internal error: connection closed due to 
keepalive timeout
  May 07 19:36:41 ap kernel: BUG: unable to handle kernel paging request at 
f9a5c3ff8030
  May 07 19:36:41 ap kernel: #PF error: [normal kernel read fault]
  May 07 19:36:41 ap kernel: PGD 85c9cc067 P4D 85c9cc067 PUD 85c9cb067 PMD 0 
  May 07 19:36:41 ap kernel: Oops:  [#1] SMP PTI
  May 07 19:36:41 ap kernel: CPU: 7 PID: 31632 Comm: worker Tainted: P U  W 
 OE 5.1.0-050100-generic #201905052130
  May 07 19:36:41 ap kernel: Hardware name: Dell Inc. Precision 5530/0FP2W2, 
BIOS 1.10.1 04/26/2019
  May 07 19:36:41 ap kernel: RIP: 0010:compaction_alloc+0x589/0x890
  May 07 19:36:41 ap kernel: Code: 7d b0 41 83 e6 1f 41 83 c6 01 4d 39 fc 73 7b 
e9 57 01 00 00 4d 89 e2 49 c1 e2 06 4c 03 15 57 b9 18 01 4d 89 d7 4d 85 ff 74 
44 <41> 8b 47 30 25 80 00 00 f0 3d 00 00 00 f0 0
  May 07 19:36:41 ap kernel: RSP: 0018:b352435b34a0 EFLAGS: 00010286
  May 07 19:36:41 ap kernel: RAX: a03dfc7d5d00 RBX: b352435b36a0 RCX: 
003d
  May 07 19:36:41 ap kernel: RDX: 800ffe00 RSI:  RDI: 
a03dfc7cd1e0
  May 07 19:36:41 ap kernel: RBP: b352435b3538 R08:  R09: 
a03dfc7d5d00
  May 07 19:36:41 ap kernel: R10: f9a5c3ff8000 R11: b352435b3719 R12: 
800ffe00
  May 07 19:36:41 ap kernel: R13: 8010 R14: 0020 R15: 
f9a5c3ff8000
  May 07 19:36:41 ap kernel: FS:  7f28c17fa700() 
GS:a03ddc3c() knlGS:
  May 07 19:36:41 ap kernel: CS:  0010 DS:  ES:  CR0: 80050033
  May 07 19:36:41 ap kernel: CR2: f9a5c3ff8030 CR3: 00069e550003 CR4: 
003626e0
  May 07 19:36:41 ap kernel: DR0:  DR1:  DR2: 

  May 07 19:36:41 ap kernel: DR3:  DR6: fffe0ff0 DR7: 
0400
  May 07 19:36:41 ap kernel: Call Trace:
  May 07 19:36:41 ap kernel:  migrate_pages+0x107/0xb40
  May 07 19:36:41 ap kernel:  ? move_freelist_tail+0xd0/0xd0
  May 07 19:36:41 ap kernel:  ? isolate_freepages_block+0x370/0x370
  May 07 19:36:41 ap kernel:  compact_zone+0x752/0xd70
  May 07 19:36:41 ap kernel:  compact_zone_order+0xd8/0x120
  May 07 19:36:41 ap kernel:  try_to_compact_pages+0xb0/0x260
  May 07 19:36:41 ap kernel:  __alloc_pages_direct_compact+0x8c/0x170
  May 07 19:36:41 ap kernel:  __alloc_pages_slowpath+0x4b3/0xeb0
  May

[Kernel-packages] [Bug 1804481] Re: SecureBoot support for arm64

2019-05-10 Thread dann frazier

Marking critical, as this prevents X-Gene/uboot systems from booting

** Changed in: linux-signed-hwe-edge (Ubuntu Bionic)
 Assignee: (unassigned) => dann frazier (dannf)

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

Title:
  SecureBoot support for arm64

Status in linux package in Ubuntu:
  Fix Released
Status in linux-meta package in Ubuntu:
  In Progress
Status in linux-signed package in Ubuntu:
  Fix Released
Status in linux-signed-hwe-edge package in Ubuntu:
  New
Status in shim package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Triaged
Status in linux-meta source package in Bionic:
  Triaged
Status in linux-signed source package in Bionic:
  Triaged
Status in linux-signed-hwe-edge source package in Bionic:
  In Progress
Status in shim source package in Bionic:
  Fix Released
Status in shim-signed source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged
Status in linux-meta source package in Cosmic:
  Triaged
Status in linux-signed source package in Cosmic:
  Triaged
Status in linux-signed-hwe-edge source package in Cosmic:
  Invalid
Status in shim source package in Cosmic:
  Fix Released
Status in shim-signed source package in Cosmic:
  Triaged
Status in linux source package in Disco:
  Fix Released
Status in linux-meta source package in Disco:
  In Progress
Status in linux-signed source package in Disco:
  Fix Released
Status in linux-signed-hwe-edge source package in Disco:
  Invalid
Status in shim source package in Disco:
  Fix Released
Status in shim-signed source package in Disco:
  Fix Released

Bug description:
  [Impact]
  Ubuntu does not currently support SecureBoot for UEFI systems on arm64 
platforms.

  [Test Case]
  See: https://wiki.ubuntu.com/UEFI/SecureBoot/Testing

  [Fix]
  - Introduce shim-signed for arm64
  - Introduce grub-signed for arm64
  - Produce signed linux kernels

  [Regression Risk]
  We're enabling new signed packages - regressions would most likely fall into 
packaging issues.

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

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

[Kernel-packages] [Bug 1804481] Re: SecureBoot support for arm64

2019-05-10 Thread dann frazier

Marking critical, as this prevents X-Gene/uboot systems from booting

** Changed in: linux-signed-hwe-edge (Ubuntu Bionic)
   Importance: Undecided => Critical

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

Title:
  SecureBoot support for arm64

Status in linux package in Ubuntu:
  Fix Released
Status in linux-meta package in Ubuntu:
  In Progress
Status in linux-signed package in Ubuntu:
  Fix Released
Status in linux-signed-hwe-edge package in Ubuntu:
  New
Status in shim package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Triaged
Status in linux-meta source package in Bionic:
  Triaged
Status in linux-signed source package in Bionic:
  Triaged
Status in linux-signed-hwe-edge source package in Bionic:
  In Progress
Status in shim source package in Bionic:
  Fix Released
Status in shim-signed source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged
Status in linux-meta source package in Cosmic:
  Triaged
Status in linux-signed source package in Cosmic:
  Triaged
Status in linux-signed-hwe-edge source package in Cosmic:
  Invalid
Status in shim source package in Cosmic:
  Fix Released
Status in shim-signed source package in Cosmic:
  Triaged
Status in linux source package in Disco:
  Fix Released
Status in linux-meta source package in Disco:
  In Progress
Status in linux-signed source package in Disco:
  Fix Released
Status in linux-signed-hwe-edge source package in Disco:
  Invalid
Status in shim source package in Disco:
  Fix Released
Status in shim-signed source package in Disco:
  Fix Released

Bug description:
  [Impact]
  Ubuntu does not currently support SecureBoot for UEFI systems on arm64 
platforms.

  [Test Case]
  See: https://wiki.ubuntu.com/UEFI/SecureBoot/Testing

  [Fix]
  - Introduce shim-signed for arm64
  - Introduce grub-signed for arm64
  - Produce signed linux kernels

  [Regression Risk]
  We're enabling new signed packages - regressions would most likely fall into 
packaging issues.

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

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

[Kernel-packages] [Bug 1828597] [NEW] KDump boot fails with nr_cpus=1

You have been subscribed to a public bug:

== Comment: #0 - Hari Krishna Bathini  - 2019-05-10 06:38:21 ==

---Problem Description---
kdump boots fails in some environments when nr_cpus=1 is passed 
 
---uname output---
na
 
Machine Type = na 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
 1. configure kdump
2. trigger crash on non-boot cpu

Expected result:
Capture dump and reboot

Actual result:
Hang in early kdump boot process after crash
 
Userspace tool common name: kdump-tools 
 
The userspace tool has the following bit modes: 64-bit 

Userspace rpm: kdump-tools

Userspace tool obtained from project website:  na

== Comment: #1 - Hari Krishna Bathini - 2019-05-10 06:45:46 ==
Launchpad bug 1560552 added "nr_cpus=1" support on ppc64 though
this change never made it upstream as maintainer has a few apprehensions..

With 4.18 kernels, this change is dropped on Ubuntu kernels too.
With nr_cpus=1 support in kernel, kdump-tools was also updated to
use "nr_cpsu=1" by default instead of "maxcpus=1" (see launchpad
bug 1568952). This kdump-tools change has to be reverted to make
it consist with the kernel change. Note that "nr_cpus=1 change had
a issues in kdump guest environment even with "nr_cpus=1" support
for kdump in kernel. So, even not withstanding the kernel revert, it is
better to default to "maxcpus=1" on all kernel versions. So, please
revert the kdump-tools fix that went in with launchpad bug 1568952

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


** Tags: architecture-ppc64le bugnameltc-177552 severity-high 
targetmilestone-inin---
-- 
KDump boot fails with nr_cpus=1
https://bugs.launchpad.net/bugs/1828597
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to kexec-tools 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 1828596] [NEW] kdump fails when crash is triggered after DLPAR cpu add operation

You have been subscribed to a public bug:

== Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 ==
---Problem Description---
kdump fails when crash is triggered after CPU add operation.
 
Machine Type = na 
 
---System Hang---
 Crashed in early boot process of kdump kernel after crash

Had to issue system reset from HMC to reclaim
 
---Steps to Reproduce---
 1. Configure kdump.
2. Add cpu from HMC.
3. Trigger crash.
4. Machine hangs after crash as below:

---
[169250.213166] IPI complete
[169250.234331] kexec: Starting switchover sequence.
I'm in purgatory
 --- STRUCK HERE ---
 
---uname output---
na
 
---Debugger---
A debugger is not configured

== Comment: #1 - Hari Krishna Bathini  - 2019-05-10 05:56:46 ==
The problem is, kexec udev rule to restart kdump-tools service - when a core is 
added,
is not being triggered. The old DT created by kexec (before the core is added)
is being used by KDump Kernel. So, when system crashes on a thread from
the added core(s), KDump kernel is failing to get the 'boot_cpuid' and
eventually failing to boot..

== Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 ==
The udev rule when CPU is added is not triggered because ppc64 does not
eject add/remove event when a CPU is hot added/removed. It only ejects
online/offline event to user space when CPU is hot added/removed.

So, the below udev rules are never triggered when needed:

SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"
SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

Also, with how CPU hot add & remove are handled in ppc64, a udev trigger
to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU
hot add case by updating the udev rule and drop the udev rule meant for CPU
hot remove in the kdump udev rules file:


SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

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


** Tags: architecture-ppc64le bugnameltc-177551 severity-high 
targetmilestone-inin---
-- 
kdump fails when crash is triggered after DLPAR cpu add operation
https://bugs.launchpad.net/bugs/1828596
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to kexec-tools 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 1828592] [NEW] Duplicate entry Exec and Path in scripts.

2019-05-10 Thread J.G.

Public bug reported:

Dear,
i was making a executable icon for pykaraoke_mini.py downloaded from github.com.
I noticed that in order to make executable work i was needed to put both full 
path to python executable in Exec variable and Path variable. In oder case the 
executable doesnt work.

Example:
[Desktop Entry]
Name=pyKaraoke mini
Version=0.75
Exec=~/pykaraoke-master/pykaraoke_mini.py
Terminal=false
Type=Application
Path=~/pykaraoke-master/

I was questioning it, because the pykaraoke deb packet seems to be not working.
The reason that pykaraoke doesn't want to play karaoke (.kar and .mid files) is 
when i run it from terminal it gives me error message:


unable to read font filename

so i guessed that python also can't find the path to the fonts used in
playing karaoke files in pykaraoke binary.

I maked a test by editing pykaraoke_mini.py lines:
font = pygame.font.Font(os.path.join(manager.FontPath, 
"DejaVuSansCondensed-Bold.ttf"), 12)

self.thinFont = pygame.font.Font(os.path.join(manager.FontPath,
"DejaVuSansCondensed.ttf"),

self.boldFont = pygame.font.Font(os.path.join(manager.FontPath,
"DejaVuSansCondensed-Bold.ttf"), fontSize)

self.titleFont = pygame.font.Font(os.path.join(manager.FontPath,
"DejaVuSansCondensed-Bold.ttf"), fontSize)

and

self.subtitleFont = pygame.font.Font(os.path.join(manager.FontPath,
"DejaVuSansCondensed.ttf"), fontSize)

by putting a full path to the selected fonts, by example:
manager.FontPath, 
"/usr/share/fonts/truetype/dejavu/DejaVuSansCondensed-Bold.ttf"

and pykaraoke_mini.py executed with no errors, but it didn't want to
play again because i think there are needed to be full paths entered in
other portions of the code, in order to make pykaraoke function
properly.

So i maked a conclusion that this is a linux bug.

Am i right or wrong?

Thank you,
greetings,
Igor

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


** Tags: linux python

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

Title:
  Duplicate entry Exec and Path in scripts.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Dear,
  i was making a executable icon for pykaraoke_mini.py downloaded from 
github.com.
  I noticed that in order to make executable work i was needed to put both full 
path to python executable in Exec variable and Path variable. In oder case the 
executable doesnt work.

  Example:
  [Desktop Entry]
  Name=pyKaraoke mini
  Version=0.75
  Exec=~/pykaraoke-master/pykaraoke_mini.py
  Terminal=false
  Type=Application
  Path=~/pykaraoke-master/

  I was questioning it, because the pykaraoke deb packet seems to be not 
working.
  The reason that pykaraoke doesn't want to play karaoke (.kar and .mid files) 
is when i run it from terminal it gives me error message:

  
  unable to read font filename

  so i guessed that python also can't find the path to the fonts used in
  playing karaoke files in pykaraoke binary.

  I maked a test by editing pykaraoke_mini.py lines:
  font = pygame.font.Font(os.path.join(manager.FontPath, 
"DejaVuSansCondensed-Bold.ttf"), 12)

  self.thinFont = pygame.font.Font(os.path.join(manager.FontPath,
  "DejaVuSansCondensed.ttf"),

  self.boldFont = pygame.font.Font(os.path.join(manager.FontPath,
  "DejaVuSansCondensed-Bold.ttf"), fontSize)

  self.titleFont = pygame.font.Font(os.path.join(manager.FontPath,
  "DejaVuSansCondensed-Bold.ttf"), fontSize)

  and

  self.subtitleFont = pygame.font.Font(os.path.join(manager.FontPath,
  "DejaVuSansCondensed.ttf"), fontSize)

  by putting a full path to the selected fonts, by example:
  manager.FontPath, 
"/usr/share/fonts/truetype/dejavu/DejaVuSansCondensed-Bold.ttf"

  and pykaraoke_mini.py executed with no errors, but it didn't want to
  play again because i think there are needed to be full paths entered
  in other portions of the code, in order to make pykaraoke function
  properly.

  So i maked a conclusion that this is a linux bug.

  Am i right or wrong?

  Thank you,
  greetings,
  Igor

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

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

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

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

Title:
  Duplicate entry Exec and Path in scripts.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Dear,
  i was making a executable icon for pykaraoke_mini.py downloaded from 
github.com.
  I noticed that in order to make executable work i was needed to put both full 
path to python executable in Exec variable and Path variable. In oder case the 
executable doesnt work.

  Example:
  [Desktop Entry]
  Name=pyKaraoke mini
  Version=0.75
  Exec=~/pykaraoke-master/pykaraoke_mini.py
  Terminal=false
  Type=Application
  Path=~/pykaraoke-master/

  I was questioning it, because the pykaraoke deb packet seems to be not 
working.
  The reason that pykaraoke doesn't want to play karaoke (.kar and .mid files) 
is when i run it from terminal it gives me error message:

  
  unable to read font filename

  so i guessed that python also can't find the path to the fonts used in
  playing karaoke files in pykaraoke binary.

  I maked a test by editing pykaraoke_mini.py lines:
  font = pygame.font.Font(os.path.join(manager.FontPath, 
"DejaVuSansCondensed-Bold.ttf"), 12)

  self.thinFont = pygame.font.Font(os.path.join(manager.FontPath,
  "DejaVuSansCondensed.ttf"),

  self.boldFont = pygame.font.Font(os.path.join(manager.FontPath,
  "DejaVuSansCondensed-Bold.ttf"), fontSize)

  self.titleFont = pygame.font.Font(os.path.join(manager.FontPath,
  "DejaVuSansCondensed-Bold.ttf"), fontSize)

  and

  self.subtitleFont = pygame.font.Font(os.path.join(manager.FontPath,
  "DejaVuSansCondensed.ttf"), fontSize)

  by putting a full path to the selected fonts, by example:
  manager.FontPath, 
"/usr/share/fonts/truetype/dejavu/DejaVuSansCondensed-Bold.ttf"

  and pykaraoke_mini.py executed with no errors, but it didn't want to
  play again because i think there are needed to be full paths entered
  in other portions of the code, in order to make pykaraoke function
  properly.

  So i maked a conclusion that this is a linux bug.

  Am i right or wrong?

  Thank you,
  greetings,
  Igor

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

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

[Kernel-packages] [Bug 1827335] Re: Unable to put offline CPU back online on Bionic/B-hwe-edge P9

2019-05-10 Thread Manoj Iyer

Po-Hsu Lin, could you please tell me the release and the kernel version
used?

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

Title:
  Unable to put offline CPU back online on Bionic/B-hwe-edge P9

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

Bug description:
  You will see these CPUs in offline state after boot.

  ubuntu@baltar:~$ cat /sys/devices/system/cpu/offline
  156-159

  ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu156/online
  1
  tee: /sys/devices/system/cpu/cpu156/online: Invalid argument
  ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu157/online
  1
  tee: /sys/devices/system/cpu/cpu157/online: Invalid argument
  ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu158/online
  1
  tee: /sys/devices/system/cpu/cpu158/online: Invalid argument
  ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu159/online
  1
  tee: /sys/devices/system/cpu/cpu159/online: Invalid argument

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-14-generic 5.0.0-14.15~18.04.1+signed1
  ProcVersionSignature: Ubuntu 5.0.0-14.15~18.04.1-generic 5.0.6
  Uname: Linux 5.0.0-14-generic ppc64le
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: ppc64el
  Date: Thu May  2 06:46:36 2019
  ProcLoadAvg: 0.00 0.00 0.00 1/1298 6496
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 5.0.0-14-generic (buildd@bos02-ppc64el-014) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #15~18.04.1-Ubuntu SMP Thu Apr 25 
18:55:27 UTC 2019
  SourcePackage: linux-signed-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 40
  cpu_coreson: Number of cores online = 39
  cpu_dscr: DSCR is 16
  cpu_freq:
   min: 2.862 GHz (cpu 79)
   max: 2.945 GHz (cpu 81)
   avg: 2.903 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=4

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

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

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

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

Title:
  dell xps 9570 wifi reconnection issue followed by freeze + Ubuntu
  18.04.2 LTS

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello Team,

  Env - Dell XPS 9570
Ubuntu 18.04.2 , HWE kernel

  We are facing intermittently wifi reconnection issue on Ubuntu 18.04.
  Software upgrade is up-to date. Also some time we facing freezing
  issue due to this hard reset required to make machine back to normal.

  Please let me know if there are any known issue with this particular
  model on 18.04 ? Please let me know.

  Thanks
  Jay

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

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

[Kernel-packages] [Bug 1802474] Re: test_map in ubuntu_bpf failed on 4.18 PowerPC

2019-05-10 Thread Po-Hsu Lin

On Disco the result is a bit different:
  libbpf: Error loading ELF section .BTF: -22. Ignored and continue.
  libbpf: object file doesn't contain bpf program

** Summary changed:

- test_map in ubuntu_bpf failed on 4.18 PowerPC
+ test_map in ubuntu_bpf failed on C/D PowerPC

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

Title:
  test_map in ubuntu_bpf failed on C/D PowerPC

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Confirmed

Bug description:
  The test_map test will fail with the following error on powerpc boxes:

  $ sudo ./test_maps 
  libbpf: object file doesn't contain bpf program
  Failed to load SK_SKB parse prog

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-11.12~18.04.1-generic 4.18.12
  Uname: Linux 4.18.0-11-generic ppc64le
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: ppc64el
  Date: Fri Nov  9 08:37:46 2018
  ProcLoadAvg: 0.18 0.51 0.47 1/1615 14440
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.18.0-11-generic (buildd@bos02-ppc64el-012) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #12~18.04.1-Ubuntu SMP Thu Oct 25 
12:58:39 UTC 2018
  SourcePackage: linux-signed-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 3.694 GHz (cpu 159)
   max: 3.695 GHz (cpu 1)
   avg: 3.694 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802474/+subscriptions

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

[Kernel-packages] [Bug 1822937] Re: NVIDIA settings won't write to /etc/xorg

2019-05-10 Thread Sebastien Bacher

** Changed in: nvidia-settings (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  NVIDIA settings won't write to /etc/xorg

Status in nvidia-settings package in Ubuntu:
  Confirmed

Bug description:
  I tried running it with root (`sudo nvidia-settings`) and without.

  I also generated an xorg file with `nvidia-xconfig`, and do the same
  thing, but it still won't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nvidia-settings 418.56-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr  3 00:33:48 2019
  InstallationDate: Installed on 2019-04-02 (0 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
  SourcePackage: nvidia-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1828564] Re: Update brcmfmac43455-sdio for rpi3b+/a+

2019-05-10 Thread Seth Forshee

For SRU we need a justification -- fixing specific bugs, important new
functionality, etc. Having "quite old" firmware is not sufficient
justification. If you wish for newer firmware to be included in bionic
please specify what bugs or features necessitate the update.

We also have to be sure that the firmware has been licensed in a way
that allows distribution in our linux-firmware package. We can be sure
that the firmware in upstream linux-firmware has been, but we've found
in the past that sometimes the licensing situation with raspi firmware
files is unclear. Please specify which specific firmware files are
required, and if not from upstream linux-firmware what license they have
for distribution. Thanks!

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

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

Title:
  Update brcmfmac43455-sdio for rpi3b+/a+

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  The firmware identified is used on Raspberry Pi devices that are
  reference devices for Ubuntu Core. The firmware currently carried in
  Bionic is quite old:

  brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Mar  1 2015
  07:29:38 version 7.45.18 (r538002) FWID 01-6a2c8ad4

  For comparison Raspbian has:

  brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Feb 27 2018
  03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04

  Could the newer firmware be made available in bionic updates?

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

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

[Kernel-packages] [Bug 1828248] Re: [linux-azure] Storage performance drop on RAID

2019-05-10 Thread Marcelo Cerri

I built a test kernel reverting the commit that Joe has mention:

https://kernel.ubuntu.com/~mhcerri/azure/xenial-linux-
azure-4.15.0-1044.48+1828248/

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

Title:
   [linux-azure] Storage performance drop on RAID

Status in linux-azure package in Ubuntu:
  New

Bug description:
  In Azure, FIO 4k tests are showing performance drops on latest proposed 
4.15.0 linux-azure kernels - from 52K IOPS to ~38K IOPS (max value reached on 
both sequential and random read tests).
  The setup used is 12 disks in RAID0.
  The affected kernels are:
  Ubuntu 14.04 + 4.15.0-1043
  Ubuntu 16.04 + 4.15.0-1044

  Previous kernel versions had reached max IOPS, ~52K IOPS on both read
  tests (e.g. 16.04 + 4.15.0-1043 kernel). Right now, it seems like the
  issue is in the diff from 1043 kernel on trusty vs 1044 kernel on
  xenial.

  The 52K IOPS is expected at qdepth=256. The repro cmd (as ran by the 
automation) is this:
  fio --size=1023G --direct=1 --ioengine=libaio --filename=/dev/md0 
--overwrite=1 --readwrite=randread --bs=4K --runtime=300 --iodepth=32 
--numjob=8 --output-format=json 
--output=/root/FIOLog/jsonLog/fio-result-randread-4K-256td.json --name='repro'

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

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

[Kernel-packages] [Bug 1828578] [NEW] dell xps 9570 wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS

Public bug reported:

Hello Team,

Env - Dell XPS 9570
  Ubuntu 18.04.2 , HWE kernel

We are facing intermittently wifi reconnection issue on Ubuntu 18.04.
Software upgrade is up-to date. Also some time we facing freezing issue
due to this hard reset required to make machine back to normal.

Please let me know if there are any known issue with this particular
model on 18.04 ? Please let me know.

Thanks
Jay

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

Title:
  dell xps 9570 wifi reconnection issue followed by freeze + Ubuntu
  18.04.2 LTS

Status in linux package in Ubuntu:
  New

Bug description:
  Hello Team,

  Env - Dell XPS 9570
Ubuntu 18.04.2 , HWE kernel

  We are facing intermittently wifi reconnection issue on Ubuntu 18.04.
  Software upgrade is up-to date. Also some time we facing freezing
  issue due to this hard reset required to make machine back to normal.

  Please let me know if there are any known issue with this particular
  model on 18.04 ? Please let me know.

  Thanks
  Jay

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

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

[Kernel-packages] [Bug 1828469] Re: Touchpad does not work on Trekstor Primebook C13B

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

Title:
  Touchpad does not work on Trekstor Primebook C13B

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  TrekStor Primebook C13B notebook appears to boot (Ubuntu 19.04) only when 
"noapic" is added to the kernel command line. Touchpad has an integrated 
fingerprint-reader and is detected as "i2c-SYNA3602:00" but does not work at 
all.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rober  1361 F pulseaudio
   /dev/snd/controlC1:  rober  1361 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-22 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: TREKSTOR Primebook C13B
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=d5915a80-bcac-46b7-ab8e-36e6b6d36162 ro noapic i2c-hid.debug=1 
hid.debug=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: CFALKSW02_BIOS_1.1.1
  dmi.board.asset.tag: Default string
  dmi.board.name: ALK_V03_CFALKSW02
  dmi.board.vendor: TS_weibu
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 31
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrCFALKSW02_BIOS_1.1.1:bd11/21/2018:svnTREKSTOR:pnPrimebookC13B:pvrDefaultstring:rvnTS_weibu:rnALK_V03_CFALKSW02:rvrDefaultstring:cvnDefaultstring:ct31:cvrDefaultstring:
  dmi.product.family: Primebook
  dmi.product.name: Primebook C13B
  dmi.product.sku: CFALKSW02
  dmi.product.version: Default string
  dmi.sys.vendor: TREKSTOR

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

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

[Kernel-packages] [Bug 1823216] Re: [trusty] 3.13.0-167-generic repeatedly trips kernel paging request BUG:

2019-05-10 Thread Liz Fong-Jones

And Trusty is now desupported, so going to close this as obsolete.

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

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

Title:
  [trusty] 3.13.0-167-generic repeatedly trips kernel paging request
  BUG:

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Invalid

Bug description:
  While trying to diagnose a problem with getting a kernel BUG: Bad page
  map in process retriever (retriever is the name of our serving
  binary), causing the serving binary to crash, we tried upgrading from
  3.13.0-121-generic to 3.13.0-167-generic and instead started more
  regularly tripping a different bug that hardlocks the system when we
  attempt to stop & restart the affected process.

  We are running Trusty on AWS in i3.xlarge instances.

  BUG: unable to handle kernel paging request at eaf0
  [89149.537277] IP: [] _raw_spin_lock+0xe/0x50
  [89149.543462] PGD 0
  [89149.545919] Oops: 0002 [#1] SMP
  [89149.549887] Modules linked in: 8021q garp stp mrp llc dm_crypt 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel serio_raw isofs aesni_intel 
aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd psmouse nvme ena floppy
  [89149.574925] CPU: 3 PID: 21681 Comm: retriever Not tainted 
3.13.0-167-generic #217-Ubuntu
  [89149.583168] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [89149.589649] task: 8807f2f7e000 ti: 88015b674000 task.ti: 
88015b674000
  [89149.597338] RIP: 0010:[]  [] 
_raw_spin_lock+0xe/0x50
  [89149.605845] RSP: :88015b675d88  EFLAGS: 00010206
  [89149.611431] RAX: 0002 RBX: 00c0dee00020 RCX: 
f000cf53
  [89149.618873] RDX: 8800 RSI: 00c0 RDI: 
eaf0
  [89149.626336] RBP: 88015b675d88 R08: 3fe0 R09: 
00a9
  [89149.633705] R10:  R11: f000ff53f000ff53 R12: 
880037471900
  [89149.641019] R13: 8807f49c57b8 R14: 8807f2eb2680 R15: 
eaf0
  [89149.648287] FS:  7f92262dd700() GS:88081fc6() 
knlGS:
  [89149.657764] CS:  0010 DS:  ES:  CR0: 80050033
  [89149.664294] CR2: eaf0 CR3: 0007f438 CR4: 
00160670
  [89149.672158] DR0:  DR1:  DR2: 

  [89149.680246] DR3:  DR6: fffe0ff0 DR7: 
0400
  [89149.688126] Stack:
  [89149.690903]  88015b675e20 811831fe 81e85225 
8807f2eb2680
  [89149.700310]  88015b675f20 88015b675e10 0007 
f000cf53
  [89149.709739]  00a9 f000ff53f000ff53 8800 
8003
  [89149.719331] Call Trace:
  [89149.722581]  [] handle_mm_fault+0x27e/0xfb0
  [89149.729984]  [] __do_page_fault+0x183/0x570
  [89149.737506]  [] ? do_futex+0x10a/0x760
  [89149.744529]  [] ? set_next_entity+0x95/0xb0
  [89149.752059]  [] ? pick_next_task_fair+0x5f/0x1b0
  [89149.76]  [] ? sched_clock_cpu+0xb5/0x100
  [89149.767489]  [] do_page_fault+0x1a/0x70
  [89149.774460]  [] page_fault+0x28/0x30
  [89149.781134] Code: 00 00 55 48 89 e5 f0 81 07 00 00 10 00 48 89 f7 57 9d 0f 
1f 44 00 00 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 b8 00 00 02 00  0f 
c1 07 89 c2 c1 ea 10 66 39 c2 75 02 5d c3 83 e2 fe 0f b7
  [89149.820963] RIP  [] _raw_spin_lock+0xe/0x50
  [89149.828646]  RSP 
  [89149.833460] CR2: eaf0
  [89149.843886] ---[ end trace 5e5ae13dbb1d0f6e ]---

  BUG: unable to handle kernel paging request at eaf0
  [66384.498399] IP: [] _raw_spin_lock+0xe/0x50
  [66384.502611] PGD 0
  [66384.504586] Oops: 0002 [#1] SMP
  [66384.507578] Modules linked in: 8021q garp stp mrp llc dm_crypt 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel serio_raw isofs aesni_intel 
aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd psmouse nvme ena floppy
  [66384.525392] CPU: 1 PID: 21144 Comm: retriever Not tainted 
3.13.0-167-generic #217-Ubuntu
  [66384.531418] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [66384.535812] task: 88074a9a9800 ti: 8807f411e000 task.ti: 
8807f411e000
  [66384.542092] RIP: 0010:[]  [] 
_raw_spin_lock+0xe/0x50
  [66384.548699] RSP: :8807f411fd88  EFLAGS: 00010206
  [66384.552560] RAX: 0002 RBX: 00c2b0c0 RCX: 
f000cf53
  [66384.557499] RDX: 8800 RSI: 00c0 RDI: 
eaf0
  [66384.562419] RBP: 8807f411fd88 R08: 3fe0 R09: 
00a9
  [66384.567450] R10:  R11: f000ff53f000ff53 R12: 
8807f4af9f00
  [66384.572935] R13: 8807f2ed9c30 R14: 8807f3ee2680 R15: 
eaf0
  [66384.578165] FS:  7f9886ac4700() GS:88081fc2() 
knlGS:
  [66384.584224] CS:  0010 DS:  ES:  CR0:

[Kernel-packages] [Bug 1827750] Re: Not boot with EFI

2019-05-10 Thread Alex Smith

** Tags added: efi raspberry raspi2 uefi

** Tags added: raspberrypi

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

Title:
  Not boot with EFI

Status in linux-raspi2 package in Ubuntu:
  Fix Committed

Bug description:
  Hello. I can't boot with linux-raspi2 kernel, but linux-generic work fine. 
Please add support kernel option CONFIG_U(EFI)_STUB=y as default.
  Thanks.

  os: ubuntu 18.04 lts arm64
  hw: raspberry pi 3b (+ tiano core uefi)

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

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

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

This change was made by a bot.

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

** Tags added: cosmic

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

Title:
  Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless
  acpi=off and noapic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Booting an Ubuntu 18.04.2 LTS amd64 installer USB on a Clevo P650RE3
  results in a hang shortly after the desktop is presented, unless
  acpi=off and noapic (or nolapic) are given as kernel boot parameters.
  The same installer runs without issue on other machines and the 16.04
  installer runs without issue on the P650RE3.

  Without passing acpi=off and noapic, a desktop comes up and a terminal
  can be obtained, but keystrokes and mouse clicks are not responded to
  after a small number of seconds. The mouse pointer continues to move
  with trackpad input.

  With careful timing I was able to obtain, uname, dmidecode and (an
  empty) lspci output. I was not able to obtain any /proc/acpi
  information, but do have dmesg. These are all attached. With acpi=off
  and noapic, I can get lspci and dmidecode output, but obviously no
  /proc/acpi. In this case the lspci output is not impty and dmidecode
  is identical to the failing case.

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

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

[Kernel-packages] [Bug 1828568] Re: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic

** Attachment added: "dmidecode.txt"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+attachment/5262933/+files/dmidecode.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/1828568

Title:
Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless
acpi=off and noapic

Status in linux package in Ubuntu:
Confirmed

Bug description:
Booting an Ubuntu 18.04.2 LTS amd64 installer USB on a Clevo P650RE3
results in a hang shortly after the desktop is presented, unless
acpi=off and noapic (or nolapic) are given as kernel boot parameters.
The same installer runs without issue on other machines and the 16.04
installer runs without issue on the P650RE3.

Without passing acpi=off and noapic, a desktop comes up and a terminal
can be obtained, but keystrokes and mouse clicks are not responded to
after a small number of seconds. The mouse pointer continues to move
with trackpad input.

With careful timing I was able to obtain, uname, dmidecode and (an
empty) lspci output. I was not able to obtain any /proc/acpi
information, but do have dmesg. These are all attached. With acpi=off
and noapic, I can get lspci and dmidecode output, but obviously no
/proc/acpi. In this case the lspci output is not impty and dmidecode
is identical to the failing case.

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

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

[Kernel-packages] [Bug 1828568] Re: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic

acpi.tar.bz was not obtainable

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

Title:
  Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless
  acpi=off and noapic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Booting an Ubuntu 18.04.2 LTS amd64 installer USB on a Clevo P650RE3
  results in a hang shortly after the desktop is presented, unless
  acpi=off and noapic (or nolapic) are given as kernel boot parameters.
  The same installer runs without issue on other machines and the 16.04
  installer runs without issue on the P650RE3.

  Without passing acpi=off and noapic, a desktop comes up and a terminal
  can be obtained, but keystrokes and mouse clicks are not responded to
  after a small number of seconds. The mouse pointer continues to move
  with trackpad input.

  With careful timing I was able to obtain, uname, dmidecode and (an
  empty) lspci output. I was not able to obtain any /proc/acpi
  information, but do have dmesg. These are all attached. With acpi=off
  and noapic, I can get lspci and dmidecode output, but obviously no
  /proc/acpi. In this case the lspci output is not impty and dmidecode
  is identical to the failing case.

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

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

[Kernel-packages] [Bug 1828568] Re: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic

** Attachment added: "lspci output for working 16.04 system on same hardware"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+attachment/5262936/+files/lspci-16.04.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/1828568

Title:
Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless
acpi=off and noapic

Status in linux package in Ubuntu:
Confirmed

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

[Kernel-packages] [Bug 1828568] [NEW] Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic

Public bug reported:

Booting an Ubuntu 18.04.2 LTS amd64 installer USB on a Clevo P650RE3
results in a hang shortly after the desktop is presented, unless
acpi=off and noapic (or nolapic) are given as kernel boot parameters.
The same installer runs without issue on other machines and the 16.04
installer runs without issue on the P650RE3.

Without passing acpi=off and noapic, a desktop comes up and a terminal
can be obtained, but keystrokes and mouse clicks are not responded to
after a small number of seconds. The mouse pointer continues to move
with trackpad input.

With careful timing I was able to obtain, uname, dmidecode and (an
empty) lspci output. I was not able to obtain any /proc/acpi
information, but do have dmesg. These are all attached. With acpi=off
and noapic, I can get lspci and dmidecode output, but obviously no
/proc/acpi. In this case the lspci output is not impty and dmidecode is
identical to the failing case.

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


** Tags: cosmic

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

Title:
  Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless
  acpi=off and noapic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Booting an Ubuntu 18.04.2 LTS amd64 installer USB on a Clevo P650RE3
  results in a hang shortly after the desktop is presented, unless
  acpi=off and noapic (or nolapic) are given as kernel boot parameters.
  The same installer runs without issue on other machines and the 16.04
  installer runs without issue on the P650RE3.

  Without passing acpi=off and noapic, a desktop comes up and a terminal
  can be obtained, but keystrokes and mouse clicks are not responded to
  after a small number of seconds. The mouse pointer continues to move
  with trackpad input.

  With careful timing I was able to obtain, uname, dmidecode and (an
  empty) lspci output. I was not able to obtain any /proc/acpi
  information, but do have dmesg. These are all attached. With acpi=off
  and noapic, I can get lspci and dmidecode output, but obviously no
  /proc/acpi. In this case the lspci output is not impty and dmidecode
  is identical to the failing case.

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

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

[Kernel-packages] [Bug 1828568] Re: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic

** Attachment added: "/proc/acpi for working 16.04 system on same hardware"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+attachment/5262938/+files/acpi-16.04.tar.bz

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

Title:
Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless
acpi=off and noapic

Status in linux package in Ubuntu:
Confirmed

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

[Kernel-packages] [Bug 1828568] Re: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic

** Attachment added: "dmesg from boot that results in hang"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+attachment/5262939/+files/dmesg.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/1828568

Title:
Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless
acpi=off and noapic

Status in linux package in Ubuntu:
Confirmed

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

[Kernel-packages] [Bug 1827750] [NEW] Not boot with EFI

You have been subscribed to a public bug by Alex Smith (diamondfrog):

Hello. I can't boot with linux-raspi2 kernel, but linux-generic work fine. 
Please add support kernel option CONFIG_U(EFI)_STUB=y as default.
Thanks.

os: ubuntu 18.04 lts arm64
hw: raspberry pi 3b (+ tiano core uefi)

** Affects: linux-raspi2 (Ubuntu)
 Importance: Undecided
 Assignee: Paolo Pisati (p-pisati)
 Status: Fix Committed


** Tags: efi kernel-bug raspberry raspberrypi raspi2 uefi
-- 
Not boot with EFI
https://bugs.launchpad.net/bugs/1827750
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to the bug report.

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

[Kernel-packages] [Bug 1828568] Re: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic

** Attachment added: "uname.txt"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+attachment/5262932/+files/uname.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/1828568

Title:
Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless
acpi=off and noapic

Status in linux package in Ubuntu:
Confirmed

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

[Kernel-packages] [Bug 1828568] Re: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic

** Attachment added: "uname for working 16.04 system on same hardware"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+attachment/5262935/+files/uname-16.04.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/1828568

Title:
Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless
acpi=off and noapic

Status in linux package in Ubuntu:
Confirmed

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

[Kernel-packages] [Bug 1828568] Re: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic

lspci.txt is empty

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

Title:
  Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless
  acpi=off and noapic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Booting an Ubuntu 18.04.2 LTS amd64 installer USB on a Clevo P650RE3
  results in a hang shortly after the desktop is presented, unless
  acpi=off and noapic (or nolapic) are given as kernel boot parameters.
  The same installer runs without issue on other machines and the 16.04
  installer runs without issue on the P650RE3.

  Without passing acpi=off and noapic, a desktop comes up and a terminal
  can be obtained, but keystrokes and mouse clicks are not responded to
  after a small number of seconds. The mouse pointer continues to move
  with trackpad input.

  With careful timing I was able to obtain, uname, dmidecode and (an
  empty) lspci output. I was not able to obtain any /proc/acpi
  information, but do have dmesg. These are all attached. With acpi=off
  and noapic, I can get lspci and dmidecode output, but obviously no
  /proc/acpi. In this case the lspci output is not impty and dmidecode
  is identical to the failing case.

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

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

[Kernel-packages] [Bug 1828568] Re: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic

** Attachment added: "dmidecode output for working 16.04 system on same
hardware"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+attachment/5262937/+files/dmidecode-16.04.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/1828568

Title:
Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless
acpi=off and noapic

Status in linux package in Ubuntu:
Confirmed

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

[Kernel-packages] [Bug 1828568] Re: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic

** Attachment added: "lspci output with acpi=off noapic boot"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+attachment/5262934/+files/lspci-acpi%3Doff-noapic.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/1828568

Title:
Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless
acpi=off and noapic

Status in linux package in Ubuntu:
Confirmed

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

[Kernel-packages] [Bug 1828564] [NEW] Update brcmfmac43455-sdio for rpi3b+/a+

2019-05-10 Thread Jonathan Cave

Public bug reported:

The firmware identified is used on Raspberry Pi devices that are
reference devices for Ubuntu Core. The firmware currently carried in
Bionic is quite old:

brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Mar  1 2015
07:29:38 version 7.45.18 (r538002) FWID 01-6a2c8ad4

For comparison Raspbian has:

brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Feb 27 2018
03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04

Could the newer firmware be made available in bionic updates?

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

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

Title:
  Update brcmfmac43455-sdio for rpi3b+/a+

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  The firmware identified is used on Raspberry Pi devices that are
  reference devices for Ubuntu Core. The firmware currently carried in
  Bionic is quite old:

  brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Mar  1 2015
  07:29:38 version 7.45.18 (r538002) FWID 01-6a2c8ad4

  For comparison Raspbian has:

  brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Feb 27 2018
  03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04

  Could the newer firmware be made available in bionic updates?

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

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

[Kernel-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

So, I tested with a 4.18 kernel and I could still reproduce the issue on
eoan. Then, I tested on a bionic system, 4.15 kernel, systemd 237, glibc
2.27, and I see a failure on malloc, also memory corruption.

This appears on the backtrace.
3738malloc_printerr ("malloc(): memory corruption");

I am going back to xenial.

Cascardo.

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
   Status: Confirmed

** Also affects: systemd (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: udisks2 (Ubuntu Eoan)
   Importance: Undecided
   Status: New

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

** Also affects: systemd (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: udisks2 (Ubuntu Disco)
   Importance: Undecided
   Status: New

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

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

** Also affects: udisks2 (Ubuntu Bionic)
   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/1814373

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in udisks2 package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  New
Status in udisks2 source package in Bionic:
  New
Status in linux source package in Disco:
  New
Status in systemd source package in Disco:
  New
Status in udisks2 source package in Disco:
  New
Status in linux source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  New
Status in udisks2 source package in Eoan:
  New

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

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

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

[Kernel-packages] [Bug 1814069] Re: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2

2019-05-10 Thread ToXinE

ok thanks for your help !

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

Title:
  kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2

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

Bug description:
  === SRU Justification ===

  [Impact]
  NULL pointer dereference in netvsc_probe(). Module hv_netvsc is included
  in initramfs, so this blocks the boot process.

  For Hyper-V only supports single channel, rndis_filter_device_add()
  bails early and jump to tag "out". Subsequent code calls
  rndis_filter_device_remove() and returns ERR_PTR(ret), where ret is
  0 (sucess). Because of that, it passes IS_ERR(nvdev) check in
  netvsc_probe() and cause a NULL pointer dereference, as nvdev now is 0:

  ...
  if (nvdev->num_chn > 1)
  schedule_work(>subchan_work);

  [Fix]
  Correctly return net_device at the end of rndis_filter_device_add().

  [Test]
  Users report positive result.

  [Regression Potenial]
  Low. Trivial change, patches are in upstream sometime.

  === Original Bug Report ===

  Ubuntu stuck on booting on HyperV Server 2008R2.
  I saw kernel messages, seems to load ram image the boot is stuck.
  Seems to be a problem with hyperv drivers propably harddrive.
  Reverted back to the previous kernel.

  Description:Ubuntu 18.04.1 LTS
  Release:18.04Description:Ubuntu 18.04.1 LTS
  Release:18.04
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 31 08:52 seq
   crw-rw 1 root audio 116, 33 Jan 31 08:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=86036ccb-bc11-11e8-93c9-00155dfd7535 ro maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/19/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090004
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 8531-7125-9206-2460-7819-2663-90
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090004:bd03/19/2009:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1788098] Re: Avoid migration issues with aligned 2MB THB

2019-05-10 Thread Juerg Haefliger

Leonardo, can you elaborate on the 'other possible issues'? We're
hesitant to pull 18 patches into a stable kernel under the assumption
that they *might* fix some *potential* issues, without clear evidence.
If you can test the single-patch kernel and report back that there are
still issues then that's a much stronger case for the other patches.

Commit 'KVM: PPC: Book3S HV: Avoid crash from THP collapse during radix
page fault' that you're asking for requires all these additional
backports to apply cleanly. Which makes me wonder if we're not actually
introducing a problem with these backports just to fix it again later.
Not saying that's the case, just wondering...

Also, the following seem to be totally unrelated and unnecessary:
  - KVM: PPC: Remove unused kvm_unmap_hva callback
  - powerpc/mm/radix: Remove unused code

While looking through the patches I also noticed that the following is the 
second patch of a series of 11 but it's the only one from the series that 
you're backporting.
  - powerpc/kvm: Switch kvm pmd allocator to custom allocator
Its commit message mentions subsequent patches of that series so I'm wondering 
why we need/want only this single patch??

Remember that we have to support this kernel for years and years to come
so we only want to backport the absolute necessary.

Lastly and FYI, the following is the minimal subset of your patches that all 
cherry-pick cleanly:
  - KVM: PPC: Book3S HV: Avoid crash from THP collapse during radix page fault
  - KVM: PPC: Book3S HV: Don't use compound_order to determine host mapping size
  - KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()
  - KVM: PPC: Book3S HV: radix: Refine IO region partition scope attributes
  - KVM: PPC: Book3S HV: Use __gfn_to_pfn_memslot() in page fault handler
  - KVM: PPC: Book3S HV: Handle 1GB pages in radix page fault handler
  - KVM: PPC: Book3S HV: Streamline setting of reference and change bits
  - KVM: PPC: Book3S HV: Radix page fault handler optimizations

Please provide some context why we need all the above (and potentially
more).

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

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

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

[Kernel-packages] [Bug 1828302] Re: CSR Bluetooth driver: Insufficient performance compared to WIndows driver

2019-05-10 Thread Luca Mastromatteo

So it looks like it's just a common interference problem with USB 3.0,
sorry for that.

I got confused because on Windows it looks like the USB 3.0 device (hard
disk) I got near the bluetooth adapter is switched off until I open a
file in it, while on Linux it looks like it's always not, so it's not a
bug but an interference.

You can close this, sorry for bothering you

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

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

Title:
  CSR Bluetooth driver: Insufficient performance compared to WIndows
  driver

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I'm reporting this because I'm pretty sure a class 2 bluetooth adapter
  shouldn't be unable to connect at less than 1 meter, when comparing
  this to the Windows driver at least...

  The bluetooth device is a CSR USB bluetooth 2.1 adapter

  hci1: Type: Primary  Bus: USB
   BD Address: 00:15:83:xx:xx:xx  ACL MTU: 310:10  SCO MTU: 64:8
   UP RUNNING PSCAN
   RX bytes:667 acl:0 sco:0 events:49 errors:0
   TX bytes:4783 acl:0 sco:0 commands:48 errors:0
   Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x83
   Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
   Link policy: RSWITCH HOLD SNIFF PARK
   Link mode: SLAVE ACCEPT
   Name: 'luky-XPS-15-9550 #2
   Class: 0x3c010c
   Service Classes: Rendering, Capturing, Object Transfer, Audio
   Device Class: Computer, Laptop
   HCI Version: 2.1 (0x4)  Revision: 0x149c
   LMP Version: 2.1 (0x4)  Subversion: 0x149c
   Manufacturer: Cambridge Silicon Radio (10)

  the kernel driver in use is `btusb`
  the ubuntu version is 19.04
  the kernel version is 5.0.0-13-generic

  In Windows this adapter work normally, on Ubuntu Linux it's barely
  able to connect to any device and maintain a stable connection, it
  completely loses the connection unlikely in Windows after more than 40
  centimeters

  Already tried the 5.1 mainline kernel, it doesn't seem different

  Worth noting that I also tried this on my laptop, and here looks like
  it works insanely better than my desktop pc...

  My desktop PC has a Ryzen 5 1600 CPU, and an MSI b350 mobo
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luky   1581 F pulseaudio
   /dev/snd/controlC1:  luky   1581 F pulseaudio
   /dev/snd/pcmC1D0c:   luky   1581 F...m pulseaudio
   /dev/snd/controlC2:  luky   1581 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-05-07 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Release amd64 
(20190416)
  IwConfig:
   enp24s0   no wireless extensions.
   
   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7A37
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=5756c217-a2d2-4100-b7c1-b38264030191 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   3: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.K0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350M MORTAR (MS-7A37)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 4
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.K0:bd01/22/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MMORTAR(MS-7A37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct4:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A37
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Kernel-packages] [Bug 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore

Hi, Hari.

Thanks a lot for the updates. No problem about the confusion. I will
mark this one as verified, then, and follow up with the other bugs.

Thank you very much.
Cascardo.

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore':
  Bad address when trying to dump vmcore

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in makedumpfile source package in Xenial:
  New
Status in linux source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Invalid
Status in makedumpfile source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Invalid
Status in makedumpfile source package in Disco:
  Fix Released

Bug description:
  [Impact]
  After a DLPAR memory/CPU add/remove operation, kdump tools need to be 
restarted or else kdump tools will fail to capture the crash. 

  [Test]

  == Comment: #0 - Ping Tian Han  - 2017-01-09 02:51:00 ==
  ---Problem Description---
  Vmcore cannot be saved when triggering bug 150353 on roselp4:

  Copying data   : [  2.0 %] \/usr/sbin/kdump-config: line 
591:  5502 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [  512.833872] kdump-tools[5450]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [  573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad 
address
  [  573.605717] kdump-tools[5450]:  * kdump-tools: failed to save vmcore in 
/var/crash/201701090223
  [  573.765417] kdump-tools[5450]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701090223/dmesg.201701090223
  [  574.285506] kdump-tools[5450]: The kernel version is not supported.
  [  574.285672] kdump-tools[5450]: The makedumpfile operation may be 
incomplete.
  [  574.285767] kdump-tools[5450]: The dmesg log is saved to 
/var/crash/201701090223/dmesg.201701090223.
  [  574.305422] kdump-tools[5450]: makedumpfile Completed.
  [  574.315363] kdump-tools[5450]:  * kdump-tools: saved dmesg content in 
/var/crash/201701090223
  [  574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600
  [  574.705384] kdump-tools[5450]: Rebooting.
   Stopping ifup for ib0...
  [  OK  ] Stopped ifup for ib0.
  [ 1008.579897] reboot: Restarting system

  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie
  Mitsuyoshi/carri...@us.ibm.com

  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = lpar

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. config kdump on roselp4
  2. try to trigger bug 150353

  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan  -
  2017-01-10 02:42:25 ==

  root@roselp4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic 
root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet 
crashkernel=384M-:512M

  root@roselp4:~# dmesg | grep Reser
  [0.00] Reserving 512MB of memory at 128MB for crashkernel (System 
RAM: 21760MB)

  [Regression Potential]
  The fix applies to makedumpfile, and could impact dump capture.

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

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

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

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

Title:
  psci in ubuntu_kvm_unit_tests failed with Disco ARM64

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
   TESTNAME=psci TIMEOUT=90s ACCEL= ./arm/run arm/psci.flat -smp $MAX_SMP
   FAIL psci (4 tests, 1 unexpected failures)

  # MAX_SMP=48
  # TESTNAME=psci TIMEOUT=90s ACCEL= ./arm/run arm/psci.flat -smp $MAX_SMP
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults 
-machine virt,gic-version=host,accel=kvm -cpu host -device virtio-serial-device 
-device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev 
-display none -serial stdio -kernel arm/psci.flat -smp 48 # -initrd 
/tmp/tmp.XqPOvHgIuL
  INFO: PSCI version 1.0
  PASS: invalid-function
  PASS: affinity-info-on
  PASS: affinity-info-off
  INFO: unexpected cpu_on return value: caller=CPU46, ret=-2
  FAIL: cpu-on
  SUMMARY: 4 tests, 1 unexpected failures

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: User Name 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  9 08:43 seq
   crw-rw 1 root audio 116, 33 May  9 08:43 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   
  Date: Fri May 10 11:31:36 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:
   
  ProcFB:
   0 EFI VGA
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=d4e5f461-24ef-47d8-a67f-42c82ff1efe8 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 0
  dmi.chassis.vendor: Cavium
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
  dmi.product.family: Default string
  dmi.product.name: ThunderX CRB
  dmi.product.sku: Default string
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cavium

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1828545/+subscriptions

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

[Kernel-packages] [Bug 1828545] [NEW] psci in ubuntu_kvm_unit_tests failed with Disco ARM64

2019-05-10 Thread Po-Hsu Lin

Public bug reported:

 TESTNAME=psci TIMEOUT=90s ACCEL= ./arm/run arm/psci.flat -smp $MAX_SMP
 FAIL psci (4 tests, 1 unexpected failures)

# MAX_SMP=48
# TESTNAME=psci TIMEOUT=90s ACCEL= ./arm/run arm/psci.flat -smp $MAX_SMP
timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults 
-machine virt,gic-version=host,accel=kvm -cpu host -device virtio-serial-device 
-device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev 
-display none -serial stdio -kernel arm/psci.flat -smp 48 # -initrd 
/tmp/tmp.XqPOvHgIuL
INFO: PSCI version 1.0
PASS: invalid-function
PASS: affinity-info-on
PASS: affinity-info-off
INFO: unexpected cpu_on return value: caller=CPU46, ret=-2
FAIL: cpu-on
SUMMARY: 4 tests, 1 unexpected failures

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-13-generic 5.0.0-13.14
ProcVersionSignature: User Name 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic aarch64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 May  9 08:43 seq
 crw-rw 1 root audio 116, 33 May  9 08:43 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu27
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:
 
Date: Fri May 10 11:31:36 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: Cavium ThunderX CRB
PciMultimedia:
 
ProcFB:
 0 EFI VGA
 1 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=d4e5f461-24ef-47d8-a67f-42c82ff1efe8 ro
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-13-generic N/A
 linux-backports-modules-5.0.0-13-generic  N/A
 linux-firmware1.178
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.11
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: To be filled by O.E.M.
dmi.board.vendor: To be filled by O.E.M.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 0
dmi.chassis.vendor: Cavium
dmi.chassis.version: To be filled by O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
dmi.product.family: Default string
dmi.product.name: ThunderX CRB
dmi.product.sku: Default string
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Cavium

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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


** Tags: apport-bug arm64 disco uec-images

** Also affects: ubuntu-kernel-tests
   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/1828545

Title:
  psci in ubuntu_kvm_unit_tests failed with Disco ARM64

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  New

Bug description:
   TESTNAME=psci TIMEOUT=90s ACCEL= ./arm/run arm/psci.flat -smp $MAX_SMP
   FAIL psci (4 tests, 1 unexpected failures)

  # MAX_SMP=48
  # TESTNAME=psci TIMEOUT=90s ACCEL= ./arm/run arm/psci.flat -smp $MAX_SMP
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults 
-machine virt,gic-version=host,accel=kvm -cpu host -device virtio-serial-device 
-device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev 
-display none -serial stdio -kernel arm/psci.flat -smp 48 # -initrd 
/tmp/tmp.XqPOvHgIuL
  INFO: PSCI version 1.0
  PASS: invalid-function
  PASS: affinity-info-on
  PASS: affinity-info-off
  INFO: unexpected cpu_on return value: caller=CPU46, ret=-2
  FAIL: cpu-on
  SUMMARY: 4 tests, 1 unexpected failures

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: User Name 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  9 08:43 seq
   crw-rw 1 root audio 116, 33 May  9 08:43 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   
  Date: Fri May 10 11:31:36 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Cavium ThunderX CRB

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

--- Comment From hbath...@in.ibm.com 2019-05-10 07:10 EDT---
(In reply to comment #53)
[...]
> could proceed with the SRU, and open a new bug to fix the CPU hotplug case,
> if there is one.

Raised bug 177551 to follow-up on the problem in CPU hot-add case which
is currently being screened internally. Will update the launchpad bug number
once we have it..

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore':
  Bad address when trying to dump vmcore

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in makedumpfile source package in Xenial:
  New
Status in linux source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Invalid
Status in makedumpfile source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Invalid
Status in makedumpfile source package in Disco:
  Fix Released

Bug description:
  [Impact]
  After a DLPAR memory/CPU add/remove operation, kdump tools need to be 
restarted or else kdump tools will fail to capture the crash. 

  [Test]

  == Comment: #0 - Ping Tian Han  - 2017-01-09 02:51:00 ==
  ---Problem Description---
  Vmcore cannot be saved when triggering bug 150353 on roselp4:

  Copying data   : [  2.0 %] \/usr/sbin/kdump-config: line 
591:  5502 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [  512.833872] kdump-tools[5450]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [  573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad 
address
  [  573.605717] kdump-tools[5450]:  * kdump-tools: failed to save vmcore in 
/var/crash/201701090223
  [  573.765417] kdump-tools[5450]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701090223/dmesg.201701090223
  [  574.285506] kdump-tools[5450]: The kernel version is not supported.
  [  574.285672] kdump-tools[5450]: The makedumpfile operation may be 
incomplete.
  [  574.285767] kdump-tools[5450]: The dmesg log is saved to 
/var/crash/201701090223/dmesg.201701090223.
  [  574.305422] kdump-tools[5450]: makedumpfile Completed.
  [  574.315363] kdump-tools[5450]:  * kdump-tools: saved dmesg content in 
/var/crash/201701090223
  [  574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600
  [  574.705384] kdump-tools[5450]: Rebooting.
   Stopping ifup for ib0...
  [  OK  ] Stopped ifup for ib0.
  [ 1008.579897] reboot: Restarting system

  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie
  Mitsuyoshi/carri...@us.ibm.com

  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = lpar

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. config kdump on roselp4
  2. try to trigger bug 150353

  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan  -
  2017-01-10 02:42:25 ==

  root@roselp4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic 
root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet 
crashkernel=384M-:512M

  root@roselp4:~# dmesg | grep Reser
  [0.00] Reserving 512MB of memory at 128MB for crashkernel (System 
RAM: 21760MB)

  [Regression Potential]
  The fix applies to makedumpfile, and could impact dump capture.

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

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

[Kernel-packages] [Bug 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore

--- Comment From hbath...@in.ibm.com 2019-05-10 06:43 EDT---
(In reply to comment #53)
> Hi, Hari.

Hi Cascardo,
> Is this fixed for the memory hotplug case? Can you verify that? Then, we
> could proceed with the SRU, and open a new bug to fix the CPU hotplug case,
> if there is one.

It does work for memory hotplug case. Sure.
Let me follow-up on the CPU hotplug issue with a separate bug..

> And what are those other issues/bugs you mention? Have they been mirrored
> yet to launchpad? Are they regressions against makedumpfile/kdump-tools on

No regression in the fix packages but issues observed while trying to validate 
them.
Pursuing them in separate bugs. Bug 177452 (mirrored as LP bug 1828187)
and Bug 177451 (being screened internally.. will let you know the LP bug # once 
it
is mirrored) Sorry if that confused you..

** Tags removed: verification-failed-bionic verification-needed 
verification-needed-cosmic
** Tags added: verification-done verification-done-bionic 
verification-done-cosmic

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore':
  Bad address when trying to dump vmcore

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in makedumpfile source package in Xenial:
  New
Status in linux source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Invalid
Status in makedumpfile source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Invalid
Status in makedumpfile source package in Disco:
  Fix Released

Bug description:
  [Impact]
  After a DLPAR memory/CPU add/remove operation, kdump tools need to be 
restarted or else kdump tools will fail to capture the crash. 

  [Test]

  == Comment: #0 - Ping Tian Han  - 2017-01-09 02:51:00 ==
  ---Problem Description---
  Vmcore cannot be saved when triggering bug 150353 on roselp4:

  Copying data   : [  2.0 %] \/usr/sbin/kdump-config: line 
591:  5502 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [  512.833872] kdump-tools[5450]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [  573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad 
address
  [  573.605717] kdump-tools[5450]:  * kdump-tools: failed to save vmcore in 
/var/crash/201701090223
  [  573.765417] kdump-tools[5450]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701090223/dmesg.201701090223
  [  574.285506] kdump-tools[5450]: The kernel version is not supported.
  [  574.285672] kdump-tools[5450]: The makedumpfile operation may be 
incomplete.
  [  574.285767] kdump-tools[5450]: The dmesg log is saved to 
/var/crash/201701090223/dmesg.201701090223.
  [  574.305422] kdump-tools[5450]: makedumpfile Completed.
  [  574.315363] kdump-tools[5450]:  * kdump-tools: saved dmesg content in 
/var/crash/201701090223
  [  574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600
  [  574.705384] kdump-tools[5450]: Rebooting.
   Stopping ifup for ib0...
  [  OK  ] Stopped ifup for ib0.
  [ 1008.579897] reboot: Restarting system

  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie
  Mitsuyoshi/carri...@us.ibm.com

  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = lpar

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. config kdump on roselp4
  2. try to trigger bug 150353

  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan  -
  2017-01-10 02:42:25 ==

  root@roselp4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic 
root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet 
crashkernel=384M-:512M

  root@roselp4:~# dmesg | grep Reser
  [0.00] Reserving 512MB of memory at 128MB for crashkernel (System 
RAM: 21760MB)

  [Regression Potential]
  The fix applies to makedumpfile, and could impact dump capture.

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

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

[Kernel-packages] [Bug 1818881] Re: ath10k_pci crashing

** Changed in: linux (Ubuntu)
 Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned)

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

Title:
  ath10k_pci crashing

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  The below happens on a regular basis on my DELL XPS 13 9380:

  [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 
[ath10k_core]
  [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 
85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 
db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 
  [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246
  [77451.338533] RAX:  RBX: 9d97b7c12290 RCX: 
9d96cbfd5528
  [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 
9d9944c51de0
  [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: 

  [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 
9d9944c51520
  [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 
9d996e503e28
  [77451.338540] FS:  () GS:9d996e50() 
knlGS:
  [77451.338541] CS:  0010 DS:  ES:  CR0: 80050033
  [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 
003606e0
  [77451.338543] Call Trace:
  [77451.338545]  
  [77451.338557]  ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core]
  [77451.338561]  ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci]
  [77451.338563]  ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci]
  [77451.338567]  ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci]
  [77451.338571]  net_rx_action+0x140/0x3a0
  [77451.338575]  __do_softirq+0xe4/0x2d4
  [77451.338580]  irq_exit+0xc5/0xd0
  [77451.338582]  do_IRQ+0x8a/0xe0
  [77451.338585]  common_interrupt+0xf/0xf
  [77451.338586]  
  [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0
  [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 
31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d 
d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 
  [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: 
ffde
  [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 
001f
  [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: 

  [77451.338625] RBP: af4601993e90 R08: 0002 R09: 
000224c0
  [77451.338626] R10: af4601993e20 R11: 00d9 R12: 
0004
  [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: 

  [77451.338630]  cpuidle_enter+0x17/0x20
  [77451.338632]  call_cpuidle+0x23/0x40
  [77451.338634]  do_idle+0x204/0x280
  [77451.338636]  cpu_startup_entry+0x73/0x80
  [77451.338639]  start_secondary+0x1ab/0x200
  [77451.338642]  secondary_startup_64+0xa5/0xb0
  [77451.338643] ---[ end trace 22914e3b3a848f81 ]---
  [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2

  $ uname -a
  Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  $ modinfo ath10k_pci
  filename:   
/lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko
  firmware:   ath10k/QCA9377/hw1.0/board.bin
  firmware:   ath10k/QCA9377/hw1.0/firmware-5.bin
  firmware:   ath10k/QCA9377/hw1.0/firmware-6.bin
  firmware:   ath10k/QCA6174/hw3.0/board-2.bin
  firmware:   ath10k/QCA6174/hw3.0/board.bin
  firmware:   ath10k/QCA6174/hw3.0/firmware-6.bin
  firmware:   ath10k/QCA6174/hw3.0/firmware-5.bin
  firmware:   ath10k/QCA6174/hw3.0/firmware-4.bin
  firmware:   ath10k/QCA6174/hw2.1/board-2.bin
  firmware:   ath10k/QCA6174/hw2.1/board.bin
  firmware:   ath10k/QCA6174/hw2.1/firmware-5.bin
  firmware:   ath10k/QCA6174/hw2.1/firmware-4.bin
  firmware:   ath10k/QCA9887/hw1.0/board-2.bin
  firmware:   ath10k/QCA9887/hw1.0/board.bin
  firmware:   ath10k/QCA9887/hw1.0/firmware-5.bin
  firmware:   ath10k/QCA988X/hw2.0/board-2.bin
  firmware:   ath10k/QCA988X/hw2.0/board.bin
  firmware:   ath10k/QCA988X/hw2.0/firmware-5.bin
  firmware:   ath10k/QCA988X/hw2.0/firmware-4.bin
  firmware:   ath10k/QCA988X/hw2.0/firmware-3.bin
  firmware:   ath10k/QCA988X/hw2.0/firmware-2.bin
  license:Dual BSD/GPL
  description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB 
devices
  author: Qualcomm Atheros
  srcversion: D49EBAB0107B6CE28383BB8
  alias:  pci:v168Cd0050sv*sd*bc*sc*i*
  alias:  pci:v168Cd0042sv*sd*bc*sc*i*
  alias:  pci:v168Cd0046sv*sd*bc*sc*i*
  alias:  pci:v168Cd0056sv*sd*bc*sc*i*
  alias:

[Kernel-packages] [Bug 1826036] Re: linux: 4.4.0-147.173 -proposed tracker

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1826034 (trusty/linux-aws), bug 1826035 
(trusty/linux-lts-xenial)
  derivatives: bug 1826024 (linux-aws), bug 1826028 (linux-kvm), bug 1826029 
(linux-raspi2), bug 1826030 (linux-snapdragon), bug 1826032 (linux-fips)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
- phase: Testing
- phase-changed: Friday, 26. April 2019 14:31 UTC
+ phase: Signoff
+ phase-changed: Friday, 10. May 2019 10:30 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Ongoing -- testing in progress
-   regression-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag 
present
security-signoff: Pending -- waiting for signoff

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

Title:
  linux: 4.4.0-147.173 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1826034 (trusty/linux-aws), bug 1826035 
(trusty/linux-lts-xenial)
  derivatives: bug 1826024 (linux-aws), bug 1826028 (linux-kvm), bug 1826029 
(linux-raspi2), bug 1826030 (linux-snapdragon), bug 1826032 (linux-fips)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Signoff
  phase-changed: Friday, 10. May 2019 10:30 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag 
present
security-signoff: Pending -- waiting for signoff

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

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

[Kernel-packages] [Bug 1827335] Re: Unable to put offline CPU back online on Bionic/B-hwe-edge P9

2019-05-10 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   Status: Fix Committed => Confirmed

** Changed in: linux (Ubuntu)
   Status: Fix Committed => 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/1827335

Title:
  Unable to put offline CPU back online on Bionic/B-hwe-edge P9

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

Bug description:
  You will see these CPUs in offline state after boot.

  ubuntu@baltar:~$ cat /sys/devices/system/cpu/offline
  156-159

  ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu156/online
  1
  tee: /sys/devices/system/cpu/cpu156/online: Invalid argument
  ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu157/online
  1
  tee: /sys/devices/system/cpu/cpu157/online: Invalid argument
  ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu158/online
  1
  tee: /sys/devices/system/cpu/cpu158/online: Invalid argument
  ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu159/online
  1
  tee: /sys/devices/system/cpu/cpu159/online: Invalid argument

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-14-generic 5.0.0-14.15~18.04.1+signed1
  ProcVersionSignature: Ubuntu 5.0.0-14.15~18.04.1-generic 5.0.6
  Uname: Linux 5.0.0-14-generic ppc64le
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: ppc64el
  Date: Thu May  2 06:46:36 2019
  ProcLoadAvg: 0.00 0.00 0.00 1/1298 6496
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 5.0.0-14-generic (buildd@bos02-ppc64el-014) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #15~18.04.1-Ubuntu SMP Thu Apr 25 
18:55:27 UTC 2019
  SourcePackage: linux-signed-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 40
  cpu_coreson: Number of cores online = 39
  cpu_dscr: DSCR is 16
  cpu_freq:
   min: 2.862 GHz (cpu 79)
   max: 2.945 GHz (cpu 81)
   avg: 2.903 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=4

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

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

[Kernel-packages] [Bug 1828469] Re: Touchpad does not work on Trekstor Primebook C13B

apport information

** Tags added: apport-collected

** Description changed:

- TrekStor Primebook C13B notebook appears to boot (Ubuntu 19.04) only
- when "noapic" is added to the kernel command line. Touchpad has an
- integrated fingerprint-reader and is detected as "i2c-SYNA3602:00" but
- does not work at all.
+ TrekStor Primebook C13B notebook appears to boot (Ubuntu 19.04) only when 
"noapic" is added to the kernel command line. Touchpad has an integrated 
fingerprint-reader and is detected as "i2c-SYNA3602:00" but does not work at 
all.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu27
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  rober  1361 F pulseaudio
+  /dev/snd/controlC1:  rober  1361 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 19.04
+ InstallationDate: Installed on 2019-04-22 (17 days ago)
+ InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
+ MachineType: TREKSTOR Primebook C13B
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=de_DE.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=d5915a80-bcac-46b7-ab8e-36e6b6d36162 ro noapic i2c-hid.debug=1 
hid.debug=1
+ ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
+ RelatedPackageVersions:
+  linux-restricted-modules-5.0.0-13-generic N/A
+  linux-backports-modules-5.0.0-13-generic  N/A
+  linux-firmware1.178
+ Tags:  disco
+ Uname: Linux 5.0.0-13-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 11/21/2018
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: CFALKSW02_BIOS_1.1.1
+ dmi.board.asset.tag: Default string
+ dmi.board.name: ALK_V03_CFALKSW02
+ dmi.board.vendor: TS_weibu
+ dmi.board.version: Default string
+ dmi.chassis.asset.tag: Default string
+ dmi.chassis.type: 31
+ dmi.chassis.vendor: Default string
+ dmi.chassis.version: Default string
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrCFALKSW02_BIOS_1.1.1:bd11/21/2018:svnTREKSTOR:pnPrimebookC13B:pvrDefaultstring:rvnTS_weibu:rnALK_V03_CFALKSW02:rvrDefaultstring:cvnDefaultstring:ct31:cvrDefaultstring:
+ dmi.product.family: Primebook
+ dmi.product.name: Primebook C13B
+ dmi.product.sku: CFALKSW02
+ dmi.product.version: Default string
+ dmi.sys.vendor: TREKSTOR

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

Title:
  Touchpad does not work on Trekstor Primebook C13B

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  TrekStor Primebook C13B notebook appears to boot (Ubuntu 19.04) only when 
"noapic" is added to the kernel command line. Touchpad has an integrated 
fingerprint-reader and is detected as "i2c-SYNA3602:00" but does not work at 
all.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rober  1361 F pulseaudio
   /dev/snd/controlC1:  rober  1361 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-22 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: TREKSTOR Primebook C13B
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=d5915a80-bcac-46b7-ab8e-36e6b6d36162 ro noapic i2c-hid.debug=1 
hid.debug=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: CFALKSW02_BIOS_1.1.1
  dmi.board.asset.tag: Default string
  dmi.board.name: ALK_V03_CFALKSW02
  dmi.board.vendor: TS_weibu
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 31
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias:

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

apport information

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

Title:
  Touchpad does not work on Trekstor Primebook C13B

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  TrekStor Primebook C13B notebook appears to boot (Ubuntu 19.04) only when 
"noapic" is added to the kernel command line. Touchpad has an integrated 
fingerprint-reader and is detected as "i2c-SYNA3602:00" but does not work at 
all.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rober  1361 F pulseaudio
   /dev/snd/controlC1:  rober  1361 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-22 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: TREKSTOR Primebook C13B
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=d5915a80-bcac-46b7-ab8e-36e6b6d36162 ro noapic i2c-hid.debug=1 
hid.debug=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: CFALKSW02_BIOS_1.1.1
  dmi.board.asset.tag: Default string
  dmi.board.name: ALK_V03_CFALKSW02
  dmi.board.vendor: TS_weibu
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 31
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrCFALKSW02_BIOS_1.1.1:bd11/21/2018:svnTREKSTOR:pnPrimebookC13B:pvrDefaultstring:rvnTS_weibu:rnALK_V03_CFALKSW02:rvrDefaultstring:cvnDefaultstring:ct31:cvrDefaultstring:
  dmi.product.family: Primebook
  dmi.product.name: Primebook C13B
  dmi.product.sku: CFALKSW02
  dmi.product.version: Default string
  dmi.sys.vendor: TREKSTOR

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

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

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

apport information

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

Title:
  Touchpad does not work on Trekstor Primebook C13B

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  TrekStor Primebook C13B notebook appears to boot (Ubuntu 19.04) only when 
"noapic" is added to the kernel command line. Touchpad has an integrated 
fingerprint-reader and is detected as "i2c-SYNA3602:00" but does not work at 
all.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rober  1361 F pulseaudio
   /dev/snd/controlC1:  rober  1361 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-22 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: TREKSTOR Primebook C13B
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=d5915a80-bcac-46b7-ab8e-36e6b6d36162 ro noapic i2c-hid.debug=1 
hid.debug=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: CFALKSW02_BIOS_1.1.1
  dmi.board.asset.tag: Default string
  dmi.board.name: ALK_V03_CFALKSW02
  dmi.board.vendor: TS_weibu
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 31
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrCFALKSW02_BIOS_1.1.1:bd11/21/2018:svnTREKSTOR:pnPrimebookC13B:pvrDefaultstring:rvnTS_weibu:rnALK_V03_CFALKSW02:rvrDefaultstring:cvnDefaultstring:ct31:cvrDefaultstring:
  dmi.product.family: Primebook
  dmi.product.name: Primebook C13B
  dmi.product.sku: CFALKSW02
  dmi.product.version: Default string
  dmi.sys.vendor: TREKSTOR

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

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

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

apport information

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

Title:
  Touchpad does not work on Trekstor Primebook C13B

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  TrekStor Primebook C13B notebook appears to boot (Ubuntu 19.04) only when 
"noapic" is added to the kernel command line. Touchpad has an integrated 
fingerprint-reader and is detected as "i2c-SYNA3602:00" but does not work at 
all.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rober  1361 F pulseaudio
   /dev/snd/controlC1:  rober  1361 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-22 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: TREKSTOR Primebook C13B
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=d5915a80-bcac-46b7-ab8e-36e6b6d36162 ro noapic i2c-hid.debug=1 
hid.debug=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: CFALKSW02_BIOS_1.1.1
  dmi.board.asset.tag: Default string
  dmi.board.name: ALK_V03_CFALKSW02
  dmi.board.vendor: TS_weibu
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 31
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrCFALKSW02_BIOS_1.1.1:bd11/21/2018:svnTREKSTOR:pnPrimebookC13B:pvrDefaultstring:rvnTS_weibu:rnALK_V03_CFALKSW02:rvrDefaultstring:cvnDefaultstring:ct31:cvrDefaultstring:
  dmi.product.family: Primebook
  dmi.product.name: Primebook C13B
  dmi.product.sku: CFALKSW02
  dmi.product.version: Default string
  dmi.sys.vendor: TREKSTOR

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

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

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

apport information

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

Title:
  Touchpad does not work on Trekstor Primebook C13B

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  TrekStor Primebook C13B notebook appears to boot (Ubuntu 19.04) only when 
"noapic" is added to the kernel command line. Touchpad has an integrated 
fingerprint-reader and is detected as "i2c-SYNA3602:00" but does not work at 
all.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rober  1361 F pulseaudio
   /dev/snd/controlC1:  rober  1361 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-22 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: TREKSTOR Primebook C13B
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=d5915a80-bcac-46b7-ab8e-36e6b6d36162 ro noapic i2c-hid.debug=1 
hid.debug=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: CFALKSW02_BIOS_1.1.1
  dmi.board.asset.tag: Default string
  dmi.board.name: ALK_V03_CFALKSW02
  dmi.board.vendor: TS_weibu
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 31
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrCFALKSW02_BIOS_1.1.1:bd11/21/2018:svnTREKSTOR:pnPrimebookC13B:pvrDefaultstring:rvnTS_weibu:rnALK_V03_CFALKSW02:rvrDefaultstring:cvnDefaultstring:ct31:cvrDefaultstring:
  dmi.product.family: Primebook
  dmi.product.name: Primebook C13B
  dmi.product.sku: CFALKSW02
  dmi.product.version: Default string
  dmi.sys.vendor: TREKSTOR

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

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

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

apport information

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

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

Title:
  Touchpad does not work on Trekstor Primebook C13B

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  TrekStor Primebook C13B notebook appears to boot (Ubuntu 19.04) only when 
"noapic" is added to the kernel command line. Touchpad has an integrated 
fingerprint-reader and is detected as "i2c-SYNA3602:00" but does not work at 
all.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rober  1361 F pulseaudio
   /dev/snd/controlC1:  rober  1361 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-22 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: TREKSTOR Primebook C13B
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=d5915a80-bcac-46b7-ab8e-36e6b6d36162 ro noapic i2c-hid.debug=1 
hid.debug=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: CFALKSW02_BIOS_1.1.1
  dmi.board.asset.tag: Default string
  dmi.board.name: ALK_V03_CFALKSW02
  dmi.board.vendor: TS_weibu
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 31
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrCFALKSW02_BIOS_1.1.1:bd11/21/2018:svnTREKSTOR:pnPrimebookC13B:pvrDefaultstring:rvnTS_weibu:rnALK_V03_CFALKSW02:rvrDefaultstring:cvnDefaultstring:ct31:cvrDefaultstring:
  dmi.product.family: Primebook
  dmi.product.name: Primebook C13B
  dmi.product.sku: CFALKSW02
  dmi.product.version: Default string
  dmi.sys.vendor: TREKSTOR

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

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

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

apport information

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

Title:
  Touchpad does not work on Trekstor Primebook C13B

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  TrekStor Primebook C13B notebook appears to boot (Ubuntu 19.04) only when 
"noapic" is added to the kernel command line. Touchpad has an integrated 
fingerprint-reader and is detected as "i2c-SYNA3602:00" but does not work at 
all.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rober  1361 F pulseaudio
   /dev/snd/controlC1:  rober  1361 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-22 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: TREKSTOR Primebook C13B
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=d5915a80-bcac-46b7-ab8e-36e6b6d36162 ro noapic i2c-hid.debug=1 
hid.debug=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: CFALKSW02_BIOS_1.1.1
  dmi.board.asset.tag: Default string
  dmi.board.name: ALK_V03_CFALKSW02
  dmi.board.vendor: TS_weibu
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 31
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrCFALKSW02_BIOS_1.1.1:bd11/21/2018:svnTREKSTOR:pnPrimebookC13B:pvrDefaultstring:rvnTS_weibu:rnALK_V03_CFALKSW02:rvrDefaultstring:cvnDefaultstring:ct31:cvrDefaultstring:
  dmi.product.family: Primebook
  dmi.product.name: Primebook C13B
  dmi.product.sku: CFALKSW02
  dmi.product.version: Default string
  dmi.sys.vendor: TREKSTOR

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

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

[Kernel-packages] [Bug 1826036] Re: linux: 4.4.0-147.173 -proposed tracker

2019-05-10 Thread Taihsiang Ho

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/xenial/4.4.0-147.173
/xenial-proposed-published.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   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/1826036

Title:
  linux: 4.4.0-147.173 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1826034 (trusty/linux-aws), bug 1826035 
(trusty/linux-lts-xenial)
  derivatives: bug 1826024 (linux-aws), bug 1826028 (linux-kvm), bug 1826029 
(linux-raspi2), bug 1826030 (linux-snapdragon), bug 1826032 (linux-fips)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 26. April 2019 14:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff

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

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

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

apport information

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

Title:
  Touchpad does not work on Trekstor Primebook C13B

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  TrekStor Primebook C13B notebook appears to boot (Ubuntu 19.04) only when 
"noapic" is added to the kernel command line. Touchpad has an integrated 
fingerprint-reader and is detected as "i2c-SYNA3602:00" but does not work at 
all.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rober  1361 F pulseaudio
   /dev/snd/controlC1:  rober  1361 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-22 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: TREKSTOR Primebook C13B
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=d5915a80-bcac-46b7-ab8e-36e6b6d36162 ro noapic i2c-hid.debug=1 
hid.debug=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: CFALKSW02_BIOS_1.1.1
  dmi.board.asset.tag: Default string
  dmi.board.name: ALK_V03_CFALKSW02
  dmi.board.vendor: TS_weibu
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 31
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrCFALKSW02_BIOS_1.1.1:bd11/21/2018:svnTREKSTOR:pnPrimebookC13B:pvrDefaultstring:rvnTS_weibu:rnALK_V03_CFALKSW02:rvrDefaultstring:cvnDefaultstring:ct31:cvrDefaultstring:
  dmi.product.family: Primebook
  dmi.product.name: Primebook C13B
  dmi.product.sku: CFALKSW02
  dmi.product.version: Default string
  dmi.sys.vendor: TREKSTOR

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

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

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

apport information

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

Title:
  Touchpad does not work on Trekstor Primebook C13B

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  TrekStor Primebook C13B notebook appears to boot (Ubuntu 19.04) only when 
"noapic" is added to the kernel command line. Touchpad has an integrated 
fingerprint-reader and is detected as "i2c-SYNA3602:00" but does not work at 
all.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rober  1361 F pulseaudio
   /dev/snd/controlC1:  rober  1361 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-22 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: TREKSTOR Primebook C13B
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=d5915a80-bcac-46b7-ab8e-36e6b6d36162 ro noapic i2c-hid.debug=1 
hid.debug=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: CFALKSW02_BIOS_1.1.1
  dmi.board.asset.tag: Default string
  dmi.board.name: ALK_V03_CFALKSW02
  dmi.board.vendor: TS_weibu
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 31
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrCFALKSW02_BIOS_1.1.1:bd11/21/2018:svnTREKSTOR:pnPrimebookC13B:pvrDefaultstring:rvnTS_weibu:rnALK_V03_CFALKSW02:rvrDefaultstring:cvnDefaultstring:ct31:cvrDefaultstring:
  dmi.product.family: Primebook
  dmi.product.name: Primebook C13B
  dmi.product.sku: CFALKSW02
  dmi.product.version: Default string
  dmi.sys.vendor: TREKSTOR

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

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

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

apport information

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

Title:
  Touchpad does not work on Trekstor Primebook C13B

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  TrekStor Primebook C13B notebook appears to boot (Ubuntu 19.04) only when 
"noapic" is added to the kernel command line. Touchpad has an integrated 
fingerprint-reader and is detected as "i2c-SYNA3602:00" but does not work at 
all.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rober  1361 F pulseaudio
   /dev/snd/controlC1:  rober  1361 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-22 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: TREKSTOR Primebook C13B
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=d5915a80-bcac-46b7-ab8e-36e6b6d36162 ro noapic i2c-hid.debug=1 
hid.debug=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: CFALKSW02_BIOS_1.1.1
  dmi.board.asset.tag: Default string
  dmi.board.name: ALK_V03_CFALKSW02
  dmi.board.vendor: TS_weibu
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 31
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrCFALKSW02_BIOS_1.1.1:bd11/21/2018:svnTREKSTOR:pnPrimebookC13B:pvrDefaultstring:rvnTS_weibu:rnALK_V03_CFALKSW02:rvrDefaultstring:cvnDefaultstring:ct31:cvrDefaultstring:
  dmi.product.family: Primebook
  dmi.product.name: Primebook C13B
  dmi.product.sku: CFALKSW02
  dmi.product.version: Default string
  dmi.sys.vendor: TREKSTOR

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

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

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