[Kernel-packages] [Bug 1629509] Re: Cannot mount overlay with upperdir on overlay

[Brett Randall]

To answer my own question above, I found these posts:
https://lkml.org/lkml/2018/1/8/81 .

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

Title:
  Cannot mount overlay with upperdir on overlay

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

Bug description:
  I have a docker setup using overlay as its storage driver. I mount an
  overlay in the container. Both the lower, upper and work directories
  are themselves on an overlay filesystem. This mount started to fail
  after upgrading to kernel 4.4.0-38 from 4.4.0-34 with the error
  message "overlayfs: filesystem on '/mnt/overlay/upper' not supported
  as upperdir".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shaw   2257 F pulseaudio
   /dev/snd/controlC1:  shaw   2257 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 30 20:06:03 2016
  HibernationDevice: RESUME=UUID=f23b927f-5173-43fe-9269-8c7714fb0927
  InstallationDate: Installed on 2016-07-23 (69 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. XPS13 9333
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=306f5ab9-de0e-4920-be20-3f4081e13c7e ro persistent quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/19/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd03/19/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04
  - LTS version

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to
  send or receive files via bluetooth,please do give a emulsion of this
  hardware problem

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun May  6 15:26:50 2018
  DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GconfCompiz:
   /apps/compiz-1/general:
 /apps/compiz-1/general/screen0:
  /apps/compiz-1/general/screen0/options:
   active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:81e5]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1366x768+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move', 'vpswitch', 
'place', 'animation', 'snap', 'compiztoolbox', 'imgpng', 'workarounds', 'expo', 
'fade', 'session', 'ezoom', 'switcher', 'scale', 'unityshell']"
  InstallationDate: Installed on 2016-11-07 (544 days ago)
  InstallationMedia:
   
  MachineType: HP HP 245 G5 Notebook PC
  MonitorsUser.xml:
   
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash
  SourcePackage: compiz
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago)
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81E5
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 73.15
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245
  dmi.product.name: HP 245 G5 Notebook PC
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1769443] Re: [RTL8723BE] Unable to receive files via Bluetooth

[Daniel van Vugt]

** Summary changed:

- [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 LTS 
version
+ [RTL8723BE] Unable to receive files via Bluetooth

** Summary changed:

- [RTL8723BE] Unable to receive files via Bluetooth
+ [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 - LTS 
version

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

Title:
  [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04
  - LTS version

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to
  send or receive files via bluetooth,please do give a emulsion of this
  hardware problem

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun May  6 15:26:50 2018
  DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GconfCompiz:
   /apps/compiz-1/general:
 /apps/compiz-1/general/screen0:
  /apps/compiz-1/general/screen0/options:
   active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:81e5]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1366x768+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move', 'vpswitch', 
'place', 'animation', 'snap', 'compiztoolbox', 'imgpng', 'workarounds', 'expo', 
'fade', 'session', 'ezoom', 'switcher', 'scale', 'unityshell']"
  InstallationDate: Installed on 2016-11-07 (544 days ago)
  InstallationMedia:
   
  MachineType: HP HP 245 G5 Notebook PC
  MonitorsUser.xml:
   
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash
  SourcePackage: compiz
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago)
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81E5
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 73.15
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245
  dmi.product.name: HP 245 G5 Notebook PC
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 219057] Re: Bluetooth does not coexist with WiFi

[Daniel van Vugt]

This bug looks old. Let's clean it up a little...

Users who experience this bug with the ath9k kernel driver please see
bug 1746164 for more recent news.

Greg Inozemtsev: If you still experience this bug then please run 'lspci
-k' and 'lsusb' on the machine and attach the output here.

Everyone else: Please report your own new bugs by running 'ubuntu-bug
bluez'.

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

** Changed in: bluez (Ubuntu)
   Importance: Wishlist => Medium

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

Title:
  Bluetooth does not coexist with WiFi

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  On my system bluetooth and wifi are unusable together. I have a built-
  in CSR-based bluetooth module in my laptop, and an Atheros wifi. Wifi
  transfers slow to a halt whenever there is BT traffic.

  For example, if I play a music file from another machine through the
  network using a BT headset, only the first few seconds of the file
  will play until the player runs out of buffered data. No further data
  is downloaded. Web pages also do not download, and I even lose
  connection to AP from time to time.

  At the same time, it looks like AFH is trying to work. If I monitor
  the value returned by 'hcitool afh', it changes. But this seems to
  have little effect on connection quality.

  Is this a problem with my hardware, or the AFH implementation? Is
  there a way to force bluetooth to not use the channels in use by WiFi?

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

-- 
Mailing list: https://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 1769443] Re: [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 LTS version

[punyabrat kumar]

No,other device such as bluetooth speaker, mouse,keyboard is not working as
well..

On Jul 24, 2018 9:36 AM, "Daniel van Vugt" 
wrote:

> Do other bluetooth devices work still? Like a mouse, keyboard or
> speaker?
>
> ** Changed in: bluez (Ubuntu)
>Status: Incomplete => New
>
> ** Changed in: linux (Ubuntu)
>Status: Incomplete => New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1769443
>
> Title:
>   [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04
>   LTS version
>
> Status in bluez package in Ubuntu:
>   Incomplete
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to
>   send or receive files via bluetooth,please do give a emulsion of this
>   hardware problem
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1
>   ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
>   Uname: Linux 4.15.0-20-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.9-0ubuntu7
>   Architecture: amd64
>   CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,
> snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,
> session,gnomecompat,animation,fade,staticswitcher,
> workarounds,scale,expo,ezoom,dbus]
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   CurrentDesktop: Unity:Unity7:ubuntu
>   Date: Sun May  6 15:26:50 2018
>   DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript:
> './xorg_fix_proprietary.py'
>   DistroCodename: bionic
>   DistroVariant: ubuntu
>   ExecutablePath: /usr/bin/compiz
>   GconfCompiz:
>/apps/compiz-1/general:
>  /apps/compiz-1/general/screen0:
>   /apps/compiz-1/general/screen0/options:
>active_plugins = [core,composite,opengl,
> compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,
> move,wall,grid,regex,imgpng,session,gnomecompat,animation,
> fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics]
> [1002:9851] (rev 40) (prog-if 00 [VGA controller])
>  Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics]
> [103c:81e5]
>   GsettingsChanges:
>b'org.compiz.core' b'outputs' b"['1366x768+0+0']"
>b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl',
> 'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move',
> 'vpswitch', 'place', 'animation', 'snap', 'compiztoolbox', 'imgpng',
> 'workarounds', 'expo', 'fade', 'session', 'ezoom', 'switcher', 'scale',
> 'unityshell']"
>   InstallationDate: Installed on 2016-11-07 (544 days ago)
>   InstallationMedia:
>
>   MachineType: HP HP 245 G5 Notebook PC
>   MonitorsUser.xml:
>
>
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic
> root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash
>   SourcePackage: compiz
>   UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago)
>   dmi.bios.date: 11/01/2016
>   dmi.bios.vendor: Insyde
>   dmi.bios.version: F.21
>   dmi.board.asset.tag: Base Board Asset Tag
>   dmi.board.name: 81E5
>   dmi.board.vendor: HP
>   dmi.board.version: KBC Version 73.15
>   dmi.chassis.asset.tag: Chassis Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: HP
>   dmi.chassis.version: Chassis Version
>   dmi.modalias: dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:
> pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:
> rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion:
>   dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245
>   dmi.product.name: HP 245 G5 Notebook PC
>   dmi.product.version: Type1ProductConfigId
>   dmi.sys.vendor: HP
>   version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
>   version.libdrm2: libdrm2 2.4.91-2
>   version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
>   version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.10.5-1ubuntu1
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20171229-1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.15-2
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/
> 1769443/+subscriptions
>

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

Title:
  [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04
  - LTS version

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug 

[Kernel-packages] [Bug 958661] Re: "Receive files over bluetooth" randomly stops working - plus setting should be available under BlueTooth settings

[Daniel van Vugt]

Please let us know if the problem persists for you and if so then what
Ubuntu version.

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

** Tags added: obex

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

Title:
  "Receive files over bluetooth" randomly stops working - plus setting
  should be available under BlueTooth settings

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I often send image files via bluetooth from my android phone to my
  ubuntu PC.

  It worked fine until yesterday, but now I systematically get "the
  remote bluetooth device rejected the request".

  Nothing has changed in the way I transfer files and I'm trying from
  the very same phone.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-16-generic 3.0.0-16.29
  ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
  Uname: Linux 3.0.0-16-generic i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  teo   32650 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
     Mixer name : 'Realtek ALC660-VD'
     Components : 'HDA:10ec0660,1043,0011 
HDA:10573055,10431316,00100700'
     Controls  : 25
     Simple ctrls  : 16
  Date: Sun Mar 18 17:55:36 2012
  HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: ASUSTeK Computer Inc. M51Sn
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-16-generic 
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-16-generic N/A
   linux-backports-modules-3.0.0-16-generic  N/A
   linux-firmware1.60.1
  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: Upgraded to oneiric on 2011-12-07 (101 days ago)
  UserAsoundrc:
   pcm.!default { type pulse }
   ctl.!default { type pulse }
   pcm.pulse { type pulse }
   ctl.pulse { type pulse }
  dmi.bios.date: 12/24/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: M51Sn
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: M51Sn
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

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

[Kernel-packages] [Bug 1769443] Re: [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 LTS version

[Daniel van Vugt]

** Tags added: obex

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

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

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

Title:
  [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04
  LTS version

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to
  send or receive files via bluetooth,please do give a emulsion of this
  hardware problem

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun May  6 15:26:50 2018
  DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GconfCompiz:
   /apps/compiz-1/general:
 /apps/compiz-1/general/screen0:
  /apps/compiz-1/general/screen0/options:
   active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:81e5]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1366x768+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move', 'vpswitch', 
'place', 'animation', 'snap', 'compiztoolbox', 'imgpng', 'workarounds', 'expo', 
'fade', 'session', 'ezoom', 'switcher', 'scale', 'unityshell']"
  InstallationDate: Installed on 2016-11-07 (544 days ago)
  InstallationMedia:
   
  MachineType: HP HP 245 G5 Notebook PC
  MonitorsUser.xml:
   
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash
  SourcePackage: compiz
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago)
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81E5
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 73.15
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245
  dmi.product.name: HP 245 G5 Notebook PC
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1731699] Re: Unable to transfer files via bluetooth to paired android phone

[Daniel van Vugt]

Please let us know if the problem persists for you and if so then what
Ubuntu version.

** Tags added: artful

** Tags added: obex

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

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

Title:
  Unable to transfer files via bluetooth to paired android phone

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to transfer files to my phone (Nexus 6P - Android 8.0) from
  Ubuntu 17.10, but when I pair the laptop and phone, I don't think it's
  pairing in a way which permits file transfers. When I pair, my phone
  gives me a checkbox "Allow xx to access your contacts and call
  history", but there is no option to allow file transfers.

  Then, when I attempt to transfer a file via Bluetooth from Ubuntu the
  transfer fails and I get the message "There was an error". My phone
  doesn't seem to recognise there's been any attempt to send a file.

  Discussed at https://ubuntuforums.org/showthread.php?t=2377286

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

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

[Kernel-packages] [Bug 1780872] Re: wake on lan is not working

[Kai-Heng Feng]

It's default off. Use parameter to turn it on: "alx.enable_wol=1"

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

Title:
  wake on lan is not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm dual-booting Ubuntu 18.04 and Windows 10. If I turn off my
  computer with Windows, I can turn it back on using wol. However, if I
  turn it off using Ubuntu the computer won't turn back on if I use wol.

  These are my network cards:

  ```
  ignacio@ignacio-XPS-8930:~$ ifconfig 
  docker0: flags=4163  mtu 1500
  inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
  inet6 fe80::42:e4ff:fe0a:9fee  prefixlen 64  scopeid 0x20
  ether 02:42:e4:0a:9f:ee  txqueuelen 0  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 165  bytes 24102 (24.1 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  enp4s0: flags=4163  mtu 1500
  inet 192.168.86.31  netmask 255.255.255.0  broadcast 192.168.86.255
  inet6 fe80::955b:12c8:20b9:7645  prefixlen 64  scopeid 0x20
  ether d8:9e:f3:85:42:8a  txqueuelen 1000  (Ethernet)
  RX packets 50484  bytes 52395285 (52.3 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 29166  bytes 4575560 (4.5 MB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  device interrupt 19  

  lo: flags=73  mtu 65536
  inet 127.0.0.1  netmask 255.0.0.0
  inet6 ::1  prefixlen 128  scopeid 0x10
  loop  txqueuelen 1000  (Local Loopback)
  RX packets 1124  bytes 95423 (95.4 KB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 1124  bytes 95423 (95.4 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  veth66fe4e4: flags=4163  mtu 1500
  inet6 fe80::2078:3ff:feb3:2aa1  prefixlen 64  scopeid 0x20
  ether 22:78:03:b3:2a:a1  txqueuelen 0  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 224  bytes 30503 (30.5 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  vethb50cc6f: flags=4163  mtu 1500
  inet6 fe80::5c0b:47ff:fef1:cfc9  prefixlen 64  scopeid 0x20
  ether 5e:0b:47:f1:cf:c9  txqueuelen 0  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 125  bytes 18006 (18.0 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  wlp3s0: flags=4099  mtu 1500
  ether 5c:ea:1d:4c:61:a7  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 0  bytes 0 (0.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  ```

  This is what ethtool tells me about my ethernet card:

  ```
  ignacio@ignacio-XPS-8930:~$ sudo ethtool enp4s0
  Settings for enp4s0:
Supported ports: [ TP ]
Supported link modes:   10baseT/Half 10baseT/Full 
100baseT/Half 100baseT/Full 
1000baseT/Full 
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes:  10baseT/Half 10baseT/Full 
100baseT/Half 100baseT/Full 
1000baseT/Full 
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Current message level: 0x60e4 (24804)
   link ifup rx_err tx_err hw wol
Link detected: yes

  ```

  And this is what happens when I try to activate wake on lan:

  
  ```
  ignacio@ignacio-XPS-8930:~$ sudo ethtool -s enp4s0 wol g
  Cannot get current wake-on-lan settings: Operation not supported
not setting wol
  ```

  Finally, this is the infor about my distro:

  ```
  ignacio@ignacio-XPS-8930:~$ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  ```

  Thanks for the help!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ethtool 1:4.15-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  9 18:58:08 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  

[Kernel-packages] [Bug 1769443] Re: [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 LTS version

[punyabrat kumar]

I'm  trying to send a music file or whatever from my Mobile to my
laptop,but unable to send files...it shows following

** Attachment added: "It shows connection unsuccessful as you can see"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769443/+attachment/5166937/+files/Screenshot_2018-07-24-09-44-23.png

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

Title:
  [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04
  LTS version

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to
  send or receive files via bluetooth,please do give a emulsion of this
  hardware problem

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun May  6 15:26:50 2018
  DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GconfCompiz:
   /apps/compiz-1/general:
 /apps/compiz-1/general/screen0:
  /apps/compiz-1/general/screen0/options:
   active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:81e5]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1366x768+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move', 'vpswitch', 
'place', 'animation', 'snap', 'compiztoolbox', 'imgpng', 'workarounds', 'expo', 
'fade', 'session', 'ezoom', 'switcher', 'scale', 'unityshell']"
  InstallationDate: Installed on 2016-11-07 (544 days ago)
  InstallationMedia:
   
  MachineType: HP HP 245 G5 Notebook PC
  MonitorsUser.xml:
   
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash
  SourcePackage: compiz
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago)
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81E5
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 73.15
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245
  dmi.product.name: HP 245 G5 Notebook PC
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1769443] Re: [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 LTS version

[punyabrat kumar]

But my laptops Bluetooth visibility and power is on...

** Attachment added: "As you can see...but unable to receive files from all 
mobiles or laptops I have tried"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769443/+attachment/5166938/+files/Screenshot%20from%202018-07-24%2009-42-31.png

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

Title:
  [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04
  LTS version

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to
  send or receive files via bluetooth,please do give a emulsion of this
  hardware problem

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun May  6 15:26:50 2018
  DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GconfCompiz:
   /apps/compiz-1/general:
 /apps/compiz-1/general/screen0:
  /apps/compiz-1/general/screen0/options:
   active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:81e5]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1366x768+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move', 'vpswitch', 
'place', 'animation', 'snap', 'compiztoolbox', 'imgpng', 'workarounds', 'expo', 
'fade', 'session', 'ezoom', 'switcher', 'scale', 'unityshell']"
  InstallationDate: Installed on 2016-11-07 (544 days ago)
  InstallationMedia:
   
  MachineType: HP HP 245 G5 Notebook PC
  MonitorsUser.xml:
   
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash
  SourcePackage: compiz
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago)
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81E5
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 73.15
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245
  dmi.product.name: HP 245 G5 Notebook PC
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1778087] Re: ELAN1200 touchpad jumps around and disconnects

[Jpphun]

i am having the same issue with Asus FX503v laptop, GTX1050. I am on
18.04 kernel 4.15.0.29. It was freezing whole computer up but adding
i8042.request into grub, freezing went away. It is still very sensitive
and opening one tab in chrome might open 6 at once. My touchpad is
Elan1200.

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

Title:
  ELAN1200 touchpad jumps around and disconnects

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is on an ASUS GL503VD laptop and would probably affect other ASUS
  laptops equipped with the ELAN1200 touchpad.

  I am on Kernel 4.17.2 because older kernels did not enable the
  touchpad at all(It was just unrecognized or i2c-hid stopped the
  computer from booting)

  The touchpad works but it has erratic behaviour and disconnects
  randomly. After it disconnects the only way to bring it back is to
  `modprobe -r hid-multitouch && modprobe hid-multitouch`

  Libinput and synaptics can handle the touchpad though I found
  synaptics to be more stable.

  dmesg gets spammed with this whenever I move the touchpad:
  [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report 
(16/65535)

  I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad
  Because from what I understand the "jumpy/disconnect" problem is associated 
to the incomplete reports and Mishurov managed to mitigate those. Unfortunately 
some symbols were deprecated in kernel 4.17.2 and it did not compile for my 
system.

  While I can use my touchpad as is right now, and "restart" it with
  modprobe when needed, it would be nice to have it function bug-free.
  (Right after I typed this my touchpad disconnected and I needed to
  modprobe again, I am considering making a cronjob for that)

  Let me know if anything else is needed. Will wait for an apport collection to 
add log files.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-10 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 4.17.2 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1758384] Re: [Acer AO532h] hibernate/resume failure

[Launchpad Bug Tracker]

[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/1758384

Title:
  [Acer AO532h] hibernate/resume failure

Status in linux package in Ubuntu:
  Expired

Bug description:
  I put the computer in hibernation using sudo pm-hibernate. Computer
  seemed to go into hibernation normally but didn't wake up properly.
  System hibernates properly under Artful. Disk has a proper 2gb swap
  partition.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13 [modified: 
boot/vmlinuz-4.15.0-12-generic]
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ka1ssr 1005 F pulseaudio
  Date: Fri Mar 23 12:36:52 2018
  DuplicateSignature: hibernate/resume:Acer AO532h:V1.26
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=600f4807-bc16-448c-9a8f-bf5330a75d9e
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180323)
  InterpreterPath: /usr/bin/python3.6
  MachineType: Acer AO532h
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=d2c54fce-ed1a-4448-b75b-94fad1b35afd ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  Title: [Acer AO532h] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 04/28/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.26
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: AO532h
  dmi.board.vendor: Acer
  dmi.board.version: V1.26
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.26
  dmi.modalias: 
dmi:bvnAcer:bvrV1.26:bd04/28/2011:svnAcer:pnAO532h:pvrV1.26:rvnAcer:rnAO532h:rvrV1.26:cvnAcer:ct10:cvrV1.26:
  dmi.product.family: Intel_Mobile
  dmi.product.name: AO532h
  dmi.product.version: V1.26
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1772573] Re: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned

[Launchpad Bug Tracker]

[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/1772573

Title:
  package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to
  install/upgrade: installed linux-image-4.15.0-20-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Expired

Bug description:
  Upgrade to newer kernel failed via command line, I used Synaptic and
  there were 2 broken packages  according to it. I removed/unmarked all
  but the current kernel "linux-image" files and that seems to have
  resolved the broken packages. I'm submitting this BEFORE I reboot just
  in case

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: qnx4 hfsplus hfs minix ntfs jfs rfcomm pci_stub bnep 
uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core 
videodev media rtsx_usb_ms memstick btusb btrtl btbcm btintel bluetooth 
rtl8723be btcoexist rtl8723_common rtl_pci rtlwifi mac80211 intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp cfg80211 snd_hda_codec_hdmi 
snd_hda_codec_conexant snd_hda_codec_generic snd_hda_intel snd_hda_codec 
intel_cstate intel_rapl_perf snd_hda_core mei_me mei lpc_ich ideapad_laptop 
sparse_keymap shpchp mac_hid rtsx_usb_sdmmc rtsx_usb nouveau i915 mxm_wmi r8169 
wmi
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Tue May 22 06:18:12 2018
  DpkgTerminalLog:
   Removing linux-modules-extra-4.15.0-20-generic (4.15.0-20.21) ...
   Removing linux-image-4.15.0-20-generic (4.15.0-20.21) ...
   E: Aborting removal of the running kernel
   dpkg: error processing package linux-image-4.15.0-20-generic (--remove):
installed linux-image-4.15.0-20-generic package pre-removal script 
subprocess returned error exit status 1
  DuplicateSignature:
   package:linux-image-4.15.0-20-generic:4.15.0-20.21
   Removing linux-image-4.15.0-20-generic (4.15.0-20.21) ...
   E: Aborting removal of the running kernel
   dpkg: error processing package linux-image-4.15.0-20-generic (--remove):
installed linux-image-4.15.0-20-generic package pre-removal script 
subprocess returned error exit status 1
  ErrorMessage: installed linux-image-4.15.0-20-generic package pre-removal 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2015-03-07 (1171 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: linux-signed
  Title: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to 
install/upgrade: installed linux-image-4.15.0-20-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-05-08 (13 days ago)

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

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

[Kernel-packages] [Bug 1773024] Re: Errors at boot

[Launchpad Bug Tracker]

[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/1773024

Title:
  Errors at boot

Status in linux package in Ubuntu:
  Expired

Bug description:
  LOGS DMESG:

  [0.048089] ACPI: Added _OSI(Module Device)
  [0.048090] ACPI: Added _OSI(Processor Device)
  [0.048091] ACPI: Added _OSI(3.0 _SCP Extensions)
  [0.048091] ACPI: Added _OSI(Processor Aggregator Device)
  [0.049587] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
  [0.049598] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
  [0.049607] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
  [0.049615] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
  [0.049676] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
  [0.049684] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
  [0.049692] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
  [0.049700] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
  [0.049760] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
  [0.049768] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
  [0.049776] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
  [0.049783] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
  [0.049843] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
  [0.049851] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
  [0.049859] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
  [0.049867] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
  [0.049925] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
  [0.049933] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
  [0.049941] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
  [0.049948] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
  [0.050008] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
  [0.050016] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
  [0.050024] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
  [0.050032] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
  [0.050091] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
  [0.050099] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
  [0.050107] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
  [0.050115] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
  [0.050173] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
  [0.050181] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
  [0.050190] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
  [0.050198] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
  [0.050258] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)
  [0.050267] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
  [0.050274] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
  [0.050282] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
  [0.050342] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
  [0.050350] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
  [0.050357] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
  [0.050365] ACPI Exception: Could not find/resolve named package 

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

[bugproxy]

--- Comment From p...@au1.ibm.com 2018-07-24 00:03 EDT---
There are a couple of points about the CMA and HPT allocations:

1. The HPT is probably getting sized according to the maximum memory of
the guest, not the initial amount of memory. Since we haven't been given
any specifics about the configuration of the guests, I can't tell
whether they are configured with maxmem greater than current/initial
memory. If the guests are configured with a very large maxmem, their
HPTs will be much larger than the 128MB mentioned in previous comments,
and that will obviously make it much more likely to have problems
allocating the HPT.

(With a sufficiently recent host kernel, guest kernel and QEMU, the HPT
can be resized while the guest is running, and in that case, QEMU
determines the size of the HPT from the current memory rather than the
maximum memory. However, HPT resizing went into the kernel later than
4.4, and I don't believe it has been backported into the Ubuntu version
of 4.4, hence the "probably" in the previous paragraph.)

2. The memory in the CMA zone is not locked away in the way that
previous comments imply. Memory in the CMA zone is still available for
movable allocations, which includes page cache and anonymous pages for
user processes, as well as memory for KVM guests. It is not available
for kernel allocations (including things like network packet buffers).

Thus it is worth while trying a larger kvm_cma_resv_ratio value in
situations like this. When fragmentation occurs, the parts of the CMA
zone that are too fragmented to use for HPTs can still be used for
running user processes and backing KVM guests.

3. Other relevant factors are whether the guest has any real PCI devices
passed through to it, and whether the guest is backed with large pages.
If the guest has any PCI devices passed through, then when the guest
sets up the DDW (dynamic DMA windows) TCE (iommu) table at boot time,
that will have the effect of pinning all the guest memory. Some of the
guest memory may have been allocated from the CMA zone. Balbir's patch
(which is in the Ubuntu 4.4 kernel now) will try to migrate any pages
that are in the CMA zone to somewhere else before they get pinned, but
if memory is in short supply, it may not succeed in moving the page out
of the CMA zone, and also the patch doesn't cope with large (16M) pages,
whether THP or explicit large pages.

Thus it would be worth disabling THP in the host.

I'm not sure whether explicit large pages could ever come from the CMA
zone. If the guests were backed by large pages, it would be worth trying
without large-page backing.

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

Title:
  KVM guest hash page table failed to allocate contiguous memory (CMA)

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

Bug description:
  Per an email forwarded within IBM, we wish to use this Launchpad bug
  to work on the technical discussion with the Canonical development
  folks and the IBM KVM and kernel team surrounding the analysis made by
  Daniel Axtens of Canonical for the customer issue raised in Case
  #00177825.

  The only statement at the moment by the KVM team was that there were
  various issues associated with CMA fragmentation causing issues with
  KVM guests. However, as mentioned, this bug is to allow the dialog
  amongst all the developers to see what can be done to help alleviate
  the situation or understand the root cause further.

  Please also note that we should not be attaching customer data to this
  bug. If that is necessary then we expect Canonical to help provide a
  controlled environment for reviewing that data so we avoid any privacy
  issues (e.g. for GDPR compliance).

  Here is the email from Daniel:

  I have looked at the sosreport you uploaded. Here is my analysis so
  far.

  Virtualisation on powerpc has some special requirements. To start a
  guest on a powerpc host, you need to allocate a contiguous area of
  memory to hold the guest's hash page table (HPT, or HTAB, depending on
  which document you look at). The HPT is required to track and manage
  guest memory.

  Your error reports show qemu asking the kernel to allocate an HTAB,
  and the kernel reporting that it had insufficient memory to do so. The
  required memory for the HPT scales with the guest memory size - it
  should be about 1/128th of guest memory, so for a 16GB guest, that's
  128MB. However, the HPT has to be allocated as a single contiguous
  memory region. (This is in contrast to regular guest memory, which is
  not required to be contiguous from the host point of view.)

  The kernel keeps a special contiguous memory area (CMA) for these
  purposes, and keeps track of the total amounts in use and still
  available. These are shown in /proc/meminfo. From the system that ran
  the sosreport, we see:

  

[Kernel-packages] [Bug 1769443] Re: [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 LTS version

[Daniel van Vugt]

Also, please explain how and where you are trying to "send or receive
files via bluetooth"? A screenshot (via PrtSc) would help.

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

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

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

Title:
  [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04
  LTS version

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to
  send or receive files via bluetooth,please do give a emulsion of this
  hardware problem

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun May  6 15:26:50 2018
  DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GconfCompiz:
   /apps/compiz-1/general:
 /apps/compiz-1/general/screen0:
  /apps/compiz-1/general/screen0/options:
   active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:81e5]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1366x768+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move', 'vpswitch', 
'place', 'animation', 'snap', 'compiztoolbox', 'imgpng', 'workarounds', 'expo', 
'fade', 'session', 'ezoom', 'switcher', 'scale', 'unityshell']"
  InstallationDate: Installed on 2016-11-07 (544 days ago)
  InstallationMedia:
   
  MachineType: HP HP 245 G5 Notebook PC
  MonitorsUser.xml:
   
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash
  SourcePackage: compiz
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago)
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81E5
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 73.15
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245
  dmi.product.name: HP 245 G5 Notebook PC
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1769443] Re: [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 LTS version

[Daniel van Vugt]

Do other bluetooth devices work still? Like a mouse, keyboard or
speaker?

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

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

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

Title:
  [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04
  LTS version

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to
  send or receive files via bluetooth,please do give a emulsion of this
  hardware problem

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun May  6 15:26:50 2018
  DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GconfCompiz:
   /apps/compiz-1/general:
 /apps/compiz-1/general/screen0:
  /apps/compiz-1/general/screen0/options:
   active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:81e5]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1366x768+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move', 'vpswitch', 
'place', 'animation', 'snap', 'compiztoolbox', 'imgpng', 'workarounds', 'expo', 
'fade', 'session', 'ezoom', 'switcher', 'scale', 'unityshell']"
  InstallationDate: Installed on 2016-11-07 (544 days ago)
  InstallationMedia:
   
  MachineType: HP HP 245 G5 Notebook PC
  MonitorsUser.xml:
   
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash
  SourcePackage: compiz
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago)
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81E5
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 73.15
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245
  dmi.product.name: HP 245 G5 Notebook PC
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://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 1769443] Re: [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 LTS version

[punyabrat kumar]

No,Its not working...unable to received files from other device,it 
always showing connection unsuccessful,

After installing these test kernals when I reload package manager I have 
received some software updates and installed it

But Bluetooth problem is going on..


On Tuesday 24 July 2018 08:48 AM, Daniel van Vugt wrote:
> Great. You installed it successfully.
>
> Please tell us if Bluetooth now works?
>
> If not then you can uninstall the test kernel with this command:
>
> sudo dpkg -r linux-headers-4.18.0-041800rc6 linux-
> headers-4.18.0-041800rc6-generic linux-image-
> unsigned-4.18.0-041800rc6-generic linux-
> modules-4.18.0-041800rc6-generic_4.18.0-041800rc6.201807221830
>
> and reboot again.
>

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

Title:
  [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04
  LTS version

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to
  send or receive files via bluetooth,please do give a emulsion of this
  hardware problem

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun May  6 15:26:50 2018
  DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GconfCompiz:
   /apps/compiz-1/general:
 /apps/compiz-1/general/screen0:
  /apps/compiz-1/general/screen0/options:
   active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:81e5]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1366x768+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move', 'vpswitch', 
'place', 'animation', 'snap', 'compiztoolbox', 'imgpng', 'workarounds', 'expo', 
'fade', 'session', 'ezoom', 'switcher', 'scale', 'unityshell']"
  InstallationDate: Installed on 2016-11-07 (544 days ago)
  InstallationMedia:
   
  MachineType: HP HP 245 G5 Notebook PC
  MonitorsUser.xml:
   
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash
  SourcePackage: compiz
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago)
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81E5
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 73.15
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245
  dmi.product.name: HP 245 G5 Notebook PC
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1769443] Re: [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 LTS version

[Daniel van Vugt]

Great. You installed it successfully.

Please tell us if Bluetooth now works?

If not then you can uninstall the test kernel with this command:

sudo dpkg -r linux-headers-4.18.0-041800rc6 linux-
headers-4.18.0-041800rc6-generic linux-image-
unsigned-4.18.0-041800rc6-generic linux-
modules-4.18.0-041800rc6-generic_4.18.0-041800rc6.201807221830

and reboot again.

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

Title:
  [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04
  LTS version

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to
  send or receive files via bluetooth,please do give a emulsion of this
  hardware problem

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun May  6 15:26:50 2018
  DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GconfCompiz:
   /apps/compiz-1/general:
 /apps/compiz-1/general/screen0:
  /apps/compiz-1/general/screen0/options:
   active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:81e5]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1366x768+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move', 'vpswitch', 
'place', 'animation', 'snap', 'compiztoolbox', 'imgpng', 'workarounds', 'expo', 
'fade', 'session', 'ezoom', 'switcher', 'scale', 'unityshell']"
  InstallationDate: Installed on 2016-11-07 (544 days ago)
  InstallationMedia:
   
  MachineType: HP HP 245 G5 Notebook PC
  MonitorsUser.xml:
   
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash
  SourcePackage: compiz
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago)
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81E5
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 73.15
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245
  dmi.product.name: HP 245 G5 Notebook PC
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1769443] Re: [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 LTS version

[punyabrat kumar]

when I'm installing these kenal in terminal it shows following outputs


welcome@HP:~$ cd ~/Downloads
welcome@HP:~/Downloads$   sudo dpkg -i linux*.deb
[sudo] password for welcome: 
Selecting previously unselected package linux-headers-4.18.0-041800rc6.
(Reading database ... 343372 files and directories currently installed.)
Preparing to unpack 
linux-headers-4.18.0-041800rc6_4.18.0-041800rc6.201807221830_all.deb ...
Unpacking linux-headers-4.18.0-041800rc6 (4.18.0-041800rc6.201807221830) ...
Selecting previously unselected package linux-headers-4.18.0-041800rc6-generic.
Preparing to unpack 
linux-headers-4.18.0-041800rc6-generic_4.18.0-041800rc6.201807221830_amd64.deb 
...
Unpacking linux-headers-4.18.0-041800rc6-generic 
(4.18.0-041800rc6.201807221830) ...
Selecting previously unselected package 
linux-image-unsigned-4.18.0-041800rc6-generic.
Preparing to unpack 
linux-image-unsigned-4.18.0-041800rc6-generic_4.18.0-041800rc6.201807221830_amd64.deb
 ...
Unpacking linux-image-unsigned-4.18.0-041800rc6-generic 
(4.18.0-041800rc6.201807221830) ...
Selecting previously unselected package linux-modules-4.18.0-041800rc6-generic.
Preparing to unpack 
linux-modules-4.18.0-041800rc6-generic_4.18.0-041800rc6.201807221830_amd64.deb 
...
Unpacking linux-modules-4.18.0-041800rc6-generic 
(4.18.0-041800rc6.201807221830) ...
Setting up linux-headers-4.18.0-041800rc6 (4.18.0-041800rc6.201807221830) ...
Setting up linux-headers-4.18.0-041800rc6-generic 
(4.18.0-041800rc6.201807221830) ...
Setting up linux-modules-4.18.0-041800rc6-generic 
(4.18.0-041800rc6.201807221830) ...
Setting up linux-image-unsigned-4.18.0-041800rc6-generic 
(4.18.0-041800rc6.201807221830) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.15.0-29-generic
I: /initrd.img.old is now a symlink to boot/initrd.img-4.15.0-29-generic
I: /vmlinuz is now a symlink to boot/vmlinuz-4.18.0-041800rc6-generic
I: /initrd.img is now a symlink to boot/initrd.img-4.18.0-041800rc6-generic
Processing triggers for linux-image-unsigned-4.18.0-041800rc6-generic 
(4.18.0-041800rc6.201807221830) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.18.0-041800rc6-generic
W: Possible missing firmware /lib/firmware/amdgpu/vega12_gpu_info.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_asd.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_sos.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_asd.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_sos.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_rlc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_mec2.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_mec.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_pfp.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_rlc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec2.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_mec.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_me.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_pfp.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_ce.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_rlc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec2.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_me.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_pfp.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_ce.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_sdma1.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_sdma.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_sdma1.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_sdma.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_sdma1.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_sdma.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_uvd.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_uvd.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_uvd.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega20_vce.bin for module 
amdgpu
W: Possible missing firmware 

[Kernel-packages] [Bug 1783246] [NEW] Cephfs + fscache: unable to handle kernel NULL pointer dereference at 0000000000000000 IP: jbd2__journal_start+0x22/0x1f0

[Daniel Axtens]

Public bug reported:

SRU Justification
-

[Impact]
Certain sequences of file system operations on a cephfs volume backed by 
fscache with an ext4 store can cause a kernel BUG:


[ 5818.932770] BUG: unable to handle kernel NULL pointer dereference at 

[ 5818.934354] IP: jbd2__journal_start+0x33/0x1e0
...
[ 5818.962490] Call Trace:
[ 5818.963055] ? ext4_writepages+0x5d5/0xf40
[ 5818.963884] __ext4_journal_start_sb+0x6d/0x120
[ 5818.964994] ext4_writepages+0x5d5/0xf40
[ 5818.965991] ? __enqueue_entity+0x5c/0x60
[ 5818.966791] ? check_preempt_wakeup+0x130/0x240
[ 5818.967679] do_writepages+0x4b/0xe0
[ 5818.968625] ? ext4_mark_inode_dirty+0x1d0/0x1d0
[ 5818.969526] ? do_writepages+0x4b/0xe0
[ 5818.970493] ? ext4_statfs+0x114/0x260
[ 5818.971267] __filemap_fdatawrite_range+0xc1/0x100
[ 5818.972425] ? __filemap_fdatawrite_range+0xc1/0x100
[ 5818.973385] filemap_write_and_wait+0x31/0x90
[ 5818.974461] ext4_bmap+0x8c/0xe0
[ 5818.975150] cachefiles_read_or_alloc_pages+0x1bf/0xd90 [cachefiles]
[ 5818.976718] ? _cond_resched+0x19/0x40
[ 5818.977482] ? wake_up_bit+0x42/0x50
[ 5818.978227] ? fscache_run_op.isra.8+0x4c/0x80 [fscache]
[ 5818.979249] __fscache_read_or_alloc_pages+0x1d3/0x2e0 [fscache]
[ 5818.980397] ceph_readpages_from_fscache+0x6c/0xe0 [ceph]
[ 5818.981630] ceph_readpages+0x49/0x100 [ceph]
[ 5818.982691] __do_page_cache_readahead+0x1c9/0x2c0
[ 5818.983628] ? __cap_is_valid+0x21/0xb0 [ceph]
[ 5818.984526] ondemand_readahead+0x11a/0x2a0
[ 5818.985374] ? ondemand_readahead+0x11a/0x2a0
[ 5818.986825] page_cache_async_readahead+0x71/0x80
[ 5818.987751] generic_file_read_iter+0x784/0xbf0
[ 5818.988663] ? ceph_put_cap_refs+0x1c4/0x330 [ceph]
[ 5818.989620] ? page_cache_tree_insert+0xe0/0xe0
[ 5818.990519] ceph_read_iter+0x106/0x820 [ceph]
[ 5818.991818] new_sync_read+0xe4/0x130
[ 5818.992588] __vfs_read+0x29/0x40
[ 5818.993504] vfs_read+0x8e/0x130
[ 5818.994192] SyS_read+0x55/0xc0
[ 5818.994870] do_syscall_64+0x73/0x130
[ 5818.995632] entry_SYSCALL_64_after_hwframe+0x3d/0xa2

[Fix]
Cherry-pick 5d988308283ecf062fa88f20ae05c52cce0bcdca from upstream.

This patch stops cephfs from reusing current->journal for its own
internal use, which means that it's valid when ext4 uses it via fscache.

[Testcase]
A user has been using the following test case:
( cat /proc/fs/fscache/stats > ~/test.log; i=0; while true; do
touch small; echo 3 > /proc/sys/vm/drop_caches & md5sum small; let "i++"; 
if ! (( $i % 1000 )); then
echo "Test iteration $i done" >> ~/test.log; cat /proc/fs/fscache/stats 
>> ~/test.log;
fi;
done ) > ~/nohup.out 2>&1

(It boils down to "touch file; drop caches; read file")
Without the patch, this fails very quickly - usually the first time, always 
within a few iterations. With the patch, the user ran this loop for over 60 
hours without incident.

[Regression potential]
The change is not trivial, but is limited to cephfs, and has been in mainline 
since v4.16. So the risk of regression is well contained.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Daniel Axtens (daxtens)
 Status: 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/1783246

Title:
  Cephfs + fscache: unable to handle kernel NULL pointer dereference at
   IP: jbd2__journal_start+0x22/0x1f0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SRU Justification
  -

  [Impact]
  Certain sequences of file system operations on a cephfs volume backed by 
fscache with an ext4 store can cause a kernel BUG:

  
  [ 5818.932770] BUG: unable to handle kernel NULL pointer dereference at 

  [ 5818.934354] IP: jbd2__journal_start+0x33/0x1e0
  ...
  [ 5818.962490] Call Trace:
  [ 5818.963055] ? ext4_writepages+0x5d5/0xf40
  [ 5818.963884] __ext4_journal_start_sb+0x6d/0x120
  [ 5818.964994] ext4_writepages+0x5d5/0xf40
  [ 5818.965991] ? __enqueue_entity+0x5c/0x60
  [ 5818.966791] ? check_preempt_wakeup+0x130/0x240
  [ 5818.967679] do_writepages+0x4b/0xe0
  [ 5818.968625] ? ext4_mark_inode_dirty+0x1d0/0x1d0
  [ 5818.969526] ? do_writepages+0x4b/0xe0
  [ 5818.970493] ? ext4_statfs+0x114/0x260
  [ 5818.971267] __filemap_fdatawrite_range+0xc1/0x100
  [ 5818.972425] ? __filemap_fdatawrite_range+0xc1/0x100
  [ 5818.973385] filemap_write_and_wait+0x31/0x90
  [ 5818.974461] ext4_bmap+0x8c/0xe0
  [ 5818.975150] cachefiles_read_or_alloc_pages+0x1bf/0xd90 [cachefiles]
  [ 5818.976718] ? _cond_resched+0x19/0x40
  [ 5818.977482] ? wake_up_bit+0x42/0x50
  [ 5818.978227] ? fscache_run_op.isra.8+0x4c/0x80 [fscache]
  [ 5818.979249] __fscache_read_or_alloc_pages+0x1d3/0x2e0 [fscache]
  [ 5818.980397] ceph_readpages_from_fscache+0x6c/0xe0 [ceph]
  [ 5818.981630] ceph_readpages+0x49/0x100 [ceph]
  [ 5818.982691] __do_page_cache_readahead+0x1c9/0x2c0
  [ 5818.983628] ? __cap_is_valid+0x21/0xb0 [ceph]
  [ 5818.984526] 

Re: [Kernel-packages] [Bug 1769443] Re: [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 LTS version

[punyabrat kumar]

Oops typing error

If it possible please release necessary software updates


I will not install such kernel's I'm not a developer, and I don't know how
to install it

On Jul 24, 2018 7:43 AM, "Punyabrat Kumar" 
wrote:

> The problem should be fix by future necessary updates, The Ubuntu
> developer should try to fix this issue...If it possible please necessary
> release  software updates,
>
> I will not installed such kernel because I'm not a developer,And I don't
> know how to install it,
>
> Please discuss this issue with other developer,Thanks
>
> On Jul 24, 2018 6:51 AM, "Daniel van Vugt" 
> wrote:
>
>> Although the latest kernel also contains the drivers:
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin
>> ux.git/tree/drivers/net/wireless/realtek/rtlwifi
>>
>> Can you please try installing a newer kernel or two from here?
>> http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
>>
>> ** Changed in: bluez (Ubuntu)
>>Status: New => Incomplete
>>
>> ** Changed in: linux (Ubuntu)
>>Status: New => Incomplete
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1769443
>>
>> Title:
>>   [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04
>>   LTS version
>>
>> Status in bluez package in Ubuntu:
>>   Incomplete
>> Status in linux package in Ubuntu:
>>   Incomplete
>>
>> Bug description:
>>   Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to
>>   send or receive files via bluetooth,please do give a emulsion of this
>>   hardware problem
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 18.04
>>   Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1
>>   ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
>>   Uname: Linux 4.15.0-20-generic x86_64
>>   .tmp.unity_support_test.0:
>>
>>   ApportVersion: 2.20.9-0ubuntu7
>>   Architecture: amd64
>>   CompizPlugins: [core,composite,opengl,compizt
>> oolbox,decor,vpswitch,snap,mousepoll,resize,place,move,
>> wall,grid,regex,imgpng,session,gnomecompat,animation,fade,
>> staticswitcher,workarounds,scale,expo,ezoom,dbus]
>>   CompositorRunning: compiz
>>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>>   CompositorUnredirectFSW: true
>>   CurrentDesktop: Unity:Unity7:ubuntu
>>   Date: Sun May  6 15:26:50 2018
>>   DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript:
>> './xorg_fix_proprietary.py'
>>   DistroCodename: bionic
>>   DistroVariant: ubuntu
>>   ExecutablePath: /usr/bin/compiz
>>   GconfCompiz:
>>/apps/compiz-1/general:
>>  /apps/compiz-1/general/screen0:
>>   /apps/compiz-1/general/screen0/options:
>>active_plugins = [core,composite,opengl,compizt
>> oolbox,decor,vpswitch,snap,mousepoll,resize,place,move,
>> wall,grid,regex,imgpng,session,gnomecompat,animation,fade,
>> staticswitcher,workarounds,scale,expo,ezoom,dbus]
>>   GraphicsCard:
>>Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics]
>> [1002:9851] (rev 40) (prog-if 00 [VGA controller])
>>  Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics]
>> [103c:81e5]
>>   GsettingsChanges:
>>b'org.compiz.core' b'outputs' b"['1366x768+0+0']"
>>b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl',
>> 'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move',
>> 'vpswitch', 'place', 'animation', 'snap', 'compiztoolbox', 'imgpng',
>> 'workarounds', 'expo', 'fade', 'session', 'ezoom', 'switcher', 'scale',
>> 'unityshell']"
>>   InstallationDate: Installed on 2016-11-07 (544 days ago)
>>   InstallationMedia:
>>
>>   MachineType: HP HP 245 G5 Notebook PC
>>   MonitorsUser.xml:
>>
>>
>>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic
>> root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash
>>   SourcePackage: compiz
>>   UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago)
>>   dmi.bios.date: 11/01/2016
>>   dmi.bios.vendor: Insyde
>>   dmi.bios.version: F.21
>>   dmi.board.asset.tag: Base Board Asset Tag
>>   dmi.board.name: 81E5
>>   dmi.board.vendor: HP
>>   dmi.board.version: KBC Version 73.15
>>   dmi.chassis.asset.tag: Chassis Asset Tag
>>   dmi.chassis.type: 10
>>   dmi.chassis.vendor: HP
>>   dmi.chassis.version: Chassis Version
>>   dmi.modalias: dmi:bvnInsyde:bvrF.21:bd11/01/
>> 2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:
>> rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion:
>>   dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245
>>   dmi.product.name: HP 245 G5 Notebook PC
>>   dmi.product.version: Type1ProductConfigId
>>   dmi.sys.vendor: HP
>>   version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
>>   version.libdrm2: libdrm2 2.4.91-2
>>   version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
>>   version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
>>   version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
>>   

[Kernel-packages] [Bug 1769443] Re: [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 LTS version

[Daniel van Vugt]

Yes, however there won't be any "future necessary updates" if we don't
know what to update.

To help us figure that out please try downloading and installing all of
these:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc6/linux-headers-4.18.0-041800rc6_4.18.0-041800rc6.201807221830_all.deb
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc6/linux-headers-4.18.0-041800rc6-generic_4.18.0-041800rc6.201807221830_amd64.deb
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc6/linux-image-unsigned-4.18.0-041800rc6-generic_4.18.0-041800rc6.201807221830_amd64.deb
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc6/linux-modules-4.18.0-041800rc6-generic_4.18.0-041800rc6.201807221830_amd64.deb

When downloaded you can install them in a terminal by running:

  cd ~/Downloads
  sudo dpkg -i linux*.deb

Then reboot.

Now check that the new kernel is active by running:

  uname -a

and send us the result that you see.

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

Title:
  [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04
  LTS version

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to
  send or receive files via bluetooth,please do give a emulsion of this
  hardware problem

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun May  6 15:26:50 2018
  DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GconfCompiz:
   /apps/compiz-1/general:
 /apps/compiz-1/general/screen0:
  /apps/compiz-1/general/screen0/options:
   active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:81e5]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1366x768+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move', 'vpswitch', 
'place', 'animation', 'snap', 'compiztoolbox', 'imgpng', 'workarounds', 'expo', 
'fade', 'session', 'ezoom', 'switcher', 'scale', 'unityshell']"
  InstallationDate: Installed on 2016-11-07 (544 days ago)
  InstallationMedia:
   
  MachineType: HP HP 245 G5 Notebook PC
  MonitorsUser.xml:
   
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash
  SourcePackage: compiz
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago)
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81E5
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 73.15
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245
  dmi.product.name: HP 245 G5 Notebook PC
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1783241] [NEW] [HMS] Upgrades to Support SocketCAN over USB on Dell IoT 300x Gateways

[Shrirang Bagul]

Public bug reported:

Several scheduled upgrades to the HMS SocketCAN protocol driver over
USB->CAN interface are required.

SocketCAN support for USB->CAN devices was introduced in Ubuntu Xenial LTS 
kernel through following patch (BugLink: 
http://bugs.launchpad.net/bugs/1774563):
cddf58207a3c UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device

== SRU Justification ==
The scheduled upgrades include following changes:
- support adapters for CL1 (Communication Layer for legacy devices) and
  CL2 (current devices)
- removed CAN-IDM100 support (Microchip Rev A microcontroller)
- add CAN-IDM101 support (Microchip Rev B microcontroller)
- add Error-Passive recognition
- move CAN message handling to the core module
- use ktime API for timestamps
- fixes Linux kernel coding style issues

== Fix ==
UBUNTU: SAUCE: (no-up) upgrade IXXAT USB SocketCAN driver

== Regression Potential ==
Low. The driver will be built only for amd64 kernels and attach itself to IXXAT 
USB-CAN adapters with VID 0x08d8. Also, patches from the vendor (HMS) have 
already been tested by Dell/ODM, Canonical QA on Dell 300x Edge IoT gateways.

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

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

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

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

Title:
  [HMS] Upgrades to Support SocketCAN over USB on Dell IoT 300x Gateways

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Several scheduled upgrades to the HMS SocketCAN protocol driver over
  USB->CAN interface are required.

  SocketCAN support for USB->CAN devices was introduced in Ubuntu Xenial LTS 
kernel through following patch (BugLink: 
http://bugs.launchpad.net/bugs/1774563):
  cddf58207a3c UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device

  == SRU Justification ==
  The scheduled upgrades include following changes:
  - support adapters for CL1 (Communication Layer for legacy devices) and
CL2 (current devices)
  - removed CAN-IDM100 support (Microchip Rev A microcontroller)
  - add CAN-IDM101 support (Microchip Rev B microcontroller)
  - add Error-Passive recognition
  - move CAN message handling to the core module
  - use ktime API for timestamps
  - fixes Linux kernel coding style issues

  == Fix ==
  UBUNTU: SAUCE: (no-up) upgrade IXXAT USB SocketCAN driver

  == Regression Potential ==
  Low. The driver will be built only for amd64 kernels and attach itself to 
IXXAT USB-CAN adapters with VID 0x08d8. Also, patches from the vendor (HMS) 
have already been tested by Dell/ODM, Canonical QA on Dell 300x Edge IoT 
gateways.

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

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

-- 
Mailing list: https://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 1769443] Re: [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 LTS version

[punyabrat kumar]

The problem should be fix by future necessary updates, The Ubuntu developer
should try to fix this issue...If it possible please necessary release
 software updates,

I will not installed such kernel because I'm not a developer,And I don't
know how to install it,

Please discuss this issue with other developer,Thanks

On Jul 24, 2018 6:51 AM, "Daniel van Vugt" 
wrote:

> Although the latest kernel also contains the drivers:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/
> linux.git/tree/drivers/net/wireless/realtek/rtlwifi
>
> Can you please try installing a newer kernel or two from here?
> http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
>
> ** Changed in: bluez (Ubuntu)
>Status: New => Incomplete
>
> ** Changed in: linux (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1769443
>
> Title:
>   [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04
>   LTS version
>
> Status in bluez package in Ubuntu:
>   Incomplete
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to
>   send or receive files via bluetooth,please do give a emulsion of this
>   hardware problem
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1
>   ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
>   Uname: Linux 4.15.0-20-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.9-0ubuntu7
>   Architecture: amd64
>   CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,
> snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,
> session,gnomecompat,animation,fade,staticswitcher,
> workarounds,scale,expo,ezoom,dbus]
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   CurrentDesktop: Unity:Unity7:ubuntu
>   Date: Sun May  6 15:26:50 2018
>   DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript:
> './xorg_fix_proprietary.py'
>   DistroCodename: bionic
>   DistroVariant: ubuntu
>   ExecutablePath: /usr/bin/compiz
>   GconfCompiz:
>/apps/compiz-1/general:
>  /apps/compiz-1/general/screen0:
>   /apps/compiz-1/general/screen0/options:
>active_plugins = [core,composite,opengl,
> compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,
> move,wall,grid,regex,imgpng,session,gnomecompat,animation,
> fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics]
> [1002:9851] (rev 40) (prog-if 00 [VGA controller])
>  Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics]
> [103c:81e5]
>   GsettingsChanges:
>b'org.compiz.core' b'outputs' b"['1366x768+0+0']"
>b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl',
> 'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move',
> 'vpswitch', 'place', 'animation', 'snap', 'compiztoolbox', 'imgpng',
> 'workarounds', 'expo', 'fade', 'session', 'ezoom', 'switcher', 'scale',
> 'unityshell']"
>   InstallationDate: Installed on 2016-11-07 (544 days ago)
>   InstallationMedia:
>
>   MachineType: HP HP 245 G5 Notebook PC
>   MonitorsUser.xml:
>
>
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic
> root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash
>   SourcePackage: compiz
>   UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago)
>   dmi.bios.date: 11/01/2016
>   dmi.bios.vendor: Insyde
>   dmi.bios.version: F.21
>   dmi.board.asset.tag: Base Board Asset Tag
>   dmi.board.name: 81E5
>   dmi.board.vendor: HP
>   dmi.board.version: KBC Version 73.15
>   dmi.chassis.asset.tag: Chassis Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: HP
>   dmi.chassis.version: Chassis Version
>   dmi.modalias: dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:
> pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:
> rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion:
>   dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245
>   dmi.product.name: HP 245 G5 Notebook PC
>   dmi.product.version: Type1ProductConfigId
>   dmi.sys.vendor: HP
>   version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
>   version.libdrm2: libdrm2 2.4.91-2
>   version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
>   version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.10.5-1ubuntu1
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20171229-1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.15-2
>
> To manage notifications about this 

[Kernel-packages] [Bug 1774563] Re: [HMS] Support SocketCAN over USB on Dell IoT 300x Gateways

[Shrirang Bagul]

** Summary changed:

- Support SocketCAN over USB on Dell IoT 300x Gateways
+ [HMS] Support SocketCAN over USB on Dell IoT 300x Gateways

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

Title:
  [HMS] Support SocketCAN over USB on Dell IoT 300x Gateways

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

Bug description:
  This driver is from IXXAT and supports SocketCAN over USB.
  (https://www.ixxat.com)

  == SRU Justification ==
  Dell IoT 300x gateways support USB-CAN peripherals. Dell expects these 
devices also support the SocketCAN over USB and is working with HMS to develop 
and upstream the driver. Meanwhile, we'll have to carry this driver as a SAUCE 
patch to support our Ubuntu Core 16 release.

  == Fix ==
  UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device

  == Regression Potential ==
  Low. The driver will be built only for amd64 kernels and attach itself to 
IXXAT USB-CAN adapters with VID 0x08d8.

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

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

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

[Kernel-packages] [Bug 1769443] Re: [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 LTS version

[Daniel van Vugt]

It appears some other people have reported similar problems with the
same RTL8723 bluetooth hardware in bug 1446239 and bug 1747421. However
both of those have closed so we only have this bug now.

It's been suggested github has better drivers. I'm not sure where but
https://github.com/lwfinger/rtlwifi_new looks like a good candidate.


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

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

Title:
  [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04
  LTS version

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to
  send or receive files via bluetooth,please do give a emulsion of this
  hardware problem

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun May  6 15:26:50 2018
  DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GconfCompiz:
   /apps/compiz-1/general:
 /apps/compiz-1/general/screen0:
  /apps/compiz-1/general/screen0/options:
   active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:81e5]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1366x768+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move', 'vpswitch', 
'place', 'animation', 'snap', 'compiztoolbox', 'imgpng', 'workarounds', 'expo', 
'fade', 'session', 'ezoom', 'switcher', 'scale', 'unityshell']"
  InstallationDate: Installed on 2016-11-07 (544 days ago)
  InstallationMedia:
   
  MachineType: HP HP 245 G5 Notebook PC
  MonitorsUser.xml:
   
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash
  SourcePackage: compiz
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago)
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81E5
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 73.15
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245
  dmi.product.name: HP 245 G5 Notebook PC
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

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

[Nicolas Krzywinski]

apport information

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

Title:
  Kernel 4.15 fails to load nvidia module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Booting into kernel 4.15 results in no graphics acceleration. No
  nvidia module is loaded.

  Manually loading the module results in:
  me@mysys /home/me $ sudo modprobe nvidia
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='nvidia_384'
  modprobe: ERROR: could not insert 'nvidia_384': Unknown symbol in module, or 
unknown parameter (see dmesg)
  me@mysys /home/me $ 

  The weird thing: there is nothing in dmesg and nothing in syslog.
  Reboot with kernel 4.13.0-43 (or older) and everything works again.

  me@mysys ~ $ uname -a
  Linux sesta10 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17 12:56:46 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  me@mysys ~ $ lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 18.3 Sylvia
  Release:  18.3
  Codename: sylvia
  me@mysys ~ $ 

  Please advise how to give more useful informations - I tried "ubuntu-bug 
linux" and "ubuntu-bug linux-image-4.15.0-29-generic" in the faulty state (on 
the CLI of kernel 4.15), but it told me that this is no linux package.. ?
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  seven  2770 F pulseaudio
   /dev/snd/controlC0:  seven  2770 F pulseaudio
   /dev/snd/controlC1:  seven  2770 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=ec22f108-69f6-4433-841d-636bab5b8f60
  InstallationDate: Installed on 2016-07-03 (750 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   anbox0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=67bad3d0-da8e-4293-97b1-a5c134911af0 ro nouveau.blacklist=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-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.157.20
  RfKill:
   
  Tags:  sylvia
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: users
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: Z170 Extreme4+
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd09/21/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Extreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1782739] Re: Boot to Black

[Daniel van Vugt]

OK. Next please try some newer (or older) kernels and see if you can
find a version which fixes the bug:

http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

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

Title:
  Boot to Black

Status in gdm3 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When I boot my new Ubuntu 18.04LTS install on my ASUS flipbook I see
  the splash screen as expected.  The boot continues and it reaches the
  point where you would expect to see the login screen.  I see what
  appears to be a non-backlighted blank black screen.  If I wait until
  all hard drive activity ceases and then type in my password and press
  enter the login completes and I am presented a normal Ubuntu desktop.

  Thank you
  Gene

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 20 07:16:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:166d]
  InstallationDate: Installed on 2018-07-20 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. TP550LA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=5b0bd839-3614-4f3d-8536-bc400cd364e5 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LA.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LA.210:bd06/27/2014:svnASUSTeKCOMPUTERINC.:pnTP550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TP
  dmi.product.name: TP550LA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1769443] Re: [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 LTS version

[Daniel van Vugt]

Although the latest kernel also contains the drivers:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/wireless/realtek/rtlwifi

Can you please try installing a newer kernel or two from here?
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

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

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

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

Title:
  [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04
  LTS version

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to
  send or receive files via bluetooth,please do give a emulsion of this
  hardware problem

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun May  6 15:26:50 2018
  DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GconfCompiz:
   /apps/compiz-1/general:
 /apps/compiz-1/general/screen0:
  /apps/compiz-1/general/screen0/options:
   active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:81e5]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1366x768+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move', 'vpswitch', 
'place', 'animation', 'snap', 'compiztoolbox', 'imgpng', 'workarounds', 'expo', 
'fade', 'session', 'ezoom', 'switcher', 'scale', 'unityshell']"
  InstallationDate: Installed on 2016-11-07 (544 days ago)
  InstallationMedia:
   
  MachineType: HP HP 245 G5 Notebook PC
  MonitorsUser.xml:
   
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash
  SourcePackage: compiz
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago)
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81E5
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 73.15
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245
  dmi.product.name: HP 245 G5 Notebook PC
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1488426] Re: High CPU usage of kworker/ksoftirqd

[AceLan Kao]

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

** Changed in: linux (Ubuntu)
 Assignee: AceLan Kao (acelankao) => (unassigned)

** Changed in: hwe-next
 Assignee: AceLan Kao (acelankao) => (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/1488426

Title:
  High CPU usage of kworker/ksoftirqd

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  kworker consuming 71.5% cpu resource
  ksoftirqd consuming 28.9% cpu resource

  It leads to power consumption issue and sometimes leads to BT does not
  work.

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

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

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

[Nicolas Krzywinski]

apport information

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

Title:
  Kernel 4.15 fails to load nvidia module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Booting into kernel 4.15 results in no graphics acceleration. No
  nvidia module is loaded.

  Manually loading the module results in:
  me@mysys /home/me $ sudo modprobe nvidia
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='nvidia_384'
  modprobe: ERROR: could not insert 'nvidia_384': Unknown symbol in module, or 
unknown parameter (see dmesg)
  me@mysys /home/me $ 

  The weird thing: there is nothing in dmesg and nothing in syslog.
  Reboot with kernel 4.13.0-43 (or older) and everything works again.

  me@mysys ~ $ uname -a
  Linux sesta10 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17 12:56:46 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  me@mysys ~ $ lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 18.3 Sylvia
  Release:  18.3
  Codename: sylvia
  me@mysys ~ $ 

  Please advise how to give more useful informations - I tried "ubuntu-bug 
linux" and "ubuntu-bug linux-image-4.15.0-29-generic" in the faulty state (on 
the CLI of kernel 4.15), but it told me that this is no linux package.. ?
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  seven  2770 F pulseaudio
   /dev/snd/controlC0:  seven  2770 F pulseaudio
   /dev/snd/controlC1:  seven  2770 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=ec22f108-69f6-4433-841d-636bab5b8f60
  InstallationDate: Installed on 2016-07-03 (750 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   anbox0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=67bad3d0-da8e-4293-97b1-a5c134911af0 ro nouveau.blacklist=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-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.157.20
  RfKill:
   
  Tags:  sylvia
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: users
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: Z170 Extreme4+
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd09/21/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Extreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

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

[Nicolas Krzywinski]

apport information

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

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

Title:
  Kernel 4.15 fails to load nvidia module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Booting into kernel 4.15 results in no graphics acceleration. No
  nvidia module is loaded.

  Manually loading the module results in:
  me@mysys /home/me $ sudo modprobe nvidia
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='nvidia_384'
  modprobe: ERROR: could not insert 'nvidia_384': Unknown symbol in module, or 
unknown parameter (see dmesg)
  me@mysys /home/me $ 

  The weird thing: there is nothing in dmesg and nothing in syslog.
  Reboot with kernel 4.13.0-43 (or older) and everything works again.

  me@mysys ~ $ uname -a
  Linux sesta10 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17 12:56:46 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  me@mysys ~ $ lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 18.3 Sylvia
  Release:  18.3
  Codename: sylvia
  me@mysys ~ $ 

  Please advise how to give more useful informations - I tried "ubuntu-bug 
linux" and "ubuntu-bug linux-image-4.15.0-29-generic" in the faulty state (on 
the CLI of kernel 4.15), but it told me that this is no linux package.. ?
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  seven  2770 F pulseaudio
   /dev/snd/controlC0:  seven  2770 F pulseaudio
   /dev/snd/controlC1:  seven  2770 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=ec22f108-69f6-4433-841d-636bab5b8f60
  InstallationDate: Installed on 2016-07-03 (750 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   anbox0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=67bad3d0-da8e-4293-97b1-a5c134911af0 ro nouveau.blacklist=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-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.157.20
  RfKill:
   
  Tags:  sylvia
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: users
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: Z170 Extreme4+
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd09/21/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Extreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

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

[Nicolas Krzywinski]

apport information

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

Title:
  Kernel 4.15 fails to load nvidia module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Booting into kernel 4.15 results in no graphics acceleration. No
  nvidia module is loaded.

  Manually loading the module results in:
  me@mysys /home/me $ sudo modprobe nvidia
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='nvidia_384'
  modprobe: ERROR: could not insert 'nvidia_384': Unknown symbol in module, or 
unknown parameter (see dmesg)
  me@mysys /home/me $ 

  The weird thing: there is nothing in dmesg and nothing in syslog.
  Reboot with kernel 4.13.0-43 (or older) and everything works again.

  me@mysys ~ $ uname -a
  Linux sesta10 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17 12:56:46 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  me@mysys ~ $ lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 18.3 Sylvia
  Release:  18.3
  Codename: sylvia
  me@mysys ~ $ 

  Please advise how to give more useful informations - I tried "ubuntu-bug 
linux" and "ubuntu-bug linux-image-4.15.0-29-generic" in the faulty state (on 
the CLI of kernel 4.15), but it told me that this is no linux package.. ?
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  seven  2770 F pulseaudio
   /dev/snd/controlC0:  seven  2770 F pulseaudio
   /dev/snd/controlC1:  seven  2770 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=ec22f108-69f6-4433-841d-636bab5b8f60
  InstallationDate: Installed on 2016-07-03 (750 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   anbox0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=67bad3d0-da8e-4293-97b1-a5c134911af0 ro nouveau.blacklist=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-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.157.20
  RfKill:
   
  Tags:  sylvia
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: users
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: Z170 Extreme4+
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd09/21/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Extreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

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

[Nicolas Krzywinski]

apport information

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

Title:
  Kernel 4.15 fails to load nvidia module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Booting into kernel 4.15 results in no graphics acceleration. No
  nvidia module is loaded.

  Manually loading the module results in:
  me@mysys /home/me $ sudo modprobe nvidia
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='nvidia_384'
  modprobe: ERROR: could not insert 'nvidia_384': Unknown symbol in module, or 
unknown parameter (see dmesg)
  me@mysys /home/me $ 

  The weird thing: there is nothing in dmesg and nothing in syslog.
  Reboot with kernel 4.13.0-43 (or older) and everything works again.

  me@mysys ~ $ uname -a
  Linux sesta10 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17 12:56:46 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  me@mysys ~ $ lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 18.3 Sylvia
  Release:  18.3
  Codename: sylvia
  me@mysys ~ $ 

  Please advise how to give more useful informations - I tried "ubuntu-bug 
linux" and "ubuntu-bug linux-image-4.15.0-29-generic" in the faulty state (on 
the CLI of kernel 4.15), but it told me that this is no linux package.. ?
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  seven  2770 F pulseaudio
   /dev/snd/controlC0:  seven  2770 F pulseaudio
   /dev/snd/controlC1:  seven  2770 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=ec22f108-69f6-4433-841d-636bab5b8f60
  InstallationDate: Installed on 2016-07-03 (750 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   anbox0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=67bad3d0-da8e-4293-97b1-a5c134911af0 ro nouveau.blacklist=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-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.157.20
  RfKill:
   
  Tags:  sylvia
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: users
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: Z170 Extreme4+
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd09/21/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Extreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

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

[Nicolas Krzywinski]

apport information

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

Title:
  Kernel 4.15 fails to load nvidia module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Booting into kernel 4.15 results in no graphics acceleration. No
  nvidia module is loaded.

  Manually loading the module results in:
  me@mysys /home/me $ sudo modprobe nvidia
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='nvidia_384'
  modprobe: ERROR: could not insert 'nvidia_384': Unknown symbol in module, or 
unknown parameter (see dmesg)
  me@mysys /home/me $ 

  The weird thing: there is nothing in dmesg and nothing in syslog.
  Reboot with kernel 4.13.0-43 (or older) and everything works again.

  me@mysys ~ $ uname -a
  Linux sesta10 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17 12:56:46 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  me@mysys ~ $ lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 18.3 Sylvia
  Release:  18.3
  Codename: sylvia
  me@mysys ~ $ 

  Please advise how to give more useful informations - I tried "ubuntu-bug 
linux" and "ubuntu-bug linux-image-4.15.0-29-generic" in the faulty state (on 
the CLI of kernel 4.15), but it told me that this is no linux package.. ?
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  seven  2770 F pulseaudio
   /dev/snd/controlC0:  seven  2770 F pulseaudio
   /dev/snd/controlC1:  seven  2770 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=ec22f108-69f6-4433-841d-636bab5b8f60
  InstallationDate: Installed on 2016-07-03 (750 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   anbox0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=67bad3d0-da8e-4293-97b1-a5c134911af0 ro nouveau.blacklist=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-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.157.20
  RfKill:
   
  Tags:  sylvia
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: users
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: Z170 Extreme4+
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd09/21/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Extreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

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

[Nicolas Krzywinski]

apport information

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

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

Title:
  Kernel 4.15 fails to load nvidia module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Booting into kernel 4.15 results in no graphics acceleration. No
  nvidia module is loaded.

  Manually loading the module results in:
  me@mysys /home/me $ sudo modprobe nvidia
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='nvidia_384'
  modprobe: ERROR: could not insert 'nvidia_384': Unknown symbol in module, or 
unknown parameter (see dmesg)
  me@mysys /home/me $ 

  The weird thing: there is nothing in dmesg and nothing in syslog.
  Reboot with kernel 4.13.0-43 (or older) and everything works again.

  me@mysys ~ $ uname -a
  Linux sesta10 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17 12:56:46 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  me@mysys ~ $ lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 18.3 Sylvia
  Release:  18.3
  Codename: sylvia
  me@mysys ~ $ 

  Please advise how to give more useful informations - I tried "ubuntu-bug 
linux" and "ubuntu-bug linux-image-4.15.0-29-generic" in the faulty state (on 
the CLI of kernel 4.15), but it told me that this is no linux package.. ?
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  seven  2770 F pulseaudio
   /dev/snd/controlC0:  seven  2770 F pulseaudio
   /dev/snd/controlC1:  seven  2770 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=ec22f108-69f6-4433-841d-636bab5b8f60
  InstallationDate: Installed on 2016-07-03 (750 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   anbox0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=67bad3d0-da8e-4293-97b1-a5c134911af0 ro nouveau.blacklist=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-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.157.20
  RfKill:
   
  Tags:  sylvia
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: users
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: Z170 Extreme4+
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd09/21/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Extreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

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

[Nicolas Krzywinski]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1783229/+attachment/5166886/+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/1783229

Title:
  Kernel 4.15 fails to load nvidia module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Booting into kernel 4.15 results in no graphics acceleration. No
  nvidia module is loaded.

  Manually loading the module results in:
  me@mysys /home/me $ sudo modprobe nvidia
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='nvidia_384'
  modprobe: ERROR: could not insert 'nvidia_384': Unknown symbol in module, or 
unknown parameter (see dmesg)
  me@mysys /home/me $ 

  The weird thing: there is nothing in dmesg and nothing in syslog.
  Reboot with kernel 4.13.0-43 (or older) and everything works again.

  me@mysys ~ $ uname -a
  Linux sesta10 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17 12:56:46 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  me@mysys ~ $ lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 18.3 Sylvia
  Release:  18.3
  Codename: sylvia
  me@mysys ~ $ 

  Please advise how to give more useful informations - I tried "ubuntu-bug 
linux" and "ubuntu-bug linux-image-4.15.0-29-generic" in the faulty state (on 
the CLI of kernel 4.15), but it told me that this is no linux package.. ?
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  seven  2770 F pulseaudio
   /dev/snd/controlC0:  seven  2770 F pulseaudio
   /dev/snd/controlC1:  seven  2770 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=ec22f108-69f6-4433-841d-636bab5b8f60
  InstallationDate: Installed on 2016-07-03 (750 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   anbox0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=67bad3d0-da8e-4293-97b1-a5c134911af0 ro nouveau.blacklist=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-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.157.20
  RfKill:
   
  Tags:  sylvia
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: users
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: Z170 Extreme4+
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd09/21/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Extreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

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

[Nicolas Krzywinski]

apport information

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

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

Title:
  Kernel 4.15 fails to load nvidia module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Booting into kernel 4.15 results in no graphics acceleration. No
  nvidia module is loaded.

  Manually loading the module results in:
  me@mysys /home/me $ sudo modprobe nvidia
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='nvidia_384'
  modprobe: ERROR: could not insert 'nvidia_384': Unknown symbol in module, or 
unknown parameter (see dmesg)
  me@mysys /home/me $ 

  The weird thing: there is nothing in dmesg and nothing in syslog.
  Reboot with kernel 4.13.0-43 (or older) and everything works again.

  me@mysys ~ $ uname -a
  Linux sesta10 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17 12:56:46 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  me@mysys ~ $ lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 18.3 Sylvia
  Release:  18.3
  Codename: sylvia
  me@mysys ~ $ 

  Please advise how to give more useful informations - I tried "ubuntu-bug 
linux" and "ubuntu-bug linux-image-4.15.0-29-generic" in the faulty state (on 
the CLI of kernel 4.15), but it told me that this is no linux package.. ?
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  seven  2770 F pulseaudio
   /dev/snd/controlC0:  seven  2770 F pulseaudio
   /dev/snd/controlC1:  seven  2770 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=ec22f108-69f6-4433-841d-636bab5b8f60
  InstallationDate: Installed on 2016-07-03 (750 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   anbox0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=67bad3d0-da8e-4293-97b1-a5c134911af0 ro nouveau.blacklist=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-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.157.20
  RfKill:
   
  Tags:  sylvia
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: users
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: Z170 Extreme4+
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd09/21/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Extreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

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

[Nicolas Krzywinski]

apport information

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

Title:
  Kernel 4.15 fails to load nvidia module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Booting into kernel 4.15 results in no graphics acceleration. No
  nvidia module is loaded.

  Manually loading the module results in:
  me@mysys /home/me $ sudo modprobe nvidia
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='nvidia_384'
  modprobe: ERROR: could not insert 'nvidia_384': Unknown symbol in module, or 
unknown parameter (see dmesg)
  me@mysys /home/me $ 

  The weird thing: there is nothing in dmesg and nothing in syslog.
  Reboot with kernel 4.13.0-43 (or older) and everything works again.

  me@mysys ~ $ uname -a
  Linux sesta10 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17 12:56:46 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  me@mysys ~ $ lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 18.3 Sylvia
  Release:  18.3
  Codename: sylvia
  me@mysys ~ $ 

  Please advise how to give more useful informations - I tried "ubuntu-bug 
linux" and "ubuntu-bug linux-image-4.15.0-29-generic" in the faulty state (on 
the CLI of kernel 4.15), but it told me that this is no linux package.. ?
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  seven  2770 F pulseaudio
   /dev/snd/controlC0:  seven  2770 F pulseaudio
   /dev/snd/controlC1:  seven  2770 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=ec22f108-69f6-4433-841d-636bab5b8f60
  InstallationDate: Installed on 2016-07-03 (750 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   anbox0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=67bad3d0-da8e-4293-97b1-a5c134911af0 ro nouveau.blacklist=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-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.157.20
  RfKill:
   
  Tags:  sylvia
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: users
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: Z170 Extreme4+
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd09/21/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Extreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

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

[Nicolas Krzywinski]

apport information

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

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

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

Title:
  Kernel 4.15 fails to load nvidia module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Booting into kernel 4.15 results in no graphics acceleration. No
  nvidia module is loaded.

  Manually loading the module results in:
  me@mysys /home/me $ sudo modprobe nvidia
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='nvidia_384'
  modprobe: ERROR: could not insert 'nvidia_384': Unknown symbol in module, or 
unknown parameter (see dmesg)
  me@mysys /home/me $ 

  The weird thing: there is nothing in dmesg and nothing in syslog.
  Reboot with kernel 4.13.0-43 (or older) and everything works again.

  me@mysys ~ $ uname -a
  Linux sesta10 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17 12:56:46 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  me@mysys ~ $ lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 18.3 Sylvia
  Release:  18.3
  Codename: sylvia
  me@mysys ~ $ 

  Please advise how to give more useful informations - I tried "ubuntu-bug 
linux" and "ubuntu-bug linux-image-4.15.0-29-generic" in the faulty state (on 
the CLI of kernel 4.15), but it told me that this is no linux package.. ?
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  seven  2770 F pulseaudio
   /dev/snd/controlC0:  seven  2770 F pulseaudio
   /dev/snd/controlC1:  seven  2770 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=ec22f108-69f6-4433-841d-636bab5b8f60
  InstallationDate: Installed on 2016-07-03 (750 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   anbox0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=67bad3d0-da8e-4293-97b1-a5c134911af0 ro nouveau.blacklist=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-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.157.20
  RfKill:
   
  Tags:  sylvia
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: users
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: Z170 Extreme4+
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd09/21/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Extreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1783229] Re: Kernel 4.15 fails to load nvidia module

[Nicolas Krzywinski]

apport information

** Tags added: apport-collected sylvia

** Description changed:

  Booting into kernel 4.15 results in no graphics acceleration. No nvidia
  module is loaded.
  
  Manually loading the module results in:
  me@mysys /home/me $ sudo modprobe nvidia
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='nvidia_384'
  modprobe: ERROR: could not insert 'nvidia_384': Unknown symbol in module, or 
unknown parameter (see dmesg)
  me@mysys /home/me $ 
  
  The weird thing: there is nothing in dmesg and nothing in syslog.
  Reboot with kernel 4.13.0-43 (or older) and everything works again.
  
  me@mysys ~ $ uname -a
  Linux sesta10 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17 12:56:46 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  me@mysys ~ $ lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 18.3 Sylvia
  Release:  18.3
  Codename: sylvia
  me@mysys ~ $ 
  
- Please advise how to give more useful informations - I tried "ubuntu-bug
- linux" and "ubuntu-bug linux-image-4.15.0-29-generic" in the faulty
- state (on the CLI of kernel 4.15), but it told me that this is no linux
- package.. ?
+ Please advise how to give more useful informations - I tried "ubuntu-bug 
linux" and "ubuntu-bug linux-image-4.15.0-29-generic" in the faulty state (on 
the CLI of kernel 4.15), but it told me that this is no linux package.. ?
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.18
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  seven  2770 F pulseaudio
+  /dev/snd/controlC0:  seven  2770 F pulseaudio
+  /dev/snd/controlC1:  seven  2770 F pulseaudio
+ CurrentDesktop: MATE
+ DistroRelease: Linux 18.3
+ HibernationDevice: RESUME=UUID=ec22f108-69f6-4433-841d-636bab5b8f60
+ InstallationDate: Installed on 2016-07-03 (750 days ago)
+ InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
+ IwConfig:
+  lono wireless extensions.
+  
+  enp0s31f6  no wireless extensions.
+  
+  anbox0no wireless extensions.
+ MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
+ Package: linux (not installed)
+ ProcFB: 0 VESA VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=67bad3d0-da8e-4293-97b1-a5c134911af0 ro nouveau.blacklist=1 quiet 
splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-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.157.20
+ RfKill:
+  
+ Tags:  sylvia
+ Uname: Linux 4.15.0-29-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: users
+ WifiSyslog:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 09/21/2015
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: P1.50
+ dmi.board.name: Z170 Extreme4+
+ dmi.board.vendor: ASRock
+ dmi.chassis.asset.tag: To Be Filled By O.E.M.
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: To Be Filled By O.E.M.
+ dmi.chassis.version: To Be Filled By O.E.M.
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd09/21/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Extreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
+ dmi.product.family: To Be Filled By O.E.M.
+ dmi.product.name: To Be Filled By O.E.M.
+ dmi.product.version: To Be Filled By O.E.M.
+ dmi.sys.vendor: To Be Filled By O.E.M.

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

Title:
  Kernel 4.15 fails to load nvidia module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Booting into kernel 4.15 results in no graphics acceleration. No
  nvidia module is loaded.

  Manually loading the module results in:
  me@mysys /home/me $ sudo modprobe nvidia
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='nvidia_384'
  modprobe: ERROR: could not insert 'nvidia_384': Unknown symbol in module, or 
unknown parameter (see dmesg)
  me@mysys /home/me $ 

  The weird thing: there is nothing in dmesg and nothing in syslog.
  Reboot with kernel 4.13.0-43 (or older) and everything works again.

  me@mysys ~ $ uname -a
  Linux sesta10 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17 12:56:46 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  me@mysys ~ $ lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  

[Kernel-packages] [Bug 1769443] Re: [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 LTS version

[Daniel van Vugt]

** Summary changed:

- Bluetooth is not working after updating my laptop to 18.04 LTS version
+ [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 LTS 
version

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

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

Title:
  [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04
  LTS version

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to
  send or receive files via bluetooth,please do give a emulsion of this
  hardware problem

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun May  6 15:26:50 2018
  DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GconfCompiz:
   /apps/compiz-1/general:
 /apps/compiz-1/general/screen0:
  /apps/compiz-1/general/screen0/options:
   active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:81e5]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1366x768+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move', 'vpswitch', 
'place', 'animation', 'snap', 'compiztoolbox', 'imgpng', 'workarounds', 'expo', 
'fade', 'session', 'ezoom', 'switcher', 'scale', 'unityshell']"
  InstallationDate: Installed on 2016-11-07 (544 days ago)
  InstallationMedia:
   
  MachineType: HP HP 245 G5 Notebook PC
  MonitorsUser.xml:
   
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash
  SourcePackage: compiz
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago)
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81E5
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 73.15
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245
  dmi.product.name: HP 245 G5 Notebook PC
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1783229

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

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

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

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

** Tags added: artful

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

Title:
  Kernel 4.15 fails to load nvidia module

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Booting into kernel 4.15 results in no graphics acceleration. No
  nvidia module is loaded.

  Manually loading the module results in:
  me@mysys /home/me $ sudo modprobe nvidia
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='nvidia_384'
  modprobe: ERROR: could not insert 'nvidia_384': Unknown symbol in module, or 
unknown parameter (see dmesg)
  me@mysys /home/me $ 

  The weird thing: there is nothing in dmesg and nothing in syslog.
  Reboot with kernel 4.13.0-43 (or older) and everything works again.

  me@mysys ~ $ uname -a
  Linux sesta10 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17 12:56:46 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  me@mysys ~ $ lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 18.3 Sylvia
  Release:  18.3
  Codename: sylvia
  me@mysys ~ $ 

  Please advise how to give more useful informations - I tried "ubuntu-
  bug linux" and "ubuntu-bug linux-image-4.15.0-29-generic" in the
  faulty state (on the CLI of kernel 4.15), but it told me that this is
  no linux package.. ?

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

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

[Kernel-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  hinic interfaces aren't getting predictable names

Status in linux package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Invalid

Bug description:
  On a HiSilicon D06 system we noticed that interfaces provided by a
  plug-in "HINIC" network card are not getting assigned predictable
  names. We're getting "ethX" names instead of the expected "enPblah"
  names.

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

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

[Kernel-packages] [Bug 1783229] Re: Kernel 4.15 fails to load nvidia module

[Nicolas Krzywinski]

** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783229/+attachment/5166880/+files/version.log

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

Title:
  Kernel 4.15 fails to load nvidia module

Status in linux package in Ubuntu:
  New

Bug description:
  Booting into kernel 4.15 results in no graphics acceleration. No
  nvidia module is loaded.

  Manually loading the module results in:
  me@mysys /home/me $ sudo modprobe nvidia
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='nvidia_384'
  modprobe: ERROR: could not insert 'nvidia_384': Unknown symbol in module, or 
unknown parameter (see dmesg)
  me@mysys /home/me $ 

  The weird thing: there is nothing in dmesg and nothing in syslog.
  Reboot with kernel 4.13.0-43 (or older) and everything works again.

  me@mysys ~ $ uname -a
  Linux sesta10 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17 12:56:46 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  me@mysys ~ $ lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 18.3 Sylvia
  Release:  18.3
  Codename: sylvia
  me@mysys ~ $ 

  Please advise how to give more useful informations - I tried "ubuntu-
  bug linux" and "ubuntu-bug linux-image-4.15.0-29-generic" in the
  faulty state (on the CLI of kernel 4.15), but it told me that this is
  no linux package.. ?

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

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

[Kernel-packages] [Bug 1783229] Re: Kernel 4.15 fails to load nvidia module

[Nicolas Krzywinski]

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783229/+attachment/5166881/+files/lspci-vnvn.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/1783229

Title:
  Kernel 4.15 fails to load nvidia module

Status in linux package in Ubuntu:
  New

Bug description:
  Booting into kernel 4.15 results in no graphics acceleration. No
  nvidia module is loaded.

  Manually loading the module results in:
  me@mysys /home/me $ sudo modprobe nvidia
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='nvidia_384'
  modprobe: ERROR: could not insert 'nvidia_384': Unknown symbol in module, or 
unknown parameter (see dmesg)
  me@mysys /home/me $ 

  The weird thing: there is nothing in dmesg and nothing in syslog.
  Reboot with kernel 4.13.0-43 (or older) and everything works again.

  me@mysys ~ $ uname -a
  Linux sesta10 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17 12:56:46 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  me@mysys ~ $ lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 18.3 Sylvia
  Release:  18.3
  Codename: sylvia
  me@mysys ~ $ 

  Please advise how to give more useful informations - I tried "ubuntu-
  bug linux" and "ubuntu-bug linux-image-4.15.0-29-generic" in the
  faulty state (on the CLI of kernel 4.15), but it told me that this is
  no linux package.. ?

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

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

[Kernel-packages] [Bug 1781016] Re: Slow flood of do_IRQ: No irq for vector

[spike speigel]

Ubuntu does not appear to be the only one with this issue on the 4.15 kernel:
https://bugzilla.redhat.com/show_bug.cgi?id=1551605

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

Title:
  Slow flood of do_IRQ: No irq for vector

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Every few seconds I get something like this in my dmesg:

  [44984.933221] do_IRQ: 1.34 No irq handler for vector
  [44986.933976] do_IRQ: 1.34 No irq handler for vector
  [44991.935614] do_IRQ: 1.34 No irq handler for vector
  [45004.938590] do_IRQ: 1.34 No irq handler for vector
  [45005.939002] do_IRQ: 4.34 No irq handler for vector
  [45034.949161] do_IRQ: 4.34 No irq handler for vector
  [45051.954569] do_IRQ: 4.34 No irq handler for vector
  [45058.956019] do_IRQ: 4.34 No irq handler for vector
  [45062.957727] do_IRQ: 4.34 No irq handler for vector
  [45063.958204] do_IRQ: 4.34 No irq handler for vector
  [45073.961103] do_IRQ: 4.34 No irq handler for vector

  The numbers vary. Some examples are 4.34, 4.36, 1.34, 0.33, 6.34,
  7.33, 5.37. Eventually dmesg's ring buffer is full and my entire log
  is just messages like above with varying #.## numbers.

  I researched it and tried disabling irqbalance. It had no effect, the
  messages continued.

  The system is a Ryzen 2700X with B350 chipset on Asus Prime B350-PLUS.
  I have 64GB of Kingston DDR4-2400 ECC memory and Samsung 960 PRO M.2
  NVMe SSD, and an Intel I350-T4 quad port gigabit NIC. This issue never
  occurred before installing 18.03 on the same hardware. No overclocking
  whatsoever has ever been done to this machine.

  Also, I had to disable selective suspend on USB in this version to
  prevent major USB issues, which was not required in 17.10, that might
  be related.

  My system seems stable, but spurious IRQs can't be good. I'd like to
  resolve this if possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-26-generic 4.15.0-26.28
  ProcVersionSignature: Ubuntu 4.15.0-26.28-generic 4.15.18
  Uname: Linux 4.15.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2145 F pulseaudio
doug   3736 F pulseaudio
   /dev/snd/controlC1:  gdm2145 F pulseaudio
doug   3736 F pulseaudio
  Date: Tue Jul 10 12:49:00 2018
  HibernationDevice:
   
  InstallationDate: Installed on 2017-06-26 (379 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-26-generic 
root=UUID=53446747-0814-48f7-b7c4-7fd7d7234d83 ro video=vesa:off vga=normal 
video=efifb:off usbcore.autosuspend=-1 usbhid.quirks=0x1e71:0x170e:0x4
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-26-generic N/A
   linux-backports-modules-4.15.0-26-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4011
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B350-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4011:bd04/19/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1781016] Re: Slow flood of do_IRQ: No irq for vector

[spike speigel]

Same here.  Not sure when this started:

~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04 LTS
Release:18.04
Codename:   bionic

~$ uname -a
Linux w00t 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

~$ dmesg

[ 2864.829849] do_IRQ: 2.33 No irq handler for vector
[ 2865.830173] do_IRQ: 2.33 No irq handler for vector
[ 2866.830508] do_IRQ: 2.33 No irq handler for vector
[ 2867.830819] do_IRQ: 2.33 No irq handler for vector
[ 2868.831143] do_IRQ: 2.33 No irq handler for vector
[ 2874.833340] do_IRQ: 2.33 No irq handler for vector
[ 2875.833649] do_IRQ: 2.33 No irq handler for vector
[ 2876.833973] do_IRQ: 2.33 No irq handler for vector
[ 2877.834289] do_IRQ: 2.33 No irq handler for vector
[ 2878.834606] do_IRQ: 2.33 No irq handler for vector
[ 2879.834868] do_IRQ: 2.33 No irq handler for vector
[ 2880.835212] do_IRQ: 2.33 No irq handler for vector
[ 2881.835559] do_IRQ: 2.33 No irq handler for vector
[ 2882.835855] do_IRQ: 2.33 No irq handler for vector
[ 2883.836186] do_IRQ: 2.33 No irq handler for vector
[ 2889.838551] do_IRQ: 2.33 No irq handler for vector
[ 2890.838868] do_IRQ: 2.33 No irq handler for vector
[ 2892.839543] do_IRQ: 2.33 No irq handler for vector


** Bug watch added: Red Hat Bugzilla #1551605
   https://bugzilla.redhat.com/show_bug.cgi?id=1551605

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

Title:
  Slow flood of do_IRQ: No irq for vector

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Every few seconds I get something like this in my dmesg:

  [44984.933221] do_IRQ: 1.34 No irq handler for vector
  [44986.933976] do_IRQ: 1.34 No irq handler for vector
  [44991.935614] do_IRQ: 1.34 No irq handler for vector
  [45004.938590] do_IRQ: 1.34 No irq handler for vector
  [45005.939002] do_IRQ: 4.34 No irq handler for vector
  [45034.949161] do_IRQ: 4.34 No irq handler for vector
  [45051.954569] do_IRQ: 4.34 No irq handler for vector
  [45058.956019] do_IRQ: 4.34 No irq handler for vector
  [45062.957727] do_IRQ: 4.34 No irq handler for vector
  [45063.958204] do_IRQ: 4.34 No irq handler for vector
  [45073.961103] do_IRQ: 4.34 No irq handler for vector

  The numbers vary. Some examples are 4.34, 4.36, 1.34, 0.33, 6.34,
  7.33, 5.37. Eventually dmesg's ring buffer is full and my entire log
  is just messages like above with varying #.## numbers.

  I researched it and tried disabling irqbalance. It had no effect, the
  messages continued.

  The system is a Ryzen 2700X with B350 chipset on Asus Prime B350-PLUS.
  I have 64GB of Kingston DDR4-2400 ECC memory and Samsung 960 PRO M.2
  NVMe SSD, and an Intel I350-T4 quad port gigabit NIC. This issue never
  occurred before installing 18.03 on the same hardware. No overclocking
  whatsoever has ever been done to this machine.

  Also, I had to disable selective suspend on USB in this version to
  prevent major USB issues, which was not required in 17.10, that might
  be related.

  My system seems stable, but spurious IRQs can't be good. I'd like to
  resolve this if possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-26-generic 4.15.0-26.28
  ProcVersionSignature: Ubuntu 4.15.0-26.28-generic 4.15.18
  Uname: Linux 4.15.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2145 F pulseaudio
doug   3736 F pulseaudio
   /dev/snd/controlC1:  gdm2145 F pulseaudio
doug   3736 F pulseaudio
  Date: Tue Jul 10 12:49:00 2018
  HibernationDevice:
   
  InstallationDate: Installed on 2017-06-26 (379 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-26-generic 
root=UUID=53446747-0814-48f7-b7c4-7fd7d7234d83 ro video=vesa:off vga=normal 
video=efifb:off usbcore.autosuspend=-1 usbhid.quirks=0x1e71:0x170e:0x4
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-26-generic N/A
   linux-backports-modules-4.15.0-26-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  

[Kernel-packages] [Bug 1783229] [NEW] Kernel 4.15 fails to load nvidia module

[Nicolas Krzywinski]

Public bug reported:

Booting into kernel 4.15 results in no graphics acceleration. No nvidia
module is loaded.

Manually loading the module results in:
me@mysys /home/me $ sudo modprobe nvidia
modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='nvidia_384'
modprobe: ERROR: could not insert 'nvidia_384': Unknown symbol in module, or 
unknown parameter (see dmesg)
me@mysys /home/me $ 

The weird thing: there is nothing in dmesg and nothing in syslog.
Reboot with kernel 4.13.0-43 (or older) and everything works again.

me@mysys ~ $ uname -a
Linux sesta10 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17 12:56:46 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
me@mysys ~ $ lsb_release -a
LSB Version:
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
Distributor ID: LinuxMint
Description:Linux Mint 18.3 Sylvia
Release:18.3
Codename:   sylvia
me@mysys ~ $ 

Please advise how to give more useful informations - I tried "ubuntu-bug
linux" and "ubuntu-bug linux-image-4.15.0-29-generic" in the faulty
state (on the CLI of kernel 4.15), but it told me that this is no linux
package.. ?

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

Title:
  Kernel 4.15 fails to load nvidia module

Status in linux package in Ubuntu:
  New

Bug description:
  Booting into kernel 4.15 results in no graphics acceleration. No
  nvidia module is loaded.

  Manually loading the module results in:
  me@mysys /home/me $ sudo modprobe nvidia
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='nvidia_384'
  modprobe: ERROR: could not insert 'nvidia_384': Unknown symbol in module, or 
unknown parameter (see dmesg)
  me@mysys /home/me $ 

  The weird thing: there is nothing in dmesg and nothing in syslog.
  Reboot with kernel 4.13.0-43 (or older) and everything works again.

  me@mysys ~ $ uname -a
  Linux sesta10 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17 12:56:46 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  me@mysys ~ $ lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 18.3 Sylvia
  Release:  18.3
  Codename: sylvia
  me@mysys ~ $ 

  Please advise how to give more useful informations - I tried "ubuntu-
  bug linux" and "ubuntu-bug linux-image-4.15.0-29-generic" in the
  faulty state (on the CLI of kernel 4.15), but it told me that this is
  no linux package.. ?

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

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

[Kernel-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names

[dann frazier]

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

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

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: linux (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/1783138

Title:
  hinic interfaces aren't getting predictable names

Status in linux package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Invalid

Bug description:
  On a HiSilicon D06 system we noticed that interfaces provided by a
  plug-in "HINIC" network card are not getting assigned predictable
  names. We're getting "ethX" names instead of the expected "enPblah"
  names.

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

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

[Kernel-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names

[Dimitri John Ledkov]

Is this critical for 18.04.1 release?

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

Title:
  hinic interfaces aren't getting predictable names

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

Bug description:
  On a HiSilicon D06 system we noticed that interfaces provided by a
  plug-in "HINIC" network card are not getting assigned predictable
  names. We're getting "ethX" names instead of the expected "enPblah"
  names.

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1783138

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

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

Title:
  hinic interfaces aren't getting predictable names

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

Bug description:
  On a HiSilicon D06 system we noticed that interfaces provided by a
  plug-in "HINIC" network card are not getting assigned predictable
  names. We're getting "ethX" names instead of the expected "enPblah"
  names.

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

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

[Kernel-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names

[dann frazier]

fyi, this appears to fix the problem for me.

** Patch added: 
"0001-hinic-Link-the-logical-network-device-to-the-pci-dev.patch"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783138/+attachment/5166848/+files/0001-hinic-Link-the-logical-network-device-to-the-pci-dev.patch

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

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

Title:
  hinic interfaces aren't getting predictable names

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

Bug description:
  On a HiSilicon D06 system we noticed that interfaces provided by a
  plug-in "HINIC" network card are not getting assigned predictable
  names. We're getting "ethX" names instead of the expected "enPblah"
  names.

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

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

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

[bugproxy]

--- Comment From s...@us.ibm.com 2018-07-23 16:30 EDT---
I think the key patch (from LP 1632045) was pulled in as of 4.4.0-51.72.  As 
far as I can tell, the CMA debugging is not in ubuntu (actually, I'm not 
positive it was even pulled in upstream, but that's less immediately 
important). I will continue to poke, but I don't think there's a good way even 
to determine, without a kdump, where that memory is in use.  I think the only 
thing to do is try to work around the problem by devoting more memory to the 
CMA by specifying a boot parameter like cma=50g for example. That would at 
least greatly alleviate  the problem, though not fix it. To fix it, I think we 
will need to arrange for a kdump from a failing system and then see exactly 
where the memory is in use.

I will keep asking my colleagues; however, that's where I am for now.

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

Title:
  KVM guest hash page table failed to allocate contiguous memory (CMA)

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

Bug description:
  Per an email forwarded within IBM, we wish to use this Launchpad bug
  to work on the technical discussion with the Canonical development
  folks and the IBM KVM and kernel team surrounding the analysis made by
  Daniel Axtens of Canonical for the customer issue raised in Case
  #00177825.

  The only statement at the moment by the KVM team was that there were
  various issues associated with CMA fragmentation causing issues with
  KVM guests. However, as mentioned, this bug is to allow the dialog
  amongst all the developers to see what can be done to help alleviate
  the situation or understand the root cause further.

  Please also note that we should not be attaching customer data to this
  bug. If that is necessary then we expect Canonical to help provide a
  controlled environment for reviewing that data so we avoid any privacy
  issues (e.g. for GDPR compliance).

  Here is the email from Daniel:

  I have looked at the sosreport you uploaded. Here is my analysis so
  far.

  Virtualisation on powerpc has some special requirements. To start a
  guest on a powerpc host, you need to allocate a contiguous area of
  memory to hold the guest's hash page table (HPT, or HTAB, depending on
  which document you look at). The HPT is required to track and manage
  guest memory.

  Your error reports show qemu asking the kernel to allocate an HTAB,
  and the kernel reporting that it had insufficient memory to do so. The
  required memory for the HPT scales with the guest memory size - it
  should be about 1/128th of guest memory, so for a 16GB guest, that's
  128MB. However, the HPT has to be allocated as a single contiguous
  memory region. (This is in contrast to regular guest memory, which is
  not required to be contiguous from the host point of view.)

  The kernel keeps a special contiguous memory area (CMA) for these
  purposes, and keeps track of the total amounts in use and still
  available. These are shown in /proc/meminfo. From the system that ran
  the sosreport, we see:

  CmaTotal: 26853376 kB
  CmaFree: 4024448 kB

  So there is a total of about 25GB of CMA, of which about 3.8GB remain.
  This is obviously more than 128MB:

  - It's very possible that between the error and the sosreport, more
  contiguous memory became available. This would match the intermittent
  nature of the issue.

  - It also might be that the failure was due to fragmentation of memory
  in the CMA pool. That is, there might be more than 128MB, but it might
  all be in chunks that are smaller than 128MB, or which don't have the
  required alignment for a HPT.

  Given that the system's uptime was 112 days when the sosreport was
  generated, it would be unsurprising if fragmentation had occurred!
  (Relatedly - you're running 4.4.0-109, which does not have the Spectre
  and Meltdown fixes.)

  This issue has come up before - both in a public Canonical-IBM
  synchronised bug report[1], and with Red Hat[2]. It appears that there
  is some work within IBM to address this, but it seems to have stalled.
  I will get in touch with the IBM powerpc kernel team on their public
  mailing list and ask about the status. I will keep you updated.

  In the mean time, I have a potential solution/workaround. By default,
  5% of memory is reserved for CMA (kernel source:
  arch/powerpc/kvm/book3s_hv_builtin.c, kvm_cma_resv_ratio). You can
  increase this with a boot parameter, so for example to reserve 10%,
  you could boot with kvm_cma_resv_ratio=10. This can be set in
  petitboot. This should significantly reduce the incidence of this
  issue - perhaps eliminating it entirely - at the cost of locking away
  more of the system's memory. You would need to experiment to determine
  the optimal value. Perhaps given that you are seeing the problem 

[Kernel-packages] [Bug 1783201] [NEW] Cosmic update to 4.17.9 stable release

[Thadeu Lima de Souza Cascardo]

Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The 4.17.9 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the 4.17.9 stable release shall be
applied:

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


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-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/1783201

Title:
  Cosmic update to 4.17.9 stable release

Status in linux package in Ubuntu:
  New

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The 4.17.9 upstream stable
 patch set is now available. It should be included in the Ubuntu
 kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.17.9 stable release shall be
  applied:

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

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

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

[Thadeu Lima de Souza Cascardo]

Server doesn't crash when using the package from bionic-proposed.

** Tags removed: verification-needed-bionic
** Tags added: verification-done-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/1772024

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

Status in linux package in Ubuntu:
  In Progress
Status in nbd package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  New
Status in nbd source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  New
Status in nbd source package in Xenial:
  Invalid
Status in linux source package in Artful:
  New
Status in nbd source package in Artful:
  Incomplete
Status in linux source package in Bionic:
  New
Status in nbd source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  In Progress
Status in nbd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  nbd-server will crash when a client connects to it, if it was started without 
a server name. It may also leak fds if fork fails.

  [Test Case]
  Running the server with an empty config file and an image on the command 
line, and then starting a local client will crash the server. After the fix, it 
doesn't crash anymore, and a filesystem may be created and used after that.

  [Regression Potential]
  The fix also implies a small package change, to use quilt. It has built just 
fine and many tests have been run on top of those packages and no failure 
seemed to be the result of those userspace changes, but known failures in the 
kernel driver.

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

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

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

[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension

[DiegoRivera]

If unloading-and-reloading the r8169 module solves the problem for you,
here's a workaround that does it automatically for you upon resume from
suspend:

1) Create a file /etc/systemd/system/fix-r8169.service  with the
following contents:

 BEGIN FILE 
[Unit]
Description=Fix RTL-8169 Driver on resume from suspend
After=suspend.target

[Service]
User=root
Type=oneshot
ExecStartPre=/sbin/modprobe -r r8169
ExecStart=/sbin/modprobe r8169
TimeoutSec=0
StandardOutput=syslog

[Install]
WantedBy=suspend.target
# END FILE #

2) Execute the following command: sudo systemctl enable
fix-r8169.service

Cheers!

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

Title:
  r8169 ethernet card don't work after returning from suspension

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

Bug description:
  ===SRU Justification===
  [Impact]
  Ethernet r8169 stops working after system resumed from suspend.

  [Test]
  User confirmed these patches fix the issue. r8169 continues to work
  after resume from suspend.

  [Regression Potential]
  Medium. The fix is limited to one device, all patches are in mainline.
  The WOL default change might cause regression for users that depend on
  BIOS settings. We can advice them to use userspace tool (systemd,
  ethtool, etc.) instead.

  ===Original Bug Report===
  I have noticed that the network stopped working on my desktop after I've 
suspended the system and woke it up. On dmesg there are messages like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity:
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:

  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
     Mixer name : 'VIA VT1818S'
     Components : 'HDA:11060440,18492818,0010'
     Controls  : 40
     Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
     Mixer name : 'ATI R6xx HDMI'
     Components : 'HDA:1002aa01,00aa0100,00100200'
     Controls  : 7
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined
     Playback channels: Mono
     Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:

  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  

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

[bugproxy]

--- Comment From s...@us.ibm.com 2018-07-23 15:10 EDT---
I'm still looking. I'm confident that daniel has correctly identified and 
explained the failure mode (i.e. out of enough CMA to create guests).  I also 
don't *think* we have enough information at the moment to say for sure why this 
particular memory pool is exhausted; however, I'm still poking around to see 
what information we *do* need.

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

Title:
  KVM guest hash page table failed to allocate contiguous memory (CMA)

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

Bug description:
  Per an email forwarded within IBM, we wish to use this Launchpad bug
  to work on the technical discussion with the Canonical development
  folks and the IBM KVM and kernel team surrounding the analysis made by
  Daniel Axtens of Canonical for the customer issue raised in Case
  #00177825.

  The only statement at the moment by the KVM team was that there were
  various issues associated with CMA fragmentation causing issues with
  KVM guests. However, as mentioned, this bug is to allow the dialog
  amongst all the developers to see what can be done to help alleviate
  the situation or understand the root cause further.

  Please also note that we should not be attaching customer data to this
  bug. If that is necessary then we expect Canonical to help provide a
  controlled environment for reviewing that data so we avoid any privacy
  issues (e.g. for GDPR compliance).

  Here is the email from Daniel:

  I have looked at the sosreport you uploaded. Here is my analysis so
  far.

  Virtualisation on powerpc has some special requirements. To start a
  guest on a powerpc host, you need to allocate a contiguous area of
  memory to hold the guest's hash page table (HPT, or HTAB, depending on
  which document you look at). The HPT is required to track and manage
  guest memory.

  Your error reports show qemu asking the kernel to allocate an HTAB,
  and the kernel reporting that it had insufficient memory to do so. The
  required memory for the HPT scales with the guest memory size - it
  should be about 1/128th of guest memory, so for a 16GB guest, that's
  128MB. However, the HPT has to be allocated as a single contiguous
  memory region. (This is in contrast to regular guest memory, which is
  not required to be contiguous from the host point of view.)

  The kernel keeps a special contiguous memory area (CMA) for these
  purposes, and keeps track of the total amounts in use and still
  available. These are shown in /proc/meminfo. From the system that ran
  the sosreport, we see:

  CmaTotal: 26853376 kB
  CmaFree: 4024448 kB

  So there is a total of about 25GB of CMA, of which about 3.8GB remain.
  This is obviously more than 128MB:

  - It's very possible that between the error and the sosreport, more
  contiguous memory became available. This would match the intermittent
  nature of the issue.

  - It also might be that the failure was due to fragmentation of memory
  in the CMA pool. That is, there might be more than 128MB, but it might
  all be in chunks that are smaller than 128MB, or which don't have the
  required alignment for a HPT.

  Given that the system's uptime was 112 days when the sosreport was
  generated, it would be unsurprising if fragmentation had occurred!
  (Relatedly - you're running 4.4.0-109, which does not have the Spectre
  and Meltdown fixes.)

  This issue has come up before - both in a public Canonical-IBM
  synchronised bug report[1], and with Red Hat[2]. It appears that there
  is some work within IBM to address this, but it seems to have stalled.
  I will get in touch with the IBM powerpc kernel team on their public
  mailing list and ask about the status. I will keep you updated.

  In the mean time, I have a potential solution/workaround. By default,
  5% of memory is reserved for CMA (kernel source:
  arch/powerpc/kvm/book3s_hv_builtin.c, kvm_cma_resv_ratio). You can
  increase this with a boot parameter, so for example to reserve 10%,
  you could boot with kvm_cma_resv_ratio=10. This can be set in
  petitboot. This should significantly reduce the incidence of this
  issue - perhaps eliminating it entirely - at the cost of locking away
  more of the system's memory. You would need to experiment to determine
  the optimal value. Perhaps given that you are seeing the problem only
  intermittently, a ratio of 7% would be sufficient - that would give
  you ~35GB of CMA.

  Please let me know if testing this setting would be an option for you.
  Please also let me know if you require further information on setting
  boot parameters with Petitboot.

  Regards,
  Daniel

  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1632045
  [2] https://bugzilla.redhat.com/show_bug.cgi?id=1304300

  Before we go any 

[Kernel-packages] [Bug 1781001] Re: DKMS seems to hang after installing a module.

[Launchpad Bug Tracker]

This bug was fixed in the package dkms - 2.3-3ubuntu9.2

---
dkms (2.3-3ubuntu9.2) bionic; urgency=medium

  * 0009-Add-support-for-UEFI-Secure-Boot-validation-toggling.patch: source
/usr/share/debconf/confmodule from dkms_common.postinst to ensure we have
all the environment ready to successfully show debconf prompts when dkms
modules are being built. (LP: #1781001)

 -- Mathieu Trudel-Lapierre   Wed, 18 Jul 2018
09:33:31 -0400

** Changed in: dkms (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  DKMS seems to hang after installing a module.

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  All users of third-party modules on Ubuntu when running under SecureBoot 
experience a package manager hang trying to initially configure the dkms 
package from the commandline.

  [Test cases]
  1) Install Ubuntu on an UEFI system
  2) Clear any files in /var/lib/shim-signed/mok: "sudo rm -rf 
/var/lib/shim-signed/mok/*"
  3) Install virtualbox-dkms: "sudo apt install virtualbox-dkms"
  4) Verify that you are prompted for a password to enroll a new MOK, and that 
you are asked that password at reboot.

  Without the patch, no prompt will appear at install of virtualbox-
  dkms.

  [Regression Potential]
  Shuffling of file descriptors as required by this change may impact dkms 
builds if these builds do special steps requiring different file descriptors. 
Any failure to install a -dkms package should be investigated as a potential 
regression coming from this SRU.

  

  (while gathering info for this bugreport, my knowledge about this
  issue has been growing. So the top part was written with not
  everything known yet)

  In my case I installed tp_smapi, but on the internet I've found others
  that have installed other modules.

  When configuring the tp-smapi-dkms package it says it will uninstall
  the module first and the it reports: Building initial module for
  4.15.0-23-generic

  After that it hangs, or so it seems. It turns out that somewhere in
  there a script is being called with output redirected to /dev/null.
  But under certain circumstances, in my case "the computer is
  configured for secure boot", whiptail is being called asking for a
  password.

  Whiptail outputs curses codes to write stuff to the screen but that is
  redirected to /dev/null. It then waits for input from the user. I've
  debugged this to the point that it is saying this:

   whiptail --backtitle Package configuration --title Configuring Secure
  Boot --output-fd 12 --nocancel --msgbox Your system has UEFI Secure
  Boot enabled.  UEFI Secure Boot requires additional configuration to
  work with  third-party drivers.  The system will assist you in
  configuring UEFI Secure Boot. To permit  the use of third-party
  drivers, a new Machine-Owner Key (MOK) has been  generated. This key
  now needs to be enrolled in your system's firmware.  To ensure that
  this change is being made by you as an authorized user,  and not by an
  attacker, you must choose a password now and then confirm  the change
  after reboot using the same password, in both the "Enroll  MOK" and
  "Change Secure Boot state" menus that will be presented to you  when
  this system reboots.  If you proceed but do not confirm the password
  upon reboot, Ubuntu will  still be able to boot on your system but any
  hardware that requires  third-party drivers to work correctly may not
  be usable. --scrolltext 20 77

  but, as I said the output is redirected to /dev/null.

  The call-tree is as follows:
  
-dpkg(18879)---tp-smapi-dkms.p(18880)---common.postinst(18881)---dkms(19146)---dkms(19161)---frontend(20224)-+-update-securebo(20238)
     |   |  

 `-whiptail(20253)

  (with the update-secureboot and whiptail both being children from "frontend". 
).
  The tp-smapi-dkms.postinst  program is still being called with stdout 
connected to my controlling terminal. The common.postinst has stdout connected 
ot /dev/null, so I'd first look in /var/lib/dpkg/info/tp-smapi-dkms.postinst
  I have looked there, and I don't see a reason why it would redirect the 
output of a subprocess to /dev/null. (the word does not occur in the short 
script.)
  Alternatively I'd think that maybe the subprocess 
/usr/lib/dkms/common.postinst would redirect its own stdout to /dev/null.

  On the other hand I found
    dkms build -m $NAME -v $VERSION -k $KERNEL $ARCH > /dev/null

  which explains the dkms subprocess running with output redirected to
  devnull, but not why the common.postinst runs with output 

[Kernel-packages] [Bug 1781001] Update Released

[Adam Conrad]

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

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

Title:
  DKMS seems to hang after installing a module.

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  All users of third-party modules on Ubuntu when running under SecureBoot 
experience a package manager hang trying to initially configure the dkms 
package from the commandline.

  [Test cases]
  1) Install Ubuntu on an UEFI system
  2) Clear any files in /var/lib/shim-signed/mok: "sudo rm -rf 
/var/lib/shim-signed/mok/*"
  3) Install virtualbox-dkms: "sudo apt install virtualbox-dkms"
  4) Verify that you are prompted for a password to enroll a new MOK, and that 
you are asked that password at reboot.

  Without the patch, no prompt will appear at install of virtualbox-
  dkms.

  [Regression Potential]
  Shuffling of file descriptors as required by this change may impact dkms 
builds if these builds do special steps requiring different file descriptors. 
Any failure to install a -dkms package should be investigated as a potential 
regression coming from this SRU.

  

  (while gathering info for this bugreport, my knowledge about this
  issue has been growing. So the top part was written with not
  everything known yet)

  In my case I installed tp_smapi, but on the internet I've found others
  that have installed other modules.

  When configuring the tp-smapi-dkms package it says it will uninstall
  the module first and the it reports: Building initial module for
  4.15.0-23-generic

  After that it hangs, or so it seems. It turns out that somewhere in
  there a script is being called with output redirected to /dev/null.
  But under certain circumstances, in my case "the computer is
  configured for secure boot", whiptail is being called asking for a
  password.

  Whiptail outputs curses codes to write stuff to the screen but that is
  redirected to /dev/null. It then waits for input from the user. I've
  debugged this to the point that it is saying this:

   whiptail --backtitle Package configuration --title Configuring Secure
  Boot --output-fd 12 --nocancel --msgbox Your system has UEFI Secure
  Boot enabled.  UEFI Secure Boot requires additional configuration to
  work with  third-party drivers.  The system will assist you in
  configuring UEFI Secure Boot. To permit  the use of third-party
  drivers, a new Machine-Owner Key (MOK) has been  generated. This key
  now needs to be enrolled in your system's firmware.  To ensure that
  this change is being made by you as an authorized user,  and not by an
  attacker, you must choose a password now and then confirm  the change
  after reboot using the same password, in both the "Enroll  MOK" and
  "Change Secure Boot state" menus that will be presented to you  when
  this system reboots.  If you proceed but do not confirm the password
  upon reboot, Ubuntu will  still be able to boot on your system but any
  hardware that requires  third-party drivers to work correctly may not
  be usable. --scrolltext 20 77

  but, as I said the output is redirected to /dev/null.

  The call-tree is as follows:
  
-dpkg(18879)---tp-smapi-dkms.p(18880)---common.postinst(18881)---dkms(19146)---dkms(19161)---frontend(20224)-+-update-securebo(20238)
     |   |  

 `-whiptail(20253)

  (with the update-secureboot and whiptail both being children from "frontend". 
).
  The tp-smapi-dkms.postinst  program is still being called with stdout 
connected to my controlling terminal. The common.postinst has stdout connected 
ot /dev/null, so I'd first look in /var/lib/dpkg/info/tp-smapi-dkms.postinst
  I have looked there, and I don't see a reason why it would redirect the 
output of a subprocess to /dev/null. (the word does not occur in the short 
script.)
  Alternatively I'd think that maybe the subprocess 
/usr/lib/dkms/common.postinst would redirect its own stdout to /dev/null.

  On the other hand I found
    dkms build -m $NAME -v $VERSION -k $KERNEL $ARCH > /dev/null

  which explains the dkms subprocess running with output redirected to
  devnull, but not why the common.postinst runs with output redirected
  to devnull.

  Anyway. DKMS kernel module install postponed, apt  

[Kernel-packages] [Bug 1783167] Re: linux 4.17.0-5 fails to build on ppc64el with gcc-8

[Thadeu Lima de Souza Cascardo]

Commit bee20031772af3debe8cbaa234528f24c7892e8f (disable -Wattribute-
alias warning for SYSCALL_DEFINEx()) may fix this, now testing.

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

Title:
  linux 4.17.0-5 fails to build on ppc64el with gcc-8

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In file included from 
/tmp/kernel-cascardo-e4c3144-A9Vl/build/arch/powerpc/kernel/syscalls.c:24:
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:233:18: 
error: 'sys_mmap2' alias between functions of incompatible types 'l
  ong int(long unsigned int,  size_t,  long unsigned int,  long unsigned int,  
long unsigned int,  long unsigned int)' {aka 'long int(long uns
  igned int,  long unsigned int,  long unsigned int,  long unsigned int,  long 
unsigned int,  long unsigned int)'} and 'long int(long int,  lo
  ng int,  long int,  long int,  long int,  long int)' [-Werror=attribute-alias]
asmlinkage long sys##name(__MAP(x,__SC_DECL,__VA_ARGS__)) \
^~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:222:2: note: 
in expansion of macro '__SYSCALL_DEFINEx'
__SYSCALL_DEFINEx(x, sname, __VA_ARGS__)
^
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:216:36: 
note: in expansion of macro 'SYSCALL_DEFINEx'
   #define SYSCALL_DEFINE6(name, ...) SYSCALL_DEFINEx(6, _##name, __VA_ARGS__)
  ^~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/arch/powerpc/kernel/syscalls.c:65:1: 
note: in expansion of macro 'SYSCALL_DEFINE6'
   SYSCALL_DEFINE6(mmap2, unsigned long, addr, size_t, len,
   ^~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:238:18: 
note: aliased declaration here
asmlinkage long __se_sys##name(__MAP(x,__SC_LONG,__VA_ARGS__)) \
^~~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:222:2: note: 
in expansion of macro '__SYSCALL_DEFINEx'
__SYSCALL_DEFINEx(x, sname, __VA_ARGS__)
^
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:216:36: 
note: in expansion of macro 'SYSCALL_DEFINEx'
   #define SYSCALL_DEFINE6(name, ...) SYSCALL_DEFINEx(6, _##name, __VA_ARGS__)
  ^~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/arch/powerpc/kernel/syscalls.c:65:1: 
note: in expansion of macro 'SYSCALL_DEFINE6'
   SYSCALL_DEFINE6(mmap2, unsigned long, addr, size_t, len,
   ^~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:233:18: 
error: 'sys_mmap' alias between functions of incompatible types 'lo
  ng int(long unsigned int,  size_t,  long unsigned int,  long unsigned int,  
long unsigned int,  off_t)' {aka 'long int(long unsigned int,  l
  ong unsigned int,  long unsigned int,  long unsigned int,  long unsigned int, 
 long int)'} and 'long int(long int,  long int,  long int,  lo
  ng int,  long int,  long int)' [-Werror=attribute-alias]
asmlinkage long sys##name(__MAP(x,__SC_DECL,__VA_ARGS__)) \
^~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:222:2: note: 
in expansion of macro '__SYSCALL_DEFINEx'
__SYSCALL_DEFINEx(x, sname, __VA_ARGS__)
^
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:216:36: 
note: in expansion of macro 'SYSCALL_DEFINEx'
   #define SYSCALL_DEFINE6(name, ...) SYSCALL_DEFINEx(6, _##name, __VA_ARGS__)
  ^~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/arch/powerpc/kernel/syscalls.c:72:1: 
note: in expansion of macro 'SYSCALL_DEFINE6'
   SYSCALL_DEFINE6(mmap, unsigned long, addr, size_t, len,
   ^~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:238:18: 
note: aliased declaration here
asmlinkage long __se_sys##name(__MAP(x,__SC_LONG,__VA_ARGS__)) \
^~~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:222:2: note: 
in expansion of macro '__SYSCALL_DEFINEx'
__SYSCALL_DEFINEx(x, sname, __VA_ARGS__)
^
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:216:36: 
note: in expansion of macro 'SYSCALL_DEFINEx'
   #define SYSCALL_DEFINE6(name, ...) SYSCALL_DEFINEx(6, _##name, __VA_ARGS__)
  ^~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/arch/powerpc/kernel/syscalls.c:72:1: 
note: in expansion of macro 'SYSCALL_DEFINE6'
   SYSCALL_DEFINE6(mmap, unsigned long, addr, size_t, len,
   ^~~

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1783167

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

Title:
  linux 4.17.0-5 fails to build on ppc64el with gcc-8

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In file included from 
/tmp/kernel-cascardo-e4c3144-A9Vl/build/arch/powerpc/kernel/syscalls.c:24:
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:233:18: 
error: 'sys_mmap2' alias between functions of incompatible types 'l
  ong int(long unsigned int,  size_t,  long unsigned int,  long unsigned int,  
long unsigned int,  long unsigned int)' {aka 'long int(long uns
  igned int,  long unsigned int,  long unsigned int,  long unsigned int,  long 
unsigned int,  long unsigned int)'} and 'long int(long int,  lo
  ng int,  long int,  long int,  long int,  long int)' [-Werror=attribute-alias]
asmlinkage long sys##name(__MAP(x,__SC_DECL,__VA_ARGS__)) \
^~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:222:2: note: 
in expansion of macro '__SYSCALL_DEFINEx'
__SYSCALL_DEFINEx(x, sname, __VA_ARGS__)
^
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:216:36: 
note: in expansion of macro 'SYSCALL_DEFINEx'
   #define SYSCALL_DEFINE6(name, ...) SYSCALL_DEFINEx(6, _##name, __VA_ARGS__)
  ^~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/arch/powerpc/kernel/syscalls.c:65:1: 
note: in expansion of macro 'SYSCALL_DEFINE6'
   SYSCALL_DEFINE6(mmap2, unsigned long, addr, size_t, len,
   ^~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:238:18: 
note: aliased declaration here
asmlinkage long __se_sys##name(__MAP(x,__SC_LONG,__VA_ARGS__)) \
^~~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:222:2: note: 
in expansion of macro '__SYSCALL_DEFINEx'
__SYSCALL_DEFINEx(x, sname, __VA_ARGS__)
^
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:216:36: 
note: in expansion of macro 'SYSCALL_DEFINEx'
   #define SYSCALL_DEFINE6(name, ...) SYSCALL_DEFINEx(6, _##name, __VA_ARGS__)
  ^~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/arch/powerpc/kernel/syscalls.c:65:1: 
note: in expansion of macro 'SYSCALL_DEFINE6'
   SYSCALL_DEFINE6(mmap2, unsigned long, addr, size_t, len,
   ^~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:233:18: 
error: 'sys_mmap' alias between functions of incompatible types 'lo
  ng int(long unsigned int,  size_t,  long unsigned int,  long unsigned int,  
long unsigned int,  off_t)' {aka 'long int(long unsigned int,  l
  ong unsigned int,  long unsigned int,  long unsigned int,  long unsigned int, 
 long int)'} and 'long int(long int,  long int,  long int,  lo
  ng int,  long int,  long int)' [-Werror=attribute-alias]
asmlinkage long sys##name(__MAP(x,__SC_DECL,__VA_ARGS__)) \
^~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:222:2: note: 
in expansion of macro '__SYSCALL_DEFINEx'
__SYSCALL_DEFINEx(x, sname, __VA_ARGS__)
^
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:216:36: 
note: in expansion of macro 'SYSCALL_DEFINEx'
   #define SYSCALL_DEFINE6(name, ...) SYSCALL_DEFINEx(6, _##name, __VA_ARGS__)
  ^~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/arch/powerpc/kernel/syscalls.c:72:1: 
note: in expansion of macro 'SYSCALL_DEFINE6'
   SYSCALL_DEFINE6(mmap, unsigned long, addr, size_t, len,
   ^~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:238:18: 
note: aliased declaration here
asmlinkage long __se_sys##name(__MAP(x,__SC_LONG,__VA_ARGS__)) \
^~~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:222:2: note: 
in expansion of macro '__SYSCALL_DEFINEx'
__SYSCALL_DEFINEx(x, sname, __VA_ARGS__)
^
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:216:36: 
note: in expansion of macro 'SYSCALL_DEFINEx'
   #define SYSCALL_DEFINE6(name, ...) SYSCALL_DEFINEx(6, _##name, __VA_ARGS__)
  ^~~
  

[Kernel-packages] [Bug 1783169] [NEW] Installation of package linux-image-4.15.0-29-generic 4.15.0-29.31 failed to install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with return cod

[Vaughn Tolle]

Public bug reported:

Both 4.15.0-23 and 4.15.0-29 have failed for the same reason, it
appears.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-29-generic 4.15.0-29.31
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
AptOrdering:
 linux-headers-4.15.0-29:amd64: Install
 linux-modules-4.15.0-29-generic:amd64: Install
 linux-image-4.15.0-29-generic:amd64: Install
 linux-modules-extra-4.15.0-29-generic:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  vaughn 1362 F pulseaudio
 /dev/snd/controlC0:  vaughn 1362 F pulseaudio
Date: Mon Jul 23 11:47:39 2018
ErrorMessage: run-parts: /etc/kernel/header_postinst.d/dkms exited with return 
code 4
HibernationDevice: RESUME=UUID=f85c69a0-8f78-4c5c-951a-99bcf5a12b45
InstallationDate: Installed on 2018-04-29 (85 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
MachineType: Hewlett-Packard HP 15 Notebook PC
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=c004bf01-2c8f-4dfd-9bc7-c3b8715bfe1c ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions: grub-pc N/A
SourcePackage: dkms
Title: package linux-image-4.15.0-29-generic 4.15.0-29.31 failed to 
install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with 
return code 4
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/29/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.13
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 2330
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 99.0B
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd08/29/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr096C12405E00050660180:rvnHewlett-Packard:rn2330:rvr99.0B:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
dmi.product.name: HP 15 Notebook PC
dmi.product.version: 096C12405E00050660180
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-package bionic

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

Title:
  Installation of package linux-image-4.15.0-29-generic 4.15.0-29.31
  failed to install/upgrade: run-parts:
  /etc/kernel/header_postinst.d/dkms exited with return code 4

Status in dkms package in Ubuntu:
  New

Bug description:
  Both 4.15.0-23 and 4.15.0-29 have failed for the same reason, it
  appears.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-29-generic 4.15.0-29.31
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   linux-headers-4.15.0-29:amd64: Install
   linux-modules-4.15.0-29-generic:amd64: Install
   linux-image-4.15.0-29-generic:amd64: Install
   linux-modules-extra-4.15.0-29-generic:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vaughn 1362 F pulseaudio
   /dev/snd/controlC0:  vaughn 1362 F pulseaudio
  Date: Mon Jul 23 11:47:39 2018
  ErrorMessage: run-parts: /etc/kernel/header_postinst.d/dkms exited with 
return code 4
  HibernationDevice: RESUME=UUID=f85c69a0-8f78-4c5c-951a-99bcf5a12b45
  InstallationDate: Installed on 2018-04-29 (85 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=c004bf01-2c8f-4dfd-9bc7-c3b8715bfe1c ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: dkms
  Title: package linux-image-4.15.0-29-generic 4.15.0-29.31 failed to 
install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with 
return code 4
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: 

[Kernel-packages] [Bug 1778844] Re: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash, kdump is not working and system enters into initramfs state

[Thadeu Lima de Souza Cascardo]

Can you run apport-collect -p linux 1778844 ?

Thank you.
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/1778844

Title:
  ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
  crash,kdump is not working and system enters into initramfs state

Status in The Ubuntu-power-systems project:
  Triaged
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  New
Status in initramfs-tools source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in makedumpfile source package in Bionic:
  New

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
  [   73.058099] GPR08: 0007 0001  
90001003
  [   73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 

  [   73.058099] GPR16: 0e4f79cc94b0 0e4f79d567e0 0e4f79d88204 
0e4f79d56818
  [   73.058099] GPR20: 0e4f79d8d5d8 0001  
7efce644
  [   73.058099] GPR24: 7efce640 0e4f79d8afb4 c15e9aa8 
0002
  [   73.058099] 

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

[bugproxy]

--- Comment From frederic.bar...@fr.ibm.com 2018-07-23 12:58 EDT---
The test kernel found in
http://kernel.ubuntu.com/~jsalisbury/lp1781436
is for the wrong architecture (s390x instead of ppc64el).

Could you rebuild for ppc64el? Thanks

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

Title:
  Update2 for ocxl driver

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

Bug description:
  == Comment: #0 - Frederic Barrat - 2018-07-12 09:56:29 ==
  ---Problem Description---
  Update to ocxl driver
   
  Contact Information = frederic.bar...@fr.ibm.com 
   
  ---uname output---
  Linux zaiuslp14 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13 08:43:33 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  opencapi adapter 

   
  Machine Type = any Power9 with opencapi support 
   
  ---Debugger---
  A debugger is not configured
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for frederic.bar...@fr.ibm.com: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Frederic Barrat  - 2018-07-12 11:11:39 ==
  Could we have the following fix backported to ubuntu 18.04? It's to address a 
problem in the relatively new ocxl driver

  It's currently in the 'next' tree of the powerpc maintainer:
  d497ebf5fb3a026c0817f8c96cde578787f24093 ocxl: Fix page fault handler in case 
of fault on dying process

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=d497ebf5fb3a026c0817f8c96cde57

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

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

[Kernel-packages] [Bug 1783167] Re: linux 4.17.0-5 fails to build on ppc64el with gcc-8

[Thadeu Lima de Souza Cascardo]

** Attachment added: "build log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783167/+attachment/5166752/+files/gbk-ppc64el.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/1783167

Title:
  linux 4.17.0-5 fails to build on ppc64el with gcc-8

Status in linux package in Ubuntu:
  New

Bug description:
  In file included from 
/tmp/kernel-cascardo-e4c3144-A9Vl/build/arch/powerpc/kernel/syscalls.c:24:
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:233:18: 
error: 'sys_mmap2' alias between functions of incompatible types 'l
  ong int(long unsigned int,  size_t,  long unsigned int,  long unsigned int,  
long unsigned int,  long unsigned int)' {aka 'long int(long uns
  igned int,  long unsigned int,  long unsigned int,  long unsigned int,  long 
unsigned int,  long unsigned int)'} and 'long int(long int,  lo
  ng int,  long int,  long int,  long int,  long int)' [-Werror=attribute-alias]
asmlinkage long sys##name(__MAP(x,__SC_DECL,__VA_ARGS__)) \
^~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:222:2: note: 
in expansion of macro '__SYSCALL_DEFINEx'
__SYSCALL_DEFINEx(x, sname, __VA_ARGS__)
^
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:216:36: 
note: in expansion of macro 'SYSCALL_DEFINEx'
   #define SYSCALL_DEFINE6(name, ...) SYSCALL_DEFINEx(6, _##name, __VA_ARGS__)
  ^~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/arch/powerpc/kernel/syscalls.c:65:1: 
note: in expansion of macro 'SYSCALL_DEFINE6'
   SYSCALL_DEFINE6(mmap2, unsigned long, addr, size_t, len,
   ^~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:238:18: 
note: aliased declaration here
asmlinkage long __se_sys##name(__MAP(x,__SC_LONG,__VA_ARGS__)) \
^~~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:222:2: note: 
in expansion of macro '__SYSCALL_DEFINEx'
__SYSCALL_DEFINEx(x, sname, __VA_ARGS__)
^
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:216:36: 
note: in expansion of macro 'SYSCALL_DEFINEx'
   #define SYSCALL_DEFINE6(name, ...) SYSCALL_DEFINEx(6, _##name, __VA_ARGS__)
  ^~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/arch/powerpc/kernel/syscalls.c:65:1: 
note: in expansion of macro 'SYSCALL_DEFINE6'
   SYSCALL_DEFINE6(mmap2, unsigned long, addr, size_t, len,
   ^~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:233:18: 
error: 'sys_mmap' alias between functions of incompatible types 'lo
  ng int(long unsigned int,  size_t,  long unsigned int,  long unsigned int,  
long unsigned int,  off_t)' {aka 'long int(long unsigned int,  l
  ong unsigned int,  long unsigned int,  long unsigned int,  long unsigned int, 
 long int)'} and 'long int(long int,  long int,  long int,  lo
  ng int,  long int,  long int)' [-Werror=attribute-alias]
asmlinkage long sys##name(__MAP(x,__SC_DECL,__VA_ARGS__)) \
^~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:222:2: note: 
in expansion of macro '__SYSCALL_DEFINEx'
__SYSCALL_DEFINEx(x, sname, __VA_ARGS__)
^
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:216:36: 
note: in expansion of macro 'SYSCALL_DEFINEx'
   #define SYSCALL_DEFINE6(name, ...) SYSCALL_DEFINEx(6, _##name, __VA_ARGS__)
  ^~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/arch/powerpc/kernel/syscalls.c:72:1: 
note: in expansion of macro 'SYSCALL_DEFINE6'
   SYSCALL_DEFINE6(mmap, unsigned long, addr, size_t, len,
   ^~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:238:18: 
note: aliased declaration here
asmlinkage long __se_sys##name(__MAP(x,__SC_LONG,__VA_ARGS__)) \
^~~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:222:2: note: 
in expansion of macro '__SYSCALL_DEFINEx'
__SYSCALL_DEFINEx(x, sname, __VA_ARGS__)
^
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:216:36: 
note: in expansion of macro 'SYSCALL_DEFINEx'
   #define SYSCALL_DEFINE6(name, ...) SYSCALL_DEFINEx(6, _##name, __VA_ARGS__)
  ^~~
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/arch/powerpc/kernel/syscalls.c:72:1: 
note: in expansion of macro 'SYSCALL_DEFINE6'
   SYSCALL_DEFINE6(mmap, unsigned long, addr, size_t, len,
   ^~~

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

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

[Kernel-packages] [Bug 1783169] Re: Installation of package linux-image-4.15.0-29-generic 4.15.0-29.31 failed to install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with return code

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  Installation of package linux-image-4.15.0-29-generic 4.15.0-29.31
  failed to install/upgrade: run-parts:
  /etc/kernel/header_postinst.d/dkms exited with return code 4

Status in dkms package in Ubuntu:
  New

Bug description:
  Both 4.15.0-23 and 4.15.0-29 have failed for the same reason, it
  appears.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-29-generic 4.15.0-29.31
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   linux-headers-4.15.0-29:amd64: Install
   linux-modules-4.15.0-29-generic:amd64: Install
   linux-image-4.15.0-29-generic:amd64: Install
   linux-modules-extra-4.15.0-29-generic:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vaughn 1362 F pulseaudio
   /dev/snd/controlC0:  vaughn 1362 F pulseaudio
  Date: Mon Jul 23 11:47:39 2018
  ErrorMessage: run-parts: /etc/kernel/header_postinst.d/dkms exited with 
return code 4
  HibernationDevice: RESUME=UUID=f85c69a0-8f78-4c5c-951a-99bcf5a12b45
  InstallationDate: Installed on 2018-04-29 (85 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=c004bf01-2c8f-4dfd-9bc7-c3b8715bfe1c ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: dkms
  Title: package linux-image-4.15.0-29-generic 4.15.0-29.31 failed to 
install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with 
return code 4
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 2330
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 99.0B
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd08/29/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr096C12405E00050660180:rvnHewlett-Packard:rn2330:rvr99.0B:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 096C12405E00050660180
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1783167] [NEW] linux 4.17.0-5 fails to build on ppc64el with gcc-8

[Thadeu Lima de Souza Cascardo]

Public bug reported:

In file included from 
/tmp/kernel-cascardo-e4c3144-A9Vl/build/arch/powerpc/kernel/syscalls.c:24:
/tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:233:18: error: 
'sys_mmap2' alias between functions of incompatible types 'l
ong int(long unsigned int,  size_t,  long unsigned int,  long unsigned int,  
long unsigned int,  long unsigned int)' {aka 'long int(long uns
igned int,  long unsigned int,  long unsigned int,  long unsigned int,  long 
unsigned int,  long unsigned int)'} and 'long int(long int,  lo
ng int,  long int,  long int,  long int,  long int)' [-Werror=attribute-alias]
  asmlinkage long sys##name(__MAP(x,__SC_DECL,__VA_ARGS__)) \
  ^~~
/tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:222:2: note: 
in expansion of macro '__SYSCALL_DEFINEx'
  __SYSCALL_DEFINEx(x, sname, __VA_ARGS__)
  ^
/tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:216:36: note: 
in expansion of macro 'SYSCALL_DEFINEx'
 #define SYSCALL_DEFINE6(name, ...) SYSCALL_DEFINEx(6, _##name, __VA_ARGS__)
^~~
/tmp/kernel-cascardo-e4c3144-A9Vl/build/arch/powerpc/kernel/syscalls.c:65:1: 
note: in expansion of macro 'SYSCALL_DEFINE6'
 SYSCALL_DEFINE6(mmap2, unsigned long, addr, size_t, len,
 ^~~
/tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:238:18: note: 
aliased declaration here
  asmlinkage long __se_sys##name(__MAP(x,__SC_LONG,__VA_ARGS__)) \
  ^~~~
/tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:222:2: note: 
in expansion of macro '__SYSCALL_DEFINEx'
  __SYSCALL_DEFINEx(x, sname, __VA_ARGS__)
  ^
/tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:216:36: note: 
in expansion of macro 'SYSCALL_DEFINEx'
 #define SYSCALL_DEFINE6(name, ...) SYSCALL_DEFINEx(6, _##name, __VA_ARGS__)
^~~
/tmp/kernel-cascardo-e4c3144-A9Vl/build/arch/powerpc/kernel/syscalls.c:65:1: 
note: in expansion of macro 'SYSCALL_DEFINE6'
 SYSCALL_DEFINE6(mmap2, unsigned long, addr, size_t, len,
 ^~~
/tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:233:18: error: 
'sys_mmap' alias between functions of incompatible types 'lo
ng int(long unsigned int,  size_t,  long unsigned int,  long unsigned int,  
long unsigned int,  off_t)' {aka 'long int(long unsigned int,  l
ong unsigned int,  long unsigned int,  long unsigned int,  long unsigned int,  
long int)'} and 'long int(long int,  long int,  long int,  lo
ng int,  long int,  long int)' [-Werror=attribute-alias]
  asmlinkage long sys##name(__MAP(x,__SC_DECL,__VA_ARGS__)) \
  ^~~
/tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:222:2: note: 
in expansion of macro '__SYSCALL_DEFINEx'
  __SYSCALL_DEFINEx(x, sname, __VA_ARGS__)
  ^
/tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:216:36: note: 
in expansion of macro 'SYSCALL_DEFINEx'
 #define SYSCALL_DEFINE6(name, ...) SYSCALL_DEFINEx(6, _##name, __VA_ARGS__)
^~~
/tmp/kernel-cascardo-e4c3144-A9Vl/build/arch/powerpc/kernel/syscalls.c:72:1: 
note: in expansion of macro 'SYSCALL_DEFINE6'
 SYSCALL_DEFINE6(mmap, unsigned long, addr, size_t, len,
 ^~~
/tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:238:18: note: 
aliased declaration here
  asmlinkage long __se_sys##name(__MAP(x,__SC_LONG,__VA_ARGS__)) \
  ^~~~
/tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:222:2: note: 
in expansion of macro '__SYSCALL_DEFINEx'
  __SYSCALL_DEFINEx(x, sname, __VA_ARGS__)
  ^
/tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:216:36: note: 
in expansion of macro 'SYSCALL_DEFINEx'
 #define SYSCALL_DEFINE6(name, ...) SYSCALL_DEFINEx(6, _##name, __VA_ARGS__)
^~~
/tmp/kernel-cascardo-e4c3144-A9Vl/build/arch/powerpc/kernel/syscalls.c:72:1: 
note: in expansion of macro 'SYSCALL_DEFINE6'
 SYSCALL_DEFINE6(mmap, unsigned long, addr, size_t, len,
 ^~~

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

Title:
  linux 4.17.0-5 fails to build on ppc64el with gcc-8

Status in linux package in Ubuntu:
  New

Bug description:
  In file included from 
/tmp/kernel-cascardo-e4c3144-A9Vl/build/arch/powerpc/kernel/syscalls.c:24:
  /tmp/kernel-cascardo-e4c3144-A9Vl/build/include/linux/syscalls.h:233:18: 
error: 'sys_mmap2' alias between functions of incompatible types 'l
  ong int(long unsigned int,  size_t,  long unsigned int,  long unsigned int,  
long unsigned int,  long unsigned int)' {aka 'long int(long uns
  igned int,  long unsigned int,  long unsigned 

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

[bugproxy]

--- Comment From frederic.bar...@fr.ibm.com 2018-07-23 12:49 EDT---
Tests passed on kernel 4.15.0-29.31

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

Title:
  Update to ocxl driver for 18.04.1

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

Bug description:
  == SRU Justification ==
  IBM is requesting these patches in Bionic.  ocxl (opencapi) is a relatively
  new driver which was added to Ubuntu 18.04; It's specific to POWER9 systems.

  == Regression Potential ==
  Medium.  There are 10 patches, but all are limited to powerpc and the ocxl 
driver.

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


  ---Problem Description---
  Update to ocxl driver

  ---uname output---
  4.15.0-22-generic

  ---Additional Hardware Info---
  opencapi adapter needed

   Machine Type = any POWER9 system

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

  == Comment: #1 - Frederic Barrat  - 2018-06-05 
03:46:00 ==
  ocxl (opencapi) is a relatively new driver which was added to Ubuntu 18.04; 
It's specific to POWER9 systems.

  We'd like to add the following 9 commits for Ubuntu 18.04.1:

  The following 2 patches are already in the main linux tree:
  474cca5fd894de99afc69274e8b25524ae62d7ee
  misc: ocxl: use put_device() instead of device_unregister()

  e7666d046ac0eda535282a5fd3b188f31d0f4afd
  ocxl: Document the OCXL_IOCTL_GET_METADATA IOCTL

  The remaining commits are in the powerpc-next tree and will be merged
  in the next merge window (i.e. in a week or so). See
  https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/log/?h=next

  819844285ef2b5d15466f5b5062514135ffba06c
  powerpc: Add TIDR CPU feature for POWER9

  3449f191ca9be1a6ac9757b8ab55f239092362e5
  powerpc: Use TIDR CPU feature to control TIDR allocation

  71cc64a85d8d99936f6851709a07f18c87a0adab
  powerpc: use task_pid_nr() for TID allocation

  19df39581ce99eb1fcfb119945810c9c5bc3f8d4
  ocxl: Rename pnv_ocxl_spa_remove_pe to clarify it's action

  e948e06fc63a1c1e36ec4c8e5c510b881ff19c26
  ocxl: Expose the thread_id needed for wait on POWER9

  02a8e5bc1c06045f36423bd9632ad9f40da18d3f
  ocxl: Add an IOCTL so userspace knows what OCXL features are available

  721c551d31fb441ff3be701ad3be14cf6e0aca3f
  ocxl: Document new OCXL IOCTLs

  Another commit ID to add to the list (fixes a commit from previous list), 
from the 'next' tree:
  2e5c93d6bb2f7bc17eb82748943a1b9f6b068520
  ocxl: Fix missing unlock on error in afu_ioctl_enable_p9_wait()

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

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

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

[Skipper]

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

Totally black screen immediately - no bios flashes.

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1779376] Re: linux: 4.4.0-131.157 -proposed tracker

[Brad Figg]

The package has been published and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/snap-release-to-stable
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-release-to-stable
   Status: Confirmed => Fix Released

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1779377 (linux-aws), bug 1779378 (linux-lts-xenial)
  derivatives: bug 1779379 (linux-aws), bug 1779380 (linux-euclid), bug 1779381 
(linux-kvm), bug 1779382 (linux-raspi2), bug 1779383 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to updates
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Monday, 23. July 2018 16:28 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1779377 (linux-aws), bug 1779378 (linux-lts-xenial)
  derivatives: bug 1779379 (linux-aws), bug 1779380 (linux-euclid), bug 1779381 
(linux-kvm), bug 1779382 (linux-raspi2), bug 1779383 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
- phase: Promoted to updates
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Monday, 23. July 2018 16:28 UTC

** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux: 4.4.0-131.157 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
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:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

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

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

  backports: bug 1779377 (linux-aws), bug 1779378 (linux-lts-xenial)
  derivatives: bug 1779379 (linux-aws), bug 1779380 (linux-euclid), bug 1779381 
(linux-kvm), bug 1779382 (linux-raspi2), bug 1779383 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1779376/+subscriptions

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

[Kernel-packages] [Bug 1714485] Re: Ubuntu 16.04: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs.

[Andrew Cloke]

** Changed in: ubuntu-power-systems
   Status: Fix Committed => Fix Released

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

Title:
  Ubuntu 16.04: kdump fails with error "kdump-tools[1532]: /etc/init.d
  /kdump-tools: 26: [: -ne: unexpected operator" when / file system is
  xfs.

Status in The Ubuntu-power-systems project:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Released
Status in makedumpfile source package in Zesty:
  Won't Fix
Status in makedumpfile source package in Artful:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-08-31 00:33:37 ==
  ---Problem Description---

  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

  ---Steps to Reproduce---

  1. Install Ubuntu 16.04.03 with / as xfs.
  2. Configure kdump.
  3. trigger crash.

  Machine hangs after below log. Attaching console log.

  [  OK  ] Reached target Network is Online.
   Starting Kernel crash dump capture service...
   Starting iSCSI initiator daemon (iscsid)...
  [   12.263089] kdump-tools[1205]: /etc/init.d/kdump-tools: 26: [: -ne: 
unexpected operator
  [  OK  ] Started Kernel crash dump capture service.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).

  
  4. After manual reboot  /etc/default/kdump-tools is empty.

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

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

[Kernel-packages] [Bug 1746088] Re: [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel

[Andrew Cloke]

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

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

Title:
  [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on
  4.13.0-26-generic kernel

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  Fix Committed
Status in crash source package in Artful:
  Won't Fix
Status in crash source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  It won't be possible to analyze dumps produced by newer kernels (hwe on 
xenial, for example).

  [Test Case]
  Tested that this version of crash can analyze both GA (4.4) and hwe (4.15) 
kernels.

  [Regression Potential]
  New crash versions may have bugs and some commands not work with older 
kernels. The smoke test helps a little, but more testing may be desirable.


  ---Problem Description---
  Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel 
(Ubuntu 16.04.4)

  ---uname output---
  Linux ltc-briggs1 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 21:40:36 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8001-22C

  ---Steps to Reproduce---
   This bug follow up bug of 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=163565
  The steps to create dump is as follows

  Once you generate the kdump
  use crash to analyze the vmcore and we get this error

  console logs ==

  root@ltc-briggs1:/var/crash/201801150227# ls
  dmesg.201801150227  vmcore.201801150227
  .0-26-generic vmcore.2018011502271150227# crash 
/usr/lib/debug/boot/vmlinux-4.13.

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)
  WARNING: cannot access vmalloc'd module memory

  crash: invalid structure member offset: thread_info_task
     FILE: task.c  LINE: 598  FUNCTION: irqstacks_init()

  [/usr/bin/crash] error trace: 1008ade0 => 1011552c => 1017d220 =>
  100833e0

    100833e0: (undetermined)
    1017d220: OFFSET_verify+80
    1011552c: task_init+5084
    1008ade0: main_loop+336

  == Comment from Hari Krishna Bathini ==

  There are quite a few commits (all available upstream) that are needed for
  crash tool to work fine. I think the right thing to do here would be to use
  the latest crash tool version 7.2.0 to go with the kernel update. Also, the
  below commit would be needed on top of 7.2.0 crash utility:

    commit c8178eca9c74f81a7f803a58d339635cc152e8d9
    Author: Dave Anderson 
    Date:   Thu Nov 9 11:39:05 2017 -0500

  Update for support of Linux 4.14 and later PPC64 kernels where the
  hash page table geometry accomodates a larger virtual address range.
  Without the patch, the virtual-to-physical translation of user space
  virtual addresses by "vm -p", "vtop", and "rd -u" may generate an
  invalid translation or otherwise fail.
  (hbath...@linux.vnet.ibm.com)

  Similar thing holds true for makedumpfile tool..

  Thanks
  Hari

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

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

[Kernel-packages] [Bug 1779376] Re: linux: 4.4.0-131.157 -proposed tracker

[Canonical Certification Team]

Snap beta testing complete, no regressions found. Ready for promotion.
Results here: https://trello.com/c/9itxFX23/299-pc-kernel-440-131157-126

** Changed in: kernel-sru-workflow/snap-certification-testing
   Status: Confirmed => 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/1779376

Title:
  linux: 4.4.0-131.157 -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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
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:
  New
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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

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

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

  backports: bug 1779377 (linux-aws), bug 1779378 (linux-lts-xenial)
  derivatives: bug 1779379 (linux-aws), bug 1779380 (linux-euclid), bug 1779381 
(linux-kvm), bug 1779382 (linux-raspi2), bug 1779383 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to updates
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1779376/+subscriptions

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

[Kernel-packages] [Bug 1714485] Re: Ubuntu 16.04: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs.

[Thadeu Lima de Souza Cascardo]

** Changed in: makedumpfile (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Ubuntu 16.04: kdump fails with error "kdump-tools[1532]: /etc/init.d
  /kdump-tools: 26: [: -ne: unexpected operator" when / file system is
  xfs.

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Released
Status in makedumpfile source package in Zesty:
  Won't Fix
Status in makedumpfile source package in Artful:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-08-31 00:33:37 ==
  ---Problem Description---

  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

  ---Steps to Reproduce---

  1. Install Ubuntu 16.04.03 with / as xfs.
  2. Configure kdump.
  3. trigger crash.

  Machine hangs after below log. Attaching console log.

  [  OK  ] Reached target Network is Online.
   Starting Kernel crash dump capture service...
   Starting iSCSI initiator daemon (iscsid)...
  [   12.263089] kdump-tools[1205]: /etc/init.d/kdump-tools: 26: [: -ne: 
unexpected operator
  [  OK  ] Started Kernel crash dump capture service.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).

  
  4. After manual reboot  /etc/default/kdump-tools is empty.

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

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

[Kernel-packages] [Bug 1723799] Re: touchpad not working after resume on kernel 4.13

[swissz]

Hi

I wrote this text to #1722379, but I think it worth to mention it here
as well.

Recently, after some updates - unfortunatelly I don't know exactly which 
updates, but in the last month - I also have the same problem.
The workaround above with the # rmmod i2c_hid && modprobe i2c_hid works, but I 
also have a different workaround: if I switch to a virtual terminal with 
CTRL+ALT+1 then back to the GUI Terminal CTRL+ALT+7 the clickpad works again.
I hope this new aspect of switching virtual terminals back and forth helps to 
understand/debug the issue better.

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

Title:
  touchpad not working after resume on kernel 4.13

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

Bug description:
  I'm running Ubuntu 17.10 [Ubuntu Artful Aardvark (development branch)
  installed from beta 2 ISO with latest apt update && apt dist-upgrade]
  with kernel:

  $ uname -rv
  4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017

  and after putting system to sleep via closing laptop lid and then
  resuming it by opening laptop lid makes touchpad not working. Kernel
  message buffer contains following error message after resume:

  PM: Device i2c-SYNA3105:00 failed to resume async: error -11

  and I can find other people reporting similar issue on other distros:

  https://bugzilla.redhat.com/show_bug.cgi?id=1431375
  https://bugzilla.kernel.org/show_bug.cgi?id=195949
  https://bugzilla.redhat.com/show_bug.cgi?id=1442699

  
  like in those other bug reports I can workaround the problem by:

  rmmod i2c-hid
  modprobe i2c-hid

  in systemd-suspend.service(8) post scripts.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-extra-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mkucharski   1367 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 15 22:49:38 2017
  HibernationDevice: RESUME=UUID=aa9acb18-b692-4020-9811-d58e5c8b8857
  InstallationDate: Installed on 2017-10-06 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05c8:03a1 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Timi TM1607
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2017
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: XMAKB200P0100
  dmi.board.asset.tag: Any
  dmi.board.name: TM1607
  dmi.board.vendor: Timi
  dmi.board.version: MP
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrXMAKB200P0100:bd05/07/2017:svnTimi:pnTM1607:pvr:rvnTimi:rnTM1607:rvrMP:cvnTimi:ct10:cvrChassisVersion:
  dmi.product.family: Timibook
  dmi.product.name: TM1607
  dmi.sys.vendor: Timi

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

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

[Kernel-packages] [Bug 1776563]

[bakarichard91]

Sorry, nothing, I changed it before :)

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  New
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

[Kernel-packages] [Bug 1776563]

[bakarichard91]

They->those

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  New
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

[Kernel-packages] [Bug 1779379] Re: linux-aws: 4.4.0-1063.72 -proposed tracker

[Brad Figg]

The package has been published and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: Confirmed => Fix Released

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1779376
  phase: Promoted to updates
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Monday, 23. July 2018 14:31 UTC
+ kernel-stable-phase:Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1779376
- phase: Promoted to updates
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Monday, 23. July 2018 14:31 UTC
- kernel-stable-phase:Released

** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-aws: 4.4.0-1063.72 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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 promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1779376
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1779379/+subscriptions

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

[Kernel-packages] [Bug 1776563]

[bakarichard91]

Zhang Rui,

why have you changed the topic? It was correct, the kernel loads only
with noapic or noacpi. The problem is DSDT/SSDT tables can not load
because of ALREADY_EXIST problem. They should be fixed by someone
correctly.

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  New
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

[Kernel-packages] [Bug 1751994] Re: ppc64el: Support firmware disable of RFI flush

[Andrew Cloke]

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

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

Title:
  ppc64el: Support firmware disable of RFI flush

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Artful:
  Invalid
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - Breno Leitao  - 2018-02-26 13:59:55 ==
  Hi Canonical,

  We still need some changes regarding spectre and meltdown. We need to
  backport the following commit to all supported kernel.

  I undertand that the backport for kernel 4.XX should be trivial. Not
  sure about kernel 3.13 yet.

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=582605a429e20ae68fd0b041b2e840af296edd08
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb0a2d2620ae431c543963c8c7f08f597366fc60

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

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

[Kernel-packages] [Bug 1714485] Re: Ubuntu 16.04: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs.

[Andrew Cloke]

** Changed in: makedumpfile (Ubuntu Artful)
   Status: Fix Committed => Invalid

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

Title:
  Ubuntu 16.04: kdump fails with error "kdump-tools[1532]: /etc/init.d
  /kdump-tools: 26: [: -ne: unexpected operator" when / file system is
  xfs.

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in makedumpfile source package in Zesty:
  Won't Fix
Status in makedumpfile source package in Artful:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-08-31 00:33:37 ==
  ---Problem Description---

  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

  ---Steps to Reproduce---

  1. Install Ubuntu 16.04.03 with / as xfs.
  2. Configure kdump.
  3. trigger crash.

  Machine hangs after below log. Attaching console log.

  [  OK  ] Reached target Network is Online.
   Starting Kernel crash dump capture service...
   Starting iSCSI initiator daemon (iscsid)...
  [   12.263089] kdump-tools[1205]: /etc/init.d/kdump-tools: 26: [: -ne: 
unexpected operator
  [  OK  ] Started Kernel crash dump capture service.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).

  
  4. After manual reboot  /etc/default/kdump-tools is empty.

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

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

[Andrew Cloke]

** Changed in: ubuntu-power-systems
   Status: In Progress => 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/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:
  Incomplete
Status in linux package in Ubuntu:
  In Progress

Bug description:
  == 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)

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 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device

[Manoj Iyer]

abdhalee, Looks like you have successfully verified, could you please
change the tag to verification-done-bionic ?

** No longer affects: linux (Ubuntu)

** No longer affects: linux (Ubuntu Xenial)

** No longer affects: linux (Ubuntu 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/1779815

Title:
  [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI
  based SAS/md raid device

Status in The Ubuntu-power-systems project:
  In Progress
Status in debian-installer package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in debian-installer source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in debian-installer source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  == Comment: #0 - ABDUL HALEEM  - 2018-07-02 03:55:33 ==
  ---Problem Description---
  Ubuntu 18.04.01 ppc64el installer does not detect LSI3008  base SAS disks / 
MD RAID devices 

  Used 20101020ubuntu543 version to install
  
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

  Contact Information = abdha...@in.ibm.com 
   
  ---uname output---
  Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = BostonLC
   
  ---boot type---
  Network boot
   

  Installer fails to detect the LSI SAS disks / RAID MD device

  ===console error log===

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? /dev/nvme0n1 - 491.5 GB NVMe Device ?
? /dev/nvme1n1 - 98.3 GB NVMe Device  ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  To make sure it detects the disks I had to 
  
  
  Detect disks-->Guided partitioning--> Guided - use entire disk 

  
?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?  /dev/nvme0n1 - 491.5 GB NVMe Device?
?  /dev/nvme1n1 - 98.3 GB NVMe Device ?
?  SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075  ?
?  SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume  ?
?  SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ  ?
? ?
??
? ?
???

  IPR had similar issue reported  #164932 and fixed with 4.15.0-20,
  looks installer need a fix for LSI (mpt3sas) devices too

  == Comment: #2 - SEETEENA THOUFEEK  - 2018-07-03 
02:01:47 ==
  164932 - refers LP1751813

  == Comment: #3 - SEETEENA THOUFEEK  - 2018-07-03 
02:02:51 ==
  Jul  2 08:49:52 anna-install: Installing mdadm-udeb
  Jul  2 08:49:52 disk-detect: No Intel/DDF RAID disks detected.
  Jul  2 08:49:52 anna-install: Installing dmraid-udeb
  Jul  2 08:49:52 disk-detect: No Serial ATA RAID disks detected
  Jul  2 08:49:53 check-missing-firmware: looking at dmesg again, restarting 
from \[  330.659712\]
  Jul  2 08:49:53 check-missing-firmware: timestamp found, truncating dmesg 
accordingly
  Jul  2 08:49:53 check-missing-firmware: saving timestamp for a later use: 
  Jul  2 08:49:53 check-missing-firmware: /dev/.udev/firmware-missing does not 

[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension

[Richard Collier]

I am new to Linux, I had the same problem on Linux Mint 19 Tara Kernel
4.15.0-29 with the driver r8169, wired network unplugged after resume
from suspend. I tried various solutions posted here but none worked. I
then reverted to Kernel 4.13.0-45 and the network is now connected after
resume.

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

Title:
  r8169 ethernet card don't work after returning from suspension

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

Bug description:
  ===SRU Justification===
  [Impact]
  Ethernet r8169 stops working after system resumed from suspend.

  [Test]
  User confirmed these patches fix the issue. r8169 continues to work
  after resume from suspend.

  [Regression Potential]
  Medium. The fix is limited to one device, all patches are in mainline.
  The WOL default change might cause regression for users that depend on
  BIOS settings. We can advice them to use userspace tool (systemd,
  ethtool, etc.) instead.

  ===Original Bug Report===
  I have noticed that the network stopped working on my desktop after I've 
suspended the system and woke it up. On dmesg there are messages like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity:
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:

  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
     Mixer name : 'VIA VT1818S'
     Components : 'HDA:11060440,18492818,0010'
     Controls  : 40
     Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
     Mixer name : 'ATI R6xx HDMI'
     Components : 'HDA:1002aa01,00aa0100,00100200'
     Controls  : 7
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined
     Playback channels: Mono
     Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:

  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 

[Kernel-packages] [Bug 1783054] Re: USB 3.0 flash drive not mounted

[Kai-Heng Feng]

This commit should fix your issue:

commit 621faf4f6a181b6e012c1d1865213f36f4159b7f
Author: Kai-Heng Feng 
Date:   Fri Apr 20 16:52:50 2018 +0300

xhci: Fix USB ports for Dell Inspiron 5775

The commit will be included in next Bionic's kernel.

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

Title:
  USB 3.0 flash drive not mounted

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I insert USB flash drive to the USB port nothing happens. The
  drive is not listed by `lsblk`.

  dmesg reports:
  ```
  [ 1262.090351] xhci_hcd :04:00.3: Error while assigning device slot ID
  [ 1262.090371] xhci_hcd :04:00.3: Max number of devices this xHCI host 
supports is 64.
  [ 1262.090378] usb usb3-port2: couldn't allocate usb_device
  [ 1280.075712] xhci_hcd :04:00.3: Command completion event does not match 
command
  ```
  Ubuntu 18.04 LTS
  kernel: 4.15.0-29-generic

  Interestingly when I reboot while keeping drive in the port it is
  mounted after reboot and fully operational.

  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
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ivan   2248 F pulseaudio
   /dev/snd/controlC0:  ivan   2248 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 22 21:53:14 2018
  HibernationDevice: RESUME=UUID=95b899e9-9c09-4cd1-8a21-f67625c9f973
  InstallationDate: Installed on 2018-07-19 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: HP HP EliteBook 745 G5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=9504892d-5b9a-4ea5-a9dc-be39611a0bf7 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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/03/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q81 Ver. 01.00.04
  dmi.board.name: 83D5
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 08.43.00
  dmi.chassis.asset.tag: 5CG8256TVY
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ81Ver.01.00.04:bd06/03/2018:svnHP:pnHPEliteBook745G5:pvr:rvnHP:rn83D5:rvrKBCVersion08.43.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 745 G5
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1778642] Re: ubuntu_lttng_smoke_test failed on Azure 4.15

[Łukasz Zemczak]

Hello Po-Hsu, or anyone else affected,

Accepted lttng-modules into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/lttng-
modules/2.8.0-1ubuntu1~16.04.7 in a few hours, and then in the -proposed
repository.

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

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

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

** Changed in: lttng-modules (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-xenial

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

Title:
  ubuntu_lttng_smoke_test failed on Azure 4.15

Status in lttng-modules:
  New
Status in ubuntu-kernel-tests:
  Invalid
Status in linux-azure package in Ubuntu:
  Invalid
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in linux-azure source package in Xenial:
  Invalid
Status in lttng-modules source package in Xenial:
  Fix Committed
Status in linux-azure source package in Bionic:
  Invalid
Status in lttng-modules source package in Bionic:
  In Progress
Status in linux-azure source package in Cosmic:
  Invalid
Status in lttng-modules source package in Cosmic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]

  After bionic/linux-azure commit
  4fbb658dd8ce96384852ceae18b0b09034de7b36 (UBUNTU: [Config] azure:
  CONFIG_HOTPLUG_CPU=n) the lttng_tracer module cannot find some symbols
  and cannot be loaded.

   kernel: [  639.538251] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
   kernel: [  639.538280] lttng_tracer: Unknown symbol lttng_hp_online (err 0)

  This is caused by lttng-modules incorrectly handling the case when
  CONFIG_HOTPLUG_CPU is not enabled.

  [Test Case]

  Install linux-azure >= 4.15.0-1014, install lttng-modules-dkms and run
  the autotest ubuntu_lttng_smoke_test testcase (or just 'sudo lttng
  list --kernel').

  [Fix]

  commit 894ce5dc825733d1ccab25b1aede9ce0be2a7c4e (Fix: do not use
  CONFIG_HOTPLUG_CPU for the new hotplug API)

  commit 1ee63d8d1b0aaf30564d3879d8e9282d0ddfef1b (Cleanup: comment
  about CONFIG_HOTPLUG_CPU ifdef)

  [Regression Potential]

  Very low. The two patches can be cleanly cherry-picked from the
  upstream commits. The first one that really fixed the issue just
  changes a single #ifdef to compile a piece of code when
  CONFIG_HOTPLUG_CPU is not defined. The second one just updates some
  comments on the code to make them consistent with the changes.

  [Original Description]

  This test will pass with the older kernel, 4.15.0-1013-azure, but not
  the 4.15.0-1014-azure in -proposed.

  It looks like the kernel module can be installed, but four tests have
  failed:

  == lttng smoke test of session create/destroy ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-14716-session
  PASSED (lttng create)
  Session test-kernel-session destroyed
  PASSED (lttng destroy)

  == lttng smoke test list kernel events ==
  FAILED (lttng list --kernel)
  FAILED (lttng list --kernel more output expected)

  == lttng smoke test trace open/close system calls ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-14716-session
  PASSED (lttng create)
  FAILED (lttng enable-event)
  Session test-kernel-session destroyed

  == lttng smoke test trace context switches ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-14716-session
  PASSED (lttng create)
  FAILED (lttng enable-event)
  Session test-kernel-session destroyed

  Summary: 4 passed, 4 failed

  http://10.246.72.46/4.15.0-1014.14-azure/bionic-linux-azure-
  
azure-4.15.0-Standard_D12-ubuntu_lttng_smoke_test/ubuntu_lttng_smoke_test/results/ubuntu_lttng_smoke_test
  .lttng-smoke-test/debug/ubuntu_lttng_smoke_test.lttng-smoke-
  test.DEBUG.html

  Error message from /var/log/syslog:

   kernel: [  639.531889] PKCS#7 signature not signed with a trusted key
   kernel: [  639.538251] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
   kernel: [  639.538280] lttng_tracer: Unknown symbol lttng_hp_online (err 0)
   lttng-sessiond[1097]: Error: Unable to load required module 
lttng-ring-buffer-client-discard
   

[Kernel-packages] [Bug 1779377] Re: linux-aws: 4.4.0-1025.26 -proposed tracker

[Brad Figg]

The package has been published and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Fix Committed => Fix Released

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1779376
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Monday, 23. July 2018 14:01 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1779376
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Monday, 23. July 2018 14:01 UTC

** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-aws: 4.4.0-1025.26 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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 promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1779376
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1779377/+subscriptions

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

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

[bugproxy]

--- Comment From kla...@br.ibm.com 2018-07-23 09:57 EDT---
(In reply to comment #16)
>
>
>
> It's already in the SRU process, got already two acks and will be released
> with the end of the netxt SRU cycle.

Was this fix released? Can this be closed?

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

Title:
  Need fix to aacraid driver to prevent panic

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

Bug description:
  
  == SRU Justification ==
  A commit introduced in mainline v4.14-rc1 to aacraid
  (b60710ec7d7ab1ca277b458338563ac21b393906) introduced a regression whereby a
  panic may happen under certain recovery situations.

  This regression is fixed by linux-next commit  7d3af7d96af7.

  
  == Fix ==
  7d3af7d96af7 ("scsi: aacraid: Correct hba_send to include iu_type")

  == Regression Potential ==
  Low.  This patch fixes a current regression.  It was cc'd to upstream
  stable, so it has had additonal upstream review.

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


  
  == Comment: #0 - Douglas Miller  - 2018-05-08 15:45:13 ==
  +++ This bug was initially created as a clone of Bug #167565 +++

  A recent commit to aacraid (b60710ec7d7ab1ca277b458338563ac21b393906)
  introduced a bug whereby a panic may happen under certain recovery
  situations. The following commit fixes that:

  
https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git/commit/?h=fixes=7d3af7d96af7b9f51e1ef67b6f4725f545737da2

  We need this commit backported to Ubuntu 18.04

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

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

[Kernel-packages] [Bug 1778844] Re: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash, kdump is not working and system enters into initramfs state

[Frank Heimes]

** Tags removed: triage-a
** Tags added: triage-g

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

Title:
  ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
  crash,kdump is not working and system enters into initramfs state

Status in The Ubuntu-power-systems project:
  Triaged
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  New
Status in initramfs-tools source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in makedumpfile source package in Bionic:
  New

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
  [   73.058099] GPR08: 0007 0001  
90001003
  [   73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 

  [   73.058099] GPR16: 0e4f79cc94b0 0e4f79d567e0 0e4f79d88204 
0e4f79d56818
  [   73.058099] GPR20: 0e4f79d8d5d8 0001  
7efce644
  [   73.058099] GPR24: 7efce640 0e4f79d8afb4 c15e9aa8 
0002
  [   73.058099] GPR28: 

[Kernel-packages] [Bug 1778844] Re: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash, kdump is not working and system enters into initramfs state

[Manoj Iyer]

** Changed in: makedumpfile (Ubuntu)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: initramfs-tools (Ubuntu)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Critical

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

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

Title:
  ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
  crash,kdump is not working and system enters into initramfs state

Status in The Ubuntu-power-systems project:
  Triaged
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  New
Status in initramfs-tools source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in makedumpfile source package in Bionic:
  New

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
  [   73.058099] GPR08: 0007 0001  
90001003
  [   73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 

[Kernel-packages] [Bug 1779353] Re: linux-oem: 4.13.0-1032.36 -proposed tracker

[Brad Figg]

The package has been published and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow/promote-to-security
   Status: Fix Committed => Fix Released

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

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

Title:
  linux-oem: 4.13.0-1032.36 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1779353/+subscriptions

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

[Kernel-packages] [Bug 1779353] Package Released!

[Brad Figg]

The package has been published and the bug is being set to Fix Released


** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to updates
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Monday, 23. July 2018 14:02 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
- phase: Promoted to updates
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Monday, 23. July 2018 14:02 UTC

** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-oem: 4.13.0-1032.36 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1779353/+subscriptions

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

[Kernel-packages] [Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device

[Frank Heimes]

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

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

Title:
  [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI
  based SAS/md raid device

Status in The Ubuntu-power-systems project:
  In Progress
Status in debian-installer package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in debian-installer source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in debian-installer source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  == Comment: #0 - ABDUL HALEEM  - 2018-07-02 03:55:33 ==
  ---Problem Description---
  Ubuntu 18.04.01 ppc64el installer does not detect LSI3008  base SAS disks / 
MD RAID devices 

  Used 20101020ubuntu543 version to install
  
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

  Contact Information = abdha...@in.ibm.com 
   
  ---uname output---
  Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = BostonLC
   
  ---boot type---
  Network boot
   

  Installer fails to detect the LSI SAS disks / RAID MD device

  ===console error log===

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? /dev/nvme0n1 - 491.5 GB NVMe Device ?
? /dev/nvme1n1 - 98.3 GB NVMe Device  ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  To make sure it detects the disks I had to 
  
  
  Detect disks-->Guided partitioning--> Guided - use entire disk 

  
?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?  /dev/nvme0n1 - 491.5 GB NVMe Device?
?  /dev/nvme1n1 - 98.3 GB NVMe Device ?
?  SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075  ?
?  SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume  ?
?  SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ  ?
? ?
??
? ?
???

  IPR had similar issue reported  #164932 and fixed with 4.15.0-20,
  looks installer need a fix for LSI (mpt3sas) devices too

  == Comment: #2 - SEETEENA THOUFEEK  - 2018-07-03 
02:01:47 ==
  164932 - refers LP1751813

  == Comment: #3 - SEETEENA THOUFEEK  - 2018-07-03 
02:02:51 ==
  Jul  2 08:49:52 anna-install: Installing mdadm-udeb
  Jul  2 08:49:52 disk-detect: No Intel/DDF RAID disks detected.
  Jul  2 08:49:52 anna-install: Installing dmraid-udeb
  Jul  2 08:49:52 disk-detect: No Serial ATA RAID disks detected
  Jul  2 08:49:53 check-missing-firmware: looking at dmesg again, restarting 
from \[  330.659712\]
  Jul  2 08:49:53 check-missing-firmware: timestamp found, truncating dmesg 
accordingly
  Jul  2 08:49:53 check-missing-firmware: saving timestamp for a later use: 
  Jul  2 08:49:53 check-missing-firmware: /dev/.udev/firmware-missing does not 
exist, skipping
  Jul  2 08:49:53 check-missing-firmware: /run/udev/firmware-missing does not 
exist, skipping
  Jul  2 08:49:53 check-missing-firmware: no missing firmware 

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  package linux-image-4.15.0-29-generic 4.15.0-29.31 failed to
  install/upgrade: installed linux-image-4.15.0-29-generic package post-
  installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dkms hangs forever.
  I have a evdi module installed which is causing the problem.
  This happened with multiple upgrades of the kernel.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-29-generic 4.15.0-29.31
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   omer  10948 F...m pulseaudio
   /dev/snd/controlC0:  gdm5804 F pulseaudio
omer  10948 F pulseaudio
  Date: Mon Jul 23 15:42:40 2018
  DpkgTerminalLog:
   Setting up linux-image-4.15.0-29-generic (4.15.0-29.31) ...
   depmod: FATAL: renameat(/lib/modules/4.15.0-29-generic, modules.dep.tmp, 
/lib/modules/4.15.0-29-generic, modules.dep): No such file or directory
   dpkg: error processing package linux-image-4.15.0-29-generic 
(--configure):
installed linux-image-4.15.0-29-generic package post-installation script 
subprocess returned error exit status 1
  ErrorMessage: installed linux-image-4.15.0-29-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2017-07-05 (382 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04f2:b57e Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80WK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=86c90392-13c2-4da2-bd0d-525cf9ae2f00 ro cgroup_enable=memory 
swapaccount=1 quiet splash nouveau.modeset=0 vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-image-4.15.0-29-generic 4.15.0-29.31 failed to 
install/upgrade: installed linux-image-4.15.0-29-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-05-07 (76 days ago)
  dmi.bios.date: 10/17/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4KCN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Provence-5R1
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y520-15IKBN
  dmi.modalias: 
dmi:bvnLENOVO:bvr4KCN40WW:bd10/17/2017:svnLENOVO:pn80WK:pvrLenovoY520-15IKBN:rvnLENOVO:rnProvence-5R1:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoY520-15IKBN:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80WK
  dmi.product.version: Lenovo Y520-15IKBN
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1746088] Re: [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel

[Andrew Cloke]

** Tags removed: triage-g verification-needed verification-needed-xenial
** Tags added: triage-a

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

Title:
  [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on
  4.13.0-26-generic kernel

Status in The Ubuntu-power-systems project:
  In Progress
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  Fix Committed
Status in crash source package in Artful:
  Won't Fix
Status in crash source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  It won't be possible to analyze dumps produced by newer kernels (hwe on 
xenial, for example).

  [Test Case]
  Tested that this version of crash can analyze both GA (4.4) and hwe (4.15) 
kernels.

  [Regression Potential]
  New crash versions may have bugs and some commands not work with older 
kernels. The smoke test helps a little, but more testing may be desirable.


  ---Problem Description---
  Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel 
(Ubuntu 16.04.4)

  ---uname output---
  Linux ltc-briggs1 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 21:40:36 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8001-22C

  ---Steps to Reproduce---
   This bug follow up bug of 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=163565
  The steps to create dump is as follows

  Once you generate the kdump
  use crash to analyze the vmcore and we get this error

  console logs ==

  root@ltc-briggs1:/var/crash/201801150227# ls
  dmesg.201801150227  vmcore.201801150227
  .0-26-generic vmcore.2018011502271150227# crash 
/usr/lib/debug/boot/vmlinux-4.13.

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)
  WARNING: cannot access vmalloc'd module memory

  crash: invalid structure member offset: thread_info_task
     FILE: task.c  LINE: 598  FUNCTION: irqstacks_init()

  [/usr/bin/crash] error trace: 1008ade0 => 1011552c => 1017d220 =>
  100833e0

    100833e0: (undetermined)
    1017d220: OFFSET_verify+80
    1011552c: task_init+5084
    1008ade0: main_loop+336

  == Comment from Hari Krishna Bathini ==

  There are quite a few commits (all available upstream) that are needed for
  crash tool to work fine. I think the right thing to do here would be to use
  the latest crash tool version 7.2.0 to go with the kernel update. Also, the
  below commit would be needed on top of 7.2.0 crash utility:

    commit c8178eca9c74f81a7f803a58d339635cc152e8d9
    Author: Dave Anderson 
    Date:   Thu Nov 9 11:39:05 2017 -0500

  Update for support of Linux 4.14 and later PPC64 kernels where the
  hash page table geometry accomodates a larger virtual address range.
  Without the patch, the virtual-to-physical translation of user space
  virtual addresses by "vm -p", "vtop", and "rd -u" may generate an
  invalid translation or otherwise fail.
  (hbath...@linux.vnet.ibm.com)

  Similar thing holds true for makedumpfile tool..

  Thanks
  Hari

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

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

[Kernel-packages] [Bug 1746088] Re: [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel

[Łukasz Zemczak]

Hello bugproxy, or anyone else affected,

Accepted crash into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/crash/7.2.3+real-1~16.04.1 in a few
hours, and then in the -proposed repository.

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

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

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

** Changed in: crash (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-xenial

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

Title:
  [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on
  4.13.0-26-generic kernel

Status in The Ubuntu-power-systems project:
  In Progress
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  Fix Committed
Status in crash source package in Artful:
  Won't Fix
Status in crash source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  It won't be possible to analyze dumps produced by newer kernels (hwe on 
xenial, for example).

  [Test Case]
  Tested that this version of crash can analyze both GA (4.4) and hwe (4.15) 
kernels.

  [Regression Potential]
  New crash versions may have bugs and some commands not work with older 
kernels. The smoke test helps a little, but more testing may be desirable.


  ---Problem Description---
  Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel 
(Ubuntu 16.04.4)

  ---uname output---
  Linux ltc-briggs1 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 21:40:36 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8001-22C

  ---Steps to Reproduce---
   This bug follow up bug of 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=163565
  The steps to create dump is as follows

  Once you generate the kdump
  use crash to analyze the vmcore and we get this error

  console logs ==

  root@ltc-briggs1:/var/crash/201801150227# ls
  dmesg.201801150227  vmcore.201801150227
  .0-26-generic vmcore.2018011502271150227# crash 
/usr/lib/debug/boot/vmlinux-4.13.

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)
  WARNING: cannot access vmalloc'd module memory

  crash: invalid structure member offset: thread_info_task
     FILE: task.c  LINE: 598  FUNCTION: irqstacks_init()

  [/usr/bin/crash] error trace: 1008ade0 => 1011552c => 1017d220 =>
  100833e0

    100833e0: (undetermined)
    1017d220: OFFSET_verify+80
    1011552c: task_init+5084
    1008ade0: main_loop+336

  == Comment from Hari Krishna Bathini ==

  There are quite a few commits (all available upstream) that are needed for
  crash tool to work fine. I think the right thing to do here would be to use
  the latest crash tool version 7.2.0 to go with the kernel update. Also, the
  below commit would be needed on top of 7.2.0 crash utility:

    commit c8178eca9c74f81a7f803a58d339635cc152e8d9
    Author: Dave Anderson 
    Date:   Thu Nov 9 11:39:05 2017 -0500

  Update for support of Linux 4.14 and later PPC64 kernels where the
  hash page table geometry accomodates a 

[Kernel-packages] [Bug 1783134] [NEW] package linux-image-4.15.0-29-generic 4.15.0-29.31 failed to install/upgrade: installed linux-image-4.15.0-29-generic package post-installation script subprocess

[Omer Katz]

Public bug reported:

dkms hangs forever.
I have a evdi module installed which is causing the problem.
This happened with multiple upgrades of the kernel.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-29-generic 4.15.0-29.31
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
AptOrdering: NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   omer  10948 F...m pulseaudio
 /dev/snd/controlC0:  gdm5804 F pulseaudio
  omer  10948 F pulseaudio
Date: Mon Jul 23 15:42:40 2018
DpkgTerminalLog:
 Setting up linux-image-4.15.0-29-generic (4.15.0-29.31) ...
 depmod: FATAL: renameat(/lib/modules/4.15.0-29-generic, modules.dep.tmp, 
/lib/modules/4.15.0-29-generic, modules.dep): No such file or directory
 dpkg: error processing package linux-image-4.15.0-29-generic 
(--configure):
  installed linux-image-4.15.0-29-generic package post-installation script 
subprocess returned error exit status 1
ErrorMessage: installed linux-image-4.15.0-29-generic package post-installation 
script subprocess returned error exit status 1
InstallationDate: Installed on 2017-07-05 (382 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 04f2:b57e Chicony Electronics Co., Ltd 
 Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80WK
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=86c90392-13c2-4da2-bd0d-525cf9ae2f00 ro cgroup_enable=memory 
swapaccount=1 quiet splash nouveau.modeset=0 vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-image-4.15.0-29-generic 4.15.0-29.31 failed to 
install/upgrade: installed linux-image-4.15.0-29-generic package 
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to bionic on 2018-05-07 (76 days ago)
dmi.bios.date: 10/17/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: 4KCN40WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Provence-5R1
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Y520-15IKBN
dmi.modalias: 
dmi:bvnLENOVO:bvr4KCN40WW:bd10/17/2017:svnLENOVO:pn80WK:pvrLenovoY520-15IKBN:rvnLENOVO:rnProvence-5R1:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoY520-15IKBN:
dmi.product.family: IDEAPAD
dmi.product.name: 80WK
dmi.product.version: Lenovo Y520-15IKBN
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-package 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/1783134

Title:
  package linux-image-4.15.0-29-generic 4.15.0-29.31 failed to
  install/upgrade: installed linux-image-4.15.0-29-generic package post-
  installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  dkms hangs forever.
  I have a evdi module installed which is causing the problem.
  This happened with multiple upgrades of the kernel.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-29-generic 4.15.0-29.31
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   omer  10948 F...m pulseaudio
   /dev/snd/controlC0:  gdm5804 F pulseaudio
omer  10948 F pulseaudio
  Date: Mon Jul 23 15:42:40 2018
  DpkgTerminalLog:
   Setting up linux-image-4.15.0-29-generic (4.15.0-29.31) ...
   depmod: FATAL: renameat(/lib/modules/4.15.0-29-generic, modules.dep.tmp, 
/lib/modules/4.15.0-29-generic, modules.dep): No such file or directory
   dpkg: error processing package linux-image-4.15.0-29-generic 
(--configure):
installed linux-image-4.15.0-29-generic package post-installation script 
subprocess returned error exit status 1
  ErrorMessage: installed linux-image-4.15.0-29-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2017-07-05 (382 days ago)
  InstallationMedia: Ubuntu 17.04